You are not logged in.
After a recent update my keyboard is unresponsive, when trying to type Luks passphrase. Same thing with snapshots.
Offline
laptop? some fancy multi-function gaming keyboard? counter-checked with $10 k120?
Offline
Regenerating initramfs fixed the problem
Offline
I've been experiencing this issue as well, specifically with my 'hfd.cn Thock 75% Wireless Keyboard'.
Regenerating initramfs using "dracut --regenerate-all --force" did not solve my case.
I updated my kernel to 7.1.5-arch1-2, and that specific keyboard stopped working during the Luks passphrase prompt. It works during the BIOS, dual-boot selection screen, and in the OS after booting.
I didn't have another wired USB keyboard to test with, but I did have a wireless one, which worked without issue.
I also tested my Lenovo laptop by updating to the same kernel, and yielded similar results. Its integrated keyboard was functional, whereas the 'hfd.cn' one was not.
Edit:
I switched to linux-lts kernel 6.18 and the issue persists. I didn't do this by downgrading, but by running "sudo pacman -S linux-lts".
Maybe rolling back fully to a previous date would've worked, but at this point I'll just keep an extra keyboard on hand.
On both kernels, after about 19 seconds, I get the message: "usb 3-2: unable to read config index 0 descriptor/start: -71"
Last edited by arch-foxx (2026-07-31 12:00:04)
Offline
I'm hitting the exact same issue, and unfortunately I don't have a spare WiFi keyboard to use. Has anyone found the root cause or a working solution?
Edit: tried downgrade kernel (linux-hardened) and headers to the previous working version, issue persist.
Last edited by canc (2026-07-31 14:44:13)
Offline
Has anyone found the root cause or a working solution?
it's usually the controller not providing a clean simple hid keyboard due to some fancy stufflike macro keys or rgb
a "proper" solution would be for whoever messed up the firmware to fix it - but such kind of hardware is usually meant for and test only with windows
thier oem just don't antucipate someone might want to use it for something lowlevel as a luks phrase
Offline
canc wrote:Has anyone found the root cause or a working solution?
it's usually the controller not providing a clean simple hid keyboard due to some fancy stufflike macro keys or rgb
a "proper" solution would be for whoever messed up the firmware to fix it - but such kind of hardware is usually meant for and test only with windows
thier oem just don't antucipate someone might want to use it for something lowlevel as a luks phrase
That could be true for my main keyboard (nuphy) but i've tested also a mac keyboard (always used it as a backup) with same results.
As both has worked for years with arch, can this be related with some recent firmware pkg updates? Any suggestion about what I can try to downgrade?
Offline
Any suggestion about what I can try to downgrade?
No idea how you'd figure out specifically what would need to be downgraded, besides downgrading to a specific date, and I haven't figured out how to do that.
Offline
Adding another data point as I am also experiencing this issue for the past few days since an update. Keyboard (a Keychron K10 over USB) works fine in UEFI, archinstall USB, and the systemd-boot menu but does nothing in the LUKS prompt (or the bail out menu after LUKS times out for this matter.) This seems to be a recent breakage. Regenerating initramfs with --no-hostonly doesn't help, neither does using the fallback image without quiet splash.
Last edited by RamenFiend (2026-08-01 17:16:05)
Offline
After updating the system, it seems the issue's been resolved, at least for my keyboard model.
Offline