ANTMINER S3+ Discussion and Support Thread

[visdude]

Can we get a firmware that actually has the correct fan speed? Out of 11 miners, 6 are wrong.

Hfan       Fans
1740   1740 1380
1560   1560 1200
1860   1860 1620
1500   1500 1320
1740   1740 1500
7140   4260 7140
9300   7200 9300
8460   8460 6240
9480   7500 9480
8940   8700 8940
10500 7080 10500

My highest fan speed beats yours:  



Kidding aside, I concur.  Considering Bitmain's technical accomplishments to date, how hard is it for them to fix this lingering issue?

it might be the fans fault..

ive had case fans in my pc that show up as spinning really fast on the motherboard sensor.. i replaced the fan and the speed shows correct..

also, id set your diff to 512..
and your hwe% is really high.. its causing your rejects to be high.. plus best share of 0 after 5 hours?

you might get more share rate if you set your diff to 512, and lower your speed to the 237.5 setting.

more shares = higher payout

It's possible that the culprit is the fan's sensor itself.  However, considering Bitmain's inability to put out a decent S3 firmware since it's introduction in June of last year, it's possible that it could be a firmware issue also.

I've played around with S3 diff settings north and south of 256 but it seems 256 is it (at least for the pool that they were pointed to at the time of the screenshot in August 2014).

[Antuam]

Hi Guys.

Be careful with the last firmware of January. I was update it yesterday in the night and today my S3+ is burn for the expensive voltage.
My Power supply, Corsair HX 1050 is work fine, but 2 of the PCIe connections are burn and the s3 don't mining. It only mining 10 minutes to 450Gh and down the hash to 50Gh more or less.

I had flash to the October firmware but my problem continue same. Any help, please?.

Best regards.
Antuam.

Can you post a picture please? Its very likely going to be an RMA if its under warranty though. PM BitmainWarranty to arrange an RMA. Be sure to link to your post describing the issues, what type and how many miners you wish to have repaired/replaced and your bitmaintech.com order number.

this means that if you are out of warranty to NOT flash newer firmware as they wont help you out?

if the firmware bricks the miners, it should be warranty forever.

Hi Guys.
Yes, I sent an e-mail with a pictures to Yoshi of Bitmaintech, but he don't tell me nothing yet.
My S3 have more of 3 moths ago  .

Regards.
Antuam

[dogie]

it might be the fans fault.. ive had case fans in my pc that show up as spinning really fast on the motherboard sensor.. i replaced the fan and the speed shows correct..

also, id set your diff to 512.. and your hwe% is really high.. its causing your rejects to be high.. plus best share of 0 after 5 hours?

you might get more share rate if you set your diff to 512, and lower your speed to the 237.5 setting.

more shares = higher payout

HW % is fine, as is anything under a few %. Diff isn't an issue on S3s, and best share has never worked.

That's also not how it works for shares, everything goes back to calculating at diff 1 otherwise it wouldn't make any sense. If you double the difficulty, you're also going to be doubling the solve time.

[pekatete]

HW % is fine, as is anything under a few %. Diff isn't an issue on S3s, and best share has never worked.

There definitely is a correlation between HW % and rejects. Furthermore, rejects reduce shares thus rewards if you are mining on a pool, and if solo mining redue your chances of solving the block even further.

Best share does not work on some pools (e.g ghash) , but works on others (e.g slush), so it is incorrect to say it has never worked, more like it does not work on your pool.

EDIT:
Diff settings can help improve rewards when mining on a pool in the very short run, so it may be fair to say it is not an issue on S3's, but that depends on the pool you are mining on. Some pools take an age to set a var diff thus costing you rewards, while others are quick. Also, intermitent connections can result in the pool setting a low diff that reduces rewards, so there is no harm in setting a minimum diff for the S3 at the onset. In any case, if the pool detects the rig is hashing at a higher diff than you've set, it will adjust it accordingly.
END EDIT:

PS. If you are not sure of the answer, do not clog the thread with waffle.

[mrpark]

I am still running on Jan firmware on my S3+, its still running fine at 450Gh/s. I am not planning on messing with it anytime soon since it's finally working after many firmware updates and hours of work.

[navigator]

One of my B5 or B6? S3's is still running a July 2014 firmware. Working great at 500gh. No reason to flash a new firmware if it's working.

[philipma1957]

One of my B5 or B6? S3's is still running a July 2014 firmware. Working great at 500gh. No reason to flash a new firmware if it's working.

So very true.

[bspurloc]

OK, I did that and it worked. So what you are telling me, you can't just power up a S3+ miner, you have to go in and reboot it from the web interface.  I find it surprising because this is the newest and greatest firmware. Is there a list of bugs somewhere? How is the average miner supposed to know all these things?

This is a bug. Reboot from the web gui and check again

What does it mean when your S3+ has a normal hash rate like 480 Gh/s, but your average is listed as 18 Gh/s? Going crazy over here...

Of the last 3 firmwares, the 12/16 seem to be the best.  I know they took it down, but it my early batch S3 up to 500G consistently.  I think I will go back to that one.  It was better than the 12/19.

it is just a bug where it lost or is using a previous output file due to an unclean reboot... no need to reboot just restart cgminer
/etc/init.d/cgminer restart

Mine do this when there is a power loss...

[mrpark]

I made a huge mistake, I rebooted one of my S3s. Now this is all I get. Can anyone shed some light on what to do? I tried rebooting a few times, it says "Alive" but I get nothing!!......

[pekatete]

I made a huge mistake, I rebooted one of my S3s. Now this is all I get. Can anyone shed some light on what to do? I tried rebooting a few times, it says "Alive" but I get nothing!!......

<snip> img </snip>

Are you sure you just rebooted?
I had a similar screen when I tried to run cgminer 4.6.1 on an S1 but forgot to modify the soft link to point to the new binary. I am not saying that is what you did, but clearly your cgminer is NOT starting .... try doing it manually (first stop then start) via the UI. If that fails, SSH into the rig and type cgminer-api then enter and post here the response you get.

[mrpark]

Yes, all I did was reboot, and the graph is even still showing 1.52 peak. I wonder if I should try the Jan firmware on it, I am just afraid it might fry the PCI-E like the other guy said. heh. Damn, why did I reboot!

I made a huge mistake, I rebooted one of my S3s. Now this is all I get. Can anyone shed some light on what to do? I tried rebooting a few times, it says "Alive" but I get nothing!!......

<snip> img </snip>

Are you sure you just rebooted?
I had a similar screen when I tried to run cgminer 4.6.1 on an S1 but forgot to modify the soft link to point to the new binary. I am not saying that is what you did, but clearly your cgminer is NOT starting .... try doing it manually (first stop then start) via the UI. If that fails, SSH into the rig and type cgminer-api then enter and post here the response you get.

[Mudbankkeith]

when the top line shows zero's in the hash rate, try the following:-

log in and go to:-

status tab

miner configuration tab

advanced settings tab (grayed out till you select it)....... then re-select the frequency, then save and apply.


(there was a reference to this back in August when the S1/S3 upgrades were first offered)

[mrpark]

I tried flashing to 1024, nothing. I just did the save and apply it didn't work, but the line for voltage on the S3 is blank. Should it be? hmm. Going to reboot once more...

when the top line shows zero's in the hash rate, try the following:-

log in and go to:-

status tab

miner configuration tab

advanced settings tab (grayed out till you select it)....... then re-select the frequency, then save and apply.


(there was a reference to this back in August when the S1/S3 upgrades were first offered)

[macgyver007]

it might be the fans fault.. ive had case fans in my pc that show up as spinning really fast on the motherboard sensor.. i replaced the fan and the speed shows correct..

also, id set your diff to 512.. and your hwe% is really high.. its causing your rejects to be high.. plus best share of 0 after 5 hours?

you might get more share rate if you set your diff to 512, and lower your speed to the 237.5 setting.

more shares = higher payout

HW % is fine, as is anything under a few %. Diff isn't an issue on S3s, and best share has never worked.

That's also not how it works for shares, everything goes back to calculating at diff 1 otherwise it wouldn't make any sense. If you double the difficulty, you're also going to be doubling the solve time.

Anything less than a few% I consider the amount of errors in the screenshot Im posting  to be excessive for an S3, and best share has always worked....doubling the solve time has nothing to do with anything being discussed either .... well played again misinformation from the paid support rep....heres something you can "pass to engineers" and perhaps refrain from future dogieshit of no value.... you can ask them why is it that on not only S3, but S2, and S4 that the best share does not show if the difficulty is set to what is recommended as the actual difficulty?  note the best share value you claim that has never worked and how it works   but why does it only work if I set difficulty to 511, or 1023, or 2047 in the case of S3, S2 and S4 respectively
So in short to see your best share on S3 set your difficulty to 511 ....I used 511 as you can see from the screenshot and using the actual # for difficulty will result in best share not working....also note what a piece of junk this s3 is..the only way it gets close to 440GH/s is using 231 frequency

[intobit459]

hey thats pretty good if your running 0103 firmware i have .6% at 218mhz around 410ghs  only way to get no x or - on asics

new fw needs major work

[-ck]

Lack of best share is not the pool's fault, it's the driver's. It doesn't calculate the share difficulty if it's coincidentally a power of 2 value at the pool.

[pekatete]

Lack of best share is not the pool's fault, it's the driver's. It doesn't calculate the share difficulty if it's coincidentally a power of 2 value at the pool.

That's interesting. I wonder why my S3 displays a best share while mining on slush but never displays one (i.e shows 0) when mining on ghash. It is the same S3, and I assume using the same driver .... or does cgminer change the driver change according to the pool you point it to?
EDIT: Or is it that the difficulty at ghash is always a power of 2 value (not sure what that means ....) and at slush is never that?

[mrpark]

I tried even flashing the S3 to 0103, i rebooted still nothing. I will try to physically reboot the miner now I guess.

[daddyfatsax]

Lack of best share is not the pool's fault, it's the driver's. It doesn't calculate the share difficulty if it's coincidentally a power of 2 value at the pool.

TIL and now i feel dumb.

[sloopy]

I have an S3 which showed up today I can not log in.
I do get to the screen where you enter the login and pass and I enter root / root no luck. I tried root / admin no luck. I powered off and pressed the hole beside the cat 5 LEDs for ten seconds, tried again with new browser window, same thing, tried with it powered on, same thing. What am I missing here please. It must be something dumb but it is driving me mad. I had another one from ebay show up doa today.