v19.1 installaton stuck at "booting..."

[dreamerman]

Hi, I was able to install the previous v18 without any problems. However, the latest v19.1 seems not to like my hardware (which have not changed since v18). My USB boots up with the menu and after loading scrips, it got stuck at the blue highlighted "booting...". I have disabled emulation 64 60 port and that got me through v18 installation. I tried to enable it but the only difference is that mu HW kept rebooting in an endless cycle after reaching "booting...". Any help or comment is appreciated.

[dreamerman]

Update: After a few attempts (changing USB sticks and re-download image) I gave up for now and tried the free Sophos XG Firewall Home Edition. Installation completed smoothly (maybe because this hardware is also used by Sophos as SG 115). I am going to give Sophos a test run until I find a solution to the booting issue.

Update: Took Sophos for a spin and seems ok. Many good features require subscription. I have not given up on opnsense yet so I installed v18.7 and like the last time it was successful. I completed all updates via console. I then upgraded to v19.1 from console and it got stuck at exactly the same point ie at blue booting. Sigh.

[franco]

It's a bug (or feature) in the base OS version 11.2. We're trying to find it, but we're not having much look so far.


Cheers,
Franco

[dreamerman]

Thanks Franco, I am currently using Sophos XG Firewall Home Edition but will revert back to Opnsense once this bug is ironed out.

[benibilme]

Hello,

I have the same issue.

As far as understand, this is a freebsd bug (feature).  Details are at this link https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172
Bug affects new generation intel celeron machines, and maybe machine with intel graphic card...
I tried to install pfsense and pfsense stuck at the very same point.

The same problem passes down to both  opnsense and pfsense. pfsense documantation covers this. freebsd bug has not been seem properly fixed but there are several work arounds as stated in bug discussions.

The one which seems easier and which I used is as follows.

During installation when you see the boot options press space bar  stop counter and select 3 to set boot options
Then type following

set kern.vty=sc
boot

After boot command, system boot  normal and passes the point where it stucks.

kern.vty="sc" must be manually added to /boot/loader.conf.local file. Otherwise it does not persist between boots. This file does not normally exist. To do that login as root after installation, you are given many selections. Select the shell option and create a new file at /boot/loader.conf.local with "kern.vty=sc" (without apostrophes)
After saving the file exit from the shell and reboot for test. I hope this helps.

[dreamerman]

Thanks benibilme. I am going to test Sophos XG Firewall Home since I have already installed it and running well on my hardware (without any glitches). Maybe I will try Opnsense in later versions when this bug is ironed-out.

[dreamerman]

I hope 19.1.4 will solve my problem, just downloaded it and will try later today.

[winds]

I think you can choose to boot from uefi

[dreamerman]

I downloaded OPNsense-19.1.4-OpenSSL-vga-amd64.img.bz2 and hash checked all ok. I am still getting the blue highlighted "booting..." error.

I can't boot under UEFI as I get this error message even before booting the OPNSENSE image "Image type x64 is not supported by this IA32 shell"

[fog]

Thanks benibilme. The same problem has an Atom E3845 board.
It works only with the " arround sc.
The default editor is ee. There ist no nano and vim.
Without editor from commandline:

Code Select Expand

echo 'kern.vty="sc"' > /boot/loader.conf.local

The keyboard mapping from the installer in /etc/rc.conf has no effect in the local console sc. It can be changed for the session with kbdmap.

You may want to set the keymap variable in /etc/rc.conf.local to the desired keymap file so that it will be automatically loaded when the system starts up. https://www.freebsd.org/cgi/man.cgi?query=sc&sektion=4

See the available keymaps: ls /usr/share/syscons/keymaps
and create /etc/rc.conf.local i.e.

Code Select Expand

echo 'keymap="german.cp850"' > /etc/rc.conf.local

[fog]

The console is only in VGA text mode 25x80.

I checked that my  Monitor support 1280x1024, see https://www.freebsd.org/doc/handbook/consoles.html#consoles-vidcontrol :

Code Select Expand

vidcontrol -i mode
vidcontrol MODE_283

and changed /boot/loader.conf.local

Code Select Expand

kern.vty="sc"
hint.sc.0.flags="0x180"
hint.sc.0.vesa_mode="283"