"
Hi dbyte,
I tried recreating your behaviour on a bedrock with a V3C44 CPU.
I was able to install Opnsense using the set hw.uart.console="mm:0xfedc9000,rs:2,bd:1" variable.
however, it seems like for me the console is ttyu2 not ttyu0.
"FreeBSD/amd64 (OPNsense.localdomain) (ttyu2)"
for me, to get t persistently work without having to use the uart variable each time i just created the /boot/loader.conf.local fileand pasted the following two lines just as you suggested.
hw.uart.console="mm:0xfedc9000,rs:2"
console="efi"
And after a reboot i do not need to do anything now.
Also i do get a login prompt without modifying /usr/local/etc/inc/system.inc.
I used OPNsense 23.7 serial
Lastly, since you seem to be A LOT more experienced than me in the freeBSD world, two questions:
where did you get this console variable
you said: "Everything is working for me now, but not the right way to fix this problem".
what will be the real right way to fix this problem?
Thanks,
Lior
I tried recreating your behaviour on a bedrock with a V3C44 CPU.
I was able to install Opnsense using the set hw.uart.console="mm:0xfedc9000,rs:2,bd:1" variable.
however, it seems like for me the console is ttyu2 not ttyu0.
"FreeBSD/amd64 (OPNsense.localdomain) (ttyu2)"
for me, to get t persistently work without having to use the uart variable each time i just created the /boot/loader.conf.local fileand pasted the following two lines just as you suggested.
hw.uart.console="mm:0xfedc9000,rs:2"
console="efi"
And after a reboot i do not need to do anything now.
Also i do get a login prompt without modifying /usr/local/etc/inc/system.inc.
I used OPNsense 23.7 serial
Lastly, since you seem to be A LOT more experienced than me in the freeBSD world, two questions:
where did you get this console variable
you said: "Everything is working for me now, but not the right way to fix this problem".
what will be the real right way to fix this problem?
Thanks,
Lior
