From nobody Thu May 11 23:14:13 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 4QHSQW1l9Zz4B9SV for ; Thu, 11 May 2023 23:14:27 +0000 (UTC) (envelope-from oleglelchuk@gmail.com) Received: from mail-qk1-x730.google.com (mail-qk1-x730.google.com [IPv6:2607:f8b0:4864:20::730]) (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 4QHSQV0kXdz3FSQ for ; Thu, 11 May 2023 23:14:26 +0000 (UTC) (envelope-from oleglelchuk@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20221208 header.b=rO5848Fs; spf=pass (mx1.freebsd.org: domain of oleglelchuk@gmail.com designates 2607:f8b0:4864:20::730 as permitted sender) smtp.mailfrom=oleglelchuk@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-qk1-x730.google.com with SMTP id af79cd13be357-757741ca000so586624885a.2 for ; Thu, 11 May 2023 16:14:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1683846865; x=1686438865; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=FKhuAnnYdJmOj2sxYcs18CM/XwH2TshU5Uqq2vW7bbk=; b=rO5848FsYl62SHjLtcGFDa5XLuPPfcfEDDzz0j+cVdgx4YDV2AePfe3C4OCFmkWgzT ItPPD5k7nSeY+lw015gzBYZGx7CRkdENQ4zBGQ64vXevQVo/CDApi8rUt9qrAjpl/EM2 DN31LFHqzLIxYOyenoda7sg7LCYOsZc+sL4xexvaLUp57LIYCt5OmlzfjILoBA5W4ACX 3ysR5XivJRbMFGAZBu7iJiiJ6Fk5Hv7jr88Q3DtVrTqmeEwo6vtfL9v6YNSc4TbyIcSz Zk1u7eLE/vZWaqwemT3TeMnnOks3WoSMLBy+GvG9Zm5FwKP/A3fhFK5MybmMnPAgFCTG 1RuQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683846865; x=1686438865; 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=FKhuAnnYdJmOj2sxYcs18CM/XwH2TshU5Uqq2vW7bbk=; b=DgFT3uVriirzW56zCUHIl2Vi6t8s0LbYj6E/I7MQOEi/yx3OaX+7bP27hGtlCxZi6L gzdzDx/a9lHVNOGR3d86hrZrGAGeqGb6fRZ3TNvnv2+5NMtH8wm3XfqoI1BUIuYNFXuT ZNpN8zdIOiXUNZ5fl5csckcFPlI8JSJLVZZWRkQXw4TXtjd6ZWDA4FzeGHVmheV2NT6/ vg3wJykE1GDJGLoWaFr5HoUUSO8/EFesTiSurSIfGCgBDrevE820EXx8mYq2ElLPtcP0 /FdTowb1M8Z2CYXHwtc0JFNrw2wXjBFfc4+He4O1sQ/N2jsWEXQsSk5FsJ0ga9oatObO zGPw== X-Gm-Message-State: AC+VfDzSTDaxImT/kTOiIkEZJVR/PGFJ24foQ1KYfSr3ingk0WP1Qxu4 Y6PfPzbMrG3bnQshnKBNnSMhH1KU6RVhXvPyEG76B7X5YhY= X-Google-Smtp-Source: ACHHUZ61Ma5DiheawSe9u1/2ZnUvOTdGRfapFI384H7HihJ1ybMRBo5UndSUQiIuIPmESaF+WbJ5XEUYhsgzM7KzRlY= X-Received: by 2002:a05:6214:d82:b0:5b5:9c2:8c29 with SMTP id e2-20020a0562140d8200b005b509c28c29mr30184784qve.12.1683846865007; Thu, 11 May 2023 16:14:25 -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 19:14:13 -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="0000000000003eb70105fb7326c7" X-Spamd-Result: default: False [-2.93 / 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.93)[-0.926]; 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::730: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: 4QHSQV0kXdz3FSQ X-Spamd-Bar: -- X-ThisMailContainsUnwantedMimeParts: N --0000000000003eb70105fb7326c7 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I meant to say "And", not "Any", at the start of the previous sentence. On Thu, May 11, 2023, 6:49 PM 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 >>>>> >>>> >>>> >>> --0000000000003eb70105fb7326c7 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I meant to say "And", not "Any", at t= he start of the previous sentence.

On Thu, May 11, 2023, 6:49 PM Oleg Lelchu= k <oleglelchuk@gmail.com>= ; wrote:
Any, by t= he way, "show console" also shows "efi,comconsole", jus= t like "kenv | grep efi" does.

On Thu, May 11, 2023 at 6:40=E2=80= =AFPM Oleg Lelchuk <oleglelchuk@gmail.com> wrote:

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


On 12. May 2023, at 01:09, Oleg Lelchuk <oleg= lelchuk@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 ConOu= t and ConOutDev variables set (by firmware), older loader did default to se= rial port, recent loader does default to efi,comconsole (see show console o= n loader prompt).=C2=A0

rgds,
toomas


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.co= m> wrote:

kenv | grep bo= ot shows me this:

Can you run k= env | grep screen ? in gfx mode, you should see screen.depth, screen.height= and screen.width

rgds,
toomas

=
=C2=A0acpi_dsdt_name=3D"/boot/acpi_dsdt.aml"
boot_verbose=3D"Y= ES"
bootenv_autolist=3D"YES"
bootenvs[0]=3D"zfs:D= ESKTOP/poudriere"
bootenvs_count=3D"1"
bootfile=3D&quo= t;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"/boo= t/kernel/kernel"
loader_conf_dirs=3D"/boot/loader.conf.d"=
module_path=3D"/boot/kernel;/boot/modules;/boot/dtb;/boot/dtb/over= lays"
nextboot_conf=3D"/boot/nextboot.conf"
ram_blackl= ist_name=3D"/boot/blacklist.txt"

The= efivar command shows me:

efivar --device-path 8be= 4df61-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@bs= dimp.com> wrote:


On Thu, 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 bo= ot menu on an Asus Prime 7590-P motherboard? Is there something quirky abou= t 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 ca= use 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=9C= text=E2=80=9D mode, which happens when system has configured to have serial= console (redirection).

I think the lat= ter isn't the case (based on earlier email with Oleg), but we can be su= re 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(0x8001010= 0),/PciRoot(0x0)/Pci(0x14,0x3)/Serial(0x1)/Uart(115200,8,N,1)/UartFlowCtrl(= Hardware)/VenVt100Plus()
=C2=A0
if there's redirect o= r something like

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

if not.

= Warner


--0000000000003eb70105fb7326c7--