Bug 575260 – sys-fs/udev: update breaks logitech bluetooth keyboard & mouse in X

• Status: RESOLVED WONTFIX
• Product: Gentoo Linux

[Description Stephen 2016-02-20 23:49:35 UTC]

You can read all about this in bug 489858, except I'm not using an overlay.  Or you can read about it -->  https://forums.gentoo.org/viewtopic-t-916064-highlight-.html.

So I will not go into too much detail here.

Every time I update sys-fs/udev my Logitech MX 5500 keyboard and mouse stop working in X.

To fix this I must edit the file:  97-hid2hci.rules

and change this line: 

# Logitech devices 
 KERNEL=="hiddev*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c70[345abce]|c71[34bc]", \ 
   RUN+="hid2hci --method=logitech-hid --devpath=%p"



to this: 

# Logitech devices 
 KERNEL=="hidraw*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c70[345abce]|c71[34bc]", \ 
   RUN+="hid2hci --method=logitech-hid --devpath=%p"



Just change hiddev* for hidraw*

This happens always and the fix works always.

[Comment 1 Rafał Mużyło 2016-02-21 13:02:37 UTC]

That thread looks somewhat outdated.

Mind attaching both 'udevadm info' and 'udevadm info -a' of the relevant nodes ?

[Comment 2 Stephen 2016-02-22 01:04:46 UTC]

# udevadm info --name=/dev/input/by-id/usb-Logitech_Logitech_BT_Mini-Receiver_001F2011CA8C-mouse
P: /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.6/2-1.6.3/2-1.6.3:1.0/0003:046D:C71C.0002/input/input19/mouse0                       
N: input/mouse0                                                                                                                       
S: input/by-id/usb-Logitech_Logitech_BT_Mini-Receiver_001F2011CA8C-mouse                                                              
S: input/by-path/pci-0000:00:1d.0-usb-0:1.6.3:1.0-mouse                                                                               
E: DEVLINKS=/dev/input/by-id/usb-Logitech_Logitech_BT_Mini-Receiver_001F2011CA8C-mouse /dev/input/by-path/pci-0000:00:1d.0-usb-0:1.6.3:1.0-mouse
E: DEVNAME=/dev/input/mouse0
E: DEVPATH=/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.6/2-1.6.3/2-1.6.3:1.0/0003:046D:C71C.0002/input/input19/mouse0
E: ID_BUS=usb
E: ID_INPUT=1
E: ID_INPUT_KEY=1
E: ID_INPUT_MOUSE=1
E: ID_MODEL=Logitech_BT_Mini-Receiver
E: ID_MODEL_ENC=Logitech\x20BT\x20Mini-Receiver
E: ID_MODEL_ID=c71c
E: ID_PATH=pci-0000:00:1d.0-usb-0:1.6.3:1.0
E: ID_PATH_TAG=pci-0000_00_1d_0-usb-0_1_6_3_1_0
E: ID_REVISION=0101
E: ID_SERIAL=Logitech_Logitech_BT_Mini-Receiver_000000000000
E: ID_SERIAL_SHORT=000000000000
E: ID_TYPE=hid
E: ID_USB_DRIVER=usbhid
E: ID_USB_INTERFACES=:030102:
E: ID_USB_INTERFACE_NUM=00
E: ID_VENDOR=Logitech
E: ID_VENDOR_ENC=Logitech
E: ID_VENDOR_ID=046d
E: MAJOR=13
E: MINOR=32
E: SUBSYSTEM=input
E: USEC_INITIALIZED=2673993

[Comment 3 Stephen 2016-02-22 01:05:29 UTC]

