Hi, I'm looking for some support but was hesitant on opening a bug in github since I'm not 100% sure if it is a systemd issue. So this is what happened:
I update my computer around once a month. Two days ago I updated my computer and after restart it prompted me for my LUKS password as always. However, this time my keyboard was not working. The lights on the keyboard turned on, but no matter how much I typed, nothing happened. My keyboard is a Keychron K8. I plugged in another keyboard, and that one worked, so I typed my LUKS password. After that, it finished booting and Plasma Login Manager appeared and my original keyboard was working again, I could enter my login password and was able to use my keyboard on all programs inside KDE. So, it is only the K8 keyboard that the LUKS prompt didn't recognize, and it is only during the LUKS prompt that the K8 keyboard is not recognized. Some details worth mentioning: 1. My keyboard is connected through USB, not bluetooth. 2. I tried rebooting with Zen, Linux and LTS kernel, with and without fallback and it didn't work. So I don't think it is a module loading issue. At least not a simple one. 3. I am using Dracut and Dracut-ukify to generate UKI images. 4. I posted my issue on reddit, and another person was able to confirm the same happened and they also have a K8 keyboard.5. I see that the Keychron K8 keyboard is recognized initially as an Apple keyboard but then it ends up using usbhid module 6. During LUKS prompt I see the following messages: usb 5-1.1: device not accepting address 3, error -71 usbhid 3-6:4.1.0: couldn't find an input interrupt endpoint 7. The other reddit user mentioned that he reverted to mkinitcpio and generated the UKI (they didn't mention how they were generating the UKI after reverting to mkinitcpio) and after that it started working again. 8. I searched my pacman logs for all the packages I changed during the last update. I didn't see any dracut packages, but I did see systemd-ukify was updated. So based on the above, I am thinking that maybe something changed on how systemd-ukify generates the UKI image when built with dracut that somehow made this specific keyboard to stop working. Thank you for your time. Let me know if this is not the right channel for support or if you need any more details, I'm happy to provide. Thanks, Jurgen.
