After update to Fedora 43 Logitech MX Master 3 stop working until Solaar start

Ask Fedora
, , ,
1

TL;DR:

USB hub port assignment issue.
YubiKey on hub port 1 caused enumeration timeouts at boot and at usbbus rescan. That cause 86 second more time to boot and also to connect logitech mouse.
Solution: Swapped YubiKey and Bolt receiver positions on the hub - problem solved. Also work put it to different hub.

Hardware:

  • Logitech MX Master 3S connected via Logitech Bolt Receiver (046d:c548)
  • YubiKey security key (5.4.3)
  • USB 2.0 Hub on motherboard with 2 ports (Genesys Logic 05e3:0610)

The Problem

After updating to Fedora 43, I experienced several interconnected issues:

  • Mouse completely non-functional at boot - couldn’t use it until after login when Solaar service loaded
  • 86-second boot delay with systemd-udevd timeout errors
  • Bluetooth service failing to start due to missing /sys/class/bluetooth directory
  • USB descriptor read errors during boot

Boot Error Logs

During boot, I saw systemd-udevd being killed by timeout with repeated USB errors:

Nov 04 18:29:13 fedora-host kernel: usb 1-10: unable to read config index 0 descriptor/start: -110
Nov 04 18:29:13 fedora-host kernel: usb 1-10: can't read configurations, error -110
Nov 04 18:29:22 fedora-host kernel: usb 1-7.1: device descriptor read/64, error -110
Nov 04 18:29:37 fedora-host kernel: usb 1-7.1: device descriptor read/64, error -110
Nov 04 18:29:38 fedora-host kernel: usb 1-7.1: new full-speed USB device number 7 using xhci_hcd
Nov 04 18:29:53 fedora-host systemd[1]: systemd-udevd.service: State 'stop-sigterm' timed out. Killing.
Nov 04 18:29:53 fedora-host systemd[1]: systemd-udevd.service: Killing process 477 (systemd-udevd) with signal SIGKILL.
Nov 04 18:29:53 fedora-host systemd[1]: systemd-udevd.service: Main process exited, code=killed, status=9/KILL
Nov 04 18:29:53 fedora-host systemd[1]: systemd-udevd.service: Failed with result 'timeout'.

The errors continued for about 86 seconds before the system finally gave up and continued booting. (I found out it when loaded from F42 kernel)

Initial Troubleshooting Attempts

Attempt 1: Dracut Bluetooth Module

I initially thought this was related to the kernel 6.12 bluetooth issues, so I added to /etc/dracut.conf.d/bluetooth.conf:

add_dracutmodules+=" bluetooth "
show_modules=yes

Rebuilt initrd and rebooted - no change.

Attempt 2: Analyzing Solaar’s Role

I noticed the mouse worked after Solaar loaded, but testing revealed:

  • Once the mouse was working, I could stop Solaar and everything continued working
  • Solaar wasn’t the solution - it was just triggering something during startup

The Diagnostic Breakthrough

After I tried to boot on my working Fedora 42 system (kernel 6.14.0-63.fc42), I found the same 86-second USB enumeration delay in dmesg logs! The difference was that F42 somehow handled it more gracefully.

I almost never turn off my PC, so I haven’t noticed any long loading times.

The logs showed the same:

  • Port 1-7.1 repeatedly failing with timeout errors (-110) and protocol errors (-71)
  • Port 1-7.2 eventually succeeding where the Bolt receiver finally appeared
  • 86 seconds of failed enumeration attempts on port 1-7.1

USB Topology

Bus 001.Port 007: Dev 004, If 0, Class=Hub, Driver=hub/4p, 480M
    |__ Port 001: Dev XXX (YubiKey - was here)
    |__ Port 002: Dev 031 (Bolt Receiver - was here)

All like F43, but systemd-oomd has bigger timeout - 1m30s.

Stupid hardware test

I physically disconnected all devices from my USB hub and reconnected only the Bolt receiver - everything worked perfectly, no timeouts!

Then I added back the YubiKey - 86-second boot delay returned!

Root Cause

The problem was not the Bolt receiver at all. It was:

  1. YubiKey on USB hub port 1 (1-7.1) was failing to respond during cold boot enumeration
  2. System spent 86 seconds trying to enumerate the non-responsive YubiKey
  3. systemd-udevd timed out waiting for USB enumeration to complete
  4. Eventually the system gave up and moved to port 2 where the Bolt receiver worked fine
  5. After login, when Solaar service started, it triggered a USB re-scan

The Solution

I simply swapped the physical positions of the YubiKey and Bolt receiver on the USB hub:

  • Bolt Receiver → Hub Port 1 (1-7.1)
  • YubiKey → Hub Port 2 (1-7.2)

Result: Boot time back to normal, mouse works immediately, no more errors!

Why I notice error only on F43

The issue exists on both versions (as seen in dmesg), but Fedora 43 handles it different because of stricter enumeration timing, less tolerance for slow devices.

F42 has 1m30s second timeout vs F43 seems to change it to 45s.

Fedora 42 probably completed the rest of the boot process while USB enumeration was still failing, making the delay less noticeable.

1 Like