Boot problem with new appliance and new installation at EFI framebuffer

[0xDEADC0DE]

I have the same problem like this poster had 7 years ago.
https://forum.opnsense.org/Archive/17_1_Legacy_Series/17_1_images_will_not_boot

When I go into the boot options with 3, I can do

set kern.vty="vt"
boot

and it boots.
I've edited /boot/loader.conf
like described here: https://www.reddit.com/r/freebsd/comments/mdo0ma/following_a_tutorial/
the default with a new installation is sc.
When I change it to vt, will it survive upgrades? If not, I have to send back the new router and get another one.
Any suggestion on what else I can do? Yes, I could install with CSM and without UEFI, but that shouldn't be necessary.

Thanks

[0xDEADC0DE]

At https://www.reddit.com/r/freebsd/comments/mdo0ma/following_a_tutorial/ they say that vt is standard since FreeBSD 12. This is 6 years ago.

[cookiemonster]

perhaps https://forum.opnsense.org/index.php?topic=45568.0

[pfry]

[...]
When I change it to vt, will it survive upgrades? [...]

I had this issue: https://forum.opnsense.org/index.php?msg=190822. Using rc.conf.local does survive upgrades.

[Patrick M. Hausen]

Use the UI for tunables and they will survive upgrades and you will have at least some inline documentation.

[0xDEADC0DE]

I will try a bit more.
When I boot the new installation with

set kern.vty="vt"
boot

and import the old config, the tunables are not set on next boot.
I have to try to boot it manually again set kern.vty="vt" and see if it boots up then.

[0xDEADC0DE]

Okay, after a second reboot, it works now with every reboot.
As I thought, when you import the config, tunables are set after the next full boot.
Then it works.