ANTMINER S3+ Discussion and Support Thread

[-ck]

I have 4.6 running and according to TOP it is hashing.

But M's Ant monitor does not talk to it any more.

according to miner status it web page it is hashing fine also.

maybe I'll waiting until M gets the ant monitor updted to the 4.6 API?

I can't live without Ant Monitor.

Fahlcor

Bitmain used a, um, hacked version of cgminer.  The API output isn't even close to accurate.  That's why one of the later versions of the firmware broke M's Ant Monitor, as the output from the API was actually malformed (incorrect) JSON.  I had to compensate for it in my code for it to work again.

Therefore it's not a surprise that the proper API from 4.6 doesn't work.  I'll see if I can put it on my S3 in a manner that I can go back.  I think I can manage that.

Actually I used their git master tree driver specifically to try and not break their luci web which shouldn't have changed their API output too much from what they expect though it needed a few basic fixes. A proper merge and rewrite would likely break all their interfaces and this binary I posted was just as a service to provide the bugfixes in later versions, especially for the protection against the redirect attack. I don't anticipate I'll be doing the proper rewrite, but Kano probably will when we free him up from pool code work.

[kabopar]

I have 4.6 running and according to TOP it is hashing.

But M's Ant monitor does not talk to it any more.

according to miner status it web page it is hashing fine also.

maybe I'll waiting until M gets the ant monitor updted to the 4.6 API?

I can't live without Ant Monitor.

Fahlcor

I updated all my S3's to 4.6 and they all show up fine on Ant Monitor (v3.1).

Cheers

[SMB-2525]

ANTMINER S3 Wireless configuration.

My B7 S3 is able to detect my wireless router without having the antenna mod discussed above. Has that been the case with the earlier versions?

Given the large number of thumbs on my two hands, it would be nice if I did not have to do the mod.

TIA

[hochiroku]

when i login and check stats of miner i can see the reject rate is ridiculously high. would it effect my mining?

[Fahlcor]

I have 4.6 running and according to TOP it is hashing.

But M's Ant monitor does not talk to it any more.

according to miner status it web page it is hashing fine also.

maybe I'll waiting until M gets the ant monitor updted to the 4.6 API?

I can't live without Ant Monitor.

Fahlcor

I updated all my S3's to 4.6 and they all show up fine on Ant Monitor (v3.1).

Cheers

yeah I switch Ant MOnitor to use Web and is looking nice now.  I'll do the other 11 now.

Could someone sticky that post and host the file long term for the others that might want to upgrade?  Seems simple enough as I doubt Bitmain would do it any time soon...

Anyone see any reason not to do this?

Fahlcor

[Fahlcor]

when i login and check stats of miner i can see the reject rate is ridiculously high. would it effect my mining?

Post your actual rates for hash as a comparison.

[Fahlcor]

I have 4.6 running and according to TOP it is hashing.

But M's Ant monitor does not talk to it any more.

according to miner status it web page it is hashing fine also.

maybe I'll waiting until M gets the ant monitor updted to the 4.6 API?

I can't live without Ant Monitor.

Fahlcor

I updated all my S3's to 4.6 and they all show up fine on Ant Monitor (v3.1).

Cheers

yeah I switch Ant MOnitor to use Web and is looking nice now.  I'll do the other 11 now.

Could someone sticky that post and host the file long term for the others that might want to upgrade?  Seems simple enough as I doubt Bitmain would do it any time soon...

Anyone see any reason not to do this?

Fahlcor

I also noticed  the load average is way lower on the CPU now that it was.  was always above 2 before.  now hovers around 1.2.  any additional benefit to these devices to run with lower/higher loads?

[-ck]

I also noticed  the load average is way lower on the CPU now that it was.  was always above 2 before.  now hovers around 1.2.  any additional benefit to these devices to run with lower/higher loads?

That's likely the advantage of the newer version. In principle it will lead to less lag time in keeping the device busy and less time to process and send shares. However cgminer is so heavily multithreaded that it probably won't matter since the latency critical parts of the cgminer code are already prioritised.

[pekatete]

I also noticed  the load average is way lower on the CPU now that it was.  was always above 2 before.  now hovers around 1.2.  any additional benefit to these devices to run with lower/higher loads?

That's likely the advantage of the newer version. In principle it will lead to less lag time in keeping the device busy and less time to process and send shares. However cgminer is so heavily multithreaded that it probably won't matter since the latency critical parts of the cgminer code are already prioritised.

Still early days since I updated my S3 with the latest cgminer (3 hrs+) but I have noticed an improvement in the pool-side reported hashrate AND I suspect a reduced DiffR. This is on top of a faster UI (which I attribute to the lower load average).

Just a question, would this cgminer run on an S1 (like to earlier Kano cgminer)?

[techgeeks]

Will this version work on the s1 or s2 machines as well?

I also noticed  the load average is way lower on the CPU now that it was.  was always above 2 before.  now hovers around 1.2.  any additional benefit to these devices to run with lower/higher loads?

That's likely the advantage of the newer version. In principle it will lead to less lag time in keeping the device busy and less time to process and send shares. However cgminer is so heavily multithreaded that it probably won't matter since the latency critical parts of the cgminer code are already prioritised.

Still early days since I updated my S3 with the latest cgminer (3 hrs+) but I have noticed an improvement in the pool-side reported hashrate AND I suspect a reduced DiffR. This is on top of a faster UI (which I attribute to the lower load average).

Just a question, would this cgminer run on an S1 (like to earlier Kano cgminer)?

[Biodom]

I also noticed  the load average is way lower on the CPU now that it was.  was always above 2 before.  now hovers around 1.2.  any additional benefit to these devices to run with lower/higher loads?

That's likely the advantage of the newer version. In principle it will lead to less lag time in keeping the device busy and less time to process and send shares. However cgminer is so heavily multithreaded that it probably won't matter since the latency critical parts of the cgminer code are already prioritised.

Still early days since I updated my S3 with the latest cgminer (3 hrs+) but I have noticed an improvement in the pool-side reported hashrate AND I suspect a reduced DiffR. This is on top of a faster UI (which I attribute to the lower load average).

Just a question, would this cgminer run on an S1 (like to earlier Kano cgminer)?

Could you report hash difference (if any) after 24hr?

[pekatete]

Could you report hash difference (if any) after 24hr?

I sure will (and that is why I said "still early days ...".

[Moria843]

Do you have to take the case off of the S3 to screw on an antenna and run wireless?

[mahowi]

I also noticed  the load average is way lower on the CPU now that it was.  was always above 2 before.  now hovers around 1.2.  any additional benefit to these devices to run with lower/higher loads?

That's likely the advantage of the newer version. In principle it will lead to less lag time in keeping the device busy and less time to process and send shares. However cgminer is so heavily multithreaded that it probably won't matter since the latency critical parts of the cgminer code are already prioritised.

Still early days since I updated my S3 with the latest cgminer (3 hrs+) but I have noticed an improvement in the pool-side reported hashrate AND I suspect a reduced DiffR. This is on top of a faster UI (which I attribute to the lower load average).

Just a question, would this cgminer run on an S1 (like to earlier Kano cgminer)?

No, it doesn't work on S1. I tried it and it's not hashing.

[pekatete]

....
Just a question, would this cgminer run on an S1 (like to earlier Kano cgminer)?

No, it doesn't work on S1. I tried it and it's not hashing.

Thats that then. Come to think of it, it even resided in the S3 directory (which should have given the game away for me!)
Thanks for placing your S1 in harm's way to clear this up.

[dlasher]

I also noticed  the load average is way lower on the CPU now that it was.  was always above 2 before.  now hovers around 1.2.  any additional benefit to these devices to run with lower/higher loads?

That's likely the advantage of the newer version. In principle it will lead to less lag time in keeping the device busy and less time to process and send shares. However cgminer is so heavily multithreaded that it probably won't matter since the latency critical parts of the cgminer code are already prioritised.

Pushed 4.6 to (60) S3's, they're all working great.. (60 minutes runtime). Thank you sir, much appreciated!

[jelin1984]

what exactly is 4.6
firmware or something else.:?/

[pekatete]

what exactly is 4.6
firmware or something else.:?/

Latest version of cgminer for the S3

[Rabinovitch]

Here's what I've used and it started hashing as usual.
1. SSH into the S3 and login
2. Issue the following commands sequentially.
  a) cd /usr/bin
  b) mv cgminer cgminer.bak
  c) wget http://ck.kolivas.org/apps/cgminer/antminer/s3/4.6.0-140908/cgminer
  d) chmod +x cgminer
  e) reboot

Confirm. Both my S3s Batch 7 were upgraded well this way.

CPU load now is about 90% instead of 99-100% with old cgminer. WebGUI is a bit quicker. Niiice!  

p.s. I suspect that it will not work for S2?..

[techgeeks]

Have you tried increasing the freq over 250 since changing? - Looks like extra CPU might equal more work into the asics.  I am not sure how or where the file is not with the new bios, that  you can set from interface.  Anyone know where to edit that file?

TIA

  

Here's what I've used and it started hashing as usual.
1. SSH into the S3 and login
2. Issue the following commands sequentially.
  a) cd /usr/bin
  b) mv cgminer cgminer.bak
  c) wget http://ck.kolivas.org/apps/cgminer/antminer/s3/4.6.0-140908/cgminer
  d) chmod +x cgminer
  e) reboot

Confirm. Both my S3s Batch 7 were upgraded well this way.

CPU load now is about 90% instead of 99-100% with old cgminer. WebGUI is a bit quicker. Niiice!