I had posted a bunch of issues with my system last week but this is the one issue I really want to solve. And thus dedicating a thread to it.
My system’s keyboard is a wired USB. Keyboard works in Bios, Grub. When I land in the GDM, the keyboard is unresponsive for 1-2 minutes. If I enter my password using the onscreen keyboard, it will log me in byt I’ll still have to wait 2 minutes to use the keyboard.
I also noticed than when I lock my PC after a while it becomes frozen or before it is frozen I’ll loose keyboard typing.
Really need help. What sort of journalctl Oman’s should I run?
Can you tell us the brand name and the model of the keyboard?
Also interesting would be if you tested to boot with an older kernel? What is the kernel which makes troubles?
Could you test with an other Keyboard if you have same issues?
Keyboard is nuphy halo65. No issue until last week. I just tried a different brand of keyboard (keychron) and same deal: responsive in bios or grub, but it take 1-2 mins in GDM. And if I login using a screen keyboard the same happens inside fedora42 / gnome 48: have to wait a minute before I can type.
Kernel is CachyOS 6.14.8. I have tried earlier versions - same issue.
If I launch the rescue kernel the keyboard will work to do control-d but the messages seem to point to issues:
So this is interesting. I tried kernel 14.0 and the behavior at the GDM went away (I could type my password as soon as after selecting a user). But because I now have a verbose boot vs. a quiet boot I can see that it hangs at systemd-journald.service; and because it hangs there it takes longer for the GDM to appear. Thus when it appears I can type because it’s been 1-2 mins.
Step-by-step I tried diff kernels. 14.0 behavior was replicable all the way to 14.4. Once I installed 14.5 the systemd.journald.services hangs but has less retries so I get to the GDM faster; but then whatever turns my typing on is not yet ready and I have to wait.
Super weird. How can I resolve the hanging? Looks like usb 1-12: device not accepting address 10, error -71 could be the issue:
LOL - so I did a google search for:
“device not accepting address 10, error -71 could be the issue linux”
and the second link is a guy name Daniel Lange that post the same “bug” in 2023 on his blog.
I then proceeded to turn off the pc, flip the off switch on the PSU, and unplugged the power connection to the wall. Waited a few mins. and now it works, back to normal in all Kernels.
[SOLVED] and thanks Daniel if you ever see this for your blog post!
