Messages

Your best bet, do a snapshot before upgrading next time.

How exactly is a snapshot going to help me with a physical box in a remote site? I would still need to go there if the system doesn't boot - which is this exact situation. If there was a way to automatically fall-back to old-good snapshot when default fails, that would be great. But when the system gets stuck during the boot and hard reboot is the only way to get another try...

This UART issue only affects really old systems. Architecture-wise, not referring to the date of purchase. Prime example: APU(2|4). These are *ancient* ;-)

It's an Intel N5105 based system and I am definitely the only one running this HW. I would even guess that the population of OPNsense users running similarly "ancient" model isn't small at all. Anyways this is really up to the OPNsense devs how they want to build the trust with their users. Breaking remote sites is not fun.

This was fixed in 25.1.6 BTW.

What exactly was fixed in 25.1.6? I updated to 25.1.8 yesterday and the system didn't boot because of the UART issue. Was your comment related to Protectli units only or the UART issue generally? Thanks!

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:

hint.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  )

Thank you man! This saved my ass today after I ran the update, rebooted and got stuck... Is there a plan to address the UART settings issue at scale or is everyone affected expected to fix it on their own? Asking as I have another firewall that is remote and pending the same set of updates. I can configure the "/boot/device.hints" file as suggested above. But will it boot 100%? Is the remote unit also affected? Is there a way to confirm it before the reboot? Thanks!