So 3 times now I have tried to fix this. I first updated from 24.7, to 25.1 and after rebooting it never came back. It got stuck on the boot menu at the "atkbd0: GIANT LOCKED) line. Every time. So I did a full reinstall, wiped both of the drives in opnsense, installed them and reinstalled the 25.1 .img. once in the GUI I restored my backup config. Worked fine but I also noticed I was missing several plugins. So I went to check and it showed several in red. In order to install them I needed to update opnsense to 25.1.6, and yet again after a reboot the same exact thing happened. I am now reinstalling again and going to leave it until I can find out more. My interface setup is as follows. I have a 4 port Ethernet nic Bge 0 is wan, bge1 Is for my HomeLab, bge2 is GhostNetwork which goes out to the camper on our property, and bge 3 is for a TPlink AP. I use isc DHCP4 for my bridge which is was the original LAN interface. So now it is LAN_Bridge, I have had zero issues until this most recent update. I'm not sure if others are having problems but I would like to know what I should do. Do I need to change over to kea DHCP? If so how do I do so without having to setup everything if If using my backup to restore changes it back to isc, also maybe this is a bug of some sort. IDK but figured I should share what's going on. hp t740 thin client tpc-1036-tc is the device I'm using.
Hi!Try this
At boot loader prompt, choose to configure boot options (or similar wording) and try:
unset hint.uart.1.at
boot
If this works, you can permanently comment the
Code:
hint.uart.1.at="isa"
entry in /boot/device.hints
Hey sorry I just saw this!! I have already installed 25.1 again but the issue is when I update to 25.1.6 within the GUI after the fresh install and restoring my config, it does the boot issue. Is what you suggested still something I can do to prevent the update from breaking when I install it? I really would like to have ALL of my plugins back but can't due to it telling me I need to update the system.
Per https://forum.opnsense.org/index.php?msg=190822 (https://forum.opnsense.org/index.php?msg=190822), which you seem to be aware of, this is a FreeBSD issue on your HW. A process to get past it is described in this post.