Ubuntu won't install: RDSEED32 is broken. Disabling the corresponding CPUID bit

Which Linux distro are you using? Ubuntu

Which release version? 24 LTS

Which kernel are you using? 04.4

Which BIOS version are you using? 4.03

Which Framework Laptop 16 model are you using? AMD Ryzen™ AI 300 Series

My Framework 16 has two SSDs. I installed Windows 11 on the first, and I’m trying to install Ubuntu 24.04 on the second.

After selecting to “Install Ubuntu” the process begins but gets stuck when the message “RDSEED32 is broken. Disabling the corresponding CPUID bit.”

Tapping the power button will bring back the loading screen, but then it freezes.

To my knowledge, I have run all possible updates. Additionally, I added “clearcpuid-reseed” on the linux line of the GRUB boot menu, though I’m not completely confident I did this correctly.

Any help is greatly appreciated. In the meantime, I’m stuck using Windows :frowning:

1 Like

One other note - there are a lot of posts saying the notice came up and then the system booted and worked fine. There are also a lot of Fedora posts.

I haven’t been able to find anyone with my specific issue of not being able to install Ubuntu.

This may not be helpful, but my wife and I just setup a dual-boot on her Framework 16, but the GNU/Linux distro is Debian sid (installed testing and then switched the repos to sid), so I’d be surprised if Ubuntu fails to work here.

If you edit the boot options to not have quiet (I think the defaults are probably quiet splash — remove both of those), do you see any additional errors?

1 Like

I really hope this is a typo. The latest kernel version available in Jammy seems to be 6.17. If your installer is giving you kernel 4.4, there’s a problem.

This worked! Thanks for the help.

Now I just have to figure out why the second SSD isn’t showing up in the Ubuntu install process… but that’s a separate issue.

Oh that’s interesting! I was hoping it would reveal more errors :joy: Make sure the SSD is seated correctly (does it show up in the UEFI or in Windows?).

Hi, I have exactly the same issue with my HP Victus 15-fb3012nf RTX 5060 Ryzen AI 5 340. The only difference is that I want to dual boot on the same SSD. Same error, same message, same symptoms, same behaviour. I spent 3 hours with HP support’s AI bot and a 10 min with a real human who ended saying me HP support doesn’t take Linux in charge. Can you explain me in detail how to fix the problem? Please it’s 2 days now I’m struggling…

1 Like

Look into disabling Plymouth at boot time.

The real fix is a BIOS update, but while you are waiting for a BIOS update, the temporary workaround (not a complete fix) is to disable Plymouth so that it doesn’t cause the boot process to fail.

The RDSEED32 is not a problem. The PC should boot and install without a problem with or without that message.
The install problem is elsewhere.
In the past, i have found that installing linux first, then installing windows works better.
You could try removing the ssd with windows on it. Install linux on the other and then insert the windows ssd back in after.
The Ubuntu install program is rubbish. Unless the disk configuration is exactly what the ubuntu installer expects, it generally does not work.
For example, the debian installer works for a much larger variety of disk configurations.
This is why removing the windows ssd might help. Ubuntu installer is more likely to be ok with it.

Note: i raised ubuntu bug reports about the ubuntu installer 3 years ago. None of them have been fixed.

This is a framework community, meant for framework devices. HP discussions are not suitable here, i suggest you go to HP community for this or any other community unless Framework has a off-topic section for non-framework devices.

Since right now you’re posting in a topic relating the Framework 16 laptop and HP is way out of bounds when it comes to this, since HP is not part of Framework.

ThanK you very much for your answer. I’ll try try a Debianand if it doesn’t work I’ll try installing a second SSD. Thanks again!

RDSEED should be fixed in Bios 3.05 now and i tried it and no longer see it anymore :slight_smile:

I still see the error message with BIOS 3.05 but as noted by others, everything seems to be working.

Mar 30 19:33:13 frame kernel: RDSEED32 is broken. Disabling the corresponding CPUID bit.

product: Laptop 13 (AMD Ryzen AI 300 Series) (FRANVACP05)

-firmware
description: BIOS
vendor: INSYDE Corp.
physical id: 0
version: 03.05
date: 10/30/2025

This message and its cause have been discussed to absolute death at RDSEED32 is broken, disabling corresponding CPUID bit.

because bios update 3.05 fix is only on framework 16 inch, which this topic is related for.

They need to roll out new update for 13 inch with fix for that.

The 13 inch laptop with Ryzen AI 300 series had it’s last bios update in 2025/11/24 which is 3.05 but that version does not have RDSEED32 fix.

So for your laptop you will have to wait for Bios 3.06 that will have most likely a fix for the RDSEED32.

1 Like

Oh, thanks. I missed that detail. :wink:

I had already installed Windows on one SSD before installing Ubuntu.

The quickest solution was to remove the Windows SSD, install Ubuntu on the remaining SSD, then reinstall the Windows SSD.

Everything has been working fine since! Expect for when I have to use Windows. Then air quotes are needed around “worked” (this is a Microsoft joke, not an actual issue).

Just for info. The RDSEED32 does not affect anything that a user will notice.
It simply asks crypto libraries to not use that instruction. The crypto library will simply use alternatives.
A user will not notice any performance difference.
The RDSEED32 message in the logs can be safely ignored.