Announcement: Bitmain launches AntMiner solution, 0.68 J/GH on chip

[adqsonline]

Looks like i will be ordering 7 of these upgrades.

 

Not a bad price of about $250 per.

Dont want to put anybody insecure with this but i would rather prefer to sell my Antminer S1 at a lower price and with that money and the money available for the upgrade buy a brand new 1 Antminer S3. Its about to maintain new equipment at home which doesnt mean the upgrade is bad. Is like to buy a brand new super computer or buy the same model with 1 year use.

[Mudbankkeith]

Looks like i will be ordering 7 of these upgrades.

 

Not a bad price of about $250 per.

Dont want to put anybody insecure with this but i would rather prefer to sell my Antminer S1 at a lower price and with that money and the money available for the upgrade buy a brand new 1 Antminer S3. Its about to maintain new equipment at home which doesnt mean the upgrade is bad. Is like to buy a brand new super computer or buy the same model with 1 year use.

in 5 weeks

[jcumins]

the only parts not being replaced are the metal parts that are not likely to wear out to much.  Oh and one fan.

[Mudbankkeith]

If you sell your S1 now, you will get about 0.20BTc for it.
If you keep it till september 20th it will earn 0.20 BTc (from now) less a contribution for electricity.

by 20th september your S1 will be worthless.

nothing to gain and nothing to loose


Bitmain will not be selling anything else before then.


Then you upgrade it for 0.46Btc (it will then be the equivelent of an S3+)

or buy a new S3+ for 0.58 BTc

Make your choice.

[OneCardShy]

a month away till the next batch? The prices would be good if it shipped in the next 2 weeks, but 4 weeks away the network difficulty will be about 30% more than it is today

todays price of 0.66 / 1.30 = 0.51BTC would be a more fair price

S3+ has much more potential to over clock as the PCB design is revised.

Hello Bitmain (via open letter),

What you are posting doesn't make sense. Are you defending the value of the S3+ (above) based upon its ability to be overclocked more reliably, even though to do so would void any warranty and all support as it could possibly destroy the miner?

"It's worth more because it might go faster... but if you try it and it breaks, you get nothing."

(Full disclosure: I have already ordered a pair of S3+'s and plan to run them at stock and to be very happy. My goal is to keep everybody honest and their perspectives clear. You cannot claim a trait for higher value if taking advantage of that trait could destroy the value entirely.)

-OCS

[nreal]

Theres some probs with s3:s - the best share doesnt update it stays 0. Ive got it working once when undercloked, but now even that doesnt help - I need it because mining in p2pool. My two units runs fine with 250mhz - no shares found though in two days? Do these work at all?

Software sources doesnt work as it should, had to modify src/gz barrier_breaker http://downloads.openwrt.org/snapshots/trunk/ar71xx/packages/packages/ to be able to opkg update

to install libncurses had to repalce packages/ with base and then back. all this to be able to install nano..

[grn]

Theres some probs with s3:s - the best share doesnt update it stays 0. Ive got it working once when undercloked, but now even that doesnt help - I need it because mining in p2pool. My two units runs fine with 250mhz - no shares found though in two days? Do these work at all?

Software sources doesnt work as it should, had to modify src/gz barrier_breaker http://downloads.openwrt.org/snapshots/trunk/ar71xx/packages/packages/ to be able to opkg update

to install libncurses had to repalce packages/ with base and then back. all this to be able to install nano..

all mine show best share. not sure why you would need to install additional packages, maybe try to cross compile your own version of openwrt and cgminer

[nreal]

Theres some probs with s3:s - the best share doesnt update it stays 0. Ive got it working once when undercloked, but now even that doesnt help - I need it because mining in p2pool. My two units runs fine with 250mhz - no shares found though in two days? Do these work at all?

Software sources doesnt work as it should, had to modify src/gz barrier_breaker http://downloads.openwrt.org/snapshots/trunk/ar71xx/packages/packages/ to be able to opkg update

to install libncurses had to repalce packages/ with base and then back. all this to be able to install nano..

all mine show best share. not sure why you would need to install additional packages, maybe try to cross compile your own version of openwrt and cgminer

To be able to use nano as editor...for one. Thank you for your help!

[nreal]

Even the uptime doesnt reset when powered of and on again. Is it because of firmware or hardware? Bought 2 of these and both have same faults. If mining with wifi the mining speed display is a mess...

[nreal]

Had to modify with NANO because ive got no time to learn vi the config file /etc/init.d/cgminer

PARAMS="$AOPTIONS $POOL1 $POOL2 $POOL3 $_pb $_ow $_bec --api-listen --api-network --queue 0"

Now it works as expected 

[ELOHIM]

a month away till the next batch? The prices would be good if it shipped in the next 2 weeks, but 4 weeks away the network difficulty will be about 30% more than it is today

todays price of 0.66 / 1.30 = 0.51BTC would be a more fair price

S3+ has much more potential to over clock as the PCB design is revised.

I second that...  (0.51Btc)

[rograz]

by 20th september your S1 will be worthless.

if 100GH/s@1W/GHs is worthless on the 20th of sept then the S3 is almost as worthless as well, might just skip buying hardware altogether then!

[Mudbankkeith]

by 20th september your S1 will be worthless.

if 100GH/s@1W/GHs is worthless on the 20th of sept then the S3 is almost as worthless as well, might just skip buying hardware altogether then!

S1 is 2.22w/Gh       if we have a 30% difficulty increase by 20th Sept, then the S1 will be near it's end.

S3 is 0.80w/Gh       That leaves the S3 (or S1 upgrade) as capable of earning a return until mid December.

[bluecityste]

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 </usr/lib/lua/luci/dispatcher.lua:194>


Any ideas how I can get on to the antminer?? Just reset?

[IYFTech]

I'm copying this from the Bitmain S3 discussion thread in the hope that Bitmain will do the right thing, abide by the law & respect ckolivas request to release their code as stipulated by the Open Source License Agreement:

I do wish the BITMAIN would publish the device driver details so that a current version of cgminer could be attained. I know at least 2 releases in 4 had notes about queue improvements and one at least specifically stated it generated work much faster. Also one of the last 3's had an improvement about how work was loaded into devices. I know for sure 3.12 is very old and I am positive that many work generation improvements have been added since then.

Exactly. I don't understand why they don't work more closely with the cgminer devs - using such an old miner for this equipment is false economy. There have been many improvements & optimixations since this cgminer release, not to mention a very important fix for work redirection by a third party.

Can we just SSH in to it and compile CGMiner to a newer version ?

One would assume that we have access to their modified code and driver for cgminer which the cgminer license stipulates, however they have ignored our requests for making that code available. I am considering what direction to take now about that license violation.

Indeed, I saw your post requesting access to the code - ignoring it seems a very strange course of action by Bitmain, especially since agreeing & cooperating would not only benefit everyone - but would also stay within the legally binding license terms.......

I hope they realize their error & do the right thing - as well as live up to their claim of supporting the Bitcoin community.

@ckolivas: Is there anything we, the community, can do to help? Maybe if we all started mailing them they will take notice?

Hmmmm.......Sorry to quote myself, but the more I think about this - the more it doesn't make any sense. in fact, it smells.

Apart from the obvious legal obligations pointed out by ckolivas, one of the hardest working & well respected Bitcoin community members there is, I find myself wondering why on earth Bitmain won't release their code - are they trying to hide something? I mean, the third party redirect fix was a very important update - why on earth would Bitmain not want to implement it? There are also a multitude of other fixes & improvements which Kano (where is he by the way?) listed in a previous post regarding the S2, but are still relevent:

Because:
1) The version in there throws away valid blocks on p2pool
2) The version in there doesn't block the recent stratum redirect problem
3) The version in there passes all shares to the pool even if they are below target (I'm sure pools must hate the S2 due to the major increase in CPU requirements at the pool)
4) The version in there has the API set to W:0/0 so anyone with network access can change your settings/pool/username (and the web page doesn't let you fix that)
5) The version in there has a modified API with different field names to the standard API so anyone using other software that reads the API must get that software changed (or use a proper API version of cgminer in the S2 )
.
.
.

By not cooperating with the cgminer devs request to release the code as they are legally bound to do - and not updating cgminer to incorporate the very important security fixes, Bitmain are not only breaking the law - but they are also arousing suspicion amongst the Bitcoin community as to why they are refusing to do so. For a company that claims to respect & care deeply for the Bitcoin community, this makes no sense to me whatsoever.

Before anyone starts breaking my balls accusing me of stirring things up trying to discredit Bitmain - I am a customer who has Bitmain hardware & am quite happy with it. I am merely pointing out the legally binding obligations Bitmain are ignoring, as well as trying to highlight the contempt that Bitmain are showing towards ckolivas & kano - without who, mining & Bitcoin would not be what it is today. We, as a community owe it to the cgminer devs to make sure that all hardware manufacturers respect their requests to release their code as stated in the open source license agreement. If they refuse - we should all be concerned as to the reasons why.

Sorry to ramble, but I'm a great believer in Open Source & what the cgminer devs have done, and continue to do. We owe them 

[jk9694]

Can someone tell me the email address to contact bitmain with for technical support.

My batch 3 S3 has been giving me hell all week.  Now the fans don't spin up and the red light just blinks.  No way to access the device or to flash it.

Thanks

[Miasma]

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 </usr/lib/lua/luci/dispatcher.lua:194>


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.

[Miasma]

ANTMINER S3 Batch 7 sales open. 0.66BTC per S3 will be shipped on August 20th, shipping cost included.

I have a dead S3 giving this message. Is there something I can do to fix it  

/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 </usr/lib/lua/luci/dispatcher.lua:194>

This is caused by defective 6-pin power connectors installed in S3s.

[samsonn25]

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 </usr/lib/lua/luci/dispatcher.lua:194>


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.

[cathoderay]

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.

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.