From nobody Fri May 12 13:26:14 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 4QHqKb5BW9z4B1bg for ; Fri, 12 May 2023 13:26:27 +0000 (UTC) (envelope-from oleglelchuk@gmail.com) Received: from mail-qv1-xf30.google.com (mail-qv1-xf30.google.com [IPv6:2607:f8b0:4864:20::f30]) (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 4QHqKb2YcBz3wt0 for ; Fri, 12 May 2023 13:26:27 +0000 (UTC) (envelope-from oleglelchuk@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-qv1-xf30.google.com with SMTP id 6a1803df08f44-62135cf0adcso23831186d6.1 for ; Fri, 12 May 2023 06:26:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1683897986; x=1686489986; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=VbNFZtFoylK4mDhQ73TF9bjYMfoeXUhdey+7uBT4aZc=; b=K6HgC+QTGEmtFnuwraN0E3uu3z02/pHT7QLmIrZM/+M5JVsb4BVHBsDrtEeva7g9kc Xn82pgqKQKux9QvRs7718xs9QISUjNof/Rw87OM82gxYLY1DjvSX9FzwIVcspGHwn/xp 4iIeyv98JMblDMgsWI+/sXys+m1Vset5OgUpeXMjTI6Biqf2+nO+VYpZrIajjfVtKv2L rvgxNdOepToMJhGn1VA/Iq4Rr2CzJKIafZsbyeemb6C4+6xJ/UStPQUVxZoNHoIzV4Sr M2w5/Zrz93LUOqxI2Odsj8UNWvPM4x0J9xySt9W1bbKCB2ntwGk7HSiVtibAP5ePzvS1 G3nA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683897986; x=1686489986; 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=VbNFZtFoylK4mDhQ73TF9bjYMfoeXUhdey+7uBT4aZc=; b=NT7Ee3JX6Cqk1AXoQlAUVNXYIZ3qQnjGZolUqjEEmua3VEM+FnIhob1kx7fnQNope5 YTJHSN1JDH0LQs+h3LQhGu1uoUzJkG0wblV6bTRnqxbTHzXjEPayaRhaOUenXog7+3xv Y6juQGbajwhyTPJXepjrX6HTzjDj02g4gjLMAfqG6JHws8JF9a+zLnNRpL/Do5DD2ff8 qB4NAL8qwZz87jp33+1xvMKZw1ghLcO0r/hfJ1T2ED2D1f89nHi7ncBfSu7jvXQ68lUQ ZLoy4qhmn0YEeGPEHB/8VAk/0A0UWk7nRYin2GsMGG8e1pAezYW4N6cl6FJnCt6u3y+O Wn5g== X-Gm-Message-State: AC+VfDxHW3FZv8pQeNIBBK7miVNgcipn1eeRYhOJg2AyCvM+IJSUbFtX Q/Yv4vIsNpmX694N9f1BWf8qWvL0xUndvG6CplE= X-Google-Smtp-Source: ACHHUZ6xwgHLuuPCLCvcJSV38/261+VHN8R7/gS3EmdqZOzFJgIx21bHJ8y5KjgyWehPaF+eMPxbbbMEpipUuINNuKk= X-Received: by 2002:ad4:5f0c:0:b0:61b:58f5:5dc3 with SMTP id fo12-20020ad45f0c000000b0061b58f55dc3mr37807728qvb.43.1683897986413; Fri, 12 May 2023 06:26:26 -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> <20230512070557.859671981b7c616c0da7d666@bidouilliste.com> <4F0D21B1-58B6-413D-8499-11AF0E338C78@me.com> In-Reply-To: From: Oleg Lelchuk Date: Fri, 12 May 2023 09:26:14 -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: Emmanuel Vadot , freebsd-current@freebsd.org Content-Type: multipart/alternative; boundary="00000000000051761205fb7f0d54" X-Rspamd-Queue-Id: 4QHqKb2YcBz3wt0 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 --00000000000051761205fb7f0d54 Content-Type: text/plain; charset="UTF-8" I don't want to go through the hassle of filling a bug with my vendor. I will just wait for you, guys, to update the stand implementation. Thank you for explaining to me what causes this issue. On Fri, May 12, 2023, 8:02 AM Toomas Soome wrote: > > > On 12. May 2023, at 14:45, Oleg Lelchuk wrote: > > I run the latest uefi bios firmware available for my motherboard. So, in > your opinion, there is something wrong with it? Is this problem somehow > related to this problem: > https://www.mail-archive.com/stable@freebsd.org/msg00235.html ? As I > mentioned earlier, my motherboard is Asus Prime 7590-P Wifi. The PC is > connected to my monitor and there is absolutely nothing connected to the > PC's serial port. If there is a bug in my motherboard's UEFI > implementation, is it possible to add code to the stand implementation of > FreeBSD that will find a way around this bug?.. Please think of > something... I definitely want to see the graphical orb logo in the FreeBSD > boot menu! > > > The UEFI specification does describe those variables, but I have not seen > them noted to be required to be present. They *usually* are present. So, if > you have latest firmware and have option to file the bug with vendor, it is > good idea to do so. > > Anyhow, as Warner already wrote, we actually have option to check ConIn > for presence of serial port too, so we should do that - it will just take a > bit of time. > > rgds, > toomas > > On Fri, May 12, 2023, 6:55 AM Toomas Soome wrote: > >> >> >> On 12. May 2023, at 13:41, Oleg Lelchuk wrote: >> >> There is only one monitor connected to my PC. >> >> >> Multiple monitors is definitely not an issue in your case (the missing >> ConOut and the decision chain based on it is the root cause). What you can >> do, is to check if there is firmware update from system vendor, that may >> fix the missing ConOut. >> >> rgds, >> toomas >> >> >> >> On Fri, May 12, 2023, 1:06 AM Emmanuel Vadot >> wrote: >> >>> On Fri, 12 May 2023 00:20:47 +0300 >>> 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 ?text? mode, which happens when system has configured to have serial >>> console (redirection). >>> > >>> > rgds, >>> > toomas >>> >>> There is a third reason : you have multiple screens and EFI firmware >>> output on all of them. Never took the time to dig into this one. >>> >>> -- >>> Emmanuel Vadot >>> >> >> > --00000000000051761205fb7f0d54 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I don't want to go through the hassle of filling a bu= g with my vendor. I will just wait for you, guys, to update the stand imple= mentation. Thank you for explaining to me what causes this issue.

=
On Fri, Ma= y 12, 2023, 8:02 AM Toomas Soome <tsoom= e@me.com> wrote:


On 12. May 2023, at 14:45, Oleg Lelchuk <oleglelchuk@gmail.com= > wrote:

I run the late= st uefi bios firmware available for my motherboard. So, in your opinion, th= ere is something wrong with it? Is this problem somehow related to this pro= blem:=C2=A0https://www.mail-archive.com= /stable@freebsd.org/msg00235.html ? As I mentioned earlier, my motherbo= ard is Asus Prime 7590-P Wifi. The PC is connected to my monitor and there = is absolutely nothing connected to the PC's serial port. If there is a = bug in my motherboard's UEFI implementation, is it possible to add code= to the stand implementation of FreeBSD that will find a way around this bu= g?.. Please think of something... I definitely want to see the graphical or= b logo in the FreeBSD boot menu!

The UEFI specification does describe those variables, but I hav= e not seen them noted to be required to be present. They *usually* are pres= ent. So, if you have latest firmware and have option to file the bug with v= endor, it is good idea to do so.

Anyhow, as Warner= already wrote, we actually have option to check ConIn for presence of seri= al port too, so we should do that - it will just take a bit of time.
<= div>
rgds,
toomas

On = Fri, May 12, 2023, 6:55 AM Toomas Soome <tsoome@me.com> wrote:


On 12. May 2023, at 13:41, Oleg Lelchuk <oleglelchuk@gmail.com> wrote:

There is only one monitor connected to my PC.

Multiple monitors is definitely not an issue in your case= (the missing ConOut and the decision chain based on it is the root cause).= What you can do, is to check if there is firmware update from system vendo= r, that may fix the missing ConOut.

rgds,
toomas



On Fri, May 12, 2= 023, 1:06 AM Emmanuel Vadot <manu@bidouilliste.com>= wrote:
On Fri, = 12 May 2023 00:20:47 +0300
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 th= e EFI boot loader want to display the graphical orb logo in its boot menu o= n an Asus Prime 7590-P motherboard? Is there something quirky about this pa= rticular 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 th= is problem and if possible, give me a solution to it.
>
> There can be two reasons. One is that resolution is low and there is n= o space to put the image on. Second one is that the screen is forced to use= ?text? mode, which happens when system has configured to have serial conso= le (redirection).
>
> rgds,
> toomas

=C2=A0There is a third reason : you have multiple screens and EFI firmware<= br> output on all of them. Never took the time to dig into this one.

--
Emmanuel Vadot <manu@bidouilliste.com> &= lt;manu@freebsd.org>


--00000000000051761205fb7f0d54--