OPI 5 HDMI output stops working (no signal) when screen turned off and on or HDMI cable unplugged an plugged back in

[martivo]

Armbianmonitor:

https://paste.next.armbian.com/usihemokey

Hi,

after upgrading to Armbian 24.11.3 noble with 6.1 Kernel I have this problem that every time I turn off my TV that is connected to OPI with HDMI, then turning it back on again it will never have a HDMI signal.

Same thing happens when I unplug the HDMI cable and plug it back in.
I can reproduce it every single time - not just occasionally.

 

It is not a hardware or cable problem, the exact same setup has worked flawlessly for long time with older Armbian and 5.1 kernel.

 

I tried disabling all of the KDE power saving settings, also totally disabled kpowerdevil - with no change.

SSH still works fine, the OS has not crashed.

 

No new messages come to "dmesg" after tuning the TV off and on. 

Only thing that appear is in /var/log/syslog is when I turn the tv back ON again. Turning it off does not add any messages.

 

2025-02-06T13:21:23.984567+02:00 loovsys DiscoverNotifier[1979]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-06T13:21:23.984940+02:00 loovsys kded6[1877]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-06T13:21:23.985204+02:00 loovsys polkit-kde-authentication-agent-1[1929]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-06T13:21:23.985425+02:00 loovsys plasmashell[1897]: kde.plasmashell: requesting unexisting screen available rect -1
2025-02-06T13:21:23.985562+02:00 loovsys plasmashell[1897]: message repeated 3 times: [ kde.plasmashell: requesting unexisting screen available rect -1]
2025-02-06T13:21:23.986668+02:00 loovsys kalendarac[1985]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-06T13:21:23.986910+02:00 loovsys kactivitymanagerd[1904]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-06T13:21:23.987124+02:00 loovsys xdg-desktop-portal-kde[1930]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-06T13:21:23.991124+02:00 loovsys plasmashell[1897]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-06T13:21:23.991328+02:00 loovsys plasmashell[1897]: kf.plasma.quick: Exposed with no visual parent. Window positioning broken.

Or another time pretty similar
 

2025-02-06T13:26:53.652232+02:00 loovsys kactivitymanagerd[1880]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-06T13:26:53.653516+02:00 loovsys kalendarac[1964]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-06T13:26:53.654495+02:00 loovsys kded6[1852]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-06T13:26:53.655328+02:00 loovsys DiscoverNotifier[1957]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-06T13:26:53.656229+02:00 loovsys xdg-desktop-portal-kde[1905]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-06T13:26:53.657111+02:00 loovsys plasmashell[1868]: kde.plasmashell: requesting unexisting screen available rect -1
2025-02-06T13:26:53.657645+02:00 loovsys plasmashell[1868]: message repeated 3 times: [ kde.plasmashell: requesting unexisting screen available rect -1]
2025-02-06T13:26:53.658397+02:00 loovsys polkit-kde-authentication-agent-1[1904]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-06T13:26:53.665372+02:00 loovsys plasmashell[1868]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-06T13:26:53.665685+02:00 loovsys plasmashell[1868]: kf.plasma.quick: Exposed with no visual parent. Window positioning broken.
2025-02-06T13:26:53.807759+02:00 loovsys plasmashell[1868]: message repeated 3 times: [ kf.plasma.quick: Exposed with no visual parent. Window positioning broken.]

When plugging the HDMI cable back in:

2025-02-06T13:30:00.668173+02:00 loovsys kalendarac[1948]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-06T13:30:00.669049+02:00 loovsys DiscoverNotifier[1946]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-06T13:30:00.669745+02:00 loovsys kactivitymanagerd[1869]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-06T13:30:00.670412+02:00 loovsys kded6[1839]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-06T13:30:00.671016+02:00 loovsys xdg-desktop-portal-kde[1889]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-06T13:30:00.671596+02:00 loovsys polkit-kde-authentication-agent-1[1888]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-06T13:30:00.672173+02:00 loovsys plasmashell[1858]: kde.plasmashell: requesting unexisting screen available rect -1
2025-02-06T13:30:00.672548+02:00 loovsys plasmashell[1858]: message repeated 3 times: [ kde.plasmashell: requesting unexisting screen available rect -1]
2025-02-06T13:30:00.672946+02:00 loovsys plasmashell[1858]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-06T13:30:00.688381+02:00 loovsys plasmashell[1858]: kf.plasma.quick: Exposed with no visual parent. Window positioning broken.
2025-02-06T13:30:00.705197+02:00 loovsys plasmashell[1858]: message repeated 2 times: [ kf.plasma.quick: Exposed with no visual parent. Window positioning broken.]
2025-02-06T13:30:01.892282+02:00 loovsys CRON[6339]: (root) CMD (/usr/lib/armbian/armbian-truncate-logs)
2025-02-06T13:30:01.895234+02:00 loovsys CRON[6338]: (root) CMD ([ -x /etc/init.d/anacron ] && if [ ! -d /run/systemd/system ]; then /usr/sbin/invoke-rc.d anacron start >/dev/null; fi)
2025-02-06T13:30:02.361046+02:00 loovsys chronyd[1553]: Selected source 212.7.1.131 (0.ubuntu.pool.ntp.org)
2025-02-06T13:30:05.222767+02:00 loovsys plasmashell[1858]: The cached device pixel ratio value was stale on window update.  Please file a QTBUG which explains how to reproduce.

