Bug 43519

Summary:	DPMS does not work for Matrox Millennium II
Product:	[Retired] Red Hat Linux	Reporter:	Karl Hakimian <hakimian>
Component:	XFree86-Servers	Assignee:	Mike A. Harris <mharris>
Status:	CLOSED ERRATA	QA Contact:	David Lawrence <dkl>
Severity:	high	Docs Contact:
Priority:	medium
Version:	7.1
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2001-06-05 16:17:26 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 Karl Hakimian 2001-06-05 14:25:10 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux 2.4.4 i686; en-US; rv:0.9)
Gecko/20010505

Description of problem:
DPMS does not seem to work correctly for my 8Meg Matrox Millennium II
card. After activating DPMS (both in XFree3 and XFree4) my monitor will
correctly turn off before logging in. After I login "xset q" shows that
DPMS is disabled and the times are all 10.

using "xset dpms 1200 2400 3600" to enable DPMS is accepted, but in 20
minutes changes it back to 10 10 10 and disabled.

"xset dpms force off" does turn off the monitor.

Any time I have played with dpms (including just doing xset q to look at
what it is) X will die within a short time (not sure how long, but it
seems to be between an hour and a day).

This card and monitor worked fine under redhat 6.1.


How reproducible:
Always

Steps to Reproduce:
1.Login. Notice that xset q reports DPMS disabled
2.enable dpms xset dpms 1200 2400 3600
3.wait 20 minutes and do xset q
	

Actual Results:  dpms is disabled again.

Expected Results:  Screen should have blanked

Additional info:

Comment 1 David Lawrence 2001-06-05 16:17:22 UTC

*** Bug 43520 has been marked as a duplicate of this bug. ***

Comment 2 Mike A. Harris 2001-06-13 01:17:08 UTC

This is not an XFree86 bug, it is a bug that has been fixed in
xscreensavers and gnome-control panel.  Please upgrade.

Comment 3 Karl Hakimian 2001-06-13 14:46:06 UTC

Turning off xscreensaver did indeed fix the problem. Any idea when an updated
RPM will be released?