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?

On Sat, May 13, 2023, 6:26 AM Oleg Lelchuk <oleglelchuk@gmail.com> 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 <oleglelchuk@gmail.com> wrote:
>
>> I got it. Thanks.
>>
>> On Fri, May 12, 2023 at 7:45 PM Ed Maste <emaste@freebsd.org> wrote:
>>
>>> On Fri, 12 May 2023 at 09:26, Oleg Lelchuk <oleglelchuk@gmail.com>
>>> 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
>>>
>>