Linux

63359 readers

1614 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 6 years ago

MODERATORS

nooter692@lemmy.ml

AgreeableLandscape@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

RDSEED 32 is broken. (piefed.social)

submitted 2 weeks ago by DanceMomsSavedMe@piefed.social to c/linux@lemmy.ml

5 comments fedilink hide all child comments

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?

you are viewing a single comment's thread
view the rest of the comments

[–] EmDash@lemmygrad.ml 1 points 1 week ago

Nothing bad will happen if you ignore this. You'll just keep getting the message on boot.

If you want to fix it, you'll need to upgrade your BIOS. Find out what motherboard you have and go to the manufacturer's website; then download the latest BIOS. Put that file on a FAT formatted thumb drive and boot to your BIOS (hold either F2 or DEL on boot, look up the key for your motherboard manufacturer). In the BIOS there will be a option to upgrade the BIOS from USB. Run that and you should be good to go!