From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 30589] New: Dual screen connected with VGA works, but not with DVI on G94 [GeForce 9600GT]
Date: Sun, 3 Oct 2010 11:30:49 -0700 (PDT) [thread overview]
Message-ID: <bug-30589-8800@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=30589
Summary: Dual screen connected with VGA works, but not with DVI
on G94 [GeForce 9600GT]
Product: xorg
Version: git
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
ReportedBy: diego.abelenda-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
Created an attachment (id=39139)
--> (https://bugs.freedesktop.org/attachment.cgi?id=39139)
Both monitors are connected via DVI after a fresh reboot
When connecting my two identical Acer monitors with their VGA input (using a
DVI-to-VGA adapter) the dual screen works and xrandr is capable of changing the
resolution of both monitors independently.
But when connecting both screens to DVI-I input one monitor stays black saying
"no signal" even if xrandr says that the screen is connected and at native
resolution.
It seems that the video= option affects this, and changes the behavior when one
monitor is connected to VGA while the other is connected to DVI input. If the
option "video=DVI-I-x:1920x1080eD" is passed for both screens (DVI-I-1 and
DVI-I-2) only the VGA one shows something while we expect only the DVI one to
work and not the VGA (as stated here : ) . If no option is passed both work as
expected.
EDID are parsed correctly and monitors are detected correctly as will be shown
in the multiple xrandr outputs that will follow.
As discussed on IRC it is impossible to force the subconnector with xrandr so
we can't test this way. But anyway the sub-connectors are selected correctly.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2010-10-03 18:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-03 18:30 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-30589-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2010-10-03 18:32 ` [Bug 30589] Dual screen connected with VGA works, but not with DVI on G94 [GeForce 9600GT] bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-10-03 18:33 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-10-03 18:33 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-10-03 18:34 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-10-03 18:35 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-10-03 18:38 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-18 18:09 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
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-30589-8800@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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.