All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 212373] New: Dual monitors does not sleep when inactive
Date: Sun, 21 Mar 2021 18:19:17 +0000	[thread overview]
Message-ID: <bug-212373-2300@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=212373

            Bug ID: 212373
           Summary: Dual monitors does not sleep when inactive
           Product: Drivers
           Version: 2.5
    Kernel Version: 5.8.0-45
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri@kernel-bugs.osdl.org
          Reporter: edouard@the-redunicorn.fr
        Regression: No

Hi,

Recently I noticed an issue with my dual monitors configuration. I used to have
my monitors sleeping after 5 minutes of inactivity, as setup in gnome control
center. 
When I changed them, the behavior was not that described anymore. It is not
related to the monitors as far as this sleeping feature works with an other OS.
The difference between the new ones and the old ones *may* be the DPMS feature.

The new behavior observed is: 
- after X minutes of inactivity, monitors go black 
- instead of having a "no signal" popup, monitors re-up after few seconds 
- after X minutes again of inactivity, monitors go black again 
- etc
I get the same by typing xset dpms force off.
When I try this with only one monitor connected, it goes to sleep as expected.

The fact is, after seeking for hours in forums, I found that :
https://askubuntu.com/questions/1047182/dual-monitors-on-18-04-with-radeon-rx-580-gpu.
And for an unknown reason, despite the fact the issue described there does not
seem to be related to mine, disabling the DC layer of amdgpu works! In other
words, after X minutes of inactivity both monitors go to sleep as expected.

I hope this is not to confusing.. it is quite hard to describe as a non-english
native person.

Cheers.

PS: my 'uname -a' returns Linux XXXX 5.8.0-45-generic #51~20.04.1-Ubuntu SMP
Tue Feb 23 13:46:31 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

                 reply	other threads:[~2021-03-21 18:19 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-212373-2300@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.