On a system that has been running just fine with 24.7 and 25.1 prior to the latest update.
I applied the latest updates and it throws an error when booting now:
CPU0:<ACPI CPU> on acpi0
The system uses DDR5 so it's relatively new hardware.
I reinstalled 25.1 and applied the update with the same result.
Also tried installing the latest FreeBSD on this system and applied updates and it boots fine.
Any hint at how I could track this issue down?
I'm going to try installing 25.1 and apply the updates on a different system and see what happens.
8 )
A picture of the screen might contain some clues...
You have disclosed so little information.
It seems specific to the particular system it was working on.
If I lock the base package and update it boots so it is something in the base package that has changed.
Using verbose boot it errors and stops at trying to initializing the uart on the motherboard, no actual serial port on the board but a uart header. I haven't tried attaching a serial adapter to the uart yet since I don't remember where I put them.
Right now I'm reading up on how to clone the repo and build the project to then try and find the base package and look through the code.
Thanks 8 )
I'm leaning towards this: After some back and forth today we are rolling back a console default change done in FreeBSD 14.2 that we do not think is necessary at this particular point in time. (https://forum.opnsense.org/index.php?topic=47125.0)
QuoteIn FreeBSD 14.2, the default console behavior is primarily driven by the vt(4) driver, which is now the recommended console driver, replacing the older syscons(4).
Figured it out.
After the update when it reboots hit <ESC> at the boot screen then enter
# set hint.uart.0.disabled=1
# set hint.uart.1.disabled=1
# boot
After it boots login and edit /boot/device.hints and change it like so then reboot to test the changes:
Quotehint.atkbdc.0.at="isa"
hint.atkbdc.0.port="0x060"
hint.atkbd.0.at="atkbdc"
hint.atkbd.0.irq="1"
hint.psm.0.at="atkbdc"
hint.psm.0.irq="12"
hint.sc.0.at="isa"
hint.sc.0.flags="0x100"
#hint.uart.0.at="isa"
#hint.uart.0.port="0x3F8"
#hint.uart.0.flags="0x10"
#hint.uart.0.irq="4"
#hint.uart.1.at="isa"
#hint.uart.1.port="0x2F8"
#hint.uart.1.irq="3"
hint.atrtc.0.at="isa"
hint.atrtc.0.port="0x70"
hint.atrtc.0.irq="8"
hint.attimer.0.at="isa"
hint.attimer.0.port="0x40"
hint.attimer.0.irq="0"
hint.acpi_throttle.0.disabled="1"
hint.p4tcc.0.disabled="1"
hint.uart.0.disabled="1"
hint.uart.1.disabled="1"
This worked for me and I learned a lot on this adventure!
8 )
Quote from: 7queue on June 07, 2025, 09:20:46 PM...
Using verbose boot it errors and stops at trying to initializing the uart on the motherboard, no actual serial port on the board but a uart header. I haven't tried attaching a serial adapter to the uart yet since I don't remember where I put them.
...
That's the kind of clue I was after. There have been several threads about these uart settings over the past few weeks.