ANTMINER S3+ Discussion and Support Thread

[pekatete]

Or he could have a DNS clash.

Turns out he had the former .... simply setting DHCP on the active connection.
Saying that, what does a DNS clash look like?

[hurricandave]

Or he could have a DNS clash.

Turns out he had the former .... simply setting DHCP on the active connection.
Saying that, what does a DNS clash look like?

Wow that's really weird, my post most of hung up for a while before updating to the thread. Anyhow, the DNS clash puts out about the same output as a failed connection, it keeps trying and gets shot down.

[sieve66]

While you're at it, update firmware to 20141219, its a critical update. Download is /s01YJK]here.

Ignore him! If it ain't broke, don't fix it!
The only thing you'd need to update with the Aug firmware is cgminer, not the firmware else you run the risk of bricking your rig, even worse, installing dodgy firmware (of which there are loads for the S3 variants)!

Yup, that sounds pretty sensible to me. I have them working so really I wont touch them  until I understand better what I am doing.

[dogie]

While you're at it, update firmware to 20141219, its a critical update. Download is here.

Ignore him! If it ain't broke, don't fix it!
The only thing you'd need to update with the Aug firmware is cgminer, not the firmware else you run the risk of bricking your rig, even worse, installing dodgy firmware (of which there are loads for the S3 variants)!

I am a representative of Bitmain. Absolutely upgrade to 12/19, it is the most stable of all S3 firmwares and fixes a critical bug.

[pekatete]

I am a representative of Bitmain. Absolutely upgrade to 12/19, it is the most stable of all S3 firmwares and fixes a critical bug.

That is bitmain's flaw to have you as a representative if they actually do. Saying that, I've never seen bitmain refer to you as their representative anywhere.

In any case, you should know that it is adequate to simply update cgminer in the Aug firmware as the reset button (your favourite excuse) works well. Just the stratum bug that was fixed in cgminer 4.6.1 needs to be corrected in the Aug firmware, but you did not even ask the OP to check for cgminer version before suggesting your firmware update (for all we know, his unit may have an updated cgminer from the previous owner!).

EDIT: And why do you insist on posting links to your firmware updates rather than refer people to the bitmain site? Does that link contain your own edited firmware where you've introduced suttle bugs to steal hash-rate or some other sinister stuff under the cover of a bitmain representative?

[dogie]

I am a representative of Bitmain. Absolutely upgrade to 12/19, it is the most stable of all S3 firmwares and fixes a critical bug.

That is bitmain's flaw to have you as a representative if they actually do. Saying that, I've never seen bitmain refer to you as their representative anywhere.

In any case, you should know that it is adequate to simply update cgminer in the Aug firmware as the reset button (your favourite excuse) works well. Just the stratum bug that was fixed in cgminer 4.6.1 needs to be corrected in the Aug firmware, but you did not even ask the OP to check for cgminer version before suggesting your firmware update (for all we know, his unit may have an updated cgminer from the previous owner!).

EDIT: And why do you insist on posting links to your firmware updates rather than refer people to the bitmain site? Does that link contain your own edited firmware where you've introduced suttle bugs to steal hash-rate or some other sinister stuff under the cover of a bitmain representative?

Because 12/19 is no longer hosted on bitmaintech, you can verify the MD5 is identical. Please take any scam accusations to the scam accusation subforum as its off topic here.

[pekatete]

I am a representative of Bitmain. Absolutely upgrade to 12/19, it is the most stable of all S3 firmwares and fixes a critical bug.

That is bitmain's flaw to have you as a representative if they actually do. Saying that, I've never seen bitmain refer to you as their representative anywhere.

In any case, you should know that it is adequate to simply update cgminer in the Aug firmware as the reset button (your favourite excuse) works well. Just the stratum bug that was fixed in cgminer 4.6.1 needs to be corrected in the Aug firmware, but you did not even ask the OP to check for cgminer version before suggesting your firmware update (for all we know, his unit may have an updated cgminer from the previous owner!).

EDIT: And why do you insist on posting links to your firmware updates rather than refer people to the bitmain site? Does that link contain your own edited firmware where you've introduced suttle bugs to steal hash-rate or some other sinister stuff under the cover of a bitmain representative?

Because 12/19 is no longer hosted on bitmaintech, you can verify the MD5 is identical. Please take any scam accusations to the scam accusation subforum as its off topic here.

If it is no longer hosted by bitmain, then anyone in their right mind should never install it as it is junk firmware and will surely invalidate any warranty they may have. It is well documented, and been brought to your attention several times, that the firmware you refer people to causes all sorts of problems but you refuse to take any notice of it.

The most recent person you tried to ram your firmware up clearly has a pre-S3+ rig, i.e Aug firmware, and those particular units have been known to have a decayed performance with the latter firmware releases, but you still jumped at the opportunity to refer them to your special upgrade .... how daft is that?

If you think I am making any un-reasonable accusations, feel free to open a scam accusation thread against me. And your private firmware updates aree the off-topic ones in as far as this thread is concerned! All firmware upgrades SHOULD be downloaded from the bitmain site, not from your stash of compromised firmwares. How bitmain let you potentialy tarnish their image beggars the question, are you their hatchet man? Fortunately, this is not a bitmain forum.

[dogie]

If it is no longer hosted by bitmain, then anyone in their right mind should never install it as it is junk firmware and will surely invalidate any warranty they may have.

That's not true.

It is well documented, and been brought to your attention several times, that the firmware you refer people to causes all sorts of problems but you refuse to take any notice of it.

That's not true. 12/19 is possibly the most stable and bug free firmware of any version ever, across all PCB versions.

The most recent person you tried to ram your firmware up clearly has a pre-S3+ rig, i.e Aug firmware, and those particular units have been known to have a decayed performance with the latter firmware releases

That's not true.

And your private firmware updates aree the off-topic ones in as far as this thread is concerned!

That's not true and doesn't even make sense.


I really don't want to be arguing with you but I have to correct incorrect or misleading statements you make to customers, as you're neither the one who will end up with a bricked unit nor has to help those customers. You seem incessant on going against everything I'm saying - because I'm the one saying it. If you really don't agree with what I'm saying then simply ignore me.

[pekatete]

I really don't want to be arguing with you but I have to correct incorrect or misleading statements you make to customers, as you're neither the one who will end up with a bricked unit nor has to help those customers. You seem incessant on going against everything I'm saying - because I'm the one saying it. If you really don't agree with what I'm saying then simply ignore me.

I am not interested in arguig with or shadowing you, but I shall always point out the misleading information you give out under the pretext of being a bitmain representative. And the ball is in your court here, if you do not want to be challenged, stop giving false advice to bitmain customers (of whom I am). And if you do not know the answer, let others who know answer!

Your self-annointed bitmain representative badge neither confers nor imparts any knowledge unto you to shadow any and every comment on a bitmain instigated thread to the extent of you pretending to be an authority on all things bitmain. That much I know from your numerous waffle responses and the patently wrong advice that you keep giving.

EDIT: If bitmain have scrapped a firmware release, why do you keep telling people to install that release? Will you recompense them if their rigs (which may be out of warranty) malfunction? Or will it be a case of you can not help since warranty period has expired? Do you ever give thought to that you twat?

[Stratobitz]

What is the simple under 50 Word Lowdown on why the 121914 Firmware is 'Critical'?

Strato

[pekatete]

What is the simple under 50 Word Lowdown on why the 121914 Firmware is 'Critical'?

Strato

Simplest answer is do not flash the 12192014 firmware because along with a raft of S3 firmware releases during that period, that version was scrapped by bitmain (after testing in general release) as being buggy. Proof of the pudding .... check the bitmain website, its no longer officially available / supported.

[Stratobitz]

What is the simple under 50 Word Lowdown on why the 121914 Firmware is 'Critical'?

Strato

Simplest answer is do not flash the 12192014 firmware because along with a raft of S3 firmware releases during that period, that version was scrapped by bitmain (after testing in general release) as being buggy. Proof of the pudding .... check the bitmain website, its no longer officially available / supported.

Ok Thanks. I appreciate the cut and dry info. My Miners are all running fine. So thats good.

Cheers!

Strato

[aarons6]

What is the simple under 50 Word Lowdown on why the 121914 Firmware is 'Critical'?

Strato

Simplest answer is do not flash the 12192014 firmware because along with a raft of S3 firmware releases during that period, that version was scrapped by bitmain (after testing in general release) as being buggy. Proof of the pudding .... check the bitmain website, its no longer officially available / supported.

the reason they scrapped this firmware is because the newer one soon after removed the voltage adjustment.

on my s3s, the 10/24 and the 12/19 have identical results, they both are really stable, low HWE and no reboots or X's.. the newer one on their website 1/9/2015 has a ton of HWE and i get random X's and reboots..

i do believe my s3s are the ones that dont have auto adjusted voltage.

[marvykkio]

the latest firmware 9.1.2015 has a ton of errors HW, it is true that for more hash for too many mistakes, and seeing the site bitmain think it is no longer updated, and just my guess

[Rabinovitch]

Has anyone else tried this antMiner_S320150109.bin?

[Pautado]

For MY s3 the best firmware is 10/24 it is the one that gets me higher hashrates and the most stable. And yes, I know about the not working reset button and I really don't care about it... If anything goes wrong I can always flash it by serial/jtag...

Has anyone else tried this antMiner_S320150109.bin?

Yes it sucks... Isn't stable at all...

[marvykkio]

Has anyone else tried this antMiner_S320150109.bin?

you I have tried the latest firmware, but makes tons of mistakes

[sloopy]

Has anyone else tried this antMiner_S320150109.bin?

In my experience the 01-09 is Crap Firmware. Things were so bad I may not have waited long enough to prove with data 10-24 works better. So, I will.


To further Pekatete's assertions regarding firmware...
Take a look at his overclocking threads and if you want, look through his post history.
If I was unable to roll back and forth between firmware revisions and test on my own I would still give a ton of credibility from his documented test results alone.

I am not saying I don't use dogie's information. I place people in context and use them for their strengths based in my experience.
pekatete knows more about the S3 firmware than probably anyone currently posting, and if someone else claims to be a better authority they should compliment their claims with the who, why, when, and how to back it up.
Model, hashrates over time, temps, frequencies, voltages, etc
That is for anyone making claims about this or that firmware, tell me all the details.

Dogie is a subcontractor for bitmain to provide support to customers on this forum. Dogie knows things and has provided great guides for n00bz which also includes reference material for everyone. While technically not an employee, him being a sub does suggest access to engineering information, or at least knowing who to ask the right questions but again, the same matters to me, employee or not, how did you arrive at the claim you make regarding S3 firmware?  To me, the reset button issue alone is not enough of a reason to upgrade. I experienced other issues. I see effects in work submitted in my own testing between those versions. I did not simply test one unit for a couple of hours. I ran several days with multiple units. I plan to do so again, and include the latest build from 01-09 in the tests. I will run each firmware version, 10-24, 12-19, and 01-09 for x amount of time on each S3. My mix of units spans from old S3 batches to much newer S3+.

I enjoy this type of process and if there is other information anyone wants just ask. While I have not been here long I have been doing things such as this for a long time, and appreciate any input from anyone, but most value the input with explanations of how someone arrives there.

[ZymurBits]

Got a chip down and need to take the blade & heat sync off and regrease it up again but can anyone quickly tell me which blade one I'm looking for?  Asic Status is telling me this:

00000000  00000000
00000000  000-0000

Thanks!

[ZymurBits]

Just to throw my 2 cents in on all the firmware bickering that's been going on.  I've tried both 10.24 and 12.19 on my S3 and S3+ rigs (solely for the cgminer update).  Ended up going back to the 10.24 image on all of them because some (not all) would loose hash over time.  Don't want to get in a fight with anyone about it but something other than the "reset" fix was in that image.  Since my rigs are all stable now, I'm not risking another botched upgrade.  To echo many previous sentiments - If it ain't broke, don't fix it.