From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 86320] Monitor on DisplayPort doesn't wake up
Date: Sat, 30 May 2015 07:46:02 +0000 [thread overview]
Message-ID: <bug-86320-502-OWTsBcwcGK@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-86320-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 559 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=86320
--- Comment #8 from Niels Ole Salscheider <niels_ole@salscheider-online.de> ---
This sounds similar to https://bugs.freedesktop.org/show_bug.cgi?id=90340.
Maybe you could try if the problem also occurs in your BIOS screen? I have
found similar reports by windows users and it might really be some hw / cable
issue.
Apart from that it seems that most (all?) setups that cause problems have a
screen with a 2560x1600 resolution...
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1510 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
next prev parent reply other threads:[~2015-05-30 7:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-86320-502@http.bugs.freedesktop.org/>
2014-11-17 16:46 ` [Bug 86320] Monitor on DisplayPort doesn't wake up bugzilla-daemon
2014-11-17 21:27 ` bugzilla-daemon
2014-11-19 15:07 ` bugzilla-daemon
2015-03-31 20:52 ` bugzilla-daemon
2015-03-31 20:56 ` bugzilla-daemon
2015-05-29 23:07 ` bugzilla-daemon
2015-05-29 23:09 ` bugzilla-daemon
2015-05-30 7:46 ` bugzilla-daemon [this message]
2015-05-30 11:46 ` bugzilla-daemon
2015-05-30 11:58 ` bugzilla-daemon
2015-05-30 12:00 ` bugzilla-daemon
2015-05-30 19:26 ` bugzilla-daemon
2015-09-21 14:58 ` bugzilla-daemon
2015-10-19 8:26 ` bugzilla-daemon
2015-11-28 18:50 ` bugzilla-daemon
2019-11-19 8:58 ` bugzilla-daemon
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-86320-502-OWTsBcwcGK@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