Created attachment 45489 [details] xorg.0.log I have verified that this is not a problem with the cable nor the monitor (all combinations of monitor and cable work when plugged into DVI-1 and none work when plugged into DVI-2) xrandr sees the second monitor and detects its make and optimal resolution properly: jrb@shiloh:~$ xrandr Screen 0: minimum 320 x 200, current 2560 x 1024, maximum 8192 x 8192 DVI-I-1 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 376mm x 301mm 1280x1024 60.0*+ 75.0 1280x960 60.0 1152x864 75.0 1280x720 60.0 1024x768 75.1 70.1 66.0 60.0 832x624 74.6 800x600 72.2 75.0 60.3 56.2 640x480 72.8 75.0 66.7 60.0 720x400 70.1 DVI-I-2 connected 1280x1024+1280+0 (normal left inverted right x axis y axis) 338mm x 270mm 1280x1024 60.0*+ 1280x960 60.0 1152x864 75.0 1024x768 75.1 70.1 60.0 832x624 74.6 800x600 72.2 75.0 60.3 56.2 640x480 72.8 75.0 66.7 60.0 720x400 70.1 jrb@shiloh:~$ But the monitor (either monitor) reports "no signal" when plugged into DVI-2. Here is
Created attachment 45490 [details] lspci -vvnn
Created attachment 45491 [details] dmesg
Hi. FYI the second DVI output works with the blob, so this is clearly not a hardware issue.
I am experiencing the same issue with the same video card. I am running x-edgers ubuntu ppa version of nouveau: xserver-xorg-video-nouveau: Installed: 1:0.0.16+git20110214.46acb7e0-0ubuntu0sarvatt2~maverick Candidate: 1:0.0.16+git20110214.46acb7e0-0ubuntu0sarvatt2~maverick
I'm seeing the same problem with the exact same hardware. However, if I boot off the Ubuntu Natty live CD, I get output to both monitors correctly. I've also experimented with the live CD and tried booting from it, but having the ISO on one of my partitions and have grub boot off the ISO. In this case I don't get multiple monitors even though it's the exact same ISO. This makes me think it's a timing issue.
Same here. See https://bugzilla.redhat.com/show_bug.cgi?id=744899 as a reference.
You might consider getting some logs with drm.debug=6 (kernel parameter) This will give you driver specific tracing and kms tracing.
FYI drm.debug=1 is only the default tracing (lot's of ioctl messages!), 2 is driver information, 4 is kms information, they are a bitmask, so 3=normal+driver and 5=normal+kms
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.