OPNsense Forum
Archive => 17.1 Legacy Series => Topic started by: guest11051 on February 08, 2017, 04:03:24 am
-
I'm stuck on 16.7 till I can get past this hang. I've tried fresh installs and upgrades with the same results.
-
Hi CincinnatiKane,
I am sorry to hear that you are having some problems. Please provide as much information with regards of the steps taken, hardware used and anything else you feel relevant. This will ensure that someone has all the information required to help you with your issue.
-
Are not able to access the firewall at all, because that screen is not actually a hang, but due to an issue with certain hardware and EFI, where the terminal isn't properly displayed.
As Franco told me:
Try setting the "vt" driver and primary console to "efi". FreeBSD flipped their the default on 11.0, and the old defaults that worked for EFI are not working so well anymore (we kept our settings to minimise impact, ironic).
After I did the above my console was back to normal, so if you can somehow fix hit with the above you might actually see the real hang.
-
I'm using a Mac Mini (2012) with a thunderbolt PCI Ethernet adapter as my second NIC. I've been running pfSense and now OPNsense for years with no issues.
I'm not familiar with managing the settings or conf details on vt(4). Can you point me to a resource for changing to EFI mode? Or provide the CLI details here?
-
The most important question: is your GUI still there?
If yes, go to System: Settings: Administration, change your primary console to EFI, enable the VT driver checkbox and reboot.
Cheers,
Franco
-
Negative. The web-GUI never starts. Any way to escape into the boot loader and alter the vt(4) settings from the command line?
-
This looks like the same problem I was having. https://forum.opnsense.org/index.php?topic=4467.0 (https://forum.opnsense.org/index.php?topic=4467.0)
Go into your CMOS/BIOS and look for anything having to do with UEFI. You probably want to enable any kind of BIOS compatibility settings (in my setup they're referred to as "Legacy") and enable them. Unfortunately for you the fix was ultimately simple on my setup, I don't know if your mac mini will have the right compatibility settings.
-
And again, a shortcoming with using a Mac for this purpose - No BIOS to access. Pure UEFI. I wonder if a 3rd party bootloader like rEFIt would be of any help.
-
I really don't know why FreeBSD decided to change the old defaults to not boot anymore. I'm sure it was a fix for something, but breaking devices here is, er, suboptimal. ;)
Try this:
Escape to loader prompt (3)
Type: set kern.vty="vt"
Type: set console="efi"
Type: boot
Cheers,
Franco
-
Try this:
Escape to loader prompt (3)
Type: set kern.vty="vt"
Type: set console="efi"
Type: boot
Cheers,
Franco
FWIW, I gave this a try on my VM with the firmware type set to EFI. It ended up doing the line by line redraw of the screen, just like after my upgrade install >https://youtu.be/8UM0aBXRSkA?t=1m19s (https://youtu.be/8UM0aBXRSkA?t=1m19s). Perhaps the mac will have better luck.
-
I really don't know why FreeBSD decided to change the old defaults to not boot anymore. I'm sure it was a fix for something, but breaking devices here is, er, suboptimal. ;)
Try this:
Escape to loader prompt (3)
Type: set kern.vty="vt"
Type: set console="efi"
Type: boot
Cheers,
Franco
Fantastic! That worked like a charm, and I was able to make the change permanent in the GUI so that the system is now stable. Thank you, Franco!
-
I'm working on vt-based images now... it looks promising, something we should have done if we knew this would have happened. Hopefully it's useful for other projects out there not wanting to go through this problematic transition... :)
Cheers,
Franco