I continue to find this extremely frustrating. I am running 6 S3+ units, each supplied by a 750-800W power supply with a single 12V rail and all four PCI-E connectors connected. I tried the 275/0815 settings, and exactly the same thing happened as the last time. Hour 1: fantastic, all units over 500 GH/s, holy crap why did I not do this earlier. Hour 2: OK, but hashrates down both as reported by units and at the pool. Hour 3: terrible, all hashrates reported by units and by pool way below stock results. So I have yet again reverted everything to 225/231/243/237/225/237 with voltage left blank.
I do not understand the mechanism here. If it is heat, why does it take 2 hours to show up? With the OC settings, all chips show up as "o" and working. But the hashrate results speak for themselves. But why the very prominent jump in hashrate for the first hour, but then utter crap out in hour 3? Can anybody explain this?
Topic: Antminer S3 batch 6 overclocking - page 3. (Read 23027 times)
Updated OP with freq 275 OC with voltage setting.
New post overcloking with voltage setting in new firmware: https://bitcointalksearch.org/topic/s3-bm1382-overclocking-with-voltage-setting-883197
I just tried this and after building up to normal speed, the hashrate dropped back down to about 1.3GH/s a few minutes later. I checked the frequency and it was set as expected. The hashrate started increasing again, but quite slowly, so I decided to reflash to the previous firmware for now.
Have you tried it yet?
I can pretty much guarrantee that this will work for all BM1382 boards, it just depends on whether you want to do it. First, run it at a frequency within the bitmain spec (the black numbers in the last table) with the voltage set. The rate will take a while to settle and will at the very least match the spec rate (expected hash in the last table), but more likely beat it (as I have demonstrated). More important though, is the lower HW rate (and again, do not jump at conclusions after the first half hour, let it run for a few hours).
If you feel the HW rate is low enough (even not and just feel like it!), turn up the freq within that voltage range (this is mine through my tests not bitmain's) and you should be OK.
For the 262.5 freq test, the voltage setting is 0750, which is the datasheet voltage for freq 250. Start with 250 and I bet you'll get very few HW errors and a good hash speed, then if you feel like it, turn up the freq and watch your hash-speed increase, with still few HW errors.
Thanks pekatete. Much appreciated. I'll try it again over the weekend.
Cheers.
New post overcloking with voltage setting in new firmware: https://bitcointalksearch.org/topic/s3-bm1382-overclocking-with-voltage-setting-883197
I just tried this and after building up to normal speed, the hashrate dropped back down to about 1.3GH/s a few minutes later. I checked the frequency and it was set as expected. The hashrate started increasing again, but quite slowly, so I decided to reflash to the previous firmware for now.
Have you tried it yet?
I can pretty much guarrantee that this will work for all BM1382 boards, it just depends on whether you want to do it. First, run it at a frequency within the bitmain spec (the black numbers in the last table) with the voltage set. The rate will take a while to settle and will at the very least match the spec rate (expected hash in the last table), but more likely beat it (as I have demonstrated). More important though, is the lower HW rate (and again, do not jump at conclusions after the first half hour, let it run for a few hours).
If you feel the HW rate is low enough (even not and just feel like it!), turn up the freq within that voltage range (this is mine through my tests not bitmain's) and you should be OK.
For the 262.5 freq test, the voltage setting is 0750, which is the datasheet voltage for freq 250. Start with 250 and I bet you'll get very few HW errors and a good hash speed, then if you feel like it, turn up the freq and watch your hash-speed increase, with still few HW errors.
New post overcloking with voltage setting in new firmware: https://bitcointalksearch.org/topic/s3-bm1382-overclocking-with-voltage-setting-883197
I just tried this and after building up to normal speed, the hashrate dropped back down to about 1.3GH/s a few minutes later. I checked the frequency and it was set as expected. The hashrate started increasing again, but quite slowly, so I decided to reflash to the previous firmware for now.
Have you tried it yet?
New post overcloking with voltage setting in new firmware: https://bitcointalksearch.org/topic/s3-bm1382-overclocking-with-voltage-setting-883197
Even with the new cgminer file, my units are doing a little worse than with the previous one. I am guessing I am losing around 10-14 GH/s per device, which is not bad but when you have 11 of them it makes a slight difference.
Do you have the latest firmware on them? i had exactly the same experience with my batch 6 units and reverted to the stock cgminer, however (again as is documented in this thread), when I updated to the latest firmware, which I had to do when upgrading my S1's, I get the same result as the stock, or slightly better, but with the security flaws plugged.Yeah I have the latest firmware, it is dated 8/26/2014. My issue is probably the 5 batch 1 miners I have, even though some of my batch 5 units are a little slow as well.
Hi m8, not sure if it's me you're thinking of above, but I did have my best results with Arctic Silver conductive paste and my latest application of Zalman paste was a lot of effort for not much reward. I've just bought some Innovation Cooling IC Diamond 7-Carat thermal compound, so will give that a whirl when I have a chance. Still deliberating about doing the big central heatsinks - presumably this involves removing the blades? Is that a straightforward process? I get funny results with my asics at different frequencies: one 'x' always shows up at 225, but not at higher frequencies and similarly with some of the others, so although I always get an 'x' at higher frequencies somewhere, it's often in different places. Also, my hashrate is rubbish at higher freqs anyway now, it only goes quicker at 231 and that doesn't seem to last long. I tend to keep it at the default 118 now and main task is to stop my hashrate dwindling away, which gradually seems to happen on my problem s3.
BTW, I've upgraded to ck's latest cgminer (4.6.1-141020) and seems ok so far - no restarts, etc. I also removed --queue 4096 and added --lowmem in the cgminer startup script, as recommended by ck.
Removing board from the heatsink does not involve much more than removing the top heatsink, just another set of screws then you slide it off (you do not have to unscrew the heatsinks from the braces).
I have not tried adding the --lowmem switch yet as I do not readily know the process, but will dig around tonite (or tomorow) and try it.
Thanks again for keeping us up to date.
Hi m8. Another little update... I tried to do the big heatsinks between the boards, but could not remove one of the screws (as you know, they go through the board itself) whatever I tried - the others were very tight too, but I managed those. In the end, I gave up on that part of the plan. However, the rest of the plan seems to have worked well: I redid the outer heatsinks using Diamond 7-Carat thermal compound and I fitted little heatsinks on the DC-DC converter chips. Since doing that, the problem S3 has sat solidly at 440 Ghash/s for weeks. So a big result (so far...).
Edit: Hmmm. My first forced reboot today (19th Nov) of the problem S3 since 'fixing' it. Average hash was heading south, after being rock solid for weeks. Didn't see that coming...
Edit2: Lost my average hash reading (again), so updated to latest firmware to see if that improved things. Ran reliably at 440 Ghash/s until 23rd Nov, when it suddenly stopped hashing and started beeping for 5 minutes. Couldn't find anything wrong via the web interface and it suddenly started working again - back at 440Ghash/s. Other S3 on same router not affected. Don't know what caused that...
Have anyone damaged a unit by OCing to like 250?
Or is it "safe" to just max them out? (if you don't get high numbers of HW-error)...
It there anything ells that I should look out for while OC to know if i run them to hard?
Best regards, and happy Halloween!
/Badz
So long as you have the unit powered properly (and you do not mind the increase in power consumption), then clock to your pleasure. Of-course when errors start geting out of hand e.g > .99% (with the new firmware you can check the %) then keep going! I have an upgraded S1 to S3 unit that is running at freq 268.5 with ~539 GH/s, however, my S3's won't go beyond 262 without the HW getting "out of hand".Or is it "safe" to just max them out? (if you don't get high numbers of HW-error)...
It there anything ells that I should look out for while OC to know if i run them to hard?
Best regards, and happy Halloween!
/Badz
PS. My guide to HW % is just mine, not official and I have not seen anyone recomend it anywhere. Follow at your own risk!
Have anyone damaged a unit by OCing to like 250?
Or is it "safe" to just max them out? (if you don't get high numbers of HW-error)...
It there anything ells that I should look out for while OC to know if i run them to hard?
Best regards, and happy Halloween!
/Badz
Or is it "safe" to just max them out? (if you don't get high numbers of HW-error)...
It there anything ells that I should look out for while OC to know if i run them to hard?
Best regards, and happy Halloween!
/Badz
OK, there is a fix for the error thrown by the new firmware update.
Do this ONLY after you have updated to the firmware of 13th Oct 2014
1. SSH into you S3 and login
2. Enter this: sed -i 's/Save\&Apply/Save\&Apply/g' /usr/lib/lua/luci/model/cbi/cgminer/cgminer.lua
Press enter and all should be OK. You can now enter the miner configuration page.
EDIT: Updated OP with instructions.
Do this ONLY after you have updated to the firmware of 13th Oct 2014
1. SSH into you S3 and login
2. Enter this: sed -i 's/Save\&Apply/Save\&Apply/g' /usr/lib/lua/luci/model/cbi/cgminer/cgminer.lua
Press enter and all should be OK. You can now enter the miner configuration page.
EDIT: Updated OP with instructions.
Bitmain released a new firmware fixing the issue.
OK, there is a fix for the error thrown by the new firmware update.
Do this ONLY after you have updated to the firmware of 13th Oct 2014
1. SSH into you S3 and login
2. Enter this: sed -i 's/Save\&Apply/Save\&Apply/g' /usr/lib/lua/luci/model/cbi/cgminer/cgminer.lua
Press enter and all should be OK. You can now enter the miner configuration page.
EDIT: Updated OP with instructions.
Do this ONLY after you have updated to the firmware of 13th Oct 2014
1. SSH into you S3 and login
2. Enter this: sed -i 's/Save\&Apply/Save\&Apply/g' /usr/lib/lua/luci/model/cbi/cgminer/cgminer.lua
Press enter and all should be OK. You can now enter the miner configuration page.
EDIT: Updated OP with instructions.
Looks like Bitmain released new firmware with version 4.6.1. I upgraded a couple of miners to that to see if I get better results. I did notice they changed the display on the mining status page slightly in the new version.
You are right! They have had the new firmware up for a while going by the date, i.e 13th October 2014
I'll update one of my S3's and see how well it does ... thanks for the headsup!
The date on the firmware is from last week, but they've only had it up for day or two. I did notice a major problem. The miner configuration page has some HTML errors preventing you from being able to make any changes to that page, including frequency.
I'll report it to Bitmain.
That is the under-statement of the year thus far!
The firmware update is completely un-usable! The configuration page is where you point to your mining pool from, and if the page can not load, you can not change / add any pools and the rig defaults to mining on the shipped pools (bitmain's pools?). Honestly Bitmain, your reputation is going down the drain here!
Looks like Bitmain released new firmware with version 4.6.1. I upgraded a couple of miners to that to see if I get better results. I did notice they changed the display on the mining status page slightly in the new version.
You are right! They have had the new firmware up for a while going by the date, i.e 13th October 2014
I'll update one of my S3's and see how well it does ... thanks for the headsup!
The date on the firmware is from last week, but they've only had it up for day or two. I did notice a major problem. The miner configuration page has some HTML errors preventing you from being able to make any changes to that page, including frequency.
I'll report it to Bitmain.
Looks like Bitmain released new firmware with version 4.6.1. I upgraded a couple of miners to that to see if I get better results. I did notice they changed the display on the mining status page slightly in the new version.
You are right! They have had the new firmware up for a while going by the date, i.e 13th October 2014
I'll update one of my S3's and see how well it does ... thanks for the headsup!
If you care to try (and it is worth your while), could you upgrade to 4.6.1-141009 (link in OP) which is what I used and do not get any unexpected restarts? Also, what batch of S3+'s is that?
That version is no longer available on the website. S3+ Batch 8. I tried it on S3 Batch 5's as well. All of them exhibit the same issue.
Would using the latest (version 4.7) binary work on an S3 or does it need to be specifically compiled for the S3?
I cannot seem to find the minor version of cgminer installed on my rigs (simply 4.6.1 via cgminer-api), but yes you are right, the older cgminer has now been pulled down (which was not the case a couple of hours ago!). I suggest the next logical thing to do is to ask on the cgminer thread.
Looks like Bitmain released new firmware with version 4.6.1. I upgraded a couple of miners to that to see if I get better results. I did notice they changed the display on the mining status page slightly in the new version.
Even with the new cgminer file, my units are doing a little worse than with the previous one. I am guessing I am losing around 10-14 GH/s per device, which is not bad but when you have 11 of them it makes a slight difference.
Do you have the latest firmware on them? i had exactly the same experience with my batch 6 units and reverted to the stock cgminer, however (again as is documented in this thread), when I updated to the latest firmware, which I had to do when upgrading my S1's, I get the same result as the stock, or slightly better, but with the security flaws plugged.Yeah I have the latest firmware, it is dated 8/26/2014. My issue is probably the 5 batch 1 miners I have, even though some of my batch 5 units are a little slow as well.
Hi m8, not sure if it's me you're thinking of above, but I did have my best results with Arctic Silver conductive paste and my latest application of Zalman paste was a lot of effort for not much reward. I've just bought some Innovation Cooling IC Diamond 7-Carat thermal compound, so will give that a whirl when I have a chance. Still deliberating about doing the big central heatsinks - presumably this involves removing the blades? Is that a straightforward process? I get funny results with my asics at different frequencies: one 'x' always shows up at 225, but not at higher frequencies and similarly with some of the others, so although I always get an 'x' at higher frequencies somewhere, it's often in different places. Also, my hashrate is rubbish at higher freqs anyway now, it only goes quicker at 231 and that doesn't seem to last long. I tend to keep it at the default 118 now and main task is to stop my hashrate dwindling away, which gradually seems to happen on my problem s3.
BTW, I've upgraded to ck's latest cgminer (4.6.1-141020) and seems ok so far - no restarts, etc. I also removed --queue 4096 and added --lowmem in the cgminer startup script, as recommended by ck.
Removing board from the heatsink does not involve much more than removing the top heatsink, just another set of screws then you slide it off (you do not have to unscrew the heatsinks from the braces).
I have not tried adding the --lowmem switch yet as I do not readily know the process, but will dig around tonite (or tomorow) and try it.
Thanks again for keeping us up to date.
Even with the new cgminer file, my units are doing a little worse than with the previous one. I am guessing I am losing around 10-14 GH/s per device, which is not bad but when you have 11 of them it makes a slight difference.
Do you have the latest firmware on them? i had exactly the same experience with my batch 6 units and reverted to the stock cgminer, however (again as is documented in this thread), when I updated to the latest firmware, which I had to do when upgrading my S1's, I get the same result as the stock, or slightly better, but with the security flaws plugged.Yeah I have the latest firmware, it is dated 8/26/2014. My issue is probably the 5 batch 1 miners I have, even though some of my batch 5 units are a little slow as well.
Hi m8, not sure if it's me you're thinking of above, but I did have my best results with Arctic Silver conductive paste and my latest application of Zalman paste was a lot of effort for not much reward. I've just bought some Innovation Cooling IC Diamond 7-Carat thermal compound, so will give that a whirl when I have a chance. Still deliberating about doing the big central heatsinks - presumably this involves removing the blades? Is that a straightforward process? I get funny results with my asics at different frequencies: one 'x' always shows up at 225, but not at higher frequencies and similarly with some of the others, so although I always get an 'x' at higher frequencies somewhere, it's often in different places. Also, my hashrate is rubbish at higher freqs anyway now, it only goes quicker at 231 and that doesn't seem to last long. I tend to keep it at the default 118 now and main task is to stop my hashrate dwindling away, which gradually seems to happen on my problem s3.
BTW, I've upgraded to ck's latest cgminer (4.6.1-141020) and seems ok so far - no restarts, etc. I also removed --queue 4096 and added --lowmem in the cgminer startup script, as recommended by ck.
^^^ very well and you are welcome.
hopefully, you get to mine an entire block ... all on your own!
hopefully, you get to mine an entire block ... all on your own!
Haha I gave up on that long ago. Actually I did point my miners at bitsolo.net over the weekend while I was building my P2Pool server. But now I have my own P2Pool server that I am running. Mining a block is enticing...and I may devote my S1's to the task once I retire them, but I am trying to get a few more hashes out of them first...
^^^ very well and you are welcome.
hopefully, you get to mine an entire block ... all on your own!
hopefully, you get to mine an entire block ... all on your own!
Haha I gave up on that long ago. Actually I did point my miners at bitsolo.net over the weekend while I was building my P2Pool server. But now I have my own P2Pool server that I am running. Mining a block is enticing...and I may devote my S1's to the task once I retire them, but I am trying to get a few more hashes out of them first...
^^^ very well and you are welcome.
hopefully, you get to mine an entire block ... all on your own!
hopefully, you get to mine an entire block ... all on your own!
Haha I gave up on that long ago. Actually I did point my miners at bitsolo.net over the weekend while I was building my P2Pool server. But now I have my own P2Pool server that I am running. Mining a block is enticing...and I may devote my S1's to the task once I retire them, but I am trying to get a few more hashes out of them first...
Jump to: