Author

Topic: ANTMINER S3+ Discussion and Support Thread - page 276. (Read 710164 times)

hero member
Activity: 556
Merit: 500
Anyone want to post on here their Antminer s3 setup? I want to replicate some sort of rack.
Thanks.
Anyone want to learn how to user search feature? You really should experiment with it. I shudder to think what will happen when your units arrive:




Here's a thread with lots of pictures for you, courtesy of my use of the search feature.
https://bitcointalk.org/index.php?topic=7216.6020
full member
Activity: 139
Merit: 100
Woot

http://www.coinwarz.com/network-hashrate-charts/bitcoin-network-hashrate-chart

according to that the network hash rate just passed ~214 phash.  Can we say another lost day of mining before difficulty occurs...

I feel worse for those with ants in limbo or on pre-order.

/sarcasm for wooting...

Fahlcor
legendary
Activity: 1064
Merit: 1001
The one page in the admin area where i shows dropbear port 22, that's what allows putty to connect right so if I changed hat to say 2013 I would use 2013 in the port box on putty to connect via ssh ?
So, anyone ?

Yes, that's correct. It changes /etc/config/dropbear and restarts.

config dropbear
   option PasswordAuth 'on'
   option RootPasswordAuth 'on'
   option Port         '2013'

But to be clear, by making that change... 2013 is what would be used in putty for SSH and that change doesnt just affect something else ?
newbie
Activity: 11
Merit: 0
The one page in the admin area where i shows dropbear port 22, that's what allows putty to connect right so if I changed hat to say 2013 I would use 2013 in the port box on putty to connect via ssh ?
So, anyone ?

Yes, that's correct. It changes /etc/config/dropbear and restarts.

config dropbear
   option PasswordAuth 'on'
   option RootPasswordAuth 'on'
   option Port         '2013'
legendary
Activity: 1064
Merit: 1001
The one page in the admin area where i shows dropbear port 22, that's what allows putty to connect right so if I changed hat to say 2013 I would use 2013 in the port box on putty to connect via ssh ?
So, anyone ?
newbie
Activity: 11
Merit: 0
I have 2 S3s that are now over-clocked. I'm using a Corsair RM850 to power both, with 4 dual PCI-E cables. I didn't have any luck getting them to run stable at 250Mhz, so I backed off to 237.5Mhz.

Results after 1 day:

http://www.ramosresearch.com/images/bitcointalk/overclock.results.2014-08-11.1.png

http://www.ramosresearch.com/images/bitcointalk/overclock.results.2014-08-11.2.png

Both miners have settled in to an average GH/s of ~478, but there's a lot of variance as you can see by the graph. Still, very pleased with the results and the lack of hardware errors.
sr. member
Activity: 280
Merit: 250
Brainwashed this way
Do any of you here know why the queue on the config is set so high? Is there a big gain from setting it to a lower number or why did they program 4096 as the queue. The discarded amounts are so high...

If you want, you can change the queue in /etc/init.d/cgminer

I use 32 and it seems to be a good compromise.  Some people use 1, others have kept 4096 - doesn't seem to have a huge effect, but can save you some CPU cycles if you make it lower.

Okay thanks, I will search. Does the 4096 and large amount of discarded not affect the overall hashrate and work submitted? Also, is 32 equivalent to 32shares or a share in that size?  I ask because I did not know if 4096 was 4096 shares or a share/shares added for a vardiff of 4096

Look at cklolivas(cgminer dev) post in this thread. Goes into great detail about this.

I will try. The results from search is a bit overwhelming in such a large thread. I was hoping for a single quick fix answer but I will try to read through the results
[/quote


https://bitcointalksearch.org/topic/m.8056057

legendary
Activity: 1081
Merit: 1001
B7 = 0.66 BTC great  Shocked


Moolah out their wazoo, eh?  I hear ya.
sr. member
Activity: 448
Merit: 252
B7 = 0.66 BTC great  Shocked
newbie
Activity: 27
Merit: 0
Do any of you here know why the queue on the config is set so high? Is there a big gain from setting it to a lower number or why did they program 4096 as the queue. The discarded amounts are so high...

If you want, you can change the queue in /etc/init.d/cgminer

I use 32 and it seems to be a good compromise.  Some people use 1, others have kept 4096 - doesn't seem to have a huge effect, but can save you some CPU cycles if you make it lower.

Okay thanks, I will search. Does the 4096 and large amount of discarded not affect the overall hashrate and work submitted? Also, is 32 equivalent to 32shares or a share in that size?  I ask because I did not know if 4096 was 4096 shares or a share/shares added for a vardiff of 4096

Look at cklolivas(cgminer dev) post in this thread. Goes into great detail about this.

I will try. The results from search is a bit overwhelming in such a large thread. I was hoping for a single quick fix answer but I will try to read through the results
legendary
Activity: 4256
Merit: 8551
'The right to privacy matters'
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.

I will bump your request.
donator
Activity: 1057
Merit: 1021
Anyone want to post on here their Antminer s3 setup? I want to replicate some sort of rack.
Thanks.



Here is my rack you can duplicate.
legendary
Activity: 1081
Merit: 1001
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.

Thank you for this post.  I hope Bitmain will capitulate as expected.  It is morally the right thing to do on their part.

It's more than morally right; it's legally required.

Although it isn't clear what recourse this community (or anyone) would have against a Chinese company that doesn't comply with the GPL. Hopefully it won't come to that...

The legal part is a given; I already got that.  I was just trying to appeal to Bitmain's morality.  I hope they still have an ounce left and not completely overwhelmed by capitalism, i.e. profit and greed.

sr. member
Activity: 266
Merit: 250
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.

now the boss is coming around here lately
we hope BITMAIN will provide the source code, so we wont ended up editing the queue by ourselves...

its kinda risky, actually i really dont know
legendary
Activity: 1081
Merit: 1001
Do any of you here know why the queue on the config is set so high? Is there a big gain from setting it to a lower number or why did they program 4096 as the queue. The discarded amounts are so high...

If you want, you can change the queue in /etc/init.d/cgminer

I use 32 and it seems to be a good compromise.  Some people use 1, others have kept 4096 - doesn't seem to have a huge effect, but can save you some CPU cycles if you make it lower.

Okay thanks, I will search. Does the 4096 and large amount of discarded not affect the overall hashrate and work submitted? Also, is 32 equivalent to 32shares or a share in that size?  I ask because I did not know if 4096 was 4096 shares or a share/shares added for a vardiff of 4096

Look at cklolivas(cgminer dev) post in this thread. Goes into great detail about this.

Do you remember which page it is approximately?

legendary
Activity: 1150
Merit: 1004
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.

Thank you for this post.  I hope Bitmain will capitulate as expected.  It is morally the right thing to do on their part.

It's more than morally right; it's legally required.

Although it isn't clear what recourse this community (or anyone) would have against a Chinese company that doesn't comply with the GPL. Hopefully it won't come to that...
sr. member
Activity: 280
Merit: 250
Brainwashed this way
Do any of you here know why the queue on the config is set so high? Is there a big gain from setting it to a lower number or why did they program 4096 as the queue. The discarded amounts are so high...

If you want, you can change the queue in /etc/init.d/cgminer

I use 32 and it seems to be a good compromise.  Some people use 1, others have kept 4096 - doesn't seem to have a huge effect, but can save you some CPU cycles if you make it lower.

Okay thanks, I will search. Does the 4096 and large amount of discarded not affect the overall hashrate and work submitted? Also, is 32 equivalent to 32shares or a share in that size?  I ask because I did not know if 4096 was 4096 shares or a share/shares added for a vardiff of 4096

Look at cklolivas(cgminer dev) post in this thread. Goes into great detail about this.
legendary
Activity: 1081
Merit: 1001
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.

Thank you for this post.  I hope Bitmain will capitulate as expected.  It is morally the right thing to do on their part.

legendary
Activity: 1081
Merit: 1001
Anyone want to post on here their Antminer s3 setup? I want to replicate some sort of rack.
Thanks.

I like this rack.  Replicate that!



legendary
Activity: 1081
Merit: 1001
Do any of you here know why the queue on the config is set so high? Is there a big gain from setting it to a lower number or why did they program 4096 as the queue. The discarded amounts are so high...

If you want, you can change the queue in /etc/init.d/cgminer

I use 32 and it seems to be a good compromise.  Some people use 1, others have kept 4096 - doesn't seem to have a huge effect, but can save you some CPU cycles if you make it lower.

Okay thanks, I will search. Does the 4096 and large amount of discarded not affect the overall hashrate and work submitted? Also, is 32 equivalent to 32shares or a share in that size?  I ask because I did not know if 4096 was 4096 shares or a share/shares added for a vardiff of 4096

I'm with y'all regarding Bitmain's pricing.  However, as long as there are hardware geeks out there who are willing to pay at any price regardless of ROI just so they can have their shiny toys to play with, Bitmain has no incentive to modify their pricing model to benefit the consumer.  We can biatch all we can in here and rationalize it in a futile attempt to sway Bitmain to our cause but unfortunately, we are a minority.  Them hardware geeks are buying the S3s like hotcakes regardless.  Remember, Bitmain is not in business for nothing; they are definitely not an NPO.  Now, if we could only convince these hardware geeks around the world...nah, greed and bragging rights rule.

Jump to: