From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 89431] Monitor is deactivated after DPMS activates
Date: Fri, 11 Sep 2015 19:31:04 +0000 [thread overview]
Message-ID: <bug-89431-502-NBNAsawLkf@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-89431-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 767 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=89431
rob@emanuele.us changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |NOTABUG
--- Comment #11 from rob@emanuele.us ---
I'd like to close this as it seems to be working now. The issue was that at
least one of the 3 monitors attached had to be connected with either an actual
Display Port connection or (in my case) an active Display Port to DVI
connection.
Without that connection it would seem to trigger that power event that was
reported.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2163 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2015-09-11 19:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-89431-502@http.bugs.freedesktop.org/>
2015-03-05 1:57 ` [Bug 89431] Monitor is deactivated after DPMS activates bugzilla-daemon
2015-03-05 2:01 ` bugzilla-daemon
2015-03-05 17:50 ` bugzilla-daemon
2015-03-06 0:57 ` bugzilla-daemon
2015-03-18 18:35 ` bugzilla-daemon
2015-03-23 3:05 ` bugzilla-daemon
2015-09-11 19:31 ` bugzilla-daemon [this message]
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-89431-502-NBNAsawLkf@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox