Topic: BITMAIN Antminer S1 support and OverClocking thread - page 4. (Read 144972 times)
Has anyone ever tried clocking an S1 beyond 400 MHz? Bitmain docs give settings info to clock up to 500 MHz. If anyone has tried let me know the power draw and hash rate and error rates you were getting. Thanks.
What would be some FOUTs to fill out this little table 
E.g., 222.5, 220, and/or 217.5. TIA
E.g., 222.5, 220, and/or 217.5. TIAAll possible values:
Code:
chip_freq timeout freq_value(s)
37.50 373 0583, 0b87
39.06 358 0c07
40.62 344 0603, 0c87
42.19 331 0d07
43.75 320 0683, 0d87
45.31 308 0e07
46.88 298 0703, 0e87
48.44 289 0f07
50.00 280 0783, 0f87
51.56 271 1007
53.12 263 0803, 1087
54.69 256 1107
56.25 248 0883, 1187
57.81 242 1207
59.38 235 0903, 1287
60.94 229 1307
62.50 224 0983, 1387, 4983, 5387
64.06 218 1407, 5407
65.62 213 0a03, 1487, 4a03, 5487
67.19 208 1507, 5507
68.75 203 0a83, 1587, 4a83, 5587
70.31 199 1607, 5607
71.88 194 0b03, 1687, 4b03, 5687
73.44 190 1707, 5707
75.00 186 0582, 0b83, 0b86, 1787, 4b83, 5787
76.56 182 5807
78.12 179 0c06, 4c03, 5887
79.69 175 5907
81.25 172 0602, 0c86, 4c83, 5987
82.81 169 5a07
84.38 165 0d06, 4d03, 5a87
85.94 162 5b07
87.50 160 0682, 0d86, 4d83, 5b87
89.06 157 5c07
90.62 154 0e06, 4e03, 5c87
92.19 151 5d07
93.75 149 0702, 0e86, 4e83, 5d87
95.31 146 5e07
96.88 144 0f06, 4f03, 5e87
98.44 142 5f07
100.00 140 0782, 0f86, 4f83, 5f87
101.56 137 6007
103.12 135 1006, 5003, 6087
104.69 133 6107
106.25 131 0802, 1086, 5083, 6187
107.81 129 6207
109.38 128 1106, 5103, 6287
110.94 126 6307
112.50 124 0882, 1186, 5183, 6387
114.06 122 6407
115.62 121 1206, 5203, 6487
117.19 119 6507
118.75 117 0902, 1286, 5283, 6587
120.31 116 6607
121.88 114 1306, 5303, 6687
123.44 113 6707
125.00 112 0982, 1386, 4982, 5383, 5386, 6787
128.12 109 1406, 5406
131.25 106 0a02, 1486, 4a02, 5486
134.38 104 1506, 5506
137.50 101 0a82, 1586, 4a82, 5586
140.62 99 1606, 5606
143.75 97 0b02, 1686, 4b02, 5686
146.88 95 1706, 5706
150.00 93 0581, 0b82, 0b85, 1786, 4b82, 5786
153.12 91 5806
156.25 89 0c05, 4c02, 5886
159.38 87 5906
162.50 86 0601, 0c85, 4c82, 5986
165.62 84 5a06
168.75 82 0d05, 4d02, 5a86
171.88 81 5b06
175.00 80 0681, 0d85, 4d82, 5b86
178.12 78 5c06
181.25 77 0e05, 4e02, 5c86
184.38 75 5d06
187.50 74 0701, 0e85, 4e82, 5d86
190.62 73 5e06
193.75 72 0f05, 4f02, 5e86
196.88 71 5f06
200.00 70 0781, 0f85, 4f82, 5f86
203.12 68 6006
206.25 67 1005, 5002, 6086
209.38 66 6106
212.50 65 0801, 1085, 5082, 6186
215.62 64 6206
218.75 64 1105, 5102, 6286
221.88 63 6306
225.00 62 0881, 1185, 5182, 6386
228.12 61 6406
231.25 60 1205, 5202, 6486
234.38 59 6506
237.50 58 0901, 1285, 5282, 6586
240.62 58 6606
243.75 57 1305, 5302, 6686
246.88 56 6706
250.00 56 0981, 1385, 4981, 5382, 5385, 6786
256.25 54 1405, 5405
262.50 53 0a01, 1485, 4a01, 5485
268.75 52 1505, 5505
275.00 50 0a81, 1585, 4a81, 5585
281.25 49 1605, 5605
287.50 48 0b01, 1685, 4b01, 5685
293.75 47 1705, 5705
300.00 46 0580, 0b81, 0b84, 1785, 4b81, 5785
306.25 45 5805
312.50 44 0c04, 4c01, 5885
318.75 43 5905
325.00 43 0600, 0c84, 4c81, 5985
331.25 42 5a05
337.50 41 0d04, 4d01, 5a85
343.75 40 5b05
350.00 40 0680, 0d84, 4d81, 5b85
356.25 39 5c05
362.50 38 0e04, 4e01, 5c85
368.75 37 5d05
375.00 37 0700, 0e84, 4e81, 5d85
381.25 36 5e05
387.50 36 0f04, 4f01, 5e85
393.75 35 5f05
400.00 35 0780, 0f84, 4f81, 5f85
406.25 34 6005
412.50 33 1004, 5001, 6085
418.75 33 6105
425.00 32 0800, 1084, 5081, 6185
431.25 32 6205
437.50 32 1104, 5101, 6285
443.75 31 6305
450.00 31 0880, 1184, 5181, 6385
456.25 30 6405
462.50 30 1204, 5201, 6485
468.75 29 6505
475.00 29 0900, 1284, 5281, 6585
481.25 29 6605
487.50 28 1304, 5301, 6685
493.75 28 6705
500.00 28 0980, 1384, 4980, 5381, 5384, 6785
512.50 27 1404, 5404
525.00 26 0a00, 1484, 4a00, 5484
537.50 26 1504, 5504
550.00 25 0a80, 1584, 4a80, 5584
562.50 24 1604, 5604
575.00 24 0b00, 1684, 4b00, 5684
587.50 23 1704, 5704
600.00 23 0b80, 1784, 4b80, 5784
612.50 22 5804
625.00 22 4c00, 5884
637.50 21 5904
650.00 21 4c80, 5984
662.50 21 5a04
675.00 20 4d00, 5a84
687.50 20 5b04
700.00 20 4d80, 5b84
712.50 19 5c04
725.00 19 4e00, 5c84
737.50 18 5d04
750.00 18 4e80, 5d84
762.50 18 5e04
775.00 18 4f00, 5e84
787.50 17 5f04
800.00 17 4f80, 5f84
812.50 17 6004
825.00 16 5000, 6084
837.50 16 6104
850.00 16 5080, 6184
862.50 16 6204
875.00 16 5100, 6284
887.50 15 6304
900.00 15 5180, 6384
912.50 15 6404
925.00 15 5200, 6484
937.50 14 6504
950.00 14 5280, 6584
962.50 14 6604
975.00 14 5300, 6684
987.50 14 6704
1000.00 14 5380, 6784
With the definition of "possible" of "fits the formula". I'm quite sure it's impossible to get any results but fried chips with values like 5380...
The formula for HW % is HW/(diffA+diffR+HW)*100 correct?
I assume it looks more like HW/((diffA+diffR+HW)*100) given that multiplication comes before division.
never wrote it down I just use a website. http://www.coincadence.com/antminer-s1-hardware-error/I assume it looks more like HW/((diffA+diffR+HW)*100) given that multiplication comes before division.
Formula: Error % = HW / ( HW + DiffA + DiffR) * 100
Thanks. That's a great tool. This is rather disheartening however. Any attempt at overclocking results in at least 14% HW errors.
Why ignore DiffS ? I use: Error % = 100 x HW / (HW + DiffA + DiffR + DiffS)
I can OC all 35 of my S1s to 375, a few to 387 and a couple to 393. Anything higher does not work.
I have a problem with my Antminer S2 (Batch 4) hoping someone has an idea.
After powering it I was able to access it and enter network & mining configuration.
The miner started to work, after some minutes it beeped and turned off.
Although I unplugged all power cables, plugged them in again it does not turn on again.
Does anyone have an idea what can be wrong? I assume it is the PSU since after switching it on it stay absolutely nothing happens.
I would appreciate any suggestions.
Regards
After powering it I was able to access it and enter network & mining configuration.
The miner started to work, after some minutes it beeped and turned off.
Although I unplugged all power cables, plugged them in again it does not turn on again.
Does anyone have an idea what can be wrong? I assume it is the PSU since after switching it on it stay absolutely nothing happens.
I would appreciate any suggestions.
Regards
1. Have you updated to the latest firmaware initramfs.bin.SD-20140619.tar
2. Are all 4 big fans spinning when you power on
I've had to simply disassemble the S2s and giggle the wires on the fans and put them back. Also I've had the 6-pin PCIe connectors back out and loose connection because they were not clicked all the way in.
3. The PSU they ship is not up to the task, especially if it's hot or you're overclocking. I replaced all mine with Corsair AX1200s.
Good luck
1. Even at clock speed the miner gives 0.3% HW Error in my other ants it 0%
I have owned many Ants ... and everyone was different .... 0.3% is acceptable in my book ... keep mining ... over 1% and you should get itchy.
I have six....and I will agree each Ant is different with HWE%. Three are under .4%, one is at 1.5% and the last two are 2.1% and 2.8%. ...all are "freq'ed" at 393MHz.
The three under .4% have an average Hashrate of over 200GH/s all the time. ...the other three are under 200GH/s. In fact, the 2.8% miner shows 195GH/s.
What can I look at to determine what may be producing the lower hashrate?
Any thoughts are are appreciated.
Are you using the latest version of their software?
Have you tried to slow the ants down a little bit?
I run my two ants at 393 MHz most of the time with HW in the range of 0.2% but when I slow them down to 350 the HW drop to less than 0.001%.
Yes latest version firmware is using.
Try to reduce the frequency. If you manage to get a very low HW at 350 MHz you'll improve your eficiency. It's better to have the ants working at a lower freq with close to zero errors than to have them overclocked but wasting power on a lot of errors
Its working fine now at normal HWE%.
I lowered to stock clock and then pushed to 387. Not mining almost near 200GH.
1. Even at clock speed the miner gives 0.3% HW Error in my other ants it 0%
I have owned many Ants ... and everyone was different .... 0.3% is acceptable in my book ... keep mining ... over 1% and you should get itchy.
I have six....and I will agree each Ant is different with HWE%. Three are under .4%, one is at 1.5% and the last two are 2.1% and 2.8%. ...all are "freq'ed" at 393MHz.
The three under .4% have an average Hashrate of over 200GH/s all the time. ...the other three are under 200GH/s. In fact, the 2.8% miner shows 195GH/s.
What can I look at to determine what may be producing the lower hashrate?
Any thoughts are are appreciated.
Are you using the latest version of their software?
Have you tried to slow the ants down a little bit?
I run my two ants at 393 MHz most of the time with HW in the range of 0.2% but when I slow them down to 350 the HW drop to less than 0.001%.
Yes latest version firmware is using.
Try to reduce the frequency. If you manage to get a very low HWE % at 350 MHz you'll improve your eficiency. It's better to have the ants working at a lower freq with close to zero errors than to have them overclocked but wasting power on a lot of errors
1. Even at clock speed the miner gives 0.3% HW Error in my other ants it 0%
I have owned many Ants ... and everyone was different .... 0.3% is acceptable in my book ... keep mining ... over 1% and you should get itchy.
I have six....and I will agree each Ant is different with HWE%. Three are under .4%, one is at 1.5% and the last two are 2.1% and 2.8%. ...all are "freq'ed" at 393MHz.
The three under .4% have an average Hashrate of over 200GH/s all the time. ...the other three are under 200GH/s. In fact, the 2.8% miner shows 195GH/s.
What can I look at to determine what may be producing the lower hashrate?
Any thoughts are are appreciated.
Are you using the latest version of their software?
Have you tried to slow the ants down a little bit?
I run my two ants at 393 MHz most of the time with HW in the range of 0.2% but when I slow them down to 350 the HW drop to less than 0.001%.
Yes latest version firmware is using.
1. Even at clock speed the miner gives 0.3% HW Error in my other ants it 0%
I have owned many Ants ... and everyone was different .... 0.3% is acceptable in my book ... keep mining ... over 1% and you should get itchy.
I have six....and I will agree each Ant is different with HWE%. Three are under .4%, one is at 1.5% and the last two are 2.1% and 2.8%. ...all are "freq'ed" at 393MHz.
The three under .4% have an average Hashrate of over 200GH/s all the time. ...the other three are under 200GH/s. In fact, the 2.8% miner shows 195GH/s.
What can I look at to determine what may be producing the lower hashrate?
Any thoughts are are appreciated.
I think temperature is the issue. That particular miner have higher temperature too.
Now when the ambient temperature lowered the error rate is also reduced to normal levels.
1. Even at clock speed the miner gives 0.3% HW Error in my other ants it 0%
I have owned many Ants ... and everyone was different .... 0.3% is acceptable in my book ... keep mining ... over 1% and you should get itchy.
I have six....and I will agree each Ant is different with HWE%. Three are under .4%, one is at 1.5% and the last two are 2.1% and 2.8%. ...all are "freq'ed" at 393MHz.
The three under .4% have an average Hashrate of over 200GH/s all the time. ...the other three are under 200GH/s. In fact, the 2.8% miner shows 195GH/s.
What can I look at to determine what may be producing the lower hashrate?
Any thoughts are are appreciated.
Are you using the latest version of their software?
Have you tried to slow the ants down a little bit?
I run my two ants at 393 MHz most of the time with HW in the range of 0.2% but when I slow them down to 350 the HWE drop to less than 0.001%.
1. Even at clock speed the miner gives 0.3% HW Error in my other ants it 0%
I have owned many Ants ... and everyone was different .... 0.3% is acceptable in my book ... keep mining ... over 1% and you should get itchy.
I have six....and I will agree each Ant is different with HWE%. Three are under .4%, one is at 1.5% and the last two are 2.1% and 2.8%. ...all are "freq'ed" at 393MHz.
The three under .4% have an average Hashrate of over 200GH/s all the time. ...the other three are under 200GH/s. In fact, the 2.8% miner shows 195GH/s.
What can I look at to determine what may be producing the lower hashrate?
Any thoughts are are appreciated.
All 8 S1 miners down but everything checks out ok??
Had a thunderstorm last night, In the morning all 8 of my S1s had stopped mining.
Able to communicate with all through their IP addresses.
Tried reboot from system menu; no change
Tried hard reboot by turning power supplies off/on; no change
Even tried rebooting modem; no change
Everything looks good and I have 3 pools configured but miner status always shows "nothing to report"
Don't get the normal "alive" or "dead" messages
Has anyone else ever seen this problem and any suggestions?
Had a thunderstorm last night, In the morning all 8 of my S1s had stopped mining.
Able to communicate with all through their IP addresses.
Tried reboot from system menu; no change
Tried hard reboot by turning power supplies off/on; no change
Even tried rebooting modem; no change
Everything looks good and I have 3 pools configured but miner status always shows "nothing to report"
Don't get the normal "alive" or "dead" messages
Has anyone else ever seen this problem and any suggestions?
Check your controller and both boards and their components care fully for any damage or smell.
Also make sure to check the PSU's are providing enough power. If you are lucky some component changes may give rebirth to you ASICs else its the last days for your ants!
Before that try a firmware reinstall as a last action. May not work, again, just try it.
I remembered seeing this once before, and rebooting the router did the trick. Built in firewall must have been keeping them from going out to the pools while still allowing me to access everything from my PC on the inside. It's awful having to re-solve things because you forgot about the first time you solved it. Unfortunately, memory does not improve with age.
All 8 S1 miners down but everything checks out ok??
Had a thunderstorm last night, In the morning all 8 of my S1s had stopped mining.
Able to communicate with all through their IP addresses.
Tried reboot from system menu; no change
Tried hard reboot by turning power supplies off/on; no change
Even tried rebooting modem; no change
Everything looks good and I have 3 pools configured but miner status always shows "nothing to report"
Don't get the normal "alive" or "dead" messages
Has anyone else ever seen this problem and any suggestions?
Had a thunderstorm last night, In the morning all 8 of my S1s had stopped mining.
Able to communicate with all through their IP addresses.
Tried reboot from system menu; no change
Tried hard reboot by turning power supplies off/on; no change
Even tried rebooting modem; no change
Everything looks good and I have 3 pools configured but miner status always shows "nothing to report"
Don't get the normal "alive" or "dead" messages
Has anyone else ever seen this problem and any suggestions?
Check your controller and both boards and their components care fully for any damage or smell.
Also make sure to check the PSU's are providing enough power. If you are lucky some component changes may give rebirth to you ASICs else its the last days for your ants!
Before that try a firmware reinstall as a last action. May not work, again, just try it.
All 8 S1 miners down but everything checks out ok??
Had a thunderstorm last night, In the morning all 8 of my S1s had stopped mining.
Able to communicate with all through their IP addresses.
Tried reboot from system menu; no change
Tried hard reboot by turning power supplies off/on; no change
Even tried rebooting modem; no change
Everything looks good and I have 3 pools configured but miner status always shows "nothing to report"
Don't get the normal "alive" or "dead" messages
Has anyone else ever seen this problem and any suggestions?
Had a thunderstorm last night, In the morning all 8 of my S1s had stopped mining.
Able to communicate with all through their IP addresses.
Tried reboot from system menu; no change
Tried hard reboot by turning power supplies off/on; no change
Even tried rebooting modem; no change
Everything looks good and I have 3 pools configured but miner status always shows "nothing to report"
Don't get the normal "alive" or "dead" messages
Has anyone else ever seen this problem and any suggestions?
How much does your ant fluctuate in it's hash rate?
Looking at the web interface or using Mdudes antmonitor, how much does your ant s1 fluctuate in hashing speed reported?
My s1 running at 400mhz with ~0.327% error rate and ~2% reject hashes on average 203gh/s but it fluctuates between 235gh/s and as low as 187gh/s.
It's running of a dell 750w server psu and has two fans. fan speed is reported as 1740 and temp is 43.
What does your ant do?
Looking at the web interface or using Mdudes antmonitor, how much does your ant s1 fluctuate in hashing speed reported?
My s1 running at 400mhz with ~0.327% error rate and ~2% reject hashes on average 203gh/s but it fluctuates between 235gh/s and as low as 187gh/s.
It's running of a dell 750w server psu and has two fans. fan speed is reported as 1740 and temp is 43.
What does your ant do?
1. Even at clock speed the miner gives 0.3% HW Error in my other ants it 0%
I have owned many Ants ... and everyone was different .... 0.3% is acceptable in my book ... keep mining ... over 1% and you should get itchy.
But problem of overheating can't be ignored. It leads power consumption issues.
Issue fixed.
1. Even at clock speed the miner gives 0.3% HW Error in my other ants it 0%
I have owned many Ants ... and everyone was different .... 0.3% is acceptable in my book ... keep mining ... over 1% and you should get itchy.
But problem of overheating can't be ignored. It leads power consumption issues.
1. Even at clock speed the miner gives 0.3% HW Error in my other ants it 0%
I have owned many Ants ... and everyone was different .... 0.3% is acceptable in my book ... keep mining ... over 1% and you should get itchy.
Here’s a little suggestion for those of you concerned with the S1 heating in the summertime.
Where I live, the temperature outside goes up to 37/38C (aprox 100F) in the afternoon and my miners are working in the 55C range during the day, although they are properly cooled with dual fans (push-pull) and an external fan. There’s just no cool air around to blow into them…
So I came up with a solution to prevent them from melting the place down while I’m at work. I created two different asic-freq files in /etc/config: “asic-freq-cool” and “asic-freq-warm” the only difference between the two being the fact that in the first one I’m using these lines for the frequency settings:
And in the second one I’m using these lines:
So the basic idea is to slow down the miner during the hottest hours of the day, and overclock it during the night. In order to do this, I created two cron tasks running two scripts.
In /usr/bin run the following commands
(add lines below)
(exit and save file)
(add lines below)
(exit and save file)
The schedulling of the tasks can be done via the S1 GUI in the System/Scheduled tasks tab but I did it by hand
(add lines below)
(exit and save file)
This will slow down my miner at 12AM and will speed it up again at 8PM. Maybe there is a better way to do this but my UNIX skills are very limited
Where I live, the temperature outside goes up to 37/38C (aprox 100F) in the afternoon and my miners are working in the 55C range during the day, although they are properly cooled with dual fans (push-pull) and an external fan. There’s just no cool air around to blow into them…
So I came up with a solution to prevent them from melting the place down while I’m at work. I created two different asic-freq files in /etc/config: “asic-freq-cool” and “asic-freq-warm” the only difference between the two being the fact that in the first one I’m using these lines for the frequency settings:
Code:
option 'freq_value' '4d81' #350M
option 'chip_freq' '350'
option 'timeout' '40'
And in the second one I’m using these lines:
Code:
option 'freq_value' '5f05' #393.75M
option 'chip_freq' '393.75'
option 'timeout' '36'
So the basic idea is to slow down the miner during the hottest hours of the day, and overclock it during the night. In order to do this, I created two cron tasks running two scripts.
In /usr/bin run the following commands
Code:
vi OC-morning
Code:
#!/bin/ash
cp /etc/config/asic-freq-cool /etc/config/asic-freq
reboot
Code:
chmod 775 OC-morning
Code:
vi OC-afternoon
Code:
#!/bin/ash
cp /etc/config/asic-freq-warm /etc/config/asic-freq
reboot
Code:
chmod 775 OC-afternoon
The schedulling of the tasks can be done via the S1 GUI in the System/Scheduled tasks tab but I did it by hand
Code:
crontab -e
Code:
0 12 * * * /etc/config /OC-morning
0 20 * * * /etc/config /OC-afternoon
This will slow down my miner at 12AM and will speed it up again at 8PM. Maybe there is a better way to do this but my UNIX skills are very limited
I am posting this here in case anyone has this problem. I spent more than 6 hours troubleshooting this.
Two of my Antminer S2s had the same issue and I believe it's the SD card inside the Beagleboard that they're using which is a 4 gb Kingston (I'm not sure if it's genuine since their write rate is incredibly slow at 4 mB/sec).
Symptoms
Antminer S2 will not retain settings, reset after reboot.
Or Antminer Blue screen when starting up.
Things Tried But Did not Work
Solution
I tried with a new SD card 2 gb that I had lying about and flashed it with an image I found somewhere on the forum here (i can't remember where now but the guy had a lot |1|1|1| in his nick name). Note this is not a normal flash via the GUI but it's a full sd card flash.
Step 1: Removing the beagle board and the SD card:
Remove the control board (the one in the middle) and you should see a micro sd card slot. Press on it and it will pop up.
Step 2: Changing to a new SD card
Download the official image they recommended for a 4 gb (link provided by BitMainTech) via a support e-mail
https://docs.google.com/file/d/0B9mK2-whJv8cU0Q5R1hIQTJnRVU/
Put it into a sd card reader and use the below app to flash the img to the NEW sd card (don't use the same one).
http://sourceforge.net/projects/win32diskimager/
Replace it the sd card and remount it inside. Give it a go!
If this helped you!
14G2KWbGZkV6TCzdXes4HQJA4Gt5jpAmVP
Two of my Antminer S2s had the same issue and I believe it's the SD card inside the Beagleboard that they're using which is a 4 gb Kingston (I'm not sure if it's genuine since their write rate is incredibly slow at 4 mB/sec).
Symptoms
Antminer S2 will not retain settings, reset after reboot.
Or Antminer Blue screen when starting up.
Things Tried But Did not Work
- Reseating all boards and checking cables
- Resetting to factory defaults
- Flashing a brand new image via the web gui
- Flashing the SD card with a brand new image via a disk imager
- Scandisk of the SD card (no errors reported)
Solution
I tried with a new SD card 2 gb that I had lying about and flashed it with an image I found somewhere on the forum here (i can't remember where now but the guy had a lot |1|1|1| in his nick name
). Note this is not a normal flash via the GUI but it's a full sd card flash.Step 1: Removing the beagle board and the SD card:
Remove the control board (the one in the middle) and you should see a micro sd card slot. Press on it and it will pop up.
Step 2: Changing to a new SD card
Download the official image they recommended for a 4 gb (link provided by BitMainTech) via a support e-mail
https://docs.google.com/file/d/0B9mK2-whJv8cU0Q5R1hIQTJnRVU/
Put it into a sd card reader and use the below app to flash the img to the NEW sd card (don't use the same one).
http://sourceforge.net/projects/win32diskimager/
Replace it the sd card and remount it inside. Give it a go!
If this helped you!
14G2KWbGZkV6TCzdXes4HQJA4Gt5jpAmVP
Jump to: