Topic: Announcement: Bitmain launches AntMiner solution, 0.68 J/GH on chip - page 28. (Read 368268 times)
August 19, 2014, 07:41:16 PM
We hope
August 19, 2014, 05:50:08 PM
Bitmain how about a updated flash image for the S1, and s2 , and s3 with the latest cgminor in it.
Cgminer 3.12.0 has been uploaded, https://github.com/bitmaintech/cgminer. The latest version will be updated in 2 weeks.
August 19, 2014, 03:54:58 PM
Bitmain how about a updated flash image for the S1, and s2 , and s3 with the latest cgminor in it.
I would think that would be the best way to insure people with update it.
I would think that would be the best way to insure people with update it.
August 19, 2014, 03:51:57 PM
Any news on the S4?
And by "S4" I mean like an S2, except using the 28nm BM1382 ASICs.
And by "S4" I mean like an S2, except using the 28nm BM1382 ASICs.
August 19, 2014, 06:08:27 AM
WALL OF BOLD & RED
Please don't post formated this ugly, it hurts my eyes. Do you think it looks more important if it is unreadable? You're wrong, it's just ignored by everyone.
Then close your eyes 
August 18, 2014, 06:12:56 AM
Dear Community,
Our truly apologies for the mis-understanding reported in this Support Thread. We are very willing to share the cgminer code to the Community.
Just reviewed our internal resource again, there is a little mis-communicaton between Customer Service Team and R&D Department. We thought this task was done 3 weeks ago..
However, R&D Department is repacking the cgminer code and will upload it to GitHub.com in 3 hours.
Any advice from the Community and Global Customers is appreciated, feel free to contact us via PM or [email protected].
Thank you!
Our truly apologies for the mis-understanding reported in this Support Thread. We are very willing to share the cgminer code to the Community.
Just reviewed our internal resource again, there is a little mis-communicaton between Customer Service Team and R&D Department. We thought this task was done 3 weeks ago..
However, R&D Department is repacking the cgminer code and will upload it to GitHub.com in 3 hours.
Any advice from the Community and Global Customers is appreciated, feel free to contact us via PM or [email protected].
Thank you!
Cgminer 3.12.0 has been uploaded, https://github.com/bitmaintech/cgminer. The latest version will be updated in 2 weeks.
A belated thank you Bitmain - but as mentioned, uploading the code using outdated software with huge security holes is not the wisest solution. Please ensure that all repos (S1, S2, & S3(+)) contain the latest cgminer software that fix the security vulnerabilities - this is very important for both the miner & the network!
Thank you for listening to the community.
August 17, 2014, 11:13:49 PM
Anminer s3 bricked after firmware upgrade.....
a firmware upgrade was performed on my s3 and now it seems to be bricked. no way to login to it in current state. not really sure what protocol seems to be at this point
i have contacted Bitmain several times (on bitcointalk, the bitmain site, and via RMA email) about this issue with no response.
aside from using it as a paperweight, anyone have suggestions on how to fix or get it going once again...is this s3 bricked state even fixable ?
thanks in advance for all input and help.
a firmware upgrade was performed on my s3 and now it seems to be bricked. no way to login to it in current state. not really sure what protocol seems to be at this point
i have contacted Bitmain several times (on bitcointalk, the bitmain site, and via RMA email) about this issue with no response. aside from using it as a paperweight, anyone have suggestions on how to fix or get it going once again...is this s3 bricked state even fixable ?
thanks in advance for all input and help.
Chances are very less to brick. Did you switch the power supply off while the upgrade was happening?
The possibility is that your miner ip reset back to the default 192.168.1.99.
And try with that ip address If that's not working you may possibly have an ip conflict.
Do a factory reset via the small button in front of your S3.
I tried the factory reset on one machine, yet I can't seem to login. I just get the LuCI black screen. Also, there is a yellow and green light above ethernet port. Any ideas?
August 17, 2014, 09:35:57 PM
Dear Community,
Our truly apologies for the mis-understanding reported in this Support Thread. We are very willing to share the cgminer code to the Community.
Just reviewed our internal resource again, there is a little mis-communicaton between Customer Service Team and R&D Department. We thought this task was done 3 weeks ago..
However, R&D Department is repacking the cgminer code and will upload it to GitHub.com in 3 hours.
Any advice from the Community and Global Customers is appreciated, feel free to contact us via PM or [email protected].
Thank you!
Our truly apologies for the mis-understanding reported in this Support Thread. We are very willing to share the cgminer code to the Community.
Just reviewed our internal resource again, there is a little mis-communicaton between Customer Service Team and R&D Department. We thought this task was done 3 weeks ago..
However, R&D Department is repacking the cgminer code and will upload it to GitHub.com in 3 hours.
Any advice from the Community and Global Customers is appreciated, feel free to contact us via PM or [email protected].
Thank you!
Thanks & well done to everyone who helped get this done - power to the Bitcoin Community!
August 17, 2014, 09:31:02 PM
They replied to that request this evening and will be uploading the code to github shortly. ;-)
August 17, 2014, 08:12:39 PM
August 17, 2014, 02:20:51 PM
My batch #3 S3 is totally bricked from what I can tell.
Symptoms:
1. Fans start and immediately stop.
2. Red status indicator only blinks red.
3. Ethernet connection does not start.
Steps taken already.
1. When the shutdowns and non-response started, removed heatsinks, cleaned and replaced with new thermal paste.
2. Switched out power supplies. Same supply works fine on my other batch #5 S3.
3. Checked all connections to the main board.
There were no hashing issues, the device would simply just go completely unresponsive. No connectivity via web or ssh. So I will ask again, how do I contact Bitmain? Is there a support address or just [email protected]? Here soon, all chance of ROI will go out the window.
Symptoms:
1. Fans start and immediately stop.
2. Red status indicator only blinks red.
3. Ethernet connection does not start.
Steps taken already.
1. When the shutdowns and non-response started, removed heatsinks, cleaned and replaced with new thermal paste.
2. Switched out power supplies. Same supply works fine on my other batch #5 S3.
3. Checked all connections to the main board.
There were no hashing issues, the device would simply just go completely unresponsive. No connectivity via web or ssh. So I will ask again, how do I contact Bitmain? Is there a support address or just [email protected]? Here soon, all chance of ROI will go out the window.
August 17, 2014, 01:11:44 PM
Anminer s3 bricked after firmware upgrade.....
a firmware upgrade was performed on my s3 and now it seems to be bricked. no way to login to it in current state. not really sure what protocol seems to be at this point i have contacted Bitmain several times (on bitcointalk, the bitmain site, and via RMA email) about this issue with no response.
aside from using it as a paperweight, anyone have suggestions on how to fix or get it going once again...is this s3 bricked state even fixable ?
thanks in advance for all input and help.
a firmware upgrade was performed on my s3 and now it seems to be bricked. no way to login to it in current state. not really sure what protocol seems to be at this point
i have contacted Bitmain several times (on bitcointalk, the bitmain site, and via RMA email) about this issue with no response. aside from using it as a paperweight, anyone have suggestions on how to fix or get it going once again...is this s3 bricked state even fixable ?
thanks in advance for all input and help.
Chances are very less to brick. Did you switch the power supply off while the upgrade was happening?
The possibility is that your miner ip reset back to the default 192.168.1.99.
And try with that ip address If that's not working you may possibly have an ip conflict.
Do a factory reset via the small button in front of your S3.
I tried the factory reset on one machine, yet I can't seem to login. I just get the LuCI black screen. Also, there is a yellow and green light above ethernet port. Any ideas?
August 17, 2014, 10:44:22 AM
ok BITMAIN I asked privately and now its out...
Look through your email for subject "some extra code doing extra things"
i attached network captures and strange results from our decompiler
The folks at White Hats for Hire, LLC are patiently awaiting an explanation before they release findings
Look through your email for subject "some extra code doing extra things"
i attached network captures and strange results from our decompiler
The folks at White Hats for Hire, LLC are patiently awaiting an explanation before they release findings
Hello peruana,
I would be very interested in seeing this info - would you kindly send me a copy of the email?
Kind regards.
August 17, 2014, 08:55:38 AM
Hi BITMAIN.
As you're an official representative of bitmain, may I ask you to please provide the source code for your modifications to cgminer in the form of the driver for the S3. cgminer is provided under the GPL version 3 license which means you are obliged by law to provide the source code to any modifications you do if you distribute binaries and you are distributing modified cgminer binaries with every S3.
Provision of the source code would allow us to aid the development of your driver and help bring your version to sync up with the latest cgminer to derive the benefits of newer versions along with its many fixes.
As you're an official representative of bitmain, may I ask you to please provide the source code for your modifications to cgminer in the form of the driver for the S3. cgminer is provided under the GPL version 3 license which means you are obliged by law to provide the source code to any modifications you do if you distribute binaries and you are distributing modified cgminer binaries with every S3.
Provision of the source code would allow us to aid the development of your driver and help bring your version to sync up with the latest cgminer to derive the benefits of newer versions along with its many fixes.
Bumping this
BITMAIN - A couple questions please:
1) Why do you continue to ignore the request by the cgminer developers to release your code as you are morally & legally required to do so under the GPLv3 License Agreement?
2) The cgminer software that you are deploying ILLEGALLY with your software has SEVERE security flaws, including the stratum redirect issue - why are you NOT implementing the latest version to eliminate these issues?
These and other questions have been asked many times by many people across this forum, but you continue to ignore them, refusing to even comment, and by doing so you are not only breaking the law, but you are also demonstrating massive contempt towards the cgminer developers & the Open Source Community as well as creating suspicion as to your reasons/motives within the Bitcoin Community.
Until you decide to capitulate & do the honorable & legally binding - and above all, the RIGHT thing - I and others on this forum will continue to pursue a response/reply to the above questions.
I urge everyone on this forum to do the same, not only out of respect & gratitude to the cgminer developers who have given so much to the Bitcoin community FOR FREE under the GPLv3 Licensing Terms, but also to ensure the security of your own extremely vulnerable mining equipment purchased from Bitmain.
Thank you.
Excellent!!
@ Bitmain - this absolutely needs to be addressed ASAP!!
August 17, 2014, 08:47:40 AM
WALL OF BOLD & RED
Please don't post formated this ugly, it hurts my eyes. Do you think it looks more important if it is unreadable? You're wrong, it's just ignored by everyone.
Would you prefer Pink?
Sorry if it hurts your eyes, but it is the message that is important, not the "look" of it......
August 17, 2014, 08:41:15 AM
Hi BITMAIN.
As you're an official representative of bitmain, may I ask you to please provide the source code for your modifications to cgminer in the form of the driver for the S3. cgminer is provided under the GPL version 3 license which means you are obliged by law to provide the source code to any modifications you do if you distribute binaries and you are distributing modified cgminer binaries with every S3.
Provision of the source code would allow us to aid the development of your driver and help bring your version to sync up with the latest cgminer to derive the benefits of newer versions along with its many fixes.
As you're an official representative of bitmain, may I ask you to please provide the source code for your modifications to cgminer in the form of the driver for the S3. cgminer is provided under the GPL version 3 license which means you are obliged by law to provide the source code to any modifications you do if you distribute binaries and you are distributing modified cgminer binaries with every S3.
Provision of the source code would allow us to aid the development of your driver and help bring your version to sync up with the latest cgminer to derive the benefits of newer versions along with its many fixes.
Bumping this
BITMAIN - A couple questions please:
1) Why do you continue to ignore the request by the cgminer developers to release your code as you are morally & legally required to do so under the GPLv3 License Agreement?
2) The cgminer software that you are deploying ILLEGALLY with your software has SEVERE security flaws, including the stratum redirect issue - why are you NOT implementing the latest version to eliminate these issues?
These and other questions have been asked many times by many people across this forum, but you continue to ignore them, refusing to even comment, and by doing so you are not only breaking the law, but you are also demonstrating massive contempt towards the cgminer developers & the Open Source Community as well as creating suspicion as to your reasons/motives within the Bitcoin Community.
Until you decide to capitulate & do the honorable & legally binding - and above all, the RIGHT thing - I and others on this forum will continue to pursue a response/reply to the above questions.
I urge everyone on this forum to do the same, not only out of respect & gratitude to the cgminer developers who have given so much to the Bitcoin community FOR FREE under the GPLv3 Licensing Terms, but also to ensure the security of your own extremely vulnerable mining equipment purchased from Bitmain.
Thank you.
+1 I support this sentiment completely
August 17, 2014, 08:39:31 AM
WALL OF BOLD & RED
Please don't post formated this ugly, it hurts my eyes. Do you think it looks more important if it is unreadable? You're wrong, it's just ignored by everyone.
Actually, I think it's an excellent post & for all the right reasons. I'm sure it is designed to catch Bitmains eye, and the fact that you commented on it means that it worked. It is a very important message & complaining about the look of it seems a little strange, tbh. Hopefully more people will also comment & show their support for the cgminer devs as opposed to how "pretty" it looks........
August 17, 2014, 08:30:28 AM
WALL OF BOLD & RED
Please don't post formated this ugly, it hurts my eyes. Do you think it looks more important if it is unreadable? You're wrong, it's just ignored by everyone.
August 17, 2014, 07:35:48 AM
Hi BITMAIN.
As you're an official representative of bitmain, may I ask you to please provide the source code for your modifications to cgminer in the form of the driver for the S3. cgminer is provided under the GPL version 3 license which means you are obliged by law to provide the source code to any modifications you do if you distribute binaries and you are distributing modified cgminer binaries with every S3.
Provision of the source code would allow us to aid the development of your driver and help bring your version to sync up with the latest cgminer to derive the benefits of newer versions along with its many fixes.
As you're an official representative of bitmain, may I ask you to please provide the source code for your modifications to cgminer in the form of the driver for the S3. cgminer is provided under the GPL version 3 license which means you are obliged by law to provide the source code to any modifications you do if you distribute binaries and you are distributing modified cgminer binaries with every S3.
Provision of the source code would allow us to aid the development of your driver and help bring your version to sync up with the latest cgminer to derive the benefits of newer versions along with its many fixes.
Bumping this
BITMAIN - A couple questions please:
1) Why do you continue to ignore the request by the cgminer developers to release your code as you are morally & legally required to do so under the GPLv3 License Agreement?
2) The cgminer software that you are deploying ILLEGALLY with your software has SEVERE security flaws, including the stratum redirect issue - why are you NOT implementing the latest version to eliminate these issues?
These and other questions have been asked many times by many people across this forum, but you continue to ignore them, refusing to even comment, and by doing so you are not only breaking the law, but you are also demonstrating massive contempt towards the cgminer developers & the Open Source Community as well as creating suspicion as to your reasons/motives within the Bitcoin Community.
Until you decide to capitulate & do the honorable & legally binding - and above all, the RIGHT thing - I and others on this forum will continue to pursue a response/reply to the above questions.
I urge everyone on this forum to do the same, not only out of respect & gratitude to the cgminer developers who have given so much to the Bitcoin community FOR FREE under the GPLv3 Licensing Terms, but also to ensure the security of your own extremely vulnerable mining equipment purchased from Bitmain.
Thank you.
August 16, 2014, 10:18:12 PM
Help please, my S3 is hashing away at bitminter but when I try to login to the antminer user interface it comes up with the following:
usr/lib/lua/luci/dispatcher.lua:448: Failed to execute function dispatcher target for entry '/'.
The called action terminated with an exception:
/usr/lib/lua/luci/sauth.lua:87: Session data invalid!
stack traceback:
[C]: in function 'assert'
/usr/lib/lua/luci/dispatcher.lua:448: in function 'dispatch'
/usr/lib/lua/luci/dispatcher.lua:195: in function
Any ideas how I can get on to the antminer?? Just reset?
usr/lib/lua/luci/dispatcher.lua:448: Failed to execute function dispatcher target for entry '/'.
The called action terminated with an exception:
/usr/lib/lua/luci/sauth.lua:87: Session data invalid!
stack traceback:
[C]: in function 'assert'
/usr/lib/lua/luci/dispatcher.lua:448: in function 'dispatch'
/usr/lib/lua/luci/dispatcher.lua:195: in function
Any ideas how I can get on to the antminer?? Just reset?
The problem is that some 6-pin PCIe connectors on your S3 are defective. You need to either move your PSU cables to the second connector on each board or add two more PCIe connectors so you have 4 per S3.
Supposedly they only have 1 6pin pcie connector to power a (400-430 watt) KNC Neptune-lmao
But yes 2 pcie connectors is better per s3 blade is better than 1.
Jump to: