AMD Microcode problem on HP OmniBook X Flip (Kraken Point)

[lacusch (Laszlo Mate Szabo)]

Hello everyone.

First time posting here so let me know if I miss something.

---

I got a new laptop this week, the HP OmniBook X Flip 2 with (14 inch with Ryzen 7) with a default Windows install.

I installed Fedora 43 KDE Plasma Desktop on it right away.

It ran without problems for a while (other than virtual keyboard crashes that I didn’t investigate further) untill I updated the system and then I couldn’t login to desktop anymore.

During the boot screen I saw the error

Message from syslogd@fedora at Jan  2 14:24:08 ...
kernel:RDSEED32 is broken. Disabling the corresponding CPUID bit.

I checked the logs and found missing microcode errors
journalctl -b -p err | less

Full log

Jan 02 14:33:10 fedora kernel: microcode: RDSEED32 is broken. Disabling the corresponding CPUID bit.

Jan 02 14:33:10 fedora kernel: microcode: No sha256 digest for patch ID: 0xb6600037 found

Jan 02 14:33:10 fedora kernel: microcode: No sha256 digest for patch ID: 0xb6600037 found

Jan 02 14:33:10 fedora kernel: microcode: CPU2: update failed for patch_level=0xb6600037

Jan 02 14:33:10 fedora kernel: microcode: CPU1: update failed for patch_level=0xb6600037

Jan 02 14:33:10 fedora kernel: microcode: No sha256 digest for patch ID: 0xb6600037 found

Jan 02 14:33:10 fedora kernel: microcode: CPU3: update failed for patch_level=0xb6600037

Jan 02 14:33:10 fedora kernel: microcode: No sha256 digest for patch ID: 0xb6600037 found

Jan 02 14:33:10 fedora kernel: microcode: CPU4: update failed for patch_level=0xb6600037

Jan 02 14:33:10 fedora kernel: microcode: No sha256 digest for patch ID: 0xb6600037 found

Jan 02 14:33:10 fedora kernel: microcode: CPU5: update failed for patch_level=0xb6600037

Jan 02 14:33:10 fedora kernel: microcode: No sha256 digest for patch ID: 0xb6600037 found

Jan 02 14:33:10 fedora kernel: microcode: CPU6: update failed for patch_level=0xb6600037

Jan 02 14:33:10 fedora kernel: microcode: No sha256 digest for patch ID: 0xb6600037 found

Jan 02 14:33:10 fedora kernel: microcode: CPU7: update failed for patch_level=0xb6600037

Jan 02 14:33:10 fedora kernel: microcode: No sha256 digest for patch ID: 0xb6600037 found

Jan 02 14:33:10 fedora kernel: microcode: CPU8: update failed for patch_level=0xb6600037

Jan 02 14:33:10 fedora kernel: microcode: No sha256 digest for patch ID: 0xb6600037 found

Jan 02 14:33:10 fedora kernel: microcode: CPU10: update failed for patch_level=0xb6600037

Jan 02 14:33:10 fedora kernel: microcode: No sha256 digest for patch ID: 0xb6600037 found

Jan 02 14:33:10 fedora kernel: microcode: CPU11: update failed for patch_level=0xb6600037

Jan 02 14:33:10 fedora kernel: microcode: No sha256 digest for patch ID: 0xb6600037 found

Jan 02 14:33:10 fedora kernel: microcode: CPU12: update failed for patch_level=0xb6600037

Jan 02 14:33:10 fedora kernel: microcode: No sha256 digest for patch ID: 0xb6600037 found

Jan 02 14:33:10 fedora kernel: microcode: CPU13: update failed for patch_level=0xb6600037

Jan 02 14:33:10 fedora kernel: microcode: No sha256 digest for patch ID: 0xb6600037 found

Jan 02 14:33:10 fedora kernel: microcode: CPU14: update failed for patch_level=0xb6600037

Jan 02 14:33:10 fedora kernel: microcode: No sha256 digest for patch ID: 0xb6600037 found

Jan 02 14:33:10 fedora kernel: microcode: CPU15: update failed for patch_level=0xb6600037

Jan 02 14:33:15 fedora kernel: platform_profile: Failed to get profile for handler hp-wmi

[END]

After that I reinstalled the machine expecting it to be a one time corruption somehow but it’s reproducible for me after every fresh install.

1. Install the fresh ISO on the Laptop (Fedora-KDE-Desktop-Live-43-1.6.x86_64.iso, verified hash)
2. Run sudo dnf update --refresh
3. Reboot
4. Missing microcode
5. No desktop login possible

I did multiple installs and eventually I managed to log-in graphically after the 3rd reinstall.

Still the microcode problem persists.
sudo dmesg | grep microcode

Full log

