[9fans] cmdline.txt for RPi 4 with QHD screen

[9fans] cmdline.txt for RPi 4 with QHD screen

[taylor.garry]

[-- Attachment #1: Type: text/plain, Size: 832 bytes --]

Hello,
Just trying to set up my RPi 4 for Plan 9. It boots into Plan 9 no problem, but at a pretty low resolution with big black borders.

I'm using a 2560x1440 screen connected with HDMI, I run it at 60Hz with other OS on the Rpi.

Could someone please suggest a cmdline.txt config for it? At the moment I've just followed this guide:

Plan 9: Setting up 9front on a Raspberry Pi (luksamuk.codes) <https://luksamuk.codes/posts/plan9-setup-rpi.html>

and used:

console=0 user=glenda nobootprompt=local!/dev/sdM0/fs

vgasize just doesn't seem to make any difference on it.

Thanks

Garry
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T42a55b55ffb81417-Md35682b4f4d11f05977b3387
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

[-- Attachment #2: Type: text/html, Size: 1599 bytes --]

Re: [9fans] cmdline.txt for RPi 4 with QHD screen

[Oliver Lowe]

Could try adding

        hdmi_enable_4kp60=1

to cmdline.txt? see also
https://www.raspberrypi.com/documentation/computers/config_txt.html

------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T42a55b55ffb81417-M08313ef7a37be8c62bc200a4
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

Re: [9fans] cmdline.txt for RPi 4 with QHD screen

[taylor.garry]

[-- Attachment #1: Type: text/plain, Size: 670 bytes --]

Thanks for the quick reply, I put in the hdmi_enable_4k line and no difference.

My cmdline.txt is:

console=0 user=glenda nobootprompt=local!/dev/sdM0/fs
hdmi_group=2
hdmi_mode=82
hdmi_enable_4kp60=1
hdmi_cvt=2560 1440 60 3 0 0 1
max_framebuffer_width=2560
max_framebuffer_height=1440
hdmi_pixel_freq_limit=400000000
vgasize=2560x1440x16

It just seems like nothing I do really seems to make much difference.

Cheers

Garry
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T42a55b55ffb81417-M7198c7cb57cfd16e8b95c984
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

[-- Attachment #2: Type: text/html, Size: 1428 bytes --]

Re: [9fans] cmdline.txt for RPi 4 with QHD screen

[adventures in9]

I had similar issues when I needed a rpi3 to be forced into running
720p into a video capture device.

These used to be handled in config.txt
It looks like they moved those setting into a legacy section;
https://www.raspberrypi.com/documentation/computers/legacy_config_txt.html#legacy-video-options

I remember it taking several tries of different combinations of group
and mode before finding one that worked.

On Thu, Apr 4, 2024 at 9:36 PM <taylor.garry@gmail.com> wrote:
>
> Thanks for the quick reply, I put in the hdmi_enable_4k line and no difference.
>
> My cmdline.txt is:
>
> console=0 user=glenda nobootprompt=local!/dev/sdM0/fs
> hdmi_group=2
> hdmi_mode=82
> hdmi_enable_4kp60=1
> hdmi_cvt=2560 1440 60 3 0 0 1
> max_framebuffer_width=2560
> max_framebuffer_height=1440
> hdmi_pixel_freq_limit=400000000
> vgasize=2560x1440x16
>
> It just seems like nothing I do really seems to make much difference.
>
> Cheers
>
> Garry
> 9fans / 9fans / see discussions + participants + delivery options Permalink

------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T42a55b55ffb81417-Mce32b985a400d620bfbd5984
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

Re: [9fans] cmdline.txt for RPi 4 with QHD screen

[taylor.garry]

[-- Attachment #1: Type: text/plain, Size: 353 bytes --]

Thanks, I managed to corrupt my card, so I'm going to reformat and try it again, I'll post config when (if) I get it to work.
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T42a55b55ffb81417-Mf18d973ed1743a2fce513ed0
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

[-- Attachment #2: Type: text/html, Size: 849 bytes --]

Re: [9fans] cmdline.txt for RPi 4 with QHD screen

[taylor.garry]

[-- Attachment #1: Type: text/plain, Size: 583 bytes --]

This gives me a QHD display on my RPi 4, this is the whole config.txt

[pi4]
kernel=9pi4
arm_64bit=1
[pi3]
kernel=9pi3
arm_64bit=1
[all]
gpu_mem=16
core_freq=250
enable_uart=1
boot_delay=1


hdmi_group=2
hdmi_mode=87
hdmi_cvt=2560 1440 60 3 0 0 1
max_framebuffer_width=2560
max_framebuffer_height=1440
hdmi_pixel_freq_limit=250000000

------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T42a55b55ffb81417-Md8c8f4c161c36eee21dc39b7
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

[-- Attachment #2: Type: text/html, Size: 1338 bytes --]

Re: [9fans] cmdline.txt for RPi 4 with QHD screen

[Alyssa M via 9fans]

[-- Attachment #1: Type: text/plain, Size: 341 bytes --]

Oooh! More pixels!
This is wonderful, thank you!
I had the same situation, but I didn't know this was possible.
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T42a55b55ffb81417-M02cd60501c363e99ed9163bd
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

[-- Attachment #2: Type: text/html, Size: 869 bytes --]

Re: [9fans] cmdline.txt for RPi 4 with QHD screen

[taylor.garry]

[-- Attachment #1: Type: text/plain, Size: 345 bytes --]

That's great, now I just need to get wifi to work... I can't get a definitive answer on RPi 4 wifi is even supported.
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T42a55b55ffb81417-M0bb93f82eedab10f21146c19
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

[-- Attachment #2: Type: text/html, Size: 841 bytes --]

Re: [9fans] cmdline.txt for RPi 4 with QHD screen

[Brian L. Stuart]

[-- Attachment #1: Type: text/plain, Size: 964 bytes --]

 I haven't had any trouble with wifi on the 4, with one caveat.  The 400 (and maybe some of the later 4s) have an updated version of the radio.  It just takes a new entry in ether4330.c and new blobs in /sys/lib/firmware.  The entry I've got in my ether4330.c is:
    { 0x4345, 9, "brcmfmac43456-sdio.bin", "brcmfmac43456-sdio.txt", "brcmfmac43456-sdio.clm_blob" },

and the files named there are the ones I added to /sys/lib/firmware.
BLS


    On Saturday, April 6, 2024 at 01:33:46 AM UTC, <taylor.garry@gmail.com> wrote:  
 
 That's great, now I just need to get wifi to work... I can't get a definitive answer on RPi 4 wifi is even supported.9fans / 9fans / seediscussions +participants +delivery optionsPermalink  
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T42a55b55ffb81417-M5332574c9fdef8908ac6b551
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

[-- Attachment #2: Type: text/html, Size: 2325 bytes --]

Re: [9fans] cmdline.txt for RPi 4 with QHD screen

[taylor.garry]

[-- Attachment #1: Type: text/plain, Size: 548 bytes --]

Hi Brian, 
Thanks for your help, does it make a difference that I'm using 9front? I don't even seem to have a /sys/lib/firmware directory, and I'm not sure I have a ether4330.c either. 

I'm sure it's obvious, but I'm a newcomer to Plan 9 and I apologise in advance if I'm missing obvious things.

Thanks

Garry
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T42a55b55ffb81417-Mbf9496cfdbfc3fb8ad314f25
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

[-- Attachment #2: Type: text/html, Size: 1177 bytes --]

Re: [9fans] cmdline.txt for RPi 4 with QHD screen

[Brian L. Stuart]

[-- Attachment #1: Type: text/plain, Size: 3531 bytes --]

 I wouldn't call it obvious.  :)  It looks like there's at least a difference in where the firmware blobs are kept.  I don't really know how much difference there is in the driver code, but I would expect that there would be a file in /sys/src/9/bcm that is analogous to ether4330.c.  But I'll have to leave it to others who are more knoledgable about the 9front internals to follow up with more details.
In the absence of a more definitive direction, I'd grep the source files in /sys/src/9/bcm for the string 4345.  As a hex number, that is the chip ID for the 802.11 interface on the 4s.  The revision number on the original 4s was 6, but the revision on my 400 is 9.  In the 9legacy version that I use, the different IDs are listed in an array of structures:
struct {
    int chipid;
    int chiprev;
    char *fwfile;
    char *cfgfile;
    char *regufile;
} firmware[] = {
    { 0x4330, 3,    "fw_bcm40183b1.bin", config40183, 0 },
    { 0x4330, 4,    "fw_bcm40183b2.bin", config40183, 0 },
    { 43362, 0,    "fw_bcm40181a0.bin", config40181, 0 },
    { 43362, 1,    "fw_bcm40181a2.bin", config40181, 0 },
    { 43430, 1,    "brcmfmac43430-sdio.bin", "brcmfmac43430-sdio.txt", 0 },
    { 43430, 2,    "brcmfmac43436-sdio.bin", "brcmfmac43436-sdio.txt",  "brcmfmac43436-sdio.clm_blob" },
    { 0x4345, 6, "brcmfmac43455-sdio.bin", "brcmfmac43455-sdio.txt", "brcmfmac43455-sdio.clm_blob" },
    { 0x4345, 9, "brcmfmac43456-sdio.bin", "brcmfmac43456-sdio.txt", "brcmfmac43456-sdio.clm_blob" },
};

The code then runs through the array comparing the ID and rev read from the controller.  When it finds a match, it sends over the various blobs.  The code that looks for the blobs in the 9legacy driver is:

    if(!waserror()){
        snprint(nbuf, sizeof nbuf, "/boot/%s", file);
        c = namec(nbuf, Aopen, OREAD, 0);
        poperror();
    }else if(!waserror()){
        snprint(nbuf, sizeof nbuf, "/sys/lib/firmware/%s", file);
        c = namec(nbuf, Aopen, OREAD, 0);
        poperror();

If it's the same in 9front, then the blobs you have might be /boot which would be necessary if you were going to take the root from a file server over wifi.  I don't ever run mine that way, so it's more convenient for me to put them in /sys/lib/firmware.
As before, I'll need to leave it to a 9front expert to point out any of my suppositions that are wrong.

Sorry for the delay.  I took a couple of hours out to take advantage of a break in the clouds here to test my setup for the eclipse on Monday.  And btw, the computer I'll have there will be my 400 running Plan 9 with the file system I'll be talking about at IWP9 next weekend.

BLS


    On Saturday, April 6, 2024 at 07:15:16 AM UTC, taylor.garry@gmail.com <taylor.garry@gmail.com> wrote:  
 
 Hi Brian, 
Thanks for your help, does it make a difference that I'm using 9front? I don't even seem to have a /sys/lib/firmware directory, and I'm not sure I have a ether4330.c either. 

I'm sure it's obvious, but I'm a newcomer to Plan 9 and I apologise in advance if I'm missing obvious things.

Thanks

Garry9fans / 9fans / seediscussions +participants +delivery optionsPermalink  
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T42a55b55ffb81417-M21bff740cfc3be6ecf936bdb
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

[-- Attachment #2: Type: text/html, Size: 6219 bytes --]

Re: [9fans] cmdline.txt for RPi 4 with QHD screen

[taylor.garry]

[-- Attachment #1: Type: text/plain, Size: 608 bytes --]

Please don't apologise Brian, thanks so much for this help.

Looking at my ether4330.c, those two entries for revisions 6 and 9 are present, but I did a "walk | grep 43444" over the whole disk and I can't find anything like those blob files anywhere. /lib/firmware is empty too.

I think I will look at giving 9legacy a try and try your advice again.

Thanks again.

Garry
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T42a55b55ffb81417-Mc6133120b2fccaf49ba2be73
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

[-- Attachment #2: Type: text/html, Size: 1234 bytes --]

Re: [9fans] cmdline.txt for RPi 4 with QHD screen

[moody]

[-- Attachment #1: Type: text/plain, Size: 644 bytes --]

All of what Brian said is true for 9front as well. If you want to see our code implementation of this you can find
it in /sys/src/9/bcm/ether4330.c. The only difference is that 9front puts firmware in /lib/firmware and not /sys/lib/firmware.
We do not provide the binary files ourselves you need to acquire them from the rasbian ISO. It should be located within
the raspbian ISO, within the fat32 partition there.
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T42a55b55ffb81417-M8d848d6549f0c7233e407ba2
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

[-- Attachment #2: Type: text/html, Size: 1183 bytes --]

Re: [9fans] cmdline.txt for RPi 4 with QHD screen

[taylor.garry]

[-- Attachment #1: Type: text/plain, Size: 469 bytes --]

Thanks, I got the Raspbian image and I can see .dtb files there, but can't find a clear explanation of how to get the .bin files out of there. For moment I've just found an Ethernet cable and now at least my Plan 9 machine is on the network.
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T42a55b55ffb81417-M0437b8df134dbeac71cffd02
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

[-- Attachment #2: Type: text/html, Size: 965 bytes --]

Re: [9fans] cmdline.txt for RPi 4 with QHD screen

[Richard Miller]

> We do not provide the binary files ourselves you need to acquire them from the rasbian ISO.

Or look in https://github.com/RPi-Distro/firmware-nonfree/raw/buster/brcm


------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T42a55b55ffb81417-Md799ead1babe0a73392e20e7
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

Re: [9fans] cmdline.txt for RPi 4 with QHD screen

[taylor.garry]

[-- Attachment #1: Type: text/plain, Size: 267 bytes --]

Thanks Richard, I will give this a try.
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T42a55b55ffb81417-M2ea35b9ed73c3d678822e320
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

[-- Attachment #2: Type: text/html, Size: 755 bytes --]