Re: [Kernel] usbhid 3-2:1.1: couldn't find an input interrupt endpoint

2017-02-23 Thread Alan Stern
On Thu, 23 Feb 2017, Cristian wrote: > Hello, > > lsusb -v; https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667370 Bus 003 Device 003: ID 0458:0186 KYE Systems Corp. (Mouse Systems) Couldn't open device, some information will be missing Device Descriptor: bLength18 bDe

Re: [Kernel] usbhid 3-2:1.1: couldn't find an input interrupt endpoint

2017-02-23 Thread Cristian
Hello, lsusb -v; https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667370 Regards, -- Cristian 2017-02-23 12:40 GMT-03:00 Alan Stern : > On Thu, 23 Feb 2017, Greg KH wrote: > >> On Tue, Feb 21, 2017 at 01:56:22PM -0300, Cristian wrote: >> > 2017-02-21 2:04 GMT-03:00 Greg KH : >> > > On Mo

Re: [Kernel] usbhid 3-2:1.1: couldn't find an input interrupt endpoint

2017-02-23 Thread Alan Stern
On Thu, 23 Feb 2017, Greg KH wrote: > On Tue, Feb 21, 2017 at 01:56:22PM -0300, Cristian wrote: > > 2017-02-21 2:04 GMT-03:00 Greg KH : > > > On Mon, Feb 20, 2017 at 03:28:37PM -0300, Cristian wrote: > > >> Hello, > > >> > > >> dmesg: > > >> [2.465370] usbhid 3-2:1.1: couldn't find an input in

Re: [Kernel] usbhid 3-2:1.1: couldn't find an input interrupt endpoint

2017-02-23 Thread Greg KH
On Tue, Feb 21, 2017 at 01:56:22PM -0300, Cristian wrote: > 2017-02-21 2:04 GMT-03:00 Greg KH : > > On Mon, Feb 20, 2017 at 03:28:37PM -0300, Cristian wrote: > >> Hello, > >> > >> dmesg: > >> [2.465370] usbhid 3-2:1.1: couldn't find an input interrupt endpoint > > > > And does this cause a prob

Re: [Kernel] usbhid 3-2:1.1: couldn't find an input interrupt endpoint

2017-02-21 Thread Cristian
Hello, lsusb -v Thannks, -- Cristian 2017-02-21 4:29 GMT-03:00 Oliver Neukum : > Am Montag, den 20.02.2017, 15:28 -0300 schrieb Cristian: >> Hello, >> >> dmesg: >> [2.465370] usbhid 3-2:1.1: couldn't find an input interrupt >> endpoint > > Most likely it does not have an interrupt endpoin

Re: [Kernel] usbhid 3-2:1.1: couldn't find an input interrupt endpoint

2017-02-21 Thread Cristian
2017-02-21 2:04 GMT-03:00 Greg KH : > On Mon, Feb 20, 2017 at 03:28:37PM -0300, Cristian wrote: >> Hello, >> >> dmesg: >> [2.465370] usbhid 3-2:1.1: couldn't find an input interrupt endpoint > > And does this cause a problem? Does the device not work? > What is the output of 'lsusb -v -s3:2' w

Re: [Kernel] usbhid 3-2:1.1: couldn't find an input interrupt endpoint

2017-02-20 Thread Oliver Neukum
Am Montag, den 20.02.2017, 15:28 -0300 schrieb Cristian: > Hello, > > dmesg: > [2.465370] usbhid 3-2:1.1: couldn't find an input interrupt > endpoint Most likely it does not have an interrupt endpoint. You will need to provide "lsusb -v" not lspci, as this bug is about a USB device. Is this a

Re: [Kernel] usbhid 3-2:1.1: couldn't find an input interrupt endpoint

2017-02-20 Thread Greg KH
On Mon, Feb 20, 2017 at 03:28:37PM -0300, Cristian wrote: > Hello, > > dmesg: > [2.465370] usbhid 3-2:1.1: couldn't find an input interrupt endpoint And does this cause a problem? Does the device not work? What is the output of 'lsusb -v -s3:2' with the device plugged in? thanks, greg k-h

[Kernel] usbhid 3-2:1.1: couldn't find an input interrupt endpoint

2017-02-20 Thread Cristian
Hello, dmesg: [2.465370] usbhid 3-2:1.1: couldn't find an input interrupt endpoint Thanks, -- Cristian [0.00] microcode: microcode updated early to revision 0x29, date = 2013-06-12 [0.00] Linux version 4.10.0-041000-generic (kernel@gloin) (gcc version 6.2.0 20161005 (Ubuntu