Update Failed With This Error

[nbca2]

Here are the details:

Code Select Expand

Reloading firmware configuration
Flushing all caches...done.
Writing firmware settings: FreeBSD OPNsense
Writing trust files...done.
Scanning /usr/share/certs/untrusted for certificates...
Scanning /usr/share/certs/trusted for certificates...
Scanning /usr/local/share/certs for certificates...
certctl: No changes to trust store were made.
Writing trust bundles...done.
Configuring login behaviour...done.
Configuring cron...done.
Configuring system logging...done.
=====
Message from cpu-microcode-rc-1.0_2:

--
This port includes an RC script, which is one of two methods to update
the CPU microcode on a FreeBSD system.

1. Early loading.
   This method does not use the RC script included here.
   This is the preferred method, because it ensures that any CPU features
   added or removed by a microcode update are visible to the kernel by
   applying the update before the kernel performs CPU feature detection.

   To enable updates using early loading, add the following lines to
   /boot/loader.conf:

   cpu_microcode_load="YES"

   and the appropriate one of these lines:

   cpu_microcode_name="/boot/firmware/intel-ucode.bin"
   cpu_microcode_name="/boot/firmware/amd-ucode.bin"

   The microcode update will be loaded when the system is rebooted.

   AMD systems running FreeBSD prior to 2024-02-22 snapshot
   34467bd76 only support late loading.


2. Late loading.
   This method, which does use the RC script included here, is enabled by
   adding the following line to /etc/rc.conf:

   microcode_update_enable="YES"

   The microcode update is then applied upon reboot or when the microcode
   update service is run via:

   # service microcode_update start

   If the CPU requires a microcode update, a console message such as the
   following will appear:

   Updating CPU Microcode...
   /usr/local/share/cpucontrol/m32306c3_00000022.fw: updating cpu /dev/cpuctl0 from rev 0x17 to rev 0x22... done.
   /usr/local/share/cpucontrol/m32306c3_00000022.fw: updating cpu /dev/cpuctl2 from rev 0x17 to rev 0x22... done.
   /usr/local/share/cpucontrol/m32306c3_00000022.fw: updating cpu /dev/cpuctl4 from rev 0x17 to rev 0x22... done.
   /usr/local/share/cpucontrol/m32306c3_00000022.fw: updating cpu /dev/cpuctl6 from rev 0x17 to rev 0x22... done.
   Done.

It is safe to enable both methods.
=====
Message from x86info-1.31.s03_1:

--
===>   NOTICE:

This port is deprecated; you may wish to reconsider installing it:

Abandoned upstream, fails to identify anything remotely new according to upstream issue reports.

It is scheduled to be removed on or after 2025-06-30.
=====
Message from cpu-microcode-amd-20241121:

--
Refer to the cpu-microcode-rc installation notes to enable AMD microcode
updates.
Checking integrity... done (0 conflicting)
Nothing to do.
***DONE***

And as you can see, the notice pertains only to the x86info package, which installs alongside the microcode update in order to be able to actually query which microcode is loaded, not to the microcode package itself.

thanks for the clarification, i misread the output

[BrandyWine]

If the plugin wil be deprecated, why bothering about it?

Who's claiming it is deprecated? Microcode updates are essential, IMHO.

Right in the plugin info when you install it. Who wrote that plugin?

[Patrick M. Hausen]

That info is coming from the x86info package, not from the plugin. See above.

[vk2him]

My Protectli NUC upgraded with no issues - I have os-cpu-microcode-intel installed

What model do you have? I have a VP2420 and plan to upgrade during the weekend.

Sorry for delay in reply - I have a VP2410, so the older version of the one you have

[mschaeffler]

I have a Protectli V1410 and also faced this issue

[Chunkers]

Hi,

I have been running OPNsense on a (Chinese) CWWK micro PC Intel N305 for a about a year with zero issues.

When I upgraded to 25.1.12 (and subsequently also direct to 25.7 from img) my router crashes at a random but fairly short time from successful installation. I have made 3 attempts so far, so before I try again I need to change something.

I wasn't able to get log files but I did manage to submit a couple of crash reports and before reinstalling 25.1 from an image (still runs flawlessly).

CORRECTION : My installation appears to include the plugin : os-cpu-microcode-intel v1.1 when it updates to 25.1.12 but it is not installed in 25.1