I also tried to switch between graphical and multi-user targets. (This works fine when the TV is never turned off - i can get the console and switch back to grapgical UI)
 

systemctl isolate multi-user.target
systemctl isolate graphical.target

 

Issuing a reboot command will bring the display back. I do not have to power cycle the entire device to get the display back.

I can also get back the display after I have lost signal by switching to the multi-user.target, unplugging and plugging back in the cable. After that i can also switch back to graphical.target and everything works.

Only switching between graphical and multi-user afer losing the signal will not bring back the display.
 

If I first switch to multi-user.target and then turn off the tv, then turning it back on the display works. I can also enable the graphical target again without problems.
Then the following messages appear in syslog
 

2025-02-06T13:37:21.290588+02:00 loovsys kernel: rockchip-vop2 fdd90000.vop: [drm:vop2_crtc_atomic_disable] Crtc atomic disable vp0
2025-02-06T13:37:24.167556+02:00 loovsys kernel: rockchip-vop2 fdd90000.vop: [drm:vop2_crtc_atomic_enable] Update mode to 3840x2160p60, type: 11(if:HDMI0, flag:0x0) for vp0 dclk: 594000000
2025-02-06T13:37:24.167664+02:00 loovsys kernel: rockchip-hdptx-phy-hdmi fed60000.hdmiphy: hdptx_ropll_cmn_config bus_width:5aa320 rate:5940000
2025-02-06T13:37:24.167680+02:00 loovsys kernel: rockchip-hdptx-phy-hdmi fed60000.hdmiphy: hdptx phy pll locked!
2025-02-06T13:37:24.167693+02:00 loovsys kernel: rockchip-vop2 fdd90000.vop: [drm:vop2_crtc_atomic_enable] dclk_out0 div: 0 dclk_core0 div: 2
2025-02-06T13:37:24.167706+02:00 loovsys kernel: rockchip-vop2 fdd90000.vop: [drm:vop2_crtc_atomic_enable] set dclk_vop0 to 594000000, get 594000000
2025-02-06T13:37:24.167719+02:00 loovsys kernel: dwhdmi-rockchip fde80000.hdmi: final tmdsclk = 594000000
2025-02-06T13:37:24.280906+02:00 loovsys kernel: dwhdmi-rockchip fde80000.hdmi: don't use dsc mode
2025-02-06T13:37:24.280986+02:00 loovsys kernel: dwhdmi-rockchip fde80000.hdmi: dw hdmi qp use tmds mode
2025-02-06T13:37:24.281000+02:00 loovsys kernel: rockchip-hdptx-phy-hdmi fed60000.hdmiphy: bus_width:0x5aa320,bit_rate:5940000
2025-02-06T13:37:24.281011+02:00 loovsys kernel: rockchip-hdptx-phy-hdmi fed60000.hdmiphy: hdptx phy lane locked!

Also in the dmesg the following appears

[  293.342367] rockchip-vop2 fdd90000.vop: [drm:vop2_crtc_atomic_disable] Crtc atomic disable vp0
[  296.325415] rockchip-vop2 fdd90000.vop: [drm:vop2_crtc_atomic_enable] Update mode to 3840x2160p60, type: 11(if:HDMI0, flag:0x0) for vp0 dclk: 594000000
[  296.326327] rockchip-hdptx-phy-hdmi fed60000.hdmiphy: hdptx_ropll_cmn_config bus_width:5aa320 rate:5940000
[  296.326706] rockchip-hdptx-phy-hdmi fed60000.hdmiphy: hdptx phy pll locked!
[  296.327137] rockchip-vop2 fdd90000.vop: [drm:vop2_crtc_atomic_enable] dclk_out0 div: 0 dclk_core0 div: 2
[  296.327226] rockchip-vop2 fdd90000.vop: [drm:vop2_crtc_atomic_enable] set dclk_vop0 to 594000000, get 594000000
[  296.327422] dwhdmi-rockchip fde80000.hdmi: final tmdsclk = 594000000
[  296.438292] dwhdmi-rockchip fde80000.hdmi: don't use dsc mode
[  296.438342] dwhdmi-rockchip fde80000.hdmi: dw hdmi qp use tmds mode
[  296.438380] rockchip-hdptx-phy-hdmi fed60000.hdmiphy: bus_width:0x5aa320,bit_rate:5940000
[  296.438665] rockchip-hdptx-phy-hdmi fed60000.hdmiphy: hdptx phy lane locked!

