Date: Thu, 11 May 2023 18:49:07 -0400 From: Oleg Lelchuk <oleglelchuk@gmail.com> To: Toomas Soome <tsoome@me.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: <CA%2BGqWgtYV%2BkorSxBZinucZyH%2BZqKi4LXUP72cEmc5AJEgH8G=Q@mail.gmail.com> In-Reply-To: <CA%2BGqWgsRVzD4Qv10nyqh4LQiWfTH%2BP_%2BYF49xKSZHm1i19XVzQ@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>
next in thread | previous in thread | raw e-mail | index | archive | help
--0000000000006e37e905fb72cc8d Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Any, by the way, "show console" also shows "efi,comconsole", just like "kenv | grep efi" does. On Thu, May 11, 2023 at 6:40=E2=80=AFPM 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=3Dc16e08e5f324aa119c85e10eaabacbd= 2abdb40e0 > . > I get this output: > kenv | grep efi > console=3D"efi,comconsole" > efi-version=3D"2.70" > efi_com_port=3D"0" > efi_com_speed=3D"0" > efi_max_resolution=3D"1x1" > entropy_efi_seed=3D"YES" > loader.efi=3D"1" > > And in the attachment, you can see the output from the loader prompt. > > > On Thu, May 11, 2023 at 6:20=E2=80=AFPM Toomas Soome <tsoome@me.com> wrot= e: > >> >> >> On 12. May 2023, at 01:09, Oleg Lelchuk <oleglelchuk@gmail.com> wrote: >> >> kenv | grep screen produces this output: >> >> screensave_load=3D"NO" >> screensave_name=3D"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 =E2=80=98gop get=E2=80=99 or =E2=80=98gop list=E2= =80=99 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=E2=80=AFPM Toomas Soome <tsoome@me.com> wro= te: >> >>> >>> >>> 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=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> wr= ote: >>> >>>> >>>> >>>> On Thu, May 11, 2023 at 3:21=E2=80=AFPM Toomas Soome <tsoome@me.com> w= rote: >>>> >>>>> >>>>> >>>>> > 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 o= n 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 c= ause >>>>> 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 =E2=80=9Ctext=E2=80=9D mode, which happens when system has config= ured 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(H= ardware)/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 >>>> >>> >>> >> --0000000000006e37e905fb72cc8d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">Any, by the way, "show console" also shows "= ;efi,comconsole", just like "kenv | grep efi" does.</div><br= ><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, M= ay 11, 2023 at 6:40=E2=80=AFPM Oleg Lelchuk <<a href=3D"mailto:oleglelch= uk@gmail.com">oleglelchuk@gmail.com</a>> wrote:<br></div><blockquote cla= ss=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">My ESP partition has EF= I/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:=C2=A0<a h= ref=3D"https://cgit.freebsd.org/src/commit/?id=3Dc16e08e5f324aa119c85e10eaa= bacbd2abdb40e0" target=3D"_blank">https://cgit.freebsd.org/src/commit/?id= =3Dc16e08e5f324aa119c85e10eaabacbd2abdb40e0</a> .=C2=A0=C2=A0=C2=A0<div>I g= et this output:</div><div>kenv | grep efi<br>console=3D"efi,comconsole= "<br>efi-version=3D"2.70"<br>efi_com_port=3D"0"<br= >efi_com_speed=3D"0"<br>efi_max_resolution=3D"1x1"<br>e= ntropy_efi_seed=3D"YES"<br>loader.efi=3D"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=3D"gmail_quote"><div dir= =3D"ltr" class=3D"gmail_attr">On Thu, May 11, 2023 at 6:20=E2=80=AFPM Tooma= s Soome <<a href=3D"mailto:tsoome@me.com" target=3D"_blank">tsoome@me.co= m</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><br><div><br><blockquote type=3D"cite"><div>On 12. May 2023, at 01:09= , Oleg Lelchuk <<a href=3D"mailto:oleglelchuk@gmail.com" target=3D"_blan= k">oleglelchuk@gmail.com</a>> wrote:</div><br><div><div dir=3D"ltr">kenv= | grep screen produces this output:<div><br></div><div>screensave_load=3D&= quot;NO"<br>screensave_name=3D"green_saver"<br></div></div><= /div></blockquote><div><br></div><div>Yep, the screen is considered to be i= n text mode and only ascii art is used (see drawer.lua).</div><div><br></di= v><div>on loader prompt, does =E2=80=98gop get=E2=80=99 or =E2=80=98gop lis= t=E2=80=99 output anything?</div><div><br></div><div>if gop does output rea= sonable data, make sure your loader.efi on ESP is up to date; if you have n= o ConOut and ConOutDev variables set (by firmware), older loader did defaul= t to serial port, recent loader does default to efi,comconsole (see show co= nsole on loader prompt).=C2=A0</div><div><br></div><div>rgds,</div><div>too= mas</div><div><br></div><blockquote type=3D"cite"><div><br><div class=3D"gm= ail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, May 11, 2023 at 6:= 06=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"><div><br><div><br><blockquote type=3D"cite"><div>On 12.= May 2023, at 00:57, Oleg Lelchuk <<a href=3D"mailto:oleglelchuk@gmail.c= om" target=3D"_blank">oleglelchuk@gmail.com</a>> wrote:</div><br><div><d= iv dir=3D"ltr" style=3D"font-family:Helvetica;font-size:14px;font-style:nor= mal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-ali= gn:start;text-indent:0px;text-transform:none;white-space:normal;word-spacin= g:0px;text-decoration:none">kenv | grep boot shows me this:</div></div></bl= ockquote><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=3D"cite"><div><d= iv dir=3D"ltr" style=3D"font-family:Helvetica;font-size:14px;font-style:nor= mal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-ali= gn:start;text-indent:0px;text-transform:none;white-space:normal;word-spacin= g:0px;text-decoration:none"><div>=C2=A0<br>acpi_dsdt_name=3D"/boot/acp= i_dsdt.aml"<br>boot_verbose=3D"YES"<br>bootenv_autolist=3D&q= uot;YES"<br>bootenvs[0]=3D"zfs:DESKTOP/poudriere"<br>bootenv= s_count=3D"1"<br>bootfile=3D"kernel"<br>cpu_microcode_n= ame=3D"/boot/firmware/ucode.bin"<br>entropy_cache_name=3D"/b= oot/entropy"<br>entropy_cache_type=3D"boot_entropy_cache"<br= >if_re_name=3D"/boot/modules/if_re.ko"<br>kernel_path=3D"/bo= ot/kernel"<br>kernelname=3D"/boot/kernel/kernel"<br>loader_c= onf_dirs=3D"/boot/loader.conf.d"<br>module_path=3D"/boot/ker= nel;/boot/modules;/boot/dtb;/boot/dtb/overlays"<br>nextboot_conf=3D&qu= ot;/boot/nextboot.conf"<br>ram_blacklist_name=3D"/boot/blacklist.= txt"<br></div><div><br></div><div>The efivar command shows me:</div><d= iv><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=3D"font-family:Helvetica;f= ont-size:14px;font-style:normal;font-variant-caps:normal;font-weight:400;le= tter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;wh= ite-space:normal;word-spacing:0px;text-decoration:none"><div class=3D"gmail= _quote" style=3D"font-family:Helvetica;font-size:14px;font-style:normal;fon= t-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:star= t;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;t= ext-decoration:none"><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" t= arget=3D"_blank">imp@bsdimp.com</a>> wrote:<br></div><blockquote class= =3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg= b(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr"><br></di= v><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On T= hu, May 11, 2023 at 3:21=E2=80=AFPM Toomas Soome <<a href=3D"mailto:tsoo= me@me.com" target=3D"_blank">tsoome@me.com</a>> wrote:<br></div><blockqu= ote class=3D"gmail_quote" 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:oleglelchuk@gmail.com" target=3D"= _blank">oleglelchuk@gmail.com</a>> wrote:<br>><span>=C2=A0</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 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 re= asons. 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 =E2=80=9Ctext=E2=80=9D = mode, which happens when system has configured to have serial console (redi= rection).<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 provi= des:</div><div>(1) kenv (to make sure boot_xxx are set, maybe via a stray l= oader.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(0x= 0)/Pci(0x14,0x3)/Serial(0x1)/Uart(115200,8,N,1)/UartFlowCtrl(Hardware)/VenV= t100Plus()<br><div>=C2=A0</div><div>if there's redirect or something li= ke</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)<b= r></div><div><br></div><div>if not.</div><div><br></div><div>Warner</div></= div></div></blockquote></div></div></blockquote></div><br></div></blockquot= e></div> </div></blockquote></div><br></div></blockquote></div> </blockquote></div> --0000000000006e37e905fb72cc8d--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2BGqWgtYV%2BkorSxBZinucZyH%2BZqKi4LXUP72cEmc5AJEgH8G=Q>