Hi all,
I have a strange problem with boot.conf (set tty fb0) on an ARM VM running
under ESXi on a Raspberry Pi 4.
After installing 7.2, and fully syspatch'ed as of today, Nov 11, I write "set
tty fb0" at the boot prompt, or adding the command to /etc/boot.conf:
disks: sd0*
>> OpenBSD/arm64 BOOTAA64 1.12
boot> set tty fb0
switching console to fb0
>> OpenBSD/arm64 BOOTAA64 1.12
boot> bsd
the kernel outputs its progress to the console, and gets to this point:
Automatic boot in progress: starting file system checks.
/dev/sd0a (4434bf5864e19328.a): file system is clean; not checking
And hangs. It never moves beyond this.
If I don't use the command, the kernel output is not visible, blank screen, and
after a few seconds, a login prompt appears:
OpenBSD/arm64 (hostname.domain) (ttyC0)
login:
Note: The "set tty fb0" command works correctly during the install sequence of
7.2.
Why would the command cause the boot sequence to hang after checking the file
system? Bug?
John
