From nobody Thu May 11 22:09:37 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 4QHQzx6TQPz4B68f for ; Thu, 11 May 2023 22:09:49 +0000 (UTC) (envelope-from oleglelchuk@gmail.com) Received: from mail-qk1-x731.google.com (mail-qk1-x731.google.com [IPv6:2607:f8b0:4864:20::731]) (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 4QHQzx4SjKz4KVs for ; Thu, 11 May 2023 22:09:49 +0000 (UTC) (envelope-from oleglelchuk@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-qk1-x731.google.com with SMTP id af79cd13be357-75131c2997bso3145222485a.1 for ; Thu, 11 May 2023 15:09:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1683842988; x=1686434988; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=V2F5KvFWFD7VPOwX0aL5cAPe764ei+4ZXs7W6hZhHWE=; b=Jag/Tl+9aKKYqCLqKOwXG/Y6+mcUK0L9LJNp4ck/X4tD0SivvfPMWnOgqDzJ3lWJoK 4uY7NXHxsLdoFxxqAGqHnnzt4lW2QaZqwPNpgnjwiJV3U2YYz5EVwgW2QUxWsFBVtKKo TAhu1w3NhwyDhQuyheXNX6z0jF4OTf5IJ7tibpEVzqpgBRTwbyHmz1EMma2T9HH1KAhH sgTlHtn6i/JOAGvEulahyuEXxS2uPPBGXpxGh7SQ32uiAIIn/YY2hCuPsOM8+TFqsqmd Ku83+qwUDDLnb8Y20/xvezDNpSCipkG+U95e8xiQnEdHKeOqDA87jEVZLdTTvhMJ7AKC /F7Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683842988; x=1686434988; 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=V2F5KvFWFD7VPOwX0aL5cAPe764ei+4ZXs7W6hZhHWE=; b=hgB3tzFmhRuZGrFdstpTL2sOa/mTjlokYZ88wzTr7WM2MNXBcgn0Q0dmhDu00QV09P HME90+KgYeHFT7EduOW/NF/YlVcE8VupIx/6Ezy2keTC9omllGrMzHSVbGNdjWrNboL/ PrWxsa6Sq98/D/wc8/rQOm5JlUQXxgevk7YecbR9xVMAvzeGOFdWD8cqQqcyiWiMBEd9 EUc6x6Yqa1r3CUWPFJ9PSmCeTvD0oaxMcxOltju9SxsB28bSi0e9IGuieQKBTTniY2gj HGHLLEVBCY5KHx+uWO+lg9z3JieVKT/O4C4r9lTj/X0cI+ygL2DVqbK5JNfxYl1AeeCO m8wA== X-Gm-Message-State: AC+VfDxaSHdkdw3UWYijudnVuEsUpCZ2th4B3yn4+MIJwP3sEd3PzpKN /WNCa+my0VHr0dR9EXSCht6EHtGEEP06DAOfCck= X-Google-Smtp-Source: ACHHUZ4XP5XqyCvdzXuLvyXZ3NQxODutnnp0MvTWUO2qcIlcMkOGTUrSJ5OsegkVEAgJIkUE7ucpasWN1hTAAhUC0OQ= X-Received: by 2002:a05:6214:5297:b0:61b:58ec:24c8 with SMTP id kj23-20020a056214529700b0061b58ec24c8mr36742295qvb.10.1683842988030; Thu, 11 May 2023 15:09:48 -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 18:09:37 -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="00000000000028bfc405fb723fa7" X-Rspamd-Queue-Id: 4QHQzx4SjKz4KVs 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 --00000000000028bfc405fb723fa7 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable kenv | grep screen produces this output: screensave_load=3D"NO" screensave_name=3D"green_saver" On Thu, May 11, 2023 at 6:06=E2=80=AFPM Toomas Soome wrote: > > > 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 fil= e > or directory > > On Thu, May 11, 2023 at 5:43=E2=80=AFPM Warner Losh wrot= e: > >> >> >> On Thu, May 11, 2023 at 3:21=E2=80=AFPM Toomas Soome wro= te: >> >>> >>> >>> > 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 th= e >>> old style ASCII orb logo in its boot menu? Please explain to me the cau= se >>> 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 u= se >>> =E2=80=9Ctext=E2=80=9D mode, which happens when system has configured t= o have serial >>> console (redirection). >>> >> >> I think the latter isn't the case (based on earlier email with Oleg), bu= t >> 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-ConOu= t >> >> 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(Har= dware)/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 >> > > --00000000000028bfc405fb723fa7 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
kenv | grep screen produces this output:

screensave_load=3D"NO"
screensave_name=3D"green_saver&q= uot;

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 | gre= p screen ? in gfx mode, you should see screen.depth, screen.height and scre= en.width

rgds,
toomas

=C2=A0
acpi_dsd= t_name=3D"/boot/acpi_dsdt.aml"
boot_verbose=3D"YES"<= br>bootenv_autolist=3D"YES"
bootenvs[0]=3D"zfs:DESKTOP/po= udriere"
bootenvs_count=3D"1"
bootfile=3D"kernel&= quot;
cpu_microcode_name=3D"/boot/firmware/ucode.bin"
entro= py_cache_name=3D"/boot/entropy"
entropy_cache_type=3D"boo= t_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"
modul= e_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-93= ca-11d2-aa0d-00e098032b8c-ConOut
efivar: fetching 8be4df61-93ca-11d2-aa0= d-00e098032b8c-ConOut: No such file or directory

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


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:
&= gt;=C2=A0
> Guys, there is something that I find puzzlin= g. Why doesn't the EFI boot loader want to display the graphical orb lo= go in its boot menu on an Asus Prime 7590-P motherboard? Is there something= quirky about this particular motherboard that forces the FreeBSD EFI loade= r 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.<= br>
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 u= se =E2=80=9Ctext=E2=80=9D mode, which happens when system has configured to= have serial console (redirection).

I t= hink 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 ar= e set, maybe via a stray loader.conf)
(2) sudo efivar --device-pa= th 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)/AcpiA= dr(0x80010100),/PciRoot(0x0)/Pci(0x14,0x3)/Serial(0x1)/Uart(115200,8,N,1)/U= artFlowCtrl(Hardware)/VenVt100Plus()
=C2=A0
if there'= s redirect or something like

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

if not.
Warner
<= /div>
--00000000000028bfc405fb723fa7--