From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 53391] New: nouveau: wrong display output order
Date: Sun, 3 Feb 2013 18:20:49 +0000 (UTC) [thread overview]
Message-ID: <bug-53391-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=53391
Summary: nouveau: wrong display output order
Product: Drivers
Version: 2.5
Kernel Version: 3.8-rc6
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
AssignedTo: drivers_video-dri@kernel-bugs.osdl.org
ReportedBy: stijn+bugs@linux-ipv6.be
Regression: No
My graphics card is a Gainward GTX480
(http://www.gainward.com/main/vgapro.php?id=238). It has 2 DVI outputs, and 1
mini HDMI output. The DVI outputs are numbered on the card, with DVI 1 being
the closest to the PCIe slot, then DVI 2, and finally the mini HDMI.
My primary (left) monitor, is connected to DVI 1, my secondary (right) monitor
to DVI 2. When I boot the computer, the BIOS initializes and uses the monitor
on DVI 1. Grub is displayed on the primary monitor, and the kernel initially
outputs to the primary monitor as well.
However, as soon as the nouveau module is loaded, the primary monitor goes to
standby and the kernel now uses the secondary monitor (on DVI 2) as primary.
When X starts (no Xorg.conf file), it is also displayed on the secondary
monitor.
When using either efifb, vesafb or uvesafb, the monitor on DVI 1 is always the
primary monitor. X with nvidia.ko also uses DVI 1 as the primary display.
Finally, when booting Windows, the startup screen is also displayed on the
monitor connected to DVI 1.
Here comes the weird part: when I am in X, and run xrandr, it does show 3
connected devices: DVI-I-1, DVI-I-2, and HDMI-1, with DVI-I-2 being the only
active one. So it seems that in X, the output order is correct, but with
nouveaufb the DVI connectors are swapped.
I will attach the output of dmesg here. If anything else is needed, please let
me know and I'll be happy to add it.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next reply other threads:[~2013-02-03 18:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-03 18:20 bugzilla-daemon [this message]
2013-02-03 18:22 ` [Bug 53391] nouveau: wrong display output order bugzilla-daemon
2013-02-09 16:46 ` bugzilla-daemon
2013-02-09 17:43 ` bugzilla-daemon
2013-02-09 17:59 ` bugzilla-daemon
2013-02-09 19:00 ` bugzilla-daemon
2013-02-09 20:11 ` bugzilla-daemon
2013-02-09 22:09 ` bugzilla-daemon
2013-02-09 22:37 ` bugzilla-daemon
2013-02-11 22:12 ` bugzilla-daemon
2013-02-12 12:54 ` bugzilla-daemon
2013-02-12 21:36 ` bugzilla-daemon
2013-02-13 0:53 ` bugzilla-daemon
2021-12-08 9:47 ` 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-53391-2300@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.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 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.