# udevadm info --name=/dev/input/by-id/usb-Logitech_Logitech_BT_Mini-Receiver_001F2011CA8C-event-mouse
P: /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.6/2-1.6.3/2-1.6.3:1.0/0003:046D:C71C.0002/input/input19/event16
N: input/event16
S: input/by-id/usb-Logitech_Logitech_BT_Mini-Receiver_001F2011CA8C-event-mouse
S: input/by-path/pci-0000:00:1d.0-usb-0:1.6.3:1.0-event-mouse
E: DEVLINKS=/dev/input/by-path/pci-0000:00:1d.0-usb-0:1.6.3:1.0-event-mouse /dev/input/by-id/usb-Logitech_Logitech_BT_Mini-Receiver_001F2011CA8C-event-mouse
E: DEVNAME=/dev/input/event16
E: DEVPATH=/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.6/2-1.6.3/2-1.6.3:1.0/0003:046D:C71C.0002/input/input19/event16
E: ID_BUS=usb
E: ID_INPUT=1
E: ID_INPUT_KEY=1
E: ID_INPUT_MOUSE=1
E: ID_MODEL=Logitech_BT_Mini-Receiver
E: ID_MODEL_ENC=Logitech\x20BT\x20Mini-Receiver
E: ID_MODEL_ID=c71c
E: ID_PATH=pci-0000:00:1d.0-usb-0:1.6.3:1.0
E: ID_PATH_TAG=pci-0000_00_1d_0-usb-0_1_6_3_1_0
E: ID_REVISION=0101
E: ID_SERIAL=Logitech_Logitech_BT_Mini-Receiver_000000000000
E: ID_SERIAL_SHORT=000000000000
E: ID_TYPE=hid
E: ID_USB_DRIVER=usbhid
E: ID_USB_INTERFACES=:030102:
E: ID_USB_INTERFACE_NUM=00
E: ID_VENDOR=Logitech
E: ID_VENDOR_ENC=Logitech
E: ID_VENDOR_ID=046d
E: MAJOR=13
E: MINOR=80
E: SUBSYSTEM=input
E: USEC_INITIALIZED=2953820

[Comment 4 Stephen 2016-02-22 01:11:16 UTC]

Created attachment 426162 [details]
udevadm info -a --name=usb-Logitech_Logitech_BT_Mini-Receiver-mouse

[Comment 5 Stephen 2016-02-22 01:14:30 UTC]

Created attachment 426164 [details]
udevadm info -a --name=usb-Logitech_Logitech_BT_Mini-Receiver-event-mouse

[Comment 6 Rafał Mużyło 2016-02-22 04:08:51 UTC]

...in this case, those aren't the relevant nodes; as those rules say, the relevant are hidraw/hiddev for that device.

[Comment 7 Stephen 2016-02-22 09:45:51 UTC]

(In reply to Rafał Mużyło from comment #6)
> ...in this case, those aren't the relevant nodes; as those rules say, the
> relevant are hidraw/hiddev for that device.

That may be the result of my having edited the 97-hid2hci.rules file with the hidraw* parameter?

Additionally, my computer worked for months after my initial install of Gentoo, presumably working with the hiddev* parameter.  Mouse and Keyboard worked seamlessly.

With the above in mind can you suggest an effective means to identify the correct nodes?  As these describe, manufacture, model, transport mechanism and serial number of the affected component.


As a slight aside, another symptom is that the mouse middle button click event gets lost eventually until I re-boot into Windows and run the Logitech config suite.  I don't think this related but its probably more meaningful for you to rule out than me.

[Comment 8 Rafał Mużyło 2016-02-22 11:41:21 UTC]

I'd go with something like 'find /dev/ -type f -name '*hidraw*'' then pass those names to 'udevadm info' (it accepts /dev paths).

Either due to a kernel config change hiddev for that mouse isn't present or is somehow incorrectly detected by the kernel - checking the udev data might show which of those fits better.

[Comment 9 Stephen 2016-02-23 00:00:46 UTC]

Created attachment 426272 [details]
udevadm info  *hidraw* usb-Logitech_Logitech_BT_Mini-Receiver-event-mouse

[Comment 10 Stephen 2017-01-20 00:18:53 UTC]

This is still going on and giving this a nudge.

[Comment 11 Mike Gilbert 2017-01-20 03:14:46 UTC]

I suggest you seek help upstream.

[Comment 12 Stephen 2017-01-20 08:40:03 UTC]

Hi Mike.

Thank you for your help.