Unsure how to proceed, advice appreciated

[marka2k]

Here are the details:

Code Select Expand

Reloading firmware configuration
Flushing all caches...done.
Writing firmware settings: FreeBSD OPNsense
Writing trust files...done.
Scanning /usr/share/certs/untrusted for certificates...
Scanning /usr/share/certs/trusted for certificates...
Scanning /usr/local/share/certs for certificates...
certctl: No changes to trust store were made.
Writing trust bundles...done.
Configuring login behaviour...done.
Configuring cron...done.
Configuring system logging...done.
=====
Message from cpu-microcode-rc-1.0_2:

--
This port includes an RC script, which is one of two methods to update
the CPU microcode on a FreeBSD system.

1. Early loading.
   This method does not use the RC script included here.
   This is the preferred method, because it ensures that any CPU features
   added or removed by a microcode update are visible to the kernel by
   applying the update before the kernel performs CPU feature detection.

   To enable updates using early loading, add the following lines to
   /boot/loader.conf:

   cpu_microcode_load="YES"

   and the appropriate one of these lines:

   cpu_microcode_name="/boot/firmware/intel-ucode.bin"
   cpu_microcode_name="/boot/firmware/amd-ucode.bin"

   The microcode update will be loaded when the system is rebooted.

   AMD systems running FreeBSD prior to 2024-02-22 snapshot
   34467bd76 only support late loading.


2. Late loading.
   This method, which does use the RC script included here, is enabled by
   adding the following line to /etc/rc.conf:

   microcode_update_enable="YES"

   The microcode update is then applied upon reboot or when the microcode
   update service is run via:

   # service microcode_update start

   If the CPU requires a microcode update, a console message such as the
   following will appear:

   Updating CPU Microcode...
   /usr/local/share/cpucontrol/m32306c3_00000022.fw: updating cpu /dev/cpuctl0 from rev 0x17 to rev 0x22... done.
   /usr/local/share/cpucontrol/m32306c3_00000022.fw: updating cpu /dev/cpuctl2 from rev 0x17 to rev 0x22... done.
   /usr/local/share/cpucontrol/m32306c3_00000022.fw: updating cpu /dev/cpuctl4 from rev 0x17 to rev 0x22... done.
   /usr/local/share/cpucontrol/m32306c3_00000022.fw: updating cpu /dev/cpuctl6 from rev 0x17 to rev 0x22... done.
   Done.

It is safe to enable both methods.
=====
Message from x86info-1.31.s03_1:

--
===>   NOTICE:

This port is deprecated; you may wish to reconsider installing it:

Abandoned upstream, fails to identify anything remotely new according to upstream issue reports.

It is scheduled to be removed on or after 2025-06-30.
=====
Message from cpu-microcode-amd-20241121:

--
Refer to the cpu-microcode-rc installation notes to enable AMD microcode
updates.
Checking integrity... done (0 conflicting)
Nothing to do.
***DONE***

And as you can see, the notice pertains only to the x86info package, which installs alongside the microcode update in order to be able to actually query which microcode is loaded, not to the microcode package itself.

Appreciate the clarification (still learning) I have loaded the Intel V1.1 of the plug in and still received the message about depreciation but not all the detail that you provided (appears to be an older and x86?)so going forward the microcode as long as it is v1.1 and not x86 will receive updates without special intervention?

Thank you all that replied

Mark

[nbca2]

As I am stubborn, I re-upgraded my system to version 25.7 (uninstalling the microcode-intel plugin first).
By reinstalling the microcode-intel plugin at the end of the update (successfully passed), I find the following output in the GUI:

Code Select Expand

The following 6 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
    cpu-microcode-intel: 20250512 [OPNsense]
    cpu-microcode-rc: 1.0_2 [OPNsense]
    libpci: 3.14.0 [OPNsense]
    os-cpu-microcode-intel: 1.1 [OPNsense]
    pciids: 20250621 [OPNsense]
    x86info: 1.31.s03_1 [OPNsense]

Number of packages to be installed: 6

