Bug 8278 - parallel port not detected after installation
parallel port not detected after installation
Status: CLOSED DUPLICATE of bug 5680
Product: Red Hat Linux
Classification: Retired
Component: control-panel (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: johnsnom
Depends On:
  Show dependency treegraph
Reported: 2000-01-07 16:07 EST by fbadescu
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-02-04 21:09:34 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 fbadescu 2000-01-07 16:07:05 EST
I could not set up a printer in control panel after I have installed RH
Linux 6.1 over an older version (6.0). Reason: the program did not detect
any parallel ports (lp0,lp1,lp2). Trying to configure it manually gave me
no good result either. I didn't resolve this even when I have used your new
boot disks from your errata web site.Reloading RH Linux 6.0, then UPGRADING
to v6.1 worked around this problem, and I had again the parallel port
correctly detected.

This may seem like a good solution, but you have to take into account the
fact that there are a lot of customers that buy RH Linux 6.1 for the first

The system I worked on is:
AMD K6-220 MHz, 64 MB RAM, two IDE HDD (Western Digital Caviar), IDE
CD-ROM. Linux is on the slave disk (hdb1...hdb8). The master disk (hda*)is
occupied by Windows NT. I boot by using LILO, which is in MBR, on hda.

I hope you will solve this problem and keep me informed about this issue.

Thank you.

Ferdi Badescu.
Comment 1 Nalin Dahyabhai 2000-02-04 21:09:59 EST
This is a duplicate of bug #5680.  Try the modules package from Raw Hide, or add
this to your /etc/conf.modules to work around it:
alias parport_lowlevel parport_pc

*** This bug has been marked as a duplicate of 5680 ***

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