Pi 4B 1GB, Raspberry Pi OS Bookworm 32-bit Desktop, Wayland using 'labwc', fully updated.
This all works fine using my monitor but not when plugging my HDMI cable into my TV. A Pi 3B (non-plus) worked with the TV, and also worked with the TV when I booted the 3B from the SD Card I am now using for the 4B.
Now, on the 4B, I get the Rainbow Splash, the four raspberries, initial boot messages, but when it does its usually momentary blanking of the display, it never returns to showing subsequent boot messages, never shows a desktop, gives a completely blank screen, no cursor, nothing.
Move the HDMI back to the monitor and it's fine. Back to TV, same blank after the initial boot messages.
Everything else seems to be working fine as I can login over Telnet as usual, do all the usual things. There's nothing in 'cmdline.txt' nor 'config.txt' that I can see which would prevent it working, no forced HDMI modes or EDID overrides, just plain 'as installed' versions AFAICT.
If I comment out the 'dtoverlay=vc4-kms-v3d' and 'max_framebuffers=2' it gets past the initial momentary blanking, continues with boot messages but then gets hung-up on "(1 of 3) job plymouth...' and '(1 of 3) job dev-dri...' and similar for a minute and a half or so and, when that finally ends, it blanks the screen, no desktop.
Adding 'hdmi-safe' delivers what seems to be '640x480' and, rather than a completely blank screen, is showing a cursor at top left, but no desktop. Mostly static but does blink and disappear occasionally.
With 'hdmi_safe=1' and the DRM VC4 V3D driver enabled it's back to not coming back after blanking after the initial boot messages.
I tried 'hdmi_force_hotplug=1' but that didn't seem to fix anything, appears to hang the Pi on reboot, requires power to be pulled to recover.
There's nothing in 'dmesg' which gives any clue as to what's going on, what's not working. It's been years since I had to bugger about getting video to work and all my video driver knowledge and notes are from way back with Buster on a 3B and I haven't kept up with how things have changed.
Is there any guide on how to diagnose the issue and resolve it, anyone know how to ?
This all works fine using my monitor but not when plugging my HDMI cable into my TV. A Pi 3B (non-plus) worked with the TV, and also worked with the TV when I booted the 3B from the SD Card I am now using for the 4B.
Now, on the 4B, I get the Rainbow Splash, the four raspberries, initial boot messages, but when it does its usually momentary blanking of the display, it never returns to showing subsequent boot messages, never shows a desktop, gives a completely blank screen, no cursor, nothing.
Move the HDMI back to the monitor and it's fine. Back to TV, same blank after the initial boot messages.
Everything else seems to be working fine as I can login over Telnet as usual, do all the usual things. There's nothing in 'cmdline.txt' nor 'config.txt' that I can see which would prevent it working, no forced HDMI modes or EDID overrides, just plain 'as installed' versions AFAICT.
Code:
console=tty1 root=PARTUUID=e086ea87-02 rootfstype=ext4 fsck.repair=yes rootwait cfg80211.ieee80211_regdom=GBCode:
# 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 camerascamera_auto_detect=1# Automatically load overlays for detected DSI displaysdisplay_auto_detect=1# Automatically load initramfs files, if foundauto_initramfs=1# Enable DRM VC4 V3D driverdtoverlay=vc4-kms-v3dmax_framebuffers=2# Don't have the firmware create an initial video= setting in cmdline.txt.# Use the kernel's default instead.disable_fw_kms_setup=1# Disable compensation for displays with overscandisable_overscan=1# Run as fast as firmware / board allowsarm_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]enable_uart=1Adding 'hdmi-safe' delivers what seems to be '640x480' and, rather than a completely blank screen, is showing a cursor at top left, but no desktop. Mostly static but does blink and disappear occasionally.
With 'hdmi_safe=1' and the DRM VC4 V3D driver enabled it's back to not coming back after blanking after the initial boot messages.
I tried 'hdmi_force_hotplug=1' but that didn't seem to fix anything, appears to hang the Pi on reboot, requires power to be pulled to recover.
There's nothing in 'dmesg' which gives any clue as to what's going on, what's not working. It's been years since I had to bugger about getting video to work and all my video driver knowledge and notes are from way back with Buster on a 3B and I haven't kept up with how things have changed.
Is there any guide on how to diagnose the issue and resolve it, anyone know how to ?
Statistics: Posted by hippy — Mon Dec 23, 2024 1:21 pm — Replies 2 — Views 36
