ANTMINER S3+ Discussion and Support Thread

[PatMan]

Well, I've tried four times to load this firmware & it failed every time. It just renders your Ant unusable, I had to reflash the older firmware again to get it usable again. I had various errors, not able to access the miner conf page was the worst one - all I got was this:



Tried reboots, cold reboots, keeping settings, not keeping settings & overwriting 3 times. The MD5 checked out too. This firmware sucks the big one.

USE THIS FIRMWARE AT YOUR PERIL

@Bitmain - really? I mean, REALLY?

It's bad enough waiting over 9 weeks for the promised S2 firmware, but uploading this obviously untested piece of garbage for everyone to brick their S3 with is just stunning. Spectacular even......

I've updated literally 100's of these things without issue, so if anyone got this to work? I'd love to hear from you........

[1713498176]

1713498176

[1713498176]

1713498176

[1713498176]

1713498176

[1713498176]

1713498176

[Ustler]

S3 firmware containing cgminer 4.6.1 has a issue with one of the config pages (preventing you from modifying the "Miner Configuration" page) in certain browsers (due to XML error)


To fix:

1) Putty to S3
2) Navigate to /usr/lib/lua/luci/model/cbi/cgminer/
3) vi cgminer.lua
4) Locate the "Save&Apply" section
5) Press i to insert
6) Navigate to right after the & and change this to "&"
7) Press escape and enter ":wq"

The resulting line should look like
pb = conf:taboption("advanced", Value, "voltage", translate("voltage"),"Modify voltage and Save&Apply, then need to Power off and Restart")


Do not attempt unless you know what you are doing.

Bitmain may simply fix this in the firmware so it may be worth the wait.

Donations: 19UCaVUvJ7kamCU2zdBioTgjFSUxmaqp3H

[Ustler]

@PatMan

Can you list out the various errors you had on pages? I can probably provide fixes for them rather quickly.

I would note that after upgrading, my 2x antminers are hashing much faster.. Reduction in HW errors on one Ant

[PatMan]

Thanks for that info Ustler - I'll try it again with your suggestion 

[Ustler]

@PatMan:

Just went through all the config pages, not seeing any other issues.. If you run into one, just let me know.

Here is what the config page looks like with the fix:

(Note: In my case I just changed & to " and ". If you follow my original instructions it would show up as "Save&Apply")..

https://i.imgur.com/8QrBDCd.png

[PatMan]

S3 firmware containing cgminer 4.6.1 has a issue with one of the config pages (preventing you from modifying the "Miner Configuration" page) in certain browsers (due to XML error)


To fix:


4) Locate the "Save&Apply" section


The resulting line should look like
pb = conf:taboption("advanced", Value, "voltage", translate("voltage"),"Modify voltage and Save&Apply, then need to Power off and Restart")


Do not attempt unless you know what you are doing.

Bitmain may simply fix this in the firmware so it may be worth the wait.

Donations: 19UCaVUvJ7kamCU2zdBioTgjFSUxmaqp3H

What line is the save&apply on? I can see 64 lines but no save&apply reference......

Thanks 

[Ustler]

My line 64 contains.. Total number of lines should be 67...

pb = conf:taboption("advanced", Value, "voltage", translate("voltage"),"Modify voltage and Save&Apply, then need to Power off and Restart")


Easiest way to find it is probably by typing in

"/Save&"

After Step 3.

Did you re-upgrade to new FW image?

[PatMan]

Yes, I'm in cgminer.lua - there are 64 lines of syntax, my line 64 says only "return m" (without the quotes)

EDIT: Typed in "/Save&" - not found. Are you sure it's in cgminer.lua?

[Ustler]

@PatMan;

Yes, pretty sure is cgminer.lua.

On the Status-->Overview page, does the date reflect 10/13 as firmware date (shown in screenshot below):

https://i.imgur.com/3XSZOuA.png

[PatMan]

I got it. Had to re-download & re-flash again, but I then found your line 67 & edited it accordingly - I can now edit the miner config  

What a joke - if Bitmain think that I'm gonna do this with my other 29 S3's, they can forget it  

I grow weary of Bitmain uploading & selling untested & untried firmware & hardware - what kind of company does this? How can they NOT test something to make sure it actually works before releasing it to the public?

Unbelievable  

many thanks for the heads up Ustler - nice one  

I repeat:

USE THIS FIRMWARE AT YOUR PERIL

@Bitmain - really? I mean, REALLY?

It's bad enough waiting over 9 weeks for the promised S2 firmware, but uploading this obviously untested piece of garbage for everyone to brick their S3 with is just stunning. Spectacular even......

[Ustler]

29 Antminers seems like a pain..

If you want, i can come up with a faster method for you to fix. Could just host the file somewhere so you just need to perform a wget and replace.

Note: Not to take sides, but this kind of error is somewhat understandable. Bitmain probably got all the functionality working and went back in and added some instructions to the file, but didn't think to test after adding the instructions.

Additional side note: This looks like the Antminer C1 firmware based on the fact it references 4x fans. Probably was pushed out ahead of the Antminer C1 to address the complaining about cgminer 4.6.1 not be present in the S3 firmware.

[PatMan]

I've noticed with this firmware that if I change the --queue setting at all, cgminer won't start, meaning I'm stuck with the ridiculously high standard setting. I'll try wget ck's update on top of this firmware to see if that will let me change the queue setting - otherwise I'll go back to the older firmware I reckon.

There is no excuse for not testing firmware thoroughly, none at all......

[faetos]

Mine ain't broke so I ain't fixin 'em.

[Ustler]

As promised, quicker way to fix config page issue

1)Putty into S3
2)Paste the code in below.. Will replace Save&Apply with Save&Apply.

Code:

sed -i 's/Save\&Apply/Save\&Apply/g' /usr/lib/lua/luci/model/cbi/cgminer/cgminer.lua

[BennyTheBall]

As promised, quicker way to fix config page issue

1)Putty into S3
2)Paste the code in below.. Will replace Save&Apply with Save&Apply.

Code:

sed -i 's/Save\&Apply/Save\&Apply/g' /usr/lib/lua/luci/model/cbi/cgminer/cgminer.lua

Thanks for this. Just updated one of my Batch 1 S3s, applied the line above and everything works great!

One question, what values would/should/could be entered in that new 'Voltage' field for the S3? And what effect would these values have on the operation?

[kabopar]

As promised, quicker way to fix config page issue

1)Putty into S3
2)Paste the code in below.. Will replace Save&Apply with Save&Apply.

Code:

sed -i 's/Save\&Apply/Save\&Apply/g' /usr/lib/lua/luci/model/cbi/cgminer/cgminer.lua

Thanks for this. Just updated one of my Batch 1 S3s, applied the line above and everything works great!

One question, what values would/should/could be entered in that new 'Voltage' field for the S3? And what effect would these values have on the operation?

+1, tried it on one S3 and it works.  Thanks Ustler!
It is also read correctly by AntMonitor.
I have the same question about the Voltage field - does it apply to S3 or is it in the same category as the support for 2 extra 'phantom' fans?

Cheers

[Ustler]

@BennyTheBall:

I have no idea with the values for voltage.. I wouldn't mess with the field without Bitmain commenting.


Edit: Was incorrect about my speculation regarding the C1.. The voltage value can be seen in the S4 manual on page 5

https://bitmaintech.com/files/download/Antminer%20S4%20Manual_EN_2014.9.29.pdf

Bitmain probably never intended the voltage to show up on S3's

[nst6563]

As promised, quicker way to fix config page issue

1)Putty into S3
2)Paste the code in below.. Will replace Save&Apply with Save&Apply.

Code:

sed -i 's/Save\&Apply/Save\&Apply/g' /usr/lib/lua/luci/model/cbi/cgminer/cgminer.lua

Thanks for this. Just updated one of my Batch 1 S3s, applied the line above and everything works great!

One question, what values would/should/could be entered in that new 'Voltage' field for the S3? And what effect would these values have on the operation?

From digging around on the bitmain github and also opening the cgminer binary and checking things out, it looks like it takes a hex value.  According to the datasheet the 'max voltage' is 1.2v.  So there's plenty of headroom to mess around with if they come default at .7v (which would be something like 0x07 I imagine....I didn't find a solid example in any of the code).

[Ustler]

@nst6563:

S4 documentation details voltage field.

Probably correlates to bitmain-voltage option that can be seen in cgminer help

Code:

cgminer --help | grep voltage

[nst6563]

@nst6563:

S4 documentation details voltage field.

Probably correlates to bitmain-voltage option that can be seen in cgminer help

Code:

cgminer --help | grep voltage

Ah yes...thanks. Looks like settings 072 would give you 0.72v, and 082 would give .82v. 

I have an s3 that won't do much over 420ghs....I might give it a shot on that one.