[CLOSED] Need bash script for OC tweaking

[gusti]

I need a bash script for automatically tweaking OC in my debian mining rigs.
In brief, the script must increase GPU clock in regular intervals, using stock aticonfig, until last OC setting fails.
When miner fails, it must reboot the rig, and come back to the last highest no-failed setting.
Script must be fully commented for further develop, and it will have a GPL license.

Max bounty : 10 btc or best offer.

[1713567742]

1713567742

[1713567742]

1713567742

[1713567742]

1713567742

[1713567742]

1713567742

[1713567742]

1713567742

[gusti]

any programmer interested ?

[kirax]

I need a bash script for automatically tweaking OC in my debian mining rigs.
In brief, the script must increase GPU clock in regular intervals, using stock aticonfig, until last OC setting fails.
When miner fails, it must reboot the rig, and come back to the last highest no-failed setting.
Script must be fully commented for further develop, and it will have a GPL license.

Max bounty : 10 btc or best offer.

The tricky part about this is that a locked card will sometimes bomb a machine so good that it cannot soft reboot. Would it be reasonable to assume that the machine is running with watchdog, which (usually) manages to reboot it, even if phoenix is currently holding most of the CPU cycles hostage?

I could look at it after the weekend.

[gusti]

I need a bash script for automatically tweaking OC in my debian mining rigs.
In brief, the script must increase GPU clock in regular intervals, using stock aticonfig, until last OC setting fails.
When miner fails, it must reboot the rig, and come back to the last highest no-failed setting.
Script must be fully commented for further develop, and it will have a GPL license.

Max bounty : 10 btc or best offer.

The tricky part about this is that a locked card will sometimes bomb a machine so good that it cannot soft reboot. Would it be reasonable to assume that the machine is running with watchdog, which (usually) manages to reboot it, even if phoenix is currently holding most of the CPU cycles hostage?

I could look at it after the weekend.

I already tested that, and they can be rebooted. Anyway, if this is not possible, I can also cold reboot them.
The important thing is to store (txt file is ok) last no-failed OC setting.

[gusti]

Still looking for a programmer to do this job.

[gusti]

just testing a forum member script.

[Chemicalbro]

More than one gpu per rig I assume too?

[gusti]

More than one gpu per rig I assume too?

Yes, but other member already sent me a workable script, so bounty is closed.
Thanks !

[flower1024]

would you share it?

[gusti]

would you share it?

No problem for me, but let me ask the original programmer of the script first.

[ovidiusoft]

No problem for me either. If it's ok with you, gusti, I'll add a suggestion to donate to my address and upload the script to my Dropbox public folder. Since you were the one requesting this script, I think it's only fair to let you decide.

[gusti]

No problem for me either. If it's ok with you, gusti, I'll add a suggestion to donate to my address and upload the script to my Dropbox public folder. Since you were the one requesting this script, I think it's only fair to let you decide.

Sure, please go ahead with that !

[ovidiusoft]

Thank you! Also, I want to publicly acknowledge that I received the 10 BTC bounty from gusti.

The script can be downloaded from http://dl.dropbox.com/u/16757143/overclock-test.sh , shortlink http://db.tt/S73vRHk . It's written in bash and uses bc, awk,
pkill, so you need to have these installed.

The script starts Phoenix and keeps changing ram/gpu frequencies in set intervals. It also monitors temperature to prevent overheating and determines average hashrates for each ram/gpu frequency pairs. It writes the results in a file called 'results.csv.TIMESTAMP' in the current directory:

Code:

GPU,RAM,Mhs
1030,320,332.04
1030,325,330.40
1030,330,332.25
1035,320,332.94
1035,325,333.64
1035,330,333.84

If the machine locks, the last line written to the file will be the last passed test. Please edit the script to change your settings and start slow (with values that you know work without hanging your system). I only tested it with Phoenix 1.50 on Debian and Ubuntu, but changes required for other versions/miners should be minimal.

I hope it's useful! If there's interest, I can start a new thread for it and develop it some more (easier to configure and working with other miners, for example).

[Bert]

Line 82 of the script has a tiny mistake.
It is:
TIME=`+%s`
And it should be
TIME=`date '+%s'`

Looks like a great script - sent a donation.

[ovidiusoft]

You're right, sorry for that, vim seems to hate me lately. I fixed it, everyone please re-download.