Open reukiodo opened 6 months ago
Switching to X11 from Wayland solved this issue (can use default dtoverlay=vc4-kms-v3d
again) as well as several other issues (vnc, CTRL+ALT+F# switching, etc) and everything is working!
Can you switch back to Wayfire with vc4-kms-v3d
and then check to see if this is the same problem as https://github.com/raspberrypi/linux/issues/5801 ?
I'm not exactly sure what you want me to do?
I reverted back to wayland (though raspi-config calls this wayfire ?) and it is back to black screen and no VNC. I can still ssh in. I tried to run kmsprint
and it doesn't even have DSI in the list:
2024-04-03 14:26:42 root@raspberrypi4:~# kmsprint
Connector 0 (32) HDMI-A-1 (disconnected)
Encoder 0 (31) TMDS
Connector 1 (41) HDMI-A-2 (disconnected)
Encoder 1 (40) TMDS
2024-04-03 14:26:45 root@raspberrypi4:~#
and reloading the driver? doesn't seem to change it:
2024-04-03 14:27:41 root@raspberrypi4:~# rmmod rpi_panel_attiny_regulator
rmmod: ERROR: Module rpi_panel_attiny_regulator is not currently loaded
2024-04-03 14:27:54 root@raspberrypi4:~# modprobe rpi_panel_attiny_regulator
2024-04-03 14:28:02 root@raspberrypi4:~# kmsprint
Connector 0 (32) HDMI-A-1 (disconnected)
Encoder 0 (31) TMDS
Connector 1 (41) HDMI-A-2 (disconnected)
Encoder 1 (40) TMDS
2024-04-03 14:28:14 root@raspberrypi4:~#
So I put added the config line and reboot:
2024-04-03 14:28:14 root@raspberrypi4:~# echo "force_turbo=1" >> /boot/firmware/config.txt
2024-04-03 14:29:46 root@raspberrypi4:~# reboot
2024-04-03 14:29:49 root@raspberrypi4:~#
but it's still a black screen... and no VNC...
Thankfully switching back to X11 resolves everything and all is working again.
Well, not everything... it seems that kmsprint
fails when on X11?
2024-04-03 14:43:52 root@raspberrypi4:~# kmsprint
terminate called after throwing an instance of 'std::runtime_error'
what(): No modesetting DRM card found
Aborted
2024-04-03 14:43:55 root@raspberrypi4:~#
and reloading the driver? doesn't seem to change it:
Okay, so it looks like you're seeing a slightly different problem then. Thanks for testing!
In the non-working setup, do you see any errors in the dmesg
output?
I'm not sure what to look for - it seems to only be looking for HDMI output I guess?
oddly, now when switching back to X11, the DSI screen doesn't come back after a reboot until a hard power off/on
it seems like the vc4-drm gpu
stuff is the main difference between the two?
Fresh install of http://downloads.raspberrypi.org/raspios_full_arm64/images/raspios_full_arm64-2024-03-13/2024-03-12-raspios-bookworm-arm64-full.img.xz on known-working 512GB Samsung Evo uSD card in RaspberryPi 4 causes blank black screen on DSI display on boot.
Workaround of
dtoverlay=vc4-fkms-v3d
in/boot/firmware/config.txt
allows GUI to be shown on DSI display as found in several forum posts, but a workaround/edit shouldn't be necessary for out-of-the-box.WIth default
dtoverlay=vc4-kms-v3d
With
dtoverlay=vc4-fkms-v3d
workaround: