Bug 102932

Summary: Install did not detect HP Deskjet 500 on LP0
Product: [openSUSE] SUSE LINUX 10.0 Reporter: Doug Beattie <dbeattie>
Component: PrintingAssignee: Johannes Meixner <jsmeix>
Status: RESOLVED DUPLICATE QA Contact: Johannes Meixner <jsmeix>
Severity: Normal    
Priority: P5 - None    
Version: Beta 1   
Target Milestone: ---   
Hardware: i686   
OS: SUSE Other   
Whiteboard:
Found By: Beta-Customer Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Doug Beattie 2005-08-09 02:18:07 UTC
Install did not detect a HP Deskjet 500 printer on LP0. Adding it manually did
not work either. This same hardware work on SuSE Pro 9.1
Comment 1 Johannes Meixner 2005-08-09 08:03:38 UTC
No more info and nothing from the logs except "it doesn't work"?

Is you parallel port correctly configured?
See the printed 9.1 manual or
and
http://portal.suse.com/sdb/en/2000/08/jsmeix_print-einrichten.html
"Prerequisites"
and
http://portal.suse.com/sdb/en/2002/04/jsmeix_print-device-parallel.html
how to set up the parallel port.

Use commads like
  dmesg | grep -i 'parport' | tail -n 100
or
  grep -i 'parport' /var/log/messages | tail -n 100
to get the last 100 (error)-messages regarding the parallel port.
Comment 2 Doug Beattie 2005-08-10 19:34:36 UTC
The following is what is repeated from the dmesg query:
lp0: using parport0 (interrupt-driven).
parport: PnPBIOS parport detected.
parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE,EPP]

The same hardware configuration, booted with 9.1, works fine.
I believe the bios and printer are set up correctly.

Please let me know if you further information.
Comment 3 Johannes Meixner 2005-08-15 12:04:11 UTC
On the one hand it looks good because your parport was
autodetected and it seems to be set up (in particular
the lp module is loaded).

On the other hand I miss an output of the printer model
like on my test machine:
------------------------------------------------------------
parport0: PC-style at 0x378 (0x778) [PCSPP,TRISTATE,EPP]
parport0: irq 7 detected
parport0: Printer, HEWLETT-PACKARD DESKJET 990C
lp0: using parport0 (polling).
------------------------------------------------------------

Check your BIOS whether there is really the IO port 0x378 set
and check your BIOS whether there is really the interrupt 7 set.
See the above mentioned support database articles how to set it up
using the recommended polling mode.

Questions:

Can you configure the printer manually in YaST?
Does it print the YaST test-page after you selected
the connection (i.e. first parallel port) and the
model manually in YaST?

Does it print "hello" using (as root):
echo -en "\rhello\r\f" >/dev/lp0
Comment 4 Doug Beattie 2005-08-16 02:13:59 UTC
First attempt to execute your echo test failed.
I had already done a manual setup through Yast as the install did not detect the
printer.
The hardware appears to be set correctly.
As I said before, this same hardware works without change on my 9.1 installation
I can boot into.

Yast does not print out the test page.

Yast shows the "Connection" as "Parallel printer on /dev/lp0"

An ls -l of /dev/lp0 shows "crw-rw----  1 root lp 6, 0 2005-08-15 19:37 /dev/lp0"

I've never seen this not work so I am baffled. Any thing else you can think of
for me to try?
Comment 5 Doug Beattie 2005-08-16 02:24:23 UTC
*** Update ***
I rebooted and now the echo outputs to the printer.
Additional reboots show the echo test of output direct to /dev/lp0 as root works.

The "Test Text Printing" page from Yast still does not print.
Comment 6 Johannes Meixner 2005-08-16 07:11:39 UTC
Yesterday I tested parallel port printing on x86_64 hardware
and here I detected that the kernel-module "lp" becomes
unloaded during startup of the YaST printer config tool.

To verify on your machine do as root:

lsmod | egrep 'lp|parport'

and you should get at least the modules parport, parport_pc, lp

Now start YaST printer config tool and do again "lsmod | egrep 'lp|parport'"
and you may see that now lp is missing.
If yes, do "modprobe lp" and testpage printing in YaST should work.

Added YaST printer config tool maintainer to Cc.


Comment 7 Johannes Meixner 2005-08-16 07:47:45 UTC
See bug #104874 which may show the reason of this problem.
And see bug #104875 which is another problem.
Comment 8 Doug Beattie 2005-08-16 14:28:57 UTC
The condition you described is the problem. After a modprobe lp to put back the
driver the test page works fine.
I guess the problem is the Yast printer config tool.
Thanks.
Comment 9 Johannes Meixner 2005-08-16 15:03:50 UTC

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