[Bug 258405] rpib4 : display resolution 4k mode and network interface does not properly work together

From: <bugzilla-noreply_at_freebsd.org>
Date: Fri, 10 Sep 2021 15:27:07 +0000
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258405

            Bug ID: 258405
           Summary: rpib4 : display resolution 4k mode and network
                    interface does not properly work together
           Product: Base System
           Version: CURRENT
          Hardware: arm64
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: arm
          Assignee: freebsd-arm_at_FreeBSD.org
          Reporter: x11max1_at_unitybox.de

Created attachment 227806
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=227806&action=edit
network interface genet0 and display resolution 1920x1280 only

I own several rpib4 model b and one of them i use as a desktop pc connected to
a 4k monitor.

Installed is FreeBSD version 13.0.
FreeBSD rpi4b 13.0-CURRENT FreeBSD 13.0-CURRENT #14 r370524: Thu Sep  9
08:46:11 CEST 2021     root_at_rpi4b:/usr/obj/usr/src/arm64.aarch64/sys/GENERIC 
arm64

There are some problem with the network interface and display relosolution.

If rpib4 is configured to load a display resolution in 4K mode (3840x2160) the
network interface is not coming up, means the network interface named "genet0"
is no more in the device tree and could not be loaded.

But without 4k mode the network interface is coming up. With this configuration
the max display resolution is "1920x1280" i can use with rpib4. 

Somewhere else have observe this behaviour ?

If starting up the same rpib4 using raspberry OS all is fine.

The problem seems to be located in the file: bcm2711-rpi-4-b.dtb 
TŚtaarting in 4k mode the network interface "genet0" is configured out after
boot process is done. Don't know see why.

/usr/local/share/rpi-firmware comes with /usr/local/share/rpi-firmware.
-rw-r--r--  1 root  wheel    49090 Mar  3  2021 bcm2711-rpi-4-b.dtb

stefanev_at_rpi4b> file -s bcm2711-rpi-4-b.dtb
bcm2711-rpi-4-b.dtb_ORIG: Device Tree Blob version 17, size=49090, boot CPU=0,
string block size=4026, DT structure block size=44992

But i have replaced this file with an older one, that makes it possible to root
up rpib4.

/boot/msdos/
-rwxr-xr-x  1 root  wheel  40659 Mar 13 13:59 bcm2711-rpi-4-b.dtb
stefanev_at_rpi4b> file -s bcm2711-rpi-4-b.dtb                                    
                                                                               
                /boot/msdos
bcm2711-rpi-4-b.dtb: Device Tree Blob version 17, size=40659, boot CPU=0,
string block size=3643, DT structure block size=36944

stefanev_at_rpi4b> cat config.txt                                                 
                                                                               
                /boot/msdos
[all]
arm_64bit=1
# enable audio (loads snd_bmc2835)
#dtparam=audio=on,i2c_arm=on,spi=on,sd_poll_once=on
dtparam=i2c_arm=on
dtoverlay=enc28j60
dtoverlay=mmc
dtoverlay=disable-bt
device_tree_address=0x4000
kernel=u-boot.bin
# 
dtoverlay=hifiberry-dac
dtoverlay=hifiberry-dacplus
dtoverlay=hifiberry-digi
dtoverlay=hifiberry-amp
dtoverlay=iqaudio-dac
dtoverlay=iqaudio-dacplus
dtdebug=1

[pi4]
#hdmi_safe=1
##### START audio over hdmi #####
# You need them both set because hdmi_group=1 tells the kernel we are using CEA 
# mode (for TV's, has sound) instead of DMT mode(for monitors, no sound) and 
# hdmi_drive=2 tells the kernel to use HDMI if available. (HDMI mode has sound,
DVI does not.)
#hdmi_group=2
hdmi_group=1
hdmi_drive=2
##### END audio over hdmi #####
armstub=armstub8-gic.bin
#### with this setting rpib4 won't start up, boot process stucks if loading 4k
#dtoverlay=vc4-fkms-v3d.dtbo
#dtoverlay=vc4-kms-v3d-pi4.dtbo
#hdmi_enable_4kp60=1
#hdmi_mode=76
#hdmi_cvt 3840 2160 60
#max_framebuffer_width=3840
#max_framebuffer=height=2160
#hdmi_ignore_edid=0xa5000080
max_framebuffers=2
disable_overscan=1

-- 
You are receiving this mail because:
You are the assignee for the bug.
Received on Fri Sep 10 2021 - 15:27:07 UTC

Original text of this message