Hi Phil,
I tried some very minor overclocking. Looks like there's only a smidge of leeway on my machine as it stands right now. Specifically, I went to 570 clock and everything was fine, but when going to 580 (also tried 600), I get the following errors, non-stop:
Note that since the last update-push from HF, bringing us back to cgminer 3.9.0h2, my system was very stable at stock clock. Hashing steadily just under 400GH/s at Eligius, with little variance. Never more than 3-4 degrees variance between the cores, miner only rebooted once in several days, etc...
So I figured I'd have more overclocking leeway than 570. Any suggestions?
Thanks.
I tried some very minor overclocking. Looks like there's only a smidge of leeway on my machine as it stands right now. Specifically, I went to 570 clock and everything was fine, but when going to 580 (also tried 600), I get the following errors, non-stop:
Note that since the last update-push from HF, bringing us back to cgminer 3.9.0h2, my system was very stable at stock clock. Hashing steadily just under 400GH/s at Eligius, with little variance. Never more than 3-4 degrees variance between the cores, miner only rebooted once in several days, etc...
So I figured I'd have more overclocking leeway than 570. Any suggestions?
Thanks.
Well, this is still happening when I overclock *at all*. 555 does it too. I even tried compiling the hash-fast cgminer build on an Ubuntu laptop to rule out *anything* having to do with the RPi; mined fine at the default 550, but gave the same above errors any higher.
Suggestions?
^^ Just in case this got lost a couple pages back ^^
??
CG v 3.11.0 makes it much easier to overclock, and has been very stable. As mentioned before you can see the "real" hashrate via the API. Also, you can easily change the clock rate via command line.
Your config file will look like this. Notice you can change clock and temp below the pool settings. Then when you run the full stats via the API it will show you actual [hash clockrate] => xxx
If you put in certain speeds then check the API it may not be the same. For what it's worth, 656 seems ideal for running a single unit on a controller whereas a controller that has 3 attached runs best at 604. With these settings the config and API show the same clockrate.
{
"pools" : [
{
"url" : "xxxx",
"user" : "xxxx",
"pass" : "123"
},
{
"url" : "xxxxx",
"user" : "xxxxx",
"pass" : "123"
}
],
"hfa-hash-clock":"656",
"hfa-temp-overheat" : "89",
"api-allow": "127.0.0.1,192.168.xxx.xx"
}
Agreed, I have 2 working stable OC rates for me, 580 and 611 seem to be workign well. I have been trying 1/2 increments and seeing how it goes.
As far as watchdog goes, Does watchdog happen due to overheating or to fast of a clock? Just trying to figure out howone could surpress watch dog. I didnt start getting watch dog errors till 615 and it happens about 10mins to 1hour.
