Difference between revisions of "How to make use of Graphics Chips Power Management features"
(→X.org on Debian) |
(PowerPlay in fglrx) |
||
| Line 3: | Line 3: | ||
radeonfb: Dynamic Clock Power Management enabled | radeonfb: Dynamic Clock Power Management enabled | ||
| − | == | + | ==Using the X.org Radeon driver== |
| + | ===Activation=== | ||
The xorg X server has support for a power saving feature from ATI called PowerPlay. Xorg calls this feature DynamicClocks. It can be enabled in the server by adding '''Option "DynamicClocks" "on"''' in the '''Device''' section in {{path|/etc/X11/xorg.conf}} | The xorg X server has support for a power saving feature from ATI called PowerPlay. Xorg calls this feature DynamicClocks. It can be enabled in the server by adding '''Option "DynamicClocks" "on"''' in the '''Device''' section in {{path|/etc/X11/xorg.conf}} | ||
| Line 23: | Line 24: | ||
{{NOTE|Enabling DynamicClocks crashes some models. If the CPU is entering one of the lower power states (C3 or lower) during Xorg startup the display may stay black. As a workaround disable DynamicClocks in Xorg and use [[Rovclock]] instead. But it does not scale the clocks to match the workload.}} | {{NOTE|Enabling DynamicClocks crashes some models. If the CPU is entering one of the lower power states (C3 or lower) during Xorg startup the display may stay black. As a workaround disable DynamicClocks in Xorg and use [[Rovclock]] instead. But it does not scale the clocks to match the workload.}} | ||
| − | ==Problem with <tt>vbetool</tt>== | + | ===Problem with <tt>vbetool</tt>=== |
When <tt>vbetool</tt> is used to restore the display state (as done by some suspend/resume scripts), the setting of <tt>DynamicClocks</tt> is forgotten and the GPU will consume more power until the next X server startup. You can manually enable DynamicTools again by starting a blank second X server (e.g., by running {{cmdroot|X :1}}) and then exiting it via {{key|Ctrl}}{{key|Alt}}{{key|Backspace}}. | When <tt>vbetool</tt> is used to restore the display state (as done by some suspend/resume scripts), the setting of <tt>DynamicClocks</tt> is forgotten and the GPU will consume more power until the next X server startup. You can manually enable DynamicTools again by starting a blank second X server (e.g., by running {{cmdroot|X :1}}) and then exiting it via {{key|Ctrl}}{{key|Alt}}{{key|Backspace}}. | ||
| − | ==Debian Notes== | + | ===Debian Notes=== |
If your {{Debian}} doesn't have Xorg, yet, see [http://incubator.vislab.usyd.edu.au/roller/page/Steve/20040909 Installing a non-intrusive X.org server on Debian]. | If your {{Debian}} doesn't have Xorg, yet, see [http://incubator.vislab.usyd.edu.au/roller/page/Steve/20040909 Installing a non-intrusive X.org server on Debian]. | ||
| Line 34: | Line 35: | ||
You can also add the following line to your repository list: | You can also add the following line to your repository list: | ||
deb http://people.debian.org/~nobse/xorg-x11/ sarge main | deb http://people.debian.org/~nobse/xorg-x11/ sarge main | ||
| + | |||
| + | ==Using the ATI proprietary driver== | ||
| + | |||
| + | Versions 8.19.10 and higher of the ATI [[fglrx]] driver support "PowerPlay", which "allows for the user to switch between power consumption modes". | ||
==External Sources== | ==External Sources== | ||
Revision as of 15:22, 13 November 2005
Contents
Power Saving With A Framebuffer Console
In order to use the dynamic GPU clock-scaling similar to what X.org has, you need to use the radeonfb kernel module. You'll need to enable the CONFIG_FB_RADEON in your kernel configuration. If setup correctly you should see something like the following in your kernel log:
radeonfb: Dynamic Clock Power Management enabled
Using the X.org Radeon driver
Activation
The xorg X server has support for a power saving feature from ATI called PowerPlay. Xorg calls this feature DynamicClocks. It can be enabled in the server by adding Option "DynamicClocks" "on" in the Device section in /etc/X11/xorg.conf
Section "Device"
Identifier "Videocard0"
Driver "radeon"
VendorName "IBM Thinkpad"
BoardName "ATI Radeon Mobility M9"
Option "DynamicClocks" "on"
EndSection
With this option enabled, the X11 server should print (/var/log/Xorg.0.log):
(**) RADEON(0): Option "DynamicClocks" "on" (II) RADEON(0): Dynamic Clock Scaling Enabled
You do not need to do anything else, it dynamically manages the power consumption itself.
Problem with vbetool
When vbetool is used to restore the display state (as done by some suspend/resume scripts), the setting of DynamicClocks is forgotten and the GPU will consume more power until the next X server startup. You can manually enable DynamicTools again by starting a blank second X server (e.g., by running # X :1) and then exiting it via CtrlAltBackspace.
Debian Notes
If your Debian doesn't have Xorg, yet, see Installing a non-intrusive X.org server on Debian.
Sarge backports are available from here or here.
You can also add the following line to your repository list:
deb http://people.debian.org/~nobse/xorg-x11/ sarge main
Using the ATI proprietary driver
Versions 8.19.10 and higher of the ATI fglrx driver support "PowerPlay", which "allows for the user to switch between power consumption modes".
