From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 102300] Missing 1920x1080_59.94Hz mode (Second monitor shows black screen but has signal)
Date: Mon, 25 Sep 2017 20:04:23 +0000 [thread overview]
Message-ID: <bug-102300-502-K8L2OL9Xyx@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-102300-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 442 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=102300
--- Comment #12 from fayn@mt2015.com ---
Arch stock kernel 4.12.13-1 still boots one monitor black, but can be restored
with xrandr.
Wayland sessions work, and they never lose signal in any situation. Xorg
sessions do randomly cause black screen
(https://bugs.freedesktop.org/show_bug.cgi?id=102956).
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1417 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-09-25 20:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-18 18:42 [Bug 102300] Second monitor shows black screen but has signal bugzilla-daemon
2017-08-18 19:00 ` bugzilla-daemon
2017-08-18 19:26 ` bugzilla-daemon
2017-08-19 10:51 ` bugzilla-daemon
2017-08-22 20:07 ` [Bug 102300] Missing 1920x1080_59.94Hz mode (Second monitor shows black screen but has signal) bugzilla-daemon
2017-08-23 1:24 ` bugzilla-daemon
2017-08-23 13:30 ` bugzilla-daemon
2017-08-23 13:32 ` bugzilla-daemon
2017-08-24 3:29 ` bugzilla-daemon
2017-08-24 8:34 ` bugzilla-daemon
2017-08-29 9:40 ` bugzilla-daemon
2017-08-29 9:43 ` bugzilla-daemon
2017-08-30 8:06 ` bugzilla-daemon
2017-09-25 20:04 ` bugzilla-daemon [this message]
2017-11-04 7:58 ` bugzilla-daemon
2019-11-19 8:21 ` 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-102300-502-K8L2OL9Xyx@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;
as well as URLs for NNTP newsgroup(s).