Bug 44811 - Logitech wireless keyboard/mouse does not work
Summary: Logitech wireless keyboard/mouse does not work
Status: RESOLVED OBSOLETE
Alias: None
Product: Drivers
Classification: Unclassified
Component: USB (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: Sarah Sharp
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-14 23:40 UTC by Laurent
Modified: 2013-11-20 00:00 UTC (History)
3 users (show)

See Also:
Kernel Version: 3.4
Subsystem:
Regression: No
Bisected commit-id:


Attachments

Description Laurent 2012-07-14 23:40:21 UTC
I have a Logitech wireless combo mk520 that do not work on my new machine (amd64). It works with the BIOS and Grub on that machine so the hardware looks fine, and it also works on a laptop (i686 based) with a 3.2 kernel which does not work either on the amd64 arch based machine.

I also tried the debian kernels which have a patch applied hid-logitech-dj.c (http://lists.debian.org/debian-kernel/2012/05/msg00277.html) with no success.
2.6 kernels seem to be OK.

Here are some logs when I "modprobe hid-logitech-dj":

[14902.392755] drivers/hid/hid-logitech-dj.c: Logitech-DJ:logi_dj_init
[14902.392767] drivers/hid/hid-logitech-dj.c: logi_dj_probe called for ifnum 0
[14902.392768] drivers/hid/hid-logitech-dj.c: logi_dj_probe: ignoring ifnum 0
[14902.392774] drivers/hid/hid-logitech-dj.c: logi_dj_probe called for ifnum 1
[14902.392776] drivers/hid/hid-logitech-dj.c: logi_dj_probe: ignoring ifnum 1
[14902.392780] drivers/hid/hid-logitech-dj.c: logi_dj_probe called for ifnum 2
[14902.392788] drivers/hid/usbhid/hid-core.c: submitting ctrl urb: Get_Report wValue=0x0110 wIndex=0x0002 wLength=7
[14902.392943] drivers/hid/usbhid/hid-core.c: submitting ctrl urb: Get_Report wValue=0x0111 wIndex=0x0002 wLength=20
[14902.393228] drivers/hid/usbhid/hid-core.c: submitting ctrl urb: Get_Report wValue=0x0120 wIndex=0x0002 wLength=15
[14902.393352] drivers/hid/usbhid/hid-core.c: submitting ctrl urb: Get_Report wValue=0x0121 wIndex=0x0002 wLength=32
[14902.393727] logitech-djreceiver 0003:046D:C52B.0012: hiddev0,hidraw3: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:14.0-4/input2
[14902.394007] logitech-djreceiver 0003:046D:C52B.0012: logi_dj_probe:logi_dj_recv_query_paired_devices error:-32
[14902.394612] logitech-djreceiver: probe of 0003:046D:C52B.0012 failed with error -32
Comment 1 Alan 2012-07-20 12:36:27 UTC
Firstly try sticking it in a different port - especially if you've got USB3 ports and it's currently in a USB3 port and then report if that helps
Comment 2 Laurent 2012-07-20 13:36:37 UTC
Nice move ! I had tried only USB2 and USB3 ports on the front of my box, but I've just tried USB2 on the back (connector directly attached to the motherboard), and it works. But the USB3 connector of the motherboard does not work any better.

Here are the logs in the working configuration :

[61669.031848] usb 6-1.6.3: new full-speed USB device number 9 using ehci_hcd
[61669.142896] usb 6-1.6.3: New USB device found, idVendor=046d, idProduct=c52b
[61669.142901] usb 6-1.6.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[61669.142904] usb 6-1.6.3: Product: USB Receiver
[61669.142906] usb 6-1.6.3: Manufacturer: Logitech
[61669.146330] logitech-djreceiver 0003:046D:C52B.0022: hiddev0,hidraw1: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:1d.0-1.6.3/input2
[61669.148366] input: Logitech Unifying Device. Wireless PID:1024 as /devices/pci0000:00/0000:00:1d.0/usb6/6-1/6-1.6/6-1.6.3/6-1.6.3:1.2/0003:046D:C52B.0022/input/input16
[61669.148520] logitech-djdevice 0003:046D:C52B.0023: input,hidraw3: USB HID v1.11 Mouse [Logitech Unifying Device. Wireless PID:1024] on usb-0000:00:1d.0-1.6.3:1
[61669.150680] input: Logitech Unifying Device. Wireless PID:2011 as /devices/pci0000:00/0000:00:1d.0/usb6/6-1/6-1.6/6-1.6.3/6-1.6.3:1.2/0003:046D:C52B.0022/input/input17
[61669.150733] logitech-djdevice 0003:046D:C52B.0024: input,hidraw4: USB HID v1.11 Keyboard [Logitech Unifying Device. Wireless PID:2011] on usb-0000:00:1d.0-1.6.3:2

Thanks !
Comment 3 Roger Davis 2012-08-08 00:53:10 UTC
It seems that there may be a lack of communication.  There are LOTS of these cases.  

Please see   http://ubuntuforums.org/search.php?searchid=87273303
Comment 4 Greg Kroah-Hartman 2012-08-08 03:15:42 UTC
Please post this information on the linux-usb@vger.kernel.org mailing list, we don't handle USB bugs using bugzilla.kernel.org, sorry.
Comment 5 Alan 2012-08-08 09:03:47 UTC
Re-opening. Greg - please don't close bugs that other people are using to track issues.

Yes the info should go to linux-usb but the bug hasn't yet been fixed

Note You need to log in before you can comment on or make changes to this bug.