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

They are the same:

Check the date out!
Mon Dec 2 12:01:29 2013

If it's having network issues it could cause many problems.  This is why I'm asking for screenshot of networking setting page for lan.

traceroute is the same.
traceroute: bad address 'openwrt.org'

_________________________

This is what I get when I ping "Nslookup"

Server:    127.0.0.1
Address 1: 127.0.0.1 localhost

nslookup: can't resolve 'openwrt.org': Name or service not known


_____________________________________

They will not even mine to Bitmain's default addresses....

Can you post your network settings of one not working?  I'm really wanting to see it's network setup, and DNS.

With that it could reveal something, worth a shot.

All the Miners that are not mining ping the same:

ping: bad address 'openwrt.org'

Well looks good there.  Try another pool see what happens. 

If that does not work if you can post a picture of your networking lan setup.

This is from the S3 that's mining:

PING openwrt.org (78.24.191.177): 56 data bytes
64 bytes from 78.24.191.177: seq=0 ttl=46 time=187.396 ms
64 bytes from 78.24.191.177: seq=1 ttl=46 time=194.451 ms
64 bytes from 78.24.191.177: seq=2 ttl=46 time=181.763 ms
64 bytes from 78.24.191.177: seq=3 ttl=46 time=202.497 ms
64 bytes from 78.24.191.177: seq=4 ttl=46 time=217.876 ms

--- openwrt.org ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 181.763/196.796/217.876 ms

ping: bad address 'openwrt.org'

If you go to network and then diagnostics ( I believe that is right on S3 I could be wrong).  When you try to ping something online does it show it has internet connection?

Have you tried another pool just to see?

This is one I did not flash the firmware on.

EDIT:
I tried using the same IP address and settings and cables etc. as the s3 that is running but won't mine.
Also tried hooking up an S1 but same issues.

Can you upload a screenshot of the config page?

Hi dogie,

Have a problem with my S3s.
They won't mine.
Been stored for a few months.

Set to factory default they will not mine to bitmain nor mine when setup.
I flashed to latest firmware and the red and green LEDs are always on and I do have access to it.

I tried flashing to the next oldest.
I get access but not to the setup page.
It says modify voltage and save so I flashed to the newest firmware again.
Could you give me a hand?

I was able to get an S4 running and one S3.
The next 4 S3s the same thing happens.


EDIT:
I only flashed the one S3.
The others no matter how many resets or reboots or repower they are all the same.
The green LED flashes steady but does not mine and I have full access.

EDIT#2:
I flashed the same one back to the first firmware.
The Red LED is not constantly on anymore.
But it's the same way it was before.
It will not mine and the green LED is a steady blink.

MM

Pool - GH.IO UK (yes I know what you are likely to say but I seem to have better luck here than AntPool or P2Pool - by about 15-20% even though sometimes its a long wait between blocks - a few quick blocks put you way ahead - maybe my luck will run out but thats based on one week tests of each pool).

Yes - after 9 hrs the miners are pulling an average of 450-470 GH/s (from their Antminer luci status pages) each but still ranging 380-750 GH/s in waves. 7 of 11 shifts (almost 4 hrs) displayed at GH.IO show 1TH/s or more for the 2 x S3's combined - which is pretty reasonable in my estimation.

Today I will clean up the S3 running at 55DegC overnight and see if I can get it down - otherwise might try the PuTTY again in case I made some mistake - otherwise revert to an earlier Firmware that runs at a lower frequency? UPDATE - cleaning cut 1 DegC at most (not very dusty in cooling webs but fans had a good accumulation of debris on them). Deduced that extra heat is mainly from the 250 mining Freq. that cropped up with the upgrade to Jan 2015 Firmware - so let it run.  Temp crept up to 56DegC over 4 hrs as the day warmed up - one ASIC cut out.  Decided to get serious.  Removed cover and left cover off. LOST 10DegC just like that.  How simple! Low temp - no noise and all ASICS back in action.

Cheers - usukan

What pool are you using?  It varies on pools but is this within first 30 minutes or so (some pools take longer then others to get accurate data).

But I would look at the S3's themself that is more accurate as far as speed.  Most likely the pool is showing to high after first connecting.  1.5 TH is far out of 2 S3's reach. 

(And i on a type it should be around 900 GH/S or so not MH/S .  Depending on units up to 1T or around there with 2 S3's is posssible.

Yes you may be right I think.

Had a few whiskeys and became highly risk tolerant.

Upgraded Firmwares on both S3's to Jan 2015.  Not without issues.  Had to reset my old one because upgrade had errors and thought I had bricked it. Mined for some dude in China for a while cos I could not change pool config until I flashed a compat Firmware. Reset and went back to 7/14 Firmware and flashed - then upgraded one by one - worked at each stage - sweet - but running at 55DegC now, Freq 250 (other one running at 41DegC with same settings? Freq 237?) - so yes full of dust I reckon.  But cranking GH/s.  I will dismantle and clean tomorrow.

What is the significance of "Frequency" ?  Why would one be higher/lower with same firmware? UPDATE I assume its been overclocked by past owner http://www.rubicite.com/Tutorials/AntMinerS3Tutorial.aspx
Will try and set back to Freq 237 tomorrow via PuTTY. UPDATE - PuTTY don't work - reset to 237.5, rebooted but still Freq 250?

So - end of my trials pretty much. Unless Mr Freq 250 burns out overnight.


 
1   usukan.worker2   778.26 Gh/s   
2   usukan.worker1   786.69 Gh/s      

These are S3's? Well yes? I should get 900GH/s combined if I'm, lucky - but 1.5 TH/s?  WTF  

Thanks Dogie & Real-Duke

Cheers - usukan

Maybe your old one is full of dust?

Sorry about this - but I have another observation and questions.

what is the MODEL and FIRMWARE below telling me? The new pre-owned one runs MUCH cooler and quieter than my old original?

Temperature comparison - old original 54-55 DegC - new pre-owned 39-40 DegC (fan speed and noise accordingly worse in old one).  Both in same area with ambient air temp 20 DegC. Both hashing at same rate 450-470 GH/s 1 hr average?

What is the significance of the different frequencies - between the 2 x S3's - 218.75 and 237.5?

 

I have one S3 (my old original)

Hostname    antMiner
Model    TP-Link TL-WR743N/ND v2
Firmware Version    OpenWrt Barrier Breaker r38031 / LuCI Trunk (svn-r9909)
Kernel Version   3.10.12

Frequency 218.75

and a new pre owned one

Hostname      antMiner
Model    S3
Firmware Version    Tue Aug 26 10:43:10 CST 2014
Kernel Version   3.10.12

Frequency 237.5



Should I update the firmware on my old original (OpenWrt Barrier Breaker r38031 / LuCI Trunk (svn-r9909)) - will this make it run cooler and quieter?

Even the Firmware at Aug 2014 on the new one seems old?  Should I update that to Jan 2015?

If I should update firmware - where do I get the firmware - Bitmain I guess.  But they have this below.  What should I select?  Do I have to do each one in sequence?

I assume you download these .bin files and then flash them to the miners - but should I just go direct to the most recent (antMiner_S320150109.bin) - for both S3's?

What sort of Firmware is "OpenWrt Barrier Breaker r38031 / LuCI Trunk (svn-r9909)" ? Old? new? custom? Good? bad? Does anybody know what date/version this equates to in terms of the updates available at Bitmain below?



https://bitmaintech.com/support.htm?pid=007201407180243004432lBQW28O0633

Antminer S3 - Firmware

FileName                           Description
antMiner_S320140711.bin   first version of firmware for antminer S3

antMiner_S320140721.bin   No beeper altert when there is no immediate hashing work.
                                        During the normal mining, Green LED is always on. If there is no immediate hashing work for 1 second, the Green LED will turn off. If it lasts more than 1 minute without hashing work,             green LED is kept off and beeper rings.

antMiner_S320140811.bin   add frequency advanced setting.

antMiner_S320140826.bin   support S3+
MD5: 48B2E769E1B57892B71D488711773002

antMiner_S320141013.bin   update cgminer to v4.6.1;
update miner status page; MD5: 87707C617911E6ABF0870040F773354D
antMiner_S320150109.bin   
1. fix bug of negative temperature
2. fix power mistake adjustment.
3. disable VDD adjustment function.
MD5: 3E77FC58E4CF9F6C27810C8154C8B0F9

Both miners are working fine with 450-470 GH/s 1 hour averages (only been running 1.5hrs so far).


Thanks usukan

Just to let you know all works just fine as you suggested - may help somebody else.

Changed the 2nd S3 IP address to 192.168.1.98

Can connect to both via computer at 192.168.1.99 and 192.168.1.98.

Both configured and mining 

On the router I can't find the IP's on DHCP Client table BUT they are all there on the ARP/RARP Table.

SWEET

Once again thanks

Cheers usukan


 

OK - excellent.  Most of this is new ground to me but I will work through this over the next few days when my extra S3's arrive.

Your advice is greatly appreciated.

Cheers - usukan

Yes you should change them to prevent conflicting IPs, bad things are likely to happen if you don't. Both the miners mining may be just temporary, as is your ability to control them/


Navigate to your router, find the "DHCP table" or "Client list". It will show all the devices currently managed, including your S3s as well as the IP assigned to them. Then you just whack that IP into a browser like you would have for 192.168.1.99.


In the same place you find the DHCP table, there is probably the option to click on one of the devices to get more settings. There will be something like "reserve IP" or "use the same IP".