On Monday, 29 January 2024 16:18:22 GMT Peter Humphrey wrote: > On Sunday, 28 January 2024 17:39:56 GMT Michael wrote: > > I'm not sure a microcode update has been released yet by AMD as a blob, > > outside what they make available to MoBo OEMs within 'BIOS firmware' > > updates. To find what's in the box use: > > > > dmesg | grep -i 'family:' > > > > Then check what CPU family and model microcodes the linux-firmware > > contains: > > https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.gi > > t/ tree/amd-ucode/README > > No luck with those.
OK, this means there is no microcode to load via the linux-firmware releases (yet). > > If you can't find your family and model in the above, then you could check > > what firmware updates are available by the MoBo's OEM. These would > > include > > microcode made directly available by AMD to the OEM. > > That's ASRock X570 Taichi. Their pages suggest that they only acknowledge > Windows 10 & 11. Check the BIOS version in dmesg and compare it with the with the ASRock's AMD chipset image on the asrock.com website. If the versions/dates are the same you have nothing more to do. If the version on the website is more recent then you may want to flash the MoBo with it. Download the zip archive on offer and unzip it, then store the new image on a USB stick which has been formatted with FAT32. Some OEMs require you rename the firmware image file, it will say so on the website, or in a README within the zip archive. Reboot and press [F2] during POST to get into the BIOS setup menu, then go to the Tools tab to flash it from the USB. You may have to re-apply in the BIOS menu any changes you had previously made after the PC reboots, because restoring the settings from a backup file doesn't always work. > I'll keep my eyes open for another glitch. Maybe the microcode isn't to > blame at all, in which case I'd better not sleep on the job. Well, updating the BIOS firmware with the latest version often contains patches for bugs and microcode patches for CPU vulnerabilities. However, this does not mean it will address the MCE errors you were experiencing.
signature.asc
Description: This is a digitally signed message part.
