Your message dated Wed, 12 Sep 2012 18:47:57 +0200
with message-id <20120912164757.ga29...@entuzijast.net>
has caused the report #685360,
regarding AMD SB 750 + Logitech USB keyboard brokenness with Linux 3.2
(regression from 3.1)
to be marked as having been forwarded to the upstream software
author(s) Nestor Lopez Casado <nlopezca...@logitech.com>, Jiri Kosina
<jkos...@suse.cz>
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
685360: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=685360
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Hi,
The introduction of the HID_LOGITECH_DJ code in 3.2+ kernels apparently
broke my Logitech K350 Wave wireless keyboard.
The hid.debug=1 dmesg difference between 3.1.0 and 3.2.0 indicates:
drivers/hid/usbhid/hid-core.c: HID probe called for ifnum 0
-drivers/hid/usbhid/hid-core.c: submitting ctrl urb: Set_Report wValue=0x0200
wIndex=0x0000 wLength=1
-input: Logitech USB Receiver as
/devices/pci0000:00/0000:00:12.0/usb5/5-2/5-2:1.0/input/input4
-generic-usb 0003:046D:C52B.0003: input: USB HID v1.11 Keyboard [Logitech USB
Receiver] on usb-0000:00:12.0-2/in
+drivers/hid/hid-logitech-dj.c: logi_dj_probe called for ifnum 0
+drivers/hid/hid-logitech-dj.c: logi_dj_probe: ignoring ifnum 0
drivers/hid/usbhid/hid-core.c: HID probe called for ifnum 1
-input: Logitech USB Receiver as
/devices/pci0000:00/0000:00:12.0/usb5/5-2/5-2:1.1/input/input5
-generic-usb 0003:046D:C52B.0004: input: USB HID v1.11 Mouse [Logitech USB
Receiver] on usb-0000:00:12.0-2/input
+drivers/hid/hid-logitech-dj.c: logi_dj_probe called for ifnum 1
+drivers/hid/hid-logitech-dj.c: logi_dj_probe: ignoring ifnum 1
drivers/hid/usbhid/hid-core.c: HID probe called for ifnum 2
+drivers/hid/hid-logitech-dj.c: logi_dj_probe called for ifnum 2
drivers/hid/usbhid/hid-core.c: submitting ctrl urb: Get_Report wValue=0x0110
wIndex=0x0002 wLength=7
drivers/hid/usbhid/hid-core.c: submitting ctrl urb: Get_Report wValue=0x0111
wIndex=0x0002 wLength=20
drivers/hid/usbhid/hid-core.c: submitting ctrl urb: Get_Report wValue=0x0120
wIndex=0x0002 wLength=15
drivers/hid/usbhid/hid-core.c: submitting ctrl urb: Get_Report wValue=0x0121
wIndex=0x0002 wLength=32
-generic-usb 0003:046D:C52B.0005: claimed by neither input, hiddev nor hidraw
-usb 2-5: reset high speed USB device number 2 using ehci_hcd
+logitech-djreceiver 0003:046D:C52B.0005: claimed by neither input, hiddev nor
hidraw
+logitech-djreceiver 0003:046D:C52B.0005: logi_dj_probe:hid_hw_start returned
error:-19
Now where did those devices 0003:046D:C52B.000[34] go with the new kernel?
They seem to be the ones that logi_dj_probe sees as 0 and 1...
The code says:
/* Ignore interfaces 0 and 1, they will not carry any data, dont create
* any hid_device for them */
if (intf->cur_altsetting->desc.bInterfaceNumber !=
LOGITECH_DJ_INTERFACE_NUMBER) {
dbg_hid("%s: ignoring ifnum %d\n", __func__,
intf->cur_altsetting->desc.bInterfaceNumber);
return -ENODEV;
}
Well, that probably explains it. But why does it do that?
lsusb -v says the following about the hardware:
Bus 005 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
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 0xc52b Unifying Receiver
bcdDevice 12.01
iManufacturer 1 Logitech
iProduct 2 USB Receiver
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 84
bNumInterfaces 3
bConfigurationValue 1
iConfiguration 4 RQR12.01_B0019
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 98mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 1 Boot Interface Subclass
bInterfaceProtocol 1 Keyboard
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.11
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 59
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 0x0008 1x 8 bytes
bInterval 8
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
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 148
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0008 1x 8 bytes
bInterval 2
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 2
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 0 No Subclass
bInterfaceProtocol 0 None
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.11
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 98
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0020 1x 32 bytes
bInterval 2
Device Status: 0x0000
(Bus Powered)
Maybe my "unifying" receiver isn't actually working as such a complex
device, and this state needs to be detected somehow?
Please let me know if there's anything I can do to help fix this.
As you may imagine, it's most annoying to have a dead keyboard as
the only keyboard in the house :)
--
2. That which causes joy or happiness.
--- End Message ---
