Post
Topic
Board Mining support
Re: Antminer S3 batch 6 overclocking
by
canford
on 22/12/2014, 01:01:22 UTC
4. If you've recently started the rig, could you post the cgminer startup string (usually logged in system log ...?)?
From the process tab:
cgminer --bitmain-options 115200:32:8:14:275:0a82 -o stratum+tcp://us1.ghash.io:3333 -O USER.WORKER:Any -o stratum+tcp://stratum.mining.eligius.st:3334 -O ADDR_WORKER:Any -o stratum+tcp://mint.bitminter.com:3333 -O USER_WORKER:PASS --bitmain-nobeeper --api-listen --api-network --bitmain-checkn2diff --bitmain-hwerror --version-file /usr/bin/compile_time --lowmem


I remember reading somewhere that it is not a good idea to run without a queue, rather have a reduced one to the 2048 one that ships. I run mine with  --queue 1024, so you could possibly try  --queue 512 if you are averse to having a long one. (I am not conversant with the why's of this, so please don't ask!)

Here's where that came from, ckolivas's recommendation when he released the S3 binary I am currently using on the OC unit:
Here's an updated S3 binary.

http://ck.kolivas.org/apps/cgminer/antminer/s3/4.6.1-141020/cgminer

Recommended if you're mining on p2pool for the default binary actually discards stale shares which you should never do, especially on p2pool. Also includes changes to queuing and memory usage that were necessary on S4 but probably only of minor benefit here. Recommend you edit the cgminer startup script to remove the --queue value entirely, and add --lowmem. Performance should be pretty much unchanged.

Death spiral on the OC unit definitive now, average down to 523 GH/s.  All chips good with "o", still just the 3 HW errors, temps 42/38.  This would bother me less if I had some explanation for what is happening.