Hello Everyone,
I am experiencing frequent input freezes and disconnections with my Logitech MK235 wireless combo (M170 mouse and K235 keyboard) sharing a single nano receiver on Fedora.
The Problem
-
Cold Boot Failure: The device consistently fails to initialize during a fresh cold boot. It is completely unresponsive at the Linux display manager/login screen.
-
Persistent Across Reboots: Soft-rebooting the machine (even over SSH) does not resolve the issue; the device remains dead.
-
Random Re-plugging Success: Physically unplugging and replugging the receiver multiple times eventually works, but it is completely random when Linux finally decides to initialize it properly.
My dmesg logs show that the hid-logitech-dj driver crashes in an aggressive loop with an invalid index error before it finally, randomly succeeds on a later USB bus assignment.
Kernel Version: 7.0.12-201.fc44.x86_64
Fedora Edition: Fedora 43, 44 Workstation (I have started having this issue few months before the release of Fedora 44 and using Fedora 43)
Relevant dmesg Log Snippet:
[ 1556.308168] usb 3-1: USB disconnect, device number 34
[ 1557.060071] usb 3-1: new full-speed USB device number 35 using xhci_hcd
[ 1557.186988] usb 3-1: New USB device found, idVendor=046d, idProduct=c534, bcdDevice=29.01
[ 1557.187001] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 1557.187005] usb 3-1: Product: USB Receiver
[ 1557.187008] usb 3-1: Manufacturer: Logitech
[ 1557.191670] logitech-djreceiver 0003:046D:C534.0139: hidraw0: USB HID v1.11 Keyboard [Logitech USB Receiver] on usb-0000:00:14.0-1/input0
[ 1557.247537] logitech-djreceiver 0003:046D:C534.013A: hiddev96,hidraw1: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-0000:00:14.0-1/input1
[ 1557.299973] logitech-djreceiver 0003:046D:C534.013A: logi_dj_hidpp_event: invalid device index:0
[ 1557.777309] usb 3-1: USB disconnect, device number 35
[ 1558.541350] usb 3-1: new full-speed USB device number 36 using xhci_hcd
[ 1558.669724] usb 3-1: New USB device found, idVendor=046d, idProduct=c534, bcdDevice=29.01
[ 1558.669749] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 1558.669753] usb 3-1: Product: USB Receiver
[ 1558.669756] usb 3-1: Manufacturer: Logitech
[ 1558.674980] logitech-djreceiver 0003:046D:C534.013B: hidraw0: USB HID v1.11 Keyboard [Logitech USB Receiver] on usb-0000:00:14.0-1/input0
[ 1558.731161] logitech-djreceiver 0003:046D:C534.013C: hiddev96,hidraw1: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-0000:00:14.0-1/input1
[ 1558.783756] logitech-djreceiver 0003:046D:C534.013C: logi_dj_hidpp_event: invalid device index:0
[ 1559.552267] usb 3-1: USB disconnect, device number 36
[ 1560.695291] usb 3-1: new full-speed USB device number 37 using xhci_hcd
[ 1560.822489] usb 3-1: New USB device found, idVendor=046d, idProduct=c534, bcdDevice=29.01
[ 1560.822496] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 1560.822498] usb 3-1: Product: USB Receiver
[ 1560.822499] usb 3-1: Manufacturer: Logitech
[ 1560.825683] logitech-djreceiver 0003:046D:C534.013D: hidraw0: USB HID v1.11 Keyboard [Logitech USB Receiver] on usb-0000:00:14.0-1/input0
[ 1560.879010] logitech-djreceiver 0003:046D:C534.013E: hiddev96,hidraw1: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-0000:00:14.0-1/input1
[ 1560.930130] logitech-djreceiver 0003:046D:C534.013E: logi_dj_hidpp_event: invalid device index:0
[ 1562.066283] logitech-djreceiver 0003:046D:C534.013E: logi_dj_hidpp_event: invalid device index:0
[ 1562.658263] logitech-djreceiver 0003:046D:C534.013E: logi_dj_hidpp_event: invalid device index:0
[ 1564.034286] logitech-djreceiver 0003:046D:C534.013E: logi_dj_hidpp_event: invalid device index:0
[ 1564.706314] logitech-djreceiver 0003:046D:C534.013E: logi_dj_hidpp_event: invalid device index:0
[ 1565.290283] logitech-djreceiver 0003:046D:C534.013E: logi_dj_hidpp_event: invalid device index:0
[ 1735.892516] igc 0000:64:00.0 enp100s0: NIC Link is Down
[ 2708.659425] usb 3-1: USB disconnect, device number 37
[ 2710.207145] usb 3-1: new full-speed USB device number 38 using xhci_hcd
[ 2710.333114] usb 3-1: New USB device found, idVendor=046d, idProduct=c534, bcdDevice=29.01
[ 2710.333120] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 2710.333121] usb 3-1: Product: USB Receiver
[ 2710.333123] usb 3-1: Manufacturer: Logitech
[ 2710.336837] logitech-djreceiver 0003:046D:C534.013F: hidraw0: USB HID v1.11 Keyboard [Logitech USB Receiver] on usb-0000:00:14.0-1/input0
[ 2710.390633] logitech-djreceiver 0003:046D:C534.0140: hiddev96,hidraw1: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-0000:00:14.0-1/input1
[ 2710.442138] logitech-djreceiver 0003:046D:C534.0140: device of type eQUAD nano Lite (0x0a) connected on slot 1
[ 2710.444138] logitech-djreceiver 0003:046D:C534.0140: device of type eQUAD nano Lite (0x0a) connected on slot 2
[ 2710.450360] input: Logitech Wireless Keyboard PID:4023 as /devices/pci0000:00/0000:00:14.0/usb3/3-1/3-1:1.1/0003:046D:C534.0140/0003:046D:4023.0141/input/input94
[ 2710.496460] logitech-hidpp-device 0003:046D:4023.0141: input,hidraw2: USB HID v1.11 Keyboard [Logitech Wireless Keyboard PID:4023] on usb-0000:00:14.0-1/input1:1
[ 2716.330246] logitech-djreceiver 0003:046D:C534.0140: device of type eQUAD nano Lite (0x0a) connected on slot 2
[ 2716.840281] logitech-hidpp-device 0003:046D:4023.0141: HID++ 2.0 device connected.
[ 2723.506649] input: Logitech Wireless Mouse as /devices/pci0000:00/0000:00:14.0/usb3/3-1/3-1:1.1/0003:046D:C534.0140/0003:046D:4054.0142/input/input95
[ 2723.507667] logitech-hidpp-device 0003:046D:4054.0142: input,hidraw3: USB HID v1.11 Mouse [Logitech Wireless Mouse] on usb-0000:00:14.0-1/input1:2
[ 2723.524224] logitech-hidpp-device 0003:046D:4054.0142: HID++ 4.5 device connected.
What I have observed:
-
The driver fails on cold boots because it enters a crash loop throwing
logi_dj_hidpp_event: invalid device index:0. -
As seen in the logs, after multiple dropouts and re-insertions, the driver randomly parses the slots sequentially, assigning the Keyboard (PID:4023) to Slot 1 and Mouse (PID:4054) to Slot 2. Once this random success happens, the devices work.
Has anyone dealt with this firmware/driver race condition during initialization on Fedora? Is there a known kernel parameter or custom udev rule that forces a proper probe on boot?