From: Gunther Mayer <gunther.mayer@gmx.net>
To: Greg KH <greg@kroah.com>
Cc: Jan-Marek Glogowski <glogow@stud.fbi.fh-darmstadt.de>,
linux-kernel@vger.kernel.org
Subject: Re: USB Microsoft Natural KeyB not recogniced as a HID device
Date: Wed, 27 Mar 2002 20:00:18 +0100 [thread overview]
Message-ID: <3CA216C2.8CA0D6F5@gmx.net> (raw)
In-Reply-To: <20020325183011.GA29011@kroah.com> <Pine.LNX.4.30.0203251957590.5375-200000@stud.fbi.fh-darmstadt.de> <20020325192216.GD29011@kroah.com>
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
next prev parent reply other threads:[~2002-03-27 19:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-25 17:57 USB Microsoft Natural KeyB not recogniced as a HID device Jan-Marek Glogowski
2002-03-25 18:30 ` Greg KH
2002-03-25 19:07 ` Jan-Marek Glogowski
2002-03-25 19:22 ` Greg KH
2002-03-27 19:00 ` Gunther Mayer [this message]
2002-03-27 19:24 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3CA216C2.8CA0D6F5@gmx.net \
--to=gunther.mayer@gmx.net \
--cc=glogow@stud.fbi.fh-darmstadt.de \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.