Bug 59054 - cannot open /dev/lp0
cannot open /dev/lp0
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Tim Waugh
Brock Organ
Depends On:
  Show dependency treegraph
Reported: 2002-01-29 20:09 EST by Need Real Name
Modified: 2007-04-18 12:39 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-02-05 17:59:48 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
cannot open lp (273 bytes, text/plain)
2002-01-30 17:38 EST, Need Real Name
no flags Details
insmod and rmmod errors (1.76 KB, text/plain)
2002-01-31 17:37 EST, Need Real Name
no flags Details
rmmod (487 bytes, text/plain)
2002-01-31 20:41 EST, Need Real Name
no flags Details

  None (edit)
Description Need Real Name 2002-01-29 20:09:44 EST
Description of Problem:
trying to print with my Epson 640 color printer. Have everything set up in
printing control panel. On start up when LPD starts get the error -new cannot
open LP device. '/dev/lp0' no such address or device. Checked and dev package is
installed, LP0 file exist. lp is installed, and I presume running. Been working
with ticket manager for over 30 days now. Reccomends reporting as a bug, since
they have no problems using the epson printer.

Version-Release number of selected component (if applicable):

How Reproducible:

Steps to Reproduce:

Actual Results:

Expected Results:

Additional Information:
Comment 1 Tim Waugh 2002-01-30 02:27:47 EST
Please attach your /etc/modules.conf.

Also please try this and attach the resulting dmesg.out file:
1. Become root.
2. Run: dmesg -c > /dev/null
3. Run: rmmod lp
4. Run: rmmod parport_pc
5. Run: insmod parport_pc
6. Run: dmesg > dmesg.out

Also what are your BIOS settings for the on-board parallel port, presuming that
the parallel port you want to use is built in to the motherboard?
Comment 2 Need Real Name 2002-01-30 17:38:13 EST
Created attachment 44056 [details]
cannot open lp
Comment 3 Need Real Name 2002-01-30 17:44:49 EST
dmesg.out file was created, but has no contents, would not attach. Tried twice.
lp is not loaded, parport_pc is also not loaded, insmod parport_pc has error
when executed.

Hope this helps
Comment 4 Tim Waugh 2002-01-30 17:46:37 EST
Well, what was the error message exactly?

Also, what about the BIOS?
Comment 5 Need Real Name 2002-01-30 17:52:23 EST
BIOS settings for parallel port is set to auto and bidirectional
Comment 6 Tim Waugh 2002-01-31 03:38:39 EST
And the error message?
Comment 7 Need Real Name 2002-01-31 17:37:52 EST
Created attachment 44180 [details]
insmod and rmmod errors
Comment 8 Tim Waugh 2002-01-31 17:44:35 EST
What format is that in?  It looks like gibberish!
Comment 9 Need Real Name 2002-01-31 20:41:34 EST
Created attachment 44196 [details]
Comment 10 Tim Waugh 2002-02-01 03:14:50 EST
And after doing that, if you run 'dmesg', it displays nothing at all?
Comment 11 Need Real Name 2002-02-04 12:22:32 EST
I did once, after running the command 3 or 4 times did get a message that I had 
mail in var/spool/root. looked weird to me, is this what I am looking for?
Comment 12 Tim Waugh 2002-02-04 12:36:20 EST
No, it isn't.  Well, I guess there really aren't any kernel messages.  That
means that just couldn't find any port at 0x378, 0x278, 0x3bc, or on the PCI bus.

What base address does the BIOS say that the port should be at?
Comment 13 Need Real Name 2002-02-05 16:49:03 EST
changed my bios from auto select for Parallel port to enabled to find the port
address. It is 0x378 and IRQ 7. Since I have made that change I nolonger get the
cannot open /dev/lp0 on the lp start up. Just a green "ok", which is good, but
still cannot print.
Comment 14 Tim Waugh 2002-02-05 17:59:42 EST
Okay, BIOS configuration thing.  Closing.

As for still not being able to print, please check for other bugzilla entries
that may be relevant.  Also make sure that you upgrade to the latest errata
packages for printing.

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