microcode update

fernandel

fernandel

I got a msg during boot: CPU microcode: no matching update found

My system: FreeBSD 15.1-RELEASE-p1
In /boot/loader.conf I have:
Code: 
cpu_microcode_load="YES"
cpu_microcode_name="/boot/firmware/amd-ucode.bin"
I have installed cpu-microcode-amd and cpu-microcode-rc

lscpu shows:
Code: 
Architecture:            amd64
Byte Order:              Little Endian
Total CPU(s):            8
Thread(s) per core:      2
Core(s) per socket:      4
Socket(s):               1
Vendor:                  AuthenticAMD
CPU family:              23
Model:                   24
Model name:              AMD Ryzen 5 PRO 3500U w/ Radeon Vega Mobile Gfx
Stepping:                1
L1d cache:               32K
L1i cache:               64K
L2 cache:                512K
L3 cache:                4M
Flags:                   fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 cflsh mmx fxsr sse sse2 htt sse3 pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 popcnt aes xsave osxsave avx f16c rdrnd syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm lahf_lm cmp_legacy svm extapic cr8_legacy lzcnt sse4a misalignsse 3dnowprefetch osvw skinit wdt tce topoext perfctr_core perfctr_nb pcx_l2i
In the past it worked but not anymore.

Thank you.
 
fahrenheit said:
fernandel see if you have microcode package installed:
$ pkg info *microcode*

In your case you should have at least these two packages:
cpu-microcode-amd-20251202
cpu-microcode-rc-1.0_2
Click to expand...
Code: 
 pkg info *microcode*
cpu-microcode-amd-20251202
cpu-microcode-rc-1.0_2
and I have in /boot/firmware/amd-ucode.bin
 
bob2112 said:
AFAIK you don't need cpu-microcode-rc-1.0_2 for loading from loader.conf, it provides an rc script to load the microcode later.
Click to expand...
I enable it rc.conf for loading later and disable in /boot/loader.conf and looks lie it works.
I tried to delete cpu-microcode-rc but it deleted also *-amd and when I pkg installed cpu-microcode-amd than install both again.
 
No, it doesn't work. I do not know what the problem is.
Code: 
 sysctl -a | grep microcode
CPU microcode: no matching update found
        value:  cpu_microcode
 

Nandor said:
Hi fernandel!


Same effect here, identical configuration via /boot/loader.conf.


- FreeBSD 14.4-RELEASE-p7
- cpu-microcode-intel-20260512_1 [quarterly]

Code: 
kernel: CPU microcode: no matching update found
kernel: CPU: Intel(R) Core(TM) i5-10400 CPU @ 2.90GHz (2900.00-MHz K8-class CPU)


The only thing I found on the subject: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=295351

But that doesn't help me either...


Any ideas or explanations are welcome.
Click to expand...
Did you check your cpu with https://github.com/speed47/spectre-meltdown-checker ? It is also in ports.
I did and many are from vendor safe, some no bsd scrips and few are vulnerable.
 
This commit has been applied to STABLE (14 & 15) and CURRENT. As it corrects a serious bug, that may arrive in the next patch, but for sure in the next minor version.

You will have to copy the loader.efi into your ESP. Do you know how to do?

If you are in hurry, you can try this one (it has this commit), newly compiled from CURRENT (for another reason).
Emrion

Post in thread 'Loader not found after upgrading the BIOS Boot Loader (Root on ZFS, freebsd-boot on USB)'

For those who are interested with EFI booting that works with a root file system that does not necessarily reside on the boot disk, Warner informed me about a recent feature of loader.efi (only in 16-CURRENT for the moment): the boot_policy variable.

You can set this var inside /efi/freebsd/loader.env or by efibootmgr. You have two choices: boot_policy=strict or boot_policy=relaxed

strict means that the loader acts as it does for 15 and lower versions: it won't boot a zpool that not belongs to the boot disk. relaxed allows to boot the zpool of...
  • Like
  • Thanks
 
Emrion said:
This commit has been applied to STABLE (14 & 15) and CURRENT. As it corrects a serious bug, that may arrive in the next patch, but for sure in the next minor version.

You will have to copy the loader.efi into your ESP. Do you know how to do?

If you are in hurry, you can try this one (it has this commit), newly compiled from CURRENT (for another reason).
Emrion

Post in thread 'Loader not found after upgrading the BIOS Boot Loader (Root on ZFS, freebsd-boot on USB)'

For those who are interested with EFI booting that works with a root file system that does not necessarily reside on the boot disk, Warner informed me about a recent feature of loader.efi (only in 16-CURRENT for the moment): the boot_policy variable.

You can set this var inside /efi/freebsd/loader.env or by efibootmgr. You have two choices: boot_policy=strict or boot_policy=relaxed

strict means that the loader acts as it does for 15 and lower versions: it won't boot a zpool that not belongs to the boot disk. relaxed allows to boot the zpool of...
  • Like
  • Thanks
Click to expand...
Hey Emrion;

to the point and detailed, as always.
That makes everything much clearer to me; so the easiest way is to just wait and see...

You will have to copy the loader.efi into your ESP. Do you know how to do?
Click to expand...
Yeah, since your posts in the updating-bootcode thread; really appreciate that!
The instructions for making it right away are the icing on the cake;

i'll take a look at it when I have some free time.


Thank you very much!
 
You must log in or register to reply here.
Back
Top