Date: Fri, 12 May 2023 01:05:50 +0300 From: Toomas Soome <tsoome@me.com> To: Oleg Lelchuk <oleglelchuk@gmail.com> Cc: Warner Losh <imp@bsdimp.com>, freebsd-current@freebsd.org 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? Message-ID: <C82DFFC7-EE39-4A4C-9BEE-9F5B8956BC75@me.com> In-Reply-To: <CA%2BGqWgta6c=W7C8Cn3c2tEW%2BehkCGFFTW8W_JQKOKjygfxzW7g@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>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] > 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 <mailto:imp@bsdimp.com>> wrote: >> >> >> On Thu, May 11, 2023 at 3:21 PM Toomas Soome <tsoome@me.com <mailto:tsoome@me.com>> wrote: >>> >>> >>> > On 12. May 2023, at 00:11, Oleg Lelchuk <oleglelchuk@gmail.com <mailto: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 --] <html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><br><div><br><blockquote type="cite"><div>On 12. May 2023, at 00:57, Oleg Lelchuk <oleglelchuk@gmail.com> wrote:</div><br class="Apple-interchange-newline"><div><meta charset="UTF-8"><div dir="ltr" style="caret-color: rgb(0, 0, 0); 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; -webkit-text-stroke-width: 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="caret-color: rgb(0, 0, 0); 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; -webkit-text-stroke-width: 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="caret-color: rgb(0, 0, 0); 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; -webkit-text-stroke-width: 0px; text-decoration: none;"><div class="gmail_quote" style="caret-color: rgb(0, 0, 0); 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; -webkit-text-stroke-width: 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">imp@bsdimp.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-style: solid; border-left-color: 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-width: 1px; border-left-style: solid; border-left-color: 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 class="Apple-converted-space"> </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></body></html>help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?C82DFFC7-EE39-4A4C-9BEE-9F5B8956BC75>