Intel ucode Plugin vs Package

Started by BrandyWine, Today at 04:32:44 AM

Previous topic - Next topic
Today at 04:32:44 AM Last Edit: Today at 04:42:37 AM by BrandyWine
I have the latest 26.1.x_x version of community OPNsense installed, but I see I still have the OPNsense Intel ucode v1.1 Plugin installed, and also the ucode package "cpu-microcode-intel-20260227" and the "os-cpu-microcode-intel-1.1". Is the plugin even needed if the latest ucode is in the Intel package?

IIRC, long ago I though in some of the upgrade text it had mentioned something about the plugin being deprecated, or something like that.
Mini-pc N150 i226v x520, FREEDOM

Uninstalling the plugin will uninstall the corresponding microcode. The real question is whether you need the microcode or you can just fallback to the one included in freebsd/opnsense. At this point, with what we have seen over the last 12 months, I would just remove it, and if nothing significant happens, keep it that way.

Quote from: sopex on Today at 10:11:46 AMAt this point, with what we have seen over the last 12 months, I would just remove it

Then you will run your CPU without any ucode updates (apart from ones that might be in your MB manufacturer's BIOS). The updates the FreeBSD/OPNsense plugin provides are not permanent but need to be applied at every boot.
Deciso DEC750
People who think they know everything are a great annoyance to those of us who do. (Isaac Asimov)

Quote from: Patrick M. Hausen on Today at 10:31:30 AM
Quote from: sopex on Today at 10:11:46 AMAt this point, with what we have seen over the last 12 months, I would just remove it

Then you will run your CPU without any ucode updates (apart from ones that might be in your MB manufacturer's BIOS). The updates the FreeBSD/OPNsense plugin provides are not permanent but need to be applied at every boot.

Yes, I totally agree with you.

IIUC...

The package (cpu-microcode-intel) gets installed by the plugin (os-cpu-microcode-intel) - no plugin, no package!

It appears that it's the x86info utility (also installed by the plugin) that reports itself as deprecated, not the (whole) plugin.

Quote from: dseven on Today at 11:53:27 AMIt appears that it's the x86info utility (also installed by the plugin) that reports itself as deprecated, not the (whole) plugin.

Correct. People also tend to overlook the message below that text box:

QuoteOutput shown here for diagnostic purposes. There is no general need for manual system intervention.
Deciso DEC750
People who think they know everything are a great annoyance to those of us who do. (Isaac Asimov)