One thing I missed from Windows after my transition to Linux was the ability to easily adjust my GPU's clock speeds and voltages. I went to the godly Arch Wiki and found there's a way to overclock AMD GPUs, but some steps are not very clear and I had to do some googling to get everything working.
EDIT: Vega GPU are not supported as of kernel 4.20.2! Here's a workaround by u/whatsaspecialusername.
First things first, your kernel has to be at least version 4.17 (you can check by running uname -a), although it's recommended to update it to the latest version for system stability, bug fixes and new features (for instance, Hawaii support for overclocking was introduced in 4.20). The driver should be amdgpu (not the proprietary amdgpu-pro). I suggest installing the latest mesa+amdgpu from this PPA for *buntu, but I don't know about other distros. It might not even be a necessary step.
You need to add the parameter amdgpu.ppfeaturemask=0xffffffff to your GRUB configuration. To do so, edit /etc/default/grub as root and add the parameter between the quotes of GRUB_CMDLINE_LINUX_DEFAULT. Save, then run sudo update-grub2 or sudo grub-mkconfig -o /boot/grub/grub.cfg, depending on your distro. Reboot. If you're running any bootloader other than GRUB, check this Arch Wiki page.
Now, we need to find the file with our GPU's clocks and voltages. In my case it was in /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/, but you can find the directory by running readlink -f /sys/class/drm/card0/device.
The file we want to work with is called pp_od_clk_voltage. Mine looked like the following (my card is a Sapphire RX 580 Nitro+ 4GB):
OD_SCLK: 0: 300MHz 750mV 1: 600MHz 769mV 2: 900MHz 887mV 3: 1145MHz 1100mV 4: 1215MHz 1181mV 5: 1257MHz 1150mV 6: 1300MHz 1150mV 7: 1411MHz 1150mV OD_MCLK: 0: 300MHz 750mV 1: 1000MHz 800mV 2: 1750MHz 950mV OD_RANGE: SCLK: 300MHz 2000MHz MCLK: 300MHz 2250MHz VDDC: 750mV 1200mV
We want to edit the P-state #7 for the core and #2 for the VRAM, as those are the values that our GPU is going to run at while under load. On Windows, my optimal values were 1450MHz for core and 2065MHz for memory, so I'm going to edit the file as follows:
sudo sh -c "echo 's 7 1450 1150' > /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/pp_od_clk_voltage"
Where "s" means we're editing the core's values, 7 is the seventh P-state, 1450 is the speed we want in MHz, 1150 is the voltage in mV. Note that I didn't run sudo echo "s 7 1450 1150" > /sys/class/drm/card0/device/pp_od_clk_voltage like the Arch Wiki states, because it would throw an error and not apply the changes (this might have worked without "sudo" if we logged in as root with sudo su, but it's best not to do so for safety reasons). See here.
Same with the VRAM: sudo sh -c "echo 'm 2 2065 950' > /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/pp_od_clk_voltage"
After these two commands the file is going to be the same except for the two lines of the P-states we just edited. We can check by running cat /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/pp_od_clk_voltage.
I didn't mess with voltages because I'm already satisfied with my results and I'm very paranoid about damaging my GPU. If you really want to, please be really careful as you might cause fatal damage to your card!
Once we are done, running sudo sh -c "echo 'c' > /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/pp_od_clk_voltage" will apply the changes and the GPU will start running at those new frequencies when under load.
While I haven't found a way to actively monitor clock speeds à la MSI Afterburner (EDIT: there is actually! See this comment by u/AlienOverlordXenu), I could see a sudden increase in FPS in Heaven Benchmark as soon as I applied the new clocks. I set the camera to free mode (so that it stops moving) and after applying the FPS went from 55-56 to 60-61!
(The guide on ArchWiki also has a command to change the maximum power consumption in Watts: I didn't mess with it as I wasn't sure what was a safe value)
Now there's one problem: every time we reboot our PC the clocks are going to reset. So how do we make them stick?
Assuming your distro has systemd, we can create a service that runs the three commands that edit and apply the clocks at boot. If your distro doesn't have systemd, you can follow these steps.
First, we need to create a script. I named mine "overclock" and put it in /usr/bin/. It looks like this:
#!/bin/sh sudo sh -c "echo 's 7 1450 1150' > /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/pp_od_clk_voltage" sudo sh -c "echo 'm 2 2065 950' > /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/pp_od_clk_voltage" sudo sh -c "echo 'c' > /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/pp_od_clk_voltage"
Then, we have to create a file in /etc/systemd/system/ with a .service extension. I named mine overclock.service:
[Unit] Description=Increase GPU core and memory clocks [Service] Type=oneshot ExecStart=/usr/bin/overclock [Install] WantedBy=multi-user.target
sudo systemctl enable overclock.service will enable our service. After rebooting it should automatically overclock the GPU. We can check if it did by running cat /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/pp_od_clk_voltage.
(It's not necessary, but I also made a script that sets the GPU back to the stock clock speeds. I didn't make a service for it, I just put it in my Documents folder.)
So that should be it! Keep in mind that it might not work on any AMD GPU, in fact I couldn't find a way to do it on my Ryzen+Vega laptop (something with power saving mode I'm guessing), but it's always worth a try. This is my first "real" guide so any feedback is very much appreciated.
Videos
This is the way I found out fucking around with LACT and CoreCtrl.
If you had used the kernel parameter amdgpu.ppfeaturemask=0xffffffff it means you already have it, this steps are for people who doesn't want to mess with kernel.
-
Install LACT https://github.com/ilya-zlobintsev/LACT
-
Install CoreCtrl
-
Open LACT and do the setup with the command line they provide and restart LACT.
-
Go OC Tab and Enable Overclocking (This will not set overclocking on your GPU, just will open more option for you to do the OC if wanted) after is done, close LACT and REBOOT your system (This reboot its important, do it).
-
Now you can control your GPU through LACT or CoreCtrl
-
You are done, I'll recommend to no touch LACT again, make every change through CoreCtrl. I do recommend to use CoreCtrl for fans curve control, they are less aggressive and in tone with the current temps than LACT and also LACT fans control it's kinda buggy.
ggs.
Introduction
To reduce power usage you will need to "undervolt", reducing the voltage of your GPU or limit the power states of the GPU.
Using a modern (4.17 or greater) kernel and the latest amdgpu driver with a Radeon GPU from 2015 or newer can allow you to overclock (and thus undervolt, reducing power usage (Watts)) you graphics card.
I will link to several resources that I have found on the subject but include snippets of the relevant information in this answer. The first section will assume you already have met the prerequistes and just want to get in and undervolt and move on. The rest of the answer will serve as a collection of AMD GPU tuning resources for those who need it.
As a forewarning, undervolting (or otherwise overclocking) the GPU can introduce stability issues. You will need to test your GPU for stability after changing any of the voltage and clock settings to make sure that it still operates in a "safe" manner (A tool like GpuTest using FurMark is a decent way to test performance and stability. Additionally there is the Phoronix Test Suite to benchmark your computer in Linux). The last thing you want to do in your efforts to reduce power draw is cause crashes, glitches, artifacts, or other degradations of performance.
Quick and Easy Undervolting
Following the Wiki guide on LinuxReviews.org you can change performance levels (and thus power usage) by doing the following:
The first thing you need to do before you can change anything is to set
/sys/class/drm/card0/device/power_dpm_force_performance_leveltomanualto enable manual control. You will getwrite error: Invalid argument errorswhen writing clock values of you don't.echo "manual" > /sys/class/drm/card0/device/power_dpm_force_performance_levelThe available
power_dpm_force_performance_levelsettings other thanmanualare:
autoDrivers chooses automaticallylowForces the lowest possible clock and locks the GPU therehighForcest the highest possible clock and locks the GPU there
profile_standard
profile_min_sclk
profile_min_mclk
profile_peak"When the profiling modes are selected, clock and power gating are disabled and the clocks are set for different profiling cases. This mode is recommended for profiling specific work loads where you do not want clock or power gating for clock fluctuation to interfere with your results.profile_standardsets the clocks to a fixed clock level which varies from asic to asic.profile_min_sclkforces the sclk to the lowest level.profile_min_mclkforces the mclk to the lowest level.profile_peaksets all clocks (mclk, sclk, pcie) to the highest levels."
Just set the value to low, or the profile_min_sclk profile_min_mclk levels to reduce the core clock and memory clocks respectively to reduce power draw.
If you require more fine grain control than the rest of this post should satisfy your needs.
Prerequisites
You will need to make sure you install a kernel that is version 4.17 or greater and the latest supported AMDGPU driver. If necessary you will need to update your Debian install to Debian 10 (Buster) or add the buster-backports repository.
To add backports so you need to edit your /etc/apt/sources.list to include a line like this:
deb http://deb.debian.org/debian buster-backports
and then run apt update to finalize the addition of the backports repository.
Install a new kernel by doing the following:
apt-cache search linux-image #Find the kernel and kernel headers available to you.
apt install linux-image-<flavor> #Use `apt-get -t buster-backports <package>` if necessary
Reboot and then install the xserver-xorg-video-amdgpu libgl1-mesa-dri libglx-mesa0 mesa-vulkan-drivers xserver-xorg-video-all packages.
If you need to enable to Southern Islands or Sea Islands support (GCN 1/GCN 2 AMD GPU), follow this ArchWiki page.
Lastly, it is required to unlock access to adjust clocks and voltages in sysfs by appending the Kernel parameter amdgpu.ppfeaturemask=0xffffffff (Note: this value could be different at the end based on testing and specific changes, this one is simply unlocking the card completely).
Edit the line following line in /etc/default/grub to:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash amdgpu.ppfeaturemask=0xffffffff"
Then run sudo update-grub.
Verify the current featuremask after reboot by checking here:
printf "0x%08x\n" $(cat /sys/module/amdgpu/parameters/ppfeaturemask)
Overclocking/Undervolting
Warning: Double check the entered values, as mistakes might instantly cause fatal hardware damage!
With everything set up, you can adjust clocks and voltages two ways, manually or tool assisted.
Manually
Reddit user Pannuba outlines how to overclock your AMD GPU in this post.
You need to edit the contents of /sys/class/drm/card0/device/pp_od_clk_voltage
Find the location to edit using readlink -f /sys/class/drm/card0/device
We want to edit the P-state #7 for the core and #2 for the VRAM, as those are the values that our GPU is going to run at while under load.
sudo sh -c "echo 's 7 1450 1150' > /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/pp_od_clk_voltage" sudo sh -c "echo 'm 2 2065 950' > /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/pp_od_clk_voltage"
Note that the file path is for their GPU. Use the previous command to discover the path for yours. The values you want for your clock speeds and voltages will also be different. To undervolt, change each P-State voltage for core and VRAM to be less than the default values. You might be able to keep the clock speeds the same but in some cases you will have to also reduce these values. This is where stability testing and benchmarking your GPU comes into play
As outlined in the ArchWiki, you can run the following to apply, verify, force certain P-states, and reset:
To apply, run
echo "c" > /sys/class/drm/card0/device/pp_od_clk_voltageTo check if it worked out, read out clocks and voltage under 3D load:
watch -n 0.5 cat /sys/kernel/debug/dri/0/amdgpu_pm_infoYou can reset to the default values using this:
echo "r" > /sys/class/drm/card0/device/pp_od_clk_voltageIt is also possible to forbid the driver so switch to certain P-states, e.g. to workaround problems with deep powersaving P-states like flickering artifacts or stutter. To force the highest VRAM P-state on a Polaris RX 5xx card, while still allowing the GPU itself to run with lower clocks, run:
echo "manual" > /sys/class/drm/card0/device/power_dpm_force_performance_level echo "2" > /sys/class/drm/card0/device/pp_dpm_mclkAllow only the three highest GPU P-states:
echo "5 6 7" > /sys/class/drm/card0/device/pp_dpm_sclkTo set the allowed maximum power consumption of the GPU to e.g. 50 Watts, run
echo 50000000 > /sys/class/drm/card0/device/hwmon/hwmon0/power1_capUntil Linux kernel 4.20, it will only be possible to decrease the value, not increase.
To enable these changes to carry over across boots you will need to create a script and systemd service. Your script should use the values you have tested to work and the file path to your GPU.
Save this script in /usr/bin/ or a safe place for systemwide scripts:
#!/bin/sh
sudo sh -c "echo 's 7 <Your desired values here>' > /sys/devices/Your/Path/Here/pp_od_clk_voltage"
sudo sh -c "echo 'm 2 <Your desired values here' > /sys/devices/Your/Path/Here/pp_od_clk_voltage"
sudo sh -c "echo 'c' > /sys/devices/Your/Path/Here/pp_od_clk_voltage"
Create a file in /etc/systemd/system/ like undervolt.service with the following contents:
[Unit]
Description=Undervolting GPU
[Service]
Type=oneshot
ExecStart=/Path/To/Script.sh
[Install]
WantedBy=multi-user.target
Run sudo systemctl enable undervolt.service to enable. After rebooting, verify by running cat /sys/devices/Your/Path/Here/pp_od_clk_voltage.
User Pannuba also suggest making a script to revert things to default values. This does not have to be a SystemD service.
Tool Assisted
There exists several tools to assist in AMD GPU overclocking:
AMDGPU Clocks, a commandline tool.
CoreCtrl, GUI tool for total system tuning.
WattmanGTK, a GTK GUI recreating the functionality of Wattman on Linux.
TuxClocker, a Qt5 GUI overclocking tool for Nvidia and AMD GPUs on Linux.
Each one has specific prerequisites and settings that could be posts on their own. Please reference their guides on how to setup and tune your system.
Conclusion
As you can see, AMD GPU Linux tuning is becoming a first class experience. Many of the features available to Windows users is now available to Linux users, even using the open source driver too. There are many tweaks and options you can make. I will leave the specifics to you. If you want to reduce power usage, you reduce the voltages of the P-States and even limit the power of the card. Make sure you test the stability of the card and your computer after changing anything. Read more about Radeon open source driver features here.
Please comment if you have any questions or issues with this answer. I highly suggest you read through each link I have provided thoroughly before attempting the commands. I appreciate feedback to correct any misconceptions and to improve my posts. I can update my answer as needed.
Best of Luck!
Resources
ArchWiki
Reddit user Pannuba's post
Radeon Open Source Features
Linux Reviews
AMDGPU Clocks
CoreCtrl
WattmanGTK
TuxClocker
GPUTest
Phoronix Test Suite
I'm going to complement kemotep's answer, in connection with my observations.
A small preface: English is not my native language. Please ignore semantic, syntactical errors and incorrectly chosen words.
Firstly, to limit the maximum consumption level of the card, you need to change the power1_cap file located along the path /sys/class/drm/card0/device/hwmon/hwmon*/
where an asterisk is a number, usually from 0 to 9. In the same directory, you can adjust the voltage of the card, find out the maximum allowable consumption limit of the card, and much more.
More details can be found at the following link: https://docs.kernel.org/gpu/amdgpu/thermal.html
Secondly, to write values, it is better to use the following type of command:
echo "10000000" | sudo tee /sys/class/drm/card0/device/hwmon/hwmon*/power1_cap
Let me explain why I think so. When executing the following script:
sudo sh -c "{your_commands and/some/random/path*/}"
the asterisk will not be replaced by the missing part of the name, but will be treated as a directory name. The problem is that inside the first hwmon folder, the next nested folder has a random number in its name (example: hwmon0, hwmon3, and so on). So it's important that the asterisk works as a command, not text.
Thirdly, there is probably an error in the method of saving changes described by kemotep.
When running a systemd Unit with the options given in the example, the scripts were not executed. In my opinion, the scripts are triggered before the video adapter in the system is initialized, which is why the specified paths simply do not exist. Or, there is another irresistible force, because of which the scripts refuse to be executed, I'm not an expert.
I will give an example of my unit file, and then I will explain for the parameters:
[Unit]
Description=Limit GPU Wattage
[Service]
Type=idle
ExecStart=/usr/bin/my_script.sh
ExecStartPost=/usr/bin/my_another_script.sh
Restart=on-failure
RestartSec=5
TimeoutSec=300
[Install]
WantedBy=multi-user.target
- The "idle" value of the Type parameter is as stated on the DigitalOcean site - https://www.digitalocean.com/community/tutorials/understanding-systemd-units-and-unit-files
The [Service] Section
The Type= directive can be one of the following:
... idle: This indicates that the service will not be run until all jobs are dispatched.
I understand it as "your Unit will be executed when all elements of the system are loaded". I may be wrong, but it works.
- ExecStartPost - I added when I was looking into the cause of Unit execution errors. I split my script into two files, and here I have indicated the path to the second one. All commands can be placed in one script, but I decided to leave everything as it is.
- Restart - responsible for restarting the script. Just in case I misunderstood the meaning of the "idle" parameter, this option should restart the Unit if it failed. It is possible to specify other restart conditions - read more at the link above.
- RestartSec - this specifies the time to wait before performing a restart.
- TimeoutSec - if I understand correctly, the unit's lifetime is indicated here. I specified 300 seconds. If it does not succeed within this time, the Unit's execution will abort.
Finally, I will describe what I did.
After setting up amdgpu.ppfeaturemask (more info can be found all over the internet), in the /usr/bin/ directory, I created two files:
my_script.sh
#!/bin/sh
sudo sh -c "echo 'low' > /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/power_dpm_force_performance_level"
my_another_script.sh
#!/bin/bash
echo "6000000" | sudo tee /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/hwmon/hwmon*/power1_cap
In the /etc/systemd/system/ directory, I created the my-gpu-setup.service file (the content was shown above).
Then, I started the service (only needs to be activated once) with the command:
sudo systemctl enable my-gpu-setup.service
And restarted the pc.
That's all.
To view information about the execution of a Unit, you can type the command:
sudo systemctl status my-gpu-setup.sevice
To roll back changes and disable the service:
Type the command
sudo systemctl disable my-gpu-setup.serviceDelete file from
/etc/systemd/system/directory (this action is optional).Restart a computer.
I don't see the point in creating a script to roll back the changes, since settings will be reset upon restart anyway, if you don't perform a new setup every time the system starts.