RDSEED 32 is broken.

submitted by

So I have that error when it starts up and it says “RDSEED32 is broken disabling the corresponding CPU bit”

I noticed today that AMD has already patched this but what is the easiest and beginner friendly way to update it on my machine? I run fedora.

I was hoping it would be some update within Linux but so far no dice as according to this page from AMD the update has already been issued. (https://www.amd.com/en/resources/product-security/bulletin/amd-sb-7055.html)

I know windows is usually the easiest way to do these things but I would be willing to learn a little bit (within my technical limits) to avoid using it for this.

And if I DID have to use windows, right now I’m using LUKS encryption so isn’t that like a monster to add windows into without messing stuff up?

I am very beginner on command line stuff but can navigate through files and stuff like that.

What’s the best move for this?

5
16

Log in to comment

Hot Top New Old

You’ve updated your motherboard’s firmware to a version that includes the fix?

What issue are you having from the missing instruction?

 reply
10
OP

I have not I guess this is step one? I was hoping to figure out a way to do it within fedora somehow but I will look into updating the motherboards firmware first then.

 reply
2
edited

If your motherboard manufacturer releases firmware through LVFS, you can use

sudo fwupdmgr refresh --force sudo fwupdmgr update

But that should normally be offered through the GNOME or KDE update utility.

I’m assuming your motherboard manufacturer doesn’t support updating through the OS (or hasn’t released a new enough AGESA build) based off your issue

 reply
1

This message “RDSEED32 is broken” pops up, because the Linux kernel checks for an AMD microcode version from before the issue was fixed. If it finds that, it disables the instruction.

Just to note, on average desktop use, this issue (with the current workaround) may cause a very slight speed decrease, but otherwise isn’t harmful. You can fix it, there’s just not a lot of reasons to do so outside of “making the error message disappear”.

You’d fix this by updating your kernel and CPU microcode to the latest available versions. I’m not sure how this process works on Fedora. This should be fixed automatically over time by just clicking “update system” when asked.

 reply
2

Just fix RDSEED32, what’s the big deal?

 reply
1
Insert image