Re: RPi4 Status and xorg behavior

Mark Millard via freebsd-arm <[email protected]>
Newsgroups gmane.os.freebsd.devel.arm
Message-ID <[email protected]>
On 2021-Mar-8, at 12:53, Mark Millard <marklmi at yahoo.com> wrote:

> On 2021-Mar-8, at 00:14, Mark Millard <marklmi at yahoo.com> wrote:
> 
> On 2021-Mar-7, at 17:10, bob prohaska <fbsd at www.zefox.net> wrote:
> 
> 
>>> In the interests of exploration, I tinkered a bit more with
>>> my Pi4 running the latest -current snapshot. Here are a few
>>> observations:
>> 
>> You may want to be explicit about the build version
>> involved (last commit involved on what branch).
>> 
>> My notes below are from a non-debugt build based on
>> main bad9fa56620e (CommitDate: 2021-03-06 21:46:28
>> +0000). Used on a RPi4B 8GiByte.
>> 
>>> Screen resolution seems to be about 30 lines by 90 columns,
>>> on a commonplace Dell 1920 by 1080 HDMI display. Mouse and
>>> keyboard work correctly.
>> 
>> My boot sequence for the RPi4B 8 GiByte shows (when I have
>> the HDMI display attached, which I usually do not):
>> 
>> EFI framebuffer information:
>> addr, size     0x3e2fe000, 0x7e9000
>> dimensions     1920 x 1080
>> stride         1920
>> masks          0x00ff0000, 0x0000ff00, 0x000000ff, 0xff000000
>> . . .
>> fb0: <BCM2835 VT framebuffer driver> on simplebus0
>> fb0: keeping existing fb bpp of 32
>> fbd0 on fb0
>> WARNING: Device "fb" is Giant locked and may be deleted before FreeBSD 14.0.
>> VT: Replacing driver "efifb" with new "fb".
>> fb0: 1920x1080(1920x1080@0,0) 32bpp
>> fb0: fbswap: 1, pitch 7680, base 0x3e2fe000, screen_size 8355840
>> . . .
>> 
>> I use:
>> 
>> if [ -x /usr/bin/resizewin ] ; then /usr/bin/resizewin -z ; fi
>> 
>> in various ~/.profile files and after logging-in doing a
>> "stty -a" shows as its first line:
>> 
>> speed 9600 baud; 67 rows; 240 columns;
>> 
>> Thus figures seem accurate.
>> 
>> I doubt that it matters but /boot/loader.conf does have:
>> 
>> boot_multicons="YES"
>> boot_serial="YES"
>> 
> 
> I tried booting 13.0-RC1 with the updated RPi4 firmware
> substituted and in that context I do see the large font
> on the display from that combination.
> 
> My main context does not have the config.txt line:
> 
> hdmi_safe=1
> 
> and if I comment it out on 13.0-RC1:
> 
> #hdmi_safe=1
> 
> and then boot again I end up with the same as my
> main enviroment was showing instead of the huge
> font showing.

Correcting my ThreadRipper display size mistake . . .

>> FYI:
>> On the ThreadRipper I do control things explicitly
>> via /boot/loader.conf having:
>> 
>> screen.textmode="0"
>> screen.font="8x16"
>> 
>> but the context is a 2560 x 1440 display and there

Really 1920 x 1200: I was thinking of the wrong
display.

>> is no serial console set up for this context. I've
>> not investigated such things on any other type of
>> context. "stty -a" ends up reporting:
>> 
>> speed 9600 baud; 75 rows; 240 columns;

At 1920 x 1200 the 75 rows and 240 columns makes
more sense vs. 1920 x 1080.

>> (System built from same sources as the RPi4B's
>> system was, also non-debug style.)

===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)

_______________________________________________
[email protected] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-arm
To unsubscribe, send any mail to "[email protected]"
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.