Created attachment 527301 [details] xrandr --verbose Description of problem: Although the second head is connected and recognized correctly by nouveau/xrandr nothing is show if the screen is enabled. Version-Release number of selected component (if applicable): kernel-3.1.0-0.rc9.git0.0.fc16.x86_64 glibc-2.14.90-10.x86_64 glibc-2.14.90-10.i686 xorg-x11-drv-nouveau-0.0.16-27.20110720gitb806e3f.fc16.x86_64 No xorg.conf.
Created attachment 527302 [details] dmesg
Created attachment 527303 [details] xorg log
Maybe I should add that the screen input is not even triggered and everything stays at no signal on the second screen.
Created attachment 527306 [details] lspci -vvv
I just did some more testing on this. Screen 1: Samsung SyncMaster 205BW Screen 2: Samsung SyncMaster 940B The problem occurs with both screens connected via DVI directly (the card has two DVI outs). Both screens have two inputs: DVI and DSUB If I use a DSUB-to-DVI-adapter on the second screens DSUB input and connect it everything works.
I'm having the same issue - one DVI output is working, the other reports no signal. xrandr reports both DVI-I-1 and DVI-I-2 as connected and the GNOME display properties component correctly identifies both monitors. My setup: kernel-3.1.0-7.fc16.x86_64 xorg-x11-drv-nouveau-0.0.16-27.20110720gitb806e3f.fc16.x86_64 no xorg.conf HP Z400 Workstation 0f:00.0 VGA compatible controller: nVidia Corporation G96 [Quadro FX 380] (rev a1) (prog-if 00 [VGA controller]) Subsystem: nVidia Corporation Device 063b Physical Slot: 2 Flags: bus master, fast devsel, latency 0, IRQ 24 Memory at f6000000 (32-bit, non-prefetchable) [size=16M] Memory at e0000000 (64-bit, prefetchable) [size=256M] Memory at f4000000 (64-bit, non-prefetchable) [size=32M] I/O ports at e000 [size=128] Expansion ROM at <unassigned> [disabled] Capabilities: <access denied> Kernel driver in use: nouveau Kernel modules: nouveau, nvidiafb My card matches that of upstream issue <https://bugs.freedesktop.org/show_bug.cgi?id=36142>, "Second DVI output produces no signal with nVidia G96 [Quadro FX 380] (rev a1)".
(In reply to comment #5) > If I use a DSUB-to-DVI-adapter on the second screens DSUB input and connect it > everything works. I've now confirmed that this is true for my setup as well.
PING! Still an issue with latest f17 + updates-testing. Ben: Anything more you need to test/reproduce? Anything we can do?
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.