Command-line ATI Overdrive Utility (with memory adjustments)?

[fpgaminer]

Is there a command-line driven ATI OverDrive Utility that allows properly adjusting the memory clock? aticonfig won't let me set the memory clock lower than the default 1000. So far I have used AMDOverdriveCtrl to set everything up, and it's great, but it requires a GUI. I want to be able to SSH into the rigs and set everything up, or even script stuff.

EDIT: Oh, looks like AMDOverdriveCtrl lets you run a "batch-mode" and specify a profile. That's pretty decent for scripting. Not ideal, but a good work around.

[shivansps]

ist easier to just flash the cards with the OC/mem underclock clocks???

[trentzb]

I've been hacking on glakkeclock a bit. I can manually set mem clocks outside BIOS limits but still have adapter index issues and core clock settings still need work. I just noted he submitted some changes over last few days which may fix some of these issues that I have been working on in my tree. Jump in and help out if you can. It uses the ADL SDK.

https://github.com/Glakke/glakkeclock

[grndzero]

I manually set FAN_SETTING percentage and FAN_CTRL enabled to no then removed everything else below that.

Code:

<OVERDRIVE_PROFILE>
  <PERFORMANCE_LEVEL level="2" gpu="90000" mem="30000" voltage="1088"/>
  <PERFORMANCE_LEVEL level="1" gpu="55000" mem="30000" voltage="1038"/>
  <PERFORMANCE_LEVEL level="0" gpu="15700" mem="30000" voltage="1000"/>
  <FAN_SETTING percentage="75"/>
  <FAN_CTRL enabled="no"/>
</OVERDRIVE_PROFILE>

then made a shell script to run overdrive on each card

Code:

 
export DISPLAY=:0.0
aticonfig --od-enable
AMDOverdriveCtrl -b -i 0 AMDOverDrive
AMDOverdriveCtrl -b -i 3 AMDOverDrive
AMDOverdriveCtrl -b -i 6 AMDOverDrive

works from an ssh session just fine as long as X, fglrx, and opencl are working properly

and once it's enabled aticonfig --odgc --adapter=all should show the memory going all the way down to the lowest point and be changeable with --odsc

[jondecker76]

So if I set the core and memory clocks using amdoverdrivectrl, the settings don't persist?

[grndzero]

So if I set the core and memory clocks using amdoverdrivectrl, the settings don't persist?

--odcc is supposed to commit clock speeds, I have never used it. I don't think it will work while using amdoverdrivectrl to lower the mem clock below the standard bios limit though. That's why I have it in a shell script.

[Prze_koles]

I manually set FAN_SETTING percentage and FAN_CTRL enabled to no then removed everything else below that.

Code:

<OVERDRIVE_PROFILE>
  <PERFORMANCE_LEVEL level="2" gpu="90000" mem="30000" voltage="1088"/>
  <PERFORMANCE_LEVEL level="1" gpu="55000" mem="30000" voltage="1038"/>
  <PERFORMANCE_LEVEL level="0" gpu="15700" mem="30000" voltage="1000"/>
  <FAN_SETTING percentage="75"/>
  <FAN_CTRL enabled="no"/>
</OVERDRIVE_PROFILE>

Wait, where did you set this?