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?

[Oleg Lelchuk]

I am still using the same workaround: instead of rv =
efi_global_getenv("ConOut", buf, &sz); I have rv =
efi_global_getenv("ConIn", buf, &sz);
Happy New Year!

On Mon, May 15, 2023 at 8:41 AM Oleg Lelchuk  wrote:

> I got it.
>
> On Mon, May 15, 2023, 8:32 AM Toomas Soome  wrote:
>
>>
>>
>> On 15. May 2023, at 15:22, Oleg Lelchuk  wrote:
>>
>> Adding screen.font="16×32" to loader.conf fixed that tiny issue mentioned
>> in the previous email message... I find it a bit surprising that I only had
>> to make one tiny change to the source code of stand to make the graphical
>> logo appear, to start playing with the EFI resolution, and etc.
>>
>>
>> The font size/resolution is difficult topic. The implementation itself
>> can choose “good enough” variant and then some people are happy and some
>> people are unhappy.
>>
>> The current loader UI is built on terminal dimensions (which depend on
>> glyph size and resolution), and there the traditional assumption is that we
>> have 80x24 terminal. With different fonts and depending on how much screen
>> space we want to leave unused, we can get different dimensions for terminal.
>>
>> And since there is quite a variation of displays, the challenge is to get
>> decent enough visual on most commonly used displays - so there can be
>> pressure to use fixed resolution etc. And this is also the reason, why you
>> see very simple boot screens with something like spinning wheel on some
>> other systems.
>>
>> rgds,
>> toomas
>>
>>
>> On Sun, May 14, 2023, 8:58 AM Oleg Lelchuk  wrote:
>>
>>> Okay, so I edited /usr/src/stand/efi/loader/main.c , and I replaced
>>> ConOut with ConIn in this line: rv = efi_global_getenv("ConIn", buf, &sz);
>>> . Now I am able to see the beautiful graphical logo in the efi boot menu!
>>> But why are the boot menu and the logo shown in the top left corner of my
>>> computer screen? My monitor is 1080p and the setting
>>> efi_max_resolution=1080p in loader.conf only affects what happens after the
>>> kernel starts booting up, but it doesn't affect what happens before it: the
>>> boot menu and the logo remain in the top left corner of the screen. Why is
>>> this the case? You can see the photo in the provided attachment... And
>>> thank you, guys, for your work!
>>>
>>> On Sat, May 13, 2023 at 9:35 AM Warner Losh  wrote:
>>>


 On Sat, May 13, 2023, 6:26 AM Oleg Lelchuk 
 wrote:

> I've been reading the documentation for loader.efi and it says this:
> "If there is no ConOut variable, both serial and video are attempted.
>  loader.efi uses the "efi" console for the video (which may or may
> not
>  work) and "comconsole" for the serial on COM1 at the default baud
> rate.
>  The kernel will use a dual console, with the video console
> primary if a
>  UEFI graphics device is detected, or the serial console as
> primary if
>  not."
> I find this language confusing because I don't know what is meant by
> "a UEFI graphics device". In my situation, is my Intel Integrated Graphics
> card an UEFI graphics device? Does it mean that once i915kms is loaded, I
> no longer deal with UEFI graphics? I think lots of people whose native
> language is English will find the documentation describing loader.efi
> confusing. The documentation page also mentions this: "BUGS
>  Systems that do not have a ConOut variable set are not conformant
> with
>  the standard, and likely have unexpected results." But I think
> you guys already implied that the UEFI specification doesn't mandate 
> having
> such a variable.
>

 That's unclear. The standard refers to it many times. Earlier versions
 especially. It doesn't say it's optional, unlike some other variables. Yet
 later versions don't say it's mandatory.  I've yet to own or use a system
 without it... such systems exist but they are quite new...

 Warner

 On Fri, May 12, 2023 at 7:55 PM Oleg Lelchuk 
> wrote:
>
>> I got it. Thanks.
>>
>> On Fri, May 12, 2023 at 7:45 PM Ed Maste  wrote:
>>
>>> On Fri, 12 May 2023 at 09:26, Oleg Lelchuk 
>>> wrote:
>>> >
>>> > 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.
>>>
>>> This issue is tracked in PR 265980 if you want to follow it.
>>> https://bugs.freebsd.org/265980
>>>
>>
>>

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?

[Oleg Lelchuk]

I got it.

On Mon, May 15, 2023, 8:32 AM Toomas Soome  wrote:

>
>
> On 15. May 2023, at 15:22, Oleg Lelchuk  wrote:
>
> Adding screen.font="16×32" to loader.conf fixed that tiny issue mentioned
> in the previous email message... I find it a bit surprising that I only had
> to make one tiny change to the source code of stand to make the graphical
> logo appear, to start playing with the EFI resolution, and etc.
>
>
> The font size/resolution is difficult topic. The implementation itself can
> choose “good enough” variant and then some people are happy and some people
> are unhappy.
>
> The current loader UI is built on terminal dimensions (which depend on
> glyph size and resolution), and there the traditional assumption is that we
> have 80x24 terminal. With different fonts and depending on how much screen
> space we want to leave unused, we can get different dimensions for terminal.
>
> And since there is quite a variation of displays, the challenge is to get
> decent enough visual on most commonly used displays - so there can be
> pressure to use fixed resolution etc. And this is also the reason, why you
> see very simple boot screens with something like spinning wheel on some
> other systems.
>
> rgds,
> toomas
>
>
> On Sun, May 14, 2023, 8:58 AM Oleg Lelchuk  wrote:
>
>> Okay, so I edited /usr/src/stand/efi/loader/main.c , and I replaced
>> ConOut with ConIn in this line: rv = efi_global_getenv("ConIn", buf, &sz);
>> . Now I am able to see the beautiful graphical logo in the efi boot menu!
>> But why are the boot menu and the logo shown in the top left corner of my
>> computer screen? My monitor is 1080p and the setting
>> efi_max_resolution=1080p in loader.conf only affects what happens after the
>> kernel starts booting up, but it doesn't affect what happens before it: the
>> boot menu and the logo remain in the top left corner of the screen. Why is
>> this the case? You can see the photo in the provided attachment... And
>> thank you, guys, for your work!
>>
>> On Sat, May 13, 2023 at 9:35 AM Warner Losh  wrote:
>>
>>>
>>>
>>> On Sat, May 13, 2023, 6:26 AM Oleg Lelchuk 
>>> wrote:
>>>
 I've been reading the documentation for loader.efi and it says this:
 "If there is no ConOut variable, both serial and video are attempted.
  loader.efi uses the "efi" console for the video (which may or may
 not
  work) and "comconsole" for the serial on COM1 at the default baud
 rate.
  The kernel will use a dual console, with the video console primary
 if a
  UEFI graphics device is detected, or the serial console as primary
 if
  not."
 I find this language confusing because I don't know what is meant by "a
 UEFI graphics device". In my situation, is my Intel Integrated Graphics
 card an UEFI graphics device? Does it mean that once i915kms is loaded, I
 no longer deal with UEFI graphics? I think lots of people whose native
 language is English will find the documentation describing loader.efi
 confusing. The documentation page also mentions this: "BUGS
  Systems that do not have a ConOut variable set are not conformant
 with
  the standard, and likely have unexpected results." But I think you
 guys already implied that the UEFI specification doesn't mandate having
 such a variable.

>>>
>>> That's unclear. The standard refers to it many times. Earlier versions
>>> especially. It doesn't say it's optional, unlike some other variables. Yet
>>> later versions don't say it's mandatory.  I've yet to own or use a system
>>> without it... such systems exist but they are quite new...
>>>
>>> Warner
>>>
>>> On Fri, May 12, 2023 at 7:55 PM Oleg Lelchuk 
 wrote:

> I got it. Thanks.
>
> On Fri, May 12, 2023 at 7:45 PM Ed Maste  wrote:
>
>> On Fri, 12 May 2023 at 09:26, Oleg Lelchuk 
>> wrote:
>> >
>> > 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.
>>
>> This issue is tracked in PR 265980 if you want to follow it.
>> https://bugs.freebsd.org/265980
>>
>
>

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?

[Toomas Soome]

> On 15. May 2023, at 15:22, Oleg Lelchuk  wrote:
> 
> Adding screen.font="16×32" to loader.conf fixed that tiny issue mentioned in 
> the previous email message... I find it a bit surprising that I only had to 
> make one tiny change to the source code of stand to make the graphical logo 
> appear, to start playing with the EFI resolution, and etc.

The font size/resolution is difficult topic. The implementation itself can 
choose “good enough” variant and then some people are happy and some people are 
unhappy.

The current loader UI is built on terminal dimensions (which depend on glyph 
size and resolution), and there the traditional assumption is that we have 
80x24 terminal. With different fonts and depending on how much screen space we 
want to leave unused, we can get different dimensions for terminal.

And since there is quite a variation of displays, the challenge is to get 
decent enough visual on most commonly used displays - so there can be pressure 
to use fixed resolution etc. And this is also the reason, why you see very 
simple boot screens with something like spinning wheel on some other systems.

rgds,
toomas

> 
> On Sun, May 14, 2023, 8:58 AM Oleg Lelchuk  > wrote:
>> Okay, so I edited /usr/src/stand/efi/loader/main.c , and I replaced ConOut 
>> with ConIn in this line: rv = efi_global_getenv("ConIn", buf, &sz); . Now I 
>> am able to see the beautiful graphical logo in the efi boot menu! But why 
>> are the boot menu and the logo shown in the top left corner of my computer 
>> screen? My monitor is 1080p and the setting efi_max_resolution=1080p in 
>> loader.conf only affects what happens after the kernel starts booting up, 
>> but it doesn't affect what happens before it: the boot menu and the logo 
>> remain in the top left corner of the screen. Why is this the case? You can 
>> see the photo in the provided attachment... And thank you, guys, for your 
>> work!
>> 
>> On Sat, May 13, 2023 at 9:35 AM Warner Losh > > wrote:
>>> 
>>> 
>>> On Sat, May 13, 2023, 6:26 AM Oleg Lelchuk >> > wrote:
 I've been reading the documentation for loader.efi and it says this: "If 
 there is no ConOut variable, both serial and video are attempted.
  loader.efi uses the "efi" console for the video (which may or may not
  work) and "comconsole" for the serial on COM1 at the default baud 
 rate.
  The kernel will use a dual console, with the video console primary if 
 a
  UEFI graphics device is detected, or the serial console as primary if
  not."
 I find this language confusing because I don't know what is meant by "a 
 UEFI graphics device". In my situation, is my Intel Integrated Graphics 
 card an UEFI graphics device? Does it mean that once i915kms is loaded, I 
 no longer deal with UEFI graphics? I think lots of people whose native 
 language is English will find the documentation describing loader.efi 
 confusing. The documentation page also mentions this: "BUGS
  Systems that do not have a ConOut variable set are not conformant with
  the standard, and likely have unexpected results." But I think you 
 guys already implied that the UEFI specification doesn't mandate having 
 such a variable.
>>> 
>>> 
>>> That's unclear. The standard refers to it many times. Earlier versions 
>>> especially. It doesn't say it's optional, unlike some other variables. Yet 
>>> later versions don't say it's mandatory.  I've yet to own or use a system 
>>> without it... such systems exist but they are quite new...
>>> 
>>> Warner
>>> 
 On Fri, May 12, 2023 at 7:55 PM Oleg Lelchuk >>> > wrote:
> I got it. Thanks.
> 
> On Fri, May 12, 2023 at 7:45 PM Ed Maste  > wrote:
>> On Fri, 12 May 2023 at 09:26, Oleg Lelchuk > > wrote:
>> >
>> > 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.
>> 
>> This issue is tracked in PR 265980 if you want to follow it.
>> https://bugs.freebsd.org/265980

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?

[Oleg Lelchuk]

Adding screen.font="16×32" to loader.conf fixed that tiny issue mentioned
in the previous email message... I find it a bit surprising that I only had
to make one tiny change to the source code of stand to make the graphical
logo appear, to start playing with the EFI resolution, and etc.

On Sun, May 14, 2023, 8:58 AM Oleg Lelchuk  wrote:

> Okay, so I edited /usr/src/stand/efi/loader/main.c , and I replaced ConOut
> with ConIn in this line: rv = efi_global_getenv("ConIn", buf, &sz); . Now I
> am able to see the beautiful graphical logo in the efi boot menu! But why
> are the boot menu and the logo shown in the top left corner of my computer
> screen? My monitor is 1080p and the setting efi_max_resolution=1080p in
> loader.conf only affects what happens after the kernel starts booting up,
> but it doesn't affect what happens before it: the boot menu and the logo
> remain in the top left corner of the screen. Why is this the case? You can
> see the photo in the provided attachment... And thank you, guys, for your
> work!
>
> On Sat, May 13, 2023 at 9:35 AM Warner Losh  wrote:
>
>>
>>
>> On Sat, May 13, 2023, 6:26 AM Oleg Lelchuk  wrote:
>>
>>> I've been reading the documentation for loader.efi and it says this: "If
>>> there is no ConOut variable, both serial and video are attempted.
>>>  loader.efi uses the "efi" console for the video (which may or may
>>> not
>>>  work) and "comconsole" for the serial on COM1 at the default baud
>>> rate.
>>>  The kernel will use a dual console, with the video console primary
>>> if a
>>>  UEFI graphics device is detected, or the serial console as primary
>>> if
>>>  not."
>>> I find this language confusing because I don't know what is meant by "a
>>> UEFI graphics device". In my situation, is my Intel Integrated Graphics
>>> card an UEFI graphics device? Does it mean that once i915kms is loaded, I
>>> no longer deal with UEFI graphics? I think lots of people whose native
>>> language is English will find the documentation describing loader.efi
>>> confusing. The documentation page also mentions this: "BUGS
>>>  Systems that do not have a ConOut variable set are not conformant
>>> with
>>>  the standard, and likely have unexpected results." But I think you
>>> guys already implied that the UEFI specification doesn't mandate having
>>> such a variable.
>>>
>>
>> That's unclear. The standard refers to it many times. Earlier versions
>> especially. It doesn't say it's optional, unlike some other variables. Yet
>> later versions don't say it's mandatory.  I've yet to own or use a system
>> without it... such systems exist but they are quite new...
>>
>> Warner
>>
>> On Fri, May 12, 2023 at 7:55 PM Oleg Lelchuk 
>>> wrote:
>>>
 I got it. Thanks.

 On Fri, May 12, 2023 at 7:45 PM Ed Maste  wrote:

