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?

2023-05-12 Thread Oleg Lelchuk 
I got it. Thanks.

On Fri, May 12, 2023 at 7:45 PM Ed Maste  wrote:

> On Fri, 12 May 2023 at 09:26, Oleg Lelchuk  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
>

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?

2023-05-12 Thread Ed Maste 
On Fri, 12 May 2023 at 09:26, Oleg Lelchuk  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

Re: git: c16e08e5f324 - main - stand/efi: Retire i386 support

2023-05-12 Thread Tomoaki AOKI 
On Fri, 12 May 2023 07:05:37 -0700 (PDT)
"Rodney W. Grimes"  wrote:

> > On Thu, 11 May 2023 23:08:30 +0200
> > Yuri  wrote:
> > 
> > > Warner Losh wrote:
> > > > 
> > > > 
> > > > On Thu, May 11, 2023, 2:50 PM Rodney W. Grimes
> > > > mailto:freebsd-...@gndrsh.dnsmgr.net>>
> > > > wrote:
> > > > 
> > > > > On Thu, May 11, 2023, 2:16 PM Yuri  > > > > wrote:
> > > > >
> > > > > > Warner Losh wrote:
> > > > > > > The branch main has been updated by imp:
> > > > > > >
> > > > > > > URL:
> > > > > >
> > > > 
> > > > https://cgit.FreeBSD.org/src/commit/?id=c16e08e5f324aa119c85e10eaabacbd2abdb40e0
> > > >  
> > > > 
> > > > > > >
> > > > > > > commit c16e08e5f324aa119c85e10eaabacbd2abdb40e0
> > > > > > > Author:? ? ?Warner Losh 
> > > > > > > AuthorDate: 2023-05-11 20:04:12 +
> > > > > > > Commit:? ? ?Warner Losh 
> > > > > > > CommitDate: 2023-05-11 20:06:03 +
> > > > > > >
> > > > > > >? ? ?stand/efi: Retire i386 support
> > > > > > >
> > > > > > >? ? ?Remove the i386 ifdefs and files. It never worked.
> > > > > > >
> > > > > > >? ? ?Sponsored by:? ? ? ? ? ?Netflix
> > > > > > >? ? ?Reviewed by:? ? ? ? ? ? manu, tsoome, kevans
> > > > > > >? ? ?Differential Revision:? https://reviews.freebsd.org/D40012
> > > > 
> > > > > >
> > > > > > As this question seems to be asked a lot on the forums, does
> > > > this mean
> > > > > > we will never support the 32bit efi booting 64bit OS?
> > > > > >
> > > > >
> > > > > Yes. It means we've given up on that. Such environments are rare 
> > > > these
> > > > > days, as far as I know, so unless someone shows up with something 
> > > > that
> > > > > works perfectly with a qemu testing recipe that we can roll it
> > > > into out
> > > > > test bed. Plus some kind of info on real hardware that does this
> > > > that's
> > > > > popular enough to justify inclusion.
> > > > 
> > > > I have only ever seen 1 implementation of x86 32bit efi, and it was
> > > > such a pile of turds I just scrapped the machine.
> > > > 
> > > > 
> > > > That was my experience as well, so I biased my action towards just
> > > > removing it. If it turns out my experience was somehow atypical and
> > > > these are popular and very much robust, I'm open to learning about it.
> > > 
> > > I just noticed that it was asked several times in the last few months
> > > trying to use FreeBSD on not-so-modern and rather exotic hardware; I
> > > don't think we really need that support, but I simply wasn't aware of
> > > efi32 status before this commit, hence I asked :)
> > 
> > Just a FYI.
> > 
> > A subscriber (not me) tried ASUS EeeBook X205TA (manufactured "2015-04")
> > through Mar.18, 2021 to Apr.13, 2021 without luck on freebsd-usrs-jp ML
> > (in Japanese, started from [1], [2] for April).
> > 
> > Atom CPU Z3735F @1.33GHz, 2GB RAM
> 
> That is a 4 core 64 bit CPU, it most likely has a 64bit efi
> implementation.

Exactly. I'd found the info while discussing with the reporter on
freebsd-uses-jp ML at Intel site.

Note that neither boot1.efi nor loader.efi shipped with FreeBSD i386
distribution couldn't boot kernel successfully (built but not working).
So I have no objection for discontinueing the support.


> > Shipped with "Windows 8.1 with Bing (32bit)" installed.
> 
> Probably a good choice to use a 32 bit OS on a machine
> with only 2GB as there is no need for a 64 bit pointer.
> This pretty much applies to any machine with 4GB or
> less of memory 

IIRC, I've read somewhere describing that ASUS EeeBook X205TA has 32bit
UEFI to boot 32bit Windoze, and supports 32bit UEFI boot only.
I've found folowing pages now, different pages I read ATM, though.

 https://github.com/filirnd/x205ta

 https://forums.linuxmint.com/viewtopic.php?t=380177


> 
> > 
> > [1]
> > https://lists.freebsd.org/pipermail/freebsd-users-jp/2021-March/001728.html
> > 
> > [2]
> > https://lists.freebsd.org/pipermail/freebsd-users-jp/2021-April/001746.html
> > 
> > 
> > -- 
> > Tomoaki AOKI]
> > 
> > 
> 
> -- 
> Rod Grimes rgri...@freebsd.org
> 


-- 
Tomoaki AOKI

Re: git: c16e08e5f324 - main - stand/efi: Retire i386 support

2023-05-12 Thread Rodney W. Grimes 
> On Thu, 11 May 2023 23:08:30 +0200
> Yuri  wrote:
> 
> > Warner Losh wrote:
> > > 
> > > 
> > > On Thu, May 11, 2023, 2:50 PM Rodney W. Grimes
> > > mailto:freebsd-...@gndrsh.dnsmgr.net>>
> > > wrote:
> > > 
> > > > On Thu, May 11, 2023, 2:16 PM Yuri  > > > wrote:
> > > >
> > > > > Warner Losh wrote:
> > > > > > The branch main has been updated by imp:
> > > > > >
> > > > > > URL:
> > > > >
> > > 
> > > https://cgit.FreeBSD.org/src/commit/?id=c16e08e5f324aa119c85e10eaabacbd2abdb40e0
> > >  
> > > 
> > > > > >
> > > > > > commit c16e08e5f324aa119c85e10eaabacbd2abdb40e0
> > > > > > Author:? ? ?Warner Losh 
> > > > > > AuthorDate: 2023-05-11 20:04:12 +
> > > > > > Commit:? ? ?Warner Losh 
> > > > > > CommitDate: 2023-05-11 20:06:03 +
> > > > > >
> > > > > >? ? ?stand/efi: Retire i386 support
> > > > > >
> > > > > >? ? ?Remove the i386 ifdefs and files. It never worked.
> > > > > >
> > > > > >? ? ?Sponsored by:? ? ? ? ? ?Netflix
> > > > > >? ? ?Reviewed by:? ? ? ? ? ? manu, tsoome, kevans
> > > > > >? ? ?Differential Revision:? https://reviews.freebsd.org/D40012
> > > 
> > > > >
> > > > > As this question seems to be asked a lot on the forums, does
> > > this mean
> > > > > we will never support the 32bit efi booting 64bit OS?
> > > > >
> > > >
> > > > Yes. It means we've given up on that. Such environments are rare 
> > > these
> > > > days, as far as I know, so unless someone shows up with something 
> > > that
> > > > works perfectly with a qemu testing recipe that we can roll it
> > > into out
> > > > test bed. Plus some kind of info on real hardware that does this
> > > that's
> > > > popular enough to justify inclusion.
> > > 
> > > I have only ever seen 1 implementation of x86 32bit efi, and it was
> > > such a pile of turds I just scrapped the machine.
> > > 
> > > 
> > > That was my experience as well, so I biased my action towards just
> > > removing it. If it turns out my experience was somehow atypical and
> > > these are popular and very much robust, I'm open to learning about it.
> > 
> > I just noticed that it was asked several times in the last few months
> > trying to use FreeBSD on not-so-modern and rather exotic hardware; I
> > don't think we really need that support, but I simply wasn't aware of
> > efi32 status before this commit, hence I asked :)
> 
> Just a FYI.
> 
> A subscriber (not me) tried ASUS EeeBook X205TA (manufactured "2015-04")
> through Mar.18, 2021 to Apr.13, 2021 without luck on freebsd-usrs-jp ML
> (in Japanese, started from [1], [2] for April).
> 
> Atom CPU Z3735F @1.33GHz, 2GB RAM

That is a 4 core 64 bit CPU, it most likely has a 64bit efi
implementation.

> Shipped with "Windows 8.1 with Bing (32bit)" installed.

Probably a good choice to use a 32 bit OS on a machine
with only 2GB as there is no need for a 64 bit pointer.
This pretty much applies to any machine with 4GB or
less of memory 

> 
> [1]
> https://lists.freebsd.org/pipermail/freebsd-users-jp/2021-March/001728.html
> 
> [2]
> https://lists.freebsd.org/pipermail/freebsd-users-jp/2021-April/001746.html
> 
> 
> -- 
> Tomoaki AOKI]
> 
> 

-- 
Rod Grimes rgri...@freebsd.org

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?

2023-05-12 Thread Oleg Lelchuk 
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  wrote:

>
>
> On 12. May 2023, at 14:45, Oleg Lelchuk  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  wrote:
>
>>
>>
>> On 12. May 2023, at 13:41, Oleg Lelchuk  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 
>> wrote:
>>
>>> On Fri, 12 May 2023 00:20:47 +0300
>>> Toomas Soome  wrote:
>>>
>>> >
>>> >
>>> > > On 12. May 2023, at 00:11, Oleg Lelchuk 
>>> 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  
>>>
>>
>>
>

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?

2023-05-12 Thread Toomas Soome 


> On 12. May 2023, at 14:45, Oleg Lelchuk  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  > wrote:
>> 
>> 
>>> On 12. May 2023, at 13:41, Oleg Lelchuk >> > 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 >> > wrote:
 On Fri, 12 May 2023 00:20:47 +0300
 Toomas Soome mailto:tso...@me.com>> wrote:
 
 > 
 > 
 > > On 12. May 2023, at 00:11, Oleg Lelchuk >>> > > > 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 mailto:m...@bidouilliste.com>> 
 mailto:m...@freebsd.org>>
>>

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?

2023-05-12 Thread Oleg Lelchuk 
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!

On Fri, May 12, 2023, 6:55 AM Toomas Soome  wrote:

>
>
> On 12. May 2023, at 13:41, Oleg Lelchuk  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 
> wrote:
>
>> On Fri, 12 May 2023 00:20:47 +0300
>> Toomas Soome  wrote:
>>
>> >
>> >
>> > > On 12. May 2023, at 00:11, Oleg Lelchuk 
>> 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  
>>
>
>

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?

2023-05-12 Thread Toomas Soome 


> On 12. May 2023, at 13:41, Oleg Lelchuk  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  > wrote:
>> On Fri, 12 May 2023 00:20:47 +0300
>> Toomas Soome mailto:tso...@me.com>> wrote:
>> 
>> > 
>> > 
>> > > On 12. May 2023, at 00:11, Oleg Lelchuk > > > > 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 mailto:m...@bidouilliste.com>> 
>> mailto:m...@freebsd.org>>

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?

2023-05-12 Thread Oleg Lelchuk 
There is only one monitor connected to my PC.

On Fri, May 12, 2023, 1:06 AM Emmanuel Vadot  wrote:

> On Fri, 12 May 2023 00:20:47 +0300
> Toomas Soome  wrote:
>
> >
> >
> > > On 12. May 2023, at 00:11, Oleg Lelchuk  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  
>