[    0.000000] microcode: No sha256 digest for patch ID: 0xb600037 found
[    0.002363] microcode: No sha256 digest for patch ID: 0xb600037 found
[    0.002363] microcode: No sha256 digest for patch ID: 0xb600037 found
[    0.002363] microcode: CPU1: update failed for patch_level=0x0b600037
[    0.002363] microcode: No sha256 digest for patch ID: 0xb600037 found
[    0.002363] microcode: CPU3: update failed for patch_level=0x0b600037
[    0.002363] microcode: CPU2: update failed for patch_level=0x0b600037
[    0.002363] microcode: No sha256 digest for patch ID: 0xb600037 found
[    0.002363] microcode: CPU4: update failed for patch_level=0x0b600037
[    0.002363] microcode: No sha256 digest for patch ID: 0xb600037 found
[    0.002363] microcode: CPU5: update failed for patch_level=0x0b600037
[    0.002363] microcode: No sha256 digest for patch ID: 0xb600037 found
[    0.002363] microcode: CPU6: update failed for patch_level=0x0b600037
[    0.002363] microcode: No sha256 digest for patch ID: 0xb600037 found
[    0.002363] microcode: CPU7: update failed for patch_level=0x0b600037
[    0.002363] microcode: No sha256 digest for patch ID: 0xb600037 found
[    0.002363] microcode: CPU8: update failed for patch_level=0x0b600037
[    0.002363] microcode: No sha256 digest for patch ID: 0xb600037 found
[    0.002363] microcode: CPU9: update failed for patch_level=0x0b600037
[    0.002363] microcode: No sha256 digest for patch ID: 0xb600037 found
[    0.002363] microcode: CPU10: update failed for patch_level=0x0b600037
[    0.002363] microcode: No sha256 digest for patch ID: 0xb600037 found
[    0.002363] microcode: CPU11: update failed for patch_level=0x0b600037
[    0.002363] microcode: No sha256 digest for patch ID: 0xb600037 found
[    0.002363] microcode: CPU12: update failed for patch_level=0x0b600037
[    0.002363] microcode: No sha256 digest for patch ID: 0xb600037 found
[    0.002363] microcode: CPU13: update failed for patch_level=0x0b600037
[    0.002363] microcode: No sha256 digest for patch ID: 0xb600037 found
[    0.002363] microcode: CPU14: update failed for patch_level=0x0b600037
[    0.002363] microcode: No sha256 digest for patch ID: 0xb600037 found
[    0.002363] microcode: CPU15: update failed for patch_level=0x0b600037
[    2.105382] microcode: Current revision: 0x0b60000e

sudo cat /proc/cpuinfo | grep microcode

Full log

microcode       : 0xb60000e
microcode       : 0xb60000e
microcode       : 0xb60000e
microcode       : 0xb60000e
microcode       : 0xb60000e
microcode       : 0xb60000e
microcode       : 0xb60000e
microcode       : 0xb60000e
microcode       : 0xb60000e
microcode       : 0xb60000e
microcode       : 0xb60000e
microcode       : 0xb60000e
microcode       : 0xb60000e
microcode       : 0xb60000e
microcode       : 0xb60000e
microcode       : 0xb60000e

I tried to update the microcode with sudo dnf update amd-ucode-firmware linux-firmware --refresh but it didn’t find anything to update.

According to the logs before and update the last update I tried most graphics firmware
(like amd-gpu-firmware-20251021-1.fc43.noarch and amd-ucode-firmware-20251021-1.fc43.noarch)
got upgraded to the from 20251021 to the 20251125 version

Is there anything know about this already / did somebody else run into this before?
Are there any suggestions on how to troubleshoot it further?

I have around week and a half to return the laptop. I don’t need it right away but I want to have a laptop that works with new Fedora releases.

Thanks for the help

Update: Looking around more on this forum the issue might be related to another post here (Amd microcode vulnerability)

RDSEED32 is broken. Disabling the corresponding CPUID bit. | RDSEED Failure on AMD Processors

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…

[spectre630 (spectre)]

You’re correct that the RDSEED32 message is related to a vulnerability mitigation. The fix is to update your laptop’s UEFI. You’ll need to get that from your vendor, in your case HP. However, they may not have released a patched version yet. For example, my Lenovo is not expected to receive a patch until February.

Updating will depend on whether HP publishes UEFI updates for your model on Linux Vendor Firmware Service (LVFS). If they do, then your process should be fairly simple. You can use fwupdmgr to update the UEFI. If you’re unlucky (like me) and your vendor does not publish for your model, then you’ll have to look at other options. For example, my Lenovo I had to get the Windows version of the UEFI updater, extract the file, and then run fwupdmgr on that file to get it to update. Your steps will vary depending on how HP does updates.

[lacusch (Laszlo Mate Szabo)]

Thanks for the help.

I don’t want to risk waiting for HP to fix it at some indeterminate time in the future.

Luckily I’m still in the return Window so just get another laptop instead

[spectre630 (spectre)]

FYI, all Zen 5 CPUs are impacted. (RDSEED Failure on AMD “Zen 5” Processors)

That said, the RDSEED32 message isn’t [likely] what is preventing your desktop. I apologize that I didn’t catch that in your original post. I focused on the RDSEED32 aspect and missed that you can’t get to desktop. I suspect that the RDSEED32 error is a red herring and not the real problem. My Zen5 laptop also gets that error, but works perfectly fine. The message is simply telling you that they’ve blocked that instruction as mitigation until patched.