On Thu, Jun 21, 2007 at 08:24:46AM +0200, Michel Dänzer wrote: > On Wed, 2007-06-20 at 20:08 +0200, Robert Siemer wrote: > > I'm pleased to announce a reliable and fast test scenario: > > > > $ xset dpms 10 20 30 > > [wait 10 seconds] > > [screen goes blank (DPMS gets active)] > > $ xset -dpms > > [no DPMS kicks in, not even after 10 seconds] > > $ xset +dpms > > [wait 10 seconds] > > > > What I now expect is that DPMS suspends (or actually "standbys") the > > screen, but that does not happen. The screen stays visible, passing 10, > > 20, 30 and more seconds. > > > > Can anybody confirm that on other systems? > > Yes. Running xset dpms 10 20 30 again seems to fix it though, so > probably the code handling xset +dpms doesn't re-enable something it > should.
I can reproduce this here with Xserver 1.3-11 and ati 6.6.192 (Thinkpad R52 with X300 board). 'xset q' says Enabled 600 600 600, so it confirms the above diagnostics. BUT, I can't reproduce the problem ati randr-1.2 git (as of commit 7b3e22e96cfc98621bd20fa76317e6d8f7242165) on similar hardware. After 'xset +dpms', 'xset q' says Enabled 10 20 30, and the display goes black after 10 seconds, as expected. So I wonder whether it could actually be driver-related and already fixed upstream. Brice
