Print Page - ATI underclocking memory under linux?

Quote from: smgoller on March 09, 2011, 10:17:41 PM

aticonfig won't let me drop my 5870s below 1200Mhz. Anything I can do to address this?

What happens when you try? (i.e. what error message etc do you get, if any?)

I can go as low as 900:

Code:

user@host:~/bin/DiabloMiner$ aticonfig --odgc

Default Adapter - ATI Radeon HD 5800 Series
                            Core (MHz)    Memory (MHz)
           Current Clocks :    900           900
             Current Peak :    900           900
  Configurable Peak Range : [600-900]     [900-1300]
                 GPU load :    99%

Here you go:

Code:

aticonfig --odsc=0,900 --adapter=1

ERROR - Set clocks failed for Adapter 1 - ATI Radeon HD 5800 Series
        Please check that input values were valid

Code:


aticonfig --odgc --adapter=all

Adapter 0 - ATI Radeon HD 5800 Series
                            Core (MHz)    Memory (MHz)
           Current Clocks :    900           1200
             Current Peak :    900           1200
  Configurable Peak Range : [600-900]     [1200-1300]
                 GPU load :    99%

Adapter 1 - ATI Radeon HD 5800 Series
                            Core (MHz)    Memory (MHz)
           Current Clocks :    900           1200
             Current Peak :    900           1200
  Configurable Peak Range : [600-900]     [1200-1300]
                 GPU load :    99%

MSI Afterburner in windows will allow you to go lower, afaik. has anyone written anything does something similar?

Quote from: smgoller on March 10, 2011, 12:38:47 AM

Here you go:

Code:

aticonfig --odsc=0,900 --adapter=1

ERROR - Set clocks failed for Adapter 1 - ATI Radeon HD 5800 Series
        Please check that input values were valid

Code:


aticonfig --odgc --adapter=all

Adapter 0 - ATI Radeon HD 5800 Series
                            Core (MHz)    Memory (MHz)
           Current Clocks :    900           1200
             Current Peak :    900           1200
  Configurable Peak Range : [600-900]     [1200-1300]
                 GPU load :    99%

Adapter 1 - ATI Radeon HD 5800 Series
                            Core (MHz)    Memory (MHz)
           Current Clocks :    900           1200
             Current Peak :    900           1200
  Configurable Peak Range : [600-900]     [1200-1300]
                 GPU load :    99%

MSI Afterburner in windows will allow you to go lower, afaik. has anyone written anything does something similar?

Strange - maybe different manufacturers set different ranges? I'm out of options, though - given the MSI Afterburner stuff - I'd assume that it *must* be possible to go outside the configurable peak range on Linux, too. (There's a thread somewhere here - you've likely seen it - where Windows users with MSI Afterburner are finding a "sweet spot" around 300MHz; it'd be good to have that available on Linux...)

you can adjust the memclock with AMD Overdrive Ctrl https://sourceforge.net/projects/amdovdrvctrl/ (https://sourceforge.net/projects/amdovdrvctrl/)

and please write on the board https://sourceforge.net/projects/amdovdrvctrl/forums/forum/1335752/topic/4026230 (https://sourceforge.net/projects/amdovdrvctrl/forums/forum/1335752/topic/4026230) for the support of multiplte GPU's, maybe in the next version ;)

if the developer sees that alot people actually need that kind of feature, i think it would be coded fast ;)

Quote from: SicKk on May 30, 2011, 11:51:35 AM

you can adjust the memclock with AMD Overdrive Ctrl https://sourceforge.net/projects/amdovdrvctrl/ (https://sourceforge.net/projects/amdovdrvctrl/)

+1. This is definitely the program you want.

Quote from: SicKk on May 30, 2011, 11:51:35 AM

and please write on the board https://sourceforge.net/projects/amdovdrvctrl/forums/forum/1335752/topic/4026230 (https://sourceforge.net/projects/amdovdrvctrl/forums/forum/1335752/topic/4026230) for the support of multiplte GPU's, maybe in the next version ;)

if the developer sees that alot people actually need that kind of feature, i think it would be coded fast ;)

I think this was already implemented. -i flag sets the GPU to be used, and you can get the ID of all GPUs with -h or something. I've used it successfully with 2X5970.

https://forum.bitcoin.org/index.php?topic=4806.0

The answer is in this thread, post # 8.

After using AMD Overdrive Ctrl the cores are more prone to freezing when going hard out mining ... I've found, I stopped using it and freezing up went away. Do this ...

Code:

$aticonfig --od-enable

Run "ATI Overclocking Utility" once from the CLI to set your range of peak speeds (move mem. slider to 300)

Code:

./atioc_x86_64

Exit from atioc, you'll probably see fan errors if using multiple cards, give it ^C in the terminal to really kill it.

Use the CLI

Code:

$aticonfig --adapter=all --od-setclocks=790,300
$aticonfig --adapter=all --odcc

to set the clock speeds and you should have stable performance over days if not weeks.

Even though after running AMDOverdriveCtl, the output of 'aticonfig --odgc --adapters=all' suggests 300 is in the acceptable memory range, --odsc won't set it. It will report that it's set.. but below a certain percent of current CPU clock, the setting is ignored and memory clock snaps back to the card default.

I can get to 910cpu 785ram on a 6950/6970.. but attempting even 1 cycle less on the RAM causes a snap back up to 1250.

Looked for the 'atioc_x86_64' mentioned by noone.. and found the tool mentioned here..

http://phoronix.com/forums/showthread.php?17331-ATI-Overclocking-Utility

Getting over my normal suspicion of random executables because this is a single purpose mining machine, I tried the most recent downloads from..

http://ompldr.org/iMXI3cQ or

http://kde-apps.org/content/show.php/ATI+Overclocking+Utility+X64?content=107457

Both give segmentation fault.

Is there a trick to making this work or another way to achieve 300mhz memory clocks on linux?

Quote from: noone on May 30, 2011, 12:15:45 PM

Code:

$aticonfig --od-enable

Run "ATI Overclocking Utility" once from the CLI to set your range of peak speeds (move mem. slider to 300)

Code:

./atioc_x86_64

Exit from atioc, you'll probably see fan errors if using multiple cards, give it ^C in the terminal to really kill it.

Use the CLI

Code:

$aticonfig --adapter=all --od-setclocks=790,300
$aticonfig --adapter=all --odcc

to set the clock speeds and you should have stable performance over days if not weeks.

This does not make sense. AMDOverdriveCtrl uses the ATI official API. Why does AMDOverdriveCtr gives, according to you, more inestability?

AMDOverDriveCtrl *causing* freezing sounds like a red herring to me....

It's more likely you were setting invalid clocks or otherwise making your card unhappy.

Run AMDOverDriveCtrl and leave it running. Do not exit it.

You should see a lower floor when you try aticonfig --odgc and aticonfig will let you set a lower clock. That's my experience.

Quote from: supa on June 13, 2011, 07:02:09 AM

AMDOverDriveCtrl *causing* freezing sounds like a red herring to me....

It's more likely you were setting invalid clocks or otherwise making your card unhappy.

Yes. I was checking now and the utility he recomended uses AMD ADL API, which I believe is the same AMDOverdriveCtrl uses. So basically both programs are frontends to the same AMD API. There should be no difference.

Quote

Run AMDOverDriveCtrl and leave it running. Do not exit it.

You should see a lower floor when you try aticonfig --odgc and aticonfig will let you set a lower clock. That's my experience.

AMDOverdriveCtrl lets you save the profile once you have a configuration you like and then you can load it with the -b option, for example:

AMDOverdriveCtrl -i 1 -b profilefordevice1.ovdr

This will set up the device 1 with the configuration on the file profilefordevice1.ovdr (that you should have created with the GUI previously) and exits, allowing you to start the miners. No need to have the GUI running. I actually have a script that sets the cards using taht comand and then launches the miners.

Even leaving AMDOverdriveCtrl running, same result.. the displayed ranges of --odgc make it look like lower clocks are possible, but below some threshold which varies based on CPU clock any change (from --odsc or GUI) doesn't take effect and in fact causes the memory to snap back to the default for the current load level. Arrrgh!!!

Quote from: HanSolo on June 13, 2011, 08:51:23 AM

I'm having the same problem.

I've got 6950s and 6970s.

RBE warns on certain changes that the native drivers may stop recognizing the card.. and someone else mentioned after a certain RBE edit even aticonfig wouldn't find the cards.

Are you using a signed 'rbe' excerpt from another card (~1kb) to get around that?

Quote from: HanSolo on June 14, 2011, 04:54:49 AM

Just as a remainder, always back up the original bios before trying to flash your card with a new one. At least you will be able to get your card to the oringinal condition.

Quote from: HanSolo on June 14, 2011, 04:54:49 AM

As already mentioned, make sure you make a backup of your existing BIOS. atiflash has a built-in command (-s X filename).

I don't bother with the RBE signatures, etc - I just change my clocks under Additional Settings with relatively good luck so far.

The only "issue" (really not an issue) is that on reboot after flash, Windows did infact not recognize the card.... and I had to go through letting it re-detect and put the drivers back in place. Occasionally, it would do that every 3 or 4th reboot. I stopped using Windows whenever possible.... ;)

PS - for the record, ^ the above only happened on one Windows PC and a buddy with an identical card doesn't have that problem.

Quote from: vx609e on June 13, 2011, 10:48:01 PM

Quote from: HanSolo on June 13, 2011, 08:51:23 AM

I'm having the same problem.

i have the same problem too on my 6990s

Adapter 0 - AMD Radeon HD 6990
Core (MHz) Memory (MHz)
Current Clocks : 950 1250
Current Peak : 950 150
Configurable Peak Range : [500-1200] [75-1500]
GPU load : 99%

Quote from: LMGTFY on March 10, 2011, 12:45:01 PM

I have two Asus 5870 and the memory can go as low as 200Mhz with AMDOverdriveCtrl. The sweet spot for me is 335Mhz. But I just got a XFX 8750 and while I can get the memory to 335Mhz, it wont allow to push the core speed more than 900Mhz. It depends on the vendor.

Quote from: hugolp on June 16, 2011, 05:35:28 AM

I got an Asus 5870 and an Alienware 5870 in the same LinuxCoin box.
AMDoverdriveCTRL allows me to:
Asus: 300-1200GPU 200-1200MEM
Alien: 300-900GPU 200-1200MEM

So the Asus runs great @ 1000//335
The Alien runs slower @ 900//310

Would love to set the GPU of the Alien higher but cant, so my conclusion is that it really depends on the manufacturer what the rangers are on the card, and of course you should be able to alter them but for me it's been hard fining how to alter the Alien.

Quote from: Folax on June 16, 2011, 12:23:01 PM

Quote from: hugolp on June 16, 2011, 05:35:28 AM

I just solved it this morning. I used SBE and winbios (or something like that) to get the bios from the Asus, copy the limitations, then mix the limitations of the ASUS with the bios of the XFX and reflashing the XFX. Works like a charm.

Quote from: Folax on June 16, 2011, 02:31:48 PM

Is there a guide somewhere on how to do this and where to get the installation packages?
When I do a forum search on SBE I get a lot of (German) BTC betting stuff but nothing on this tool, also 'Winbios' does not return much unfortunately (only this post).

It was RBE: http://www.techpowerup.com/rbe/ Just follow the official tutorial, its all explained.

Quote from: HanSolo on June 14, 2011, 04:54:49 AM

I cannot for certain say for those, but I am running 6870's, with RBE modified bioses. The newest version, 1.28, supported overvolting them, which is pretty useful. The doom and gloom forum posts about the cards not being recognized in windows and BSOD's seem to be limited to the windows world. I used "method 2" , aka the no checksum, direct write, screw it lets see if it works method, to increase my overdrive limits to 1200 MHZ on a couple of cards so far, and linux has been happily mining away now for days on them as I test for stable clocks.

Note, I changed the GPU register, modified the fan curve, and used method 2 to increase the max overdrive, but I didn't mss with any powerplay states, so I don't know if that will work or not.

Underclocking memory would likely mean modifying the powerplay states, and I have been too lazy to do that thus far.

There was a post I made about this on the techpowerup forums, but it is gone to the nether since apparently putting a hosting company in your .sig is a bannable offence. Not that I am bitter.

Bitcoin Forum

Other => CPU/GPU Bitcoin mining hardware => Topic started by: smgoller on March 09, 2011, 10:17:41 PM