Re: Why doesn't the EFI boot loader want to display the graphical orb logo in its boot menu on an Asus Prime 7590-P motherboard?

From: Oleg Lelchuk <oleglelchuk_at_gmail.com>
Date: Thu, 11 May 2023 21:57:55 UTC
kenv | grep boot shows me this:

acpi_dsdt_name="/boot/acpi_dsdt.aml"
boot_verbose="YES"
bootenv_autolist="YES"
bootenvs[0]="zfs:DESKTOP/poudriere"
bootenvs_count="1"
bootfile="kernel"
cpu_microcode_name="/boot/firmware/ucode.bin"
entropy_cache_name="/boot/entropy"
entropy_cache_type="boot_entropy_cache"
if_re_name="/boot/modules/if_re.ko"
kernel_path="/boot/kernel"
kernelname="/boot/kernel/kernel"
loader_conf_dirs="/boot/loader.conf.d"
module_path="/boot/kernel;/boot/modules;/boot/dtb;/boot/dtb/overlays"
nextboot_conf="/boot/nextboot.conf"
ram_blacklist_name="/boot/blacklist.txt"

The efivar command shows me:

efivar --device-path 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut
efivar: fetching 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut: No such file
or directory

On Thu, May 11, 2023 at 5:43 PM Warner Losh <imp@bsdimp.com> wrote:

>
>
> On Thu, May 11, 2023 at 3:21 PM Toomas Soome <tsoome@me.com> wrote:
>
>>
>>
>> > On 12. May 2023, at 00:11, Oleg Lelchuk <oleglelchuk@gmail.com> wrote:
>> >
>> > Guys, there is something that I find puzzling. Why doesn't the EFI boot
>> loader want to display the graphical orb logo in its boot menu on an Asus
>> Prime 7590-P motherboard? Is there something quirky about this particular
>> motherboard that forces the FreeBSD EFI loader to display the old style
>> ASCII orb logo in its boot menu? Please explain to me the cause of this
>> problem and if possible, give me a solution to it.
>>
>> There can be two reasons. One is that resolution is low and there is no
>> space to put the image on. Second one is that the screen is forced to use
>> “text” mode, which happens when system has configured to have serial
>> console (redirection).
>>
>
> I think the latter isn't the case (based on earlier email with Oleg), but
> we can be sure if he provides:
> (1) kenv (to make sure boot_xxx are set, maybe via a stray loader.conf)
> (2) sudo efivar --device-path 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut
>
> It should show something like:
> 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut
> :
> PciRoot(0x2)/Pci(0x1,0x2)/Pci(0x0,0x0)/Pci(0x0,0x0)/AcpiAdr(0x80010100),/PciRoot(0x0)/Pci(0x14,0x3)/Serial(0x1)/Uart(115200,8,N,1)/UartFlowCtrl(Hardware)/VenVt100Plus()
>
> if there's redirect or something like
>
> 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut
> : PciRoot(0x2)/Pci(0x1,0x2)/Pci(0x0,0x0)/Pci(0x0,0x0)/AcpiAdr(0x80010100)
>
> if not.
>
> Warner
>