Bug 43668 - Secondary monitor always in standby on dual head NV94
Summary: Secondary monitor always in standby on dual head NV94
Status: RESOLVED INVALID
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/nouveau (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Nouveau Project
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-09 07:28 UTC by sep16
Modified: 2013-08-18 18:09 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
Xorg log using nouveau-0.0.16_pre20111109 (62.48 KB, text/plain)
2011-12-09 07:28 UTC, sep16
no flags Details
xrandr -q output using nouveau-0.0.16_pre20111109 (1.14 KB, text/plain)
2011-12-09 07:29 UTC, sep16
no flags Details
lspci -vvv (22.17 KB, text/plain)
2011-12-09 07:30 UTC, sep16
no flags Details
dmesg using nouveau-0.0.16_pre20111109 (91.66 KB, text/plain)
2011-12-09 07:31 UTC, sep16
no flags Details
dmesg using nvidia-290.10 (87.09 KB, text/plain)
2011-12-09 07:31 UTC, sep16
no flags Details

Description sep16 2011-12-09 07:28:56 UTC
Created attachment 54270 [details]
Xorg log using nouveau-0.0.16_pre20111109

After switching from the nVidia binary drivers to nouveau, I am unable to use
my dual head setup; the second monitor refuses to come out of standby.

xrandr -q reports that the monitors are recognized and correctly configured.  
In gnome-shell I can drag a window off of the working monitor, so it appears
that the desktop is configured as expected, just that the secondary monitor is
not receiving a signal.

It seems to work fine with no xorg.conf, and I tried various configurations for about six hours with no success.  The only thing was that when I used the RightOf/LeftOf options in the Monitors sections, gnome3 would come up in fallback mode.

nVidia binary drivers 290.10 (and earlier) have worked fine.

 - XFX nVidia GeForce 9600GT (NV50/NV94) w/ dual DVI-I outputs
 - dual NEC 2560x1600 monitors
 - xorg-server 1.11.2
 - nouveau 0.0.16_pre20111109 (also tried _pre20110323)
 - Gentoo amd64 linux-3.1.0

I'll attach some basic logs; let me know if you need anything else.
Comment 1 sep16 2011-12-09 07:29:50 UTC
Created attachment 54271 [details]
xrandr -q output using nouveau-0.0.16_pre20111109
Comment 2 sep16 2011-12-09 07:30:22 UTC
Created attachment 54272 [details]
lspci -vvv
Comment 3 sep16 2011-12-09 07:31:20 UTC
Created attachment 54273 [details]
dmesg using nouveau-0.0.16_pre20111109
Comment 4 sep16 2011-12-09 07:31:54 UTC
Created attachment 54274 [details]
dmesg using nvidia-290.10
Comment 5 Ben Skeggs 2011-12-09 17:02:40 UTC
Do both displays work if you tell nouveau to attempt to set your chipset to its full clock speeds?  (DISCLAIMER: do this at your own risk) Append "nouveau.perflvl_wr=7777 nouveau.perflvl=3" to your kernel options when you boot.
Comment 6 sep16 2011-12-13 14:29:55 UTC
No.  The first time I tried "startx" it crashed; the console was unresponsive, but I was able to ssh in to reboot.  The second time one monitor came up, with the background image and some random green pixels, then went completely white.
Comment 7 Ilia Mirkin 2013-08-18 18:09:12 UTC
It appears that this bug report has laid dormant for quite a while. Sorry we haven't gotten to it. Since we fix bugs all the time, chances are pretty good that your issue has been fixed with the latest software. Please give it a shot. (Linux kernel 3.10.7, xf86-video-nouveau 1.0.9, mesa 9.1.6, or their git versions.) If upgrading to the latest isn't an option for you, your distro's bugzilla is probably the right destination for your bug report.

In an effort to clean up our bug list, we're pre-emptively closing all bugs that haven't seen updates since 2011. If the original issue remains, please make sure to provide fresh info, see http://nouveau.freedesktop.org/wiki/Bugs/ for what we need to see, and re-open this one.

Thanks,

The Nouveau Team


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.