Hello people,
I’m currently running a dual boot configuration of CachyOS and Windows 10 on a Lenovo Legion 5, intel i5 10300H with Nvidia RTX 2060 graphics, with KDE Plasma and Wayland (KWin). I run this machine through an HDMI connection to my 2014 Samsung Smart TV (UN40J5200).
Everything runs as supposed, including login, but once KDE Plasma initializes and the desktop appears, about 5 to 10 seconds later the TV goes to black and turns itself off, with red lights blinking every second coming out of it, before it either reboots on its own (with TV logo included, meaning a full power off) after 5 seconds or so, or I have to manually turn it on. After that, everything works as intended for the rest of the session. Anynet+ (HDMI-CEC) and Eco PowerSaving modes are both turned off on the TV settings.
It’s basically the exact same issue this user also had on this old forum post, even to the details. The solution given at the time, to disable ddcutil on powerdevil, however, did not work for me. Only difference it made was that the blinking lights are no longer there, but I have to manually unplug and plug again the HDMI cable before the TV can pick up the signal again, something that didn’t happen earlier.
As far as I’ve tested, this issue does not happen on old TVs (as in, non-smart), but it has repeated on every smart tv I have tested so far.
So, a month later. Still haven’t found a solution or mitigation for this. But by looking at the journalctl logs I managed to find a possible related entry.
may 22 22:51:54 Legion-AMC org_kde_powerdevil[1459]: [ 1560][ 17.146804] Udev event detected
may 22 22:51:54 Legion-AMC org_kde_powerdevil[1459]: [ 1560][ 17.146854] Udev_Event_Detail
may 22 22:51:54 Legion-AMC org_kde_powerdevil[1459]: [ 1560][ 17.146854] prop_subsystem: drm
may 22 22:51:54 Legion-AMC org_kde_powerdevil[1459]: [ 1560][ 17.146854] prop_action: changemay 22 22:51:54 Legion-AMC org_kde_powerdevil[1459]: [ 1560][ 17.146804] Udev event detected
may 22 22:51:54 Legion-AMC org_kde_powerdevil[1459]: [ 1560][ 17.146854] Udev_Event_Detail
may 22 22:51:54 Legion-AMC org_kde_powerdevil[1459]: [ 1560][ 17.146854] prop_subsystem: drm
may 22 22:51:54 Legion-AMC org_kde_powerdevil[1459]: [ 1560][ 17.146854] prop_action: change
may 22 22:51:54 Legion-AMC org_kde_powerdevil[1459]: [ 1560][ 17.146854] prop_connector: (null)
may 22 22:51:54 Legion-AMC org_kde_powerdevil[1459]: [ 1560][ 17.146854] prop_devname: /dev/dri/card1may 22 22:51:54 Legion-AMC org_kde_powerdevil[1459]: [ 1560][ 17.146804] Udev event detected
may 22 22:51:54 Legion-AMC org_kde_powerdevil[1459]: [ 1560][ 17.146854] Udev_Event_Detail
may 22 22:51:54 Legion-AMC org_kde_powerdevil[1459]: [ 1560][ 17.146854] prop_subsystem: drm
may 22 22:51:54 Legion-AMC org_kde_powerdevil[1459]: [ 1560][ 17.146854] prop_action: change
may 22 22:51:54 Legion-AMC org_kde_powerdevil[1459]: [ 1560][ 17.146854] prop_connector: (null)
may 22 22:51:54 Legion-AMC org_kde_powerdevil[1459]: [ 1560][ 17.146854] prop_devname: /dev/dri/card1
may 22 22:51:54 Legion-AMC org_kde_powerdevil[1459]: [ 1560][ 17.146854] prop_devmode: (null)
may 22 22:51:54 Legion-AMC org_kde_powerdevil[1459]: [ 1560][ 17.146854] prop_hotplug: 1
may 22 22:51:54 Legion-AMC org_kde_powerdevil[1459]: [ 1560][ 17.146854] prop_major: 226
may 22 22:51:54 Legion-AMC org_kde_powerdevil[1459]: [ 1560][ 17.146854] prop_minor: 1
may 22 22:51:54 Legion-AMC org_kde_powerdevil[1459]: [ 1560][ 17.146854] sysname: card1
may 22 22:51:54 Legion-AMC org_kde_powerdevil[1459]: [ 1560][ 17.146854] syspath: /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card1
may 22 22:51:54 Legion-AMC org_kde_powerdevil[1459]: [ 1560][ 17.146854] attr_name: (null)
may 22 22:51:54 Legion-AMC org_kde_powerdevil[1459]: [ 1560][ 17.146876] (dw_watch_display_connections) Time since last return from sleep = 17041392334 ns = 17041 ms
may 22 22:51:54 Legion-AMC kwin_wayland[1268]: Atomic modeset test failed! Argumento inválido
may 22 22:51:54 Legion-AMC org_kde_powerdevil[1459]: [ 1560][ 17.146854] prop_devmode: (null)
may 22 22:51:54 Legion-AMC org_kde_powerdevil[1459]: [ 1560][ 17.146854] prop_hotplug: 1
may 22 22:51:54 Legion-AMC org_kde_powerdevil[1459]: [ 1560][ 17.146854] prop_major: 226
may 22 22:51:54 Legion-AMC org_kde_powerdevil[1459]: [ 1560][ 17.146854] prop_minor: 1
may 22 22:51:54 Legion-AMC org_kde_powerdevil[1459]: [ 1560][ 17.146854] sysname: card1
may 22 22:51:54 Legion-AMC org_kde_powerdevil[1459]: [ 1560][ 17.146854] syspath: /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card1
may 22 22:51:54 Legion-AMC org_kde_powerdevil[1459]: [ 1560][ 17.146854] attr_name: (null)
may 22 22:51:54 Legion-AMC org_kde_powerdevil[1459]: [ 1560][ 17.146876] (dw_watch_display_connections) Time since last return from sleep = 17041392334 ns = 17041 ms
may 22 22:51:54 Legion-AMC kwin_wayland[1268]: Atomic modeset test failed! Argumento inválido
may 22 22:51:54 Legion-AMC org_kde_powerdevil[1459]: [ 1560][ 17.146854] prop_connector: (null)
may 22 22:51:54 Legion-AMC org_kde_powerdevil[1459]: [ 1560][ 17.146854] prop_devname: /dev/dri/card1
may 22 22:51:54 Legion-AMC org_kde_powerdevil[1459]: [ 1560][ 17.146854] prop_devmode: (null)
may 22 22:51:54 Legion-AMC org_kde_powerdevil[1459]: [ 1560][ 17.146854] prop_hotplug: 1
may 22 22:51:54 Legion-AMC org_kde_powerdevil[1459]: [ 1560][ 17.146854] prop_major: 226
may 22 22:51:54 Legion-AMC org_kde_powerdevil[1459]: [ 1560][ 17.146854] prop_minor: 1
may 22 22:51:54 Legion-AMC org_kde_powerdevil[1459]: [ 1560][ 17.146854] sysname: card1
may 22 22:51:54 Legion-AMC org_kde_powerdevil[1459]: [ 1560][ 17.146854] syspath: /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card1
may 22 22:51:54 Legion-AMC org_kde_powerdevil[1459]: [ 1560][ 17.146854] attr_name: (null)
may 22 22:51:54 Legion-AMC org_kde_powerdevil[1459]: [ 1560][ 17.146876] (dw_watch_display_connections) Time since last return from sleep = 17041392334 ns = 17041 ms
may 22 22:51:54 Legion-AMC kwin_wayland[1268]: Atomic modeset test failed! Argumento inválido
I have isolated this udev event happening every single session at the exact same time the tv screen turns off and reboots. Sometimes, when the reboot itself takes only a second or 2 to occur, I can only find one of these events. But when the reboots are longer (10 or more seconds long), I can find up to six of these happening in quick succession in journalctl.
Sadly, I lack the technical expertise to recognize exactly what is going on, and googling has only yielded decade long posts unrelated to this issue in particular, or implementing solutions already discarded in testing before (such as disabling ddcutil or manually inputing an EDID). I post this here in the hopes someone with more expertise in the matter can help, or at least recognize roughly where the point of failure is to report the bug.
Will update if I find anything else.