ANTMINER S3+ Discussion and Support Thread

[Biodom]

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

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

Well, it has been a few days. Can you report any increase in hashing on 4.6.0 in comparison with the stock version?
Thanks.

One thing that is still whirling away in my mind is why the same chip always comes trumps with the X? Also this may have something to do with power, as I am running the S3 off a 550 watt server PSU. If the unit is drawing anything over 460 watts, then that might be the reason.

I have one batch1 miner at 237.5 with one ASIC that always has the X, hence it is at 464-465Gh instead of 478Gh, but since it is still better than 441 at default, I let it be.

[pekatete]

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

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

Well, it has been a few days. Can you report any increase in hashing on 4.6.0 in comparison with the stock version?
Thanks.

One thing that is still whirling away in my mind is why the same chip always comes trumps with the X? Also this may have something to do with power, as I am running the S3 off a 550 watt server PSU. If the unit is drawing anything over 460 watts, then that might be the reason.

I have one batch1 miner at 237.5 with one ASIC that always has the X, hence it is at 464-465Gh instead of 478Gh, but since it is still better than 441 at default, I let it be.

I suppose I could let it be, but it seems to be running per my "normal" now I have turned it down a notch and thus far a touch above the hash-rate I got when overclocked at the higher freq (with 4.6 upgrade).

This, however, is the proof of the pudding (to me at least) that 4.6 is worthy of getting, if not just for the security bug-fixes.

Couple of days of running under 4.6.0 now, and very happy. CPU load lower, and less hashrate variance.

BEFORE:


AFTER:


Thank you Con!

And the proverbial chicken and egg situation:
The smoother hash-rate variance is due to stable submissions thus accurate dynamic Diff allocation, or is it the other way round?

[faetos]

I'm trying 4.6 as well on two batch 2s. So far so good - stable, load is lower and web gui is more responsive (due to lower load). Hashrate  is very stable as well

[stan258]

After updating to 4.6 one S3 would not hash.  Maybe I missed something.  After updating, reboot then save and apply freq in advanced settings unit should fire up?

[Count_Frackula]

After updating to 4.6 one S3 would not hash.  Maybe I missed something.  After updating, reboot then save and apply freq in advanced settings unit should fire up?

Is all your base firmware also up to date?

[thehairymob]

Nope still not working. Follow all commands but had to delete cgminer from ant so it would install new version or I got an error. After that the s3 wouldn't mine so had to reflash it. Working again. Lost some more hair trying this, hehehe.

[stan258]

After updating to 4.6 one S3 would not hash.  Maybe I missed something.  After updating, reboot then save and apply freq in advanced settings unit should fire up?

Is all your base firmware also up to date?

S320140811.bin?

[Count_Frackula]

After updating to 4.6 one S3 would not hash.  Maybe I missed something.  After updating, reboot then save and apply freq in advanced settings unit should fire up?

Is all your base firmware also up to date?

S320140811.bin?

So no.
I would update to the most recent version, uncheck the box to keep settings, then apply cgminer using the following:

1. SSH into the S3 and login
2. Issue the following commands sequentially.

Code:

cd /usr/bin
mv cgminer cgminer.bak
wget http://ck.kolivas.org/apps/cgminer/antminer/s3/4.6.0-140908/cgminer
chmod +x cgminer
reboot

[navigator]

My B8 order shipped, says it will be here friday

[stan258]

After updating to 4.6 one S3 would not hash.  Maybe I missed something.  After updating, reboot then save and apply freq in advanced settings unit should fire up?

Is all your base firmware also up to date?

S320140811.bin?

So no.
I would update to the most recent version, uncheck the box to keep settings, then apply cgminer using the following:

1. SSH into the S3 and login
2. Issue the following commands sequentially.

Code:

cd /usr/bin
mv cgminer cgminer.bak
wget http://ck.kolivas.org/apps/cgminer/antminer/s3/4.6.0-140908/cgminer
chmod +x cgminer
reboot

Thanks up on 4.6 now.  Thanks

[montyfd]

Where can i see the actual cgminer i am running?

[Count_Frackula]

Where can i see the actual cgminer i am running?

SSH in and execute cgminer -V
Make sure you reboot after installing before you run this.

[twib2]

Nope still not working. Follow all commands but had to delete cgminer from ant so it would install new version or I got an error. After that the s3 wouldn't mine so had to reflash it. Working again. Lost some more hair trying this, hehehe.

Which commands, exactly?  It sounds like either you didn't set the execute flag to make it executable (won't run without it normally), you transferred it via the wrong protocol (ascii vs binary), or you simply had a bad transfer.

If you followed any of the instructions here, you wouldn't need to reflash the whole S3 since you would have a backup cgminer (the original one) still on hand.  Simply rename it (i.e. mv cgminer.bak cgminer) and you'd be back up and running.  Changing out cgminer shouldn't do anything else to your machine, so putting the old one back should be all it would take.

Here's the instructions I used, with a short explanation of what each does:


cd /usr/bin                         # move to the correct directory that has the original cgminer file
cp cgminer cgminer.orig      # makes a backup of the original file so I still have the original one on hand to copy back
wget http://ck.kolivas.org/apps/cgminer/antminer/s3/4.6.0-140908/cgminer             # retrieves the new file on top of the old one
                                                                                                                            # (this preserves the permissions, including executability)
ls -tralF cgminer*               # list all files that begin with cgminer - look for the same execution settings
                                        # (Settings on the left should read "-rwxr-xr-x" indicating it is executable, and it should be 502276 bytes in size)
                                        # if the flags for x don't look the same simply type 'chmod a+x cgminer' without the quotes and hit return/enter
/etc/init.d/cgminer restart  # restart the miner process - no need to reboot!


Hope this helps!

[Bitkoinzz]

you guys are crazy. plug em in and let run. then go do something else. GO BITMAIN

[thehairymob]

Thanks Twib will try it tomorrow night as I've been working all day and now need to chill.

[sjc1490]

Just did a UPS track by reference for my Batch 8 S3+ and it shows a Friday delivery date. Haven't received the bitmain email yet but it has shipped.

[Syke]

Shipping 10 days early. Way to go Bitmain!

Now how about that price on B9?

[tom99]

Just did a UPS track by reference for my Batch 8 S3+ and it shows a Friday delivery date. Haven't received the bitmain email yet but it has shipped.

  grats and so soon for this B8.

[nexus99]

Just did a UPS track by reference for my Batch 8 S3+ and it shows a Friday delivery date. Haven't received the bitmain email yet but it has shipped.

How do you do that?

[tom99]

Just did a UPS track by reference for my Batch 8 S3+ and it shows a Friday delivery date. Haven't received the bitmain email yet but it has shipped.

How do you do that?

  check your account for UPS # or you support to get email with UPS # to check it.