No HDMI output on ROCK64 with DietPi 7.8.2

Hi there,

I wanted to give DietPi another go, after trying it a long time ago.
If I remember correctly I did have HDMI output back then.
HDMI is working fine with other images.

Is this a bug, or has support been removed?

The image for the Rock64 has been updated a month ago to Bullseye and it is still supported

At the moment I am not aware on such a bug report. Probably you could share some more system details.

Required Information

  • DietPi version | cat /boot/dietpi/.version
  • Distro version | echo $G_DISTRO_NAME $G_RASPBIAN
  • Kernel version | uname -a
  • SBC model | echo $G_HW_MODEL_NAME or (EG: RPi3)

Probably you could have a look

Hey Joulinar

I am on the latest Bullseye on a ROCK64 (aarch64).


Linux DietPi 5.10.63-rockchip64 #21.08.2 SMP PREEMPT Wed Sep 8 10:57:23 UTC 2021 aarch64 GNU/Linux

No idea, generally it works, I am just chatting with a guys on the PINE64 forum about Kodi, so display output obviously works for him. Please paste the full kernel logs, let’s see if there is something about HDMI:


I can’t find any obvious errors related with HDMI(video) in the logs
Also I2C is working as I can see my Monitor’s EDID in the desktop logs

[    0.000000] Machine model: Pine64 Rock64
[    1.245170] reg-fixed-voltage vcc-host-5v-regulator: Failed to register regulator: -517
[    3.088528] rk808-regulator rk808-regulator: there is no dvs0 gpio
[    3.088581] rk808-regulator rk808-regulator: there is no dvs1 gpio
[    3.088596] rk808-regulator rk808-regulator: max buck steps per change: 8
[    3.292243] vcc_host_5v: supplied by vcc_sys
[    3.297921] debugfs: Directory 'power-domain' with parent 'pm_genpd' already present!
[    3.298654] debugfs: Directory 'power-domain' with parent 'pm_genpd' already present!
[    3.299366] debugfs: Directory 'power-domain' with parent 'pm_genpd' already present!
[    4.056838] gpio-syscon ff100000.syscon:grf-gpio: can't read the data register offset!
[    4.092192] rockchip-vop ff370000.vop: Adding to iommu group 1
[    4.105775] rockchip-drm display-subsystem: bound ff370000.vop (ops vop_component_ops [rockchipdrm])
[    4.106402] dwhdmi-rockchip ff3c0000.hdmi: Detected HDMI TX controller v2.11a with HDCP (inno_dw_hdmi_phy2)
[    4.109690] dwhdmi-rockchip ff3c0000.hdmi: registered DesignWare HDMI I2C bus driver
[    4.110853] rockchip-drm display-subsystem: bound ff3c0000.hdmi (ops dw_hdmi_rockchip_ops [rockchipdrm])
[    8.463060] rc rc0: dw_hdmi as /devices/platform/ff3c0000.hdmi/rc/rc0
[    8.463289] input: dw_hdmi as /devices/platform/ff3c0000.hdmi/rc/rc0/input4
[    8.475023] [drm] Initialized lima 1.1.0 20191231 for ff300000.gpu on minor 1
[    8.526180] videodev: Linux video capture interface: v2.00
[    8.601213] Registered IR keymap rc-empty
[    8.601445] rc rc1: gpio_ir_recv as /devices/platform/ir-receiver/rc/rc1
[    8.602884] rc rc1: lirc_dev: driver gpio_ir_recv registered at minor = 0, raw IR receiver, no transmitter
[    8.603067] input: gpio_ir_recv as /devices/platform/ir-receiver/rc/rc1/input5
[    8.708895] hantro_vpu: module is from the staging directory, the quality is unknown, you have been warned.
[    8.835226] hantro-vpu Adding to iommu group 0
[    8.900387] hantro-vpu registered rockchip,rk3328-vpu-dec as /dev/video0
[    8.948094] random: crng init done
[    8.948110] random: 7 urandom warning(s) missed due to ratelimiting
[    9.009043] hdmi-audio-codec ASoC: error at snd_soc_component_of_xlate_dai_id on -22
[    9.037384] spdif-dit spdif-dit: ASoC: source widget Playback overwritten
[    9.037399] spdif-dit spdif-dit: ASoC: source widget Playback overwritten

So, after posting the logs yesterday.
And no signs from the logs that HDMI should not work.
I tried a second monitor … nothing, and a third … bingo!

However, HDMI output works on all monitors running a different non DietPi image (same SBC).
HDMI output also works with DietPi if I plug the working monitor in for a second and then switch back to the first monitor.
The second monitor only works with this trick, if I set a fixed resolution in the desktop environment. (it doesn’t support 1920*1080)

It seems the reported resolution in the EDID is not applied correctly?
What is the resolution that DietPi boots with, and can I change this?

Hmm, on ROCK64 DietPi does not enforce any resolution what just uses what the firmware/kernel default to. If you find time, could you test it with the Armbian Bullseye image?
It should behave the same as same kernel and firmware is used.