On Mon, Aug 06, 2018 at 11:31:11AM -0700, Nick Desaulniers wrote:
> On Mon, Aug 6, 2018 at 11:27 AM Alan Stern <st...@rowland.harvard.edu> wrote:
> >
> > On Mon, 6 Aug 2018, Nick Desaulniers wrote:
> >
> > > On Mon, Jul 30, 2018 at 1:24 PM Alan Stern <st...@rowland.harvard.edu> 
> > > wrote:
> > > >
> > > > On Mon, 30 Jul 2018, Nick Desaulniers wrote:
> > > >
> > > > > Hello,
> > > > > Today my usb keyboard stopped working:
> > > > >
> > > > > [513672.838235] usbhid 3-10.1:1.0: couldn't find an input interrupt 
> > > > > endpoint
> > > > >
> > > > > I happen to have two models of the same keyboard (Das Keyboard
> > > > > Ultimate 4C), from the working one:
> > > > > [   37.865738] usb 1-1.1: New USB device found, idVendor=24f0, 
> > > > > idProduct=0142
> > > > > and the broken one:
> > > > > [513672.837646] usb 3-10.1: New USB device found, idVendor=24f0, 
> > > > > idProduct=0000
> > > > >
> > > > > This causes the product to be misidentified.  Is something wrong with
> > > > > the keyboard that's causing it to misreport the idProduct?
> > > >
> > > > Probably it lost some of its firmware.
> > >
> > > Is it possible to ask Linux to remount this device with a new idProduct?
> >
> > It's not possible to change the idProduct value.
> >
> > It is possible to try to use the keyboard in spite of the wrong
> > idProduct.  In fact, that's what your computer tried to do.  But it
> > didn't work, as you can see from the "couldn't find an input interrupt
> > endpoint" error message in the log
> 
> There's nothing for handling quirks? Surely not all devices are so
> well behaved.  Worst case I guess I could modify whatever maps
> idProducts to drivers in *my* kernel and use that?

No, your firmware is really broken and it is not responding with a full
USB descriptor, it is messed up, there's nothing that any operating
system can do about it, sorry.

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to