fouad
Newbie
 Offline
Activity: 2
Merit: 0
|
 |
March 11, 2014, 07:57:43 PM |
|
Hi all,
I receive the following message when I try to connect to the miner.
LuCI - LUA Configuration Interfac (blanc screen)
Can someone help me please?
|
|
|
|
|
|
S4VV4S
|
|
March 11, 2014, 08:38:14 PM |
|
Hi all,
I receive the following message when I try to connect to the miner.
LuCI - LUA Configuration Interfac (blanc screen)
Can someone help me please?
For some reason you have not actually accessed the interface. Try a reload and give it a minute. |
|
|
|
|
|
freebit13
|
|
March 11, 2014, 08:48:17 PM |
|
Hi all,
I receive the following message when I try to connect to the miner.
LuCI - LUA Configuration Interfac (blanc screen)
Can someone help me please?
Your IP address has probably changed and it's loading a cached page... press ctrl+F5 to reload the screen. If nothing shows up you are going to need an ip scanner to find the ip of your miner. |
Decentralize EVERYTHING!
|
|
|
|
Cheeseater
|
|
March 11, 2014, 09:55:11 PM |
|
Hi, have and Ant that just started to shut down on me. This morning I noticed the green led's on the outer blades were both off. The Wrt board lights were still on and the ethernet lights were flashing as normal. Tried to log into it but couldn't. Did a reboot and all was well, just got home and the same problem. Anyone else had this happen or have any ideas? I'll log in now and see if anything looks weird. Thanks
|
|
|
|
|
|
S4VV4S
|
|
March 11, 2014, 10:06:27 PM |
|
Hi, have and Ant that just started to shut down on me. This morning I noticed the green led's on the outer blades were both off. The Wrt board lights were still on and the ethernet lights were flashing as normal. Tried to log into it but couldn't. Did a reboot and all was well, just got home and the same problem. Anyone else had this happen or have any ideas? I'll log in now and see if anything looks weird. Thanks
Sounds like a PSU problem to me. What PSU are you using? |
|
|
|
|
jelin1984
Legendary
Offline
Activity: 2408
Merit: 1004
|
|
March 11, 2014, 10:09:18 PM |
|
Summary
Elapsed GH/S(5s) GH/S(avg) FoundBlocks Getworks Accepted Rejected HW Utility Discarded Stale LocalWork WU DiffA DiffR DiffS BestShare
7h 46m 44s
173.05
178.70
0
657
2,233
2
3,394
4
1,305
0
1,467,673
2,496
1,188,520
1,272
0
1,111,248
|
|
|
|
|
jelin1984
Legendary
Offline
Activity: 2408
Merit: 1004
|
|
March 11, 2014, 10:09:44 PM |
|
Hw is the hardware errors?
How must be??
|
|
|
|
|
|
Cheeseater
|
|
March 11, 2014, 10:14:59 PM |
|
Hi, have and Ant that just started to shut down on me. This morning I noticed the green led's on the outer blades were both off. The Wrt board lights were still on and the ethernet lights were flashing as normal. Tried to log into it but couldn't. Did a reboot and all was well, just got home and the same problem. Anyone else had this happen or have any ideas? I'll log in now and see if anything looks weird. Thanks
Sounds like a PSU problem to me. What PSU are you using? CX 600 393MHZ it started and was working fine compared the sys log to other ants and it was completely different. Tried logging back in and got the following /usr/lib/lua/luci/dispatcher.lua:448: Failed to execute function dispatcher target for entry '/'. The called action terminated with an exception: /usr/lib/lua/luci/sauth.lua:87: Session data invalid! stack traceback: [C]: in function 'assert' /usr/lib/lua/luci/dispatcher.lua:448: in function 'dispatch' /usr/lib/lua/luci/dispatcher.lua:195: in function </usr/lib/lua/luci/dispatcher.lua:194> |
|
|
|
|
MrTeal
Legendary
Offline
Activity: 1274
Merit: 1004
|
|
March 11, 2014, 10:17:55 PM |
|
Hw is the hardware errors?
How must be??
I wouldn't complain about 0.1% HW errors. That looks fine. |
|
|
|
|
|
wpgdeez
|
|
March 11, 2014, 10:32:33 PM |
|
These January boards seem to be flaky, getting 151 off 1 and 120 off the other. I know its not power because I disconnected 2 working ANTS and used the same PSU from them with the same results. Guess I will try a firmware update next. Hope my 5 coming next week don't have the same issue  |
|
|
|
|
|
S4VV4S
|
|
March 11, 2014, 10:37:07 PM |
|
Hi, have and Ant that just started to shut down on me. This morning I noticed the green led's on the outer blades were both off. The Wrt board lights were still on and the ethernet lights were flashing as normal. Tried to log into it but couldn't. Did a reboot and all was well, just got home and the same problem. Anyone else had this happen or have any ideas? I'll log in now and see if anything looks weird. Thanks
Sounds like a PSU problem to me. What PSU are you using? CX 600 393MHZ it started and was working fine compared the sys log to other ants and it was completely different. Tried logging back in and got the following /usr/lib/lua/luci/dispatcher.lua:448: Failed to execute function dispatcher target for entry '/'. The called action terminated with an exception: /usr/lib/lua/luci/sauth.lua:87: Session data invalid! stack traceback: [C]: in function 'assert' /usr/lib/lua/luci/dispatcher.lua:448: in function 'dispatch' /usr/lib/lua/luci/dispatcher.lua:195: in function </usr/lib/lua/luci/dispatcher.lua:194> try 375Mhz and slowly bring it up. I think that your PSU cannot handle it. Maybe a more experienced member can verify this, but I have heard that other users had probs with the cx600. Personally I use one cx750 for each and they are not even overclocked. |
|
|
|
|
|
Cheeseater
|
|
March 11, 2014, 10:40:43 PM |
|
Hi, have and Ant that just started to shut down on me. This morning I noticed the green led's on the outer blades were both off. The Wrt board lights were still on and the ethernet lights were flashing as normal. Tried to log into it but couldn't. Did a reboot and all was well, just got home and the same problem. Anyone else had this happen or have any ideas? I'll log in now and see if anything looks weird. Thanks
Sounds like a PSU problem to me. What PSU are you using? CX 600 393MHZ it started and was working fine compared the sys log to other ants and it was completely different. Tried logging back in and got the following /usr/lib/lua/luci/dispatcher.lua:448: Failed to execute function dispatcher target for entry '/'. The called action terminated with an exception: /usr/lib/lua/luci/sauth.lua:87: Session data invalid! stack traceback: [C]: in function 'assert' /usr/lib/lua/luci/dispatcher.lua:448: in function 'dispatch' /usr/lib/lua/luci/dispatcher.lua:195: in function </usr/lib/lua/luci/dispatcher.lua:194> try 375Mhz and slowly bring it up. I think that your PSU cannot handle it. Maybe a more experienced member can verify this, but I have heard that other users had probs with the cx600. Personally I use one cx750 for each and they are not even overclocked. I'll give it a try will post the sys log after reboot I apologize in advance for the long post coming. Hopefully someone will see what it is, just got it Monday. |
|
|
|
|
|
Cheeseater
|
|
March 11, 2014, 11:17:38 PM |
|
Fri Mar 7 10:22:12 2014 daemon.notice netifd: lan (631): Sending discover...
Fri Mar 7 10:22:13 2014 daemon.info sysinit: ntpd: resolved peer 3.openwrt.pool.ntp.org to 67.18.187.111
Fri Mar 7 10:22:13 2014 daemon.info sysinit: ntpd: sent query to 67.18.187.111
Fri Mar 7 10:22:13 2014 daemon.info sysinit: ntpd: resolved peer 2.openwrt.pool.ntp.org to 129.250.35.251
Fri Mar 7 10:22:13 2014 daemon.info sysinit: ntpd: sent query to 129.250.35.251
Fri Mar 7 10:22:13 2014 daemon.info sysinit: ntpd: resolved peer 1.openwrt.pool.ntp.org to 184.105.182.7
Fri Mar 7 10:22:13 2014 daemon.info sysinit: ntpd: sent query to 184.105.182.7
Fri Mar 7 10:22:13 2014 daemon.info sysinit: ntpd: resolved peer 0.openwrt.pool.ntp.org to 184.22.97.162
Fri Mar 7 10:22:13 2014 daemon.info sysinit: ntpd: sent query to 184.22.97.162
Fri Mar 7 10:22:13 2014 daemon.info sysinit: ntpd: reply from 129.250.35.251: reach 0x01 offset 420621.609588 delay 0.028075 status 0x24 strat 2 refid 0xd133a1ee rootdelay 0.005890
Fri Mar 7 10:22:13 2014 daemon.info sysinit: ntpd: reply from 67.18.187.111: reach 0x01 offset 420621.612023 delay 0.053287 status 0x24 strat 2 refid 0x808a8dac rootdelay 0.016556
Fri Mar 7 10:22:13 2014 daemon.info sysinit: ntpd: reply from 184.22.97.162: reach 0x01 offset 420621.613557 delay 0.054871 status 0x24 strat 2 refid 0x8076190c rootdelay 0.043366
Fri Mar 7 10:22:13 2014 daemon.info sysinit: ntpd: reply from 184.105.182.7: reach 0x01 offset 420621.613231 delay 0.105110 status 0x24 strat 2 refid 0xd8dafeca rootdelay 0.001190
Fri Mar 7 10:22:14 2014 daemon.info sysinit: ntpd: sent query to 67.18.187.111
Fri Mar 7 10:22:14 2014 daemon.info sysinit: ntpd: sent query to 184.105.182.7
Fri Mar 7 10:22:14 2014 daemon.info sysinit: ntpd: reply from 67.18.187.111: reach 0x03 offset 420621.613637 delay 0.055955 status 0x24 strat 2 refid 0x808a8dac rootdelay 0.016556
Fri Mar 7 10:22:14 2014 daemon.info sysinit: ntpd: reply from 184.105.182.7: reach 0x03 offset 420621.612570 delay 0.104104 status 0x24 strat 2 refid 0xd8dafeca rootdelay 0.001190
Fri Mar 7 10:22:15 2014 daemon.info sysinit: ntpd: sent query to 67.18.187.111
Fri Mar 7 10:22:15 2014 daemon.info sysinit: ntpd: sent query to 129.250.35.251
Fri Mar 7 10:22:15 2014 daemon.info sysinit: ntpd: sent query to 184.22.97.162
Fri Mar 7 10:22:15 2014 daemon.info sysinit: ntpd: reply from 129.250.35.251: reach 0x03 offset 420621.611508 delay 0.032669 status 0x24 strat 2 refid 0xd133a1ee rootdelay 0.005890
Fri Mar 7 10:22:15 2014 daemon.info sysinit: ntpd: reply from 67.18.187.111: reach 0x07 offset 420621.613920 delay 0.057415 status 0x24 strat 2 refid 0x808a8dac rootdelay 0.016556
Fri Mar 7 10:22:15 2014 daemon.info sysinit: ntpd: reply from 184.22.97.162: reach 0x03 offset 420621.615444 delay 0.059030 status 0x24 strat 2 refid 0x8076190c rootdelay 0.043366
Fri Mar 7 10:22:16 2014 daemon.info sysinit: ntpd: sent query to 184.105.182.7
Fri Mar 7 10:22:16 2014 daemon.info sysinit: ntpd: sent query to 184.22.97.162
Fri Mar 7 10:22:16 2014 daemon.info sysinit: ntpd: reply from 184.22.97.162: reach 0x07 offset 420621.614455 delay 0.057509 status 0x24 strat 2 refid 0x8076190c rootdelay 0.043366
Fri Mar 7 10:22:16 2014 daemon.info sysinit: ntpd: reply from 184.105.182.7: reach 0x07 offset 420621.609121 delay 0.096621 status 0x24 strat 2 refid 0xd8dafeca rootdelay 0.001190
Fri Mar 7 10:22:17 2014 daemon.info sysinit: ntpd: sent query to 67.18.187.111
Fri Mar 7 10:22:17 2014 daemon.info sysinit: ntpd: sent query to 129.250.35.251
Fri Mar 7 10:22:17 2014 daemon.info sysinit: ntpd: sent query to 184.22.97.162
Fri Mar 7 10:22:17 2014 daemon.info sysinit: ntpd: reply from 129.250.35.251: reach 0x07 offset 420621.611499 delay 0.032790 status 0x24 strat 2 refid 0xd133a1ee rootdelay 0.005890
Fri Mar 7 10:22:17 2014 daemon.info sysinit: ntpd: reply from 67.18.187.111: reach 0x0f offset 420621.614046 delay 0.057432 status 0x24 strat 2 refid 0x808a8dac rootdelay 0.016556
Fri Mar 7 10:22:17 2014 daemon.info sysinit: ntpd: reply from 184.22.97.162: reach 0x0f offset 420621.615462 delay 0.059072 status 0x24 strat 2 refid 0x8076190c rootdelay 0.043366
Fri Mar 7 10:22:18 2014 daemon.info sysinit: ntpd: sent query to 67.18.187.111
Fri Mar 7 10:22:18 2014 daemon.info sysinit: ntpd: sent query to 129.250.35.251
Fri Mar 7 10:22:18 2014 daemon.info sysinit: ntpd: sent query to 184.105.182.7
Fri Mar 7 10:22:18 2014 daemon.info sysinit: ntpd: reply from 129.250.35.251: reach 0x0f offset 420621.618661 delay 0.045978 status 0x24 strat 2 refid 0xd133a1ee rootdelay 0.005890
Fri Mar 7 10:22:18 2014 daemon.info sysinit: ntpd: reply from 67.18.187.111: reach 0x1f offset 420621.621467 delay 0.071996 status 0x24 strat 2 refid 0x808a8dac rootdelay 0.016556
Fri Mar 7 10:22:18 2014 daemon.info sysinit: ntpd: reply from 184.105.182.7: reach 0x0f offset 420621.620041 delay 0.118584 status 0x24 strat 2 refid 0xd8dafeca rootdelay 0.001190
Fri Mar 7 10:22:19 2014 daemon.info sysinit: ntpd: sent query to 184.22.97.162
Fri Mar 7 10:22:19 2014 daemon.info sysinit: ntpd: reply from 184.22.97.162: reach 0x1f offset 420621.610403 delay 0.049994 status 0x24 strat 2 refid 0x8076190c rootdelay 0.043366
Fri Mar 7 10:22:20 2014 daemon.info sysinit: ntpd: sent query to 67.18.187.111
Fri Mar 7 10:22:20 2014 daemon.info sysinit: ntpd: sent query to 129.250.35.251
Fri Mar 7 10:22:20 2014 daemon.info sysinit: ntpd: sent query to 184.105.182.7
Wed Mar 12 07:12:42 2014 daemon.info sysinit: ntpd: reply from 129.250.35.251: reach 0x1f offset 420621.610769 delay 0.032257 status 0x24 strat 2 refid 0xd133a1ee rootdelay 0.005890
Wed Mar 12 07:12:42 2014 daemon.info sysinit: ntpd: setting clock to Wed Mar 12 07:12:42 CST 2014 (offset 420621.610896s)
Wed Mar 12 07:12:42 2014 daemon.info sysinit: --bitmain-options 115200:32:8:36:393.75:5f05 -o Stratum.bitcoin.cz:3333 -O -o stratum.mining.eligius.st:3334 -O 17UhZWXLyiHmPmAb4VdFweGWRYY52qjxwp:123 --api-listen --api-network
Wed Mar 12 07:12:42 2014 daemon.info sysinit: - init complete -
Wed Mar 12 07:12:42 2014 kern.info kernel: [ 33.830000] bitmain 1-1.1:1.0: USB Bitmain asic #0 now disconnected
Wed Mar 12 07:13:23 2014 cron.err crond[575]: time disparity of 7011 minutes detected
Wed Mar 12 07:15:01 2014 cron.info crond[575]: crond: USER root pid 859 cmd /usr/bin/cgminer-monitor
|
|
|
|
|
Biodom
Legendary
Offline
Activity: 3794
Merit: 3999
|
|
March 11, 2014, 11:33:09 PM |
|
Trying to use Antminer with setup on a Mac, made some initial progress. I can see the miner on my laptop when connected via direct ethernet cable.
Miner has a sticker with 192.168.1.99
I have a wireless router with internal IP addresses assigned as 10.0.1.2-31 and router address as 10.0.1.1
I saw the internal address of the miner as 10.0.1.31 using inet (program) when miner was attached to the router (initially).
External public address of the whole setup, which could be checked during browsing, is 98.201.121.X
I've got a laptop that has internal IP address 10.0.1.5 (gives the same external IP address as everything else on my network).
1. I connected miner directly to the laptop via ethernet, manually changed laptop IP to 192.168.1.254 (it did not accept 192.168.1.99 which was on the sticker), however when I entered 198.168.1.99 to a browser, laptop successfully connected to Antminer and I was able to setup mining configuration.
My question is: what I should enter in WAN and LAN setup fields on the miner considering above info?
Currently Antminer's WAN reads:
static
Addr 192.168.1.99
Mask 255.255.255.0
Gateway 192.168.1.1
IPv4 broadcast 192.168.1.255
DNS 192.168.1.1
Antminer's LAN reads: DHCP client
What do I change miner's WAN and LAN to? Should I change WAN to My external address and router (98.201.121.X and 98.201.120.X) or my internal addresses (10.0.1.1 for router and already assigned 10.0.1.31 for miner) and not touch LAN? Also my router is set to assign WAN automatically-does it mean anything for settings? Also router is set on sharing one public IP address among all devices-how this would work?
I am a noob at this, looked over dozens if not hundreds of pages on this and other forums.
Can someone help me please, especially if you set it up using Apple mac, but any help will be much appreciated.
|
|
|
|
|
|
dandirk
|
|
March 11, 2014, 11:42:54 PM |
|
What is an acceptable HW error rate?  My week old antminer is getting 3% OC'd to 393.75, was getting 6% @ 400. Temps reported by antminer are 46/45. My pool results (so far) seem close to what 200Gh/s is expected to get. Performance as reported by pool is anywhere from 175gh/s to 210gh/s. |
|
|
|
|
|
|
|
S4VV4S
|
|
March 12, 2014, 12:44:55 AM |
|
Fri Mar 7 10:22:12 2014 daemon.notice netifd: lan (631): Sending discover...
Fri Mar 7 10:22:13 2014 daemon.info sysinit: ntpd: resolved peer 3.openwrt.pool.ntp.org to 67.18.187.111
Fri Mar 7 10:22:13 2014 daemon.info sysinit: ntpd: sent query to 67.18.187.111
Fri Mar 7 10:22:13 2014 daemon.info sysinit: ntpd: resolved peer 2.openwrt.pool.ntp.org to 129.250.35.251
Fri Mar 7 10:22:13 2014 daemon.info sysinit: ntpd: sent query to 129.250.35.251
Fri Mar 7 10:22:13 2014 daemon.info sysinit: ntpd: resolved peer 1.openwrt.pool.ntp.org to 184.105.182.7
Fri Mar 7 10:22:13 2014 daemon.info sysinit: ntpd: sent query to 184.105.182.7
Fri Mar 7 10:22:13 2014 daemon.info sysinit: ntpd: resolved peer 0.openwrt.pool.ntp.org to 184.22.97.162
Fri Mar 7 10:22:13 2014 daemon.info sysinit: ntpd: sent query to 184.22.97.162
Fri Mar 7 10:22:13 2014 daemon.info sysinit: ntpd: reply from 129.250.35.251: reach 0x01 offset 420621.609588 delay 0.028075 status 0x24 strat 2 refid 0xd133a1ee rootdelay 0.005890
Fri Mar 7 10:22:13 2014 daemon.info sysinit: ntpd: reply from 67.18.187.111: reach 0x01 offset 420621.612023 delay 0.053287 status 0x24 strat 2 refid 0x808a8dac rootdelay 0.016556
Fri Mar 7 10:22:13 2014 daemon.info sysinit: ntpd: reply from 184.22.97.162: reach 0x01 offset 420621.613557 delay 0.054871 status 0x24 strat 2 refid 0x8076190c rootdelay 0.043366
Fri Mar 7 10:22:13 2014 daemon.info sysinit: ntpd: reply from 184.105.182.7: reach 0x01 offset 420621.613231 delay 0.105110 status 0x24 strat 2 refid 0xd8dafeca rootdelay 0.001190
Fri Mar 7 10:22:14 2014 daemon.info sysinit: ntpd: sent query to 67.18.187.111
Fri Mar 7 10:22:14 2014 daemon.info sysinit: ntpd: sent query to 184.105.182.7
Fri Mar 7 10:22:14 2014 daemon.info sysinit: ntpd: reply from 67.18.187.111: reach 0x03 offset 420621.613637 delay 0.055955 status 0x24 strat 2 refid 0x808a8dac rootdelay 0.016556
Fri Mar 7 10:22:14 2014 daemon.info sysinit: ntpd: reply from 184.105.182.7: reach 0x03 offset 420621.612570 delay 0.104104 status 0x24 strat 2 refid 0xd8dafeca rootdelay 0.001190
Fri Mar 7 10:22:15 2014 daemon.info sysinit: ntpd: sent query to 67.18.187.111
Fri Mar 7 10:22:15 2014 daemon.info sysinit: ntpd: sent query to 129.250.35.251
Fri Mar 7 10:22:15 2014 daemon.info sysinit: ntpd: sent query to 184.22.97.162
Fri Mar 7 10:22:15 2014 daemon.info sysinit: ntpd: reply from 129.250.35.251: reach 0x03 offset 420621.611508 delay 0.032669 status 0x24 strat 2 refid 0xd133a1ee rootdelay 0.005890
Fri Mar 7 10:22:15 2014 daemon.info sysinit: ntpd: reply from 67.18.187.111: reach 0x07 offset 420621.613920 delay 0.057415 status 0x24 strat 2 refid 0x808a8dac rootdelay 0.016556
Fri Mar 7 10:22:15 2014 daemon.info sysinit: ntpd: reply from 184.22.97.162: reach 0x03 offset 420621.615444 delay 0.059030 status 0x24 strat 2 refid 0x8076190c rootdelay 0.043366
Fri Mar 7 10:22:16 2014 daemon.info sysinit: ntpd: sent query to 184.105.182.7
Fri Mar 7 10:22:16 2014 daemon.info sysinit: ntpd: sent query to 184.22.97.162
Fri Mar 7 10:22:16 2014 daemon.info sysinit: ntpd: reply from 184.22.97.162: reach 0x07 offset 420621.614455 delay 0.057509 status 0x24 strat 2 refid 0x8076190c rootdelay 0.043366
Fri Mar 7 10:22:16 2014 daemon.info sysinit: ntpd: reply from 184.105.182.7: reach 0x07 offset 420621.609121 delay 0.096621 status 0x24 strat 2 refid 0xd8dafeca rootdelay 0.001190
Fri Mar 7 10:22:17 2014 daemon.info sysinit: ntpd: sent query to 67.18.187.111
Fri Mar 7 10:22:17 2014 daemon.info sysinit: ntpd: sent query to 129.250.35.251
Fri Mar 7 10:22:17 2014 daemon.info sysinit: ntpd: sent query to 184.22.97.162
Fri Mar 7 10:22:17 2014 daemon.info sysinit: ntpd: reply from 129.250.35.251: reach 0x07 offset 420621.611499 delay 0.032790 status 0x24 strat 2 refid 0xd133a1ee rootdelay 0.005890
Fri Mar 7 10:22:17 2014 daemon.info sysinit: ntpd: reply from 67.18.187.111: reach 0x0f offset 420621.614046 delay 0.057432 status 0x24 strat 2 refid 0x808a8dac rootdelay 0.016556
Fri Mar 7 10:22:17 2014 daemon.info sysinit: ntpd: reply from 184.22.97.162: reach 0x0f offset 420621.615462 delay 0.059072 status 0x24 strat 2 refid 0x8076190c rootdelay 0.043366
Fri Mar 7 10:22:18 2014 daemon.info sysinit: ntpd: sent query to 67.18.187.111
Fri Mar 7 10:22:18 2014 daemon.info sysinit: ntpd: sent query to 129.250.35.251
Fri Mar 7 10:22:18 2014 daemon.info sysinit: ntpd: sent query to 184.105.182.7
Fri Mar 7 10:22:18 2014 daemon.info sysinit: ntpd: reply from 129.250.35.251: reach 0x0f offset 420621.618661 delay 0.045978 status 0x24 strat 2 refid 0xd133a1ee rootdelay 0.005890
Fri Mar 7 10:22:18 2014 daemon.info sysinit: ntpd: reply from 67.18.187.111: reach 0x1f offset 420621.621467 delay 0.071996 status 0x24 strat 2 refid 0x808a8dac rootdelay 0.016556
Fri Mar 7 10:22:18 2014 daemon.info sysinit: ntpd: reply from 184.105.182.7: reach 0x0f offset 420621.620041 delay 0.118584 status 0x24 strat 2 refid 0xd8dafeca rootdelay 0.001190
Fri Mar 7 10:22:19 2014 daemon.info sysinit: ntpd: sent query to 184.22.97.162
Fri Mar 7 10:22:19 2014 daemon.info sysinit: ntpd: reply from 184.22.97.162: reach 0x1f offset 420621.610403 delay 0.049994 status 0x24 strat 2 refid 0x8076190c rootdelay 0.043366
Fri Mar 7 10:22:20 2014 daemon.info sysinit: ntpd: sent query to 67.18.187.111
Fri Mar 7 10:22:20 2014 daemon.info sysinit: ntpd: sent query to 129.250.35.251
Fri Mar 7 10:22:20 2014 daemon.info sysinit: ntpd: sent query to 184.105.182.7
Wed Mar 12 07:12:42 2014 daemon.info sysinit: ntpd: reply from 129.250.35.251: reach 0x1f offset 420621.610769 delay 0.032257 status 0x24 strat 2 refid 0xd133a1ee rootdelay 0.005890
Wed Mar 12 07:12:42 2014 daemon.info sysinit: ntpd: setting clock to Wed Mar 12 07:12:42 CST 2014 (offset 420621.610896s)
Wed Mar 12 07:12:42 2014 daemon.info sysinit: --bitmain-options 115200:32:8:36:393.75:5f05 -o Stratum.bitcoin.cz:3333 -O -o stratum.mining.eligius.st:3334 -O 17UhZWXLyiHmPmAb4VdFweGWRYY52qjxwp:123 --api-listen --api-network
Wed Mar 12 07:12:42 2014 daemon.info sysinit: - init complete -
Wed Mar 12 07:12:42 2014 kern.info kernel: [ 33.830000] bitmain 1-1.1:1.0: USB Bitmain asic #0 now disconnected
Wed Mar 12 07:13:23 2014 cron.err crond[575]: time disparity of 7011 minutes detected
Wed Mar 12 07:15:01 2014 cron.info crond[575]: crond: USER root pid 859 cmd /usr/bin/cgminer-monitor
Most of the above are NTP related. Have you tried disabling NTP? Just to see where that gets you. |
|
|
|
|
|
jedimstr
|
|
March 12, 2014, 12:59:09 AM |
|
Trying to use Antminer with setup on a Mac, made some initial progress. I can see the miner on my laptop when connected via direct ethernet cable.
Miner has a sticker with 192.168.1.99
I have a wireless router with internal IP addresses assigned as 10.0.1.2-31 and router address as 10.0.1.1
I saw the internal address of the miner as 10.0.1.31 using inet (program) when miner was attached to the router (initially).
External public address of the whole setup, which could be checked during browsing, is 98.201.121.X
I've got a laptop that has internal IP address 10.0.1.5 (gives the same external IP address as everything else on my network).
1. I connected miner directly to the laptop via ethernet, manually changed laptop IP to 192.168.1.254 (it did not accept 192.168.1.99 which was on the sticker), however when I entered 198.168.1.99 to a browser, laptop successfully connected to Antminer and I was able to setup mining configuration.
My question is: what I should enter in WAN and LAN setup fields on the miner considering above info?
Currently Antminer's WAN reads:
static
Addr 192.168.1.99
Mask 255.255.255.0
Gateway 192.168.1.1
IPv4 broadcast 192.168.1.255
DNS 192.168.1.1
Antminer's LAN reads: DHCP client
What do I change miner's WAN and LAN to? Should I change WAN to My external address and router (98.201.121.X and 98.201.120.X) or my internal addresses (10.0.1.1 for router and already assigned 10.0.1.31 for miner) and not touch LAN? Also my router is set to assign WAN automatically-does it mean anything for settings? Also router is set on sharing one public IP address among all devices-how this would work?
I am a noob at this, looked over dozens if not hundreds of pages on this and other forums.
Can someone help me please, especially if you set it up using Apple mac, but any help will be much appreciated.
Ignore the Antminer's "LAN" settings... the controller board on the Antminer S1 is a customized router itself so it's "WAN" is going to connect to your LAN. So for the Antminer's WAN settings, use most of the options similar to your Mac's (Network Pref Pane/Advanced) but for the main IP Address you have three options: 1. Set it to DHCP (get it's own address from your router) and you'll have to find the IP using inet like you did earlier, but the IP may change at a later date. 2. Set it to DHCP but set a static assigned IP based on the mac address of the Antminer from your router's settings. 3. Set a static IP for an unused address on the same subnet the rest of your network is on (10.0.1.x). Mask: 255.255.255.0 Gateway: 10.0.1.1 IPv4 broadcast: 10.0.1.255. DNS: 10.0.1.1 |
|
|
|
|
Cheeseater
|
|
March 12, 2014, 01:15:56 AM |
|
Most of the above are NTP related.
Have you tried disabling NTP?
Just to see where that gets you.
[/quote]
The damn thing has gone completely lame. both blades dead, the led's on the wrt board are lit but the one under the rj45 connector is dead. Reset has no affect. will try swapping PSU but I fear the WRT board is shit.
|
|
|
|
|
|
S4VV4S
|
|
March 12, 2014, 01:26:59 AM |
|
Most of the above are NTP related.
Have you tried disabling NTP?
Just to see where that gets you.
The damn thing has gone completely lame. both blades dead, the led's on the wrt board are lit but the one under the rj45 connector is dead. Reset has no affect. will try swapping PSU but I fear the WRT board is shit. [/quote] Sounds like a connection problem to me. EDIT: Can you ping google.com from your miner? |
|
|
|
|
|
