Date: Thu, 11 May 2023 22:21:52 -0400 From: Oleg Lelchuk <oleglelchuk@gmail.com> To: freebsd-current@freebsd.org Subject: Fwd: 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? Message-ID: <CA%2BGqWgtG=PXxBrZDNWK-tJfO9fvgDLS8SwTYNTSw7vE1z9FmyA@mail.gmail.com> In-Reply-To: <CA%2BGqWgv4xX3hvtGGuubROZMkgHFHN854ocys7zyLf=j0rOs7SQ@mail.gmail.com> References: <CA%2BGqWgudMq%2BeV5OJzuC_zR1Osdrak70PmOpFJqLMk3aDE0wy8w@mail.gmail.com> <3B658415-3AD0-4E8B-8CBE-F13FA70CBDC8@me.com> <CANCZdfr5B%2BsFhF8Xdmd3WXRor7oVEn_YFpQ8nADn=xLigzAwgg@mail.gmail.com> <CA%2BGqWgta6c=W7C8Cn3c2tEW%2BehkCGFFTW8W_JQKOKjygfxzW7g@mail.gmail.com> <C82DFFC7-EE39-4A4C-9BEE-9F5B8956BC75@me.com> <CA%2BGqWgv8Ma9UB5mrXX=ChogmQBwUinYdE5hXDXYB1uWXgO2M-A@mail.gmail.com> <252DD208-79A1-4F0A-8F98-B2F56770CD49@me.com> <CA%2BGqWgsRVzD4Qv10nyqh4LQiWfTH%2BP_%2BYF49xKSZHm1i19XVzQ@mail.gmail.com> <CA%2BGqWgtYV%2BkorSxBZinucZyH%2BZqKi4LXUP72cEmc5AJEgH8G=Q@mail.gmail.com> <CANCZdfoomgi2oVrDXY2asvwsR8%2BrZSppFKvLwMxWACeBi8TJwA@mail.gmail.com> <CA%2BGqWgv4xX3hvtGGuubROZMkgHFHN854ocys7zyLf=j0rOs7SQ@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] ---------- Forwarded message --------- From: Oleg Lelchuk <oleglelchuk@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 <imp@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 <imp@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 <oleglelchuk@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 <oleglelchuk@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 <tsoome@me.com> wrote: >>> >>>> >>>> >>>> On 12. May 2023, at 01:09, Oleg Lelchuk <oleglelchuk@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 <tsoome@me.com> wrote: >>>> >>>>> >>>>> >>>>> On 12. May 2023, at 00:57, Oleg Lelchuk <oleglelchuk@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 <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 >>>>>> >>>>> >>>>> >>>> [-- Attachment #2 --] <div dir="ltr"><br><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">---------- Forwarded message ---------<br>From: <strong class="gmail_sendername" dir="auto">Oleg Lelchuk</strong> <span dir="auto"><<a href="mailto:oleglelchuk@gmail.com">oleglelchuk@gmail.com</a>></span><br>Date: Thu, May 11, 2023 at 10:19 PM<br>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?<br>To: Warner Losh <<a href="mailto:imp@bsdimp.com">imp@bsdimp.com</a>><br></div><br><br><div dir="ltr">I see this output:<div>efivar --device-path 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConIn<br>8be4df61-93ca-11d2-aa0d-00e098032b8c-ConIn<br>: PciRoot(0x0)/Pci(0x1f,0x0)/Acpi(PNP0303,0x0),/PciRoot(0x0)/Pci(0x14,0x0)/USB(0x2,0x0)<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, May 11, 2023 at 9:54 PM Warner Losh <<a href="mailto:imp@bsdimp.com" target="_blank">imp@bsdimp.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>No ConOut variable -> we assume the widest possible amount of hardware. which is why you see efi comconsole as the console.</div><div><br></div><div>Can you send me the output of</div><div>efivar --device-path 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConIn</div><div><br></div><div>It should look like:</div><div>8be4df61-93ca-11d2-aa0d-00e098032b8c-ConIn<br>: PciRoot(0x0)/Pci(0x1f,0x0)/Acpi(PNP0303,0x0),/PciRoot(0x0)/Pci(0x1f,0x0)/Acpi(PNP0303,0x1)</div><div><br></div><div>I've been putting-off falling back to ConIn to determine the default console device. I'd like</div><div>to collect a few more examples before I start.<br></div><div><br></div><div>Warner<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, May 11, 2023 at 4:49 PM Oleg Lelchuk <<a href="mailto:oleglelchuk@gmail.com" target="_blank">oleglelchuk@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Any, by the way, "show console" also shows "efi,comconsole", just like "kenv | grep efi" does.</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, May 11, 2023 at 6:40 PM Oleg Lelchuk <<a href="mailto:oleglelchuk@gmail.com" target="_blank">oleglelchuk@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">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: <a href="https://cgit.freebsd.org/src/commit/?id=c16e08e5f324aa119c85e10eaabacbd2abdb40e0" target="_blank">https://cgit.freebsd.org/src/commit/?id=c16e08e5f324aa119c85e10eaabacbd2abdb40e0</a>; . <div>I get this output:</div><div>kenv | grep efi<br>console="efi,comconsole"<br>efi-version="2.70"<br>efi_com_port="0"<br>efi_com_speed="0"<br>efi_max_resolution="1x1"<br>entropy_efi_seed="YES"<br>loader.efi="1"</div><div><br></div><div>And in the attachment, you can see the output from the loader prompt.</div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, May 11, 2023 at 6:20 PM Toomas Soome <<a href="mailto:tsoome@me.com" target="_blank">tsoome@me.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><br><div><br><blockquote type="cite"><div>On 12. May 2023, at 01:09, Oleg Lelchuk <<a href="mailto:oleglelchuk@gmail.com" target="_blank">oleglelchuk@gmail.com</a>> wrote:</div><br><div><div dir="ltr">kenv | grep screen produces this output:<div><br></div><div>screensave_load="NO"<br>screensave_name="green_saver"<br></div></div></div></blockquote><div><br></div><div>Yep, the screen is considered to be in text mode and only ascii art is used (see drawer.lua).</div><div><br></div><div>on loader prompt, does ‘gop get’ or ‘gop list’ output anything?</div><div><br></div><div>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). </div><div><br></div><div>rgds,</div><div>toomas</div><div><br></div><blockquote type="cite"><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, May 11, 2023 at 6:06 PM Toomas Soome <<a href="mailto:tsoome@me.com" target="_blank">tsoome@me.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><br><div><br><blockquote type="cite"><div>On 12. May 2023, at 00:57, Oleg Lelchuk <<a href="mailto:oleglelchuk@gmail.com" target="_blank">oleglelchuk@gmail.com</a>> wrote:</div><br><div><div dir="ltr" style="font-family:Helvetica;font-size:14px;font-style:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none">kenv | grep boot shows me this:</div></div></blockquote><div><br></div><div>Can you run kenv | grep screen ? in gfx mode, you should see screen.depth, screen.height and screen.width</div><div><br></div><div>rgds,</div><div>toomas</div><br><blockquote type="cite"><div><div dir="ltr" style="font-family:Helvetica;font-size:14px;font-style:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none"><div> <br>acpi_dsdt_name="/boot/acpi_dsdt.aml"<br>boot_verbose="YES"<br>bootenv_autolist="YES"<br>bootenvs[0]="zfs:DESKTOP/poudriere"<br>bootenvs_count="1"<br>bootfile="kernel"<br>cpu_microcode_name="/boot/firmware/ucode.bin"<br>entropy_cache_name="/boot/entropy"<br>entropy_cache_type="boot_entropy_cache"<br>if_re_name="/boot/modules/if_re.ko"<br>kernel_path="/boot/kernel"<br>kernelname="/boot/kernel/kernel"<br>loader_conf_dirs="/boot/loader.conf.d"<br>module_path="/boot/kernel;/boot/modules;/boot/dtb;/boot/dtb/overlays"<br>nextboot_conf="/boot/nextboot.conf"<br>ram_blacklist_name="/boot/blacklist.txt"<br></div><div><br></div><div>The efivar command shows me:</div><div><br></div><div>efivar --device-path 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut<br>efivar: fetching 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut: No such file or directory<br></div></div><br style="font-family:Helvetica;font-size:14px;font-style:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none"><div class="gmail_quote" style="font-family:Helvetica;font-size:14px;font-style:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none"><div dir="ltr" class="gmail_attr">On Thu, May 11, 2023 at 5:43 PM Warner Losh <<a href="mailto:imp@bsdimp.com" target="_blank">imp@bsdimp.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, May 11, 2023 at 3:21 PM Toomas Soome <<a href="mailto:tsoome@me.com" target="_blank">tsoome@me.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br><br>> On 12. May 2023, at 00:11, Oleg Lelchuk <<a href="mailto:oleglelchuk@gmail.com" target="_blank">oleglelchuk@gmail.com</a>> wrote:<br>><span> </span><br>> 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.<br><br>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).<br></blockquote><div><br></div><div>I think the latter isn't the case (based on earlier email with Oleg), but we can be sure if he provides:</div><div>(1) kenv (to make sure boot_xxx are set, maybe via a stray loader.conf)</div><div>(2) sudo efivar --device-path 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut</div><div><br></div><div>It should show something like:</div><div>8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut<br></div>: 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()<br><div> </div><div>if there's redirect or something like</div><div><br></div><div>8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut<br>: PciRoot(0x2)/Pci(0x1,0x2)/Pci(0x0,0x0)/Pci(0x0,0x0)/AcpiAdr(0x80010100)<br></div><div><br></div><div>if not.</div><div><br></div><div>Warner</div></div></div></blockquote></div></div></blockquote></div><br></div></blockquote></div> </div></blockquote></div><br></div></blockquote></div> </blockquote></div> </blockquote></div> </blockquote></div> </div></div>help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2BGqWgtG=PXxBrZDNWK-tJfO9fvgDLS8SwTYNTSw7vE1z9FmyA>