Quote from: pekatete on December 21, 2014, 11:57:12 PM

Quote from: canford on December 21, 2014, 11:37:07 PM

I am using the 1024 firmware, the only change on top of that is adding the new frequencies into cgminer.lua. All six units stable again at the lower frequencies with no voltage setting.

Trying again on one unit, this time with ckolivas's S3 cgminer 4.6.1 build, also deleting --queue and adding --lowmem. I can't think of anything else to try. The S3's are in a ventilated space, so the ambient temperature over the three hour period is constant. Why would I get great results for 1+ hours, but poor results over 3 hours?

Possibly easier to simply post a shot of your web UI, but I'll ask just in case:
1. What temps do you have on that rig?
Right now showing 43 & 42 25 minutes in (and reporting 538 GH/s avg), it don't think it got above 44 the last time I tried it. Ambient temp in the room 18C.

2. What is the HW %
0 (zero). Last try it got a an occasional HW error, but they were minor. One of the six units got a bogged down in HW errors, but then performed well when I dropped the frequency to 268.

3. What freq are you running at?
275/0815 target, last night's test I ran five that way, then the one I dropped to 268/0815.

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

5. Finally, could you also post the freq setting line that you are running from the cgminer.lua file?
pb:value("14:275:0a82", translate("275M"))
[/quote]

Thanks for the help! Answers above in bold.