Bitmain's Released Antminer S9, World's First 16nm Miner Ready to Order

[ComputerGenie]

...Really pissed off at Bitmain. Just when I think they can't get any scummier, they find a way.

And they did exactly what to you?  

Caused my stash to be worth a few hundred thousand less than it was a few days ago over all this Bitcoin Unlimited/Antpool bullshit.

Ignoring that most will doubt you actually have over 1KBTC, sweating a 24% correction drop after a 270+% gain in the last 9 months suggests that Bitcoin (or any crypto, for that matter) might not be a good fit for you.

[ComputerGenie]

...not planning to do anything with my stash until at least 2020...

So, in other words, you've lost nothing (because current value has nothing to do with the value 3 years from now), you're merely venting because you're on the bandwagon of segwit lemmings and Bitmain isn't, and you want Bitcoin to be further centralized around Core. Got it!

[ComputerGenie]

segwit lemmings

Ah, so you're clearly a Roger Ver felater.

Got it.

There's 2 types of segwit people:
1) those that think it's a good idea
2) those that belong to the cult that think it's the next Saviour.

You're obviously a FUD spewing troll that belongs to the 2nd group.   

I'm neither a fan nor a follower of Ver, unlike you I make up my own mind. Now be a good little lemming and go spread your FUD on Redshit or Twatter...

[ComputerGenie]

What FUD ? You've made up your mind about supporting Bitcoin Unlimited - A closed-source cryptocurrency with laughable code-quality.

You deserve to be mocked mercilessly.

1) I like that you falsely assume that because I don't support A that I must support B (ignoring the fact that I may support C, D, or E instead).
2) If miners choose to mine on Bitmain's pool (signalling their support for BU), that has nothing to do with the product this thread is about.
3) Up to this point, Core devs support what Core devs want/like/believe and the community can be damned. When Core supports BIPs that the majority of the community wants (even though Core devs personally don't like them), then you might have some valid ground to stand on throwing rocks at Bitmain because they don't support the wants of the Core devs.

[ComputerGenie]

1) I like that you falsely assume...

Just like you falsely assumed I was lying about the estimated HODLINGS in my BTC stash ?

Yeah, fuck off already. You're likely a mEth-head...

Yes, you're right, because I am, in fact, "most" people on here.

...most will doubt...

[HagssFIN]

There use to be such high demand for manual control ability with autotune S9 models, but now, has someone tried my method with S9?
I've done this successfully to my two R4s.

This is also S9 related, so I thought to share this here as well.
If there is someone with a desire for non-autotune settings, be brave and please report if you get same results as I had  

Originally posted in the R4 thread https://bitcointalk.org/index.php?topic=1597639.msg18267781#msg18267781

Well, this is an interesting find and I thought I'll share it with you.

I had a problem booting my Antminer R4 8.0 Th/s, batch 2, autotune-model.

So I went looking in here:
Bitmain.com: Three Ways to Restore Factory Settings (R4/S9/T9)
https://enforum.bitmain.com/bbs/topics/3957

I used the last option in the list, IP Reporter button restore.

Usage: Please power off the miner, then hold down the IP Reporter and don’t release it. At the same time, please power on the miner.
Releasing the IP Reporter after 5 seconds, the machine will automatically restore factory settings.

My miner restored with firmware Aug. 9 2016 and autotune settings were gone.
I am now suddenly able to control frequency and custom fan settings.  

This was not my original problem, but I'm happy with it.
My original problem was that the miner jammed somehow in the booting process and didn't even show up in my router ip list.

[NotFuzzyWarm]

My latest s9 just arrived via UPS. Came up just fine and running 13.6TH/s.
Now just gotta hope that it continues to do so...

Und no - I am not about to risk one of my auto-tune s9's with the reset trick....

[HagssFIN]

There is nothing to risk when you really think about it in software level.
And I have tested it two times.
It takes an original (older) firmware for both the controller and hash board PIC.

R4 and S9 have the same controller and pretty much the same software.

[elokk]

Hey, Bitmain.

How does it feel being the most hated entity in Bitcoinia right now, over your BU bullshit ?

Go choke on your own greed, fuckers.

Yeah, how dare they not support further centralizing Bitcoin around the wants of the Core devs? What are these people thinking? After all, what is the point of a decentralized coin and freedom of choice when Core devs can make all of the decisions for everyone?

Core updates code with new releases, nodes are not required to upgrade

[ComputerGenie]

Core updates code with new releases, nodes are not required to upgrade

Q: And the version of Core that is up-to-date and allows you to not signal in favor of segwit is where? 
A: Nowhere, because no such creature exists.

Q: And the version of Core that is up-to-date and allows you to signal in favor of a BIP that Core devs are not in favor of is where? 
A: Nowhere, because no such creature exists.

[fanatic26]

Q: And the version of Core that is up-to-date and allows you to not signal in favor of segwit is where? 
A: Nowhere, because no such creature exists.

Q: And the version of Core that is up-to-date and allows you to signal in favor of a BIP that Core devs are not in favor of is where? 
A: Nowhere, because no such creature exists.

How dare you point out flaws in the almighty CORE OVERLORDS. Shouldnt you just read /r/bitcoin and follow all the sheep there in blindly laying blame on random people rather than objectively looking at the facts? Pretty sure thats how most of the community works these days lol

[fanatic26]

There use to be such high demand for manual control ability with autotune S9 models, but now, has someone tried my method with S9?
I've done this successfully to my two R4s.

I have a couple misbehaving S9s that I wouldnt mind trying this on. If I get time later this week to try it I will report back on what I find. I have a couple batches of autotunes I can try this on.

[elokk]

Core updates code with new releases, nodes are not required to upgrade

Q: And the version of Core that is up-to-date and allows you to not signal in favor of segwit is where? 
A: Nowhere, because no such creature exists.

Q: And the version of Core that is up-to-date and allows you to signal in favor of a BIP that Core devs are not in favor of is where? 
A: Nowhere, because no such creature exists.

You are free to run whatever client you wish or support a different chain. Nobody is forcing you to use Core. However, the best and most competent developers contribute  and maintain code to the core client. You are free to open a Git and submit proposals if know of a beneficial feature that is not currently available.

If you do not support segwit, run versions prior to 0.13.1, that is if you run a node.

Being that this is the Antminer s9 thread, we should get back on topic:

After speaking with a Bitmain representative in regards to the issues with their 16nm products, I would highly recommend using a hosting service. Things as little as a power outage, lost internet connection, etc can cause asics to burn which may not even be detectable by a quick visual inspection. Obviously, a hosting company is not immune from these service interruptions but should be setup with fail-overs. All of my s9 & r4 repairs were burned asics. I never had one case of burned asic on prior Bitmain products (s1, s3, s5, s7)

[ComputerGenie]

You are free to run whatever client you wish or support a different chain. Nobody is forcing you to use Core. However, the best and most competent developers contribute  and maintain code to the core client. You are free to open a Git and submit proposals if know of a beneficial feature that is not currently available.

If you do not support segwit, run versions prior to 0.13.1, that is if you run a node.
...

Yes, it is wholly true that if you want to run a Core node, you are free to not support segwit by running an older, less optimized version of Core that is worse for the network as a whole.
Meanwhile in the decentralized world where Bitcoin is supposed to be run by a consensus, if the majority want x in a wallet, then Core devs should put x in the wallet. In the decentralized world where Bitcoin is supposed to be run by a consensus, one shouldn't have to make the choice between a client that is, literally, slower and one that signals something that the majority obviously don't want.

"You are free to open a Git and submit proposals if know of a beneficial feature that is not currently available." Satoshi Nakamoto, himself, could write a BIP that 99% of the community wants and if the devs personally dislike the change, then it's not going into Core.

[VentMine]

After speaking with a Bitmain representative in regards to the issues with their 16nm products, I would highly recommend using a hosting service. Things as little as a power outage, lost internet connection, etc can cause asics to burn which may not even be detectable by a quick visual inspection. Obviously, a hosting company is not immune from these service interruptions but should be setup with fail-overs. All of my s9 & r4 repairs were burned asics. I never had one case of burned asic on prior Bitmain products (s1, s3, s5, s7)

I'm just curious what you mean here. What safety measures would a premier hosting service have in place to help prevent failed / burnt hashboards? What kind of "failovers"?

[ComputerGenie]

I'm just curious what you mean here. What safety measures would a premier hosting service have in place to help prevent failed / burnt hashboards? What kind of "failovers"?

Data-centers have large-scale surge protection and redundant power supply sources (things that are cost ineffective in a smaller environment). Boards can become damaged by brown-outs and surges that occur during standard power recovery, the protections that a data-center has nearly eliminates those issues.

[Colohub]

I'm just curious what you mean here. What safety measures would a premier hosting service have in place to help prevent failed / burnt hashboards? What kind of "failovers"?

Data-centers have large-scale surge protection and redundant power supply sources (things that are cost ineffective in a smaller environment). Boards can become damaged by brown-outs and surges that occur during standard power recovery, the protections that a data-center has nearly eliminates those issues.

Agreed, not only do we host in our data center, we are nearing 300 Antminers of our own with 20 more that went online yesterday. Power is strictly monitored at the distribution unit as well as at the outlet level on the pdu's in the cage. No more thank 80% of a 30AMP circuit is every drawn. Irregularities, if any, are reported via text message. In the even of any outages, battery backups immediately kick in for 20 seconds prior to a 2 megawatt generator supplying power. Put to the test 2x since 2013 and worked flawlessly. We also ring fiber in the center and to Chicago/Omaha to ensure no connectivity loss. We have hosted an A4 for an overseas client, that was concerned about excessive reboots, not a single one since coming aboard in late January.

[Micky25]

After speaking with a Bitmain representative in regards to the issues with their 16nm products, I would highly recommend using a hosting service. Things as little as a power outage, lost internet connection, etc can cause asics to burn which may not even be detectable by a quick visual inspection. Obviously, a hosting company is not immune from these service interruptions but should be setup with fail-overs. All of my s9 & r4 repairs were burned asics. I never had one case of burned asic on prior Bitmain products (s1, s3, s5, s7)

Could that be because you don't have autotune on the prior products? For me, the most cogent and simplest explanation for the burned asics is their wretched autotune software. Made to maximize profit by pressing the utmost hash out of each chip, some of them get, unsurprisingly, wasted by that.

[fanatic26]

I never had one case of burned asic on prior Bitmain products (s1, s3, s5, s7)

I can show you pictures of HUNDREDS of burnt up S7 hashing boards i have in house. The early batch s7s had a firmware bug and they would catch on fire for a variety of reasons. I once lost 24 of them because a fan failed on a procurve switch and it shut down. This is NOT a new thing.


P.S. it has nothing to do with the autotune firmware. That firmware was created specifically to verify it was not running any chips on a hashing board out of spec.

[Micky25]

P.S. it has nothing to do with the autotune firmware. That firmware was created specifically to verify it was not running any chips on a hashing board out of spec.

Did you watch what happens during this autotune process? Though I'm no coder, this doesn't look overly elaborated to me. I seams like a try and error approach.