Pages:
Author

Topic: Antminer S3 batch 6 overclocking (Read 23045 times)

brand new
Activity: 0
Merit: 0
August 03, 2015, 07:08:12 AM


You are good to go .... even 262.5M @0750 volt (if cables are bigger than 16AWG populate all 4 PCI-E ports)

http://ixmsk.eu/bcoin/cutimage2.JPG

Later sign up


5H running time: 470ghs AVG (all time)

http://ixmsk.eu/bcoin/cutimage-5h.JPG

Edited:

If you would like to reduce the frequency from 150-175 volts how much should I give him?
newbie
Activity: 1
Merit: 0
January 21, 2018, 06:05:53 AM
@pakatete i'm trying to change via putty

vim /etc/config/asic-freq

config 'asic-freq' 'default'

        option 'freq_value'    '0a82'  #275M
        option 'chip_freq'     '275'
        option 'timeout'       '14'

        #option 'ereq_value'    '1286'  #237.5M
        #option 'chip_freq'     '237.5'
        #option 'timeout'       '17'

        #option 'freq_value'    '0882'  #225M
        #option 'chip_freq'     '225'
        #option 'timeout'       '18'

        #option 'freq_value'    '1106'  #218.75M
        #option 'chip_freq'     '218.75'
        #option 'timeout'       '18'

        #option 'freq_value'    '1086'  #212.5M
        #option 'chip_freq'     '212.5'
        #option 'timeout'       '18'

250M to 275,,,but in miner configuration menu still 250...how to change it....
many thanks...
hero member
Activity: 518
Merit: 500
August 03, 2015, 06:45:46 AM
Hey

http://ixmsk.eu/bcoin/cutimage.JPG

231.25M
0750 volt

how much should be reduced?
That's a lot HW?

HW is OK .... go to
250M
0750 volt

if you have a good PSU.

Hp DPS-800GB A 1000W 230v

You are good to go .... even 262.5M @0750 volt (if cables are bigger than 16AWG populate all 4 PCI-E ports)
hero member
Activity: 518
Merit: 500
August 03, 2015, 06:39:55 AM
Hey

http://ixmsk.eu/bcoin/cutimage.JPG

231.25M
0750 volt

how much should be reduced?
That's a lot HW?

HW is OK .... go to
250M
0750 volt

if you have a good PSU.
hero member
Activity: 518
Merit: 500
July 05, 2015, 11:01:17 AM
All still OC'd - I have a few on freq 262 @ 0750 and another lot on freq 281.25 @ 0755 (those seem to be the sweet spots for my rigs).
What is the freq_value setting you're using for 281.25? Also, how did you find these values in the first place? This thread is the only place I managed to find the freq_values for these frequencies over 250.

Someone probably clever (or clever at copying) put them out somewhere, and I put a link to them in the OP somewhere.
Freq 281.25 has a timeout of 14 and  freq_value of 1606 (you can play with the voltage to suit your rig ....)
hero member
Activity: 924
Merit: 1000
April 20, 2015, 11:23:06 PM
Solid eh?

We have some S2's still running on Freicoin network. Amazing they just keep going. We had to exchange out the flamed out PSUs we had with them originally though. They didn't last a month. We swapped out and didn't even bother RMA/Replacing via Bitmain just no point.
hero member
Activity: 518
Merit: 500
April 20, 2015, 07:34:39 AM
Still running your S3's Pek?
Yep, still running them ...

OC'ing them?
Or underclocking now?

All still OC'd - I have a few on freq 262 @ 0750 and another lot on freq 281.25 @ 0755 (those seem to be the sweet spots for my rigs).
hero member
Activity: 924
Merit: 1000
April 20, 2015, 07:16:51 AM
Still running your S3's Pek?
Yep, still running them ...

OC'ing them?
Or underclocking now?
hero member
Activity: 518
Merit: 500
April 18, 2015, 09:00:38 AM
Still running your S3's Pek?
Yep, still running them ...
hero member
Activity: 924
Merit: 1000
April 18, 2015, 08:57:31 AM
Still running your S3's Pek?
sr. member
Activity: 805
Merit: 250
March 16, 2015, 02:54:18 PM
Even though this thread is a bit old, i just wanted to stop by and tell you that YOU my friend are a GOD.

i followed your instructions and my s3+ is doing 553gh stable, with very little HW like 0.0002% for 48hours.
tonight i will doing my other 5 units

Happy Hashing to everyone
member
Activity: 89
Merit: 10
January 01, 2015, 02:07:28 AM
All three OC experiments failed.  Both of the other units I tried 250/0750 with looked fantastic for the first hour, then slid into slow decline without any symptoms other than declining hashrate.  They bottomed out at about 430 after 12 hours.  Reverting to stock and taking a break!

I am not by any means disputing your results as that would be futile, however if I may point out my experience with S3's, it is very rare that you find any two units hashing the same, even when using similar freq & voltage settings, PSU and connected to the same pool.

In your case however, that you have experienced the same wall of performance after the first hour, and that happening on most of your units, leads me to believe the issue must be local to your setup.

My first instinct was a heat / temperature problem, however, you seem to discount this as a possibility, and that the units run as normal on stock frequencies seems to justify that. I am not completely sold though since I have never run an S3 variant at temps as high as yours. Before the season change and my moving my rigs outside, I had them all running the fans at full pelt, aka blue wire hack, which kept the temps low, and now that the seasons have changed and my rigs reside in the garden, my temps are a lot lower.

My second guess is how you are powering your rigs. Though you appear to have the right PSU's, this may be a cause if you have them all plugged into the same extension lead. They may not trip your circuit, but they will compete for power, especially if you are running them off a 110v circuit.

If you choose to attempt the OC again, I wish you luck, but I think in your instance I have given as much help as I possibly can, bearing in mind I am neither an engineer nor an electrician.

Thanks for trying to help!  I am both an engineer and an electrician.  I do not think I have power issues, as all 6 units are running from Corsair 750 or 800W supplies, with all four PCI-E connectors well seated.  Three power supplies are on one 20A 120V circuit, and three are on another.  So there is plenty of spare power.

I think what is happening is a slow overheating.  Interestingly, the S3s do not appear to respond by increasing the fan speeds, instead the hash rate goes down as we have discussed.  All six units are in a well ventilated space that stays around 18C.  The S3s report temps around 39-42C, so not very high.

If I find the time, I may try redoing the paste and/or maxing the fan speeds to see if that helps.  I will also keep an eye out for any S3 firmware updates that fix something.  For now, I have concluded that my six units are not overclockable other than the slight bump I get from setting the frequencies to 225/231/243/237/225/237 for the six.

Very frustrating to see such promising hashrate increases in the first hour, but then nothing sustainable.  But overall I am impressed with the units, they are all working to spec and running just fine.
hero member
Activity: 518
Merit: 500
December 22, 2014, 10:57:04 PM
All three OC experiments failed.  Both of the other units I tried 250/0750 with looked fantastic for the first hour, then slid into slow decline without any symptoms other than declining hashrate.  They bottomed out at about 430 after 12 hours.  Reverting to stock and taking a break!

I am not by any means disputing your results as that would be futile, however if I may point out my experience with S3's, it is very rare that you find any two units hashing the same, even when using similar freq & voltage settings, PSU and connected to the same pool.

In your case however, that you have experienced the same wall of performance after the first hour, and that happening on most of your units, leads me to believe the issue must be local to your setup.

My first instinct was a heat / temperature problem, however, you seem to discount this as a possibility, and that the units run as normal on stock frequencies seems to justify that. I am not completely sold though since I have never run an S3 variant at temps as high as yours. Before the season change and my moving my rigs outside, I had them all running the fans at full pelt, aka blue wire hack, which kept the temps low, and now that the seasons have changed and my rigs reside in the garden, my temps are a lot lower.

My second guess is how you are powering your rigs. Though you appear to have the right PSU's, this may be a cause if you have them all plugged into the same extension lead. They may not trip your circuit, but they will compete for power, especially if you are running them off a 110v circuit.

If you choose to attempt the OC again, I wish you luck, but I think in your instance I have given as much help as I possibly can, bearing in mind I am neither an engineer nor an electrician.
member
Activity: 89
Merit: 10
December 22, 2014, 04:16:22 PM
It took longer, but 250/0750 also a dead end.  Over 500 first hour, then down.  After 3h down to 485 average, 458 last hour on the pool.  All "o" on the chips and only 1 HW.  Dropping to 243/0750 for the next run.


243/0750 also a dead end, dropped to 4h running average of 471, with last hour on the pool at 449.  Trying 237/0750.

I also started playing with the slowest of the others (225 for 453, no voltage change).  Trying 250/0750, and so far 2 hours in it is rock solid at the expected 504.  Not going to count those chickens, will see what it looks like tomorrow.

237 was repeated "x" from chips over four reboots, so bailed.  231 was 428 over an hour at the pool, also bailed.  That unit just doesn't want to OC.  Reverted to 225/no-volt.

Other unit, however, continues to hum along at 504 after 5h.  I do not understand these things.

I noticed that repeated x's clear when you restart cgminer e.g via the System Start Up tab (which also happens when you Save & Apply settings) - just saying so you can reduce your restart / reboot cycle length.

Been said a lot of times. S3's are the same, but different ..... most of the S3 variants in my stable run best at different settings, and those with the same settings, on the same pool, over the same connection produce differing results! So there goes.

All three OC experiments failed.  Both of the other units I tried 250/0750 with looked fantastic for the first hour, then slid into slow decline without any symptoms other than declining hashrate.  They bottomed out at about 430 after 12 hours.  Reverting to stock and taking a break!
hero member
Activity: 518
Merit: 500
December 22, 2014, 07:58:10 AM
It took longer, but 250/0750 also a dead end.  Over 500 first hour, then down.  After 3h down to 485 average, 458 last hour on the pool.  All "o" on the chips and only 1 HW.  Dropping to 243/0750 for the next run.


243/0750 also a dead end, dropped to 4h running average of 471, with last hour on the pool at 449.  Trying 237/0750.

I also started playing with the slowest of the others (225 for 453, no voltage change).  Trying 250/0750, and so far 2 hours in it is rock solid at the expected 504.  Not going to count those chickens, will see what it looks like tomorrow.

237 was repeated "x" from chips over four reboots, so bailed.  231 was 428 over an hour at the pool, also bailed.  That unit just doesn't want to OC.  Reverted to 225/no-volt.

Other unit, however, continues to hum along at 504 after 5h.  I do not understand these things.

I noticed that repeated x's clear when you restart cgminer e.g via the System Start Up tab (which also happens when you Save & Apply settings) - just saying so you can reduce your restart / reboot cycle length.

Been said a lot of times. S3's are the same, but different ..... most of the S3 variants in my stable run best at different settings, and those with the same settings, on the same pool, over the same connection produce differing results! So there goes.
member
Activity: 89
Merit: 10
December 22, 2014, 07:50:54 AM
It took longer, but 250/0750 also a dead end.  Over 500 first hour, then down.  After 3h down to 485 average, 458 last hour on the pool.  All "o" on the chips and only 1 HW.  Dropping to 243/0750 for the next run.


243/0750 also a dead end, dropped to 4h running average of 471, with last hour on the pool at 449.  Trying 237/0750.

I also started playing with the slowest of the others (225 for 453, no voltage change).  Trying 250/0750, and so far 2 hours in it is rock solid at the expected 504.  Not going to count those chickens, will see what it looks like tomorrow.

237 was repeated "x" from chips over four reboots, so bailed.  231 was 428 over an hour at the pool, also bailed.  That unit just doesn't want to OC.  Reverted to 225/no-volt.

Other unit, however, continues to hum along at 504 after 5h.  I do not understand these things.
member
Activity: 89
Merit: 10
December 22, 2014, 04:59:48 AM
It took longer, but 250/0750 also a dead end.  Over 500 first hour, then down.  After 3h down to 485 average, 458 last hour on the pool.  All "o" on the chips and only 1 HW.  Dropping to 243/0750 for the next run.


243/0750 also a dead end, dropped to 4h running average of 471, with last hour on the pool at 449.  Trying 237/0750.

I also started playing with the slowest of the others (225 for 453, no voltage change).  Trying 250/0750, and so far 2 hours in it is rock solid at the expected 504.  Not going to count those chickens, will see what it looks like tomorrow.
member
Activity: 89
Merit: 10
December 22, 2014, 01:09:57 AM
My procedure lately is to put in freq/volt, save & apply, power cycle, then system/reboot.  I added on the last step after just a power cycle would result in bad stats in Miner Status.

I used to have that issue (and always had to do an SSH reboot after a power cycle). Of late, though, it seems to have been fixed .... all I did once is before I rebooted via SSH, I first went into the System -> Start Up tab and stopped cgminer, then entered reboot in the SSH window. Now the stats are OK after a brutal power cycle .... (but I was called names when I mentioned the stats problem on this forum!)

It doesn't happen every time, but a significant % of power cycles result in Miner Status using the previous elapsed time, so everything gets pushed lower.  A warm reboot always results in the correct outcome.  This is a funny hobby to have, these things have minds of their own.
member
Activity: 89
Merit: 10
December 22, 2014, 12:46:42 AM
It took longer, but 250/0750 also a dead end.  Over 500 first hour, then down.  After 3h down to 485 average, 458 last hour on the pool.  All "o" on the chips and only 1 HW.  Dropping to 243/0750 for the next run.
hero member
Activity: 518
Merit: 500
December 21, 2014, 09:55:18 PM
Sorry, missed this post.  I will try 275/0800 after we see what happens with 250/0750.  My procedure lately is to put in freq/volt, save & apply, power cycle, then system/reboot.  I added on the last step after just a power cycle would result in bad stats in Miner Status.

I used to have that issue (and always had to do an SSH reboot after a power cycle). Of late, though, it seems to have been fixed .... all I did once is before I rebooted via SSH, I first went into the System -> Start Up tab and stopped cgminer, then entered reboot in the SSH window. Now the stats are OK after a brutal power cycle .... (but I was called names when I mentioned the stats problem on this forum!)

Have you tried OC on an S3+ with factory thermal paste?  The six I am working with are untouched.  So if it is a chip-level thermal problem that is not reported to the sw, then I guess that could explain the difference here.

I did OC one S3+ before I redid the paste which worked OK at 262.5 (which was the only "good" freq I had at the time). I now redo all the S3's I get by, at the very least, putting heat-pads on the chips, so for now all have been "modded" if you like.
Pages:
Jump to: