Hi, my Huawei Matebook D 14" with zen+ AMD Ryzen 2500 is not well compatible with linux, there are some freez everiday when browsin or open videos (more than 4 times a day), the reason is Huawei abandon Matebook and no Bios update since the beginning and AMD microcode available on linux kernel is not last one (the last and working I have grab on github and is safe and I use it since years)
So the only working solution is a TRICK, insert the wotking AMD ucode that i found on /BOOT so the system load it instead of the old and problematic microcode. This trick was perfectly working on Cachyos but since last month my troubles come back again, freez and freez … so I made a
sudo dmesg | grep -i micro
and the result is that cachy now is loading the old and problematic amd microdode instead of mine even if mine is placed in the /BOOT folder but is not loaded anymore.
Probably some changes on Cachy that now force load microcode avalable on kernel … How can I solve? I need my microcode loaded instead of default, is the only way to use the notebook becaus 4 or more freez at day is not a great experience, when freezing I only can force restart and is not healthy for my laptop
Thank and sorry for my englhis, I hope you understand my problem.
yes, what is strange is that even if on /ROOT there is no more the buggy microcode, I uninstalled amd-ucode too so no more microcode on my system, if i do a sudo dmesg | grep -i micro the result is the old and buggy microcode and I don’t know where Cachy is loading it.
I update grub with sudo grub-mkconfig -o /boot/grub/grub.cfg restart my machine but the output is the same: cachy is loading the old one, probably directly from the kernel and not seen my good microcode on /ROOT.
Before it was not that way, cachy was loading my microcode first, that change in the behaviour is more or less since last month.
My machine freez opening terminal 2 times in last 5 minutes, so I need loading my microcode instead or the system will be damaged with those frequent force restarts.
Ever consider that your BIOS firmware might also hold CPU microcode? If you uninstalled the microcode package then obviously it’s not going to load whatever new version is working for you. What is the exact path of the “good microcode” in “/ROOT”?
my “good microcode” is stored on /ROOT simply that and it was working.
On a secondary partition I installed Garuda to test (last year the trick was working on Garuda and Endeavour) and sadly seems the trick is not working anymore, even on Garuda loaded microcode is the bad one.
Probably since last month for security reason kernel is set to load its microcode no mater what you have on ROOT. This means I have to force restart several time a day my crappy Huawei laptop 
I try LTS kernel but the result is the same.
BIOS firmware is the same since 4 years ago and then abandoned by Huawei so if previously the “trick” was working it means that BIOS firmware doens’t hold microcode.
I write to Huawei asking update BIOS and they reply that machine is only windows 10 compatible and not linux …
What is the absolute path of the “good microcode” here? Frankly I’m not sure what /ROOT is and the fact that the kernel itself doesn’t have any microcode blobs.