I got my new computer (and my first linux machine) some months back and a little while I started getting an error on startup saying RDSEED32 is broken disabling cubit. After that my USB ports stopped working reliably. Googling the problem led to a lot of things that a newbie Linux user like me wouldn't understand, so I turned to AI. It got me to do a bunch of edits to the grub file, which didn't fix the error but seemed to get my USB working ok, and actually fixing the error seemed like it required messing with my bios which was too big of an ask from an AI to do for me, so I put it out of my mind and thought that updates would fix it.
Cut to now, when apparently my usb problems affecting my mouse speed and youtube audio now **(Edit: Fix that, turned out to be driver problem)**and the updater isn't working, but that is apparently an unrelated issue, according to chat gpt, and I think I need to rely on some kindly strangers to help me fix the RDSeed error and not rely on random googling and chat gpt.
System information
OS: Zorin 18.1 Pro
Processor: AMD Ryzen™ 9 9900X × 24
Graphics: NVIDIA 5070ti
Memory: 32 gb
Firmware version 9004
Linux Kernel 6.17.0-23-generic
I'll also include the grubs file. I don't have the chatgpt logs of everything I did but I know I added all the "quiet splash amd_iommu=off pcie_aspm=off usbcore.autosuspend=-1 usbcore.old_scheme_first=1" stuff
Hello, thank you very much for responding!
The software update program isn't working for me. Would that be something I have to go to the manufacturer's website for or something? I've never had to update my BIOS before.
Also, the youtube and mouse studdering turned out to be a nvidia driver issue, which I managed to fix, but RDseed is still broken.
Okay, got it. I'm looking at the bios files for my motherboard and it mentions needing to use a flashback tool and to rename something with BIOS renamer. Stuff like that makes me kinda nervous (I'm not super tech savy). Do I have to chase down those tools? Is there a step by step resouce? This is what I'm looking at: PRIME B850-PLUS｜Motherboards｜ASUS Global
Well, that was an ordeal. After many failed EZflash attempts and more Flashback attempts, using different files (and quickly learning that prime b850 plus was different from a prime b850 plus wifi board) I managed to get it to work. It turned out to be a problem with my mobo specifically. Cyberpower cheaped out and the version of Bios that shipped was a very bad one that seemed to think new versions of BIOS was old versions, to my uneducated understanding. Thankfully the exact voodoo magic I needed to do was outlined in a reddit post I stumbled across here: https://www.reddit.com/r/ASUS/comments/1oq5t79/asus_prime_b850_plus_wifi_bios_update_has_me/
Thanks a lot Nourpon for helping me through this, often I don't know where to start fixing problems if google doesn't present an obvious solution. You are a scholar and a saint.
A quotation of the steps, in case that reddit post vanishes and some other poor sufferer stumbles on this thread looking for the solution:
I downloaded the latest version of the correct bios for this motherboard, extracted it, used the rename tool to rename the bios, and then copied this A5660.CAP file to a USB flash drive.
The USB flash drive is recommended to be < 32 GB (mine was 16 GB), and it should be formatted to FAT32. The A5660.CAP file was the only file present on the flash drive.
I shut the system down, and flipped the physical power supply switch off for 20 seconds, then flipped the power supply switch back on and left the PC powered off.
I placed the USB drive into the USB slot marked "BIOS" on the back of my PC, and then held down the FlashBack button (very close to the USB slot) for 3-5 seconds until I saw the LED blink 3 times.
This starts the flashback process of loading the bios from the USB to the motherboard. The LED continued blinking for 4-5 minutes, and then stopped. At this point, I powered up the PC and I now had the correct bios installed and working as expected.
This bios change did necessitate that I recreate my Windows PIN once it loaded.
Edit: The CAP file I used was different than the one in instructions because it was newer, so don't be surprised if yours is also different poor person from the future.
