OPNsense Forum

English Forums => Hardware and Performance => Topic started by: fastboot on May 14, 2026, 09:37:05 AM

Title: cpu-microcode-intel: no matching update found on Intel Core i3-1215U
Post by: fastboot on May 14, 2026, 09:37:05 AM
Hi @Franco,

I may have found a microcode packaging/split-file issue on OPNsense.

System:

Protectli VP6630
Intel Core i3-1215U, Alder Lake R0
coreboot 0.9.0

Installed packages:

cpu-microcode-intel-20260227
os-cpu-microcode-intel-1.1

Current microcode after boot:

x86info -a | grep -i micro
Microcode version: 0x0000000000000432

Boot message:

dmesg | grep -i micro
[1] CPU microcode: no matching update found

The package only provides this split file for CPUID 06-9a-04:

/usr/local/share/cpucontrol/06-9a-04.40
but for Intel Core Gen12 / Alder Lake R0 I would expect platform 06-9a-04/80, not /40.

Full relevant output:

pkg info -x microcode
cpu-microcode-intel-20260227
os-cpu-microcode-intel-1.1

pkg info -l cpu-microcode-intel | grep -E 'intel-ucode|06-9a-04|microcode'
cpu-microcode-intel-20260227:
        /boot/firmware/intel-ucode.bin
        /usr/local/share/cpucontrol/06-9a-04.40

find /usr/local/share/cpucontrol /boot/firmware -iname '*06-9a-04*' -o -iname '*intel*ucode*'
/usr/local/share/cpucontrol/06-9a-04.40
/boot/firmware/intel-ucode.bin



Is it possible that the split microcode file 06-9a-04.80 is missing from the package, so the Intel microcode plugin cannot update this CPU and keeps the firmware-provided 0x432?

Thanks!


FB
Title: Re: cpu-microcode-intel: no matching update found on Intel Core i3-1215U
Post by: meyergru on May 14, 2026, 12:29:21 PM
It really looks like this is the case. There should be two more files, namely .10 and .80 if the full binary was split correctly. Under Linux, where full binaries are in use, the file is three times as big as the .40 version. You CPU should have a 0x43a firmware.

To carry over the correct files is a little complicated, because on boot, intel-ucode.bin is used and that lacks the relevant parts as well.

You should probabaly create a bug report for FreeBSD.