From nobody Fri May 12 01:54:20 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 4QHWzD0S5nz4BLCl for ; Fri, 12 May 2023 01:54:32 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ej1-x62c.google.com (mail-ej1-x62c.google.com [IPv6:2a00:1450:4864:20::62c]) (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 4QHWzC65KWz3pY7 for ; Fri, 12 May 2023 01:54:31 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ej1-x62c.google.com with SMTP id a640c23a62f3a-956ff2399b1so1769711066b.3 for ; Thu, 11 May 2023 18:54:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20221208.gappssmtp.com; s=20221208; t=1683856468; x=1686448468; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=8NdwP2oAusSqiBd87qouNIbkn+u2L3vqRUFv+7K12hM=; b=Gwo1/qjygUG0DhnaqsY7H7pK7WtteUUJDvl13GaVnJP6crDxDCcrCHXn0i+xuZf4Bg l+uX1H0UI055mEnajspnbYqbN7AJlK9O8xrZaHxT5a26pEXW6wgS420rVWFRSVpRBRMp lIO/zQpFDrzqfLkQOVYXSetpqCnd/SXrtINse7oOdAdOUXP1DAY7gH4JVV/wpYuo/0Q4 bfbLZdKj3QtWJ8PxO+INOpe/4Z9kSMqhDB07E4gRq3+twMjNZL3FW0uc/IBHz4tSEDFH kNo9RT0VILSWMTVoqPG7v1awInJzON7ZOp8vFRmIeppsSN1bShzVrlZHVkP/QYo22NEN Ppiw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683856468; x=1686448468; 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=8NdwP2oAusSqiBd87qouNIbkn+u2L3vqRUFv+7K12hM=; b=C+ysf9DjRFxhmai3XcQG10XV+QoLbGlDfl6iHkuIh/L1mDAP2mrZcILVSUlY8k079w rCsP6coWVSppdCWgKM15WcNHVa2h2neZX00pMbL8nBTNYzny3d2/Q4RAEpG0dFat15/r FowMOoR17Lt/g+yUCHX+zMDb6YvikQe3jj6nmG0jRzbr84c5OY68hcFUdFGXIrlKzrLb 5P5n2nkD/c7oROV95ddZv1qQrX82i0k2PMXzDvNLBAbxOLHnNA8mjLVIAts0uebmn2xS Rk583hZ0dx0UIoB4a/QTSnVR6O85S04Uhm9/AOEX0inPQtrtCJDU98a9zVmQ0XwnnwhJ r/Fw== X-Gm-Message-State: AC+VfDwh9bCm/Jl0kJmT6eRMjEm7ZpfeqYj9b4jxbtfUNHvUk44yB+w3 Ry3nH3OqClyySn9ypCa69dPaoRVDKHiCZnG8fLX18Q== X-Google-Smtp-Source: ACHHUZ7rz5y24lJmmGJFBKkuOMPSUi1tBTVHiTCA5M+gJps1YnP3A9lLqXztX3UGAgJ8uoVwJNo/Vf8OVwcBnFlVtu0= X-Received: by 2002:a17:907:9454:b0:953:291a:6705 with SMTP id dl20-20020a170907945400b00953291a6705mr21458912ejc.17.1683856468446; Thu, 11 May 2023 18:54:28 -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: Warner Losh Date: Thu, 11 May 2023 19:54:20 -0600 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: Oleg Lelchuk Cc: Toomas Soome , freebsd-current@freebsd.org Content-Type: multipart/alternative; boundary="000000000000a79fa805fb75627d" X-Rspamd-Queue-Id: 4QHWzC65KWz3pY7 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --000000000000a79fa805fb75627d Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable No ConOut variable -> we assume the widest possible amount of hardware. which is why you see efi comconsole as the console. Can you send me the output of efivar --device-path 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConIn It should look like: 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConIn : PciRoot(0x0)/Pci(0x1f,0x0)/Acpi(PNP0303,0x0),/PciRoot(0x0)/Pci(0x1f,0x0)/Ac= pi(PNP0303,0x1) I've been putting-off falling back to ConIn to determine the default console device. I'd like to collect a few more examples before I start. Warner On Thu, May 11, 2023 at 4:49=E2=80=AFPM Oleg Lelchuk wrote: > 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 t= o >> the main branch: >> https://cgit.freebsd.org/src/commit/?id=3Dc16e08e5f324aa119c85e10eaabacb= d2abdb40e0 >> . >> 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 wro= te: >> >>> >>> >>> 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 wr= ote: >>> >>>> >>>> >>>> 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 w= rote: >>>> >>>>> >>>>> >>>>> On Thu, May 11, 2023 at 3:21=E2=80=AFPM Toomas Soome = wrote: >>>>> >>>>>> >>>>>> >>>>>> > 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 = 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 force= d to >>>>>> use =E2=80=9Ctext=E2=80=9D mode, which happens when system has confi= gured 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.con= f) >>>>> (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(0x8001010= 0),/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(0x8001010= 0) >>>>> >>>>> if not. >>>>> >>>>> Warner >>>>> >>>> >>>> >>> --000000000000a79fa805fb75627d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
No ConOut variable -> we assume the widest possibl= e amount of hardware. which is why you see efi comconsole as the console.

Can you send me the output of
efivar --de= vice-path 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConIn

It should look like:
8be4df61-93ca-11d2-aa0d-00e098032b8c-ConI= n
: PciRoot(0x0)/Pci(0x1f,0x0)/Acpi(PNP0303,0x0),/PciRoot(0x0)/Pci(0x1f,= 0x0)/Acpi(PNP0303,0x1)

I've been putting-off f= alling back to ConIn to determine the default console device. I'd like<= /div>
to collect a few more examples before I start.

=
Warner

On Thu, May 11, 2023 at 4:49=E2=80=AFPM Oleg Lel= chuk <oleglelchuk@gmail.com= > wrote:
Any, by the way, "show console" also shows "efi= ,comconsole", just like "kenv | grep efi" does.

On Thu, May 1= 1, 2023 at 6:40=E2=80=AFPM Oleg Lelchuk <oleglelchuk@gmail.com> wrote:
<= blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-l= eft:1px solid rgb(204,204,204);padding-left:1ex">
My ESP pa= rtition has EFI/BOOT/BOOTX64.efi . I copied /boot/loader.efi to EFI/BOOT/BO= OTX64.efi when I compiled stand after this commit was added to the main bra= nch:=C2=A0https://cgit.freebsd.org/sr= c/commit/?id=3Dc16e08e5f324aa119c85e10eaabacbd2abdb40e0 .=C2=A0=C2=A0= =C2=A0
I get this output:
kenv | grep efi
console=3D"= efi,comconsole"
efi-version=3D"2.70"
efi_com_port=3D&q= uot;0"
efi_com_speed=3D"0"
efi_max_resolution=3D"= 1x1"
entropy_efi_seed=3D"YES"
loader.efi=3D"1&quo= t;

And in the attachment, you can see the output f= rom the loader prompt.


On Thu, May 11, 2023 at 6:20=E2= =80=AFPM Toomas Soome <tsoome@me.com> wrote:


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

kenv | grep screen produces this output:

scree= nsave_load=3D"NO"
screensave_name=3D"green_saver"

Yep, the screen is cons= idered 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 dat= e; if you have no ConOut and ConOutDev variables set (by firmware), older l= oader did default to serial port, recent loader does default to efi,comcons= ole (see show console on loader prompt).=C2=A0

rgd= s,
toomas


=
On Thu, Ma= y 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:<= /div>
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

=C2=A0
acpi_dsdt_name= =3D"/boot/acpi_dsdt.aml"
boot_verbose=3D"YES"
boo= tenv_autolist=3D"YES"
bootenvs[0]=3D"zfs:DESKTOP/poudrier= e"
bootenvs_count=3D"1"
bootfile=3D"kernel"<= br>cpu_microcode_name=3D"/boot/firmware/ucode.bin"
entropy_cac= he_name=3D"/boot/entropy"
entropy_cache_type=3D"boot_entr= opy_cache"
if_re_name=3D"/boot/modules/if_re.ko"
kerne= l_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"
n= extboot_conf=3D"/boot/nextboot.conf"
ram_blacklist_name=3D&quo= t;/boot/blacklist.txt"

The efivar command= shows me:

efivar --device-path 8be4df61-93ca-11d2= -aa0d-00e098032b8c-ConOut
efivar: fetching 8be4df61-93ca-11d2-aa0d-00e09= 8032b8c-ConOut: No such file or directory

<= div class=3D"gmail_quote" style=3D"font-family:Helvetica;font-size:14px;fon= t-style:normal;font-variant-caps:normal;font-weight:400;letter-spacing:norm= al;text-align:start;text-indent:0px;text-transform:none;white-space:normal;= word-spacing:0px;text-decoration:none">
On Thu, May 11, 2023 at 5:43=E2=80=AFPM Warner Losh <imp@bsdimp.com> wrote:
<= blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-l= eft:1px solid rgb(204,204,204);padding-left:1ex">


On Thu, May 11, 2023 at 3:21=E2=80=AFPM Toomas Soome <tsoome@me.com> wrote:<= br>


> On = 12. May 2023, at 00:11, Oleg Lelchuk <oleglelchuk@gmail.com> wrote:
>= =C2=A0
> Guys, there is something that I find puzzling. Why do= esn'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 a= bout this particular motherboard that forces the FreeBSD EFI loader to disp= lay 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.

Th= ere 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 ser= ial 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, ma= ybe via a stray loader.conf)
(2) sudo efivar --device-path 8be4df= 61-93ca-11d2-aa0d-00e098032b8c-ConOut

It should sh= ow something like:
8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut
: PciRoot(0x2)/Pci(0x1,0x2)/Pci(0x0,0x0)/Pci(0x0,0x0)/AcpiAdr(0x8001= 0100),/PciRoot(0x0)/Pci(0x14,0x3)/Serial(0x1)/Uart(115200,8,N,1)/UartFlowCt= rl(Hardware)/VenVt100Plus()
=C2=A0
if there's redirec= t or something like

8be4df61-93ca-11d2-aa0d-00e098= 032b8c-ConOut
: PciRoot(0x2)/Pci(0x1,0x2)/Pci(0x0,0x0)/Pci(0x0,0x0)/Acpi= Adr(0x80010100)

if not.

Warner

=

--000000000000a79fa805fb75627d--