As soon as I use the graphical target, then dmesg shows nothing and syslog only the messages I showed before.
 

root@loovsys:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Armbian 24.11.3 noble
Release:        24.04
Codename:       noble
root@loovsys:~# uname -a
Linux loovsys.eu 6.1.84-vendor-rk35xx #1 SMP Thu Jan  9 02:09:01 UTC 2025 aarch64 aarch64 aarch64 GNU/Linux

 

 

Anyone experiencing similar issues or has any idea what could be the reason for it? Otherwise  t

[martivo]

I now uninstalled KDE and installed XFCE. I also tried with Cinnamon Wayland - also no problems there

The issue is only present in KDE desktop. So something is wrong there.

 

 

When i turn off and on the screen in XFCE, i see similar messages in syslog as when doing the same in console.

2025-02-06T14:58:10.864100+02:00 loovsys kernel: rockchip-vop2 fdd90000.vop: [drm:vop2_crtc_atomic_disable] Crtc atomic disable vp0
2025-02-06T14:58:10.897375+02:00 loovsys kernel: [drm:vop2_plane_atomic_check] *ERROR* Esmart0-win0 is invisible(src: pos[0, 0] rect[64 x 64] dst: pos[3530, 1348] rect[64 x 64]
2025-02-06T14:58:14.507317+02:00 loovsys kernel: [drm:vop2_plane_atomic_check] *ERROR* Esmart0-win0 is invisible(src: pos[0, 0] rect[64 x 64] dst: pos[3373, 2143] rect[64 x 64]
2025-02-06T14:58:14.507355+02:00 loovsys kernel: rockchip-vop2 fdd90000.vop: [drm:vop2_crtc_atomic_enable] Update mode to 3840x2160p60, type: 11(if:HDMI0, flag:0x0) for vp0 dclk: 594000000
2025-02-06T14:58:14.507357+02:00 loovsys kernel: rockchip-hdptx-phy-hdmi fed60000.hdmiphy: hdptx_ropll_cmn_config bus_width:5aa320 rate:5940000
2025-02-06T14:58:14.507359+02:00 loovsys kernel: rockchip-hdptx-phy-hdmi fed60000.hdmiphy: hdptx phy pll locked!
2025-02-06T14:58:14.507361+02:00 loovsys kernel: rockchip-vop2 fdd90000.vop: [drm:vop2_crtc_atomic_enable] dclk_out0 div: 0 dclk_core0 div: 2
2025-02-06T14:58:14.507362+02:00 loovsys kernel: rockchip-vop2 fdd90000.vop: [drm:vop2_crtc_atomic_enable] set dclk_vop0 to 594000000, get 594000000
2025-02-06T14:58:14.523961+02:00 loovsys kernel: dwhdmi-rockchip fde80000.hdmi: final tmdsclk = 594000000
2025-02-06T14:58:14.637291+02:00 loovsys kernel: dwhdmi-rockchip fde80000.hdmi: don't use dsc mode
2025-02-06T14:58:14.637303+02:00 loovsys kernel: dwhdmi-rockchip fde80000.hdmi: dw hdmi qp use tmds mode
2025-02-06T14:58:14.637304+02:00 loovsys kernel: rockchip-hdptx-phy-hdmi fed60000.hdmiphy: bus_width:0x5aa320,bit_rate:5940000
2025-02-06T14:58:14.637305+02:00 loovsys kernel: rockchip-hdptx-phy-hdmi fed60000.hdmiphy: hdptx phy lane locked!

 

Edited Thursday at 04:20 PM by martivo

[Werner]

rockchip bsp kernel has recently been bumped to 6.1.99. Maybe things run smoother using it. You can use the build framework to create a set of kernel package to install via dpkg. Or use armbian-config to switch to beta repo which should also have it.

[martivo]

@Werner thanks, Ill try to update the Kernel at some point, but seems this is a KDE or plasma bug. After understanding that it's somehow related to KDE I found many bug reports with similar signal loss issues with KDE using Wayland on other devices. I don't think this is a Kernel or Armbian issue - especially since it works fine with cinnamon(wayland) and xfce. I will give a try on KDE again in 6 months and see if the bug is fixed.

Edited Friday at 07:33 AM by martivo