> On Fri, 12 May 2023 at 09:26, Oleg Lelchuk 
> wrote:
> >
> > 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.
>
> This issue is tracked in PR 265980 if you want to follow it.
> https://bugs.freebsd.org/265980
>

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?

[Warner Losh]

On Sat, May 13, 2023, 6:26 AM Oleg Lelchuk  wrote:

> I've been reading the documentation for loader.efi and it says this: "If
> there is no ConOut variable, both serial and video are attempted.
>  loader.efi uses the "efi" console for the video (which may or may not
>  work) and "comconsole" for the serial on COM1 at the default baud
> rate.
>  The kernel will use a dual console, with the video console primary if
> a
>  UEFI graphics device is detected, or the serial console as primary if
>  not."
> I find this language confusing because I don't know what is meant by "a
> UEFI graphics device". In my situation, is my Intel Integrated Graphics
> card an UEFI graphics device? Does it mean that once i915kms is loaded, I
> no longer deal with UEFI graphics? I think lots of people whose native
> language is English will find the documentation describing loader.efi
> confusing. The documentation page also mentions this: "BUGS
>  Systems that do not have a ConOut variable set are not conformant with
>  the standard, and likely have unexpected results." But I think you
> guys already implied that the UEFI specification doesn't mandate having
> such a variable.
>

That's unclear. The standard refers to it many times. Earlier versions
especially. It doesn't say it's optional, unlike some other variables. Yet
later versions don't say it's mandatory.  I've yet to own or use a system
without it... such systems exist but they are quite new...

Warner

On Fri, May 12, 2023 at 7:55 PM Oleg Lelchuk  wrote:
>
>> I got it. Thanks.
>>
>> On Fri, May 12, 2023 at 7:45 PM Ed Maste  wrote:
>>
>>> On Fri, 12 May 2023 at 09:26, Oleg Lelchuk 
>>> wrote:
>>> >
>>> > 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.
>>>
>>> This issue is tracked in PR 265980 if you want to follow it.
>>> https://bugs.freebsd.org/265980
>>>
>>

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?

[Oleg Lelchuk]

I've been reading the documentation for loader.efi and it says this: "If
there is no ConOut variable, both serial and video are attempted.
 loader.efi uses the "efi" console for the video (which may or may not
 work) and "comconsole" for the serial on COM1 at the default baud rate.
 The kernel will use a dual console, with the video console primary if a
 UEFI graphics device is detected, or the serial console as primary if
 not."
I find this language confusing because I don't know what is meant by "a
UEFI graphics device". In my situation, is my Intel Integrated Graphics
card an UEFI graphics device? Does it mean that once i915kms is loaded, I
no longer deal with UEFI graphics? I think lots of people whose native
language is English will find the documentation describing loader.efi
confusing. The documentation page also mentions this: "BUGS
 Systems that do not have a ConOut variable set are not conformant with
 the standard, and likely have unexpected results." But I think you
guys already implied that the UEFI specification doesn't mandate having
such a variable.

On Fri, May 12, 2023 at 7:55 PM Oleg Lelchuk  wrote:

> I got it. Thanks.
>
> On Fri, May 12, 2023 at 7:45 PM Ed Maste  wrote:
>
>> On Fri, 12 May 2023 at 09:26, Oleg Lelchuk  wrote:
>> >
>> > 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.
>>
>> This issue is tracked in PR 265980 if you want to follow it.
>> https://bugs.freebsd.org/265980
>>
>

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?

[Oleg Lelchuk]

I got it. Thanks.

On Fri, May 12, 2023 at 7:45 PM Ed Maste  wrote:

