What is the lowest freq we can go on a S3 ?? For the summer! 
150 easy.
my batch 1 set of 2 has run 24/7/365 since july 25 of 2014
freq 212 as these did not like to clock high. i can not complain since they have run for just under 9 months so far.
Topic: BITMAIN Antminer S3 support and OverClocking thread - page 10. (Read 158144 times)
150 easy.
my batch 1 set of 2 has run 24/7/365 since july 25 of 2014
freq 212 as these did not like to clock high. i can not complain since they have run for just under 9 months so far.
What is the lowest freq we can go on a S3 ?? For the summer!
The file with frequency values for the advanced page with miner settings is
Code:
/usr/lib/lua/luci/model/cbi/cgminer/cgminer.lua
Look at the end of the file for the frequency list.
Here are highlighted in red the lines with new frequency not included in the stock firmware.
Quote
pb:value("13:300:0b82", translate("300M"))
pb:value("14:293.75:1706", translate("293.75M"))
pb:value("14:287.5:0b02", translate("287.5M"))
pb:value("14:281.25:1606", translate("281.25M"))
pb:value("15:275:0a82", translate("275M"))
pb:value("15:268.75:1506", translate("268.75M"))
pb:value("15:262.5:0a02", translate("262.5M"))
pb:value("16:256.25:1406", translate("256.25M"))
pb:value("16:250:0982", translate("250M"))
pb:value("16:243.75:1306", translate("243.75M"))
pb:value("17:237.5:1286", translate("237.5M"))
pb:value("17:231.25:1206", translate("231.25M"))
pb:value("18:225:0882", translate("225M"))
pb:value("18:218.75:1106", translate("218.75M (default)"))
pb:value("18:212.5:1086", translate("212.5M"))
pb:value("19:206.25:1006", translate("206.25M"))
pb:value("20:200:0782", translate("200M"))
pb:value("20:196:1f07", translate("196M"))
pb:value("20:193:0f03", translate("193M"))
pb:value("23:175:0d83", translate("175M"))
pb:value("27:150:0b83", translate("150M"))
pb:value("33:125:0983", translate("125M"))
pb:value("40:100:0783", translate("100M"))
pb:value("14:293.75:1706", translate("293.75M"))
pb:value("14:287.5:0b02", translate("287.5M"))
pb:value("14:281.25:1606", translate("281.25M"))
pb:value("15:275:0a82", translate("275M"))
pb:value("15:268.75:1506", translate("268.75M"))
pb:value("15:262.5:0a02", translate("262.5M"))
pb:value("16:256.25:1406", translate("256.25M"))
pb:value("16:250:0982", translate("250M"))
pb:value("16:243.75:1306", translate("243.75M"))
pb:value("17:237.5:1286", translate("237.5M"))
pb:value("17:231.25:1206", translate("231.25M"))
pb:value("18:225:0882", translate("225M"))
pb:value("18:218.75:1106", translate("218.75M (default)"))
pb:value("18:212.5:1086", translate("212.5M"))
pb:value("19:206.25:1006", translate("206.25M"))
pb:value("20:200:0782", translate("200M"))
pb:value("20:196:1f07", translate("196M"))
pb:value("20:193:0f03", translate("193M"))
pb:value("23:175:0d83", translate("175M"))
pb:value("27:150:0b83", translate("150M"))
pb:value("33:125:0983", translate("125M"))
pb:value("40:100:0783", translate("100M"))
Many thanks, just made these changes to my S3+. Very useful information, kudos to you for providing it!
Wich cgminer version contains the last update from the 9th January ?
Current bios uses cgminer v4.6.1. I did not see any direct changes for S3 in the change log from the orignal ver included to the updated one. So, my best guess is it improves communication with some pools.
No, I'm thinking that I'll absolutely need to lower the wattage/GH/s as the summer heats up and these get more inefficient. I've seen the thread where resistors are soldered in parallel within the voltage regulator but not prepared to do that.
I'll just run a vent tube to the window, to try to help out at hours it's less than 85F outside. It'll be fine running in a closed off room with the rooms vents closed, but that room will be toasty.
The most telling and important part of the miner is the cgminer version, mine only have v3.12.0-1. Still need to look if I can gain anything by upgrading.
As for voltage, your are stuck. I don't think anyone got these to work at anything higher than 250 and stable.
As for voltage, your are stuck. I don't think anyone got these to work at anything higher than 250 and stable.
No, I'm thinking that I'll absolutely need to lower the wattage/GH/s as the summer heats up and these get more inefficient. I've seen the thread where resistors are soldered in parallel within the voltage regulator but not prepared to do that.
Wich cgminer version contains the last update from the 9th January ?
The most telling and important part of the miner is the cgminer version, mine only have v3.12.0-1. Still need to look if I can gain anything by upgrading.
As for voltage, your are stuck. I don't think anyone got these to work at anything higher than 250 and stable.
As for voltage, your are stuck. I don't think anyone got these to work at anything higher than 250 and stable.
May I ask which firmware you're using? I tried one and got a failure to load the GUI situation forcing me back. Is this usual or something to do with my setup?
I think I am using the absolute oldest possible on these S3s.
OpenWrt Barrier Breaker r38031 / LuCI Trunk (svn-r9909)
Kernel Version 3.10.12
Copyright 2011-2013
If you downloaded the right firmware, did you follow instructions to the letter to install?
Firmware version Thu Aug 7 Kernel 3.10.12
I was hoping to move up to a voltage option along with frequency.
May I ask which firmware you're using? I tried one and got a failure to load the GUI situation forcing me back. Is this usual or something to do with my setup?
I think I am using the absolute oldest possible on these S3s.
OpenWrt Barrier Breaker r38031 / LuCI Trunk (svn-r9909)
Kernel Version 3.10.12
Copyright 2011-2013
If you downloaded the right firmware, did you follow instructions to the letter to install?
May I ask which firmware you're using? I tried one and got a failure to load the GUI situation forcing me back. Is this usual or something to do with my setup?
There was this info about the advanced tab further back in the thread, but that's for the newer machines and people that updated the bios. I have no interest in breaking something that works well, so I'm on the old bios still. I also figured anyone inquiring here about overclocking would have looked all through the miner web login. An oversight on my part.
What I'm really interested in seeing is charts showing the difference in different diff settings on these oc s3s.
What I'm really interested in seeing is charts showing the difference in different diff settings on these oc s3s.
Updating bios helps with efficiency as the firmware is further optimized to get the most out of your ASICs. Furthermore, I have gone through all the tabs when I got my S3, however, the other tabs were so grayed out and I use my 46" TV for a display that is further away I simply didn't see this advanced configuration.
Before Overclocking the unit my average hash rate per day chart showed 450 GHs;
After Overclicking (running only 2x 6 Pin) one of my ASICs chips became inactive (on 250 Freq) and the hashrate became more unstable still marginally better and the chart showed 470 GHs;
Because of this huge variance and instability I decided to give my S3 2 more 6 pins running total of 4x 6 Pin and once again attempted to run it on OC (250 Freq) and the hash rate is significantly better and the ASIC that was inactive before is now back to OK state. I haven't run the unit for a long time but I have been observing the hasrate over the period of 5 minutes and it is stable in between 515 GHs - 570 Ghs. Much much better! Anyone who OC's their S3 needs to run 4 x 6 Pin or otherwise it won't make any sense. OH, and the temps im getting is 40C~~
In a 79-86F room, it stays steady at 43 to 45C now. I will optimize the cooling as it gets warmer, otherwise the room will get over 90F easily.
There was this info about the advanced tab further back in the thread, but that's for the newer machines and people that updated the bios. I have no interest in breaking something that works well, so I'm on the old bios still. I also figured anyone inquiring here about overclocking would have looked all through the miner web login. An oversight on my part.
What I'm really interested in seeing is charts showing the difference in different diff settings on these oc s3s.
What I'm really interested in seeing is charts showing the difference in different diff settings on these oc s3s.
Updating bios helps with efficiency as the firmware is further optimized to get the most out of your ASICs. Furthermore, I have gone through all the tabs when I got my S3, however, the other tabs were so grayed out and I use my 46" TV for a display that is further away I simply didn't see this advanced configuration.
Before Overclocking the unit my average hash rate per day chart showed 450 GHs;
After Overclicking (running only 2x 6 Pin) one of my ASICs chips became inactive (on 250 Freq) and the hashrate became more unstable still marginally better and the chart showed 470 GHs;
Because of this huge variance and instability I decided to give my S3 2 more 6 pins running total of 4x 6 Pin and once again attempted to run it on OC (250 Freq) and the hash rate is significantly better and the ASIC that was inactive before is now back to OK state. I haven't run the unit for a long time but I have been observing the hasrate over the period of 5 minutes and it is stable in between 515 GHs - 570 Ghs. Much much better! Anyone who OC's their S3 needs to run 4 x 6 Pin or otherwise it won't make any sense. OH, and the temps im getting is 40C~~
There was this info about the advanced tab further back in the thread, but that's for the newer machines and people that updated the bios. I have no interest in breaking something that works well, so I'm on the old bios still. I also figured anyone inquiring here about overclocking would have looked all through the miner web login. An oversight on my part.
What I'm really interested in seeing is charts showing the difference in different diff settings on these oc s3s.
What I'm really interested in seeing is charts showing the difference in different diff settings on these oc s3s.
Hey Guys, so for anyone who might have the same problem here is what I have found out from the seller:
"Overclocking these units is no longer done by editing the frequency file; one of the recent firmware upgrades changed that. Now you do it directly through the web interface: go to Miner Configuration screen, and then the 'Advanced' tab. You'll see a dropdown with a bunch of frequency settings that you can pick from. Using all 4 6pin connectors can help with stability"
Surprised nobody here knew this... Anyways that's the solution.
"Overclocking these units is no longer done by editing the frequency file; one of the recent firmware upgrades changed that. Now you do it directly through the web interface: go to Miner Configuration screen, and then the 'Advanced' tab. You'll see a dropdown with a bunch of frequency settings that you can pick from. Using all 4 6pin connectors can help with stability"
Surprised nobody here knew this... Anyways that's the solution.
Yes and Yes. Overclocking generally means more power draw and since the cables are split and come from the same source and each cable can handle only 12V+ and there are three such cables per 6 pins. I will try to plugin independent 6 pins from other cables and see if that will work. I think what the issue is that it is not getting enough power to support OC.
I don't think there is a fallback if there's trouble at 250, should just start beeping, or no fan, if it doesn't work at 250. I would triple-check the edited file. Cables are rated for amperage, that's the real defining part if the cable can handle the miners need. I use a 460w power supply that can supply 38 amps, along with two of it's PCI-e cables, no issues what-so-ever. Cables stay at room temp.
After you triple check the file to edit, from the very top to the very bottom, then cycle the power on the power supply, or unplug and re-plug.
I'll check again when I'm back home. I run 600W with 45 A 12V rail so should be good. Will unplug everything and plug it back in and let you know if it worked.
Yes and Yes. Overclocking generally means more power draw and since the cables are split and come from the same source and each cable can handle only 12V+ and there are three such cables per 6 pins. I will try to plugin independent 6 pins from other cables and see if that will work. I think what the issue is that it is not getting enough power to support OC.
I don't think there is a fallback if there's trouble at 250, should just start beeping, or no fan, if it doesn't work at 250. I would triple-check the edited file. Cables are rated for amperage, that's the real defining part if the cable can handle the miners need. I use a 460w power supply that can supply 38 amps, along with two of it's PCI-e cables, no issues what-so-ever. Cables stay at room temp.
After you triple check the file to edit, from the very top to the very bottom, then cycle the power on the power supply, or unplug and re-plug.
So I changed the frequency file to run at 250 Mhz, rebooted the device and the clock is still sitting at 225 Mhz. I do have 2x 6 pin goin into each group and each of those 6 pin cables splits into two, so I use the splitted ones going into the other two 6 pins. Do you think the reason of why it doesn't go higher than 225 Mhz is because I need to use independent cables going into another 6 pin for this to work?
Things to look for:
Did you actually save the file? Open it back up and check if the edits were kept
Did you put a hashmark in front of the 225MHz three items you are not using? Got to comment those out
You don't need to have all four power connections populated, one from each long side is fine, as long as it supplies the needed power. Sometimes those splitting cables can heat up more than the actual cable from the power supply. I wouldn't split them.
Yes and Yes. Overclocking generally means more power draw and since the cables are split and come from the same source and each cable can handle only 12V+ and there are three such cables per 6 pins. I will try to plugin independent 6 pins from other cables and see if that will work. I think what the issue is that it is not getting enough power to support OC.
So I changed the frequency file to run at 250 Mhz, rebooted the device and the clock is still sitting at 225 Mhz. I do have 2x 6 pin goin into each group and each of those 6 pin cables splits into two, so I use the splitted ones going into the other two 6 pins. Do you think the reason of why it doesn't go higher than 225 Mhz is because I need to use independent cables going into another 6 pin for this to work?
Things to look for:
Did you actually save the file? Open it back up and check if the edits were kept
Did you put a hashmark in front of the 225MHz three items you are not using? Got to comment those out
You don't need to have all four power connections populated, one from each long side is fine, as long as it supplies the needed power. Sometimes those splitting cables can heat up more than the actual cable from the power supply. I wouldn't split them.
So I changed the frequency file to run at 250 Mhz, rebooted the device and the clock is still sitting at 225 Mhz. I do have 2x 6 pin goin into each group and each of those 6 pin cables splits into two, so I use the splitted ones going into the other two 6 pins. Do you think the reason of why it doesn't go higher than 225 Mhz is because I need to use independent cables going into another 6 pin for this to work?
I will note I got the unit secondhand, and not one clue what batch it is. It has been running just great at 250mhz, putting out 503.07 GH/s average for the day. The one issue with the explanation here is !wq did not work with the vi that is on my machine(vim pointed to vi). After escaping from the input mode, ZZ got it saved and exited. I imagine a lot of people could be confused by that.
Replace !wq to ZZ and there's no issues
Replace !wq to ZZ and there's no issues
You wanted wq! not !wq
PS. wq! stands for write then quit by force if needed!
Jump to: