Bug 43520 - DPMS does not work for Matrox Millennium II
Summary: DPMS does not work for Matrox Millennium II
Status: CLOSED DUPLICATE of bug 43519
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: XFree86-Servers   
(Show other bugs)
Version: 7.1
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Mike A. Harris
QA Contact: David Lawrence
Depends On:
TreeView+ depends on / blocked
Reported: 2001-06-05 14:25 UTC by Karl Hakimian
Modified: 2007-04-18 16:33 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-06-05 14:25:47 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Karl Hakimian 2001-06-05 14:25:43 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux 2.4.4 i686; en-US; rv:0.9)

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:

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:27 UTC
Same bug entered twice.

*** This bug has been marked as a duplicate of 43519 ***

Note You need to log in before you can comment on or make changes to this bug.