On Sat, May 05, 2007 at 07:34:30AM -0700, Nick Jacobs wrote: > > > Graham Seaman wrote: > > > > 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 > > > I had a similar problem and found that what happens is that Etch can assign > a different lp device number to the printer every time it's turned on. So if > your CUPS printer is set up as /dev/usb/lp0, CUPS won't see anything on lp0. > lsusb tells you what the device number is. In your case, it seems to be 28 > (from above). So if you had reconfigured the printer as /dev/usb/lp28, it > would have worked. This means you have to reconfigure the printer every time > you turn it on and off again, which sucks. But at least you will be able to > print. you can write a custom udev rule to correct this problem, if that is indeed the problem. google on "writing udev rules" and you'll get the how-to in the first couple hits A
Attachment:
signature.asc
Description: Digital signature