DSI Panel on Pi 5 and 6.6 Kernel

macromorgan commented 8 months ago

Describe the bug

My DSI panel (an official Raspberry Pi 7 inch panel) will not work anymore after upgrading to the 6.6 kernel. vclog gives the following error when I try to apply the vc4-kms-dsi-7inch overlay:

006863.114: dterror: invalid target (phandle -908620279)

Steps to reproduce the behaviour

Upgrade to the 6.6 kernel on 64bit Raspbian Bookworm.

Device (s)

Raspberry Pi 5

System

cat /etc/rpi-issue Raspberry Pi reference 2023-10-10 Generated using pi-gen, https://github.com/RPi-Distro/pi-gen, 962bf483c8f326405794827cce8c0313fd5880a8, stage4

uname -a Linux SidePi 6.6.20+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.6.20-1+rpt1 (2024-03-07) aarch64 GNU/Linux

Logs

`sudo raspinfo` System Information

Raspberry Pi 5 Model B Rev 1.0 PRETTY_NAME="Debian GNU/Linux 12 (bookworm)" NAME="Debian GNU/Linux" VERSION_ID="12" VERSION="12 (bookworm)"

Raspberry Pi reference 2023-10-10 Generated using pi-gen, https://github.com/RPi-Distro/pi-gen, 962bf483c8f326405794827cce8c0313fd5880a8, stage4

Linux SidePi 6.6.20+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.6.20-1+rpt1 (2024-03-07) aarch64 GNU/Linux Revision : d04170 Serial : <> Model : Raspberry Pi 5 Model B Rev 1.0 Throttled flag : throttled=0x0 Camera : vc_gencmd_read_response returned -1 error=1 error_msg="Command not registered"

Videocore information

vc_gencmd_read_response returned -1 error=1 error_msg="Command not registered"

Filesystem information

Filesystem 1K-blocks Used Available Use% Mounted on udev 3948128 0 3948128 0% /dev tmpfs 824576 6208 818368 1% /run /dev/nvme0n1p2 245610540 21670488 211447164 10% / tmpfs 4122848 32 4122816 1% /dev/shm tmpfs 5120 80 5040 2% /run/lock /dev/nvme0n1p1 523248 75884 447364 15% /boot/firmware tmpfs 824560 144 824416 1% /run/user/1000

Filename Type Size Used Priority /var/swap file 8388576 0 -2 /dev/zram0 partition 4194288 0 100

Package version information

raspberrypi-ui-mods: Installed: 1.20240311 raspberrypi-sys-mods: Installed: 20240129 openbox: Installed: 3.6.1-10+rpt1 lxpanel: Installed: 0.10.1-2+rpt19 pcmanfm: Installed: 1.3.2-1+rpt19 rpd-plym-splash: Installed: 0.38

Networking Information

eth0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 ether m.m.m.m txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 112

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet x.x.x.x netmask x.x.x.x inet6 ::1 prefixlen 128 scopeid 0x10 loop txqueuelen 1000 (Local Loopback) RX packets 99 bytes 8707 (8.5 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 99 bytes 8707 (8.5 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet x.x.x.x netmask x.x.x.x broadcast x.x.x.x inet6 2600:1700:fb0:y::y.y.y.y prefixlen 128 scopeid 0x0 inet6 y::y.y.y.y prefixlen 64 scopeid 0x20 inet6 y.y.y.y.y.y.y.y prefixlen 64 scopeid 0x0 inet6 fddc:8820:y::y.y.y.y prefixlen 128 scopeid 0x0 inet6 y.y.y.y.y.y.y.y prefixlen 64 scopeid 0x0 ether m.m.m.m txqueuelen 1000 (Ethernet) RX packets 37280 bytes 5059636 (4.8 MiB) RX errors 0 dropped 2 overruns 0 frame 0 TX packets 486 bytes 87416 (85.3 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

USB Information

/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/2p, 480M | Port 2: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M | Port 2: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/2p, 480M | Port 2: Dev 2, If 0, Class=Audio, Driver=snd-usb-audio, 12M | Port 2: Dev 2, If 1, Class=Audio, Driver=snd-usb-audio, 12M |__ Port 2: Dev 2, If 2, Class=Human Interface Device, Driver=usbhid, 12M

Display Information

Running (F)KMS, console

/sys/class/drm/card1-HDMI-A-1

/sys/class/drm/card1-HDMI-A-2

/sys/class/drm/card1-Writeback-1

/sys/class/drm/card1-Writeback-2

Connector 0 (32) HDMI-A-1 (disconnected) Encoder 0 (31) TMDS Connector 1 (41) HDMI-A-2 (disconnected) Encoder 1 (40) TMDS

HDMI0: HDMI_HOTPLUG = 0x00000000 HDMI1: HDMI_HOTPLUG = 0x00000000

/sys/kernel/debug/dri/1/state: plane[45]: plane-0 crtc=(null) fb=0 crtc-pos=0x0+0+0 src-pos=0.000000x0.000000+0.000000+0.000000 rotation=1 normalized-zpos=0 color-encoding=ITU-R BT.709 YCbCr color-range=YCbCr limited range plane[62]: plane-1 crtc=(null) fb=0 crtc-pos=0x0+0+0 src-pos=0.000000x0.000000+0.000000+0.000000 rotation=1 normalized-zpos=0 color-encoding=ITU-R BT.709 YCbCr color-range=YCbCr limited range plane[76]: plane-2 crtc=(null) fb=0 crtc-pos=0x0+0+0 src-pos=0.000000x0.000000+0.000000+0.000000 rotation=1 normalized-zpos=0 color-encoding=ITU-R BT.709 YCbCr color-range=YCbCr limited range plane[87]: plane-3 crtc=(null) fb=0 crtc-pos=0x0+0+0 src-pos=0.000000x0.000000+0.000000+0.000000 rotation=1 normalized-zpos=0 color-encoding=ITU-R BT.709 YCbCr color-range=YCbCr limited range plane[98]: plane-4 crtc=(null) fb=0 crtc-pos=0x0+0+0 src-pos=0.000000x0.000000+0.000000+0.000000 rotation=1 normalized-zpos=1 color-encoding=ITU-R BT.709 YCbCr color-range=YCbCr limited range plane[108]: plane-5 crtc=(null) fb=0 crtc-pos=0x0+0+0 src-pos=0.000000x0.000000+0.000000+0.000000 rotation=1 normalized-zpos=2 color-encoding=ITU-R BT.709 YCbCr color-range=YCbCr limited range plane[118]: plane-6 crtc=(null) fb=0 crtc-pos=0x0+0+0 src-pos=0.000000x0.000000+0.000000+0.000000 rotation=1 normalized-zpos=3 color-encoding=ITU-R BT.709 YCbCr color-range=YCbCr limited range plane[128]: plane-7 crtc=(null) fb=0 crtc-pos=0x0+0+0 src-pos=0.000000x0.000000+0.000000+0.000000 rotation=1 normalized-zpos=4 color-encoding=ITU-R BT.709 YCbCr color-range=YCbCr limited range plane[138]: plane-8 crtc=(null) fb=0 crtc-pos=0x0+0+0 src-pos=0.000000x0.000000+0.000000+0.000000 rotation=1 normalized-zpos=5 color-encoding=ITU-R BT.709 YCbCr color-range=YCbCr limited range plane[148]: plane-9 crtc=(null) fb=0 crtc-pos=0x0+0+0 src-pos=0.000000x0.000000+0.000000+0.000000 rotation=1 normalized-zpos=6 color-encoding=ITU-R BT.709 YCbCr color-range=YCbCr limited range plane[158]: plane-10 crtc=(null) fb=0 crtc-pos=0x0+0+0 src-pos=0.000000x0.000000+0.000000+0.000000 rotation=1 normalized-zpos=7 color-encoding=ITU-R BT.709 YCbCr color-range=YCbCr limited range plane[168]: plane-11 crtc=(null) fb=0 crtc-pos=0x0+0+0 src-pos=0.000000x0.000000+0.000000+0.000000 rotation=1 normalized-zpos=8 color-encoding=ITU-R BT.709 YCbCr color-range=YCbCr limited range plane[178]: plane-12 crtc=(null) fb=0 crtc-pos=0x0+0+0 src-pos=0.000000x0.000000+0.000000+0.000000 rotation=1 normalized-zpos=9 color-encoding=ITU-R BT.709 YCbCr color-range=YCbCr limited range plane[188]: plane-13 crtc=(null) fb=0 crtc-pos=0x0+0+0 src-pos=0.000000x0.000000+0.000000+0.000000 rotation=1 normalized-zpos=a color-encoding=ITU-R BT.709 YCbCr color-range=YCbCr limited range plane[198]: plane-14 crtc=(null) fb=0 crtc-pos=0x0+0+0 src-pos=0.000000x0.000000+0.000000+0.000000 rotation=1 normalized-zpos=b color-encoding=ITU-R BT.709 YCbCr color-range=YCbCr limited range plane[208]: plane-15 crtc=(null) fb=0 crtc-pos=0x0+0+0 src-pos=0.000000x0.000000+0.000000+0.000000 rotation=1 normalized-zpos=c color-encoding=ITU-R BT.709 YCbCr color-range=YCbCr limited range plane[218]: plane-16 crtc=(null) fb=0 crtc-pos=0x0+0+0 src-pos=0.000000x0.000000+0.000000+0.000000 rotation=1 normalized-zpos=d color-encoding=ITU-R BT.709 YCbCr color-range=YCbCr limited range plane[228]: plane-17 crtc=(null) fb=0 crtc-pos=0x0+0+0 src-pos=0.000000x0.000000+0.000000+0.000000 rotation=1 normalized-zpos=e color-encoding=ITU-R BT.709 YCbCr color-range=YCbCr limited range plane[238]: plane-18 crtc=(null) fb=0 crtc-pos=0x0+0+0 src-pos=0.000000x0.000000+0.000000+0.000000 rotation=1 normalized-zpos=f color-encoding=ITU-R BT.709 YCbCr color-range=YCbCr limited range plane[248]: plane-19 crtc=(null) fb=0 crtc-pos=0x0+0+0 src-pos=0.000000x0.000000+0.000000+0.000000 rotation=1 normalized-zpos=10 color-encoding=ITU-R BT.709 YCbCr color-range=YCbCr limited range plane[258]: plane-20 crtc=(null) fb=0 crtc-pos=0x0+0+0 src-pos=0.000000x0.000000+0.000000+0.000000 rotation=1 normalized-zpos=11 color-encoding=ITU-R BT.709 YCbCr color-range=YCbCr limited range plane[268]: plane-21 crtc=(null) fb=0 crtc-pos=0x0+0+0 src-pos=0.000000x0.000000+0.000000+0.000000 rotation=1 normalized-zpos=11 color-encoding=ITU-R BT.709 YCbCr color-range=YCbCr limited range plane[278]: plane-22 crtc=(null) fb=0 crtc-pos=0x0+0+0 src-pos=0.000000x0.000000+0.000000+0.000000 rotation=1 normalized-zpos=11 color-encoding=ITU-R BT.709 YCbCr color-range=YCbCr limited range plane[288]: plane-23 crtc=(null) fb=0 crtc-pos=0x0+0+0 src-pos=0.000000x0.000000+0.000000+0.000000 rotation=1 normalized-zpos=11 color-encoding=ITU-R BT.709 YCbCr color-range=YCbCr limited range crtc[55]: mop enable=0 active=0 self_refresh_active=0 planes_changed=0 mode_changed=0 active_changed=0 connectors_changed=0 color_mgmt_changed=0 plane_mask=0 connector_mask=0 encoder_mask=0 mode: "": 0 0 0 0 0 0 0 0 0 0 0x0 0x0 crtc[72]: moplet enable=0 active=0 self_refresh_active=0 planes_changed=0 mode_changed=0 active_changed=0 connectors_changed=0 color_mgmt_changed=0 plane_mask=0 connector_mask=0 encoder_mask=0 mode: "": 0 0 0 0 0 0 0 0 0 0 0x0 0x0 crtc[86]: crtc-2 enable=0 active=0 self_refresh_active=0 planes_changed=0 mode_changed=0 active_changed=0 connectors_changed=0 color_mgmt_changed=0 plane_mask=0 connector_mask=0 encoder_mask=0 mode: "": 0 0 0 0 0 0 0 0 0 0 0x0 0x0 crtc[97]: crtc-3 enable=0 active=0 self_refresh_active=0 planes_changed=0 mode_changed=0 active_changed=0 connectors_changed=0 color_mgmt_changed=0 plane_mask=0 connector_mask=0 encoder_mask=0 mode: "": 0 0 0 0 0 0 0 0 0 0 0x0 0x0 connector[32]: HDMI-A-1 crtc=(null) self_refresh_aware=0 max_requested_bpc=8 colorspace=Default connector[41]: HDMI-A-2 crtc=(null) self_refresh_aware=0 max_requested_bpc=8 colorspace=Default connector[61]: Writeback-1 crtc=(null) self_refresh_aware=0 max_requested_bpc=0 colorspace=Default connector[75]: Writeback-2 crtc=(null) self_refresh_aware=0 max_requested_bpc=0 colorspace=Default

Audio Information

List of PLAYBACK Hardware Devices card 0: vc4hdmi0 [vc4-hdmi-0], device 0: MAI PCM i2s-hifi-0 [MAI PCM i2s-hifi-0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: vc4hdmi1 [vc4-hdmi-1], device 0: MAI PCM i2s-hifi-0 [MAI PCM i2s-hifi-0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 3: MAX98357A [MAX98357A], device 0: 1f000a0000.i2s-HiFi HiFi-0 [1f000a0000.i2s-HiFi HiFi-0] Subdevices: 1/1 Subdevice #0: subdevice #0

null Discard all samples (playback) or generate zero samples (capture) default Default Audio Device sysdefault Default Audio Device lavrate Rate Converter Plugin Using Libav/FFmpeg Library samplerate Rate Converter Plugin Using Samplerate Library speexrate Rate Converter Plugin Using Speex Resampler jack JACK Audio Connection Kit oss Open Sound System pulse PulseAudio Sound Server speex Plugin using Speex DSP (resample, agc, denoise, echo, dereverb) upmix Plugin for channel upmix (4,6,8) vdownmix Plugin for channel downmix (stereo) with a simple spacialization hw:CARD=vc4hdmi0,DEV=0 vc4-hdmi-0, MAI PCM i2s-hifi-0 Direct hardware device without any conversions plughw:CARD=vc4hdmi0,DEV=0 vc4-hdmi-0, MAI PCM i2s-hifi-0 Hardware device with all software conversions default:CARD=vc4hdmi0 vc4-hdmi-0, MAI PCM i2s-hifi-0 Default Audio Device sysdefault:CARD=vc4hdmi0 vc4-hdmi-0, MAI PCM i2s-hifi-0 Default Audio Device hdmi:CARD=vc4hdmi0,DEV=0 vc4-hdmi-0, MAI PCM i2s-hifi-0 HDMI Audio Output dmix:CARD=vc4hdmi0,DEV=0 vc4-hdmi-0, MAI PCM i2s-hifi-0 Direct sample mixing device usbstream:CARD=vc4hdmi0 vc4-hdmi-0 USB Stream Output hw:CARD=vc4hdmi1,DEV=0 vc4-hdmi-1, MAI PCM i2s-hifi-0 Direct hardware device without any conversions plughw:CARD=vc4hdmi1,DEV=0 vc4-hdmi-1, MAI PCM i2s-hifi-0 Hardware device with all software conversions default:CARD=vc4hdmi1 vc4-hdmi-1, MAI PCM i2s-hifi-0 Default Audio Device sysdefault:CARD=vc4hdmi1 vc4-hdmi-1, MAI PCM i2s-hifi-0 Default Audio Device hdmi:CARD=vc4hdmi1,DEV=0 vc4-hdmi-1, MAI PCM i2s-hifi-0 HDMI Audio Output dmix:CARD=vc4hdmi1,DEV=0 vc4-hdmi-1, MAI PCM i2s-hifi-0 Direct sample mixing device usbstream:CARD=vc4hdmi1 vc4-hdmi-1 USB Stream Output usbstream:CARD=Device USB PnP Sound Device USB Stream Output hw:CARD=MAX98357A,DEV=0 MAX98357A, 1f000a0000.i2s-HiFi HiFi-0 Direct hardware device without any conversions plughw:CARD=MAX98357A,DEV=0 MAX98357A, 1f000a0000.i2s-HiFi HiFi-0 Hardware device with all software conversions default:CARD=MAX98357A MAX98357A, 1f000a0000.i2s-HiFi HiFi-0 Default Audio Device sysdefault:CARD=MAX98357A MAX98357A, 1f000a0000.i2s-HiFi HiFi-0 Default Audio Device dmix:CARD=MAX98357A,DEV=0 MAX98357A, 1f000a0000.i2s-HiFi HiFi-0 Direct sample mixing device usbstream:CARD=MAX98357A MAX98357A USB Stream Output

Failed to connect to bus: No medium found

Connection failure: Connection refused pa_context_connect() failed: Connection refused

config.txt

arm_64bit=1 arm_boost=1 arm_freq=2400 arm_freq_min=1500 arm_peri_high=1 audio_pwm_mode=2 auto_initramfs=1 avs_temp=55965 camera_auto_detect=-1 core_freq=910 core_freq_min=500 disable_commandline_tags=2 disable_fw_kms_setup=1 disable_l2cache=1 display_default_lcd=-1 display_hdmi_rotate=-1 display_lcd_rotate=-1 dvfs=4 enable_gic=1 enable_uart=-1 force_eeprom_read=1 force_pwm_open=1 framebuffer_depth=16 framebuffer_ignore_alpha=1 framebuffer_swap=1 gpu_freq_min=500 hdmi_enable_4kp60=1 hevc_freq=910 hevc_freq_min=500 ignore_lcd=-1 init_uart_clock=0x2dc6c00 isp_freq=910 isp_freq_min=500 mask_gpu_interrupt1=16418 max_framebuffers=1 over_voltage_avs=0x1ae14 pause_burst_frames=1 pciex4_reset=1 pmic_turbo_threshold=600 power_force_3v3_pwm=1 program_serial_random=1 total_mem=8192 v3d_freq=960 v3d_freq_min=500 vpred=8701 vpred_max=8701 hdmi_force_cec_address:0=65535 hdmi_force_cec_address:1=65535 device_tree=- overlay_prefix=overlays/ hdmi_cvt:0= hdmi_cvt:1= hdmi_edid_filename:0= hdmi_edid_filename:1= hdmi_timings:0= hdmi_timings:1=

cmdline.txt

reboot=w coherent_pool=1M 8250.nr_uarts=1 pci=pcie_bus_safe snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 smsc95xx.macaddr=<> vc_mem.mem_base=0x3fc00000 vc_mem.mem_size=0x40000000 console=tty1 root=PARTUUID=<> rootfstype=ext4 fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles cfg80211.ieee80211_regdom=US

pin configuration

vcdbg log messages

005600.866: Initial voltage 800000 temp 55415 005798.296: avs_2712: AVS pred 8701 870100 temp 55965 005798.307: vpred 870 mV +0 005802.717: FB framebuffer_swap 1 005831.664: Select resolution HDMI0/2 hotplug 0 max_mode 2 005831.679: Select resolution HDMI1/2 hotplug 0 max_mode 2 006493.014: dtb_file 'bcm2712-rpi-5-b.dtb' 006863.114: dterror: invalid target (phandle -908620279) 006863.123: dterror: merge failed 009832.414: Starting OS 9832 ms 009835.050: 00000040: -> 00000480 009835.066: 00000030: -> 00100080 009835.083: 00000034: -> 00100080 009835.098: 00000038: -> 00100080 009835.115: 0000003c: -> 00100080

Additional context

No response

pelwell commented 8 months ago

Something in the Device Tree has got corrupted - either on the filesystem or during the firmware's processing (which shouldn't happen!). Can you post the content of your config.txt, and also the output of these commands:

$ md5sum /boot/firmware/bcm2712-rpi-5-b.dtb
$ md5sum /boot/firmware/overlays/vc4-kms-dsi-7inch.dtbo

macromorgan commented 8 months ago

7e45c8e547f7cc77838f9738b3e0a6b8 /boot/firmware/bcm2712-rpi-5-b.dtb 0dff4d158f83b8e860267750e2283cc3 /boot/firmware/overlays/vc4-kms-dsi-7inch.dtbo

Those are the md5sums I show.

edit: Here is the config.txt. I commented a decent amount of stuff out as part of the troubleshooting process, but what's enabled is what I'm currently using.

# For more options and information see # http://rptl.io/configtxt # Some settings may impact device functionality. See link above for `details

# Uncomment some or all of these to enable the optional hardware interfaces dtparam=i2c_arm=on dtparam=i2s=on #dtparam=spi=on

# Enable audio (loads snd_bcm2835) #dtparam=audio=on

# Additional overlays and parameters are documented # /boot/firmware/overlays/README

# Automatically load overlays for detected cameras #camera_auto_detect=0

# Automatically load overlays for detected DSI displays #display_auto_detect=0

# Automatically load initramfs files, if found auto_initramfs=1

# Enable DRM VC4 V3D driver dtoverlay=vc4-kms-v3d #,cma-default,noaudio,nohdmi #max_framebuffers=1

# Don't have the firmware create an initial video= setting in cmdline.txt. # Use the kernel's default instead. disable_fw_kms_setup=1

# Run in 64-bit mode arm_64bit=1

# Disable compensation for displays with overscan #disable_overscan=1

# Run as fast as firmware / board allows arm_boost=1

[cm4] # Enable host mode on the 2711 built-in XHCI USB controller. # This line should be removed if the legacy DWC2 controller is required # (e.g. for USB device mode) or if USB support is not required. #otg_mode=1

[all] dtparam=nvme dtparam=rtc_bbat_vchg=3000000 #dtparam=pwr_led_trigger=default-on #dtparam=pwr_led_activelow=off #dtparam=act_led_trigger=default-on #dtparam=act_led_activelow=off #dtparam=hdmi=off dtparam=cooling_fan=on #dtparam=watchdog=on #dtparam=krnbt=on #disable_splash=1 #enable_uart=0 #dtoverlay=vc4-kms-v3d-pi5,cma-default,noaudio,nohdmi dtoverlay=vc4-kms-dsi-7inch,dsi0 dtoverlay=max98357a,no-sdmode #dtoverlay=ov5647,cam1,rotation=180,orientation=0

PinkFreud commented 8 months ago

I'm seeing the same issue on a Pi 4 w/ the official Raspberry Pi 7" touchscreen.

The following appears in dmesg:

[    3.376801] input: vc4-hdmi-1 HDMI Jack as /devices/platform/soc/fef05700.hdmi/sound/card1/input3
[    3.377195] vc4-drm gpu: bound fef05700.hdmi (ops vc4_hdmi_ops [vc4])
[    3.378203] vc4-drm gpu: bound fe700000.dsi (ops vc4_dsi_ops [vc4])
[    3.378644] vc4-drm gpu: bound fe004000.txp (ops vc4_txp_ops [vc4])
[    3.378992] vc4-drm gpu: bound fe206000.pixelvalve (ops vc4_crtc_ops [vc4])
[    3.379337] vc4-drm gpu: bound fe207000.pixelvalve (ops vc4_crtc_ops [vc4])
[    3.381694] vc4-drm gpu: bound fe20a000.pixelvalve (ops vc4_crtc_ops [vc4])
[    3.381962] vc4-drm gpu: bound fe216000.pixelvalve (ops vc4_crtc_ops [vc4])
[    3.382313] vc4-drm gpu: bound fec12000.pixelvalve (ops vc4_crtc_ops [vc4])
[    3.389014] [drm] Initialized vc4 0.0.0 20140616 for gpu on minor 1
[    4.671511] vc4_dsi fe700000.dsi: transfer interrupt wait timeout
[    4.671528] vc4_dsi fe700000.dsi: instat: 0x00000000
[    4.671539] [drm:vc4_dsi_host_transfer [vc4]] *ERROR* DSI transfer failed, resetting: -110
[    4.887504] tc358762 fe700000.dsi.0: error initializing bridge (-110)
[    4.890052] Console: switching to colour frame buffer device 100x30
[    4.903675] vc4-drm gpu: [drm] fb0: vc4drmfb frame buffer device

DSI was working fine on here w/ the 6.1.x kernels, but after updating to 6.6, it only works at boot, going dead around the time the desktop starts.

macromorgan commented 8 months ago

I suspect this is a different issue (or could be related, who knows) because in my case the devicetree overlay doesn't even apply. I confirmed the md5sum from the latest packages and it does appear correct.

PinkFreud commented 8 months ago

Well, if it helps, I've confirmed that switching back to 6.1.0-rpi8-rpi-v8 fixes DSI for me, even with the newly installed overlays from the 6.6 kernel package. In my case, the overlays appear to be fine, but one of the kernel drivers in 6.6 is likely not.

You can try copying your old kernel + initrd from /boot to /boot/firmware (filenames in /boot/firmware should be kernel_2712.img and initramfs_2712 for your Pi 5, iirc) and reboot to see if the display is still broken under the old kernel.

pelwell commented 8 months ago

@macromorgan Using the same kernel and config.txt as you I get the same md5sums and no corruption.

What are you booting off?
You seem to have 3 HID devices, a USB soundcard and an I2S soundcard attached. How is that all powered, i.e. give me the details of all the power supplies in the system.

macromorgan commented 8 months ago

I'm booting from NVME. https://www.waveshare.com/pcie-to-m.2-hat-plus.htm

I have the official power supply plugged into a Y adapter that plugs into both the Pi itself and the DSI controller board. Here is what the cable looks like: https://smarticase.com/products/smartipi-touch-2-cable-replacement-set

I have a Rii Wireless keyboard for input (not sure why it shows up as 3 HID devices, should just be the 2 for keyboard and touchpad). I am using an i2s mono amplifier for audio output, and a USB microphone for audio input.

I also have the official RTC battery and official heatsink/fan assembly.

I'm using a non-official camera module that works, but has a green tint (that I need to troubleshoot further but haven't yet).

Again though, the root cause appears to be the vc4-kms-dsi-7inch.dtbo not cleanly applying, still not figuring out why. Is there a known-good configuration you can do where at a minimum the nvme and vc4-kms-dsi-7inch overlays can be applied cleanly on a Pi 5?

Thank you.

pelwell commented 8 months ago

Is there a known-good configuration you can do where at a minimum the nvme and vc4-kms-dsi-7inch overlays can be applied cleanly on a Pi 5?

I think I might not be understanding what you are asking, because isn't that what I've done by copying your config.txt? It shouldn't matter that the hardware isn't present because it isn't until the kernel starts that it will be looked for.

Except for the NVME drive - I'm testing on an SD card, so that is one significant difference.

Some ideas for tests:

If you have a spare SD card, install a fresh Bookworm image on it, copy over your config.txt, and see if you get any error messages about the overlay application.
It sounds like you are expecting a lot from one power supply. Can you disconnect most of the external hardware and see if anything changes (apart from not finding the hardware...)?

macromorgan commented 8 months ago

I disconnected everything except the RTC battery and fan, but am still getting the error in vclog about applying the overlay. I'll troubleshoot this further (though it seems weird that power would cause this issue in the firmware). I'll report back.

macromorgan commented 8 months ago

Root cause (could point to a firmware problem though).

When this HAT is present it prevents the overlay for the official DSI panel from applying cleanly: https://www.waveshare.com/pcie-to-m.2-hat-plus.htm

This behavior seems to be new to the 6.6 kernel (possibly due to some changes in how the overlays are done).

pelwell commented 8 months ago

Would you mind dumping out the HAT EEPROM for me and uploading the file somewhere?

$ wget https://github.com/raspberrypi/utils/blob/master/eeptools/eepflash.sh
$ sudo eepflash.sh -r -f=waveshare_m2.eep -t=24c32

pelwell commented 8 months ago

Athough if it's a HAT+ then only the overlay name should be present...

pelwell commented 8 months ago

And if it does follow the spec, the EEPROM may have one of the new addresses. This might work better:

$ wget https://github.com/raspberrypi/utils/blob/master/eeptools/eepflash.sh
$ sudo dtparam i2c_vc=on
$ i2cdetect -y 0
# Look for something between 50 and 53 (probably 51)
$ sudo eepflash.sh -r -f=waveshare_m2.eep -t=24c32 -a=51
# Replace 51 above with the actual EEPROM address - use hexadecimal, with no 0x prefix

macromorgan commented 8 months ago

Something is there at 0x51 on i2c9, but the dump is not working.

macromorgan@raspberrypi:~ $ sudo eepflash.sh -r -f=waveshare_m2.eep -t=24c32 -a=51 This will attempt to talk to an eeprom at i2c address 0x51. Make sure there is an eeprom at this address. This script comes with ABSOLUTELY no warranty. Continue only if you know what you are doing. Do you wish to continue? (yes/no): yes Reading... dd: failed to open '/sys/class/i2c-adapter/i2c-0/0-0051/eeprom': No such file or directory Closing EEPROM Device. Error doing I/O operation.

macromorgan commented 8 months ago

output of i2cdetect -y 9

 0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f

00: -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- 51 -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- --

pelwell commented 8 months ago

Try with -d=9 (that should have been automatically applied):

$ sudo eepflash.sh -r -f=waveshare_m2.eep -t=24c32 -a=51 -d=9

macromorgan commented 8 months ago

Here's the EEPROM dump, thank you for your help with this. waveshare_m2.zip

pelwell commented 8 months ago

Thanks. Unfortunately, even with that eep file flashed into one of our M2 HATs and your config.txt I don't see the corruption. I'm now cloning my card onto an NVME drive so I can boot of that, just in case that makes a difference.

pelwell commented 8 months ago

Nope - just the same:

pi@raspberrypi:~$ sudo vclog -m
006916.181: Initial voltage 800000 temp 56515
007115.849: avs_2712: AVS pred 8469 846900 temp 56515
007118.842: vpred 846 mV +0
007126.865: FB framebuffer_swap 1
007156.225: Select resolution HDMI0/2 hotplug 0 max_mode 2
007159.662: Select resolution HDMI1/2 hotplug 0 max_mode 2
007851.016: dtb_file 'bcm2712-rpi-5-b.dtb'
011343.394: Starting OS 11343 ms
011347.175: 00000040: -> 00000480
011348.660: 00000030: -> 00100080
011352.762: 00000034: -> 00100080
011356.864: 00000038: -> 00100080
011360.966: 0000003c: -> 00100080

macromorgan commented 8 months ago

Is that also with the dtoverlay=vc4-kms-dsi-7inch present? Because in order to trigger the issue I need both the hat to be present and the overlay to be loaded. The hat by itself or the overlay by itself works just fine.

macromorgan commented 8 months ago

I've also taken the hat off and attempted to apply just the pciex1 parameter with the vc4-kms-dsi-7inch, but that also works. I'm at a really weird loss (note that I'm booting from a clean install off of the SD card now).

pelwell commented 8 months ago

That's with your config.txt as posted above, so yes, it does include the dsi-7inch overlay.

macromorgan commented 8 months ago

That's with your config.txt as posted above, so yes, it does include the dsi-7inch overlay.

Let me try a completely different device and see if I can observe the same behavior...

macromorgan commented 8 months ago

Different device. Different OS (but still fully updated). Same outcome when the Wavshare hat is present.

006233.194: dtb_file 'bcm2712-rpi-5-b.dtb' 006563.509: dterror: invalid target (phandle -1985364471) 006563.520: dterror: merge failed

macromorgan commented 8 months ago

Even weirder... when I don't hook up the HAT to the GPIO it works... Booted from NVME and all...

So there's some weird combination of this specific HAT, the DSI screen, the 6.6 device trees that the firmware seems to not like. Removing the hat detection, removing the DSI screen overlay, or using the 6.1 kernel and everything works...

004778.381: Initial voltage 800000 temp 49370 004975.776: avs_2712: AVS pred 8662 866200 temp 49920 004975.788: vpred 866 mV +0 004980.179: FB framebuffer_swap 1 005009.126: Select resolution HDMI0/2 hotplug 0 max_mode 2 005009.142: Select resolution HDMI1/2 hotplug 1 max_mode 2 005021.573: HDMI1 edid block 0 offset 0 005021.583: 00ffffffffffff004c2dd50500000000 005021.594: 14130103801009780aee91a3544c9926 005021.606: 0f5054bfee0001010101010101010101 005021.616: 010101010101662150b051001b304070 005021.627: 3600a05a0000001e011d007251d01e20 005021.638: 6e285500a05a0000001e000000fd0018 005021.649: 4b1a5117000a202020202020000000fc 005021.660: 0053796e634d61737465720a2020016d 005034.088: HDMI1 edid block 1 offset 128 005034.099: 02031df1459004052203230907076703 005034.110: 0c001000b82de2000f83010000011d80 005034.120: 18711c1620582c2500a05a0000009e8c 005034.129: 0ad08a20e02d10103e9600a05a000000 005034.139: 1e011d007251d01e206e285500a05a00 005034.149: 00001e00000000000000000000000000 005034.158: 00000000000000000000000000000000 005034.168: 000000000000000000000000000000fb 005034.195: HDMI1: best-mode 2 (limit 2) 1920x1080 60 Hz CEA modes 38000100040000000000000000000000 extensions 1 005034.239: FB0 disp 1 max-fb 1 1920x1080 stride 3840 base 0x3f800000 005563.492: dtb_file 'bcm2712-rpi-5-b.dtb' 009189.524: Starting OS 9189 ms 009192.159: 00000040: -> 00000480 009192.175: 00000030: -> 00100080 009192.191: 00000034: -> 00100080 009192.206: 00000038: -> 00100080 009192.223: 0000003c: -> 00100080

macromorgan commented 8 months ago

I see the same strange resistor issue. Odd that it worked despite that? https://github.com/geerlingguy/raspberry-pi-pcie-devices/issues/595

macromorgan commented 8 months ago

So it's not a "solution" per-se and instead points to a possible bug in the firmware, but it looks like if I do force_eeprom_read=0 in my config.txt everything goes back to the way it was prior to the 6.6 kernel. I'll close an issue here and open a new one with the firmware.

pelwell commented 8 months ago

It would be great if you could replace that force_eeprom_read=0 with a "dtoverlay=" (no overlay name) at the top of config.txt

macromorgan commented 8 months ago

That did not change anything, it still didn't work. So far the only thing I can to do get it to work is to add force_eeprom_read=0.

raspberrypi / linux