Date: Fri, 12 May 2023 09:26:14 -0400 From: Oleg Lelchuk <oleglelchuk@gmail.com> To: Toomas Soome <tsoome@me.com> Cc: 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%2BGqWgta5%2B-POUk88Z%2B-_FtcJouvLZpu5vYQ6kfX1DGwwjeCXw@mail.gmail.com> In-Reply-To: <B8A678CB-8E2C-4A4C-852C-3E66C2C3B4B4@me.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>
next in thread | previous in thread | raw e-mail | index | archive | help
--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 <tsoome@me.com> wrote: > > > On 12. May 2023, at 14:45, Oleg Lelchuk <oleglelchuk@gmail.com> 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 <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 vendor, that may >> fix the missing ConOut. >> >> rgds, >> toomas >> >> >> >> On Fri, May 12, 2023, 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 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 <manu@bidouilliste.com> <manu@freebsd.org> >>> >> >> > --00000000000051761205fb7f0d54 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"auto">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.</div><br>= <div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, Ma= y 12, 2023, 8:02 AM Toomas Soome <<a href=3D"mailto:tsoome@me.com">tsoom= e@me.com</a>> wrote:<br></div><blockquote class=3D"gmail_quote" style=3D= "margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style= =3D"line-break:after-white-space"><br><div><br><blockquote type=3D"cite"><d= iv>On 12. May 2023, at 14:45, Oleg Lelchuk <<a href=3D"mailto:oleglelchu= k@gmail.com" target=3D"_blank" rel=3D"noreferrer">oleglelchuk@gmail.com</a>= > wrote:</div><br><div><div dir=3D"ltr"><div dir=3D"auto">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=A0<a href=3D"https://www.mail-archive.com/stable@freebsd.org/msg00= 235.html" target=3D"_blank" rel=3D"noreferrer">https://www.mail-archive.com= /stable@freebsd.org/msg00235.html</a> ? 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!</div></div><br></div></blockquote><div><br= ></div><div>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.</div><div><br></div><div>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><= div><br></div><div>rgds,</div><div>toomas</div><br><blockquote type=3D"cite= "><div><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On = Fri, May 12, 2023, 6:55 AM Toomas Soome <<a href=3D"mailto:tsoome@me.com= " target=3D"_blank" rel=3D"noreferrer">tsoome@me.com</a>> wrote:<br></di= v><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;borde= r-left:1px solid rgb(204,204,204);padding-left:1ex"><div><br><div><br><bloc= kquote type=3D"cite"><div>On 12. May 2023, at 13:41, Oleg Lelchuk <<a hr= ef=3D"mailto:oleglelchuk@gmail.com" rel=3D"noreferrer noreferrer" target=3D= "_blank">oleglelchuk@gmail.com</a>> wrote:</div><br><div><div dir=3D"aut= o">There is only one monitor connected to my PC.</div></div></blockquote><d= iv><br></div><div>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.</div><div><br></div><div>rgds,</div><di= v>toomas</div><div><br></div><br><blockquote type=3D"cite"><div><br><div cl= ass=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, May 12, 2= 023, 1:06 AM Emmanuel Vadot <<a href=3D"mailto:manu@bidouilliste.com" re= l=3D"noreferrer noreferrer" target=3D"_blank">manu@bidouilliste.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);padding-left:1ex">On Fri, = 12 May 2023 00:20:47 +0300<br> Toomas Soome <<a href=3D"mailto:tsoome@me.com" rel=3D"noreferrer norefer= rer noreferrer" target=3D"_blank">tsoome@me.com</a>> wrote:<br> <br> > <br> > <br> > > On 12. May 2023, at 00:11, Oleg Lelchuk <<a href=3D"mailto:ole= glelchuk@gmail.com" rel=3D"noreferrer noreferrer noreferrer" target=3D"_bla= nk">oleglelchuk@gmail.com</a>> wrote:<br> > > <br> > > 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.<br> > <br> > 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).<br> > <br> > rgds,<br> > toomas<br> <br> =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.<br> <br> -- <br> Emmanuel Vadot <<a href=3D"mailto:manu@bidouilliste.com" rel=3D"noreferr= er noreferrer noreferrer" target=3D"_blank">manu@bidouilliste.com</a>> &= lt;<a href=3D"mailto:manu@freebsd.org" rel=3D"noreferrer noreferrer norefer= rer" target=3D"_blank">manu@freebsd.org</a>><br> </blockquote></div> </div></blockquote></div><br></div></blockquote></div> </div></blockquote></div><br></div></blockquote></div> --00000000000051761205fb7f0d54--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2BGqWgta5%2B-POUk88Z%2B-_FtcJouvLZpu5vYQ6kfX1DGwwjeCXw>