I love Solus so after installed on my personal laptop I try it on my dad laptop (Huawei Matebook 14 witn Zen+ Amd SoC) that is a problematic pc on linux because Huwei abandoned it since the start so no bios update and AMD update microcode only for last top cpu, so the amd-ucode load from bios is not 100% linux compatible.
PC freez every hour or so performing normal task as browsing, watching video or download a ISO.
That's why I have a "good" microcode amd_uc.img (the same in HP and Dell laptop with the same CPU) and I have used it without issue for long time with a "Trick" putting the good microcode on the /Boot folder, reload grub (on distro with grub) and freez problem solved.
Sadly since november probably some changes on firmware, kernel, mkinitcpio, I don't know ...but now if I do a
sudo dmesg | grep -i micro
systems (arch, debian, all I have try) shows me they are loading the bad microcode that has patch_level=0x08101007 instead of the good microcode I have in /Boot folder that have patch_level=0x08101016
That's why freez come back again sadly since november.
My sistem is this:
CPU:
Info: model: AMD Ryzen 5 2500U with Radeon Vega Mobile Gfx bits: 64
type: MT MCP arch: Zen level: v3 note: check built: 2017-19 process: GF 14nm
family: 0x17 (23) model-id: 0x11 (17) stepping: 0 microcode: 0x8101007
Solus is using bios microcode so it's freezing too even less frequent than arch distros or debian, so my question is:
in Solus how can I load my "good" amd-ucode.img stored on /Boot instead of the bad one in the bios?
Thanks
