Topic: [Guide] Dogie's Comprehensive Bitmain Antminer S3 Setup [HD] - page 3. (Read 137777 times)

Anyone else have this happen to them?

I have two S3 miners running through WIFI and also connected to only one to my computer by Ethernet cable.
I can access both WIFI miners through that 1 cable so am communicating to the second one
I guess through a bridge.

Does not matter which one I am connected to, it is the same result.
Pretty cool!

MM

Your pc must have an IP address of 192.168.1.XXX to be able to bring up the web gui interface.  Or you must change the IP address on the S3 to be YYY.ZZZ.WWW.XXX where the YYY.ZZZ.WWW parts all match your PC.

Yes, pc to miner connection. I managed to get putty to work but I cannot access the webgui on the miner.

By direct you mean straight from S3 to PC?   If so likely you need to set your PC on a static IP address aswell as there is not a DHCP server giving out address's.

So I have a feeling that is problem.  Look at how to set a static lots of good articles (guessing your windows).    And if your not comterable with that you can always use a router between them.

My S3 is set to factory default of 192.168.1.99 but I cannot connect to it via the browser using a direct connection to my pc.

What should my PC settings be?

Once you change to DHCP you need to open a browser enter 192.168.1.1 to get into your router and search for the S3 to find the IP it has assigned it.
Once you have the IP put it in a browser and you will then be able to log into your S3 again.
The reason it sits there waiting to update is you ae no longer connected to it because it was assigned an IP by your router.

Hope that helps.

Happy Mining!
 
MM

New Shortened setup version:

S3 WIFI setup including WWAN static IPs.

The info Frotz provided helped and thanks!

I could not connect through my Verizon hot spot but I have it set to static IP so I think this is the problem
and will have to change it to DHCP when I have time and try it.
The S3 did connect to another wireless network.
I followed your instructions but reduced them and included my findings not that all may matter but it worked for me in the following sequence:

S3 WIFI SETUP:

1- Starting from a factory-reset miner, log into it through Ethernet plugged directly from your computer to the miner.
Go to WAN and write down all the following addresses under your static IP of 192.168.1.99

Here is the list...
IPv4 netmask:
IPv4 gateway:
IPv4 broadcast:
Use custom DNS servers:

Once you have the above 4 addresses written down...
Go to Network->Wifi, Hit Search, find your Wireless Network/Cell Phone Wifi/Wifi Extender and connect with it.  
Then go to Network->Interfaces-WWAN at the bottom and hit "Connect".
2- Even if LAN has DHCP hit apply and save anyway,
For me this generated a MAC address.
3- Go to WWAN and change DHCP to Static IP and enter the listed info above
list...
IPv4 netmask:
IPv4 gateway:
IPv4 broadcast:
Use custom DNS servers:

Hit Save and Apply.
Then go to WAN and change to DHCP
and you will begin mining.

Repeat the procedure for multiple miners with different WWAN static IPs.

Happy WIFI Mining!
 

MikeMike

When you change to DHCP the ip address of the machine changes.  You need to access the machine via its new address once you "save and apply".

2 hours on changing to DHCP?   It should be like 30 seconds or so.   Have not heard of it taking that long.

It has been a while since I have dealt with S3's.  But I don't remember any operation taking that long.

hi
sorry if this has been asked before, but......
i've got 2 x s3 here
started to configure one of them.
got the pool details in ok.
when i change the wan network over to dchp, click change protocol and then apply and save, it just sits there saying "waiting for changes to be applied"
been about 2 hours now.
it's hashing and submitting results to the pool (about 420 - 430 gh/s) but i can't set up the other one until its finished.
any idea how long it could take ??
many thanks

That's in your router's settings, google "your router's name" and "change subnet".

How do you change the subnet from .0. too .1.  I've tried everything

Well if you want try to find out what the component is and try to track some down. Then acquire them, then solder them into place. Then you'd get another dice roll at making the miner work, but there is also a very real chance that it is not the only problem.

All in all, seem like a lot of work.

While i was waiting for your reply i popped off the heatsink anyway. I could see the source of one chips problem, a crushed component labelled FB14. Looks like at some stage somebody tried to re apply the paste but over tightened the heatsink, or knocked it into components while trying to put it back.

I suspect the same is the case with the other side hash board.

I wouldn't waste your time on this, its such a small amount of hash rate that is likely unrecoverable anyway. There isn't even anything you can do for dead chips but see if it spontaneously resolves itself.

Ive tried it on an RM1000x, works fine with the other S3+. I can try it on the AX760 but i doubt the PSU is the problem.

I checked the PCI-E connectors on the hashboard to see if the maybe were damaged (pins or solder joints) but they looked fine, also im using 4 connectors so even if one on each hashboard was damaged it would still work ?

Do you think i should try reseating the outside heatsinks ?

If your PSU is good and you've tried hard restarts (from the PSU), there isn't really anything you can do about it.

Here you go !

http://i63.tinypic.com/255kjea.png

Thanks Dogie

Can you post a screenshot of the status page please?

I managed to recover an S3+ using the recovery steps on the forum (https://bitcointalksearch.org/topic/m.9902302). Which was great since it was stone dead.

Though i noticed that a whole row of 8 chips shows as (--------). Could this still be a firmware issue ? Or is something else wrong. The S3+ mines at around 300GH so definately some chips are not running.