Re: Dell P2715Q Monitor does not wake up after sleep (off, standby, or suspend)
On Sat, Aug 12, 2017 at 02:28:03PM -0400, Greg Gorsuch wrote: Actually, I was looking at the output from the xrander -q I posted in my first e-mail. It does show the display as connected still or "again" - the only explanation I see for the DPMS (?) induced change. I have tried udevadm monitor and do not see any events. Not even when you actually unplug the device??? a rule UBSYSTEM=="drm", ACTION=="change", RUN+="/usr/local/bin/fix_dell_monitor.sh", but it doesn't seem like that ever gets executed. Hard to say. Typical pitfall is that xrandr needs to be run for the current XAuthority and Display (iow. as you user and with some environment set) - not as root. Try to "echo foo > /tmp/bar" to check whether it's called. Also do not forget to reload the rules. Where is the logic for deactivating monitors and waking up from sleep actually handled? *Shrug* The hardware triggers an interrupt, the kernel/module sends a udev event and "some™" userspace process acts accordingly (or not) I'd try with a pure X11 server first and foremost to see whether some supersophisticated DE daemon makes a bad choice. (Ie. launch only the server and an xterm) The nvidia blob actually has an "UseHotplugEvents" device option, but that won't work w/ DP (because hotplug events are mandatory for this connection) Cheers, Thomas ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: https://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
Re: Dell P2715Q Monitor does not wake up after sleep (off, standby, or suspend)
On Fri, Aug 11, 2017 at 3:08 PM, Greg Gorsuch wrote:
> Your description sounds about right. Since I do see a message ("Entering
> energy saver mode") come up on the monitor when I move the mouse as I
> mentioned before, this does suggest it has been awakened and becomes
> unrigistered at this point and sees no input anymore (hence the message).
> All the windows are already moved to the other monitor at this point and the
> screen saver seems like it has more or less died (though it does prompt for
> the password and allows me to log in).
>
> I did what you asked, but it didn't really give any useful info since it
> normally takes a while for the monitor to fail to come back up (maybe 5 or
> 10 minutes after I lock the screen even with the sleep time as 1 minutes or
> so). I kind of already generated the info you may be seeking in my original
> post.
>
> I am wondering if there is some way to just "lock" the setup so that the
> monitor is always there if it is a registration problem, or change things so
> the monitor is not unrigestering itself.
Does the monitor have an option to disable input polling? Some
monitors rotate through their inputs when they are not getting a
signal to see if one attaches so they can automatically switch to that
input. This often confuses drivers because the input switching on the
monitor often triggers a hotplug event which looks like the display
has been disconnected to the driver since the monitor has switched to
another input.
Alex
>
>
> On Thu, Aug 10, 2017 at 9:55 AM, Thomas Lübking
> wrote:
>>
>> On Wed, Aug 09, 2017 at 11:39:06AM -0400, Greg Gorsuch wrote:
>>>
>>> Where are the sleep logistics handled? Is it with the X server, the
>>> NVIDIA
>>> drivers, the Linux Kernel, or somewhere else? Is it possible to capture
>>> the
>>> communications on Windows 10 to identify how it is being handled. I don't
>>> get the feeling it should be that complex to fix or at least implement a
>>> work around since xrander is able to bring the monitor back online.
>>
>>
>> It sounds like when you go dpms off, the monitor unregisters and when
>> you go dpms on, the monitor re-registers.
>> Then some semi-smart randr daemon kicks in and adjusts the layout, but
>> does not so when the monitor comes back.
>>
>> Try to log the setup in the various modes:
>>
>> xset dpms force standby; sleep 10; xrandr --current > ~/randr.standby;
>> xset dpms force suspend; sleep 10; xrandr --current > ~/randr.suspend;
>> xset dpms force off; sleep 10; xrandr --current > ~/randr.off; xset
>> dpms force on
>>
>> Also try the behavior on a "naked" X11 server (no desktop session, only
>> an xterm) to see whether some client or the server adjusts the randr
>> setup.
>>
>> Cheers,
>> Thomas
>
>
>
>
> --
> Greg Gorsuch
>
> ___
> xorg@lists.x.org: X.Org support
> Archives: http://lists.freedesktop.org/archives/xorg
> Info: https://lists.x.org/mailman/listinfo/xorg
> Your subscription address: %(user_address)s
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s
Re: Dell P2715Q Monitor does not wake up after sleep (off, standby, or suspend)
Your description sounds about right. Since I do see a message ("*Entering
energy saver mode*") come up on the monitor when I move the mouse as I
mentioned before, this does suggest it has been awakened and becomes
unrigistered at this point and sees no input anymore (hence the message).
All the windows are already moved to the other monitor at this point and
the screen saver seems like it has more or less died (though it does prompt
for the password and allows me to log in).
I did what you asked, but it didn't really give any useful info since it
normally takes a while for the monitor to fail to come back up (maybe 5 or
10 minutes after I lock the screen even with the sleep time as 1 minutes or
so). I kind of already generated the info you may be seeking in my
original post.
I am wondering if there is some way to just "lock" the setup so that the
monitor is always there if it is a registration problem, or change things
so the monitor is not unrigestering itself.
On Thu, Aug 10, 2017 at 9:55 AM, Thomas Lübking
wrote:
> On Wed, Aug 09, 2017 at 11:39:06AM -0400, Greg Gorsuch wrote:
>
>> Where are the sleep logistics handled? Is it with the X server, the NVIDIA
>> drivers, the Linux Kernel, or somewhere else? Is it possible to capture
>> the
>> communications on Windows 10 to identify how it is being handled. I don't
>> get the feeling it should be that complex to fix or at least implement a
>> work around since xrander is able to bring the monitor back online.
>>
>
> It sounds like when you go dpms off, the monitor unregisters and when
> you go dpms on, the monitor re-registers.
> Then some semi-smart randr daemon kicks in and adjusts the layout, but
> does not so when the monitor comes back.
>
> Try to log the setup in the various modes:
>
> xset dpms force standby; sleep 10; xrandr --current > ~/randr.standby;
> xset dpms force suspend; sleep 10; xrandr --current > ~/randr.suspend;
> xset dpms force off; sleep 10; xrandr --current > ~/randr.off; xset
> dpms force on
>
> Also try the behavior on a "naked" X11 server (no desktop session, only
> an xterm) to see whether some client or the server adjusts the randr setup.
>
> Cheers,
> Thomas
>
--
Greg Gorsuch
randr.off
Description: Binary data
randr.standby
Description: Binary data
randr.suspend
Description: Binary data
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s
Re: Dell P2715Q Monitor does not wake up after sleep (off, standby, or suspend)
I don't think the monitor ever worked correctly in Linux in this regard. It is a couple years old. It is still under warranty, but Dell says they won't help since it might involve Linux. It does appear to work correctly under Windows 10 from the limited testing I did. Since this is the case it should be possible to make it work with Linux. That being said if it was possible to demonstrate some aspect of it is flawed under Windows then I suspect they might help. Where are the sleep logistics handled? Is it with the X server, the NVIDIA drivers, the Linux Kernel, or somewhere else? Is it possible to capture the communications on Windows 10 to identify how it is being handled. I don't get the feeling it should be that complex to fix or at least implement a work around since xrander is able to bring the monitor back online. __ When was this purchased? What is its date of manufacture? Did it ever work right with any Linux distro or kernel? Any chance you can still return it to vendor? I suspect this may well be a problem with no other solution. https://www.newegg.com/Product/Product.aspx?Item=N82E16824260115 reviews indicate I'm not the only one with DisplayPort sleep mode trouble with a Dell display. My Dell U2913WM behaves as expected, unless connected via DisplayPort. When connected to my Dell DisplayPort-equipped PCs via DisplayPort, it absolutely must be powered up before turning on the PC. Otherwise, it stays in sleep mode indefinitely. I managed to get Dell to replace it next day on my first phone call, but eventually Dell refused further help because my Dell /PCs/ were "out of support". -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: https://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
Re: Dell P2715Q Monitor does not wake up after sleep (off, standby, or suspend)
Gregory Gorsuch composed on 2017-08-07 11:11 (UTC-0400): > I am having an issue with my Dell P2715Q monitor not waking up from > standby, suspend, and off. This problem seems to only occur on > Linux. I have tried Windows 10 and the Dell monitor seems to wake up > o.k. so far. The monitor is connected through a display port. > I would appreciate help solving this problem. I have created a > script using the output from "*xscreensaver-command -watch*" to use > *xrandr* to turn the screen on, but this is a bit of a band-aide > since the screen becomes visible behind the screen saver while the > Dell monitor is being turned back on by the script. When was this purchased? What is its date of manufacture? Did it ever work right with any Linux distro or kernel? Any chance you can still return it to vendor? I suspect this may well be a problem with no other solution. https://www.newegg.com/Product/Product.aspx?Item=N82E16824260115 reviews indicate I'm not the only one with DisplayPort sleep mode trouble with a Dell display. My Dell U2913WM behaves as expected, unless connected via DisplayPort. When connected to my Dell DisplayPort-equipped PCs via DisplayPort, it absolutely must be powered up before turning on the PC. Otherwise, it stays in sleep mode indefinitely. I managed to get Dell to replace it next day on my first phone call, but eventually Dell refused further help because my Dell /PCs/ were "out of support". -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: https://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
