Date: Sat, 13 May 2023 08:26:24 -0400 From: Oleg Lelchuk <oleglelchuk@gmail.com> To: Ed Maste <emaste@freebsd.org> Cc: Toomas Soome <tsoome@me.com>, Emmanuel Vadot <manu@bidouilliste.com>, freebsd-current@freebsd.org 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? Message-ID: <CA%2BGqWgumZtyVJTbyfMf2bLypK1Ndw1L1AcQ7LTjnCtvRwAtJtA@mail.gmail.com> In-Reply-To: <CA%2BGqWgsviBD_B_OQHERZd4J6S0chT-F=Rz0kExtUWq9t6QV_dA@mail.gmail.com> References: <CA%2BGqWgudMq%2BeV5OJzuC_zR1Osdrak70PmOpFJqLMk3aDE0wy8w@mail.gmail.com> <3B658415-3AD0-4E8B-8CBE-F13FA70CBDC8@me.com> <20230512070557.859671981b7c616c0da7d666@bidouilliste.com> <CA%2BGqWguYpkm17xTQKN3qgyACpG7MkHPK3jJz=f9tx=zovvaNMA@mail.gmail.com> <4F0D21B1-58B6-413D-8499-11AF0E338C78@me.com> <CA%2BGqWguPT8uxtGhbWBw4kmR34jC7kG-DSMT0SuEm02smaigoEA@mail.gmail.com> <B8A678CB-8E2C-4A4C-852C-3E66C2C3B4B4@me.com> <CA%2BGqWgta5%2B-POUk88Z%2B-_FtcJouvLZpu5vYQ6kfX1DGwwjeCXw@mail.gmail.com> <CAPyFy2A4cW4SnFLEypM31JMDJT=A=vMh%2BW5g%2BO2gigf5OWDKrA@mail.gmail.com> <CA%2BGqWgsviBD_B_OQHERZd4J6S0chT-F=Rz0kExtUWq9t6QV_dA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--0000000000001a670705fb9255b6
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
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=E2=80=AFPM Oleg Lelchuk <oleglelchuk@gmail.com=
> wrote:
> I got it. Thanks.
>
> On Fri, May 12, 2023 at 7:45=E2=80=AFPM Ed Maste <emaste@freebsd.org> wro=
te:
>
>> 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. Than=
k
>> 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
>>
>
--0000000000001a670705fb9255b6
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">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.<br>=C2=A0 =C2=A0 =C2=A0loader.efi uses the "efi" c=
onsole for the video (which may or may not<br>=C2=A0 =C2=A0 =C2=A0work) and=
"comconsole" for the serial on COM1 at the default baud rate.<br=
>=C2=A0 =C2=A0 =C2=A0The kernel will use a dual console, with the video con=
sole primary if a<br>=C2=A0 =C2=A0 =C2=A0UEFI graphics device is detected, =
or the serial console as primary if<br>=C2=A0 =C2=A0 =C2=A0not."<div>I=
find this language confusing because I don't know what is meant by &qu=
ot;a UEFI graphics device". In my situation, is my Intel Integrated Gr=
aphics card an UEFI graphics device? Does it mean that once i915kms is load=
ed, I no longer deal with UEFI graphics? I think lots of people whose nativ=
e language is English will find the documentation describing loader.efi con=
fusing. The documentation page also mentions this: "BUGS</div>=C2=A0 =
=C2=A0 =C2=A0Systems that do not have a ConOut variable set are not conform=
ant with<br>=C2=A0 =C2=A0 =C2=A0the standard, and likely have unexpected re=
sults." But I think you guys already implied that the UEFI specificati=
on doesn't mandate having such a variable.</div><br><div class=3D"gmail=
_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, May 12, 2023 at 7:55=
=E2=80=AFPM Oleg Lelchuk <<a href=3D"mailto:oleglelchuk@gmail.com">olegl=
elchuk@gmail.com</a>> wrote:<br></div><blockquote class=3D"gmail_quote" =
style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);pa=
dding-left:1ex"><div dir=3D"ltr">I got it. Thanks.</div><br><div class=3D"g=
mail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, May 12, 2023 at 7=
:45=E2=80=AFPM Ed Maste <<a href=3D"mailto:emaste@freebsd.org" target=3D=
"_blank">emaste@freebsd.org</a>> wrote:<br></div><blockquote class=3D"gm=
ail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,=
204,204);padding-left:1ex">On Fri, 12 May 2023 at 09:26, Oleg Lelchuk <<=
a href=3D"mailto:oleglelchuk@gmail.com" target=3D"_blank">oleglelchuk@gmail=
.com</a>> wrote:<br>
><br>
> I don't want to go through the hassle of filling a bug with my ven=
dor. I will just wait for you, guys, to update the stand implementation. Th=
ank you for explaining to me what causes this issue.<br>
<br>
This issue is tracked in PR 265980 if you want to follow it.<br>
<a href=3D"https://bugs.freebsd.org/265980" rel=3D"noreferrer" target=3D"_b=
lank">https://bugs.freebsd.org/265980</a><br>;
</blockquote></div>
</blockquote></div>
--0000000000001a670705fb9255b6--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2BGqWgumZtyVJTbyfMf2bLypK1Ndw1L1AcQ7LTjnCtvRwAtJtA>