From nobody Fri May 12 02:21:52 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 4QHXb23bDxz4BMXR for ; Fri, 12 May 2023 02:22:06 +0000 (UTC) (envelope-from oleglelchuk@gmail.com) Received: from mail-qv1-xf2b.google.com (mail-qv1-xf2b.google.com [IPv6:2607:f8b0:4864:20::f2b]) (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 4QHXb13K5Gz3rn1 for ; Fri, 12 May 2023 02:22:05 +0000 (UTC) (envelope-from oleglelchuk@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20221208 header.b=Gm4AskwR; spf=pass (mx1.freebsd.org: domain of oleglelchuk@gmail.com designates 2607:f8b0:4864:20::f2b as permitted sender) smtp.mailfrom=oleglelchuk@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-qv1-xf2b.google.com with SMTP id 6a1803df08f44-61b6101a1b9so42932316d6.3 for ; Thu, 11 May 2023 19:22:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1683858123; x=1686450123; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=0HkE9Gyj1sB1OoR3RsUiaeeABQ9RWJGuvwQI7qSH8jA=; b=Gm4AskwR4PtydebP7MrGT3zIGVgH/DrRnaks8S1A48rmDueuDazLGIAvLoSQAsWzi8 Io4UdvQEumEnit8ie/CBrtTK3Hn3jxjory6h0zkUEzJK+Y1KN+nV0ZaDIqdJ7dM7CTPb +QUNwUdGBT8XL7OWO2eL/zLkRJjygAWxltP+ZUnxPCheABeQ5AZYKw0XuPl3YDMEnBSk asybQAHT+AhWourqJP4Z2qliySi3u0ORpEc9uL2UeLR5XzY96Lkhl9VGDIPZla/Y8bOu 1jWO/Br8zFK1pOS102HY31WLm1Trno2rGNEf3kQVyGzbnixHoB6+pSK3wrMPSuiiz+Cq DGKA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683858123; x=1686450123; h=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=0HkE9Gyj1sB1OoR3RsUiaeeABQ9RWJGuvwQI7qSH8jA=; b=e7S1f+fkHcX2bKvWZjUAYC0JT+gkvzJgr6kDmN4lqdVIckwUrmpyl4iaibVgJu9JjM gahLRgkjrFexf2E5yXXmu4smWemzoIfKeQ+0Cd5usFogigFPvpX3vviLBoyk5aMn7M14 nyilDukszCZQYIto4JNfp660h+mgb3o7b2POuhVP+nH6dW5GjeCTNA6pcJx60yfHx0Wr nKkudzB75cXv4hmRZoI3owaVC0hv1VVrAg7HX+lwWV+4zQ+BbALI64TKxLkvlHekEBuL 9dhV+XDLawkBivJF+rJEPa/zjxJlsGiJ3NYaEXkRO07M4ps5maD6SCZp8grmB8W1FCnz OH0Q== X-Gm-Message-State: AC+VfDwfJZuU2ZM47VrBkJPoyYraF+hWFI4Gd4Oj+IgOs9vz4HsFYHLK Lm/AskAgEzLt4tfQwkEOfhVSOGE2z00qGQ5cABCyyEPKSn0= X-Google-Smtp-Source: ACHHUZ7lMNljEeRcYnzlk387x01EkxoTVgKjT9/dznrqWZidAfnpxAizW2UMkoZdQl9Q7CsUk4pa9b/hRLVaqxDfMsg= X-Received: by 2002:a05:6214:cc2:b0:5ed:ddf0:7c2d with SMTP id 2-20020a0562140cc200b005edddf07c2dmr43723817qvx.25.1683858123386; Thu, 11 May 2023 19:22:03 -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 22:21:52 -0400 Message-ID: Subject: Fwd: 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: freebsd-current@freebsd.org Content-Type: multipart/alternative; boundary="0000000000004bf25305fb75c58c" X-Spamd-Result: default: False [-2.03 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-0.998]; 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]; NEURAL_HAM_SHORT(-0.03)[-0.031]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; RCPT_COUNT_ONE(0.00)[1]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::f2b: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)[]; TO_DN_NONE(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FROM_EQ_ENVFROM(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; RCVD_COUNT_TWO(0.00)[2] X-Rspamd-Queue-Id: 4QHXb13K5Gz3rn1 X-Spamd-Bar: -- X-ThisMailContainsUnwantedMimeParts: N --0000000000004bf25305fb75c58c Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable ---------- Forwarded message --------- From: Oleg Lelchuk Date: Thu, May 11, 2023 at 10:19=E2=80=AFPM 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: Warner Losh I see this output: efivar --device-path 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConIn 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConIn : PciRoot(0x0)/Pci(0x1f,0x0)/Acpi(PNP0303,0x0),/PciRoot(0x0)/Pci(0x14,0x0)/US= B(0x2,0x0) On Thu, May 11, 2023 at 9:54=E2=80=AFPM Warner Losh wrote: > 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)/= Acpi(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 t= o >>> EFI/BOOT/BOOTX64.efi when I compiled stand after this commit was added = to >>> the main branch: >>> https://cgit.freebsd.org/src/commit/?id=3Dc16e08e5f324aa119c85e10eaabac= bd2abdb40e0 >>> . >>> 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 wr= ote: >>> >>>> >>>> >>>> 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 i= s >>>> 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 w= rote: >>>> >>>>> >>>>> >>>>> 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/overlay= s" >>>>> 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 = wrote: >>>>> >>>>>> >>>>>> >>>>>> 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 EF= I >>>>>>> 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 displa= y 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 i= s >>>>>>> no space to put the image on. Second one is that the screen is forc= ed to >>>>>>> use =E2=80=9Ctext=E2=80=9D mode, which happens when system has conf= igured 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(0x800101= 00),/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(0x800101= 00) >>>>>> >>>>>> if not. >>>>>> >>>>>> Warner >>>>>> >>>>> >>>>> >>>> --0000000000004bf25305fb75c58c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


---------- Forwarded message ---------
From: Oleg Lelchuk <oleglelchuk@gmail.com&g= t;
Date: Thu, May 11, 2023 at 10:19=E2=80=AFPM
Subject: Re: Wh= y 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: Warner Losh <= imp@bsdimp.com>


<= div dir=3D"ltr">I see this output:
efivar --device-path 8be4df61-93ca-1= 1d2-aa0d-00e098032b8c-ConIn
8be4df61-93ca-11d2-aa0d-00e098032b8c-ConIn: PciRoot(0x0)/Pci(0x1f,0x0)/Acpi(PNP0303,0x0),/PciRoot(0x0)/Pci(0x14,0x0= )/USB(0x2,0x0)

On Thu, May 11, 2023 at 9:54=E2=80=AFPM Warner Losh= <imp@bsdimp.com= > wrote:
No ConOut variable -> we assume the widest possible am= ount 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

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

I've been putting-off falli= ng 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= <oleglelchuk= @gmail.com> wrote:
Any, by the way, "show console" also = shows "efi,comconsole", just like "kenv | grep efi" doe= s.

On Thu, May 11, 2023 at 6:40=E2=80=AFPM Oleg Lelchuk <oleglelchuk@gmail.com> wr= ote:
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:=C2=A0https://cgit= .freebsd.org/src/commit/?id=3Dc16e08e5f324aa119c85e10eaabacbd2abdb40e0 = .=C2=A0=C2=A0=C2=A0
I get this output:
kenv | grep efi
con= sole=3D"efi,comconsole"
efi-version=3D"2.70"
efi_= com_port=3D"0"
efi_com_speed=3D"0"
efi_max_resolu= tion=3D"1x1"
entropy_efi_seed=3D"YES"
loader.efi= =3D"1"

And in the attachment, you can se= e the output from the loader prompt.


On Thu, May 11, 20= 23 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:

screensave_load=3D"NO"
screensave_name=3D"green_s= aver"

Yep, the s= creen is considered to be in text mode and only ascii art is used (see draw= er.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 firmw= are), older loader did default to serial port, recent loader does default t= o efi,comconsole (see show console on loader prompt).=C2=A0

<= /div>
rgds,
toomas


On Thu, May 11, 2023 at 6:06=E2=80=AFPM Toomas Soome <tsoome@me.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">



=C2=A0
ac= pi_dsdt_name=3D"/boot/acpi_dsdt.aml"
boot_verbose=3D"YES&= quot;
bootenv_autolist=3D"YES"
bootenvs[0]=3D"zfs:DESK= TOP/poudriere"
bootenvs_count=3D"1"
bootfile=3D"k= ernel"
cpu_microcode_name=3D"/boot/firmware/ucode.bin"entropy_cache_name=3D"/boot/entropy"
entropy_cache_type=3D&qu= ot;boot_entropy_cache"
if_re_name=3D"/boot/modules/if_re.ko&qu= ot;
kernel_path=3D"/boot/kernel"
kernelname=3D"/boot/k= ernel/kernel"
loader_conf_dirs=3D"/boot/loader.conf.d"module_path=3D"/boot/kernel;/boot/modules;/boot/dtb;/boot/dtb/overlay= s"
nextboot_conf=3D"/boot/nextboot.conf"
ram_blacklist= _name=3D"/boot/blacklist.txt"

The ef= ivar command shows me:

efivar --device-path 8be4df= 61-93ca-11d2-aa0d-00e098032b8c-ConOut
efivar: fetching 8be4df61-93ca-11d= 2-aa0d-00e098032b8c-ConOut: No such file or directory

On Thu, May 11, 2023 at 5:43=E2=80=AFPM Warner Losh <imp@bsdimp.com> wro= te:


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

> On 12. May 2023, at 00:11, Oleg Lelchuk <oleglelchuk@gmail.com> wrote:<= br>>=C2=A0
> Guys, there is something that I find puz= zling. Why doesn't the EFI boot loader want to display the graphical or= b logo in its boot menu on an Asus Prime 7590-P motherboard? Is there somet= hing quirky about this particular motherboard that forces the FreeBSD EFI l= oader to display the old style ASCII orb logo in its boot menu? Please expl= ain 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 ther= e 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 configure= d 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_xx= x are set, maybe via a stray loader.conf)
(2) sudo efivar --devic= e-path 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut

It should show something like:
8be4df61-93ca-11d2-aa0d-00e098032= b8c-ConOut
: PciRoot(0x2)/Pci(0x1,0x2)/Pci(0x0,0x0)/Pci(0x0,0x0)/A= cpiAdr(0x80010100),/PciRoot(0x0)/Pci(0x14,0x3)/Serial(0x1)/Uart(115200,8,N,= 1)/UartFlowCtrl(Hardware)/VenVt100Plus()
=C2=A0
if there&= #39;s redirect or something like

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

if not.

Warner


--0000000000004bf25305fb75c58c--