# 5K@60 HDMI output

**URL:** https://dietpi.com/forum/t/5k-60-hdmi-output/24717
**Category:** General Discussion
**Created:** [24 November 2025 22:37 UTC](https://dietpi.com/forum/t/5k-60-hdmi-output/24717 "2025-11-24T22:37:31Z")
**Posts on this page:** 1
**Showing post:** 15

<div class="post-metadata">

### Author: ![MichaIng](https://dietpi.com/forum/user_avatar/dietpi.com/michaing/32/7_2.png) [@MichaIng](https://dietpi.com/forum/u/MichaIng)
#### Post date: [27 November 2025 00:24 UTC](https://dietpi.com/forum/t/5k-60-hdmi-output/24717/15 "2025-11-27T00:24:29Z")

</div>

Hmm, the pixel clock rates logged by the old kernel do not match 5k@60Hz at all, and it does say `don't use dsc mode` as well. How is this possible? Is there another another way to force higher resolution and frequency through limited bandwidth?

> [@Jappe](#):
>
> Ah ok I learned now, you can reach the 60Hz with this resolution, but with fewer bandwith, so the picture loses probably some quality. Sry for the madness 😃

Please explain 🤓.

> [@Jappe](#):
>
> Its a RC kernel, probably thats why. Some audio functionality errors put and I guess it then stops to log anything.

RC or not is not related. Linux does not enable debug flags on master branch or so, and RC’s are in any case potentially ready for release, just going through more testing and bug fix time. So I guess mainline Linux does just not log mode changes, respectively the mainline Rockchip HDMI driver does not. And it seems to be stricter regarding max pixel clock rates, or does not support whichever magic the vendor kernel does, to force higher resolution/frequency through lower bandwidth.

The HDMI audio codec errors are dumb indeed, respectively that it seems to retry reading that info from the monitor over and over. Funnily, the same error was reported for RPi with Kodi in 2022:

> **[Adding boot parameters to the rpi (and any arm build probably) - LibreELEC Forum](https://forum.libreelec.tv/thread/25714-adding-boot-parameters-to-the-rpi-and-any-arm-build-probably/?postID=171328#post171328)**
>
> Hello everyone :) 
> 
> Now that kodi 20a1 is released and libreelec's nightlies use it, I decided to try it on my rpi3b+. It was on le 9.2.8, but since its update to le 10 was delayed until 10.0.2, it was left unused for months now.
> 
> So, instead of...

> [@Question: snd\_soc\_dai\_startup on i2s-hifi: -19](https://dietpi.com/forum/t/question-snd-soc-dai-startup-on-i2s-hifi-19/14580):
>
> Creating a bug report/issue Hello, check my oldschool picture wink How can i fix “failed to open zone.tab” and those “snd\_soc\_dai\_startup on i2s-hifi: -19” errors? My Raspi4 is connected to the TV via mini-HDMI. Thank you! Required Information root@DietPi-Rasp4:~# echo $G\_DISTRO\_NAME $G\_RASPBIAN bullseye 0 root@DietPi-Rasp4:~# apt policy kodi apt policy kodi-bin kodi: Installiert: 2:19.1+dfsg2-2+deb11u1 Installationskandidat: 2:19.1+dfs…

Does HDMI audio finally work despite those errors?

---

_[View the full topic](https://dietpi.com/forum/t/5k-60-hdmi-output/24717)._