Rock (Pi) 4B Plus gives no HDMI output

Creating a bug report/issue

I have searched the existing open and closed issues

It seems there are similar issues, but they were either outdated, showing different errors and/or using different boards:

The problem: My new Rock (Pi) 4B+ board does not seem to provide HDMI output, but works fine over SSH.

Required Information

  • DietPi version | cat /boot/dietpi/.version :
    G_DIETPI_VERSION_CORE=9
    G_DIETPI_VERSION_SUB=9
    G_DIETPI_VERSION_RC=0
    G_GITBRANCH='master'
    G_GITOWNER='MichaIng'
    G_LIVE_PATCH_STATUS[0]='applied'
    G_LIVE_PATCH_STATUS[1]='applied'
    G_LIVE_PATCH_STATUS[2]='not applicable'
    G_LIVE_PATCH_STATUS[3]='not applicable'
    
  • Distro version | echo $G_DISTRO_NAME $G_RASPBIAN :
    bookworm
  • Kernel version | uname --all :
    Linux DietPi 6.6.56-current-rockchip64 #1 SMP PREEMPT Thu Oct 10 10:50:06 UTC 2024 aarch64 GNU/Linux
  • Architecture | dpkg --print-architecture :
    arm64
  • SBC model | echo $G_HW_MODEL_NAME or (EG: RPi3)
    ROCK 4 (aarch64)
  • Power supply used | (EG: 5V 1A RAVpower) :
    90W PD USB-C from monitor
  • SD card used | (EG: SanDisk ultra)
    Verbatim Premium MicroSDHC Card 32GB, V10, U1

Additional Information (if applicable)

  • Software title | (EG: Nextcloud)
    n.a. - Clean minimal install (no other software running)
  • Was the software title installed freshly or updated/migrated?
    n.a. - Clean minimal install (no other software running)
  • Can this issue be replicated on a fresh installation of DietPi?
    Yes, with both of the latest Bookworm and Bullseye releases for the Rock Pi 4

Steps to reproduce

  1. Flash a (fresh) MicroSD card with the latest DietPI Bookworm image for Rock Pi 4 (I am using Balena Etcher to do so) :
    https://dietpi.com/downloads/images/DietPi_ROCKPi4-ARMv8-Bookworm.img.xz
  2. Insert MicroSD Card into Rock 4 board
  3. Connect HDMI-Cable to monitor and Rock 4 board, and set monitor to input from HDMI cable
  4. Connect power to Rock 4 board

Expected behaviour

  • I expect the display to show visual output of a command prompt / terminal

Actual behaviour

  • The display states: ‘No input’. Re-connecting the HDMI-cable or a power-cycle on the board does not help.

Extra details

  • The monitor is pretty new, never had any issues with it, it is an LG 27UP85NP-W 4K monitor
  • The same cable and input channel on the monitor work fine with another laptop as input source (outputting 4K@60hz without problems).

Output of some of the commands requested to try in other / similar topics:

$ cat /proc/device-tree/model
Radxa ROCK Pi 4B
$ fbset -i

mode "3840x2160"
    geometry 3840 2160 3840 2160 32
    timings 0 0 0 0 0 0 0
    rgba 8/16,8/8,8/0,0/0
endmode

Frame buffer device information:
    Name        : rockchipdrmfb
    Address     : 0
    Size        : 33177600
    Type        : PACKED PIXELS
    Visual      : TRUECOLOR
    XPanStep    : 1
    YPanStep    : 1
    YWrapStep   : 0
    LineLength  : 15360
    Accelerator : No

Running fbset -xres 1920 -yres 1080 does not make any change.

$ dmesg | grep hdmi
[    0.077630] platform ff900000.vop: Fixed dependency cycle(s) with /hdmi@ff940000
[    0.077742] platform ff8f0000.vop: Fixed dependency cycle(s) with /hdmi@ff940000
[    0.077822] platform ff940000.hdmi: Fixed dependency cycle(s) with /vop@ff8f0000
[    0.077906] platform ff940000.hdmi: Fixed dependency cycle(s) with /vop@ff900000
[    2.314523] dwhdmi-rockchip ff940000.hdmi: Detected HDMI TX controller v2.11a with HDCP (DWC HDMI 2.0 TX PHY)
[    2.317333] rockchip-drm display-subsystem: bound ff940000.hdmi (ops 0xffff8000811dad40)

Does HDMI output works with other OS?

Thanks @Jappe for the lightning quick reply!

Yes, using the Debian 11 image on the Radxa documentation page (Release 20230601-0112 · radxa-build/rock-pi-4b-plus · GitHub, image https://github.com/radxa-build/rock-pi-4b-plus/releases/download/20230601-0112/rock-pi-4b-plus_debian_bullseye_cli_b21.img.xz) the monitor shows output as expected (command prompt/terminal) using the same cable, monitor and input channel.

@MichaIng Do you happen to have any idea what else I can try to provide more information that could be of any help?