6100 Firmware 03.00.00.03t-uc-126
-
Hmm, nope. 18 is the latest microcontroller code version.
[25.07-RC] [admin@6100.stevew.lan]/root: ls -ls /usr/local/share/pfSense-pkg-Netgate_Firmware_Upgrade/roms/ total 10695 817 -rw-r--r-- 1 root wheel 8388608 Nov 12 2024 ADI_DFF2-01.00.00.17-nodebug.rom 3257 -rw-r--r-- 1 root wheel 16777216 Nov 12 2024 ADI_PLCC-01.00.00.20.bin 1073 -rw-r--r-- 1 root wheel 16777216 Nov 12 2024 ADI_RCC-01.00.00.18-nodebug-16m.rom 817 -rw-r--r-- 1 root wheel 8388608 Nov 12 2024 ADI_RCCVE-01.00.00.17-nodebug.rom 2361 -rw-r--r-- 1 root wheel 8388608 Nov 12 2024 CORDOBA-03.00.00.01-2Ct-uc-15.fd 2373 -rw-r--r-- 1 root wheel 8388608 Nov 12 2024 CORDOBA-03.00.00.03t-uc-18.fd[25.07-RC][admin@6100.stevew.lan]/root: sysctl dev.cordbuc.0.version dev.cordbuc.0.version: 18Try a full power cycle if you haven't already.
-
Thanks Steve, the full power cycle / cold boot got things sorted:


-
Nice. Weird though.

-
@stephenw10 Updated to 25.11.a.20250916.0600 yesterday and noticed this came up again (little different this time, now it says
03.00.00.03t-uc-254)


Cold boot fixed it again. Strange.
-
Hmm, if you see it again check the version reported in the sysctl:
[25.07.1-RELEASE][admin@6100.stevew.lan]/root: sysctl dev.cordbuc.0.version dev.cordbuc.0.version: 18 -
@stephenw10 Yeah, damn, I had that in my notes from the last time, but I forgot. I'll try to remember next time!
-
It pretty much has to be reporting incorrectly there since that's what the gui uses but it would be good to confirm.
-
@stephenw10 fast forward a bit! just had this happen again on a different 6100 after an upgrade from 25.07 → 26.03.1. Haven't rebooted yet in case there are any other commands you want me to run. Things seem to be working fine.


from the console:
# sysctl dev.cordbuc.0.version dev.cordbuc.0.version: 190# ls -ls /usr/local/share/pfSense-pkg-Netgate_Firmware_Upgrade/roms/ total 10695 817 -rw-r--r-- 1 root wheel 8388608 May 15 19:08 ADI_DFF2-01.00.00.17-nodebug.rom 3257 -rw-r--r-- 1 root wheel 16777216 May 15 19:08 ADI_PLCC-01.00.00.20.bin 1073 -rw-r--r-- 1 root wheel 16777216 May 15 19:08 ADI_RCC-01.00.00.18-nodebug-16m.rom 817 -rw-r--r-- 1 root wheel 8388608 May 15 19:08 ADI_RCCVE-01.00.00.17-nodebug.rom 2361 -rw-r--r-- 1 root wheel 8388608 May 15 19:08 CORDOBA-03.00.00.01-2Ct-uc-15.fd 2373 -rw-r--r-- 1 root wheel 8388608 May 15 19:08 CORDOBA-03.00.00.03t-uc-18.fd# sysctl -a | grep -Ei 'cordob|cordb' Netgate Cordoba GPIO Driver 0.4 loaded cordbuc0: <Netgate Cordoba IO controller> at port 0x800 on isa0 gpio0: <Cordoba uC GPIO controller> on cordbuc0 dev.gpio.0.%parent: cordbuc0 dev.gpio.0.%desc: Cordoba uC GPIO controller dev.cordbuc.0.version: 190 dev.cordbuc.0.%iommu: dev.cordbuc.0.%parent: isa0 dev.cordbuc.0.%pnpinfo: dev.cordbuc.0.%location: dev.cordbuc.0.%driver: cordbuc dev.cordbuc.0.%desc: Netgate Cordoba IO controller dev.cordbuc.%parent: -
Hmm, well that confirms the driver is reporting incorrectly.
If you reboot without power cycling does it still show that?
If you then power cycle does it show the expected value?
-
@stephenw10 thanks I will check tonight when everyone goes home
-
@stephenw10 update: after warm reboot, still reporting
03.00.00.03t-uc-190I'm not onsite to do a cold reboot, but will ask them to do it on Monday. I assume that will clear whatever this strange condition is.
-
Hmm, interesting. That implies it's actually the microcontroller reporting that value to the driver.
