ethOS 1.3.1 is coming soon, and with it. MANY overclocking changes for the amdgpu driver.
Due to advancements in the driver itself, as well as a new amdgpu data gather / configuration functionality for ethos-smi, our in house created low-level GPU management application overclocking for RX cards is getting a major overhaul.
Heres what you need to know:
First and foremost: old voltage settings MAY NOT WORK. Start at 950mv and work down to find where your cards use the least amount of power and are stable.
Note: All items in code tags (IE:
pwr below) are items meant to be in your remote or local configuration file.
pwrfor setting DPM state on RX gpus. This change was necessary to bring power tune back to what it was originally intended to do, allow the user to adjust the power consumption of the gpu. DPM state was the only option to do this when RX 480 gpus first came to market and the amdgpu driver was immature, this is no longer the case. DPM no longer has a bearing on power draw when
vltis used. It is advised to only use
vltwhen initially tuning gpus for performance and stability.
vlt(Voltage adjustment) now works on all* rx 470/480/570/580 gpus. (I put the asterisk, because I am sure at least one GPU exists that doesn’t will not accept it. )
safevolt(Sanity check) now keeps gpus within normal operating range, but allows advanced operators the ability to unlock advanced tweaking capabilities. (More on that later.)
pwr(Powertune) To reiterate again, is no longer DPM state, and DPM state should no longer affect power draw when
vltis use. Please see below for a detailed description of the new RX
New functionality and examples:
pwr is now a value in watts, it functions similar to NVIDIA
pwr value, as it is a value in watts. It is worth noting that while the theory behind it is the same, it currently does not offer the same kind of easy tuning that pwr on NVIDIA gpus allows. It is more for limiting power in cases where you would otherwise have too much draw on your power supply. It should be used in conjunction WITH
vlt to achieve maximum performance. Hashrate is pretty harshly negatively impacted and thats why, while we felt this new feature was important enough to include, we do not currently advise using it as one of your primary tools to tune RX gpus.
rx 480 example:
pwr 0f66f0 110
This would hard limit gpu0 of rig 0f66f0 to 110 watts.
globalpowertune is also available to set a farm wide limit. Note that this is only advised if all of your GPUs are identical.
This would hard limit all NVIDIA/amdgpu GPUs which do not have a series or per rig pwr line to 110 watts.
series based power tune (Per gpu bios part number) is my personal favorite for tuning a large amount of varying GPUs. as it allows the flexibility to move cards around within the farm without having to re-tune or adjust the config file in any way:
pwr 113-D0090101-100 110
This would hard limit all GPU’s using the bios: 113-D0090101-100 to 110 watts. It is a single value.
Watts for AMD RX GPUs will now show on your ethos panel, as well as in show stats. Note that due to card design, the watts value may vary +-5% from the actual wall draw. We have taken careful consideration and calculations to ensure that this value is as close as possible, but some cards just do not provide accurate information. It is ALWAYS advised to check your actual wall draw if you are running close to 100% capacity of your power supply.
vlt for RX now has a set of safe limits, that can be expanded by using the following in config:
Without the above the GPU core “safe voltage range” is 950 to +150 over stock.
safevolt disabled the range is 650 to +250 over stock . Please be careful!
safevolt disabled also allows setting of vddci for advanced tuners.
vddci 113-67101-100 950
this sets all gpus with “113-67101-100” as bios part number to 950 vddci.
per rig example:
vddci 0f66f0 950 900 1000 980 This sets rig 0f66f0 gpu 0 to 950, gpu 1 to 900, gpu 2 to 1000, gpu 3 to 980.
Vddci is an advanced tuning parameter and is normally not needed to be adjusted, bumping it up +25mv over stock may allow better memory stability.
Note that if you go too high or too low with any specific parameter it is possible you will have to reboot the machine without overclocks (new boot option) or reset the config in order to get the machine to mine again.
Another cool new feature is that some functionality can be applied on the fly for testing.
Example to dial in watts you may run the following while the miner is running and see the results immediately:
Note: all items in code tags from here down are commands for the terminal or ssh prompt.
sudo ethos-smi -g 1 --power 110
This would set the
pwr limit on this GPU to 110 until reboot. once you find a value you are satisified with, you can add it to your configuration file.
To set fans to automatic (bios fan profile) you can do the following:
sudo ethos-smi -g 2 --fan auto
This would put the fan on GPU 2 to auto mode. Please note that most bios profiles are too slow to react to be useful for mining.
You can also adjust the
dpm value on the fly and check results on hash, and to a lesser degree power function
sudo ethos-smi -g 6 --dpm 7
would raise your core clock slightly on GPU 6
You can also view current runtime stats for your GPUs, or a specific GPU using the commands below
See stats for all GPUs:
See stats for a specific GPU (example is GPU 0):
sudo ethos-smi -g 0
31 thoughts on “ethOS 1.3.1 and new amdgpu (RX) GPU Undervolting and power management options”
so dpm would be set like
dpm worker 3 3 3 3 3 3 like the old powertune setting.
and if earlier I had a globalpowertune 7, how now it is necessary to write? O_O
it would now be
And what does this parameter mean? I just can not fully understand (
thanks for the detailed description of new features. You mentioned new feature “reboot the machine without overclocks (new boot option)”. What is the code for it? I did not find it in KB or description below or sample config. Thanks a lot.
its a boot menu option, so it is not in the config. You select it from the machine physically. Its mainly for crash cart usage, or people that keep rig plugged up to keyboard / monitor
When you wrote this:
“You can also adjust the rpm value on the fly and check results on hash, and to a lesser degree power function
sudo ethos-smi -g 6 –dpm 7”
I asume that you intended to say that you can adjust the dpm (not the rpm) on the fly.
Corrected in the post. Safari autocorrected it for me…. grr 🙂
What I am seeing is that vlt from local.conf also sets the memory voltage to the same value. Any ideeas?
Thats correct Smoker, the memory voltage is tied to the core voltage within the smu itself. So that is why it is important to pick sane values, because lowering memory voltage too much will cause crashes.
On my rig it has slightly increased CPU load. It is around 13 all the time. Is this known or it is just my rig?
please use the ethOS support channel from here: http://ethosdistro.com/kb/#support
is there any problem if i use both vlt and dpm
dpm d04bbd 2 2 2 2 2 2 2 2
vlt d04bbd 880 880 880 880 880 880 880 880
mining2018, They both synergies together and it depends on your card, dpm is not a required parameter, try the automatic setting first ( don’t have a dpm set)
if i want to put down the power tune i have to remplace pwr for dpm i have rx580 is that correct
Gian, use vlt to bring power down, but yes, your old pwr value is now the dam value
Is there a ‘globalDPM’ parameter available ?
so i set my config like this:
dpm 3 3 3 3 3 3 3
vlt 1050 1050 1050 1050 1050 1050
flags –cl-global-work 8192 –farm-recheck 200
I have 6x RX580 8 GB
with this settings 188,7Mh/s by 1040WATT on the wall.
Can someone give me some advices how i can get the WATT down?
If i put globalpowertune to 110 or 115 one card work only with 28 Mh/s, with 120 every have 31,45Mh/s.
Thank you in advance.
Andreas, please use the ethOS support channel: http://ethosdistro.com/kb/#support
could you add phonex miner? in some rx it is more stable, and what about xmr cpu? it is really interesting for big farms when you could use cpu
does the ptune have to be set in the local.config file , or can it be done at the command prompt ?
this comman has not worked for me in tuning down gpu:
sudo ethos-smi -g 6 –dpm 5
After updating to 1.3.1 and in local.conf, “vlt” only changes “Memory Voltage” and does not have any effects on “Core Voltage”. So, total consumption is higher than 1.3.0 and I don’t know how I can change the core voltage. Any suggestion?
Eli, please use the ethos support channel from the kb: http://ethosdistro.com/kb/#support
Please, what is the concept or relevance of “sysload”, whats parameters affect it and wich is the operation normal range.
Love the changes. Going to have some fun testing this out.
I’ve had one GPU that’s not happy for months now and this gives me the tools to test on the fly.
this is the best documentation I’ve seen so far for understandable configuration and what each setting does. On my EthOS rig I get 30 – 31 mh/s and run from 105 up to 148 watts depending on the card: about 1750 w rig total for 10 cards rx 570’s and 580’s with timing adjusted bios. My local.conf settings are:
cor rigid 1150 1150 1150 1150 1150 1150 1150 1150 1150 1150 1150 1150
mem rigid 2150 2150 2150 2150 2150 2150 2150 2150 2150 2150 2150 2150
pwr rigid 150 155 150 150 150 150 150 150 150 150 150 150
vlt rigid 0.900 0.900 0.900 0.900 0.900 0.900 0.900 0.900 0.900 0.900 0.900 0.900
Any idea on when will the update for removing the bios mem limit is coming?
My GPUs are currently limited by the mem limit in bios in 1.3.1 and there’s too many 20+ different roms that i lost count so changing the mem limit in bios is a huge task but panel verification requires 1.3.1 per panel.
can some specify
vddci [rigname] 0950
mvddci [rigname] 980
does vlt affect the core volatage for RX 580 cards or both the memory and core?
I hace this config in my rig and is crashing, the hashing goes down when the cpu usage goes up:
This rig have 11 gpu and start whit 28-30 hash per card and after 8 minuts goes to 14-16 hash