---------- Forwarded message --------- From: Oleg Lelchuk <oleglelc...@gmail.com> Date: Thu, May 11, 2023 at 10:19 PM Subject: 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? To: Warner Losh <i...@bsdimp.com>
I see this output: efivar --device-path 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConIn 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConIn : PciRoot(0x0)/Pci(0x1f,0x0)/Acpi(PNP0303,0x0),/PciRoot(0x0)/Pci(0x14,0x0)/USB(0x2,0x0) On Thu, May 11, 2023 at 9:54 PM Warner Losh <i...@bsdimp.com> wrote: > No ConOut variable -> we assume the widest possible amount of hardware. > which is why you see efi comconsole as the console. > > Can you send me the output of > efivar --device-path 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConIn > > It should look like: > 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConIn > : > PciRoot(0x0)/Pci(0x1f,0x0)/Acpi(PNP0303,0x0),/PciRoot(0x0)/Pci(0x1f,0x0)/Acpi(PNP0303,0x1) > > I've been putting-off falling back to ConIn to determine the default > console device. I'd like > to collect a few more examples before I start. > > Warner > > On Thu, May 11, 2023 at 4:49 PM Oleg Lelchuk <oleglelc...@gmail.com> > wrote: > >> Any, by the way, "show console" also shows "efi,comconsole", just like >> "kenv | grep efi" does. >> >> On Thu, May 11, 2023 at 6:40 PM Oleg Lelchuk <oleglelc...@gmail.com> >> wrote: >> >>> My ESP partition has EFI/BOOT/BOOTX64.efi . I copied /boot/loader.efi to >>> EFI/BOOT/BOOTX64.efi when I compiled stand after this commit was added to >>> the main branch: >>> https://cgit.freebsd.org/src/commit/?id=c16e08e5f324aa119c85e10eaabacbd2abdb40e0 >>> . >>> I get this output: >>> kenv | grep efi >>> console="efi,comconsole" >>> efi-version="2.70" >>> efi_com_port="0" >>> efi_com_speed="0" >>> efi_max_resolution="1x1" >>> entropy_efi_seed="YES" >>> loader.efi="1" >>> >>> And in the attachment, you can see the output from the loader prompt. >>> >>> >>> On Thu, May 11, 2023 at 6:20 PM Toomas Soome <tso...@me.com> wrote: >>> >>>> >>>> >>>> On 12. May 2023, at 01:09, Oleg Lelchuk <oleglelc...@gmail.com> wrote: >>>> >>>> kenv | grep screen produces this output: >>>> >>>> screensave_load="NO" >>>> screensave_name="green_saver" >>>> >>>> >>>> Yep, the screen is considered to be in text mode and only ascii art is >>>> used (see drawer.lua). >>>> >>>> on loader prompt, does ‘gop get’ or ‘gop list’ output anything? >>>> >>>> if gop does output reasonable data, make sure your loader.efi on ESP is >>>> up to date; if you have no ConOut and ConOutDev variables set (by >>>> firmware), older loader did default to serial port, recent loader does >>>> default to efi,comconsole (see show console on loader prompt). >>>> >>>> rgds, >>>> toomas >>>> >>>> >>>> On Thu, May 11, 2023 at 6:06 PM Toomas Soome <tso...@me.com> wrote: >>>> >>>>> >>>>> >>>>> On 12. May 2023, at 00:57, Oleg Lelchuk <oleglelc...@gmail.com> wrote: >>>>> >>>>> kenv | grep boot shows me this: >>>>> >>>>> >>>>> Can you run kenv | grep screen ? in gfx mode, you should see >>>>> screen.depth, screen.height and screen.width >>>>> >>>>> rgds, >>>>> toomas >>>>> >>>>> >>>>> 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 <i...@bsdimp.com> wrote: >>>>> >>>>>> >>>>>> >>>>>> On Thu, May 11, 2023 at 3:21 PM Toomas Soome <tso...@me.com> wrote: >>>>>> >>>>>>> >>>>>>> >>>>>>> > On 12. May 2023, at 00:11, Oleg Lelchuk <oleglelc...@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 >>>>>> >>>>> >>>>> >>>>
