Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 7625 - Printing is broken in RedHat 6.1
Printing is broken in RedHat 6.1
Product: Red Hat Linux
Classification: Retired
Component: lpr (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Bernhard Rosenkraenzer
Depends On:
  Show dependency treegraph
Reported: 1999-12-06 04:29 EST by charshman
Modified: 2008-05-01 11:37 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-02-07 12:35:39 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description charshman 1999-12-06 04:29:36 EST
RedHat 6.1, as it ships (verified with both the Professional
installation I
did, as well as with the $3 copy I got at Comdex), has broken printing.
We had to add the following line to /etc/conf.modules on every computer
we had in the shop (all more or less standard x86 boxes with LPT ports
set to SPP, EPP, or ECP on 0x378/IRQ7):

alias parport_lowlevel parport_pc

A quick search of deja.com will reveal this is a problem faced by many
RedHat users, but a search of the knowledgebase does not turn up this

Could you please look into this, and post it as an errata or whatever is

RedHat's policy for dealing with such things?  Thanks!

Chris Harshman
Comment 1 James Culbertson 1999-12-29 20:45:59 EST
Agreed that this is very annoying and should be put on the
Knowledge Base ASAP. I wasted an hour on this one before
finding it on deja.com, and this was apparently submitted
early in December.
Comment 2 Bernhard Rosenkraenzer 2000-02-07 12:35:59 EST
This was a bug in the installer - it should have added the line to conf.modules
in the first place.

It has been listed on the "gotchas" page since the problem was discovered a
couple of days after the 6.1 release.

6.2 (beta3, as released today) doesn't have the problem.

Note You need to log in before you can comment on or make changes to this bug.