Re: Boot stops at loader after build/install cycle

From: Marcin Cieslak <saper_at_saper.info>
Date: Thu, 30 Mar 2023 17:49:46 UTC
On Thu, 30 Mar 2023, Warner Losh wrote:

> On Thu, Mar 30, 2023 at 9:27 AM bob prohaska <fbsd@www.zefox.net> wrote:
>
> The sequence ending in R is indeed "report cursor location" so it's the
> result
> of resizewin not reading it and leaving that around maybe? Or something else
> sending the Query Cursor Location and then not reading it.
>
> https://www.cse.psu.edu/~kxc104/class/cmpen472/11f/hw/hw7/vt100ansi.htm

Yes, there is also one more sequence popping up in the boot screen,
right before "Loading kernel..."

Loading /boot/defaults/loader.conf
Loading /boot/defaults/loader.conf
Loading /boot/device.hints
Loading /boot/loader.conf
Loading /boot/loader.conf.local
[?25hcLoading kernel...
/boot/kernel/kernel text=0x2a8 text=0x8bcbf0 text=0x1f97ac data=0x1a6ac0 data=0x0+0x381000 syms=[0x8+0x11f6a0+0x8+0x14398a]
Loading configured modules...
/boot/entropy size=0x1000
/boot/kernel/umodem.ko text=0x2160 text=0x1440 data=0x6e8+0x10 syms=[0x8+0xf60+0x8+0xb7b]
loading required module 'ucom'
/boot/kernel/ucom.ko text=0x249f text=0x3840 data=0x8a0+0x858 syms=[0x8+0x1188+0x8+0xb1c]
/etc/hostid size=0x25

Hit [Enter] to boot immediately, or any other key for command prompt.


Type '?' for a list of commands, 'help' for more detailed help.
OK 6;176R


I have commented out loader.perform("efi-autoresizecons") in /boot/lua/loader.lua
so at least my console doesn't get cleared when booting (what for?)

Casually looking at EFI bootloader source I find that sometimes
we talk to the EFI "console" and let it do things :(

loader.efi(8) is not opimistic as well:

BUGS
      Systems that do not have a ConOut variable set are not conformant with
      the standard, and likely have unexpected results.

      Non-x86 serial console handling is even more confusing and less well
      documented.

      Sometimes when the serial port speed isn't set, 9600 is used.  Other
      times the result is typically 115200 since the speed remains unchanged
      from the default.

Looks like BOOT_PROMPT_123 macro is there for a reason!

Marcin