Bug 1110523

Summary: Logitech Unified Receiver support broken, mouse won't work
Product: Red Hat Enterprise Linux 7 Reporter: Forrest Taylor <ftaylor>
Component: kernelAssignee: Benjamin Tissoires <btissoir>
kernel sub component: Desktop Other QA Contact: Desktop QE <desktop-qa-list>
Status: CLOSED ERRATA Docs Contact:
Severity: medium    
Priority: unspecified CC: ahinek, asanders, ayadav, bbenson, chenders, mboisver, peter.hutterer, rhaggard, rick, smooge, tdawson, tpelka, vbenes
Version: 7.0   
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: kernel-3.10.0-148.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-05 12:23:55 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1154209    
Attachments:
Description Flags
Code to reset Logitech unifying receiver
none
udev rule to execute logitech-fix.sh
none
Updated udev script none

Description Forrest Taylor 2014-06-17 20:28:52 UTC
Description of problem:
Using a Logitech Unified Receiver with a wireless device will not work on RHEL7.

This issue can be found here:
https://bugzilla.kernel.org/show_bug.cgi?id=60507

A workaround can be found in comment 6:
https://bugzilla.kernel.org/show_bug.cgi?id=60507#c6

I tried to reload the hid-logitech-dj driver, but that didn't help.  Sending the code to the /dev/hidraw? device as in the comment worked for me.

kernel-3.10.0-123.el7.x86_64

Comment 2 Stephen John Smoogen 2014-07-19 18:00:10 UTC
I can confirm that this happens with certain hardware combinations and is due to a bug in the kernel that was in the 3.10.0 base kernel but later fixed in a later patch set.

The problem seems to be with having a logitech receiver plugged into a non USB 2.0 plug. If it is plugged into a USB 1, 1.5, 3.0 or a 2.0/3.0 switched (like on an Lenovo Thinkpad T540p) the kernel will see the device (it shows up in lsusb, dmesg reports it there etc) but it will not take input from the device. 

Change the port to a USB 2.0 and it works. Run a mainline kernel and it works. Problem looks to be:

https://bugzilla.kernel.org/show_bug.cgi?id=60507

Comment 4 Benjamin Tissoires 2014-07-29 21:25:46 UTC
I just confirmed that 42c22dbf81ebd1146960875ddfe71630cb2b3ae6 in Linus tree fixed the bug in RHEL 7.

The problem occurs on a Lenovo t540p (I guess the t440s should be also affected) and can be easily reproduce on this platform:

- without the fix:
* plug a Logitech Receiver connected to a mouse/touchpad
* dmesg shows:
[   78.854552] usb 3-1: new full-speed USB device number 6 using xhci_hcd
[   78.868041] usb 3-1: New USB device found, idVendor=046d, idProduct=c52b
[   78.868044] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[   78.868046] usb 3-1: Product: USB Receiver
[   78.868047] usb 3-1: Manufacturer: Logitech
[   78.980266] logitech-djreceiver 0003:046D:C52B.0003: hiddev0,hidraw0: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:14.0-1/input2

and the mouse is not responsive

- with the fix:
* plug a Logitech Receiver connected to a mouse/touchpad
* dmesg shows:
[   78.854552] usb 3-1: new full-speed USB device number 6 using xhci_hcd
[   78.868041] usb 3-1: New USB device found, idVendor=046d, idProduct=c52b
[   78.868044] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[   78.868046] usb 3-1: Product: USB Receiver
[   78.868047] usb 3-1: Manufacturer: Logitech
[   78.980266] logitech-djreceiver 0003:046D:C52B.0003: hiddev0,hidraw0: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:14.0-1/input2
[   79.031855] input: Logitech Unifying Device. Wireless PID:400a as /devices/pci0000:00/0000:00:14.0/usb3/3-1/3-1:1.2/0003:046D:C52B.0003/input/input14
[   79.032180] logitech-djdevice 0003:046D:C52B.0004: input,hidraw1: USB HID v1.11 Mouse [Logitech Unifying Device. Wireless PID:400a] on usb-0000:00:14.0-1:1

and the mouse is just working.

Comment 6 Forrest Taylor 2014-08-05 14:54:50 UTC
Created attachment 924232 [details]
Code to reset Logitech unifying receiver

Comment 7 Forrest Taylor 2014-08-05 14:55:34 UTC
Created attachment 924233 [details]
udev rule to execute logitech-fix.sh

Comment 8 Forrest Taylor 2014-08-05 14:57:22 UTC
Workaround:

Copy (attached) logitech-fix.sh file to /usr/local/bin/
Copy (attached) 99-logitech.rules to /etc/udev/rules.d/

Ensure 99-logitech.rules has the proper ID (look at the output of lsusb).  Now when the device is attached, the udev rule will kick off the workaround script.

Comment 12 Jarod Wilson 2014-09-02 15:19:51 UTC
Patch(es) available on kernel-3.10.0-148.el7

Comment 14 Forrest Taylor 2014-09-10 12:34:10 UTC
Created attachment 936126 [details]
Updated udev script

Added an ACTION that was missing from the original udev rules script.

Comment 15 Forrest Taylor 2014-09-10 12:36:35 UTC
Note, the logitech-mouse.sh script uses sudo, so remove that if root is not allowed to use sudo.

Comment 18 Bruce O. Benson 2014-10-07 15:51:27 UTC
Seems like it starts working only if I plug another mouse into one of the USB 2-capable ports first (like maybe to push it into USB 2 mode?).

Holler if any in-situ testing is needed...and for any testing related to ThinkPad W540+RHEL7....especially for the awful touchpad it has.

Comment 23 Michael Boisvert 2015-01-23 20:03:40 UTC
Tested on a Lenovo x230t USB3.0 port with kernel-3.10.0-222.el7 installed and a Logitech Touchpad. The Unified Receiver is working as it should, and I am able to use the touchpad correctly.

Verified.

Comment 25 errata-xmlrpc 2015-03-05 12:23:55 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2015-0290.html

Comment 26 Peter Hutterer 2015-04-08 23:39:58 UTC
*** Bug 1190768 has been marked as a duplicate of this bug. ***

Comment 28 Benjamin Tissoires 2015-04-30 21:26:34 UTC
*** Bug 1185389 has been marked as a duplicate of this bug. ***

Comment 29 Don Zickus 2015-07-16 20:45:01 UTC
*** Bug 1203455 has been marked as a duplicate of this bug. ***