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?
- Reply: Oleg Lelchuk : "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?"
- In reply to: Oleg Lelchuk : "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?"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Fri, 12 May 2023 12:01:53 UTC
> 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 <mailto:tsoome@me.com>> wrote: >> >> >>> On 12. May 2023, at 13:41, Oleg Lelchuk <oleglelchuk@gmail.com <mailto: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 <mailto:manu@bidouilliste.com>> wrote: >>>> On Fri, 12 May 2023 00:20:47 +0300 >>>> Toomas Soome <tsoome@me.com <mailto:tsoome@me.com>> wrote: >>>> >>>> > >>>> > >>>> > > On 12. May 2023, at 00:11, Oleg Lelchuk <oleglelchuk@gmail.com <mailto: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 <mailto:manu@bidouilliste.com>> <manu@freebsd.org <mailto:manu@freebsd.org>> >>