Date: Fri, 12 May 2023 01:20:45 +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: <252DD208-79A1-4F0A-8F98-B2F56770CD49@me.com> In-Reply-To: <CA%2BGqWgv8Ma9UB5mrXX=ChogmQBwUinYdE5hXDXYB1uWXgO2M-A@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>
next in thread | previous in thread | raw e-mail | index | archive | help
--Apple-Mail=_F350D337-8EBA-43F1-BD14-4E4E648D5862 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On 12. May 2023, at 01:09, Oleg Lelchuk <oleglelchuk@gmail.com> wrote: >=20 > kenv | grep screen produces this output: >=20 > 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).=20 rgds, toomas >=20 > On Thu, May 11, 2023 at 6:06=E2=80=AFPM Toomas Soome <tsoome@me.com = <mailto:tsoome@me.com>> wrote: >>=20 >>=20 >>> On 12. May 2023, at 00:57, Oleg Lelchuk <oleglelchuk@gmail.com = <mailto:oleglelchuk@gmail.com>> wrote: >>>=20 >>> kenv | grep boot shows me this: >>=20 >> Can you run kenv | grep screen ? in gfx mode, you should see = screen.depth, screen.height and screen.width >>=20 >> rgds, >> toomas >>=20 >>> =20 >>> 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" >>>=20 >>> The efivar command shows me: >>>=20 >>> efivar --device-path 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut >>> efivar: fetching 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut: No = such file or directory >>>=20 >>> On Thu, May 11, 2023 at 5:43=E2=80=AFPM Warner Losh <imp@bsdimp.com = <mailto:imp@bsdimp.com>> wrote: >>>>=20 >>>>=20 >>>> On Thu, May 11, 2023 at 3:21=E2=80=AFPM Toomas Soome <tsoome@me.com = <mailto:tsoome@me.com>> wrote: >>>>>=20 >>>>>=20 >>>>> > On 12. May 2023, at 00:11, Oleg Lelchuk <oleglelchuk@gmail.com = <mailto:oleglelchuk@gmail.com>> wrote: >>>>> >=20 >>>>> > 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. >>>>>=20 >>>>> 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 = configured to have serial console (redirection). >>>>=20 >>>> 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 >>>>=20 >>>> It should show something like: >>>> 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut >>>> : = PciRoot(0x2)/Pci(0x1,0x2)/Pci(0x0,0x0)/Pci(0x0,0x0)/AcpiAdr(0x80010100),/P= ciRoot(0x0)/Pci(0x14,0x3)/Serial(0x1)/Uart(115200,8,N,1)/UartFlowCtrl(Hard= ware)/VenVt100Plus() >>>> =20 >>>> if there's redirect or something like >>>>=20 >>>> 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut >>>> : = PciRoot(0x2)/Pci(0x1,0x2)/Pci(0x0,0x0)/Pci(0x0,0x0)/AcpiAdr(0x80010100) >>>>=20 >>>> if not. >>>>=20 >>>> Warner >>=20 --Apple-Mail=_F350D337-8EBA-43F1-BD14-4E4E648D5862 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 <html><head><meta http-equiv=3D"content-type" content=3D"text/html; = charset=3Dutf-8"></head><body style=3D"overflow-wrap: break-word; = -webkit-nbsp-mode: space; line-break: = after-white-space;"><br><div><br><blockquote type=3D"cite"><div>On 12. = May 2023, at 01:09, Oleg Lelchuk <oleglelchuk@gmail.com> = wrote:</div><br class=3D"Apple-interchange-newline"><div><div = dir=3D"ltr">kenv | grep screen produces this = output:<div><br></div><div>screensave_load=3D"NO"<br>screensave_name=3D"gr= een_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 =E2=80=98= gop get=E2=80=99 or =E2=80=98gop list=E2=80=99 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=3D"cite"><div><br><div = class=3D"gmail_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">tsoome@me.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><br><div><br><blockquote = type=3D"cite"><div>On 12. May 2023, at 00:57, Oleg Lelchuk <<a = href=3D"mailto:oleglelchuk@gmail.com" = target=3D"_blank">oleglelchuk@gmail.com</a>> = wrote:</div><br><div><div dir=3D"ltr" = style=3D"font-family:Helvetica;font-size:14px;font-style:normal;font-varia= nt-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text= -indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-d= ecoration: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><blo= ckquote type=3D"cite"><div><div dir=3D"ltr" = style=3D"font-family:Helvetica;font-size:14px;font-style:normal;font-varia= nt-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text= -indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-d= ecoration:none"><div> <br>acpi_dsdt_name=3D"/boot/acpi_dsdt.aml"<br>b= oot_verbose=3D"YES"<br>bootenv_autolist=3D"YES"<br>bootenvs[0]=3D"zfs:DESK= TOP/poudriere"<br>bootenvs_count=3D"1"<br>bootfile=3D"kernel"<br>cpu_micro= code_name=3D"/boot/firmware/ucode.bin"<br>entropy_cache_name=3D"/boot/entr= opy"<br>entropy_cache_type=3D"boot_entropy_cache"<br>if_re_name=3D"/boot/m= odules/if_re.ko"<br>kernel_path=3D"/boot/kernel"<br>kernelname=3D"/boot/ke= rnel/kernel"<br>loader_conf_dirs=3D"/boot/loader.conf.d"<br>module_path=3D= "/boot/kernel;/boot/modules;/boot/dtb;/boot/dtb/overlays"<br>nextboot_conf= =3D"/boot/nextboot.conf"<br>ram_blacklist_name=3D"/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=3D"font-family:Helvetica;font-size:14px;font-style:normal;font-varia= nt-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text= -indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-d= ecoration:none"><div class=3D"gmail_quote" = style=3D"font-family:Helvetica;font-size:14px;font-style:normal;font-varia= nt-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text= -indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-d= ecoration: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" = target=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 rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div = dir=3D"ltr"><br></div><br><div class=3D"gmail_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_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> </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 =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 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),/P= ciRoot(0x0)/Pci(0x14,0x3)/Serial(0x1)/Uart(115200,8,N,1)/UartFlowCtrl(Hard= ware)/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></body></html>= --Apple-Mail=_F350D337-8EBA-43F1-BD14-4E4E648D5862--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?252DD208-79A1-4F0A-8F98-B2F56770CD49>