DPMS cannot suspend monitor in Gutsy
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xorg-server (Fedora) |
New
|
Undecided
|
Unassigned | ||
xorg-server (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Binary package hint: xserver-
I have an "ATI Technologies Inc RS482 [Radeon Xpress 200]" on-motherboard display adapter. I have to run it with the VESA driver rather than the ATI driver, due to various problems with the ATI driver that prevent it from using resolutions above 640x480 with my monitor.
Under Feisty, DPMS worked fine... the monitor would suspend itself according to the settings in the GNOME Power Management applet.
Under Gutsy, DPMS does not work. The monitor never suspends itself, and it fails even when explicitly activating DPMS from the command line:
$ xset dpms force off # nothing happens!
$ xset q
...
DPMS (Energy Star):
Standby: 0 Suspend: 0 Off: 0
DPMS is Enabled
Monitor is On
...
*HOWEVER*, I *can* activate DPMS using vbetool which directly accesses the BIOS:
$ sudo vbetool dpms off # monitor suspends!
$ sudo vebtool dpms on # monitor turns back on!
So I believe this is a problem with the VESA driver. Here are the relevant portions of my /etc/X11/xorg.conf:
Section "Device"
Identifier "ATI Technologies Inc RS482 [Radeon Xpress 200]"
Driver "vesa"
BusID "PCI:1:5:0"
EndSection
Section "Monitor"
Identifier "DELL P991"
Option "DPMS"
HorizSync 30-107
VertRefresh 48-120
EndSection
Section "Screen"
Identifier "Default Screen"
Device "ATI Technologies Inc RS482 [Radeon Xpress 200]"
Monitor "DELL P991"
SubSection "Display"
EndSection
Section "ServerLayout"
Identifier "Default Layout"
Screen "Default Screen"
InputDevice "Generic Keyboard"
InputDevice "Configured Mouse"
# Uncomment if you have a wacom tablet
# InputDevice "stylus" "SendCoreEvents"
# InputDevice "cursor" "SendCoreEvents"
# InputDevice "eraser" "SendCoreEvents"
EndSection
Related branches
Changed in xorg-server: | |
importance: | Undecided → Medium |
status: | Incomplete → Triaged |
Hi Dan,
Since you can trigger the bug using xset, it sounds like a bug in the server rather than in -vesa, so I'm re-filing against the server.
Also, can you let us know if this is still happening with Hardy?