Bug#352142: HP 1320 quit working except when set to "Save Toner" mode
On Tue, Feb 14, 2006 at 12:59:42AM -0200, Henrique de Moraes Holschuh wrote:
> This is bad. Which kernel? I recall older kernels were fubar and they
> caused those errors to show up, but that was at 2.6.12 or thereabouts, I
> think.
It's a 2.6.15 kernel from the Debian Etch linux-image-2.6.15-1-686
package (version 2.6.15-4).
> 1.3.1.1? Do you have an USB hub in the way? Try connecting the printer
> directly to the computer, just in case. Good USB2.0 hubs are hard to come
> by.
Yeah, I was going the USB hub in my Dell monitor. That seems to
have been part of the problem.
I tried plugging directly into the docking station of my laptop, rebooted,
and tried printing one of the documents that gave me errors in the past.
It still crashed my printer again, but I was able to get a cleaner
log of error messages after the reboot. It also seems to reset the
printer automatically about 5 minutes after the error; I never noticed
that before, but maybe I just always power-cycled the printer before
that happened.
At first, I thought it was producing less errors, but it actually seems
to be that the first time, it only produces the HP channel error, and
the other usblp errors only happen on subsequent printer crashes. I
also didn't see any hpiod error messages, but I think those mostly only
occured up if the printer was off or unresponsive when cups was trying
to send data, which might only happen with longer print jobs.
[booting...]
Feb 14 11:39:56 localhost kernel: drivers/usb/class/usblp.c: usblp0: USB Bidirectional printer dev 4 if 0 alt 1 proto 2 vid 0x03F0 pid 0x1D17
Feb 14 11:39:56 localhost kernel: usbcore: registered new driver usblp
Feb 14 11:39:56 localhost kernel: drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
Feb 14 11:39:57 localhost hpiod: 0.9.7 accepting connections at 59026...
[print something]
Feb 14 11:46:35 localhost kernel: drivers/usb/class/usblp.c: usblp0: error = -110 setting HP channel
[hplip resets the printer after 5 minutes?]
Feb 14 11:50:28 localhost kernel: usb 5-1.2: USB disconnect, address 4
Feb 14 11:50:28 localhost kernel: drivers/usb/class/usblp.c: usblp0: removed
Feb 14 11:50:38 localhost kernel: usb 5-1.2: new full speed USB device using ehci_hcd and address 9
Feb 14 11:50:38 localhost kernel: drivers/usb/class/usblp.c: usblp0: USB Bidirectional printer dev 9 if 0 alt 1 proto 2 vid 0x03F0 pid 0x1D17
[try printing again]
Feb 14 12:00:27 localhost kernel: drivers/usb/class/usblp.c: usblp0: nonzero read/write bulk status received: -2
Feb 14 12:00:27 localhost kernel: drivers/usb/class/usblp.c: usblp0: error -2 reading from printer
Feb 14 12:00:52 localhost kernel: drivers/usb/class/usblp.c: usblp0: error = -110 setting HP channel
[printer resets again]
Feb 14 12:04:46 localhost kernel: usb 5-1.2: USB disconnect, address 9
Feb 14 12:04:46 localhost kernel: drivers/usb/class/usblp.c: usblp0: removed
Feb 14 12:04:56 localhost kernel: usb 5-1.2: new full speed USB device using ehci_hcd and address 10
Feb 14 12:04:56 localhost kernel: drivers/usb/class/usblp.c: usblp0: USB Bidirectional printer dev 10 if 0 alt 1 proto 2 vid 0x03F0 pid 0x1D17
> > (But cupsd does still spins in an infinite loop if I try to list the available
> > "HP (HPLID)" PPD's.)
>
> Take a look on /usr/share/cups/models, make sure nothing in there (following
> symlinks, even) is not in a loop. I doubt CUPS is smart enough to break
> loops, it isn't smart enough for a lot of far more pertinent stuff.
No symlink cycles. There was a redundancy in that
/usr/share/cups/models/foomatic-rip -> /usr/share/ppd
and
/usr/share/cups/models/lpid -> /usr/share/ppd/lpid
but deleting the lpid symlink, didn't fix anything.
I guess I should file this as a separate bug report against cupsys.
> If nothing of the above helps, take it to the HPLIP forum on
> hpinkjet.sf.net, HP gives official support there even for tracking down
> hardware issues, as long as it is an HPLIP-supported printer (and yours is).
> They can't help you with CUPS, but they may be able to help if the usblp
> problem shows up again.
OK, I'll try to follow it up there when I have a chance. But since I
have a work around (using the USB Device URI), I'll probably just use
that for a while.
--
Jeffery von Ronne
Assistant Professor
Department of Computer Science
University of Texas at San Antonio
Reply to: