Re: testers needed: loader: use display pixel density for font autoselection

[Toomas Soome via freebsd-current]

> On 2. Mar 2021, at 20:32, Rodney W. Grimes  
> wrote:
> 
>>> On 26. Feb 2021, at 17:56, Rodney W. Grimes  
>>> wrote:
>>> 
> On 26. Feb 2021, at 05:42, Rodney W. Grimes  
> wrote:
> 
>>> On 23. Feb 2021, at 17:53, Jakob Alvermark  wrote:
>>> 
>>> On 2/23/21 12:27 PM, Toomas Soome via freebsd-current wrote:
 hi!
 
 I have done some work to make font pickup a bit smarter (hopefully 
 better;), but my own ability to test is limited to one bugged 
 supermicro and one MBP with retina display?
 
 The phab link ishttps://reviews.freebsd.org/D28849  
 
 
 I have built loader binaries as well (bios and uefi):
 loader_lua
 loader_lua.efi
> 
> I have tested this on:
>   Lenovo W530
>   Dell E5470
>   Acer Aspire 1410
> 
> all work fine with resonable display resolution.
> 
> One more comment below...
> 
 
 To test, you should remove screen.font= line from loader.conf and test 
 with different resolutions.
 
 thanks,
 toomas
>>> 
>>> 
>>> 
>>> Hi Toomas,
>>> 
>>> 
>>> I tested on five different setups.
>>> 
>>> Surface Pro 10.6"@1920x1080:
>>> 
>>> The loader menu looks different, the "FreeBSD" text is on the right 
>>> side of the screen.
>> 
>> 
>> I think, this was the lua script bug we did fix not too long time ago.
>> 
>>> 
>>> Otherwise, the font size is what I would call a normal size.
>>> 
>>> 
>>> Acer laptop 11.6"@1366x768:
>>> 
>>> Menu looks fine. Almost fills the entire screen.
>>> 
>>> The font feels a little too big.
>> 
>> 
>> The laptop built in displays usually do not give out EDID (we get 
>> physical dimensions from EDID), so there we fall back to try to get 
>> 80x25 terminal method.
> 
> I am having a hard time with that statement.  EDID is very common on 
> laptop screens, infact I can not recall ever not seeing EDID on a laptops 
> builtin screen.
> My 11" acer 1400 has EDID in it.
> 
> 
 
 
 If there is EDID, then it is all good. I have seen cases we do not get it 
 with available API.
>>> 
>>> Is there a way for me to know if the laoder found EDID data or not?
>>> It might be that the issue is that what ever loader is using for an API is 
>>> not working.
>>> I based my "EDID is very common on laptop screens" on the fact that X11 
>>> almost always finds EDID.
>>> 
>> 
>> Yes, gop get / vbe list   ? yes, it is inconsistent, should fix at some 
>> point? :)
>> 
>> we do use gop get active edid/get discovered edid protocol and vbe function 
>> 0x4f15.
> 
> On all my handy laptops, E5470, T400, W530, Acer 1410 edid is present and seen
> by the loader.
> 
> 

Thank You!

rgds,
toomas

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: testers needed: loader: use display pixel density for font autoselection

[Rodney W. Grimes]

> > On 26. Feb 2021, at 17:56, Rodney W. Grimes  
> > wrote:
> > 
> >>> On 26. Feb 2021, at 05:42, Rodney W. Grimes  
> >>> wrote:
> >>> 
> > On 23. Feb 2021, at 17:53, Jakob Alvermark  wrote:
> > 
> > On 2/23/21 12:27 PM, Toomas Soome via freebsd-current wrote:
> >> hi!
> >> 
> >> I have done some work to make font pickup a bit smarter (hopefully 
> >> better;), but my own ability to test is limited to one bugged 
> >> supermicro and one MBP with retina display?
> >> 
> >> The phab link ishttps://reviews.freebsd.org/D28849  
> >> 
> >> 
> >> I have built loader binaries as well (bios and uefi):
> >> loader_lua
> >> loader_lua.efi

I have tested this on:
Lenovo W530
Dell E5470
Acer Aspire 1410

all work fine with resonable display resolution.

One more comment below...

> >> 
> >> To test, you should remove screen.font= line from loader.conf and test 
> >> with different resolutions.
> >> 
> >> thanks,
> >> toomas
> > 
> > 
> > 
> > Hi Toomas,
> > 
> > 
> > I tested on five different setups.
> > 
> > Surface Pro 10.6"@1920x1080:
> > 
> > The loader menu looks different, the "FreeBSD" text is on the right 
> > side of the screen.
>  
>  
>  I think, this was the lua script bug we did fix not too long time ago.
>  
> > 
> > Otherwise, the font size is what I would call a normal size.
> > 
> > 
> > Acer laptop 11.6"@1366x768:
> > 
> > Menu looks fine. Almost fills the entire screen.
> > 
> > The font feels a little too big.
>  
>  
>  The laptop built in displays usually do not give out EDID (we get 
>  physical dimensions from EDID), so there we fall back to try to get 
>  80x25 terminal method.
> >>> 
> >>> I am having a hard time with that statement.  EDID is very common on 
> >>> laptop screens, infact I can not recall ever not seeing EDID on a laptops 
> >>> builtin screen.
> >>> My 11" acer 1400 has EDID in it.
> >>> 
> >>> 
> >> 
> >> 
> >> If there is EDID, then it is all good. I have seen cases we do not get it 
> >> with available API.
> > 
> > Is there a way for me to know if the laoder found EDID data or not?
> > It might be that the issue is that what ever loader is using for an API is 
> > not working.
> > I based my "EDID is very common on laptop screens" on the fact that X11 
> > almost always finds EDID.
> > 
> 
> Yes, gop get / vbe list   ? yes, it is inconsistent, should fix at some 
> point? :)
> 
> we do use gop get active edid/get discovered edid protocol and vbe function 
> 0x4f15.

On all my handy laptops, E5470, T400, W530, Acer 1410 edid is present and seen
by the loader.


> 
> rgds,
> toomas

-- 
Rod Grimes rgri...@freebsd.org
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: testers needed: loader: use display pixel density for font autoselection

[Toomas Soome via freebsd-current]

> On 26. Feb 2021, at 17:56, Rodney W. Grimes  
> wrote:
> 
>>> On 26. Feb 2021, at 05:42, Rodney W. Grimes  
>>> wrote:
>>> 
> On 23. Feb 2021, at 17:53, Jakob Alvermark  wrote:
> 
> On 2/23/21 12:27 PM, Toomas Soome via freebsd-current wrote:
>> hi!
>> 
>> I have done some work to make font pickup a bit smarter (hopefully 
>> better;), but my own ability to test is limited to one bugged supermicro 
>> and one MBP with retina display?
>> 
>> The phab link ishttps://reviews.freebsd.org/D28849  
>> 
>> 
>> I have built loader binaries as well (bios and uefi):
>> loader_lua
>> loader_lua.efi
>> 
>> To test, you should remove screen.font= line from loader.conf and test 
>> with different resolutions.
>> 
>> thanks,
>> toomas
> 
> 
> 
> Hi Toomas,
> 
> 
> I tested on five different setups.
> 
> Surface Pro 10.6"@1920x1080:
> 
> The loader menu looks different, the "FreeBSD" text is on the right side 
> of the screen.
 
 
 I think, this was the lua script bug we did fix not too long time ago.
 
> 
> Otherwise, the font size is what I would call a normal size.
> 
> 
> Acer laptop 11.6"@1366x768:
> 
> Menu looks fine. Almost fills the entire screen.
> 
> The font feels a little too big.
 
 
 The laptop built in displays usually do not give out EDID (we get physical 
 dimensions from EDID), so there we fall back to try to get 80x25 terminal 
 method.
>>> 
>>> I am having a hard time with that statement.  EDID is very common on laptop 
>>> screens, infact I can not recall ever not seeing EDID on a laptops builtin 
>>> screen.
>>> My 11" acer 1400 has EDID in it.
>>> 
>>> 
>> 
>> 
>> If there is EDID, then it is all good. I have seen cases we do not get it 
>> with available API.
> 
> Is there a way for me to know if the laoder found EDID data or not?
> It might be that the issue is that what ever loader is using for an API is 
> not working.
> I based my "EDID is very common on laptop screens" on the fact that X11 
> almost always finds EDID.
> 

Yes, gop get / vbe list   — yes, it is inconsistent, should fix at some point… 
:)

we do use gop get active edid/get discovered edid protocol and vbe function 
0x4f15.

rgds,
toomas
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: testers needed: loader: use display pixel density for font autoselection

[Rodney W. Grimes]

> > On 26. Feb 2021, at 05:42, Rodney W. Grimes  
> > wrote:
> > 
> >>> On 23. Feb 2021, at 17:53, Jakob Alvermark  wrote:
> >>> 
> >>> On 2/23/21 12:27 PM, Toomas Soome via freebsd-current wrote:
>  hi!
>  
>  I have done some work to make font pickup a bit smarter (hopefully 
>  better;), but my own ability to test is limited to one bugged supermicro 
>  and one MBP with retina display?
>  
>  The phab link ishttps://reviews.freebsd.org/D28849  
>  
>  
>  I have built loader binaries as well (bios and uefi):
>  loader_lua
>  loader_lua.efi
>  
>  To test, you should remove screen.font= line from loader.conf and test 
>  with different resolutions.
>  
>  thanks,
>  toomas
> >>> 
> >>> 
> >>> 
> >>> Hi Toomas,
> >>> 
> >>> 
> >>> I tested on five different setups.
> >>> 
> >>> Surface Pro 10.6"@1920x1080:
> >>> 
> >>> The loader menu looks different, the "FreeBSD" text is on the right side 
> >>> of the screen.
> >> 
> >> 
> >> I think, this was the lua script bug we did fix not too long time ago.
> >> 
> >>> 
> >>> Otherwise, the font size is what I would call a normal size.
> >>> 
> >>> 
> >>> Acer laptop 11.6"@1366x768:
> >>> 
> >>> Menu looks fine. Almost fills the entire screen.
> >>> 
> >>> The font feels a little too big.
> >> 
> >> 
> >> The laptop built in displays usually do not give out EDID (we get physical 
> >> dimensions from EDID), so there we fall back to try to get 80x25 terminal 
> >> method.
> > 
> > I am having a hard time with that statement.  EDID is very common on laptop 
> > screens, infact I can not recall ever not seeing EDID on a laptops builtin 
> > screen.
> > My 11" acer 1400 has EDID in it.
> > 
> > 
> 
> 
> If there is EDID, then it is all good. I have seen cases we do not get it 
> with available API.

Is there a way for me to know if the laoder found EDID data or not?
It might be that the issue is that what ever loader is using for an API is not 
working.
I based my "EDID is very common on laptop screens" on the fact that X11 almost 
always finds EDID.

> >>> 
> >>> Thinkpad built in 13"@1920x1080:
> >>> 
> >>> Menu looks fine, but a little slow.
> >>> 
> >>> The font size is a little to big for my liking. When drm loads and 
> >>> mirrors the screen to my external 27" it looks comically large.
> >>> 
> >> 
> >> There is another issue - once DRM will kick in, we should re-consider the 
> >> console attributes, like fonts, but at this time, the kernel itself only 
> >> can use what was built in (8x16), or what loader was offering (default if 
> >> present). So it is up to user to act there.
> > 
> > It would be really nice if DRM could pick up what the resolution and font 
> > was when it loaded!
> 
> it should do more, my supermicro X10SAE is ony doing 800x600 with UEFI, it 
> has dell 27? 4k monitor connected. VBE can get 1600x1200 from the same set. 
> What I would like to see is, once KMS is attached (i915), I?d like to get 
> bets possible resolution and appropriate font. But thats something for future 
> work.
> 
> > 
> >> 
> >>> 
> >>> Thinkpad external 24"@1920x1200:
> >>> 
> >>> Menu looks OK, uses about a quarter of the screen.
> >>> 
> >>> Font size is fine, but once drm loads it looks a bit squeezed (like thin 
> >>> and tall), but I guess that's drm detecting the built in 1920x1080, and 
> >>> the external display is stretched.
> >>> 
> >>> 
> >>> Thinkpad external 27"@3840x2160:
> >>> 
> >>> Menu looks OK, uses about a quarter of the screen.
> >>> 
> >>> Font size is fine.
> >>> 
> >>> Looking at the dmesg though, it says: VT(efifb): resolution 1920x1080
> >>> 
> >>> 
> >>> Jakob
> >>> 
> >> 
> >> 
> >> Those cases .. I suppose the menu was still at left side, not in middle? 
> >> The thing there is, our menu is designed for 80x25 screen, with respective 
> >> constants. 
> > 
> > SO again... why are we deviating from that causing us issues?
> 
> 
> You have misunderstood - the current menu code *is* built for 80x25 - the 
> menu frame size is fixed, logo/brand locations are constants and so on.

No, I think you have misunderstood me.  I really do not like that the Loader 
and DRM seeem to deviate significantly from the default screen textual 
dimensions, as in that every thing is great on just about every machine I use 
until either the loader or DRM decides that it wants to use a resolution that, 
IMHO, is far too small font wise.  Aka almost all machines booted to a "DOS" 
prompt well have a 80x25 text mode screen.  FreeBSD seems to like to do a lot 
of 128x43.

> 
> 
> > 
> >> 
> >> many thanks for testing,
> > 
> > I have downloaded your modified loader, and put it in place, it shall get 
> > tested on my next reboot, which should be soon as 13-BETA4 should be 
> > popping out soon.
> > 
> 
> thank you!

Still waiting on Beta4, but I think I am 

Re: testers needed: loader: use display pixel density for font autoselection

[Toomas Soome via freebsd-current]

> On 26. Feb 2021, at 05:42, Rodney W. Grimes  wrote:
> 
>>> On 23. Feb 2021, at 17:53, Jakob Alvermark  wrote:
>>> 
>>> On 2/23/21 12:27 PM, Toomas Soome via freebsd-current wrote:
 hi!
 
 I have done some work to make font pickup a bit smarter (hopefully 
 better;), but my own ability to test is limited to one bugged supermicro 
 and one MBP with retina display?
 
 The phab link ishttps://reviews.freebsd.org/D28849  
 
 
 I have built loader binaries as well (bios and uefi):
 loader_lua
 loader_lua.efi
 
 To test, you should remove screen.font= line from loader.conf and test 
 with different resolutions.
 
 thanks,
 toomas
>>> 
>>> 
>>> 
>>> Hi Toomas,
>>> 
>>> 
>>> I tested on five different setups.
>>> 
>>> Surface Pro 10.6"@1920x1080:
>>> 
>>> The loader menu looks different, the "FreeBSD" text is on the right side of 
>>> the screen.
>> 
>> 
>> I think, this was the lua script bug we did fix not too long time ago.
>> 
>>> 
>>> Otherwise, the font size is what I would call a normal size.
>>> 
>>> 
>>> Acer laptop 11.6"@1366x768:
>>> 
>>> Menu looks fine. Almost fills the entire screen.
>>> 
>>> The font feels a little too big.
>> 
>> 
>> The laptop built in displays usually do not give out EDID (we get physical 
>> dimensions from EDID), so there we fall back to try to get 80x25 terminal 
>> method.
> 
> I am having a hard time with that statement.  EDID is very common on laptop 
> screens, infact I can not recall ever not seeing EDID on a laptops builtin 
> screen.
> My 11" acer 1400 has EDID in it.
> 
> 


If there is EDID, then it is all good. I have seen cases we do not get it with 
available API.


>>> 
>>> Thinkpad built in 13"@1920x1080:
>>> 
>>> Menu looks fine, but a little slow.
>>> 
>>> The font size is a little to big for my liking. When drm loads and mirrors 
>>> the screen to my external 27" it looks comically large.
>>> 
>> 
>> There is another issue - once DRM will kick in, we should re-consider the 
>> console attributes, like fonts, but at this time, the kernel itself only can 
>> use what was built in (8x16), or what loader was offering (default if 
>> present). So it is up to user to act there.
> 
> It would be really nice if DRM could pick up what the resolution and font was 
> when it loaded!

it should do more, my supermicro X10SAE is ony doing 800x600 with UEFI, it has 
dell 27” 4k monitor connected. VBE can get 1600x1200 from the same set. What I 
would like to see is, once KMS is attached (i915), I’d like to get bets 
possible resolution and appropriate font. But thats something for future work.

> 
>> 
>>> 
>>> Thinkpad external 24"@1920x1200:
>>> 
>>> Menu looks OK, uses about a quarter of the screen.
>>> 
>>> Font size is fine, but once drm loads it looks a bit squeezed (like thin 
>>> and tall), but I guess that's drm detecting the built in 1920x1080, and the 
>>> external display is stretched.
>>> 
>>> 
>>> Thinkpad external 27"@3840x2160:
>>> 
>>> Menu looks OK, uses about a quarter of the screen.
>>> 
>>> Font size is fine.
>>> 
>>> Looking at the dmesg though, it says: VT(efifb): resolution 1920x1080
>>> 
>>> 
>>> Jakob
>>> 
>> 
>> 
>> Those cases .. I suppose the menu was still at left side, not in middle? The 
>> thing there is, our menu is designed for 80x25 screen, with respective 
>> constants. 
> 
> SO again... why are we deviating from that causing us issues?


You have misunderstood - the current menu code *is* built for 80x25 - the menu 
frame size is fixed, logo/brand locations are constants and so on.


> 
>> 
>> many thanks for testing,
> 
> I have downloaded your modified loader, and put it in place, it shall get 
> tested on my next reboot, which should be soon as 13-BETA4 should be popping 
> out soon.
> 

thank you!

rgds,
toomas

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: testers needed: loader: use display pixel density for font autoselection

[Rodney W. Grimes]

> > On 23. Feb 2021, at 17:53, Jakob Alvermark  wrote:
> > 
> > On 2/23/21 12:27 PM, Toomas Soome via freebsd-current wrote:
> >> hi!
> >> 
> >> I have done some work to make font pickup a bit smarter (hopefully 
> >> better;), but my own ability to test is limited to one bugged supermicro 
> >> and one MBP with retina display?
> >> 
> >> The phab link ishttps://reviews.freebsd.org/D28849  
> >> 
> >> 
> >> I have built loader binaries as well (bios and uefi):
> >> loader_lua
> >> loader_lua.efi
> >> 
> >> To test, you should remove screen.font= line from loader.conf and test 
> >> with different resolutions.
> >> 
> >> thanks,
> >> toomas
> > 
> > 
> > 
> > Hi Toomas,
> > 
> > 
> > I tested on five different setups.
> > 
> > Surface Pro 10.6"@1920x1080:
> > 
> > The loader menu looks different, the "FreeBSD" text is on the right side of 
> > the screen.
> 
> 
> I think, this was the lua script bug we did fix not too long time ago.
> 
> > 
> > Otherwise, the font size is what I would call a normal size.
> > 
> > 
> > Acer laptop 11.6"@1366x768:
> > 
> > Menu looks fine. Almost fills the entire screen.
> > 
> > The font feels a little too big.
> 
> 
> The laptop built in displays usually do not give out EDID (we get physical 
> dimensions from EDID), so there we fall back to try to get 80x25 terminal 
> method.

I am having a hard time with that statement.  EDID is very common on laptop 
screens, infact I can not recall ever not seeing EDID on a laptops builtin 
screen.
My 11" acer 1400 has EDID in it.


> > 
> > Thinkpad built in 13"@1920x1080:
> > 
> > Menu looks fine, but a little slow.
> > 
> > The font size is a little to big for my liking. When drm loads and mirrors 
> > the screen to my external 27" it looks comically large.
> > 
> 
> There is another issue - once DRM will kick in, we should re-consider the 
> console attributes, like fonts, but at this time, the kernel itself only can 
> use what was built in (8x16), or what loader was offering (default if 
> present). So it is up to user to act there.

It would be really nice if DRM could pick up what the resolution and font was 
when it loaded!

> 
> > 
> > Thinkpad external 24"@1920x1200:
> > 
> > Menu looks OK, uses about a quarter of the screen.
> > 
> > Font size is fine, but once drm loads it looks a bit squeezed (like thin 
> > and tall), but I guess that's drm detecting the built in 1920x1080, and the 
> > external display is stretched.
> > 
> > 
> > Thinkpad external 27"@3840x2160:
> > 
> > Menu looks OK, uses about a quarter of the screen.
> > 
> > Font size is fine.
> > 
> > Looking at the dmesg though, it says: VT(efifb): resolution 1920x1080
> > 
> > 
> > Jakob
> > 
> 
> 
> Those cases .. I suppose the menu was still at left side, not in middle? The 
> thing there is, our menu is designed for 80x25 screen, with respective 
> constants. 

SO again... why are we deviating from that causing us issues?

> 
> many thanks for testing,

I have downloaded your modified loader, and put it in place, it shall get 
tested on my next reboot, which should be soon as 13-BETA4 should be popping 
out soon.

> toomas
> 
> 
> 

-- 
Rod Grimes rgri...@freebsd.org
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: testers needed: loader: use display pixel density for font autoselection

[Toomas Soome via freebsd-current]

> On 23. Feb 2021, at 17:53, Jakob Alvermark  wrote:
> 
> On 2/23/21 12:27 PM, Toomas Soome via freebsd-current wrote:
>> hi!
>> 
>> I have done some work to make font pickup a bit smarter (hopefully better;), 
>> but my own ability to test is limited to one bugged supermicro and one MBP 
>> with retina display…
>> 
>> The phab link ishttps://reviews.freebsd.org/D28849  
>> 
>> 
>> I have built loader binaries as well (bios and uefi):
>> loader_lua
>> loader_lua.efi
>> 
>> To test, you should remove screen.font= line from loader.conf and test with 
>> different resolutions.
>> 
>> thanks,
>> toomas
> 
> 
> 
> Hi Toomas,
> 
> 
> I tested on five different setups.
> 
> Surface Pro 10.6"@1920x1080:
> 
> The loader menu looks different, the "FreeBSD" text is on the right side of 
> the screen.


I think, this was the lua script bug we did fix not too long time ago.

> 
> Otherwise, the font size is what I would call a normal size.
> 
> 
> Acer laptop 11.6"@1366x768:
> 
> Menu looks fine. Almost fills the entire screen.
> 
> The font feels a little too big.


The laptop built in displays usually do not give out EDID (we get physical 
dimensions from EDID), so there we fall back to try to get 80x25 terminal 
method.

> 
> 
> Thinkpad built in 13"@1920x1080:
> 
> Menu looks fine, but a little slow.
> 
> The font size is a little to big for my liking. When drm loads and mirrors 
> the screen to my external 27" it looks comically large.
> 

There is another issue - once DRM will kick in, we should re-consider the 
console attributes, like fonts, but at this time, the kernel itself only can 
use what was built in (8x16), or what loader was offering (default if present). 
So it is up to user to act there.

> 
> Thinkpad external 24"@1920x1200:
> 
> Menu looks OK, uses about a quarter of the screen.
> 
> Font size is fine, but once drm loads it looks a bit squeezed (like thin and 
> tall), but I guess that's drm detecting the built in 1920x1080, and the 
> external display is stretched.
> 
> 
> Thinkpad external 27"@3840x2160:
> 
> Menu looks OK, uses about a quarter of the screen.
> 
> Font size is fine.
> 
> Looking at the dmesg though, it says: VT(efifb): resolution 1920x1080
> 
> 
> Jakob
> 


Those cases .. I suppose the menu was still at left side, not in middle? The 
thing there is, our menu is designed for 80x25 screen, with respective 
constants. 

many thanks for testing,
toomas

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: testers needed: loader: use display pixel density for font autoselection

[Jakob Alvermark]

On 2/23/21 12:27 PM, Toomas Soome via freebsd-current wrote:

hi!

I have done some work to make font pickup a bit smarter (hopefully better;), 
but my own ability to test is limited to one bugged supermicro and one MBP with 
retina display…

The phab link ishttps://reviews.freebsd.org/D28849  


I have built loader binaries as well (bios and uefi):
loader_lua
loader_lua.efi

To test, you should remove screen.font= line from loader.conf and test with 
different resolutions.

thanks,
toomas




Hi Toomas,


I tested on five different setups.

Surface Pro 10.6"@1920x1080:

The loader menu looks different, the "FreeBSD" text is on the right side 
of the screen.


Otherwise, the font size is what I would call a normal size.


Acer laptop 11.6"@1366x768:

Menu looks fine. Almost fills the entire screen.

The font feels a little too big.


Thinkpad built in 13"@1920x1080:

Menu looks fine, but a little slow.

The font size is a little to big for my liking. When drm loads and 
mirrors the screen to my external 27" it looks comically large.



Thinkpad external 24"@1920x1200:

Menu looks OK, uses about a quarter of the screen.

Font size is fine, but once drm loads it looks a bit squeezed (like thin 
and tall), but I guess that's drm detecting the built in 1920x1080, and 
the external display is stretched.



Thinkpad external 27"@3840x2160:

Menu looks OK, uses about a quarter of the screen.

Font size is fine.

Looking at the dmesg though, it says: VT(efifb): resolution 1920x1080


Jakob


___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: testers needed: loader: use display pixel density for font autoselection

[Johan Hendriks]

On 23/02/2021 12:27, Toomas Soome via freebsd-current wrote:

hi!

I have done some work to make font pickup a bit smarter (hopefully better;), 
but my own ability to test is limited to one bugged supermicro and one MBP with 
retina display…

The phab link is https://reviews.freebsd.org/D28849 


I have built loader binaries as well (bios and uefi):
loader_lua 
loader_lua.efi 

To test, you should remove screen.font= line from loader.conf and test with 
different resolutions.

thanks,
toomas
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


On my Intel core2 it looks fine, it has smaller fonts than before, but 
this looks more like a 1280 x 1024 screen that i use.
I use vbe_max_resolution="1280x1024" in /boot/loader.conf to use the new 
boot screens.

This is 13.0-BETA3 with the latest patches of today.

This is my dmesg output.

---<>---
Copyright (c) 1992-2021 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
    The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 13.0-BETA3 #52 releng/13.0-n244538-d7296b893969-dirty: Tue Feb 
23 15:58:29 CET 2021

    root@srv-01.thuis.local:/usr/obj/usr/src/amd64.amd64/sys/KRNL amd64
FreeBSD clang version 11.0.1 (g...@github.com:llvm/llvm-project.git 
llvmorg-11.0.1-0-g43ff75f2c3fe)

VT(vbefb): resolution 1280x1024
CPU: Intel(R) Core(TM)2 Duo CPU E6550  @ 2.33GHz (2327.55-MHz 
K8-class CPU)

  Origin="GenuineIntel"  Id=0x6fb  Family=0x6  Model=0xf Stepping=11
Features=0xbfebfbff
Features2=0xe3fd
  AMD Features=0x20100800
  AMD Features2=0x1
  VT-x: (disabled in BIOS) HLT,PAUSE
  TSC: P-state invariant, performance statistics
real memory  = 5372903424 (5124 MB)
avail memory = 5054898176 (4820 MB)
Event timer "LAPIC" quality 100
ACPI APIC Table: 
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
FreeBSD/SMP: 1 package(s) x 2 core(s)
random: unblocking device.
ioapic0: MADT APIC ID 1 != hw id 0
ioapic0  irqs 0-23
Launching APs: 1
Timecounter "TSC-low" frequency 1163773173 Hz quality 1000
KTLS: Initialized 2 threads
random: entropy device external interface
[ath_hal] loaded
WARNING: Device "kbd" is Giant locked and may be deleted before FreeBSD 
13.0.

kbd1 at kbdmux0
000.54 [4350] netmap_init   netmap: loaded module
WARNING: Device "spkr" is Giant locked and may be deleted before FreeBSD 
13.0.

mlx5en: Mellanox Ethernet driver 3.6.0 (December 2020)
nexus0
cryptosoft0: 
aesni0: No AES or SHA support.
acpi0: 
acpi0: Power Button (fixed)
cpu0:  on acpi0
attimer0:  port 0x40-0x43 irq 0 on acpi0
Timecounter "i8254" frequency 1193182 Hz quality 0
Event timer "i8254" frequency 1193182 Hz quality 100
atrtc0:  port 0x70-0x71 irq 8 on acpi0
atrtc0: registered as a time-of-day clock, resolution 1.00s
Event timer "RTC" frequency 32768 Hz quality 0
hpet1:  iomem 0xfed0-0xfed003ff on acpi0
Event timer "HPET" frequency 14318180 Hz quality 450
Event timer "HPET1" frequency 14318180 Hz quality 440
Event timer "HPET2" frequency 14318180 Hz quality 440
Event timer "HPET3" frequency 14318180 Hz quality 440
hpet0:  iomem 0xfed0-0xfed003ff on acpi0
device_attach: hpet0 attach returned 12
Timecounter "ACPI-fast" frequency 3579545 Hz quality 900
acpi_timer0: <24-bit timer at 3.579545MHz> port 0xf808-0xf80b on acpi0
pcib0:  port 0xcf8-0xcff on acpi0
Firmware Error (ACPI): \134_SB.PCI0._OSC: Excess arguments - ASL 
declared 5, ACPI requires 4 (20201113/nsarguments-311)
Firmware Error (ACPI): Failure creating named object 
[\134_SB.PCI0._OSC.CAPD], AE_ALREADY_EXISTS (20201113/dsfield-352)
ACPI Error: AE_ALREADY_EXISTS, CreateBufferField failure 
(20201113/dswload2-639)
ACPI Error: Aborting method \134_SB.PCI0._OSC due to previous error 
(AE_ALREADY_EXISTS) (20201113/psparse-689)

pcib0: _OSC failed: AE_ALREADY_EXISTS
pci0:  on pcib0
vgapci0:  port 0x1230-0x1237 mem 
0xf010-0xf017,0xe000-0xefff,0xf000-0xf00f irq 16 
at device 2.0 on pci0

agp0:  on vgapci0
WARNING: Device "agp" is Giant locked and may be deleted before FreeBSD 
13.0.

agp0: aperture size is 256M, detected 6140k stolen memory
vgapci0: Boot video device
pci0:  at device 3.0 (no driver attached)
atapci0:  port 
0x1238-0x123f,0x1270-0x1273,0x1240-0x1247,0x1274-0x1277,0x11e0-0x11ef 
irq 18 at device 3.2 on pci0

ata2:  at channel 0 on atapci0
ata3:  at channel 1 on atapci0
pci0:  at device 3.3 (no driver attached)
em0:  port 0x1100-0x111f mem 
0xf018-0xf019,0xf01a5000-0xf01a5fff irq 19 at device 25.0 on pci0

em0: Using 1024 TX descriptors and 1024 RX descriptors
em0: Using an MSI interrupt
em0: Ethernet address: 00:22:64:19:cf:e6
em0: 

Re: testers needed: loader: use display pixel density for font autoselection

[Santiago Martinez]

Will test today and report back.

Santi


On 2/23/21 11:27 AM, Toomas Soome via freebsd-current wrote:

hi!

I have done some work to make font pickup a bit smarter (hopefully better;), 
but my own ability to test is limited to one bugged supermicro and one MBP with 
retina display…

The phab link is https://reviews.freebsd.org/D28849 


I have built loader binaries as well (bios and uefi):
loader_lua 
loader_lua.efi 

To test, you should remove screen.font= line from loader.conf and test with 
different resolutions.

thanks,
toomas
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: testers needed: loader: use display pixel density for font autoselection

[David Wolfskill]

I will plan on testing later today, using the laptop that has a mouse
that doesn't work under FreeBSD. :-}

As time permits between meeetings & stuff...

Peace,
david
-- 
David H. Wolfskill  da...@catwhisker.org
It is supremely disingenuous to claim a lack of jurisdiction, then 
proceed to participate in a decision on the same matter.

See https://www.catwhisker.org/~david/publickey.gpg for my public key.


signature.asc
Description: PGP signature