From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 89155] Dual monitor setup does not initialize
Date: Mon, 16 Feb 2015 19:32:48 +0000 [thread overview]
Message-ID: <bug-89155-502-K39f4s7cCu@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-89155-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 743 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=89155
--- Comment #4 from Adam Reichold <adam.reichold@t-online.de> ---
(In reply to Alex Deucher from comment #3)
> (In reply to Adam Reichold from comment #2)
> > Maybe as a clarification: Both monitors always initialize properly when only
> > one is connected.
>
> When only one is connected at boot time? If so does it matter which one?
If at boot time, only one monitor is connected, then it does initialize
properly. This is true for both monitors, i.e. VGA-only works and DVI-only
works, but not both at the same time. (It also works correctly if I boot using
only one monitor and attach the second one later.)
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1620 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-02-16 19:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-15 13:53 [Bug 89155] Dual monitor setup does not initialize bugzilla-daemon
2015-02-15 13:54 ` bugzilla-daemon
2015-02-15 14:02 ` bugzilla-daemon
2015-02-16 17:29 ` bugzilla-daemon
2015-02-16 19:32 ` bugzilla-daemon [this message]
2015-08-15 13:12 ` bugzilla-daemon
2016-01-16 11:00 ` bugzilla-daemon
2019-11-19 9:01 ` 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-89155-502-K39f4s7cCu@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