Date: Sat, 13 May 2023 07:35:12 -0600 From: Warner Losh <imp@bsdimp.com> To: Oleg Lelchuk <oleglelchuk@gmail.com> Cc: Ed Maste <emaste@freebsd.org>, Toomas Soome <tsoome@me.com>, Emmanuel Vadot <manu@bidouilliste.com>, FreeBSD Current <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: <CANCZdforzzd6kwQZ7RVctB5MG1=BU86ot7vBGydCek%2BUV44JOw@mail.gmail.com> In-Reply-To: <CA%2BGqWgumZtyVJTbyfMf2bLypK1Ndw1L1AcQ7LTjnCtvRwAtJtA@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> <CA%2BGqWgumZtyVJTbyfMf2bLypK1Ndw1L1AcQ7LTjnCtvRwAtJtA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--0000000000002f95f405fb934b0f Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 no= t > 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 i= f > a > UEFI graphics device is detected, or the serial console as primary i= f > 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 wi= th > 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=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> wr= ote: >> >>> 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. Tha= nk >>> 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 >>> >> --0000000000002f95f405fb934b0f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"auto"><div><br><br><div class=3D"gmail_quote"><div dir=3D"ltr" = class=3D"gmail_attr">On Sat, May 13, 2023, 6:26 AM Oleg Lelchuk <<a href= =3D"mailto:oleglelchuk@gmail.com">oleglelchuk@gmail.com</a>> wrote:<br><= /div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-le= ft:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr">I've been reading = the documentation for loader.efi and it says this: "If there is no Con= Out variable, both serial and video are attempted.<br>=C2=A0 =C2=A0 =C2=A0l= oader.efi uses the "efi" console 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 us= e a dual console, with the video console 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 "a UEFI graphics device". In my= situation, is my Intel Integrated Graphics card an UEFI graphics device? D= oes it mean that once i915kms is loaded, I no longer deal with UEFI graphic= s? I think lots of people whose native language is English will find the do= cumentation describing loader.efi confusing. The documentation page also me= ntions this: "BUGS</div>=C2=A0 =C2=A0 =C2=A0Systems that do not have a= ConOut variable set are not conformant with<br>=C2=A0 =C2=A0 =C2=A0the sta= ndard, and likely have unexpected results." But I think you guys alrea= dy implied that the UEFI specification doesn't mandate having such a va= riable.</div></blockquote></div></div><div dir=3D"auto"><br></div><div dir= =3D"auto">That's unclear. The standard refers to it many times. Earlier= versions especially. It doesn't say it's optional, unlike some oth= er variables. Yet later versions don't say it's mandatory.=C2=A0 I&= #39;ve yet to own or use a system without it... such systems exist but they= are quite new...</div><div dir=3D"auto"><br></div><div dir=3D"auto">Warner= </div><div dir=3D"auto"><br></div><div dir=3D"auto"><div class=3D"gmail_quo= te"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-lef= t:1px #ccc solid;padding-left:1ex"><div class=3D"gmail_quote"><div dir=3D"l= tr" class=3D"gmail_attr">On Fri, May 12, 2023 at 7:55=E2=80=AFPM Oleg Lelch= uk <<a href=3D"mailto:oleglelchuk@gmail.com" target=3D"_blank" rel=3D"no= referrer">oleglelchuk@gmail.com</a>> wrote:<br></div><blockquote class= =3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg= b(204,204,204);padding-left:1ex"><div dir=3D"ltr">I got it. Thanks.</div><b= r><div class=3D"gmail_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@freeb= sd.org" target=3D"_blank" rel=3D"noreferrer">emaste@freebsd.org</a>> wro= te:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px = 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Fri, 12 M= ay 2023 at 09:26, Oleg Lelchuk <<a href=3D"mailto:oleglelchuk@gmail.com"= target=3D"_blank" rel=3D"noreferrer">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 noreferrer" t= arget=3D"_blank">https://bugs.freebsd.org/265980</a><br>; </blockquote></div> </blockquote></div> </blockquote></div></div></div> --0000000000002f95f405fb934b0f--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdforzzd6kwQZ7RVctB5MG1=BU86ot7vBGydCek%2BUV44JOw>