Re: usb/cups printer problem after etch upgrade

On Sun, Apr 29, 2007 at 20:32:59 +0100, graham wrote:
Florian Kulzer wrote:

find /dev/ -name usblp0 -exec ls -l {} \;
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
I'd still like to see the output of the above command just to be sure.

Oops, sorry thought I'd checked this but I hadn't.
/dev/usblp0 does not exist. There is a /dev/usb/lp0, however. Here are all
the usb devices:

snoopy> find /dev/ -name "usb*" -exec ls -l {} \;

[...]

crw-rw---- 1 root lp 180, 0 2005-02-26 06:43 lp0
crw-rw---- 1 root lp 180, 1 2005-02-26 06:43 lp1

[ snip: and so on ]

I think these are all from /dev/.static/dev/. You have to find out which
device node is created for the printer in /dev/ outside of .static.
Compare a directory listing before and after you plug in the printer if
necessary. You can use something like

find /dev/ | sort > before.txt

< plug in the printer >

find /dev/ | sort > after.txt

diff -u before.txt after.txt

I need to see the properties of the newly-created device node (and only
of this one). Make sure it is really /dev/usb/lp0.

[...]

snoopy>/usr/lib/cups/backend/usb
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
series;CLS:PRINTER;"
So far, so good. Now let's see how the printer is defined for CUPS. Post
the output of
grep DeviceURI /etc/cups/printers.conf
DeviceURI usb://Brother/HL-5040%20series

Looks identical to the /dev name to me.
Most USB DeviceURIs that I find on the web have "?serial=..." appended
after the <model> string. Maybe the problem is that in your case no
serial number is found by the USB backend of CUPS. (I am speculating
here; I never used CUPS with a USB printer.)

Now he tells me ;-)
Seems a little unlikely though as this setup all worked fine with sarge

You could try:
DeviceURI usb:/dev/...
or
DeviceURI USB #1

I've tried
DeviceURI usb:/dev/lp0

which didn't change anything

What about "usb:/dev/usb/lp0"?

You could also try to find a serial number like this:

udevinfo -a -p $(udevinfo -q path -n /dev/usb/lp0) | grep -i serial

Another thing that might be important is how you handled the cupsys
configuration files during the upgrade. Did you keep your old ones or
did you replace them with the maintainer's new versions?

--
Regards, | http://users.icfo.es/Florian.Kulzer
Florian |


--
To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx
with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx

Relevant Pages

  • Re: usb/cups printer problem after etch upgrade
    ... Florian Kulzer wrote: ... I have a server running cups, with a wireless usb connector connected to ... some ways of specifying the DeviceURI have become ... Did you purge hotplug? ...
    (Debian-User)
  • Re: usb/cups printer problem after etch upgrade
    ... Following which I power cycled the printer and rebooted the server. ... serial number is found by the USB backend of CUPS. ... DeviceURI usb:/dev/... ... To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx ...
    (Debian-User)
  • Re: CUPS, USB printers & "Permission Denied"
    ... watched as nothing happened (it didn't display any messages in the web ... I found that the usb backend stalled here before actually doing any ... DeviceURI file:/dev/ulpt0 ... Then restart cups. ...
    (freebsd-questions)
  • Re: usb/cups printer problem after etch upgrade
    ... configuration files during the upgrade. ... After I changed DeviceURI to /dev/usb/lp0, the cups admin panel immediately showed 'new printer found'. ... Make sure that you choose the right driver for the printer; ... To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx with a subject of "unsubscribe". ...
    (Debian-User)