You are not logged in.
Pages: 1
I have setup my power management so that it should turn off and lock screens (1xHDMI + 1xDP over USB-C docking station) when idle.
It works indeed.
Only thing is that sometimes™ when I move the mouse, hit a SHIFT or NumLock key the DP screen doesn't turn on and keeps looping through its input ports (2xHDMI 1xDP).
The only way to get it back is to do CTRL-ALT-F3 to get a character console. After a few seconds the DP monitor turns back on.
When I hit ALT-F1 to get to the graphical displayport both are working.
It looks like the DP is not powered back on until I get to the character console.
This is not happening always and I have not been able to reproduce the problem.
My system is:
GPU : Intel Corporation TigerLake-LP GT2
Kernel Version : 6.11.9.zen1-1
Plasma Version : 6.2.3-1
KDE Version : 24.08.3-1
Frameworks Version : 6.8.0-1
Qt5 Version : 5.15.15+kde+r141-1
Qt6 Version : 6.8.0-1
Wayland Version : 1.23.1-1
Plasma/Wayland Protocols Version : 1.14.0-1
XOrg/Wayland Version : 24.1.4-1
Mesa Version : 1:24.2.7-1
LibVA Version : 2.22.0-1
LIBVA_DRIVER_NAME=iHD
SDDM : extra/sddm 0.21.0-4My docking station is a "Lenovo ThinkPad USB-C Dock Gen2" and monitors are "Samsung LU28R55" (DP) and "Samsung S24D300" (HDMI).
Any idea?
Last edited by 0BADC0DE (2024-11-21 10:35:57)
Maybe Computers Will Never Become As Intelligent
As Humans. Surely They Won't Ever Become So Stupid.
Offline
The other output wakes up fine, it's only the one behind the USB dock?
USB autosuspend? Do other devices behind the dock still work?
You're probably relying on the mode switch to wake the output, you could instead try to change the resolution of refresh rate.
This is plasma on wayland? Have you ever experienced similar w/ X11?
And since the USB-C dock is involved, check the surrounding journal (from monitor when to sleep until it finally woke up) for relevant entries.
Offline
The other output wakes up fine, it's only the one behind the USB dock?
Both are attached to the USB-C docking station, 1 on HDMI and 1 on DP.
(This is because one of the two displays has HDMI only.)
Actually everything is attached to the dock. I have a single USB3/USBC cable between the dock and the laptop, charging included.
USB autosuspend?
No idea. How can I check?
Do other devices behind the dock still work?
Keyboard and mouse are attached to the dock and both work.
Ethernet cable is attached to the dock RJ45 and works.
Only DP display "sometimes" doesn't wake up.
In the sense that the display cycles through all of its options and none is reported as active.
You're probably relying on the mode switch to wake the output, you could instead try to change the resolution of refresh rate.
Not sure I get the point. Anyway, my primary display is the one that doesn't wake up.
I can try to switch the other one as primary and try to change resolution or refresh rate to wake the sleepy one up.
This is plasma on wayland? Have you ever experienced similar w/ X11?
Yes, it is: see my earlier system report.
I don't have X11 since long now. And, as I am not able to reliably reproduce the problem this would require me to wait indefinitely until I get the issue.
Which makes the entire issue a "semi-decidable problem".
And since the USB-C dock is involved, check the surrounding journal (from monitor when to sleep until it finally woke up) for relevant entries.
I can try this approach too.
Last edited by 0BADC0DE (2024-11-22 11:13:33)
Maybe Computers Will Never Become As Intelligent
As Humans. Surely They Won't Ever Become So Stupid.
Offline
No idea. How can I check?
Disable it but since everything else behind the usb port still works, that's unlikely (ie. impossible)
Not sure I get the point. Anyway, my primary display is the one that doesn't wake up.
When you're handing over the output from wayland to the framebuffer console, there's a "resolution change" (even if you can't see it)
Reconfiguring the outputs (resolution or refresh rate change, maybe even just explicitly enabling the output) might mitigate this.
Also please post the output of "kscreendoctor" and "qdbus6 org.kde.KWin /KWin supportInformation" after losing the output.
Offline
Pages: 1