Greg KH wrote:
> On Mon, Mar 25, 2002 at 08:07:21PM +0100, Jan-Marek Glogowski wrote:
> > Hi Greg
> >
> > [schnipp]
> > > Can you try the patches at:
> > > http://marc.theaimsgroup.com/?l=linux-usb-devel&m=101684196109355
> > > and also:
> > > http://marc.theaimsgroup.com/?l=linux-usb-devel&m=101684207509482
> > >
> > > And let us know if they help you out?
> > [schnapp]
> >
> > Applied both patches - the keyboard is detected again, but I still have
> > some errors in the lsusb-output (see attachment).
>
> Sounds like a device that is lying about it's strings. If the device
> works, I wouldn't worry about it :)
Greg, bad guessing. This is not the device's fault but the linux usb
drivers are buggy.
The messages:
bInterfaceClass cannot get string descriptor 1, error = Broken
pipe(32)
cannot get string descriptor 2, error = Broken pipe(32)
go away after "rmmod hid" (or whatever driver is using the device).
This is a long standing bug.
Regards, Gunther
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Mar 31 2002 - 22:00:13 EST