> On Fri, 12 May 2023 at 09:26, Oleg Lelchuk  wrote:
> >
> > 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.
>
> This issue is tracked in PR 265980 if you want to follow it.
> https://bugs.freebsd.org/265980
>

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?

[Ed Maste]

On Fri, 12 May 2023 at 09:26, Oleg Lelchuk  wrote:
>
> 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.

This issue is tracked in PR 265980 if you want to follow it.
https://bugs.freebsd.org/265980

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?

[Oleg Lelchuk]

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  
>>>
>>
>>
>

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?

[Toomas Soome]

> 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  <mailto:tso...@me.com>> wrote:
>> 
>> 
>>> On 12. May 2023, at 13:41, Oleg Lelchuk >> <mailto:oleglelc...@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 vendor, that may fix 
>> the missing ConOut.
>> 
>> rgds,
>> toomas
>> 
>> 
>>> 
>>> On Fri, May 12, 2023, 1:06 AM Emmanuel Vadot >> <mailto:m...@bidouilliste.com>> wrote:
>>>> On Fri, 12 May 2023 00:20:47 +0300
>>>> Toomas Soome mailto:tso...@me.com>> wrote:
>>>> 
>>>> > 
>>>> > 
>>>> > > On 12. May 2023, at 00:11, Oleg Lelchuk >>> > > <mailto:oleglelc...@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 
>>>> > > 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 mailto:m...@bidouilliste.com>> 
>>>> mailto:m...@freebsd.org>>
>> 

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?

[Oleg Lelchuk]

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!

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  
>>
>
>

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?

[Toomas Soome]

> 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  <mailto:m...@bidouilliste.com>> wrote:
>> On Fri, 12 May 2023 00:20:47 +0300
>> Toomas Soome mailto:tso...@me.com>> wrote:
>> 
>> > 
>> > 
>> > > On 12. May 2023, at 00:11, Oleg Lelchuk > > > <mailto:oleglelc...@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 
>> > > 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 mailto:m...@bidouilliste.com>> 
>> mailto:m...@freebsd.org>>

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?

[Oleg Lelchuk]

There is only one monitor connected to my PC.

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  
>

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?

[Emmanuel Vadot]

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  

Fwd: 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?

[Oleg Lelchuk]

-- Forwarded message -
From: Oleg Lelchuk 
Date: Thu, May 11, 2023 at 10:19 PM
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 


I see this output:
efivar --device-path 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConIn
8be4df61-93ca-11d2-aa0d-00e098032b8c-ConIn
:
PciRoot(0x0)/Pci(0x1f,0x0)/Acpi(PNP0303,0x0),/PciRoot(0x0)/Pci(0x14,0x0)/USB(0x2,0x0)

On Thu, May 11, 2023 at 9:54 PM Warner Losh  wrote:

> No ConOut variable -> we assume the widest possible amount of hardware.
> which is why you see efi comconsole as the console.
>
> Can you send me the output of
> efivar --device-path 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConIn
>
> It should look like:
> 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConIn
> :
> PciRoot(0x0)/Pci(0x1f,0x0)/Acpi(PNP0303,0x0),/PciRoot(0x0)/Pci(0x1f,0x0)/Acpi(PNP0303,0x1)
>
> I've been putting-off falling back to ConIn to determine the default
> console device. I'd like
> to collect a few more examples before I start.
>
> Warner
>
> On Thu, May 11, 2023 at 4: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 PM 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 to
>>> the main branch:
>>> https://cgit.freebsd.org/src/commit/?id=c16e08e5f324aa119c85e10eaabacbd2abdb40e0
>>> .
>>> I get this output:
>>> kenv | grep efi
>>> console="efi,comconsole"
>>> efi-version="2.70"
>>> efi_com_port="0"
>>> efi_com_speed="0"
>>> efi_max_resolution="1x1"
>>> entropy_efi_seed="YES"
>>> loader.efi="1"
>>>
>>> And in the attachment, you can see the output from the loader prompt.
>>>
>>>
>>> On Thu, May 11, 2023 at 6:20 PM Toomas Soome  wrote:
>>>
>>>>
>>>>
>>>> On 12. May 2023, at 01:09, Oleg Lelchuk  wrote:
>>>>
>>>> kenv | grep screen produces this output:
>>>>
>>>> screensave_load="NO"
>>>> screensave_name="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 ‘gop get’ or ‘gop list’ 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 PM 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="/boot/acpi_dsdt.aml"
>>>>> boot_verbose="YES"
>>>>> bootenv_autolist="YES"
>>>>> bootenvs[0]="zfs:DESKTOP/poudriere"
>>>>> bootenvs_count="1"
>>>>> bootfile="kernel"
>>>>> cpu_microcode_name="/boot/firmware/ucode.bin"
>>>>> entropy_cache_name="/boot/entropy"
>>>>> entropy_cache_type="boot_entropy_cache"
>>>>> if_re_name="/boot/modules/if_re.ko"
>>>>> kernel_path="/boot/kernel"
>>>>> kernelname="/boot/kernel/kernel"
>>>>> loader_conf_dirs="/boot/loader.conf.d"
>>>>> module_path="/boot/kernel;/boot/modules;/boot/dtb;/boot/dtb/overlays"
>>>>> nextboot_conf="/boot/nextboot.conf"
>>>>> ram_blacklist_name="/boot/blacklist.txt"
>>>>>
>>

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?

