From nobody Thu May 11 21:57:55 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 4QHQkS1PnBz4B5HL for ; Thu, 11 May 2023 21:58:08 +0000 (UTC) (envelope-from oleglelchuk@gmail.com) Received: from mail-qk1-x729.google.com (mail-qk1-x729.google.com [IPv6:2607:f8b0:4864:20::729]) (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 4QHQkR6sF4z4G6r for ; Thu, 11 May 2023 21:58:07 +0000 (UTC) (envelope-from oleglelchuk@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-qk1-x729.google.com with SMTP id af79cd13be357-757742c2e5fso490148285a.1 for ; Thu, 11 May 2023 14:58:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1683842286; x=1686434286; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=qJtv9sYAa9nPQBQGPUUeEtNTa/Th4INGDNXrj9/wlmg=; b=kuT7FzgcGOjgr0D6/maEG9nVV8wWawQuB1G8/WOP5ZCEiuVKsreZO9W0IGqZf2LdLq /LGbGI8ytN+ztzM81nCUP2XbMNwkD9C21bo4peJrTnfq8gBaMlnj8+G0YXQoWQzWw4n9 F/cFJouylylNw4fArSOlPPYXRoT5d3xoPH0KHXUMICv/tj62JNpfCAFjzRfEkrluP7qd 1bXtS0aCzP80jlM0tVnJWsXkuqYrmE8OXPLk71u86qXh+2ee8GCQsGAUoDOHJ81Vbeyn PN5DRru/+LK/mziY3K7C+dgZhvdq6Kb9V+XPW3qPYYcvxo72DKs5qokRT7IXpSwtD+6j v8Mw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683842286; x=1686434286; 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=qJtv9sYAa9nPQBQGPUUeEtNTa/Th4INGDNXrj9/wlmg=; b=HOFp4OPppVvLZuyTYQGKuK13OSDl3SHcOHdK3z6MERW7hCBK5FYvZNuHXgoF9y0Kof HkMyZdr9iqlGDhdi+UjqGFEolNOut1CrGiE0rn6cSGBe+ItyiEitm/a2fckvoWlxrJBZ T6lB5wyaZhkHg81KQitOpVr4O5e2XQ4eKaNrRQiA2WbAsNuYehxutkUfcbaY7cGjWzEx SGjHm7EFQqoiKWnke+0XOmoPCMcM1tmWmA6FTT1P2EFAfoxihrsNr2BIOk4I2qv6OQh6 uQ9c3cg5ODpd7h+GHrn/ZiJDwduHKMcOhh7yYCoGkJk1YXycwupcGg9TcomkaDmWOtRI jtjg== X-Gm-Message-State: AC+VfDyt2KQPtps0Rhb3MbxoXVmvQDCCsAVBWfSy1EwoXW9i9hzIDCFg 22elarxkPFi65XT/QsPKlsAMonFhovy5LEyMuVg= X-Google-Smtp-Source: ACHHUZ5JS+snoInYfUHhABvp77bDDPOGCs9vFk+U2TunpfK2s6Y2ysJyssyKbOxYf35gFNgemMfZT1QGo2c9R8JaygE= X-Received: by 2002:ad4:5f8e:0:b0:5ef:8909:9b43 with SMTP id jp14-20020ad45f8e000000b005ef89099b43mr36648701qvb.36.1683842286474; Thu, 11 May 2023 14:58:06 -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> In-Reply-To: From: Oleg Lelchuk Date: Thu, 11 May 2023 17:57:55 -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: Warner Losh Cc: Toomas Soome , freebsd-current@freebsd.org Content-Type: multipart/alternative; boundary="00000000000057d84205fb72159c" X-Rspamd-Queue-Id: 4QHQkR6sF4z4G6r X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --00000000000057d84205fb72159c Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable kenv | grep boot shows me this: 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 wrote: > > > On Thu, May 11, 2023 at 3:21=E2=80=AFPM Toomas Soome wrot= e: > >> >> >> > On 12. May 2023, at 00:11, Oleg Lelchuk wrote: >> > >> > Guys, there is something that I find puzzling. Why doesn't the EFI boo= t >> loader want to display the graphical orb logo in its boot menu on an Asu= s >> Prime 7590-P motherboard? Is there something quirky about this particula= r >> 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 forced to us= e >> =E2=80=9Ctext=E2=80=9D mode, which happens when system has configured 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(Hard= ware)/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 > --00000000000057d84205fb72159c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
kenv | grep boot shows me this:
=C2=A0
acpi_dsdt_na= me=3D"/boot/acpi_dsdt.aml"
boot_verbose=3D"YES"
b= ootenv_autolist=3D"YES"
bootenvs[0]=3D"zfs:DESKTOP/poudri= ere"
bootenvs_count=3D"1"
bootfile=3D"kernel"= ;
cpu_microcode_name=3D"/boot/firmware/ucode.bin"
entropy_c= ache_name=3D"/boot/entropy"
entropy_cache_type=3D"boot_en= tropy_cache"
if_re_name=3D"/boot/modules/if_re.ko"
ker= nel_path=3D"/boot/kernel"
kernelname=3D"/boot/kernel/kern= el"
loader_conf_dirs=3D"/boot/loader.conf.d"
module_pa= th=3D"/boot/kernel;/boot/modules;/boot/dtb;/boot/dtb/overlays"nextboot_conf=3D"/boot/nextboot.conf"
ram_blacklist_name=3D&q= uot;/boot/blacklist.txt"

The efivar comma= nd shows me:

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

On Thu, May 11, 2023= at 5:43=E2=80=AFPM Warner Losh <imp@b= sdimp.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:
>
> 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 reasons. One is that resolution is low and there is no spa= ce 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).

I think t= he 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 8be= 4df61-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(0x8= 0010100),/PciRoot(0x0)/Pci(0x14,0x3)/Serial(0x1)/Uart(115200,8,N,1)/UartFlo= wCtrl(Hardware)/VenVt100Plus()
=C2=A0
if there's redi= rect or something like

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

if not.

Warner
--00000000000057d84205fb72159c--