Keyboard not working anymore at Disk Decryption Screen!

[nasicus (Patrick)]

Hi guys

I’m on fedora 43. Yesterday I did a `sudo dnf update` (I think it updated the kernel among other things) and this morign the keyboard of my laptop didn’t work anymore on the disk decrypt screen… which isn’t optimal ;D

I already wanted to start panicking, but then after a forced shutdown (via power button) and repowering it back on I selected another version (the second one) in the (boot?) menu and there it worked again.

The one where the keyboard not working (the default one) is highlighted in this photo:

If this isn’t only me it’s probably a quite severe bug?

My model is:

HP HP ZBook Ultra G1a 14 inch Mobile Workstation PC

BTW: I’m a Linux noob, so if yo uneed any other infos just tell me how I can help you!

Edit: [Solved] Fedora 43 unable to boot after upgrading to kernel version 6.17.8 sounds related!

[lizardhat88 (Mitch)]

I have the same issue with the newest kernel 6.17.8. I am using an ASUS Zenbook S 16 UM5606WA.

During boot, before the decryption screen, I get an error RDSEED32 is broken. Disabling the corresponding CPUID bit.

"RDSEED32 is broken. Disabling the corresponding CPUID bit."

Since I installed the Fedora Linux (6. 17.7-300 fc43.x86_64) 43 (Workstation Edition) update on my Framework 13 AMD Ryzen AI 300 Series - Ryzen AI 5 340, upon booting this message comes up “[RDSEED32 is broken. Disabling the corresponding CPUID bit.]” . This wasn’t fixed with the most recent update either (6. 17.8-300 fc43.x86_64) 43 (Workstation Edition). So now when I boot it up, after the message disappers, it comes up with a menu of the different updates, and upon clicking the the most recen…

I am unable to use my keyboard to input my password for decryption. The keyboard backlight is on but no inputs detected.

Possibly related AMD bulletin: RDSEED Failure on AMD “Zen 5” Processors

I did notice that a BIOS update came out for my laptop today from ASUS. I flashed the new BIOS and the issue is not resolved.

It looks like AMD will be pushing a fix out next week and then I’ll have to wait for ASUS to push a BIOS update?

Booting with 6.17.7 doesn’t get the error message and my keyboard works fine for the password prompt.

[djanges (Jan)]

I have the same problem and came to the same conclusion as lizardhat88.

AMD’s official information shows that the RDSEED microcode mitigation for Zen 5 is being released starting November 25, 2025, depending on CPU family.

I just realized, i am already a BIOS Version behind, but the BIOS Version from 2025-10-09 does not have the fix. It seems as if Lenovo only released a BIOS update for Windows, since on the Website i only see a .exe file and the AI that i asked said, i cant install it with Linux and the BIOS itself cant handle the .exe file either. Since i trust you guys more than an AI, is this correct in your view? So do i have to install Windows for the BIOS updates?

[lizardhat88 (Mitch)]

Lenevo IdeaPad and Legion etc only have an .exe from their site. It’s insane and Lenevo is the only one I know that does it.

Thinkpads should have the BIOS files available and be flashed in the BIOS before OS boot.

Use something like Hiren’s BootCD PE to boot into a live windows environment and run the updater.

Side note: if you’re using AI for tech support, I highly suggest using a legit model

[djanges (Jan)]

Thank you very much for the great informations, i will look into Hiren’s BootCD PE.
Before, I always had Thinkpads and thought the whole of Lenovo was good for Linux but that does not seem to be true, especially when it comes to BIOS updates. I guess a dual Boot setup might be an alternative, but i have no time for setting everything up again.

Can you recommend an AI for tech support? I use Mammouth AI so i can use all the major AI’s but for Linux they all sucked so far. First they seem very good and i started working with them super confidently, until i realized they mostly produce a mess and cost more time compared to just doing the proper work.

[jrredho (john r red-horse)]

If you’re referring to the fact that you don’t see any keyboard input progress in the LUKS password prompt form at boot time, this is addressed here: "RDSEED32 is broken. Disabling the corresponding CPUID bit." - #14 by rubenstobbart

tl;dr The input is still getting received, and, after the unlocking happens, all further keyboard input is reflected normally. The fix is reportedly on the way.

[nasicus (Patrick)]

can indeed confirm, that even though you don’t see anything you can still blindly type your passord and press enter. After that be patione for ~30 secs and you’ll see the password screen.