From nobody Thu May 11 22:49:07 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4QHRsX1QVvz4B7p8 for ; Thu, 11 May 2023 22:49:20 +0000 (UTC) (envelope-from oleglelchuk@gmail.com) Received: from mail-qk1-x72a.google.com (mail-qk1-x72a.google.com [IPv6:2607:f8b0:4864:20::72a]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QHRsW075cz4QSk for ; Thu, 11 May 2023 22:49:19 +0000 (UTC) (envelope-from oleglelchuk@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20221208 header.b=h9ZlfMYP; spf=pass (mx1.freebsd.org: domain of oleglelchuk@gmail.com designates 2607:f8b0:4864:20::72a as permitted sender) smtp.mailfrom=oleglelchuk@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-qk1-x72a.google.com with SMTP id af79cd13be357-7577a91cfd6so294500185a.3 for ; Thu, 11 May 2023 15:49:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1683845358; x=1686437358; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=lXOGe2t14E/NYGRxAHxUunslrb6eCydXN44Q/9kuZTk=; b=h9ZlfMYPUF0yibkFshmqDAIX9XnWv+VNrwlmMSBYetcO3HkfxIz4eyFTPuyit5JqIM Byyq2gmm5FYj8FMcEfnw/tYP4UebwNeFHaHNXS4geHAlEhv2PleFvLNdZ2ioWUC7BCIm pBDXA1ZWWdYQbbtpw4mgRDYtX+gXH8pOmZS+v8IFPwAm0GUFLNNe9kzslYBKYm3hbIhB KjWHMMXsHW4UadSmXDt8kCDlFOREOWsUWjulOmxQDkbvIHrycmdjJAiNcZcG/O5UwNW5 uJp4V7bvP78aPDeSiZxpEZOa9QRJCn4NvELdGKdRoPj7tR8iScyZWKqJmGUUrCT8sQma H2Gg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683845358; x=1686437358; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=lXOGe2t14E/NYGRxAHxUunslrb6eCydXN44Q/9kuZTk=; b=l2JNm9OK8Xns3lVShCF0C+WZPlDkFpjuAC082e0PHG4rObDXWGAyGrPpNiVuc/XFLH 9BnAY0fIvwdjdx1h+WFOBterfY1OVEQNH2PtZjVQsY70Pw+J9rkUbWy4fCLyqew4f6a3 AAaVAFjH8MSm5zZQUdPzFSzRYQACxK7tihhwrzmeFAFE0gjsAhQ8QOYYQWe4Q0XHblIY 6QP+X9+yoFeuoRJDgo9Xpe1qVLWaBVyjRMVyFw9FwduQjQ2n+6nLytZPjGVGwHCGmQ4u dTkUQ9nTO39bwdCPIF7z13/cSAuz799SJHd2CWnUBzph79hqEqAVPmvm0npqfElR2hlm Sf/Q== X-Gm-Message-State: AC+VfDzyxmVzbBEm8dxxX8HNJImPZWHQmR84B3GJGI3Qs62mUYPsfGg7 fiS+QqXlZ5xK9soGjZfc2Kg52kCI7kPy8WVX84bj5S+X+Tg= X-Google-Smtp-Source: ACHHUZ6149wpW1BjvF0fFyr87VxpOdlTBoSyGu9+mFWcJtH0LX34X8Gnz98NYkvRRkN0RmSyeeaczIpV5nLDCwrNtIY= X-Received: by 2002:a05:6214:1cc4:b0:5e9:2bad:c8fa with SMTP id g4-20020a0562141cc400b005e92badc8famr34480045qvd.33.1683845358171; Thu, 11 May 2023 15:49:18 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: <3B658415-3AD0-4E8B-8CBE-F13FA70CBDC8@me.com> <252DD208-79A1-4F0A-8F98-B2F56770CD49@me.com> In-Reply-To: From: Oleg Lelchuk Date: Thu, 11 May 2023 18:49:07 -0400 Message-ID: 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: Toomas Soome Cc: Warner Losh , freebsd-current@freebsd.org Content-Type: multipart/alternative; boundary="0000000000006e37e905fb72cc8d" X-Spamd-Result: default: False [-2.92 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.92)[-0.922]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20221208]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::72a:from]; ARC_NA(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; DKIM_TRACE(0.00)[gmail.com:+]; MID_RHS_MATCH_FROMTLD(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_TO(0.00)[me.com]; RCVD_TLS_LAST(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FREEMAIL_ENVFROM(0.00)[gmail.com]; RCVD_COUNT_TWO(0.00)[2] X-Rspamd-Queue-Id: 4QHRsW075cz4QSk X-Spamd-Bar: -- X-ThisMailContainsUnwantedMimeParts: N --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 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 wrot= e: > >> >> >> On 12. May 2023, at 01:09, Oleg Lelchuk 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 wro= te: >> >>> >>> >>> On 12. May 2023, at 00:57, Oleg Lelchuk 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 wr= ote: >>> >>>> >>>> >>>> On Thu, May 11, 2023 at 3:21=E2=80=AFPM Toomas Soome w= rote: >>>> >>>>> >>>>> >>>>> > On 12. May 2023, at 00:11, Oleg Lelchuk >>>>> 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
Any, by the way, "show console" also shows "= ;efi,comconsole", just like "kenv | grep efi" does.
On Thu, M= ay 11, 2023 at 6:40=E2=80=AFPM Oleg Lelchuk <oleglelchuk@gmail.com> wrote:
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=A0https://cgit.freebsd.org/src/commit/?id= =3Dc16e08e5f324aa119c85e10eaabacbd2abdb40e0 .=C2=A0=C2=A0=C2=A0
I g= et 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"
e= ntropy_efi_seed=3D"YES"
loader.efi=3D"1"
<= br>
And in the attachment, you can see the output from the loader= prompt.


On Thu, May 11, 2023 at 6:20=E2=80=AFPM Tooma= s Soome <tsoome@me.co= m> wrote:


On 12. May 2023, at 01:09= , Oleg Lelchuk <oleglelchuk@gmail.com> wrote:

kenv= | grep screen produces this output:

screensave_load=3D&= quot;NO"
screensave_name=3D"green_saver"
<= /div>

Yep, the screen is considered to be i= n 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 lis= t=E2=80=99 output anything?

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

rgds,
too= mas


On Thu, May 11, 2023 at 6:= 06=E2=80=AFPM 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

<= /div>
rgds,
toomas

=C2=A0
acpi_dsdt_name=3D"/boot/acp= i_dsdt.aml"
boot_verbose=3D"YES"
bootenv_autolist=3D&q= uot;YES"
bootenvs[0]=3D"zfs:DESKTOP/poudriere"
bootenv= s_count=3D"1"
bootfile=3D"kernel"
cpu_microcode_n= ame=3D"/boot/firmware/ucode.bin"
entropy_cache_name=3D"/b= oot/entropy"
entropy_cache_type=3D"boot_entropy_cache"if_re_name=3D"/boot/modules/if_re.ko"
kernel_path=3D"/bo= ot/kernel"
kernelname=3D"/boot/kernel/kernel"
loader_c= onf_dirs=3D"/boot/loader.conf.d"
module_path=3D"/boot/ker= nel;/boot/modules;/boot/dtb;/boot/dtb/overlays"
nextboot_conf=3D&qu= ot;/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 T= hu, May 11, 2023 at 3:21=E2=80=AFPM Toomas Soome <tsoome@me.com> wrote:


> On 12. May 2023, at = 00:11, Oleg Lelchuk <oleglelchuk@gmail.com> wrote:
>=C2=A0
= > 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.

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).

I think the latter isn't = the case (based on earlier email with Oleg), but we can be sure if he provi= des:
(1) kenv (to make sure boot_xxx are set, maybe via a stray l= oader.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(0x= 0)/Pci(0x14,0x3)/Serial(0x1)/Uart(115200,8,N,1)/UartFlowCtrl(Hardware)/VenV= t100Plus()
=C2=A0
if there's redirect or something li= ke

8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut
= : PciRoot(0x2)/Pci(0x1,0x2)/Pci(0x0,0x0)/Pci(0x0,0x0)/AcpiAdr(0x80010100)

if not.

Warner


--0000000000006e37e905fb72cc8d--