Date: Thu, 11 May 2023 17:57:55 -0400 From: Oleg Lelchuk <oleglelchuk@gmail.com> To: Warner Losh <imp@bsdimp.com> Cc: Toomas Soome <tsoome@me.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: <CA%2BGqWgta6c=W7C8Cn3c2tEW%2BehkCGFFTW8W_JQKOKjygfxzW7g@mail.gmail.com> In-Reply-To: <CANCZdfr5B%2BsFhF8Xdmd3WXRor7oVEn_YFpQ8nADn=xLigzAwgg@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>
next in thread | previous in thread | raw e-mail | index | archive | help
--00000000000057d84205fb72159c Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable kenv | grep boot shows me this: acpi_dsdt_name=3D"/boot/acpi_dsdt.aml" boot_verbose=3D"YES" bootenv_autolist=3D"YES" bootenvs[0]=3D"zfs:DESKTOP/poudriere" bootenvs_count=3D"1" bootfile=3D"kernel" cpu_microcode_name=3D"/boot/firmware/ucode.bin" entropy_cache_name=3D"/boot/entropy" entropy_cache_type=3D"boot_entropy_cache" if_re_name=3D"/boot/modules/if_re.ko" kernel_path=3D"/boot/kernel" kernelname=3D"/boot/kernel/kernel" loader_conf_dirs=3D"/boot/loader.conf.d" module_path=3D"/boot/kernel;/boot/modules;/boot/dtb;/boot/dtb/overlays" nextboot_conf=3D"/boot/nextboot.conf" ram_blacklist_name=3D"/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=E2=80=AFPM Warner Losh <imp@bsdimp.com> wrote: > > > On Thu, May 11, 2023 at 3:21=E2=80=AFPM Toomas Soome <tsoome@me.com> wrot= e: > >> >> >> > 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 boo= t >> loader want to display the graphical orb logo in its boot menu on an Asu= s >> Prime 7590-P motherboard? Is there something quirky about this particula= r >> 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 us= e >> =E2=80=9Ctext=E2=80=9D 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(Hard= ware)/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 > --00000000000057d84205fb72159c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">kenv | grep boot shows me this:<div>=C2=A0<br>acpi_dsdt_na= me=3D"/boot/acpi_dsdt.aml"<br>boot_verbose=3D"YES"<br>b= ootenv_autolist=3D"YES"<br>bootenvs[0]=3D"zfs:DESKTOP/poudri= ere"<br>bootenvs_count=3D"1"<br>bootfile=3D"kernel"= ;<br>cpu_microcode_name=3D"/boot/firmware/ucode.bin"<br>entropy_c= ache_name=3D"/boot/entropy"<br>entropy_cache_type=3D"boot_en= tropy_cache"<br>if_re_name=3D"/boot/modules/if_re.ko"<br>ker= nel_path=3D"/boot/kernel"<br>kernelname=3D"/boot/kernel/kern= el"<br>loader_conf_dirs=3D"/boot/loader.conf.d"<br>module_pa= th=3D"/boot/kernel;/boot/modules;/boot/dtb;/boot/dtb/overlays"<br= >nextboot_conf=3D"/boot/nextboot.conf"<br>ram_blacklist_name=3D&q= uot;/boot/blacklist.txt"<br></div><div><br></div><div>The efivar comma= nd shows me:</div><div><br></div><div>efivar --device-path 8be4df61-93ca-11= d2-aa0d-00e098032b8c-ConOut<br>efivar: fetching 8be4df61-93ca-11d2-aa0d-00e= 098032b8c-ConOut: No such file or directory<br></div></div><br><div class= =3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, May 11, 2023= at 5:43=E2=80=AFPM Warner Losh <<a href=3D"mailto:imp@bsdimp.com">imp@b= sdimp.com</a>> wrote:<br></div><blockquote class=3D"gmail_quote" style= =3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding= -left:1ex"><div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gm= ail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, May 11, 2023 at 3:= 21=E2=80=AFPM Toomas Soome <<a href=3D"mailto:tsoome@me.com" target=3D"_= blank">tsoome@me.com</a>> wrote:<br></div><blockquote class=3D"gmail_quo= te" style=3D"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=3D"mailto:oleglelc= huk@gmail.com" target=3D"_blank">oleglelchuk@gmail.com</a>> wrote:<br> > <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 particu= lar 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 pr= oblem 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 spa= ce to put the image on. Second one is that the screen is forced to use =E2= =80=9Ctext=E2=80=9D mode, which happens when system has configured to have = serial console (redirection).<br></blockquote><div><br></div><div>I think t= he 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 8be= 4df61-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(0x8= 0010100),/PciRoot(0x0)/Pci(0x14,0x3)/Serial(0x1)/Uart(115200,8,N,1)/UartFlo= wCtrl(Hardware)/VenVt100Plus()<br><div>=C2=A0</div><div>if there's redi= rect or something like</div><div><br></div><div>8be4df61-93ca-11d2-aa0d-00e= 098032b8c-ConOut<br>: PciRoot(0x2)/Pci(0x1,0x2)/Pci(0x0,0x0)/Pci(0x0,0x0)/A= cpiAdr(0x80010100)<br></div><div><br></div><div>if not.</div><div><br></div= ><div>Warner</div></div></div> </blockquote></div> --00000000000057d84205fb72159c--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2BGqWgta6c=W7C8Cn3c2tEW%2BehkCGFFTW8W_JQKOKjygfxzW7g>