[Warner Losh]

No ConOut variable -> we assume the widest possible amount of hardware.
which is why you see efi comconsole as the console.

Can you send me the output of
efivar --device-path 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConIn

It should look like:
8be4df61-93ca-11d2-aa0d-00e098032b8c-ConIn
:
PciRoot(0x0)/Pci(0x1f,0x0)/Acpi(PNP0303,0x0),/PciRoot(0x0)/Pci(0x1f,0x0)/Acpi(PNP0303,0x1)

I've been putting-off falling back to ConIn to determine the default
console device. I'd like
to collect a few more examples before I start.

Warner

On Thu, May 11, 2023 at 4: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 PM 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 to
>> the main branch:
>> https://cgit.freebsd.org/src/commit/?id=c16e08e5f324aa119c85e10eaabacbd2abdb40e0
>> .
>> I get this output:
>> kenv | grep efi
>> console="efi,comconsole"
>> efi-version="2.70"
>> efi_com_port="0"
>> efi_com_speed="0"
>> efi_max_resolution="1x1"
>> entropy_efi_seed="YES"
>> loader.efi="1"
>>
>> And in the attachment, you can see the output from the loader prompt.
>>
>>
>> On Thu, May 11, 2023 at 6:20 PM Toomas Soome  wrote:
>>
>>>
>>>
>>> On 12. May 2023, at 01:09, Oleg Lelchuk  wrote:
>>>
>>> kenv | grep screen produces this output:
>>>
>>> screensave_load="NO"
>>> screensave_name="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 ‘gop get’ or ‘gop list’ 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 PM 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="/boot/acpi_dsdt.aml"
>>>> boot_verbose="YES"
>>>> bootenv_autolist="YES"
>>>> bootenvs[0]="zfs:DESKTOP/poudriere"
>>>> bootenvs_count="1"
>>>> bootfile="kernel"
>>>> cpu_microcode_name="/boot/firmware/ucode.bin"
>>>> entropy_cache_name="/boot/entropy"
>>>> entropy_cache_type="boot_entropy_cache"
>>>> if_re_name="/boot/modules/if_re.ko"
>>>> kernel_path="/boot/kernel"
>>>> kernelname="/boot/kernel/kernel"
>>>> loader_conf_dirs="/boot/loader.conf.d"
>>>> module_path="/boot/kernel;/boot/modules;/boot/dtb;/boot/dtb/overlays"
>>>> nextboot_conf="/boot/nextboot.conf"
>>>> ram_blacklist_name="/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 PM Warner Losh  wrote:
>>>>
>>>>>
>>>>>
>>>>> On Thu, May 11, 2023 at 3:21 PM 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).
>>>>>>
>>>>>
>>>>> 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(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(0x80010100)
>>>>>
>>>>> if not.
>>>>>
>>>>> Warner
>>>>>
>>>>
>>>>
>>>

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?

[Oleg Lelchuk]

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 PM 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 to
>> the main branch:
>> https://cgit.freebsd.org/src/commit/?id=c16e08e5f324aa119c85e10eaabacbd2abdb40e0
>> .
>> I get this output:
>> kenv | grep efi
>> console="efi,comconsole"
>> efi-version="2.70"
>> efi_com_port="0"
>> efi_com_speed="0"
>> efi_max_resolution="1x1"
>> entropy_efi_seed="YES"
>> loader.efi="1"
>>
>> And in the attachment, you can see the output from the loader prompt.
>>
>>
>> On Thu, May 11, 2023 at 6:20 PM Toomas Soome  wrote:
>>
>>>
>>>
>>> On 12. May 2023, at 01:09, Oleg Lelchuk  wrote:
>>>
>>> kenv | grep screen produces this output:
>>>
>>> screensave_load="NO"
>>> screensave_name="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 ‘gop get’ or ‘gop list’ 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 PM 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="/boot/acpi_dsdt.aml"
>>>> boot_verbose="YES"
>>>> bootenv_autolist="YES"
>>>> bootenvs[0]="zfs:DESKTOP/poudriere"
>>>> bootenvs_count="1"
>>>> bootfile="kernel"
>>>> cpu_microcode_name="/boot/firmware/ucode.bin"
>>>> entropy_cache_name="/boot/entropy"
>>>> entropy_cache_type="boot_entropy_cache"
>>>> if_re_name="/boot/modules/if_re.ko"
>>>> kernel_path="/boot/kernel"
>>>> kernelname="/boot/kernel/kernel"
>>>> loader_conf_dirs="/boot/loader.conf.d"
>>>> module_path="/boot/kernel;/boot/modules;/boot/dtb;/boot/dtb/overlays"
>>>> nextboot_conf="/boot/nextboot.conf"
>>>> ram_blacklist_name="/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 PM Warner Losh  wrote:
>>>>
>>>>>
>>>>>
>>>>> On Thu, May 11, 2023 at 3:21 PM 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).
>>>>>>
>>>>>
>>>>> 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(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(0x80010100)
>>>>>
>>>>> if not.
>>>>>
>>>>> Warner
>>>>>
>>>>
>>>>
>>>

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?

[Oleg Lelchuk]

Any, by the way, "show console" also shows "efi,comconsole", just like
"kenv | grep efi" does.

On Thu, May 11, 2023 at 6:40 PM 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 to
> the main branch:
> https://cgit.freebsd.org/src/commit/?id=c16e08e5f324aa119c85e10eaabacbd2abdb40e0
> .
> I get this output:
> kenv | grep efi
> console="efi,comconsole"
> efi-version="2.70"
> efi_com_port="0"
> efi_com_speed="0"
> efi_max_resolution="1x1"
> entropy_efi_seed="YES"
> loader.efi="1"
>
> And in the attachment, you can see the output from the loader prompt.
>
>
> On Thu, May 11, 2023 at 6:20 PM Toomas Soome  wrote:
>
>>
>>
>> On 12. May 2023, at 01:09, Oleg Lelchuk  wrote:
>>
>> kenv | grep screen produces this output:
>>
>> screensave_load="NO"
>> screensave_name="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 ‘gop get’ or ‘gop list’ 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 PM 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="/boot/acpi_dsdt.aml"
>>> boot_verbose="YES"
>>> bootenv_autolist="YES"
>>> bootenvs[0]="zfs:DESKTOP/poudriere"
>>> bootenvs_count="1"
>>> bootfile="kernel"
>>> cpu_microcode_name="/boot/firmware/ucode.bin"
>>> entropy_cache_name="/boot/entropy"
>>> entropy_cache_type="boot_entropy_cache"
>>> if_re_name="/boot/modules/if_re.ko"
>>> kernel_path="/boot/kernel"
>>> kernelname="/boot/kernel/kernel"
>>> loader_conf_dirs="/boot/loader.conf.d"
>>> module_path="/boot/kernel;/boot/modules;/boot/dtb;/boot/dtb/overlays"
>>> nextboot_conf="/boot/nextboot.conf"
>>> ram_blacklist_name="/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 PM Warner Losh  wrote:
>>>
>>>>
>>>>
>>>> On Thu, May 11, 2023 at 3:21 PM 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).
>>>>>
>>>>
>>>> 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(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(0x80010100)
>>>>
>>>> if not.
>>>>
>>>> Warner
>>>>
>>>
>>>
>>

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?

[Toomas Soome]

> On 12. May 2023, at 01:09, Oleg Lelchuk  wrote:
> 
> kenv | grep screen produces this output:
> 
> screensave_load="NO"
> screensave_name="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 ‘gop get’ or ‘gop list’ 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 PM Toomas Soome  <mailto:tso...@me.com>> wrote:
>> 
>> 
>>> On 12. May 2023, at 00:57, Oleg Lelchuk >> <mailto:oleglelc...@gmail.com>> 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="/boot/acpi_dsdt.aml"
>>> boot_verbose="YES"
>>> bootenv_autolist="YES"
>>> bootenvs[0]="zfs:DESKTOP/poudriere"
>>> bootenvs_count="1"
>>> bootfile="kernel"
>>> cpu_microcode_name="/boot/firmware/ucode.bin"
>>> entropy_cache_name="/boot/entropy"
>>> entropy_cache_type="boot_entropy_cache"
>>> if_re_name="/boot/modules/if_re.ko"
>>> kernel_path="/boot/kernel"
>>> kernelname="/boot/kernel/kernel"
>>> loader_conf_dirs="/boot/loader.conf.d"
>>> module_path="/boot/kernel;/boot/modules;/boot/dtb;/boot/dtb/overlays"
>>> nextboot_conf="/boot/nextboot.conf"
>>> ram_blacklist_name="/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 PM Warner Losh >> <mailto:i...@bsdimp.com>> wrote:
>>>> 
>>>> 
>>>> On Thu, May 11, 2023 at 3:21 PM Toomas Soome >>> <mailto:tso...@me.com>> wrote:
>>>>> 
>>>>> 
>>>>> > On 12. May 2023, at 00:11, Oleg Lelchuk >>>> > <mailto:oleglelc...@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 
>>>>> > 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).
>>>> 
>>>> 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(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(0x80010100)
>>>> 
>>>> if not.
>>>> 
>>>> Warner
>> 

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?

[Oleg Lelchuk]

kenv | grep screen produces this output:

screensave_load="NO"
screensave_name="green_saver"

On Thu, May 11, 2023 at 6:06 PM 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="/boot/acpi_dsdt.aml"
> boot_verbose="YES"
> bootenv_autolist="YES"
> bootenvs[0]="zfs:DESKTOP/poudriere"
> bootenvs_count="1"
> bootfile="kernel"
> cpu_microcode_name="/boot/firmware/ucode.bin"
> entropy_cache_name="/boot/entropy"
> entropy_cache_type="boot_entropy_cache"
> if_re_name="/boot/modules/if_re.ko"
> kernel_path="/boot/kernel"
> kernelname="/boot/kernel/kernel"
> loader_conf_dirs="/boot/loader.conf.d"
> module_path="/boot/kernel;/boot/modules;/boot/dtb;/boot/dtb/overlays"
> nextboot_conf="/boot/nextboot.conf"
> ram_blacklist_name="/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 PM Warner Losh  wrote:
>
>>
>>
>> On Thu, May 11, 2023 at 3:21 PM 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).
>>>
>>
>> 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(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(0x80010100)
>>
>> if not.
>>
>> Warner
>>
>
>

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?

[Toomas Soome]

> 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="/boot/acpi_dsdt.aml"
> boot_verbose="YES"
> bootenv_autolist="YES"
> bootenvs[0]="zfs:DESKTOP/poudriere"
> bootenvs_count="1"
> bootfile="kernel"
> cpu_microcode_name="/boot/firmware/ucode.bin"
> entropy_cache_name="/boot/entropy"
> entropy_cache_type="boot_entropy_cache"
> if_re_name="/boot/modules/if_re.ko"
> kernel_path="/boot/kernel"
> kernelname="/boot/kernel/kernel"
> loader_conf_dirs="/boot/loader.conf.d"
> module_path="/boot/kernel;/boot/modules;/boot/dtb;/boot/dtb/overlays"
> nextboot_conf="/boot/nextboot.conf"
> ram_blacklist_name="/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 PM Warner Losh  <mailto:i...@bsdimp.com>> wrote:
>> 
>> 
>> On Thu, May 11, 2023 at 3:21 PM Toomas Soome > <mailto:tso...@me.com>> wrote:
>>> 
>>> 
>>> > On 12. May 2023, at 00:11, Oleg Lelchuk >> > <mailto:oleglelc...@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 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).
>> 
>> 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(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(0x80010100)
>> 
>> if not.
>> 
>> Warner

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?

[Oleg Lelchuk]

kenv | grep boot shows me this:

acpi_dsdt_name="/boot/acpi_dsdt.aml"
boot_verbose="YES"
bootenv_autolist="YES"
bootenvs[0]="zfs:DESKTOP/poudriere"
bootenvs_count="1"
bootfile="kernel"
cpu_microcode_name="/boot/firmware/ucode.bin"
entropy_cache_name="/boot/entropy"
entropy_cache_type="boot_entropy_cache"
if_re_name="/boot/modules/if_re.ko"
kernel_path="/boot/kernel"
kernelname="/boot/kernel/kernel"
loader_conf_dirs="/boot/loader.conf.d"
module_path="/boot/kernel;/boot/modules;/boot/dtb;/boot/dtb/overlays"
nextboot_conf="/boot/nextboot.conf"
ram_blacklist_name="/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 PM Warner Losh  wrote:

>
>
> On Thu, May 11, 2023 at 3:21 PM 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).
>>
>
> 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(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(0x80010100)
>
> if not.
>
> Warner
>

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?

[Warner Losh]

On Thu, May 11, 2023 at 3:21 PM 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).
>

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(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(0x80010100)

if not.

Warner

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?

[Toomas Soome]

> 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

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?

[Oleg Lelchuk]

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.