[Guide] Dogie's Comprehensive Bitmain AntMiner S1 Setup [HD]

[steelydev]

Does anyone know the spec on the Antminer S1 antenna connector?  I can't find a definitive post.  Is it SMA or RP-SMA?  Or something else?  Thanks.

[1714160149]

1714160149

[1714160149]

1714160149

[1714160149]

1714160149

[dogie]

Does anyone know the spec on the Antminer S1 antenna connector?  I can't find a definitive post.  Is it SMA or RP-SMA?  Or something else?  Thanks.

How would we be able to tell?

[avtogen]

Does anyone know the spec on the Antminer S1 antenna connector?  I can't find a definitive post.  Is it SMA or RP-SMA?  Or something else?  Thanks.

http://imgur.com/m8yO2qG

Seems like SMA

[norgan]

Does anyone know the spec on the Antminer S1 antenna connector?  I can't find a definitive post.  Is it SMA or RP-SMA?  Or something else?  Thanks.

http://imgur.com/m8yO2qG

Seems like SMA

yeah sma, I used my spare ones off my Asus access points and it is the same as a juniper firewall. pretty standard.

[bcseb]

I'm unable to access the antminer config page.  I've tried two ip addresses - the one on the side of the miner and the one I was told by the eprson I got it from.
Really frustrating as it's powered up and seems to be working fine.
Any hints?
https://i.imgur.com/jRugKhG.png?1

[dogie]

Which are the two IPs you were told?

[bcseb]

The one on the unit is 192.168.1.99, I was told 192.168.186.200
I have tried changing my IP address to 192.168.1.XXX, but browser still wouldn't load the configuration page, and of course all internet connection was gone.
I'm still unclear whether I should be trying to plug the miner into my router, or delay that until after I've configured it, but I think I've tried every variation so far - changing IP address, through the router, straight into the PC.
Also tried a factory reset and have tried 192.268.1.99 and 198.268.186.200 just in case, again both through the router and directly to the ethernet port on the PC.
Someone suggested Wireshark, which I intend to look into tomorrow.
I appreciate all the help so far, and will keep trying.  The more suggestions I get the more avenues I can try.  This is a great forum with some really helpful people; so far the only people ho have made me feel stupid are myself and my 11 year old son.

[dogie]

The one on the unit is 192.168.1.99, I was told 192.168.186.200
I have tried changing my IP address to 192.168.1.XXX, but browser still wouldn't load the configuration page, and of course all internet connection was gone.
I'm still unclear whether I should be trying to plug the miner into my router, or delay that until after I've configured it, but I think I've tried every variation so far - changing IP address, through the router, straight into the PC.
Also tried a factory reset and have tried 192.268.1.99 and 198.268.186.200 just in case, again both through the router and directly to the ethernet port on the PC.
Someone suggested Wireshark, which I intend to look into tomorrow.
I appreciate all the help so far, and will keep trying.  The more suggestions I get the more avenues I can try.  This is a great forum with some really helpful people; so far the only people ho have made me feel stupid are myself and my 11 year old son.

If you've factory reset, plug it into the router and run an IP scanner to see where its turn up. If you see nothing, it might be sitting on another subnet (192.168.x....). You can either change router subnet and try again if its not a problem for you, or plug the S1 into a laptop and try the same.

[bcseb]

Used an IP scanner and now trying to connect via wifi in case that's easier - the miner is only about 2 feet away from the router.
IP scanner is giving the IP address as 192.168.1.99 (Paragon technologies - I assume that's the one).
Should I try temporarily changing my IPv4 address and Default gateway?  If so, what settings should I use.  I've already tried a few without success.
Whenever I try to use chrome after changing IPv4 and gateway it just says "can not connect to the internet."
I've tried just about every combination I can think of - and have even disabled my firewall for 15 minutes just in case that was interfering somehow.
I'm about to try to connect it to my son's PC upstairs and see if I can configure it there - not over optimistic at the moment though.

[kabopar]

Used an IP scanner and now trying to connect via wifi in case that's easier - the miner is only about 2 feet away from the router.
IP scanner is giving the IP address as 192.168.1.99 (Paragon technologies - I assume that's the one).
Should I try temporarily changing my IPv4 address and Default gateway?  If so, what settings should I use.  I've already tried a few without success.
Whenever I try to use chrome after changing IPv4 and gateway it just says "can not connect to the internet."
I've tried just about every combination I can think of - and have even disabled my firewall for 15 minutes just in case that was interfering somehow.
I'm about to try to connect it to my son's PC upstairs and see if I can configure it there - not over optimistic at the moment though.

Unless you want to complicate matters, connect the S1 directly to the PC with a LAN cable (no router, no Wifi) and then enter 192.168.1.99 into your browser, then you should be able to see the web gui of the Antminer, change the IP to what ever your network needs, set your mining pools etc.

(if your router supports the 192.168.1.xxx address range, you can do it through the router, assuming that there is no other device at 192.168.1.99).

Cheers

[bcseb]

Used an IP scanner and now trying to connect via wifi in case that's easier - the miner is only about 2 feet away from the router.
IP scanner is giving the IP address as 192.168.1.99 (Paragon technologies - I assume that's the one).
Should I try temporarily changing my IPv4 address and Default gateway?  If so, what settings should I use.  I've already tried a few without success.
Whenever I try to use chrome after changing IPv4 and gateway it just says "can not connect to the internet."
I've tried just about every combination I can think of - and have even disabled my firewall for 15 minutes just in case that was interfering somehow.
I'm about to try to connect it to my son's PC upstairs and see if I can configure it there - not over optimistic at the moment though.

Change the ipaddress of your PC to 192.168.1.10 then plug an Ethernet cable to the ant. Then browse to 192 168.1.99. From there go check the IP assigned to wifi and revert your PC back and use that address to connect.

I tried this and it worked.  Have since reset the IP address of the miner, and now all is purring away prettily.
Thanks to everyone for their help, and also to those who just read my posts.  Maybe someone else will find this helpful in the future.
 

[bcseb]

Used an IP scanner and now trying to connect via wifi in case that's easier - the miner is only about 2 feet away from the router.
IP scanner is giving the IP address as 192.168.1.99 (Paragon technologies - I assume that's the one).
Should I try temporarily changing my IPv4 address and Default gateway?  If so, what settings should I use.  I've already tried a few without success.
Whenever I try to use chrome after changing IPv4 and gateway it just says "can not connect to the internet."
I've tried just about every combination I can think of - and have even disabled my firewall for 15 minutes just in case that was interfering somehow.
I'm about to try to connect it to my son's PC upstairs and see if I can configure it there - not over optimistic at the moment though.

Unless you want to complicate matters, connect the S1 directly to the PC with a LAN cable (no router, no Wifi) and then enter 192.168.1.99 into your browser, then you should be able to see the web gui of the Antminer, change the IP to what ever your network needs, set your mining pools etc.

(if your router supports the 192.168.1.xxx address range, you can do it through the router, assuming that there is no other device at 192.168.1.99).

Cheers

Thanks Kabopar - that is pretty much what I tried yesterday.  For some reason I still don't understand I had to change my PC IP address to 192.168.1.10, all other variations of...1.xxx didn't work.
Once I finally got up the interface I changed the IP address of the miner, and all is working now (touch wood).

[lazlopanaflex]

Its pretty close but sounds okay.

Cool, ty sir (and thx for all the great guides )

[J_Dubbs]

My oldest Antminer has been a real pain lately. A few weeks ago I had to move it, have always had it on WiFi, and occasionally it would fall off the network, or basically stop hashing and beep, and I'd have to reboot it. Recently it started doing this a lot more, and I did a factory reset and used an Ethernet cable instead of WiFi- still having issues with it! Here's the log, does anyone know how to read this??

Log pasted into quote box, ends with "timed out":

Thu Jul 17 11:03:27 2014 kern.info kernel: [ 72.110000] wlan0: associate with 00:0f:66:aa:02:f5 (try 1/3) Thu Jul 17 11:03:27 2014 kern.info kernel: [ 72.200000] wlan0: associate with 00:0f:66:aa:02:f5 (try 2/3) Thu Jul 17 11:03:27 2014 kern.info kernel: [ 72.300000] wlan0: associate with 00:0f:66:aa:02:f5 (try 3/3) Thu Jul 17 11:03:27 2014 kern.info kernel: [ 72.360000] wlan0: association with 00:0f:66:aa:02:f5 timed out Thu Jul 17 11:03:29 2014 cron.err crond[575]: time disparity of 1534 minutes detected Thu Jul 17 11:03:37 2014 kern.info kernel: [ 82.130000] wlan0: authenticate with 00:0f:66:aa:02:f5 Thu Jul 17 11:03:37 2014 kern.info kernel: [ 82.160000] wlan0: send auth to 00:0f:66:aa:02:f5 (try 1/3) Thu Jul 17 11:03:37 2014 kern.info kernel: [ 82.170000] wlan0: authenticated Thu Jul 17 11:03:37 2014 kern.info kernel: [ 82.180000] ath9k ar933x_wmac wlan0: disabling HT/VHT due to WEP/TKIP use Thu Jul 17 11:03:37 2014 kern.info kernel: [ 82.180000] ath9k ar933x_wmac wlan0: disabling HT as WMM/QoS is not supported by the AP Thu Jul 17 11:03:37 2014 kern.info kernel: [ 82.190000] ath9k ar933x_wmac wlan0: disabling VHT as WMM/QoS is not supported by the AP Thu Jul 17 11:03:37 2014 kern.info kernel: [ 82.210000] wlan0: associate with 00:0f:66:aa:02:f5 (try 1/3) Thu Jul 17 11:03:37 2014 kern.info kernel: [ 82.300000] wlan0: associate with 00:0f:66:aa:02:f5 (try 2/3) Thu Jul 17 11:03:37 2014 kern.info kernel: [ 82.360000] wlan0: associate with 00:0f:66:aa:02:f5 (try 3/3) Thu Jul 17 11:03:37 2014 kern.info kernel: [ 82.430000] wlan0: association with 00:0f:66:aa:02:f5 timed out Thu Jul 17 11:03:43 2014 kern.info kernel: [ 87.630000] wlan0: authenticate with 00:0f:66:aa:02:f5 Thu Jul 17 11:03:43 2014 kern.info kernel: [ 87.660000] wlan0: direct probe to 00:0f:66:aa:02:f5 (try 1/3) Thu Jul 17 11:03:43 2014 kern.info kernel: [ 87.880000] wlan0: direct probe to 00:0f:66:aa:02:f5 (try 2/3) Thu Jul 17 11:03:43 2014 kern.info kernel: [ 88.090000] wlan0: direct probe to 00:0f:66:aa:02:f5 (try 3/3) Thu Jul 17 11:03:43 2014 kern.info kernel: [ 88.300000] wlan0: authentication with 00:0f:66:aa:02:f5 timed out Thu Jul 17 11:03:54 2014 kern.info kernel: [ 99.070000] wlan0: authenticate with 00:0f:66:aa:02:f5 Thu Jul 17 11:03:54 2014 kern.info kernel: [ 99.100000] wlan0: send auth to 00:0f:66:aa:02:f5 (try 1/3) Thu Jul 17 11:03:54 2014 kern.info kernel: [ 99.150000] wlan0: authenticated Thu Jul 17 11:03:54 2014 kern.info kernel: [ 99.180000] ath9k ar933x_wmac wlan0: disabling HT/VHT due to WEP/TKIP use Thu Jul 17 11:03:54 2014 kern.info kernel: [ 99.180000] ath9k ar933x_wmac wlan0: disabling HT as WMM/QoS is not supported by the AP Thu Jul 17 11:03:54 2014 kern.info kernel: [ 99.190000] ath9k ar933x_wmac wlan0: disabling VHT as WMM/QoS is not supported by the AP Thu Jul 17 11:03:54 2014 kern.info kernel: [ 99.210000] wlan0: associate with 00:0f:66:aa:02:f5 (try 1/3) Thu Jul 17 11:03:54 2014 kern.info kernel: [ 99.220000] wlan0: RX AssocResp from 00:0f:66:aa:02:f5 (capab=0x411 status=0 aid=3) Thu Jul 17 11:03:54 2014 kern.info kernel: [ 99.220000] wlan0: associated Thu Jul 17 11:05:44 2014 kern.info kernel: [ 209.100000] wlan0: deauthenticated from 00:0f:66:aa:02:f5 (Reason: 7) Thu Jul 17 11:05:45 2014 kern.info kernel: [ 210.350000] wlan0: authenticate with 00:0f:66:aa:02:f5 Thu Jul 17 11:05:45 2014 kern.info kernel: [ 210.380000] wlan0: send auth to 00:0f:66:aa:02:f5 (try 1/3) Thu Jul 17 11:05:45 2014 kern.info kernel: [ 210.440000] wlan0: authenticated Thu Jul 17 11:05:45 2014 kern.info kernel: [ 210.440000] ath9k ar933x_wmac wlan0: disabling HT/VHT due to WEP/TKIP use Thu Jul 17 11:05:45 2014 kern.info kernel: [ 210.440000] ath9k ar933x_wmac wlan0: disabling HT as WMM/QoS is not supported by the AP Thu Jul 17 11:05:45 2014 kern.info kernel: [ 210.450000] ath9k ar933x_wmac wlan0: disabling VHT as WMM/QoS is not supported by the AP Thu Jul 17 11:05:45 2014 kern.info kernel: [ 210.470000] wlan0: associate with 00:0f:66:aa:02:f5 (try 1/3) Thu Jul 17 11:05:45 2014 kern.info kernel: [ 210.480000] wlan0: RX AssocResp from 00:0f:66:aa:02:f5 (capab=0x411 status=0 aid=3) Thu Jul 17 11:05:45 2014 kern.info kernel: [ 210.490000] wlan0: associated Thu Jul 17 11:06:01 2014 cron.info crond[575]: crond: USER root pid 1174 cmd /usr/bin/cgminer-monitor Thu Jul 17 11:09:01 2014 cron.info crond[575]: crond: USER root pid 1192 cmd /usr/bin/cgminer-monitor Thu Jul 17 11:10:51 2014 kern.info kernel: [ 515.850000] wlan0: deauthenticated from 00:0f:66:aa:02:f5 (Reason: 7) Thu Jul 17 11:10:52 2014 kern.info kernel: [ 517.100000] wlan0: authenticate with 00:0f:66:aa:02:f5 Thu Jul 17 11:10:52 2014 kern.info kernel: [ 517.130000] wlan0: send auth to 00:0f:66:aa:02:f5 (try 1/3) Thu Jul 17 11:10:52 2014 kern.info kernel: [ 517.230000] wlan0: send auth to 00:0f:66:aa:02:f5 (try 2/3) Thu Jul 17 11:10:52 2014 kern.info kernel: [ 517.310000] wlan0: send auth to 00:0f:66:aa:02:f5 (try 3/3) Thu Jul 17 11:10:52 2014 kern.info kernel: [ 517.410000] wlan0: authentication with 00:0f:66:aa:02:f5 timed out Thu Jul 17 11:10:56 2014 kern.info kernel: [ 520.800000] wlan0: authenticate with 00:0f:66:aa:02:f5 Thu Jul 17 11:10:56 2014 kern.info kernel: [ 520.830000] wlan0: direct probe to 00:0f:66:aa:02:f5 (try 1/3) Thu Jul 17 11:10:56 2014 kern.info kernel: [ 521.050000] wlan0: direct probe to 00:0f:66:aa:02:f5 (try 2/3) Thu Jul 17 11:10:56 2014 kern.info kernel: [ 521.260000] wlan0: direct probe to 00:0f:66:aa:02:f5 (try 3/3) Thu Jul 17 11:10:56 2014 kern.info kernel: [ 521.470000] wlan0: authentication with 00:0f:66:aa:02:f5 timed out Thu Jul 17 11:11:06 2014 kern.info kernel: [ 530.540000] wlan0: authenticate with 00:0f:66:aa:02:f5 Thu Jul 17 11:11:06 2014 kern.info kernel: [ 530.570000] wlan0: send auth to 00:0f:66:aa:02:f5 (try 1/3) Thu Jul 17 11:11:06 2014 kern.info kernel: [ 530.580000] wlan0: authenticated Thu Jul 17 11:11:06 2014 kern.info kernel: [ 530.580000] ath9k ar933x_wmac wlan0: disabling HT/VHT due to WEP/TKIP use Thu Jul 17 11:11:06 2014 kern.info kernel: [ 530.590000] ath9k ar933x_wmac wlan0: disabling HT as WMM/QoS is not supported by the AP Thu Jul 17 11:11:06 2014 kern.info kernel: [ 530.590000] ath9k ar933x_wmac wlan0: disabling VHT as WMM/QoS is not supported by the AP Thu Jul 17 11:11:06 2014 kern.info kernel: [ 530.610000] wlan0: associate with 00:0f:66:aa:02:f5 (try 1/3) Thu Jul 17 11:11:06 2014 kern.info kernel: [ 530.640000] wlan0: RX AssocResp from 00:0f:66:aa:02:f5 (capab=0x411 status=0 aid=3) Thu Jul 17 11:11:06 2014 kern.info kernel: [ 530.650000] wlan0: associated Thu Jul 17 11:12:01 2014 cron.info crond[575]: crond: USER root pid 1276 cmd /usr/bin/cgminer-monitor Thu Jul 17 11:12:50 2014 kern.info kernel: [ 635.410000] wlan0: deauthenticated from 00:0f:66:aa:02:f5 (Reason: 7) Thu Jul 17 11:12:52 2014 kern.info kernel: [ 636.690000] wlan0: authenticate with 00:0f:66:aa:02:f5 Thu Jul 17 11:12:52 2014 kern.info kernel: [ 636.720000] wlan0: send auth to 00:0f:66:aa:02:f5 (try 1/3) Thu Jul 17 11:12:52 2014 kern.info kernel: [ 636.740000] wlan0: authenticated Thu Jul 17 11:12:52 2014 kern.info kernel: [ 636.740000] ath9k ar933x_wmac wlan0: disabling HT/VHT due to WEP/TKIP use Thu Jul 17 11:12:52 2014 kern.info kernel: [ 636.740000] ath9k ar933x_wmac wlan0: disabling HT as WMM/QoS is not supported by the AP Thu Jul 17 11:12:52 2014 kern.info kernel: [ 636.750000] ath9k ar933x_wmac wlan0: disabling VHT as WMM/QoS is not supported by the AP Thu Jul 17 11:12:52 2014 kern.info kernel: [ 636.770000] wlan0: associate with 00:0f:66:aa:02:f5 (try 1/3) Thu Jul 17 11:12:52 2014 kern.info kernel: [ 636.890000] wlan0: RX AssocResp from 00:0f:66:aa:02:f5 (capab=0x411 status=0 aid=3) Thu Jul 17 11:12:52 2014 kern.info kernel: [ 636.900000] wlan0: associated Thu Jul 17 11:14:07 2014 kern.info kernel: [ 712.110000] wlan0: deauthenticated from 00:0f:66:aa:02:f5 (Reason: 7) Thu Jul 17 11:14:08 2014 kern.info kernel: [ 713.470000] eth1: link down Thu Jul 17 11:14:10 2014 kern.info kernel: [ 715.060000] wlan0: authenticate with 00:0f:66:aa:02:f5 Thu Jul 17 11:14:10 2014 kern.info kernel: [ 715.090000] wlan0: direct probe to 00:0f:66:aa:02:f5 (try 1/3) Thu Jul 17 11:14:10 2014 kern.info kernel: [ 715.310000] wlan0: direct probe to 00:0f:66:aa:02:f5 (try 2/3) Thu Jul 17 11:14:11 2014 kern.info kernel: [ 715.520000] wlan0: direct probe to 00:0f:66:aa:02:f5 (try 3/3) Thu Jul 17 11:14:11 2014 kern.info kernel: [ 715.730000] wlan0: authentication with 00:0f:66:aa:02:f5 timed out Thu Jul 17 11:14:11 2014 kern.info kernel: [ 716.470000] eth1: link up (100Mbps/Full duplex) Thu Jul 17 11:14:12 2014 kern.info kernel: [ 717.420000] wlan0: authenticate with 00:0f:66:aa:02:f5 Thu Jul 17 11:14:12 2014 kern.info kernel: [ 717.450000] wlan0: send auth to 00:0f:66:aa:02:f5 (try 1/3) Thu Jul 17 11:14:13 2014 kern.info kernel: [ 717.470000] wlan0: authenticated Thu Jul 17 11:14:13 2014 kern.info kernel: [ 717.470000] ath9k ar933x_wmac wlan0: disabling HT/VHT due to WEP/TKIP use Thu Jul 17 11:14:13 2014 kern.info kernel: [ 717.480000] ath9k ar933x_wmac wlan0: disabling HT as WMM/QoS is not supported by the AP Thu Jul 17 11:14:13 2014 kern.info kernel: [ 717.490000] ath9k ar933x_wmac wlan0: disabling VHT as WMM/QoS is not supported by the AP Thu Jul 17 11:14:13 2014 kern.info kernel: [ 717.500000] wlan0: associate with 00:0f:66:aa:02:f5 (try 1/3) Thu Jul 17 11:14:13 2014 kern.info kernel: [ 717.500000] wlan0: RX AssocResp from 00:0f:66:aa:02:f5 (capab=0x411 status=0 aid=3) Thu Jul 17 11:14:13 2014 kern.info kernel: [ 717.510000] wlan0: associated Thu Jul 17 11:15:01 2014 cron.info crond[575]: crond: USER root pid 1395 cmd /usr/bin/cgminer-monitor Thu Jul 17 11:15:09 2014 kern.info kernel: [ 774.370000] wlan0: authenticate with 00:0f:66:aa:02:f5 Thu Jul 17 11:15:09 2014 kern.info kernel: [ 774.390000] wlan0: send auth to 00:0f:66:aa:02:f5 (try 1/3) Thu Jul 17 11:15:10 2014 kern.info kernel: [ 774.470000] wlan0: authenticated Thu Jul 17 11:15:10 2014 kern.info kernel: [ 774.490000] ath9k ar933x_wmac wlan0: disabling HT/VHT due to WEP/TKIP use Thu Jul 17 11:15:10 2014 kern.info kernel: [ 774.490000] ath9k ar933x_wmac wlan0: disabling HT as WMM/QoS is not supported by the AP Thu Jul 17 11:15:10 2014 kern.info kernel: [ 774.500000] ath9k ar933x_wmac wlan0: disabling VHT as WMM/QoS is not supported by the AP Thu Jul 17 11:15:10 2014 kern.info kernel: [ 774.520000] wlan0: associate with 00:0f:66:aa:02:f5 (try 1/3) Thu Jul 17 11:15:10 2014 kern.info kernel: [ 774.580000] wlan0: RX AssocResp from 00:0f:66:aa:02:f5 (capab=0x411 status=0 aid=3) Thu Jul 17 11:15:10 2014 kern.info kernel: [ 774.580000] wlan0: associated Thu Jul 17 11:18:01 2014 cron.info crond[575]: crond: USER root pid 1454 cmd /usr/bin/cgminer-monitor Thu Jul 17 11:19:09 2014 kern.info kernel: [ 1013.970000] wlan0: authenticate with 00:0f:66:aa:02:f5 Thu Jul 17 11:19:09 2014 kern.info kernel: [ 1014.000000] wlan0: send auth to 00:0f:66:aa:02:f5 (try 1/3) Thu Jul 17 11:19:09 2014 kern.info kernel: [ 1014.170000] wlan0: send auth to 00:0f:66:aa:02:f5 (try 2/3) Thu Jul 17 11:19:09 2014 kern.info kernel: [ 1014.330000] wlan0: send auth to 00:0f:66:aa:02:f5 (try 3/3) Thu Jul 17 11:19:10 2014 kern.info kernel: [ 1014.550000] wlan0: authentication with 00:0f:66:aa:02:f5 timed out Thu Jul 17 11:19:11 2014 kern.info kernel: [ 1015.750000] wlan0: authenticate with 00:0f:66:aa:02:f5 Thu Jul 17 11:19:11 2014 kern.info kernel: [ 1015.780000] wlan0: direct probe to 00:0f:66:aa:02:f5 (try 1/3) Thu Jul 17 11:19:11 2014 kern.info kernel: [ 1016.000000] wlan0: direct probe to 00:0f:66:aa:02:f5 (try 2/3) Thu Jul 17 11:19:11 2014 kern.info kernel: [ 1016.210000] wlan0: direct probe to 00:0f:66:aa:02:f5 (try 3/3) Thu Jul 17 11:19:11 2014 kern.info kernel: [ 1016.420000] wlan0: authentication with 00:0f:66:aa:02:f5 timed out Thu Jul 17 11:19:15 2014 kern.info kernel: [ 1019.800000] wlan0: authenticate with 00:0f:66:aa:02:f5 Thu Jul 17 11:19:15 2014 kern.info kernel: [ 1019.830000] wlan0: direct probe to 00:0f:66:aa:02:f5 (try 1/3) Thu Jul 17 11:19:15 2014 kern.info kernel: [ 1020.050000] wlan0: direct probe to 00:0f:66:aa:02:f5 (try 2/3) Thu Jul 17 11:19:15 2014 kern.info kernel: [ 1020.260000] wlan0: direct probe to 00:0f:66:aa:02:f5 (try 3/3) Thu Jul 17 11:19:15 2014 kern.info kernel: [ 1020.470000] wlan0: authentication with 00:0f:66:aa:02:f5 timed out Thu Jul 17 11:19:25 2014 kern.info kernel: [ 1029.540000] wlan0: authenticate with 00:0f:66:aa:02:f5 Thu Jul 17 11:19:25 2014 kern.info kernel: [ 1029.570000] wlan0: direct probe to 00:0f:66:aa:02:f5 (try 1/3) Thu Jul 17 11:19:25 2014 kern.info kernel: [ 1029.790000] wlan0: direct probe to 00:0f:66:aa:02:f5 (try 2/3) Thu Jul 17 11:19:25 2014 kern.info kernel: [ 1030.000000] wlan0: direct probe to 00:0f:66:aa:02:f5 (try 3/3) Thu Jul 17 11:19:25 2014 kern.info kernel: [ 1030.210000] wlan0: authentication with 00:0f:66:aa:02:f5 timed out Thu Jul 17 11:19:46 2014 kern.info kernel: [ 1051.040000] wlan0: authenticate with 00:0f:66:aa:02:f5 Thu Jul 17 11:19:46 2014 kern.info kernel: [ 1051.070000] wlan0: direct probe to 00:0f:66:aa:02:f5 (try 1/3) Thu Jul 17 11:19:46 2014 kern.info kernel: [ 1051.290000] wlan0: direct probe to 00:0f:66:aa:02:f5 (try 2/3) Thu Jul 17 11:19:47 2014 kern.info kernel: [ 1051.500000] wlan0: direct probe to 00:0f:66:aa:02:f5 (try 3/3) Thu Jul 17 11:19:47 2014 kern.info kernel: [ 1051.710000] wlan0: authentication with 00:0f:66:aa:02:f5 timed out Thu Jul 17 11:20:08 2014 kern.info kernel: [ 1072.550000] wlan0: authenticate with 00:0f:66:aa:02:f5 Thu Jul 17 11:20:08 2014 kern.info kernel: [ 1072.570000] wlan0: direct probe to 00:0f:66:aa:02:f5 (try 1/3) Thu Jul 17 11:20:08 2014 kern.info kernel: [ 1072.790000] wlan0: direct probe to 00:0f:66:aa:02:f5 (try 2/3) Thu Jul 17 11:20:08 2014 kern.info kernel: [ 1073.000000] wlan0: direct probe to 00:0f:66:aa:02:f5 (try 3/3) Thu Jul 17 11:20:08 2014 kern.info kernel: [ 1073.210000] wlan0: authentication with 00:0f:66:aa:02:f5 timed out Thu Jul 17 11:20:29 2014 kern.info kernel: [ 1094.050000] wlan0: authenticate with 00:0f:66:aa:02:f5 Thu Jul 17 11:20:29 2014 kern.info kernel: [ 1094.070000] wlan0: direct probe to 00:0f:66:aa:02:f5 (try 1/3) Thu Jul 17 11:20:29 2014 kern.info kernel: [ 1094.290000] wlan0: direct probe to 00:0f:66:aa:02:f5 (try 2/3) Thu Jul 17 11:20:30 2014 kern.info kernel: [ 1094.500000] wlan0: direct probe to 00:0f:66:aa:02:f5 (try 3/3) Thu Jul 17 11:20:30 2014 kern.info kernel: [ 1094.710000] wlan0: authentication with 00:0f:66:aa:02:f5 timed out Thu Jul 17 11:20:51 2014 kern.info kernel: [ 1115.550000] wlan0: authenticate with 00:0f:66:aa:02:f5 Thu Jul 17 11:20:51 2014 kern.info kernel: [ 1115.570000] wlan0: direct probe to 00:0f:66:aa:02:f5 (try 1/3) Thu Jul 17 11:20:51 2014 kern.info kernel: [ 1115.790000] wlan0: direct probe to 00:0f:66:aa:02:f5 (try 2/3) Thu Jul 17 11:20:51 2014 kern.info kernel: [ 1116.000000] wlan0: direct probe to 00:0f:66:aa:02:f5 (try 3/3) Thu Jul 17 11:20:51 2014 kern.info kernel: [ 1116.210000] wlan0: authentication with 00:0f:66:aa:02:f5 timed out Thu Jul 17 11:21:01 2014 cron.info crond[575]: crond: USER root pid 1592 cmd /usr/bin/cgminer-monitor Thu Jul 17 11:21:21 2014 kern.info kernel: [ 1145.490000] wlan0: authenticate with 00:0f:66:aa:02:f5 Thu Jul 17 11:21:21 2014 kern.info kernel: [ 1145.520000] wlan0: direct probe to 00:0f:66:aa:02:f5 (try 1/3) Thu Jul 17 11:21:21 2014 kern.info kernel: [ 1145.740000] wlan0: direct probe to 00:0f:66:aa:02:f5 (try 2/3) Thu Jul 17 11:21:21 2014 kern.info kernel: [ 1145.950000] wlan0: direct probe to 00:0f:66:aa:02:f5 (try 3/3) Thu Jul 17 11:21:21 2014 kern.info kernel: [ 1146.160000] wlan0: authentication with 00:0f:66:aa:02:f5 timed out Thu Jul 17 11:21:52 2014 kern.info kernel: [ 1177.130000] wlan0: authenticate with 00:0f:66:aa:02:f5 Thu Jul 17 11:21:52 2014 kern.info kernel: [ 1177.160000] wlan0: direct probe to 00:0f:66:aa:02:f5 (try 1/3) Thu Jul 17 11:21:52 2014 kern.info kernel: [ 1177.380000] wlan0: direct probe to 00:0f:66:aa:02:f5 (try 2/3) Thu Jul 17 11:21:53 2014 kern.info kernel: [ 1177.590000] wlan0: direct probe to 00:0f:66:aa:02:f5 (try 3/3) Thu Jul 17 11:21:53 2014 kern.info kernel: [ 1177.800000] wlan0: authentication with 00:0f:66:aa:02:f5 timed out Thu Jul 17 11:22:24 2014 kern.info kernel: [ 1208.770000] wlan0: authenticate with 00:0f:66:aa:02:f5 Thu Jul 17 11:22:24 2014 kern.info kernel: [ 1208.800000] wlan0: direct probe to 00:0f:66:aa:02:f5 (try 1/3) Thu Jul 17 11:22:24 2014 kern.info kernel: [ 1209.020000] wlan0: direct probe to 00:0f:66:aa:02:f5 (try 2/3) Thu Jul 17 11:22:24 2014 kern.info kernel: [ 1209.230000] wlan0: direct probe to 00:0f:66:aa:02:f5 (try 3/3) Thu Jul 17 11:22:24 2014 kern.info kernel: [ 1209.440000] wlan0: authentication with 00:0f:66:aa:02:f5 timed out Thu Jul 17 11:22:54 2014 kern.info kernel: [ 1238.720000] wlan0: authenticate with 00:0f:66:aa:02:f5 Thu Jul 17 11:22:54 2014 kern.info kernel: [ 1238.750000] wlan0: direct probe to 00:0f:66:aa:02:f5 (try 1/3) Thu Jul 17 11:22:54 2014 kern.info kernel: [ 1238.970000] wlan0: direct probe to 00:0f:66:aa:02:f5 (try 2/3) Thu Jul 17 11:22:54 2014 kern.info kernel: [ 1239.180000] wlan0: direct probe to 00:0f:66:aa:02:f5 (try 3/3) Thu Jul 17 11:22:54 2014 kern.info kernel: [ 1239.390000] wlan0: authentication with 00:0f:66:aa:02:f5 timed out Thu Jul 17 11:23:24 2014 kern.info kernel: [ 1268.670000] wlan0: authenticate with 00:0f:66:aa:02:f5 Thu Jul 17 11:23:24 2014 kern.info kernel: [ 1268.700000] wlan0: direct probe to 00:0f:66:aa:02:f5 (try 1/3) Thu Jul 17 11:23:24 2014 kern.info kernel: [ 1268.920000] wlan0: direct probe to 00:0f:66:aa:02:f5 (try 2/3) Thu Jul 17 11:23:24 2014 kern.info kernel: [ 1269.130000] wlan0: direct probe to 00:0f:66:aa:02:f5 (try 3/3) Thu Jul 17 11:23:24 2014 kern.info kernel: [ 1269.340000] wlan0: authentication with 00:0f:66:aa:02:f5 timed out Thu Jul 17 11:24:01 2014 cron.info crond[575]: crond: USER root pid 1782 cmd /usr/bin/cgminer-monitor Thu Jul 17 11:24:24 2014 kern.info kernel: [ 1329.040000] wlan0: authenticate with 00:0f:66:aa:02:f5 Thu Jul 17 11:24:24 2014 kern.info kernel: [ 1329.070000] wlan0: direct probe to 00:0f:66:aa:02:f5 (try 1/3) Thu Jul 17 11:24:24 2014 kern.info kernel: [ 1329.290000] wlan0: direct probe to 00:0f:66:aa:02:f5 (try 2/3) Thu Jul 17 11:24:25 2014 kern.info kernel: [ 1329.500000] wlan0: direct probe to 00:0f:66:aa:02:f5 (try 3/3) Thu Jul 17 11:24:25 2014 kern.info kernel: [ 1329.710000] wlan0: authentication with 00:0f:66:aa:02:f5 timed out Thu Jul 17 11:25:25 2014 kern.info kernel: [ 1389.770000] wlan0: authenticate with 00:0f:66:aa:02:f5 Thu Jul 17 11:25:25 2014 kern.info kernel: [ 1389.800000] wlan0: send auth to 00:0f:66:aa:02:f5 (try 1/3) Thu Jul 17 11:25:25 2014 kern.info kernel: [ 1389.980000] wlan0: send auth to 00:0f:66:aa:02:f5 (try 2/3) Thu Jul 17 11:25:25 2014 kern.info kernel: [ 1390.170000] wlan0: send auth to 00:0f:66:aa:02:f5 (try 3/3) Thu Jul 17 11:25:25 2014 kern.info kernel: [ 1390.370000] wlan0: authentication with 00:0f:66:aa:02:f5 timed out

It seems like on the Ethernet cable it will hop back online on it's own, but with the WiFi once it falls off I need to reboot the miner or the router, sometimes both.

[J_Dubbs]

Bump- anyone able to help with the above issue?

[dogie]

S1s will do this, especially as they get old. There is an auto S1 restarted somewhere on the forums which will monitor and auto reboot any S1s that go down.

[J_Dubbs]

S1s will do this, especially as they get old. There is an auto S1 restarted somewhere on the forums which will monitor and auto reboot any S1s that go down.

I think it might have been a heat issue. I blasted it with air and mounted it a bit different so the fan was less obstructed and it seems to be solid, for now at least.

[Sickler]

This should really help me get started, thanks!

[norgan]

S1s will do this, especially as they get old. There is an auto S1 restarted somewhere on the forums which will monitor and auto reboot any S1s that go down.

I think it might have been a heat issue. I blasted it with air and mounted it a bit different so the fan was less obstructed and it seems to be solid, for now at least.

I found that when getting a bit hot and overclocking that i'd get logs like that.

[pokeyjones]

HELP!

My other 3 AntMiner S1s are happily running offsite. Just picked up 3 machines with a single power supply.

Need the simple cable diagram for hooking them up. They've been run before, should be close to plug and play. Going to reset the miners before attempting to log in and do that work.

Each miner has 2 CAT-5 Jacks, where do each of those go? One per to the router/internuts connection? I have a 5 port hub, use that?

you guys rock. thanks!