Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux? |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
04-08-2020, 11:34 AM
|
#1
|
Member
Registered: May 2009
Distribution: Manjaro
Posts: 156
Rep:
|
Monitor doesn't stay in standby when using a DP cable
Having another little issue with my new monitor. I switched the connection from a HDMI cable to a DP one, as there are a few improvements to using DisplayPort instead. This introduces a small annoyance I don't know how to fix.
Whenever the monitor goes into standby, it only stays that way for a few seconds before turning itself back on. Power Management - Energy Saving - Screen Energy Saving is set to 5 minutes; The OS does indeed power the monitor off after this idle time and I even see its power LED indicating that. However it only stays this way for roughly 6 - 8 seconds: Despite not moving the mouse or pressing any key, the monitor always powers back on after this amount before I do so. The problem only started after changing the cable type.
Anyone else experiencing this issue and knows how to solve it? Is this perhaps a kernel / X11 bug that I should report? openSUSE Tumbleweed x64 KDE, amdgpu module, monitor is a ViewSonic VX2758-C-MHD 23.6.
|
|
|
04-08-2020, 11:58 AM
|
#2
|
Member
Registered: May 2009
Distribution: Manjaro
Posts: 156
Original Poster
Rep:
|
Some interesting insight: I tried the following commands, all of which will put the monitor into standby once ran but in every case it still only stays that way for 6 seconds before coming back on:
Code:
xset dpms force off
xset dpms force standby
xset dpms force suspend
|
|
|
04-28-2020, 08:45 AM
|
#3
|
Member
Registered: May 2009
Distribution: Manjaro
Posts: 156
Original Poster
Rep:
|
Now that I've permanently switched from X11 to Wayland I decided to do a few more tests. Via HDMI cable, the monitor will go into standby properly including on WL! Unfortunately I need to use DisplayPort for a few reasons... such as the HDMI connection only working at 120 Hz instead of the full 144 Hz, while also requiring me to boot with "amdgpu.dc=0" else the monitor won't turn on through this cable. It appears whatever the issue is, clearly only DP is affected... is it even the monitor's fault or a Kernel bug in the end? Does Wayland offer any monitor power management settings I can play with? I really don't wish to wear my monitor out nor waste electricity by keeping it turned on throughout the night... and I can't manually power it off either since if I do Wayland will freak out that there's no display and crash the session to the login screen, or switch to my VR headset as a primary display making it impossible to see anything and bring my monitor back on without rebooting.
|
|
|
04-28-2020, 09:54 AM
|
#4
|
Senior Member
Registered: Dec 2005
Location: Florida
Distribution: CentOS/Fedora/Pop!_OS
Posts: 2,983
|
MirceaKitsune, I have had similar issues under Fedora 28/29/30 with both HDMI and DP connection. Had it under my older monitors using HDMI and with my new monitors running on either HDMI/DP. I am able to force standby with:
Code:
#!/bin/bash
qdbus org.freedesktop.ScreenSaver /ScreenSaver Lock
xset dpms force standby
That will work 90% of the time. At some point this too fails to work and I have to power cycle the workstation. Note this is on a workstation, not a laptop.
|
|
|
04-28-2020, 09:58 AM
|
#5
|
Member
Registered: May 2009
Distribution: Manjaro
Posts: 156
Original Poster
Rep:
|
Quote:
Originally Posted by lleb
MirceaKitsune, I have had similar issues under Fedora 28/29/30 with both HDMI and DP connection. Had it under my older monitors using HDMI and with my new monitors running on either HDMI/DP. I am able to force standby with:
Code:
#!/bin/bash
qdbus org.freedesktop.ScreenSaver /ScreenSaver Lock
xset dpms force standby
That will work 90% of the time. At some point this too fails to work and I have to power cycle the workstation. Note this is on a workstation, not a laptop.
|
Thank you, I shall try this later. Wanted to confirm it works on Wayland first: xset sounds like an X11 command, will it work on a Wayland Plasma session too?
[EDIT] The command 'xset dpms' confirms this is no longer a feature on Wayland: "Server does not have extension for dpms option". This Reddit thread and other posts suggest the Powerdevil utility handles monitor standby directly now.
Last edited by MirceaKitsune; 04-28-2020 at 11:33 AM.
|
|
|
05-21-2020, 12:34 PM
|
#6
|
Member
Registered: May 2009
Distribution: Manjaro
Posts: 156
Original Poster
Rep:
|
Any new thoughts on this please? I really don't wish to leave my monitor on during the night like that. If I could I'd use the HDMI cable which doesn't have this issue, but I can only use the monitor in 120 Hz mode over HDMI not 144 Hz like DP. Perhaps a different driver or kernel module is used for DisplayPort which isn't properly sending the standby signal to the monitor?
|
|
|
06-18-2020, 07:24 AM
|
#7
|
LQ Newbie
Registered: Jun 2020
Posts: 4
Rep: 
|
Hi there!
I'm encountering a similar issue. The monitor is ViewSonic VX2458, resolution 1080P 144Hz, OS Arch Linux, KDE Plasma. It doesn't stay in standby for more than a few seconds on either HDMI or DP.
Having the KDE Display Settings window open (System Settings > Display and Monitor), what I noticed is that the monitor enters sleep, after a few seconds it goes out of sleep, the display settings are grayed out, after a few seconds the display goes back to sleep, then it wakes up after a few seconds, the display settings shows a message: "An output has been removed. Settings have been reloaded". After a few seconds the display goes back to sleep and so on. At some point the cycle is broken and the display is always on.
The above hints at a possible cause: after the monitor goes into sleep, something inside the graphical interface decides to search for displays on all interfaces, including disconnected on power saving, the monitor is happy to reply to the scan and it wakes up. This triggers the graphical interface to report new display on the DP interface and the cycle is formed.
I don't know how to properly debug this. Any directions are appreciated! Thanks!
I've tried this to force it into standby, however the monitor wakes up after a few seconds and the output is re-enabled automatically before a key is even pressed, just as with power-saving settings:
xrandr --output DisplayPort-3 --off; read -n1; xrandr --output DisplayPort-3 --auto
|
|
|
06-18-2020, 08:13 PM
|
#8
|
Member
Registered: May 2009
Distribution: Manjaro
Posts: 156
Original Poster
Rep:
|
Quote:
Originally Posted by DorInZbor
Hi there!
I'm encountering a similar issue. The monitor is ViewSonic VX2458, resolution 1080P 144Hz, OS Arch Linux, KDE Plasma. It doesn't stay in standby for more than a few seconds on either HDMI or DP.
Having the KDE Display Settings window open (System Settings > Display and Monitor), what I noticed is that the monitor enters sleep, after a few seconds it goes out of sleep, the display settings are grayed out, after a few seconds the display goes back to sleep, then it wakes up after a few seconds, the display settings shows a message: "An output has been removed. Settings have been reloaded". After a few seconds the display goes back to sleep and so on. At some point the cycle is broken and the display is always on.
The above hints at a possible cause: after the monitor goes into sleep, something inside the graphical interface decides to search for displays on all interfaces, including disconnected on power saving, the monitor is happy to reply to the scan and it wakes up. This triggers the graphical interface to report new display on the DP interface and the cycle is formed.
I don't know how to properly debug this. Any directions are appreciated! Thanks!
I've tried this to force it into standby, however the monitor wakes up after a few seconds and the output is re-enabled automatically before a key is even pressed, just as with power-saving settings:
xrandr --output DisplayPort-3 --off; read -n1; xrandr --output DisplayPort-3 --auto
|
Thank you for the useful information! Someone suggested a way to test this theory which I haven't gotten to yet... to quote it from the openSUSE forum thread:
Quote:
One other possibility. After adding a DP connected 4K monitor I discovered that the hot-plugging behaviour around DP is very different than for HDMI or DVI. I wonder it some hotplug related bug might be causing your issue. For KDE-Plasma KScreen 2 deals with DP hot plug monitor events. KScreen 2 can be safely disabled if you're using a fixed (unchanging) monitor configuration. Disable Application Menu -> System Settings -> Workspace -> Startup and Shutdown -> Background services -> KScreen 2.
|
|
|
|
06-19-2020, 05:50 AM
|
#9
|
LQ Newbie
Registered: Jun 2020
Posts: 4
Rep: 
|
In the same window (Application Menu -> System Settings -> Workspace -> Startup and Shutdown -> Background services) there's the option to stop a service from running. I've stopped KScreen 2 and the monitor remains in stand-by. Thus the issue is with the KScreen 2 service.
|
|
|
06-19-2020, 09:42 AM
|
#10
|
Member
Registered: May 2009
Distribution: Manjaro
Posts: 156
Original Poster
Rep:
|
I can confirm that disabling hotplugging fixes this problem! After going to System Settings - Workspace - Startup and Shutdown - Background Services and disabling KScreen 2, I'm able to properly put my monitor into standby. This component is responsible for waking the monitor up immediately after it powers down even when you don't press a key or move the mouse.
Note that this only fixes monitor standby for the X11 Plasma session, not Wayland which appears to be an unrelated issue! Even with KScreen2 disabled, I still get a session crash and taken back to the login screen when my monitor goes into standby over the DP cable, although standby via HDMI works in Wayland too.
Due to this on top of numerous other issues, I've had to switch back to using the X11 session. I really wanted to stick to Wayland but at this stage it's far too buggy at least for KDE Plasma breaking too many functionalities.
|
|
|
10-11-2021, 01:30 AM
|
#11
|
LQ Newbie
Registered: Oct 2021
Posts: 1
Rep: 
|
Wow - disable KScreen 2 fixed by months-long issue of not being able to turn off monitors without turning the entire PC. Thank you thank you!
Did anybody report this issue to KDE? I want to make sure the devs have the right information in order to fix this.
|
|
|
10-11-2021, 10:42 AM
|
#12
|
Member
Registered: May 2009
Distribution: Manjaro
Posts: 156
Original Poster
Rep:
|
Quote:
Originally Posted by RushPL
Wow - disable KScreen 2 fixed by months-long issue of not being able to turn off monitors without turning the entire PC. Thank you thank you!
Did anybody report this issue to KDE? I want to make sure the devs have the right information in order to fix this.
|
It is reported for ages. Unfortunately, like many obvious issues, they can take years before being properly fixed... not blaming the developers as they have their own work to do, but it would be really nice if something this problematic could be addressed in a couple of months instead of left there.
|
|
|
All times are GMT -5. The time now is 04:48 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|