Warning try at own risk
IntroductionARM processors users can ignore this post as
An Arm processor SNIP does not use digital microcode SNIP
https://www.zdnet.com/article/arm-processors-everything-you-need-to-know-now/Bios updates are preferred over using early loading microcodes
Microcodes are useful if motherboard maker has no recent bios updates or
third party bios maker reluctant to provide updates or
you may be reluctant to flash bios as you may be concerned you might "brick" your motherboard.
Some motherboards can have dual bios setups YMMV
Kernel series 6.1 and higher no longer allow late loading of microcodes.
With kernel version 6.1 a late microcode loading is not possible anymore because it is now disabled by default
https://wiki.gentoo.org/wiki/MicrocodeWhy else is it important to use early loading microcodes?
Loading microcode early can fix CPU issues before they are observed during kernel boot time
https://www.kernel.org/doc/html/v5.18/x86/microcode.htmlContentsPost 2 create AMD all current microcodes
Post 3 create AMD microcode for your CPU family
Where possible I include a command and my output in a quote box. I use a quote box
to make certain links scrollable
Research current bios microcodes.
grep microcode /proc/cpuinfo
grep microcode /proc/cpuinfo
microcode : 0x8108109
microcode : 0x8108109
microcode : 0x8108109
microcode : 0x8108109
The duplication of microcodes means 4 cores.
I also used
https://wiki.archlinux.org/title/microcodeNote that early loading microcodes reside in RAM so are lost on shutdown or reboot.
They can not update your bios firmware. But you can regain them by using the same bootloader menu.
If you are too lazy to have multiple boot loader menus, you could try
a live edit of bootloader to disable microcodes from *ucode image
dis_ucode_ldr
Proof boot code worked can be seen by not giving any hits for
dmesg | grep microcode
Note that boot code needs understems and fails with hyphens.
For those migrating from persistent file distros, we do do not use
sudo update-initramfs -u
to embed microcodes into our core or rootfs
Research to see if you can use an early loading
microcode for your CPUstep 1
Identify your AMD cpu family
grep -F -m 1 "cpu family" /proc/cpuinfo
cpu family :23
step 2
check link for possible matches
https://wiki.gentoo.org/wiki/AMD_microcode#Microcode_firmware_filesdecimal 23 becomes 17 hexadecimal (=17h)
17h has 3 possible firmware but only one is Ryzen so...
step 3 if needed for 17h or 19h....one way to check
tce-load -w -i inxi
inxi -Cxxx
inxi -Cxxx
CPU:
Info: quad core model: AMD Ryzen 3 3200G with Radeon Vega Graphics bits: 64
type: MCP smt: <unsupported> arch: Zen/Zen+ note: check rev: 1 cache:
step 4 If still unsure start a new forum post
I suggest you post inxi -Cxxx and inxi -Mxxx
inxi -Mxxx
Machine:
Type: Desktop Mobo: Micro-Star model: B450 GAMING PLUS MAX (MS-7B86) v: 3.0
serial: <superuser required> BIOS: American Megatrends LLC. v: H.C0
date: 05/17/2021
You can not use early loading unless your current CPU falls under family
15h to 19h