Bugzilla – Bug 287091
Printing doesn't work on a Laserjet 5P
Last modified: 2007-06-26 05:45:51 UTC
Printing doesn't work on my HP laserjet 5P. I found the problem already in alpha 4, i don't know about older versions as i didn't install it on this system. I'm using this PDD filter: HP LaserJet 5P Foomatic/ljet4 (recommended) (HP/LaserJet_5P-ljet4.ppd.gz) I've also tried: HP LaserJet 5P Foomatic/hpijs (manufacturer-PPDs/hplip/HP-LaserJet_5P-hpijs.ppd.gz) Both didn't work. I get onlu bogus charakter on the print out.
What exactly do you mean with "bogus charakter on the print out"? When you print via echo Hello | lp -d <queue-name> do you get the characters 'H' 'e' 'l' 'l' 'o' printed but they look ugly (i.e. like a bad font) or do you get nonsense characters printed like "$eg~'u&&Tgdf51""?#**:;847hedf..." To get debugging info from CUPS see http://en.opensuse.org/SDB:CUPS_in_a_Nutshell "If problems are encountered": 1. Set the "LogLevel debug" in /etc/cups/cupsd.conf. 2. Stop cupsd. 3. Move /var/log/cups/error_log* to another location (or delete it) in order to avoid having to search through gigantic log files. 4. Start cupsd. 5. Retry the action leading to the problem. 6. Now /var/log/cups/error_log contains many messages that are useful for troubleshooting.
echo Hello | lp -d laserjet5p Prints perfectly. Also printing from OpenOffice that didn't works works properly. The problem occured again when i started configuring via yast/prinetr again. The printer didn't do anything (hang?) after i tried to print a test page with photo. Also a restart of cups didn't fix the problem. I didn't power cycle the printer yet.
Created attachment 148224 [details] cups log files in /var/log/cups
In your CUPS error_log there are error messages: -------------------------------------------------------------------------- Unable to bind socket for address 127.0.0.1:631 - Address already in use. -------------------------------------------------------------------------- This means that some other process has already the IPP port 631 in use. Use "netstat -nap | grep 631" (as root) to find out which process it is and kill it before you restart CUPS. There are no other error messages of interest. In particular "grep PID" in your CUPS error_log results that all filters and the "parallel" backend seem to run successfully for all print jobs which are logged in your CUPS error_log. By the way: I asked explicitely for the log for exactly one failed job. It doesn't help at all to provide tons of arbitrary logs and let me guess from it what might perhaps be a failed job. As it works some time and then not, it looks like one more instance of the various parallel port problems (see also bug #286361). There are some bug reports about problems with the parallel port in our Novell/Suse Bugzilla. A good report to start is bug #185135. See also the other bug reports which are mentioned there. The current workaround is to experiment with various BIOS settings and explicite additional settings in /etc/modprobe.conf to find a setup, which actually works in a particular problematic case. The traditional safe BIOS settings are: IO address 378 (hexadecimal) Interrupt 7 Mode "Normal" or "SPP" or "Output-Only" (other modes may not work) DMA is disabled (should be automatically switched off using the modes above) You might have to use a higher-level parport mode (some kind of fast bidirectional mode). Those modes (EPP or even ECP) normally require an interrupt and ECP additionally requires DMA. To activate the interrupt mode, set in /etc/modprobe.conf something like "options parport_pc io=0x378 irq=7" where io and irq must match to your BIOS settings. Make sure that the IRQ which you use for the parallel port is not used by any other stuff (check /proc/interrupts) and see our online documentation (package opensuse-manual_en) chapter "Printer Operation", section "Troubleshooting", sub-section "Parallel Ports". *** This bug has been marked as a duplicate of bug 185135 ***