Re: usb/cups printer problem after etch upgrade
On Thu, Apr 26, 2007 at 15:18:52 +0100, graham wrote:
> Hi,
>
> 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
> seconds..."
>
> lsusb shows that the printer is there, and visible over wireless:
>
> snoopy: lsusb
> 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:
>
> snoopy: lsmod
> <snip>
> 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.
The obligatory checklist for the udev transition is:
Did you purge hotplug?
Did you upgrade to the 2.6.18 kernel?
You can run
tail -fn0 /var/log/syslog | sed 's/.*kernel: //'
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
shell prompt.)
> Has anyone else run into the same problem, or found a solution?
Post the output that you get when you run
/usr/lib/cups/backend/usb
--
Regards, | http://users.icfo.es/Florian.Kulzer
Florian |
Reply to: