Re: cups on wheezy problem
On 08/09/2011 10:54 AM, Camaleón wrote:
On Mon, 08 Aug 2011 14:54:26 -0400, Wayne Topa wrote:
On 08/08/2011 02:02 PM, Wayne Topa wrote:
(...)
I will re-do the question... Do you think the above error has
something to do with udev/kernel not detecting the printer?
It is not detecting the usb to parallel interface, yes.
But it is listed and visible when you run "lsusb" :-?
"mtp-probe" sounds to me like another thing (used on/for USB media
players):
That error was from wheezy when i plugged in the usb printer cable.
Here is what I see in Squeeze when I plug in that cable:
Aug 8 13:52:38 dj kernel: [14830.023088] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Aug 8 13:52:38 dj kernel: [14830.023092] usb 3-1: Product: IEEE-1284 Controller
Aug 8 13:52:38 dj kernel: [14830.023095] usb 3-1: Manufacturer: Prolific Technology Inc.
Aug 8 13:52:38 dj kernel: [14830.034204] usblp1: USB Bidirectional printer dev 3 if 0 alt 1 proto 2 vid 0x067B pid 0x2305
Wheezy
Aug 9 11:26:08 dj kernel: [ 551.816184] usb 3-1: usbfs: interface 0
claimed by usblp while 'usb' sets config #1
Note: Bug#545288: CUPS 1.4.0-4 doesn't find USB-printer Date: Sun, 6
Sep 2009 12:39:46 +0200
And is the same as what I get in 2011????
Cups interface Printer Tab
6P HP LaserJet 6P HP LaserJet 6P Foomatic/ljet4 Paused -
"/usr/lib/cups/backend/usb failed"
Draft Draft HP6P HP LaserJet 6P - CUPS+Gutenprint v5.2.7
Processing - "Waiting for printer to become available..."
[VT3 root@dj-WHEEZY]
~# dpkg -S /usr/lib/cups/backend/usb
dpkg-query: no path found matching pattern /usr/lib/cups/backend/usb.
[VT3 root@dj-WHEEZY]
~# dpkg -S /usr/lib/cups/backend/
foomatic-filters, cups, cups-pdf: /usr/lib/cups/backend
[VT3 root@dj-WHEEZY] **** This differs from the stable cups
~# lpinfo -v
network beh
file cups-pdf:/
direct scsi
network http
network socket
network lpd
network ipp
***** No USB interface???
Have you tried to set the printer from CUPS web interface?
As shown above, yes. I still can't rule out udevd OR Cups as the problem.
Why would no one else be having this problem? Make no sense to me.
Thanks again for being my sounding board. :-)
Wayne
Reply to: