Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

USB rules ran before devices created #291

Open
zlice opened this issue Jan 20, 2025 · 0 comments
Open

USB rules ran before devices created #291

zlice opened this issue Jan 20, 2025 · 0 comments

Comments

@zlice
Copy link

zlice commented Jan 20, 2025

sys info

  • kernel 6.12.9 (since maybe 6.2? i forget when. built with my own config)
  • AMD 9700X (previously 5600X)
  • ASROCK x670E mATX steel legend (previously ASROCK x570 mATX pro4)
  • OS drive Intel optane (previously a different optane and nvme before that)
  • keyboard custom QMK
  • mouse custom QMK/ploopy
  • webcam logitech C920
  • Intel A770 GPU (with USB led controller from the card)
  • void linux

Issue

For a while I have been having issues with udev rules not loading or detecting USB devices at boot. Or being ran before they are created. I'm not really sure which or how to go about debugging.

This shows up as either my keyboard/mouse needing re-plugged at login to even log in. Or my webcam permissions being wrong and still root:root 0600. I have somewhat prevented re-plugging my keyboard/mouse by adding usbcore.quirks=feed:0000:gki at boot. Although there is a delay while waiting for usb to be available. (dmesg shows things are seen before login but they do not work until maybe 10 seconds after staring at the screen)

This is sometimes fixed between kernel updates but has been more frequent as time goes on (as newer kernels come out). Previously moving devices to different USB ports would allow for some magic combo that would run rules and assign permissions (and you know, actually let devices show up) - now that does not work.

Runnning a udev reload will fix things, but I expect them to be fine at boot.

There is another issue where my dmesg shows a 4-5 second stall at boot due to AMD-Vi (some virtualization part of iommu ?), but that seems specific to this motherboard. It could be related, and the udev rules issue could a similar AMD or ASROCK thing but they do not respond.

Appreciate any help or debug guidance. If more info would help, let me know.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant