Anyone know if you can get the fans to sync?
Doesn't make sense in a push/pull config to have one fan running at a different speed than the other.
Topic: ANTMINER S3+ Discussion and Support Thread - page 141. (Read 710164 times)
To clarify:
1) Download the updated firmware from: https://bitmaintech.com/support.htm?pid=007201407180243004432lBQW28O0633
2) SSH/Putty into S3
3) Paste the code in below.. Will replace Save&Apply with Save&Apply.
1) Download the updated firmware from: https://bitmaintech.com/support.htm?pid=007201407180243004432lBQW28O0633
2) SSH/Putty into S3
3) Paste the code in below.. Will replace Save&Apply with Save&Apply.
Code:
sed -i 's/Save\&Apply/Save\&Apply/g' /usr/lib/lua/luci/model/cbi/cgminer/cgminer.lua
4) Execute the following codeCode:
/etc/init.d/cgminer restart
This worked great but i like the boot strap skin now that i found it, i may just keep that view.
@toptek
Unless you have fan pointing on S3, removing the cover may do more harm than good. Point of cover is to force air through heatsink fins.
Unless you have fan pointing on S3, removing the cover may do more harm than good. Point of cover is to force air through heatsink fins.
HW still too high... How can I lower those?
S3 ? set it to defaults for while see if its a OC issue , is it heating up if so remove the cover for a while to see if open air helps . make sure both fan are turning .I have a upgraded S3 i upgraded that runs better then the S3 i bought from butmain all most no hard ware error with the upgrade .I may just pull the boards on the S3 and re paste them its my Second S3, first one just stopped working they replaced it no questions asked .
@aclass
Reduce frequency or possibly change PSU.
How high is too high?
Reduce frequency or possibly change PSU.
How high is too high?
HW still too high... How can I lower those?
@nst6563
Would love to know if the voltage change works.
Would love to know if the voltage change works.
@cloh76
No difference between S3 and S3+.
All settings should be retained during FW upgrade unless you unchecked the "Retain Settings" option.
No difference between S3 and S3+.
All settings should be retained during FW upgrade unless you unchecked the "Retain Settings" option.
To clarify:
1) Download the updated firmware from: https://bitmaintech.com/support.htm?pid=007201407180243004432lBQW28O0633
2) SSH/Putty into S3
3) Paste the code in below.. Will replace Save&Apply with Save&Apply.
1) Download the updated firmware from: https://bitmaintech.com/support.htm?pid=007201407180243004432lBQW28O0633
2) SSH/Putty into S3
3) Paste the code in below.. Will replace Save&Apply with Save&Apply.
Code:
sed -i 's/Save\&Apply/Save\&Apply/g' /usr/lib/lua/luci/model/cbi/cgminer/cgminer.lua
4) Execute the following codeCode:
/etc/init.d/cgminer restart
As promised, quicker way to fix config page issue
1)Putty into S3
2)Paste the code in below.. Will replace Save&Apply with Save&Apply.
1)Putty into S3
2)Paste the code in below.. Will replace Save&Apply with Save&Apply.
Code:
sed -i 's/Save\&Apply/Save\&Apply/g' /usr/lib/lua/luci/model/cbi/cgminer/cgminer.lua
Thanks Ustler - Just to clarify...
1) Download the updated firmware from: https://bitmaintech.com/support.htm?pid=007201407180243004432lBQW28O0633
2) Putty into S3
3) Paste the code in below.. Will replace Save&Apply with Save&Apply.
Code:
sed -i 's/Save\&Apply/Save\&Apply/g' /usr/lib/lua/luci/model/cbi/cgminer/cgminer.lua
4)Reboot
a) cd /usr/bin
b) /etc/init.d/cgminer restart
Do i need to re-apply or change any settings if flashing an S3+; Is it different from a standard S3?
Where did HW go? I can't find it in the new firmware
Naaah: Found it below all the pool lines
Naaah: Found it below all the pool lines
@nst6563:
S4 documentation details voltage field.
Probably correlates to bitmain-voltage option that can be seen in cgminer help
S4 documentation details voltage field.
Probably correlates to bitmain-voltage option that can be seen in cgminer help
Code:
cgminer --help | grep voltage
Ah yes...thanks. Looks like settings 072 would give you 0.72v, and 082 would give .82v.
I have an s3 that won't do much over 420ghs....I might give it a shot on that one.
@nst6563:
S4 documentation details voltage field.
Probably correlates to bitmain-voltage option that can be seen in cgminer help
S4 documentation details voltage field.
Probably correlates to bitmain-voltage option that can be seen in cgminer help
Code:
cgminer --help | grep voltage
As promised, quicker way to fix config page issue
1)Putty into S3
2)Paste the code in below.. Will replace Save&Apply with Save&Apply.
1)Putty into S3
2)Paste the code in below.. Will replace Save&Apply with Save&Apply.
Code:
sed -i 's/Save\&Apply/Save\&Apply/g' /usr/lib/lua/luci/model/cbi/cgminer/cgminer.lua
Thanks for this. Just updated one of my Batch 1 S3s, applied the line above and everything works great!
One question, what values would/should/could be entered in that new 'Voltage' field for the S3? And what effect would these values have on the operation?
From digging around on the bitmain github and also opening the cgminer binary and checking things out, it looks like it takes a hex value. According to the datasheet the 'max voltage' is 1.2v. So there's plenty of headroom to mess around with if they come default at .7v (which would be something like 0x07 I imagine....I didn't find a solid example in any of the code).
@BennyTheBall:
I have no idea with the values for voltage.. I wouldn't mess with the field without Bitmain commenting.
Edit: Was incorrect about my speculation regarding the C1.. The voltage value can be seen in the S4 manual on page 5
https://bitmaintech.com/files/download/Antminer%20S4%20Manual_EN_2014.9.29.pdf
Bitmain probably never intended the voltage to show up on S3's
I have no idea with the values for voltage.. I wouldn't mess with the field without Bitmain commenting.
Edit: Was incorrect about my speculation regarding the C1.. The voltage value can be seen in the S4 manual on page 5
https://bitmaintech.com/files/download/Antminer%20S4%20Manual_EN_2014.9.29.pdf
Bitmain probably never intended the voltage to show up on S3's
As promised, quicker way to fix config page issue
1)Putty into S3
2)Paste the code in below.. Will replace Save&Apply with Save&Apply.
1)Putty into S3
2)Paste the code in below.. Will replace Save&Apply with Save&Apply.
Code:
sed -i 's/Save\&Apply/Save\&Apply/g' /usr/lib/lua/luci/model/cbi/cgminer/cgminer.lua
Thanks for this. Just updated one of my Batch 1 S3s, applied the line above and everything works great!
One question, what values would/should/could be entered in that new 'Voltage' field for the S3? And what effect would these values have on the operation?
It is also read correctly by AntMonitor.
I have the same question about the Voltage field - does it apply to S3 or is it in the same category as the support for 2 extra 'phantom' fans?
Cheers
As promised, quicker way to fix config page issue
1)Putty into S3
2)Paste the code in below.. Will replace Save&Apply with Save&Apply.
1)Putty into S3
2)Paste the code in below.. Will replace Save&Apply with Save&Apply.
Code:
sed -i 's/Save\&Apply/Save\&Apply/g' /usr/lib/lua/luci/model/cbi/cgminer/cgminer.lua
Thanks for this. Just updated one of my Batch 1 S3s, applied the line above and everything works great!
One question, what values would/should/could be entered in that new 'Voltage' field for the S3? And what effect would these values have on the operation?
As promised, quicker way to fix config page issue
1)Putty into S3
2)Paste the code in below.. Will replace Save&Apply with Save&Apply.
1)Putty into S3
2)Paste the code in below.. Will replace Save&Apply with Save&Apply.
Code:
sed -i 's/Save\&Apply/Save\&Apply/g' /usr/lib/lua/luci/model/cbi/cgminer/cgminer.lua
Mine ain't broke so I ain't fixin 'em.
I've noticed with this firmware that if I change the --queue setting at all, cgminer won't start, meaning I'm stuck with the ridiculously high standard setting. I'll try wget ck's update on top of this firmware to see if that will let me change the queue setting - otherwise I'll go back to the older firmware I reckon.
There is no excuse for not testing firmware thoroughly, none at all......
There is no excuse for not testing firmware thoroughly, none at all......
Jump to: