Read the statement by Michael Teeuw here.
suddenly the screen can't turn on
-
@sdetweil nope, I was using a 3 years old OS, so I did an upgrade to latest version of the OS on my RPi 3B+, problem still the same.
-
@lkthomas do it failed before you upgraded the os.
-
@sdetweil yes, it failed even before upgrading the OS, it’s not “upgrading”, it’s a fresh install
-
Give this a try:
in /boot/config.txt
changedtoverlay=vc4-kms-v3d
to
dtoverlay=vc4-fkms-v3d
then
vcgencmd display_power 1
vcgencmd display_power 0BR
Jens -
@MyMirror testing now, but isn’t fkms deprecated already?
-
@MyMirror I got the same issue using FKMS with “vcgencmd display_power 1” command, it got blank screen after 2 seconds of showing the object on the monitor
-
@lkthomas
Hmm, you are on Bookworm, right?
Maybe this helps: https://forums.raspberrypi.com/viewtopic.php?t=358689 -
I was just trying to get a PIR Sensor running to toggle the display on Pi5 and this was the way to go on a fresh OS install, maybe it´ll help you out too
WAYLAND_DISPLAY=“wayland-1” wlr-randr --output HDMI-A-1 --off
WAYLAND_DISPLAY=“wayland-1” wlr-randr --output HDMI-A-1 --onIf you monitor turns back on by itself after ~10 secs add vc4.force_hotplug=1 (1=hmdi1 / 2=hdmi2 / 3=both) to the end of your /boot/firmware/cmdline.txt
if you´re running rotated you can add that as --transform 90 (more options see wlr-randr --help)
vcgencmd, xrandr and xset were not working anymore for me
-
@schris88 only pi4 or 5 will have Wayland display manager.
pi3 is still on x11
-
@sdetweil I am using RPi 3B+