Messages

I can also confirm '-w' works for opnsense 19.1.x and vanilla HBSD 11.
HBSD 12 does not need it, so I asume once opnsense is based on that we can drop it again.

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.

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.

I just switched and seems OK at first glance,

To be fair I am not using it as my main gateway (that is still an OpenBSD box) but infront of my virtual test env.
So far so good.

Sounds great, poke me on twitter (same handle) if you want some testing done.

I just installed and looking very promising, the interface is very refreshing.

Although I too was a bit disappointed with the lack of ZFS support.
On the surface ZFS support may seem like a lot of work for little benifit.

However proper boot environment support would be awesome (not sure freebsd has this though) (I mostly use OmniOS) It's great for versioning or even to test stuff and revert.

Additional benefits would be compression, lz4 especially adds little overhead but nice space savings. Imagine a caching http proxy, lots of small text files + lz4 would be awesome.

Replicating setups/backups would also be pretty cool, you could zfs send/receive certain snapshots or even datasets, e.g. http proxy cache on a seperate dataset, you can easily send it to a different install in one go with this.

I'm not much of a coder but I am willing to test if that would help.