Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 10 Sep 2021 15:27:07 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-arm@FreeBSD.org
Subject:   [Bug 258405] rpib4 : display resolution 4k mode and network interface does not properly work together
Message-ID:  <bug-258405-7@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D258405

            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@FreeBSD.org
          Reporter: x11max1@unitybox.de

Created attachment 227806
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D227806&action=
=3Dedit
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@rpi4b:/usr/obj/usr/src/arm64.aarch64/sys/GENERI=
C=20
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 "gene=
t0"
is no more in the device tree and could not be loaded.

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

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=20
T=C5=9Ataarting 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@rpi4b> file -s bcm2711-rpi-4-b.dtb
bcm2711-rpi-4-b.dtb_ORIG: Device Tree Blob version 17, size=3D49090, boot C=
PU=3D0,
string block size=3D4026, DT structure block size=3D44992

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@rpi4b> file -s bcm2711-rpi-4-b.dtb=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20
                /boot/msdos
bcm2711-rpi-4-b.dtb: Device Tree Blob version 17, size=3D40659, boot CPU=3D=
0,
string block size=3D3643, DT structure block size=3D36944

stefanev@rpi4b> cat config.txt=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20
                /boot/msdos
[all]
arm_64bit=3D1
# enable audio (loads snd_bmc2835)
#dtparam=3Daudio=3Don,i2c_arm=3Don,spi=3Don,sd_poll_once=3Don
dtparam=3Di2c_arm=3Don
dtoverlay=3Denc28j60
dtoverlay=3Dmmc
dtoverlay=3Ddisable-bt
device_tree_address=3D0x4000
kernel=3Du-boot.bin
#=20
dtoverlay=3Dhifiberry-dac
dtoverlay=3Dhifiberry-dacplus
dtoverlay=3Dhifiberry-digi
dtoverlay=3Dhifiberry-amp
dtoverlay=3Diqaudio-dac
dtoverlay=3Diqaudio-dacplus
dtdebug=3D1

[pi4]
#hdmi_safe=3D1
##### START audio over hdmi #####
# You need them both set because hdmi_group=3D1 tells the kernel we are usi=
ng CEA=20
# mode (for TV's, has sound) instead of DMT mode(for monitors, no sound) an=
d=20
# hdmi_drive=3D2 tells the kernel to use HDMI if available. (HDMI mode has =
sound,
DVI does not.)
#hdmi_group=3D2
hdmi_group=3D1
hdmi_drive=3D2
##### END audio over hdmi #####
armstub=3Darmstub8-gic.bin
#### with this setting rpib4 won't start up, boot process stucks if loading=
 4k
#dtoverlay=3Dvc4-fkms-v3d.dtbo
#dtoverlay=3Dvc4-kms-v3d-pi4.dtbo
#hdmi_enable_4kp60=3D1
#hdmi_mode=3D76
#hdmi_cvt 3840 2160 60
#max_framebuffer_width=3D3840
#max_framebuffer=3Dheight=3D2160
#hdmi_ignore_edid=3D0xa5000080
max_framebuffers=3D2
disable_overscan=3D1

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-258405-7>