Description of problem: After screen saver kicks in and turns off laptop LCD, external monitor attached via DisplayPort constantly turns off and on. Would like external monitor to remain off just like main LCD built in to laptop. Version-Release number of selected component (if applicable): Kernel: 3.4.3-1.fc17.x86_64 xorg-x11-drv-nouveau-0.0.16-35.20120306gitf5d1cd2.fc17.x86_64 How reproducible: Always Steps to Reproduce: 1. Power on laptop and log in 2. Attach external LCD monitor (Dell U2410) via DisplayPort on back of laptop to DisplayPort on back of monitor. 3. Set up mirrored display mode 4. Run xscreensaver-command -lock (or wait for idle timeout for screen to auto-lock and go into power saving mode Actual results: 1. LCD Panel on laptop screen turns off 2. External monitor indicates it's going into power saving mode and successfully does so. Within 1-2 seconds, it comes on again with a blank screen, then says it's going into power savings mode. This repeats itself indefinitely. Expected results: Both laptop LCD panel and external monitor should turn off and remain so until I hit a key or move the mouse. Additional info: Dell E6500 laptop with F17 + GNOME shell. Disabled gnome-screen-saver and installed xscreensaver to attempt resolution of a different issue, but symptoms are the same. lspci shows: --------------------------------------------------------- # lspci -vv -s 01:00.0 01:00.0 VGA compatible controller: nVidia Corporation G98M [Quadro NVS 160M] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device 024f Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 16 Region 0: Memory at f5000000 (32-bit, non-prefetchable) [size=16M] Region 1: Memory at e0000000 (64-bit, prefetchable) [size=256M] Region 3: Memory at f2000000 (64-bit, non-prefetchable) [size=32M] Region 5: I/O ports at df00 [size=128] [virtual] Expansion ROM at f4000000 [disabled] [size=128K] Capabilities: [60] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+ Address: 0000000000000000 Data: 0000 Capabilities: [78] Express (v2) Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <512ns, L1 <4us ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset- DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+ MaxPayload 128 bytes, MaxReadReq 512 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- LnkCap: Port #0, Speed 5GT/s, Width x16, ASPM L0s L1, Latency L0 <512ns, L1 <1us ClockPM- Surprise- LLActRep- BwNot- LnkCtl: ASPM L0s L1 Enabled; RCB 128 bytes Disabled- Retrain- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x16, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- DevCap2: Completion Timeout: Not Supported, TimeoutDis+ DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LnkCtl2: Target Link Speed: 5GT/s, EnterCompliance- SpeedDis-, Selectable De-emphasis: -6dB Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance De-emphasis: -6dB LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete-, EqualizationPhase1- EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest- Capabilities: [100 v1] Virtual Channel Caps: LPEVC=0 RefClk=100ns PATEntryBits=1 Arb: Fixed- WRR32- WRR64- WRR128- Ctrl: ArbSelect=Fixed Status: InProgress- VC0: Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans- Arb: Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256- Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=01 Status: NegoPending- InProgress- Capabilities: [128 v1] Power Budgeting <?> Capabilities: [600 v1] Vendor Specific Information: ID=0001 Rev=1 Len=024 <?> Kernel driver in use: nouveau # --------------------------------------------------------- xrandr: --------------------------------------------------------- $ xrandr Screen 0: minimum 320 x 200, current 1920 x 1200, maximum 8192 x 8192 LVDS-1 connected 1920x1200+0+0 (normal left inverted right x axis y axis) 331mm x 207mm 1920x1200 60.0*+ 59.9 40.0 1920x1080 60.0 1600x1200 59.9 1680x1050 60.0 1400x1050 60.0 1280x1024 59.9 1280x960 59.9 1152x864 60.0 1024x768 59.9 800x600 59.9 640x480 59.4 720x400 59.6 640x400 60.0 640x350 59.8 VGA-1 disconnected (normal left inverted right x axis y axis) DP-1 connected 1920x1200+0+0 (normal left inverted right x axis y axis) 518mm x 324mm 1920x1200 60.0*+ 1920x1080 50.0 60.0 24.0 25.0 30.0 1600x1200 60.0 1280x1024 75.0 60.0 1152x864 75.0 1280x720 50.0 60.0 1440x576 25.0 1024x768 75.1 60.0 1440x480 30.0 800x600 75.0 60.3 720x576 50.0 720x480 59.9 640x480 75.0 60.0 59.9 720x400 70.1 DP-2 disconnected (normal left inverted right x axis y axis) $ ---------------------------------------------------------
Created attachment 594044 [details] 2012-06-24 - Copy of /var/log/Xorg.0.log
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. 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 prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 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 to Fedora 17's end of life. 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 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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. Thank you for reporting this bug and we are sorry it could not be fixed.