[Bug 35638] Re: Printer is not detected properly over USB
george.p.whitmore at gmail.com
Fri Apr 11 12:04:39 UTC 2008
Use a parallel centronics printer cable with your R51. It works perfect for
both windows (any) and Linux (any)
I don't have a parallel in port on my new T61, so have to use USB. Still
haven't heard about any Cups fixes to solve the USB problem with early HP
On Fri, Apr 11, 2008 at 12:26 AM, dracon <picky2k at yahoo.com> wrote:
> Have this identical problem but being a nube have no real clue how to
> >From above:
> "On my R51 connected to the Laserjet4 running WindowsXP, I had to tell
> Windows to use the USB port to find the Printer, it does that and works.
> That could be a way to fix it with Linux CUPS."
> I have same condition except:
> Windows 2K, processor self assembled (INTELD865PERL MB/1.5GB)
> LJ4 on Parallel to USB cable
> HP 890c Deskjet on same cable type.
> My Ubuntu system is Gutsy. (7.10)
> HP 890c never (well almost never) fails to identify and jobs will follow
> it if usb cable is moved to another usb port.
> HP LJ4 almost never identifies.
> W2k is rock solid on both printers using these cables so the cables must
> be passing device ids. Up to now Ive not found many things Windoze can do
> the Ubuntu could not. This appears to be one of those more noticeable
> Sometimes a reboot will find the HP4 but usually not. Once found it can be
> added and functions until a reboot.
> Have never seen it drop once found until the system is rebooted. Then it
> will show in the installed printers list but will not print.
> If this is a bug that has been opened www.cups.org can you point me to
> the bug report and I'll follow it there.
> lpinfo and lsusb runs attached
> latest lpinfo -v (it varies from time to time)
> $ lpinfo -v
> network socket
> network beh
> direct usb://HP/DESKJET%20890C
> direct hpfax
> direct hp
> network http
> network ipp
> network lpd
> direct parallel:/dev/lp0
> direct parallel:/dev/lp1
> file cups-pdf:/
> direct scsi
> network smb
> Coincident lsusb output:
> $ lsusb
> Bus 008 Device 009: ID 06e1:0709 ADS Technologies, Inc.
> Bus 008 Device 008: ID 067b:2305 Prolific Technology, Inc. PL2305 Parallel
> Bus 008 Device 007: ID 047e:2892 Agere Systems, Inc. (Lucent)
> Bus 008 Device 006: ID 0409:005a NEC Corp.
> Bus 008 Device 001: ID 0000:0000
> Bus 007 Device 005: ID 14cd:6600
> Bus 007 Device 004: ID 05e3:0760 Genesys Logic, Inc. Card Reader
> Bus 007 Device 002: ID 03f0:1705 Hewlett-Packard <my ed: this is a
> scanner not printer>
> Bus 007 Device 001: ID 0000:0000
> Bus 003 Device 001: ID 0000:0000
> Bus 005 Device 001: ID 0000:0000
> Bus 004 Device 001: ID 0000:0000
> Bus 001 Device 003: ID 067b:2305 Prolific Technology, Inc. PL2305 Parallel
> Bus 001 Device 001: ID 0000:0000
> Bus 002 Device 001: ID 0000:0000
> Bus 006 Device 004: ID 0802:2800 Mako Technologies, LLC
> Bus 006 Device 001: ID 0000:0000
> Printer is not detected properly over USB
> You received this bug notification because you are a direct subscriber
> of the bug.
** Attachment added: "unnamed"
Printer is not detected properly over USB
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to linux-source-2.6.15 in ubuntu.
More information about the kernel-bugs