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

Is there an easy way to get this onto our boxes?

Do I just get form command line or?

Thx

Fahlcor

No there are more than enough topics already, and people can come to the cgminer thread to discuss it if they wish. I already monitor hundreds of threads and do not wish to be burdened by more.

maybe we should make a topic about this, so all people can keep up to date about this
till bitmain give us the newest cgminer

coz this page will be drowned in 2 or 3days 

mr ckolivas, maybe its better that you create the topic
coz, i saw you warned many times, but people wont know if it gets drowned 

Wow if this works as I'm sure it will I think we owe ckolivas a BIG thank you.

Will give it a shot. Expect a tip to your BTC address ckolivas !

Strato

I don't have the build environment to create a full binary image, and the code will need a LOT of work to actually become part of mainline cgminer it seems, but for the time being here is a link to a bugfixed binary of cgminer 4.6.0 for the S3 based on the bitmain code. Copy the file into /usr/bin/ on the S3 overwriting the existing one:
http://ck.kolivas.org/apps/cgminer/antminer/s3/4.6.0-140908/cgminer

If I recall, thats the last one released which went on all my miners. It allows you to set frequencies for overclocking without the need to SSH in to the system. Beyond that, I am not currently aware of any other benefits.

Absolutely! Although Slush's is 0.01 BTC minimum, I reckon I'll still get a payout from all three each week assuming the S3 delivers in split (balance) mode.  But as I type my averages are:

Eligius - 101.81 GHs
BTC Guild - 113.38 GHs
Slush - 130 GHs

Combined this is 344 GHs which, admittedly is a figure based on pool reported speeds that can be inaccurate, but it is far enough below the S3's standard 453 GHs to cause some concern. Is it just me? Anyone else found this?

I am trying to compile the latest cgminer for S3.
I spent some time to configure my environment and now I can build and run some old cgminer versions.

But I do not have enough time to understand cgminer code and I could not build the latest, 4.6 cgminer
driver-bitmain.c depends on a few deprecated but important functions:
- clone_queued_work_byid
- inc_work_stats
- submit_nonce_direct
It there anybody who can explain how can I replace these functions with the new cgminer api?

at some pools (Slush's) you can select the payout at as low as 0.001 BTC; you can also point several miners to the same wallet address (in Eligius, just use _), which will speed up the payouts.

I'll look at the code today.

Yes, I am aware I can have 1, 2 or 3 pools. My view is that since BTC Guild, Eligius and Slush combined are equal to a little less than GHash.io or Discus Fish in terms of hashing power, by mining on all three I should get a similar rate of payout to if I were on one of the big two (although I won't get to payout thresholds as quickly). I prefer this because although I'm only a tiny fish in a big ocean, I'd like bitcoin to stay decentralised and because it gives me a smoother payout rate rather than the lumpy mining that comes from putting all my hashing power on one smaller pool. A steadier payout rate means I can use my BTC for everyday purchases more easily rather than being a hoarding or trading type that is concerned with BTC's value in fiat. In short, for me it's an extra income. But that's just my philosophy. What I'm really looking for is someone who knows whether an S3 running in balance mode delivers it's full GH/s and why balance and load balance mode seem to cause trouble with Ghash.io difficulty settings.

hello

did anyone test the last firmware antMiner_S320140826.bin?

what gains can we achieve with this new firmwere?

the purpose of three pools specification usually is NOT to split equally, but to provide a backup. BTW, you don't have to have a third pool specified, it could be just two.

Maybe @Kano could come to the rescue and compile a new binary just like he did with the s1/s2?

https://github.com/kanoi/cgminer-binaries/tree/master/AntS1

I´m even willing to send him a tip, anyone else cares to join?

Hi guys,

I just got started with my first Antminer S3 and one of the features I liked the look of was the ability to specify three pools and mine from them simultaneously. I figured that this would mean a more stable level of mining income for me since using three pools would mean that the risk of one pool being very unlucky in any given time period would be offset by the chance of one of the other two pools being above average lucky. All things being equal, it should mean getting closer to a miner's average return, rather than peaks and troughs. At least that was the theory...

When I tried this, I initially set it up with Ghash.io, Slush and BTC Guild. All was good except that GHash error rate decided to go to the moon! I started getting 60 - 80% reject rates per shift with masses of low difficulty rejects, despite specifying in their workers page to send them at diff 256. This was in stark contrast to when I first rigged it up online. I pointed it at Ghash.io alone and it performed very well, a few GH/s less than advertised but I'm only running it off of a CS550M PSU with two connectors so I hadn't expected it to overperform.

Naturally I did what any sane miner would do and ditched GHash.io in favour of Eligius  

Jokes aside, does the S3 perform as rewardingly when split between 3 pools as it does when aimed just at 1 or does some GH/s never get utilized? And does anyone know why mine struggles with GHash.io difficulty when it's aimed there as part of a balanced pool set up but works fine with GHash.io if I set it to work 100% on that pool alone?

PS Sorry to post this while an important discussion on security is going on but I wasn't sure whether to start a new thread for this or keep it in this thread where all the S3 expertise is clearly hanging out 

I don't believe that to be the case I'm afraid. I believe it's possible to redirect a proportion of hash rate, so that your miners never actually show as idle......not sure though, maybe ckolivas can clarify this?

The reason its smart to have each miner on its own worker and then have a pool that will e-mail you when your workers have been idle.

I just can't see that being the case tbh. I'm sure if they found their entire hashing farm was being redirected to a different pool, they'd soon implement it.......

I would speculate that they're short staffed, and the oob cgminer doesn't work for them, so they have to customize it.

M

It seems to me that the obvious & right thing for Bitmain to do is what they promised the community they would do. Take down the S3+ firmware update (which does not match the MD5 checksum anyway) and replace it with one that contains the latest cgminer code that fixes the redirect issue. As has been mentioned before - why wouldn't they want to do this? Why would such a large miner manufacturer insist on keeping this security flaw in place?

Food for thought indeed......