Bug 515316

Summary:	DPMS (Suspend, Off, On) doesn't work if Kernel Mode Setting (KMS) enabled
Product:	[Fedora] Fedora	Reporter:	Tony Nelson <tonynelson>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	11	CC:	c.shoemaker, itamar, kernel-maint, rhughes
Target Milestone:	---
Target Release:	---
Hardware:	i586
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-06-28 13:58:08 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Tony Nelson 2009-08-03 17:19:41 UTC

Description of problem:
DPMS Suspend works with Kernel Mode Setting (KMS) On in 2.6.29.4 kernel but not in later 2.6.29.5 or 2.6.29.6 kernels; it works with all those kernels if KMS if off.  Gnome Power Manager can't Suspend the display nor can `xset dpms force suspend` (or "off") if booted without "nomodeset in kernels after 2.6.29.4.

This is on an old ASUS A7V-133 MB, Athlon 1.2GHz, 768MB, ATI Technologies Inc Radeon RV100 QY [Radeon 7000/VE] rev 0, on a Princeton EO930 CRT display.

Version-Release number of selected component (if applicable):
kernel-2.6.29.6-213.fc11.i586
kernel-2.6.29.5-208.fc11.i586
(and other nearby kernels from Koji)

How reproducible:
always

Steps to Reproduce:
1. boot affected kernel without nomodeset
2. `xset dpms force suspend`
3. boot unaffected kernel or affected kernel with nomodeset
4. `xset dpms force suspend`
  
Actual results:
2. No change to display
4. Display Suspends

Expected results:
Display is Suspended to low power mode.

Additional info:
Note the ATI Radeon RV100 and the CRT display.

Comment 1 Bug Zapper 2010-04-28 09:31:47 UTC

This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11.  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 '11'.

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 11'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 11 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 2 Chris Shoemaker 2010-05-01 15:03:10 UTC

I seem to have the same problem with:

kernel-2.6.32.11-99.fc12.x86_64
00:02.0 VGA compatible controller: Intel Corporation Pineview Integrated Graphics Controller (rev 02)

I suggest bumping version to Fedora 12

Comment 3 Bug Zapper 2010-06-28 13:58:08 UTC

Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 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.