From nobody Thu May 11 21:43:22 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 4QHQPh4TdNz4B4Yb for ; Thu, 11 May 2023 21:43:36 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ed1-x529.google.com (mail-ed1-x529.google.com [IPv6:2a00:1450:4864:20::529]) (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 4QHQPh0VXwz4DL9 for ; Thu, 11 May 2023 21:43:36 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ed1-x529.google.com with SMTP id 4fb4d7f45d1cf-50bd2d7ba74so83471740a12.1 for ; Thu, 11 May 2023 14:43:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20221208.gappssmtp.com; s=20221208; t=1683841413; x=1686433413; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=WdInz2IZYSs7uhop03oexJ7otaWd27U/96c1EP8R2bo=; b=WQFiEdszXyzrEiJIj+rbIlr1ZY+01jhQFBMTGExJOIhUGwkUqXd2N12ckovsaJ1uss vLsIHSGLelwWAIqJyLCI0qAFSmY97k72rEQobb+BfQM2e5HMsL97pReNOSopMHwyHHC+ zC6c55eU1HeVblddHt76HcOSWnHJ1Z2s86UIP+hR88XVC9YAH1GAxek5YgPKmFJXK3W9 G5GeWDQZRUIdXGXewg9OOE7dLlUgt2gXwBu1FV8eD11e+PDAEsEH/r48DpYjrnGHxgXF pauvEwP3AU8+x96DlKhuWsrGIpQ67v4PpILPhyeFCkkVhziPXsU76EoAPq5WiCAkX0HO LjJA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683841413; x=1686433413; 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=WdInz2IZYSs7uhop03oexJ7otaWd27U/96c1EP8R2bo=; b=VtkxhgGafsAVE3aiQRRF9sKfwAM/GnYxRW2//u+zdC3QnSE940XM3AnxgOP8Zlal28 0VsFsytl+hYILDIShvxrMS3DKezpbcWwCHXRG5fftS2b8xtrLhhAmnVIeLiSNIwPL7ZH UvBPVDxkRnhSnD2yZc9Bgput6bu13YlqYq8CmqYMqguORRLtGSHQOtky6J5T5na1Pt3K 3vY23lO2GIFFkSVG2nRVhK6AkSz+/AGi+acS+Ce37p7efLH3u8NZk3DW40/VHmo9leqb 9LgnuHKvtl8laAaAPAn1XBADOeYI9mzxvpeRfrjiwgKWPYKjyJ5z+7fepikY1JWtQ7vW qJSw== X-Gm-Message-State: AC+VfDxug7o4gKpdvWXSDdvcatq46LVgsLycbsI0XQOei2b5IBmuXtpJ pLCvD2g6FHK3Ih+7ytI2UgWirocmphYWjLG520RQYr302vPJlF9V6vk= X-Google-Smtp-Source: ACHHUZ7jCd/XZ2gQSyQwjx5IVILpfBCY9ax7sG9AD4YYr0E4uFWPYwzOLx/r9Jh+cY7lF0tKvPDX2seIfkzBuhYrv+w= X-Received: by 2002:a17:907:3f22:b0:96a:2b4:eb69 with SMTP id hq34-20020a1709073f2200b0096a02b4eb69mr9411445ejc.31.1683841413233; Thu, 11 May 2023 14:43:33 -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: <3B658415-3AD0-4E8B-8CBE-F13FA70CBDC8@me.com> From: Warner Losh Date: Thu, 11 May 2023 15:43:22 -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: Toomas Soome Cc: Oleg Lelchuk , freebsd-current@freebsd.org Content-Type: multipart/alternative; boundary="0000000000004b4ff605fb71e1d2" X-Rspamd-Queue-Id: 4QHQPh0VXwz4DL9 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 --0000000000004b4ff605fb71e1d2 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 forced to use > =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),/Pc= iRoot(0x0)/Pci(0x14,0x3)/Serial(0x1)/Uart(115200,8,N,1)/UartFlowCtrl(Hardwa= re)/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 --0000000000004b4ff605fb71e1d2 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Thu, May 11, 2023 at 3:21=E2=80=AF= PM 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
--0000000000004b4ff605fb71e1d2--