Re: usb/cups printer problem after etch upgrade
Thanks for the response! Answers inline below: basically everything
seems to be right - but cups still thinks the printer is paused...
Florian Kulzer wrote:
On Thu, Apr 26, 2007 at 15:18:52 +0100, graham wrote:
I have a server running cups, with a wireless usb connector connected to a
remote Brother 5040 laser printer. It's always worked fine, modulo a little
crackle on the television when printing ;-)
After upgrading the server to etch (without any major problems) cups no
longer sees the printer. Cups is running ok, and knows about the printer,
but the web interface always displays the message:
" HL5040 (Default Printer) "Printer not connected; will retry in 30
lsusb shows that the printer is there, and visible over wireless:
Bus 003 Device 002: ID 13fd:0540
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 028: ID 04f9:0016 Brother Industries, Ltd
Bus 001 Device 001: ID 0000:0000
lsmod shows I have the usb modules:
ehci_hcd 27144 0
ohci_hcd 17540 0
sis900 21120 0
mii 5376 1 sis900
usbcore 109444 5 usblp,usb_storage,ehci_hcd,ohci_hcd
I guess this is yet another strangeness with changes to udev?
That is possible, but it could also be due to the changes between CUPS
1.1 and 1.2. AFAIK, some ways of specifying the DeviceURI have become
obsolete for the new version.
Seems likely, though I haven't spotted the new way in the docs. There's
another etch user on the cups mailing list with a similar-sounding
problem (but no answers).
The obligatory checklist for the udev transition is:
Did you purge hotplug?
apt-get remove hotplug
Reading package lists... Done
Building dependency tree... Done
Package hotplug is not installed, so not removed
Did you upgrade to the 2.6.18 kernel?
You can run
tail -fn0 /var/log/syslog | sed 's/.*kernel: //'
ohci_hcd 0000:00:03.0: wakeup
usb 1-1: new full speed USB device using ohci_hcd and address 83
usb 1-1: configuration #1 chosen from 1 choice
drivers/usb/class/usblp.c: usblp0: USB Bidirectional printer dev 83 if 0
alt 0 proto 2 vid 0x04F9 pid 0x0016
and check if udev creates a device node when the printer is switched on
or when you plug in the usb connector. (Press CTRL+C to return to the
Has anyone else run into the same problem, or found a solution?
Post the output that you get when you run
direct usb://Brother/HL-5040%20series "Brother HL-5040 series" "Brother
HL-5040 series USB #1" "MFG:Brother;CMD:PJL,PCL,PCLXL;MDL:HL-5040