omarchy icon indicating copy to clipboard operation
omarchy copied to clipboard

RDSEED32 is broken. Disabling the corresponding CPUID bit - after today's last update

Open guirossibrum opened this issue 1 month ago • 13 comments

System details

Omarchy 3.1.7 / Linux 6.17.8-arch1-1

What's wrong?

I never seen this error until today's update. Does anyone know a fix? thank you

Image

guirossibrum avatar Nov 15 '25 12:11 guirossibrum

PS, the system still boots, but it takes about 30 seconds longer. Thank you

guirossibrum avatar Nov 15 '25 12:11 guirossibrum

Update - at first I thoght this was caused by Omarchy update, but then after some more research, I found this can be related to an AMD firmware/BIOS issue: https://www.amd.com/en/resources/product-security/bulletin/amd-sb-7055.html

Question - when AMD releases updated BIOS, am I able to update it via Omarchy Menu / Update / Firmware? thanks

guirossibrum avatar Nov 15 '25 12:11 guirossibrum

Interesting. I am also experiencing it on my FW13 (AMD Ryzen AI 9 HX 370) and FW Desktop (AMD RYZEN AI MAX+ 395).

marcinczenko avatar Nov 15 '25 21:11 marcinczenko

After this update my bluetooth adapter is no longer detected (FW Desktop)

kylebragger avatar Nov 16 '25 15:11 kylebragger

After this update my bluetooth adapter is no longer detected (FW Desktop)

i just installed for the first time and have no bluetooth. ( same version same RDSEED32 message )

AnthonyPoschen avatar Nov 17 '25 16:11 AnthonyPoschen

Question - when AMD releases updated BIOS, am I able to update it via Omarchy Menu / Update / Firmware? thanks

Omarchy uses fwupdmgr here. You can check whether your device is supported: https://fwupd.org/lvfs/search?value=framework

My Ideapad is not supported, I'll have to play around with Lenovo's exe file to make it bootable.

ivfiev avatar Nov 17 '25 20:11 ivfiev

Pretty sure it's not a BIOS problem, I'm experiencing the exact same behavior (failing Bluetooth support on the first boot and RDSEED32 after an attempted reboot) on my Lenovo IdeaPad Pro 5 with Ryzen AI 7 350.

The bootable snapshots saved me tho.

pkwagner avatar Nov 17 '25 20:11 pkwagner

For Framework users, some more info may be coming here: https://community.frame.work/t/rdseed32-is-broken-disabling-the-corresponding-cpuid-bit/77830

marcinczenko avatar Nov 17 '25 23:11 marcinczenko

After this update my bluetooth adapter is no longer detected (FW Desktop)

i still don't want to believe it, but after lot's of things tried this worked, so maybe it works for you. @kylebragger https://www.reddit.com/r/archlinux/comments/zweejv/comment/lwlq8b5/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button

AnthonyPoschen avatar Nov 17 '25 23:11 AnthonyPoschen

After this update my bluetooth adapter is no longer detected (FW Desktop)

i still don't want to believe it, but after lot's of things tried this worked, so maybe it works for you. @kylebragger https://www.reddit.com/r/archlinux/comments/zweejv/comment/lwlq8b5/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button

Yes hard reset (unplug + hold power button) worked for me on Beelink GTR9 Pro to get bluetooth working. However the "RDSEED32 is broken" still appears on reboot.

cyppe avatar Nov 18 '25 07:11 cyppe

For the RDSEED32 problem, the fix has already been merged into the Linux kernel repository. I guess the next release will fix it.

pkwagner avatar Nov 18 '25 12:11 pkwagner

I am experiencing the same issue on my Lenovo Thinkpad T14s (AMD Ryzen AI 7 Pro 350) causing my bluetooth chip to be unavailable (so no bluetooth since kernel update). Do we know when the new release of the Linux kernel with the fix will be ?

P.S. The hardreset fix didn't work for me, if anyone has another fix, I'm interested

Tigid0u avatar Nov 22 '25 10:11 Tigid0u

FYI the kernel commit linked above isn't the full fix, the other half of the fix will come in the linux-firmware package (which hasn't yet been released - the latest firmware release https://archlinux.org/packages/core/any/linux-firmware/ doesn't include that microcode update). Also I believe that microcode update is for the Epyc 9005 processors, not the consumer Ryzen processors. AMD's page says the target release is "late Nov 25". https://www.amd.com/en/resources/product-security/bulletin/amd-sb-7055.html - so we're still a ways out from this being fixed :(

I ended up compiling a kernel that commented out the check for "RDSEED32 is broken" to fix this for myself. I don't recommend this unless you know what you are doing :)

diff --git a/arch/x86/kernel/cpu/amd.c b/arch/x86/kernel/cpu/amd.c
index 5d46709c58d0..a4677799adca 100644
--- a/arch/x86/kernel/cpu/amd.c
+++ b/arch/x86/kernel/cpu/amd.c
@@ -1050,11 +1050,11 @@ static const struct x86_cpu_id zen5_rdseed_microcode[] = {

 static void init_amd_zen5(struct cpuinfo_x86 *c)
 {
-       if (!x86_match_min_microcode_rev(zen5_rdseed_microcode)) {
-               clear_cpu_cap(c, X86_FEATURE_RDSEED);
-               msr_clear_bit(MSR_AMD64_CPUID_FN_7, 18);
-               pr_emerg_once("RDSEED32 is broken. Disabling the corresponding CPUID bit.\n");
-       }
+       // if (!x86_match_min_microcode_rev(zen5_rdseed_microcode)) {
+       //      clear_cpu_cap(c, X86_FEATURE_RDSEED);
+       //      msr_clear_bit(MSR_AMD64_CPUID_FN_7, 18);
+       //      pr_emerg_once("RDSEED32 is broken. Disabling the corresponding CPUID bit.\n");
+       // }
 }

 static void init_amd(struct cpuinfo_x86 *c)

phillipleblanc avatar Nov 24 '25 08:11 phillipleblanc