1. Computers
  2. Display Drivers
  3. Graphics Cards
  4. Memory
  5. Motherboards
  6. Processors
  7. Software
  8. Storage
  9. Operating Systems


Facebook RSS Twitter Twitter Google Plus


Phoronix Test Suite

OpenBenchmarking.org

ATIpower: ATI Linux GPU Overclocking

Michael Larabel

Published on 2 April 2007
Written by Michael Larabel
Page 1 of 1 - Comment On This Article

When it comes to overclocking ATI Radeon graphics cards under Linux the only real option has been using rovclock. Rovclock is a Radeon overclocking utility written and developed by Sebastian Witt. This tool has been in development since 2005 but it took quite a while before the Radeon R300/R400 series was even supported. Rovclock still lacks support for the Radeon X1000 (R500) series, however, there is a new contender to the ATI Linux GPU overclocking arena and that is ATIpower.

The first and only release available at this time for ATIpower is version 0.1, which was released this past October. This utility is designed for changing the frequency of the GPU and memory on Linux -- you can either underclock or overclock with ATIpower. However, unlike rovclock, you cannot tweak the memory timings with this software package. The overclocking process is handled using the ATI X extension (ATIpower borrows code from the fireglcontrolpanel). It is important to keep in mind that this as with rovclock is a third party utility that is not endorsed by ATI/AMD and could potentially damage or destroy your graphics card. Use this software at your own risk.

$ aticonfig --lsp
core/mem [flags]
-----------------
1: 128/135 MHz [low voltage]
2: 324/135 MHz


Contrary to what is displayed from aticonfig --lsp for listing the various PowerPlay states, there are more. All available states are listed in the /var/log/Xorg.0.log, and below is an example from a Mobility Radeon X1400.

(II) fglrx(0): POWERplay version 3. 5 power states available:
(II) fglrx(0): 1. 392/342MHz @ 60Hz [enable load balancing]
(II) fglrx(0): 2. 128/135MHz @ 60Hz [low voltage, enable sleep]
(II) fglrx(0): 3. 209/135MHz @ 60Hz [low voltage, enable sleep]
(II) fglrx(0): 4. 324/135MHz @ 60Hz [enable sleep]
(II) fglrx(0): 5. 338/342MHz @ 60Hz [enable sleep, thermal diode mode]

Using the ATI X extension ATIpower accesses this information and then makes it possible for the end-user to specify one of these power-states from the expanded list. Below is the output available from ATIpower on the same GPU.

$ ./atipower
* id: 1, gpu: 391 mhz, mem: 342 mhz
id: 2, gpu: 128 mhz, mem: 135 mhz
id: 3, gpu: 209 mhz, mem: 135 mhz
id: 4, gpu: 324 mhz, mem: 135 mhz
id: 5, gpu: 337 mhz, mem: 342 mhz

ATIpower can be used by running atipower and then passing only the id of the power-state as the argument. As this was the output from a Mobility Radeon, no ATI OverDrive states were listed but only states for downclocking the GPU to save on power and reduce the heat output. While we have only begun testing ATIpower, a reader who initially brought this to our attention has claimed 25% more frames on glxgears and fgl_glxgears when at its maximum OverDrive state compared to the standard operating frequencies. While the addition of AMD Catalyst Control Center was nice, don't look for official OverDrive overclocking support in the Linux drivers for sometime. The ATIpower utility does seem promising and should work with any Radeon graphics card with the fglrx drivers where the multiple power-states are available.

Shortly we will follow up with an article that looks at overclocking various Radeon desktop graphics cards under Linux and their impact on the overall performance. In the mean time, if you have tried out ATIpower, please share your thoughts on the Phoronix Forums.

About The Author
Michael Larabel is the principal author of Phoronix.com and founded the web-site in 2004 with a focus on enriching the Linux hardware experience and being the largest web-site devoted to Linux hardware reviews, particularly for products relevant to Linux gamers and enthusiasts but also commonly reviewing servers/workstations and embedded Linux devices. Michael has written more than 10,000 articles covering the state of Linux hardware support, Linux performance, graphics hardware drivers, and other topics. Michael is also the lead developer of the Phoronix Test Suite, Phoromatic, and OpenBenchmarking.org automated testing software. He can be followed via and or contacted via .
Latest Linux Hardware Reviews
  1. AMD's New Athlon/Semprons Give Old Phenom CPUs A Big Run For The Money
  2. 13-Way Low-End GPU Comparison With AMD's AM1 Athlon
  3. ASUS AM1I-A: A Mini-ITX Board For Socketed Kabini APUs
  4. Mini-Box M350: A Simple, Affordable Mini-ITX Case
Latest Linux Articles
  1. How Much Video RAM Is Needed For Catalyst R3 Graphics?
  2. Ubuntu 12.04 LTS vs. 14.04 LTS Cloud Benchmarks
  3. Ubuntu 12.04.4 vs. 13.10 vs. 14.04 LTS Desktop Benchmarks
  4. AMD OpenCL Performance With AM1 Kabini APUs
Latest Linux News
  1. Packard Bell LM85 Now Supported By Coreboot
  2. AmazonBasics External USB 2.0 DVD Writer For Linux
  3. TP-LINK TG-3468: A $12 Linux PCI-E Gigabit Network Adapter
  4. Linux 3.15 Lands Some DRM Graphics Driver Fixes
  5. AMD Is Disabling DPM Support For RV770 GPUs
  6. ReactOS Working On A Community Windows OS
  7. eRacks Keeps Pushing Linux, Open-Source Systems After 15 Years
  8. Borderlands Is Being Considered For Linux
  9. Mesa 10.0 & 10.1 Stable Get Updated
  10. Git 2.0 Test Releases Begin With Many Changes
  11. Wine 1.7.17 Works On Its Task Scheduler, C Run-Time
  12. The Improv ARM Board Still Isn't Shipping; Riding A Dead Horse?
Latest Forum Discussions
  1. The GNOME Foundation Is Running Short On Money
  2. Updated and Optimized Ubuntu Free Graphics Drivers
  3. Catalyst 14.3 Beta
  4. Suggestions about how to make a Radeon HD 7790 work decently?
  5. Radeon 8000M problematic on Linux?
  6. Linux Kernel Developers Fed Up With Ridiculous Bugs In Systemd
  7. After Jack Keane, RuseSoft will briing Ankh 3 to Linux through Desura
  8. Suspected PHP Proxy Issue