19.1 r1 setup console stopped at booting

[winds]

我编辑了loader.conf文件，添加了kern.vty="sc"，然后它正常了
I edited the loader.conf file, added kern.vty="sc", and it worked fine.

Code Select Expand

#kern.vty
console="comconsole,vidconsole"
kern.vty="sc"

CPU:Intel(R) Celeron(R) CPU J1900 @ 1.99GHz (4 cores)

[weust]

It's better to change the console output in the WebGUI.
I can't check it right now, but it's somewhere under Configuration. General I believe.
Set it to VGA or perhaps EFI.

[franco]

Thanks for the hint. As with 11.0 to 11.1, 11.1 to 11.2 seems to change some parts around the use of vt vs. sc drivers... much to the surprise of the booting users. ;/


Cheers,
Franco

[weust]

It's what I have in bhyve too, no matter what console type I choose.
And that's still with 18.7.10.

[sjorge]

Just jumping in here, I am having issues as wel and have not had success with 19.1.r1 (or r2).

I run mine in bhyve with UEFI (under SmartOS) with only a serial port attached. I did notice some weirdness in 18.7.10 too.

vt=off, primary=serial => correct colors
vt=on, primary=serial => inncorrect colors on loader + double text? (I think vt is doing some sort of redirection)

As an experiment to get 19.1.r1 working I enabled the the vnc console...

vt=on, primary=efi => correct colors on EFI console, correct colors on serial during loader (nothing there after)
vt=on, primary=efi, secundary=serial => correct colors on EFI console, incorrect colors on serial during loader and double output
vt=on, primary=serial, secunmdary=efi => same as above
vt=off, primary=serial => correct colors on serial, nothing on efi console
vt=off, primaru=efi => correct colors on efi console
vt=off, primary=serial, secundary=efi => failed to boot
vt=off, primary=vga (for giggles) nothing worning about 'vidconsole' not available on EFI and serial, box hangs.

So it looks like on 18.7.10 atleast vt=on will results in output of loader on both serial and efi (and vga?) but once the kernel takes over it will only end up on the primary console. Not sure how different the behavior is on 19.1.r1 as I got nothing to work once we get past loader. I tried varius combos of vt=off/on and primary/secundary.

I did do all this via the webui so not sure if messing with loader.conf will give different results.

[sjorge]

I have a easier way to test it instead of taking down my main internet router...

I tried the following on the loader console:

set console="comconsole"
set kern.vty="sc"
show console
show kern.vty
boot

That show the correct variables but the it prints the following:
ooting...
Start @ 0xffffffff80316000 ...
EFI framebuffer information:
addr, size     0xc1000000, 0x1000000
dimensions     1024 x 768
stride         1024
masks          0x00ff0000, 0x0000ff00, 0x000000ff, 0xff000000

So it does still try to start the efi console? I do have both serial and efi console attached to this VM, so it will also grab the efi console it seems. Still hangs.

[peppersass]

I had this problem after upgrading from 18.7.4 to 19.1.1.

I'm using a ProtecLi FW4A-0 nano PC with a Lilliput monitor with HDMI input connected to the FW4A-0 VGA port through a VGA-to-HDMI adapter.

Per weust's advice, I went into the WebGUI interface, selected System...Settings...Administration, and unchecked "Use the virtual terminal driver (vt)". The primary monitor was already set to VGA.

Works now.

[robvh]

Fresh install of OPNsense-19.1-OpenSSL-vga-amd64.img from a USB stick on a real (J1900, UEFI) machine hangs at Booting ...

Luckily, I'm not the first victim (https://forum.opnsense.org/index.php?topic=11400.msg51534#msg51534 and https://twitter.com/opnsense/status/1091014083112062980) and of course I didn't have to read Release Update before, so after several attempts I was finally quick enough to hit 3 at the boot prompt.
Enter set kern.vty="sc" and now the boot process from USB continues.

After running installer, boot from the internal sata disk hangs again, at Booting ...
But now I'm prepared and change the "Console driver" option via the web interface (System-Settings-Administration).

I am impressed that OPNsense 19.1 picks up the config file (that I last maintained with 17.1) and comes up with all functions right off the bat.  I am not impressed with a comment that manual entry of "use the hardware console" was documented in the Release Update, so not a bug.