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 <gregkh@xxxxxxxxxxxxxxxxxxx>: > > > 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? > > > > > > caravena@caravena-530U3C-530U4C:~$ lsusb -v -s3:2 > > > > Bus 003 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse > > Couldn't open device, some information will be missing > > Device Descriptor: > > bLength 18 > > bDescriptorType 1 > > bcdUSB 2.00 > > bDeviceClass 0 (Defined at Interface level) > > bDeviceSubClass 0 > > bDeviceProtocol 0 > > bMaxPacketSize0 8 > > idVendor 0x046d Logitech, Inc. > > idProduct 0xc077 M105 Optical Mouse > > bcdDevice 72.00 > > iManufacturer 1 > > iProduct 2 > > iSerial 0 > > bNumConfigurations 1 > > Configuration Descriptor: > > bLength 9 > > bDescriptorType 2 > > wTotalLength 34 > > bNumInterfaces 1 > > bConfigurationValue 1 > > iConfiguration 0 > > bmAttributes 0xa0 > > (Bus Powered) > > Remote Wakeup > > MaxPower 100mA > > Interface Descriptor: > > bLength 9 > > bDescriptorType 4 > > bInterfaceNumber 0 > > bAlternateSetting 0 > > bNumEndpoints 1 > > bInterfaceClass 3 Human Interface Device > > bInterfaceSubClass 1 Boot Interface Subclass > > bInterfaceProtocol 2 Mouse > > iInterface 0 > > HID Device Descriptor: > > bLength 9 > > bDescriptorType 33 > > bcdHID 1.11 > > bCountryCode 0 Not supported > > bNumDescriptors 1 > > bDescriptorType 34 Report > > wDescriptorLength 46 > > Report Descriptors: > > ** UNAVAILABLE ** > > Endpoint Descriptor: > > bLength 7 > > bDescriptorType 5 > > bEndpointAddress 0x81 EP 1 IN > > bmAttributes 3 > > Transfer Type Interrupt > > Synch Type None > > Usage Type Data > > wMaxPacketSize 0x0004 1x 4 bytes > > bInterval 10 > > Your device has an interrupt endpoint in there, odd. This is not the same device that the original message complained about. Compare the vendor and product ID numbers with the dmesg log: [ 2.452110] usb 3-2: New USB device found, idVendor=0458, idProduct=0186 [ 2.452113] usb 3-2: New USB device strings: Mfr=4, Product=40, SerialNumber=0 [ 2.452115] usb 3-2: Product: Wired Mouse [ 2.452117] usb 3-2: Manufacturer: KYE SYSTEMS CORP. [ 2.458338] hidraw: raw HID events driver (C) Jiri Kosina [ 2.465370] usbhid 3-2:1.1: couldn't find an input interrupt endpoint In order to diagnose the problem, we need to see the "lsusb -v" output for the device that's causing the problem. Alan Stern > Does it still work properly? Is this a regression from an older kernel > version? If so, can you use 'git bisect' to track down the offending > commit? > > thanks, > > greg k-h > -- > To unsubscribe from this list: send the line "unsubscribe linux-usb" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