The process will require 29 MiB more space.
21 MiB to be downloaded.
[1/6] Fetching x86info-1.31.s03_1.pkg: ......... done
[2/6] Fetching pciids-20250621.pkg: .......... done
[3/6] Fetching cpu-microcode-rc-1.0_2.pkg: . done
[4/6] Fetching libpci-3.14.0.pkg: ......... done
[5/6] Fetching cpu-microcode-intel-20250512.pkg: .......... done
[6/6] Fetching os-cpu-microcode-intel-1.1.pkg: . done
Checking integrity... done (0 conflicting)
[1/6] Installing pciids-20250621...
[1/6] Extracting pciids-20250621: ..... done
[2/6] Installing cpu-microcode-rc-1.0_2...
[2/6] Extracting cpu-microcode-rc-1.0_2: .... done
[3/6] Installing libpci-3.14.0...
[3/6] Extracting libpci-3.14.0: .......... done
[4/6] Installing x86info-1.31.s03_1...
[4/6] Extracting x86info-1.31.s03_1: ....... done
[5/6] Installing cpu-microcode-intel-20250512...
[5/6] Extracting cpu-microcode-intel-20250512: .......... done
[6/6] Installing os-cpu-microcode-intel-1.1...
[6/6] Extracting os-cpu-microcode-intel-1.1: .. done
Reloading firmware configuration
*** OPNsense\Kea\KeaDhcpv4 migration failed from 1.0.3 to 1.0.4, check log for details
Flushing all caches...done.
Writing firmware settings: FreeBSD OPNsense
Writing trust files...done.
Scanning /usr/share/certs/untrusted for certificates...
Scanning /usr/share/certs/trusted for certificates...
Scanning /usr/local/share/certs for certificates...
certctl: No changes to trust store were made.
Writing trust bundles...done.
Configuring login behaviour...done.
Configuring cron...done.
Configuring system logging...done.
=====
Message from cpu-microcode-rc-1.0_2:

--
This port includes an RC script, which is one of two methods to update
the CPU microcode on a FreeBSD system.
What does that mean?
*** OPNsense\Kea\KeaDhcpv4 migration failed from 1.0.3 to 1.0.4, check log for details

Why does it show up right after this line:
Reloading firmware configuration

which is the last line of text i can see on video before it crashes, when i try to upgrade from 25.1.12 to 25.7 with microcode plugin installed.

is there a correlation between the two situations or is it just random?




addendum:
i used kea in the past. In KEA DHCPv4 - Reservation was populated with reservation for the router ip. Deleted this line, the installation of the plugin didn't encour the error

Code Select Expand

......
[4/6] Extracting x86info-1.31.s03_1: ....... done
[5/6] Installing cpu-microcode-intel-20250512...
[5/6] Extracting cpu-microcode-intel-20250512: .......... done
[6/6] Installing os-cpu-microcode-intel-1.1...
[6/6] Extracting os-cpu-microcode-intel-1.1: .. done
Reloading firmware configuration
Flushing all caches...done.
Writing firmware settings: FreeBSD OPNsense
Writing trust files...done.
Scanning /usr/share/certs/untrusted for certificates...
Scanning /usr/share/certs/trusted for certificates...
Scanning /usr/local/share/certs for certificates...
certctl: No changes to trust store were made.
Writing trust bundles...done.
Configuring login behaviour...done.
Configuring cron...done.
Configuring system logging...done.
=====
Message from cpu-microcode-rc-1.0_2:

i tried to delete this line in the backup router and then perform the upgrade from 21.1.12 to 25.7, but it hungs always at Reloading firmware configuration

[nbca2]

Upgrade went well,
 however i've some problem of packet loss on the gateway of wireguard vpn.
 Unistalled microcode plugin, no more "loss" on wireguard vpn gateway.

i investigated the anomaly of the lost packages, it was due to vpn server side causes and not the opnsense router.

[turipriv]

My Protectli NUC upgraded with no issues - I have os-cpu-microcode-intel installed

What model do you have? I have a VP2420 and plan to upgrade during the weekend.

Sorry for delay in reply - I have a VP2410, so the older version of the one you have

Thank you for replying.

I still have to try the upgrade, as my last weekend was a mess.

Hopefully, I will try over the next one.

[nbca2]

update from 25.7 to 25.7.1, went well, no errors, with intel microcode plugin installed.

[turipriv]

Finally upgraded.

From 25.1.12 to 25.7, then from 25.7 to 25.7.1_1.

All went smoothly, no error, no crash, no kernel panic.

FWIW, I had the cpu-microcode plugin already installed before performing the upgrades.

My HW is stated in my signature.

Round of applause to the developers for the usually excellent job.