[Setup & Troubleshoot] Bitmain AntMiner S1 180GH/S miner - page 78.

mingophoria

full member

Activity: 154

Merit: 100

Code:

Mon Dec  2 11:28:08 2013 daemon.info sysinit: open pic update file fail 
Mon Dec  2 11:28:08 2013 daemon.info sysinit: Control bootloader to app
Mon Dec  2 11:28:08 2013 daemon.info sysinit: setting up led WAN
Mon Dec  2 11:28:08 2013 daemon.info sysinit: setting up led WANL
Mon Dec  2 11:28:08 2013 daemon.info sysinit: setting up led LAN1
Mon Dec  2 11:28:08 2013 daemon.info sysinit: setting up led LAN2
Mon Dec  2 11:28:08 2013 daemon.info sysinit: setting up led LAN3
Mon Dec  2 11:28:08 2013 daemon.info sysinit: setting up led LAN4
Mon Dec  2 11:28:08 2013 daemon.info sysinit: setting up led WLAN
Mon Dec  2 11:28:09 2013 daemon.notice netifd: lan (631): Sending discover...
Mon Dec  2 11:28:09 2013 kern.info kernel: [   22.270000] usb 1-1.1: USB disconnect, device number 3
Mon Dec  2 11:28:09 2013 kern.info kernel: [   22.280000] bitmainbl 1-1.1:1.0: USB Bitmain asic #0 now disconnected
Mon Dec  2 11:28:10 2013 kern.info kernel: [   22.670000] usb 1-1.1: new full-speed USB device number 4 using ehci-platform
Mon Dec  2 11:28:10 2013 kern.info kernel: [   23.130000] bitmain 1-1.1:1.0: USB Bitmain asic device now attached to USB Bitmain asic-0
Mon Dec  2 11:28:10 2013 kern.warn kernel: [   23.140000] PIC microchip usb OK
Mon Dec  2 11:28:10 2013 daemon.info sysinit: command failed: Device or resource busy (-16)
Mon Dec  2 11:28:12 2013 daemon.notice netifd: lan (631): Sending discover...
Mon Dec  2 11:28:13 2013 daemon.notice netifd: wwan (923): udhcpc (v1.19.4) started
Mon Dec  2 11:28:13 2013 daemon.notice netifd: wwan (923): Sending discover...
Mon Dec  2 11:28:14 2013 kern.info kernel: [   27.190000] wlan0: authenticate with 00:8e:f2:68:d1:bc
Mon Dec  2 11:28:14 2013 kern.info kernel: [   27.230000] wlan0: direct probe to 00:8e:f2:68:d1:bc (try 1/3)
Mon Dec  2 11:28:14 2013 kern.info kernel: [   27.440000] wlan0: send auth to 00:8e:f2:68:d1:bc (try 2/3)
Mon Dec  2 11:28:15 2013 kern.info kernel: [   27.660000] wlan0: send auth to 00:8e:f2:68:d1:bc (try 3/3)
Mon Dec  2 11:28:15 2013 kern.info kernel: [   27.670000] wlan0: authenticated
Mon Dec  2 11:28:15 2013 kern.info kernel: [   27.680000] wlan0: associate with 00:8e:f2:68:d1:bc (try 1/3)
Mon Dec  2 11:28:15 2013 kern.info kernel: [   27.690000] wlan0: RX AssocResp from 00:8e:f2:68:d1:bc (capab=0x411 status=0 aid=5)
Mon Dec  2 11:28:15 2013 kern.info kernel: [   27.690000] wlan0: associated
Mon Dec  2 11:28:16 2013 daemon.notice netifd: wwan (923): Sending discover...
Mon Dec  2 11:28:19 2013 daemon.notice netifd: wwan (923): Sending discover...
Mon Dec  2 11:28:23 2013 kern.info kernel: [   35.740000] wlan0: deauthenticated from 00:8e:f2:68:d1:bc (Reason: 15)
Mon Dec  2 11:28:24 2013 kern.info kernel: [   36.550000] wlan0: authenticate with 00:8e:f2:68:d1:bc
Mon Dec  2 11:28:24 2013 kern.info kernel: [   36.580000] wlan0: send auth to 00:8e:f2:68:d1:bc (try 1/3)
Mon Dec  2 11:28:24 2013 kern.info kernel: [   37.050000] wlan0: authenticated
Mon Dec  2 11:28:24 2013 kern.info kernel: [   37.060000] wlan0: associate with 00:8e:f2:68:d1:bc (try 1/3)
Mon Dec  2 11:28:24 2013 kern.info kernel: [   37.060000] wlan0: RX AssocResp from 00:8e:f2:68:d1:bc (capab=0x411 status=0 aid=5)
Mon Dec  2 11:28:24 2013 kern.info kernel: [   37.070000] wlan0: associated
Mon Dec  2 11:28:25 2013 daemon.notice netifd: wwan (923): Sending select for 192.168.0.13...
Mon Dec  2 11:28:26 2013 daemon.notice netifd: wwan (923): Lease of 192.168.0.13 obtained, lease time 86400
Mon Dec  2 11:28:26 2013 daemon.notice netifd: Interface 'wwan' is now up
Mon Dec  2 11:28:26 2013 user.notice firewall: Reloading firewall due to ifup of wwan (wlan0)
Mon Dec  2 11:28:28 2013 daemon.info dnsmasq[695]: reading /tmp/resolv.conf.auto
Mon Dec  2 11:28:28 2013 daemon.info dnsmasq[695]: using nameserver 194.168.8.100#53
Mon Dec  2 11:28:28 2013 daemon.info dnsmasq[695]: using nameserver 194.168.4.100#53
Mon Dec  2 11:28:28 2013 daemon.info dnsmasq[695]: using nameserver 192.168.1.1#53
Mon Dec  2 11:28:28 2013 daemon.info dnsmasq[695]: using local addresses only for domain lan
Mon Dec  2 11:28:28 2013 daemon.info sysinit: ntpd: resolved peer 3.openwrt.pool.ntp.org to 31.135.95.60
Mon Dec  2 11:28:28 2013 daemon.info sysinit: ntpd: sent query to 31.135.95.60
Mon Dec  2 11:28:28 2013 daemon.info sysinit: ntpd: resolved peer 2.openwrt.pool.ntp.org to 176.9.7.115
Mon Dec  2 11:28:28 2013 daemon.info sysinit: ntpd: sent query to 176.9.7.115
Mon Dec  2 11:28:28 2013 daemon.info sysinit: ntpd: resolved peer 1.openwrt.pool.ntp.org to 86.57.251.8
Mon Dec  2 11:28:28 2013 daemon.info sysinit: ntpd: sent query to 86.57.251.8
Mon Dec  2 11:28:28 2013 daemon.info sysinit: ntpd: resolved peer 0.openwrt.pool.ntp.org to 193.34.155.4
Mon Dec  2 11:28:28 2013 daemon.info sysinit: ntpd: sent query to 193.34.155.4
Mon Dec  2 11:28:28 2013 daemon.info sysinit: ntpd: reply from 176.9.7.115: reach 0x01 offset 7329713.760425 delay 0.179206 status 0x24 strat 2 refid 0xc035676c rootdelay 0.011765
Mon Dec  2 11:28:28 2013 daemon.info sysinit: Alarm clock
Mon Dec  2 11:28:28 2013 daemon.info sysinit: --bitmain-options 115200:32:8:40:350:4d81 -o stratum+tcp://stratum.mining.eligius.st:3334 -O 13Gy3mveiQkCu2Gk72gDrNn7Vq81TuzyeL:x -o stratum+tcp://stratum.mining.eligius.st:3334 -O 13Gy3mveiQkCu2Gk72gDrNn7Vq81TuzyeL:x -o stratum+tcp://stratum.50btc.com:3333 -O [email protected]:123 --api-listen --api-network
Mon Dec  2 11:28:28 2013 daemon.info sysinit: - init complete -
Mon Dec  2 11:28:29 2013 kern.info kernel: [   41.760000] bitmain 1-1.1:1.0: USB Bitmain asic #0 now disconnected
Mon Dec  2 11:28:33 2013 kern.info kernel: [   45.840000] wlan0: authenticate with 00:8e:f2:68:d1:bc
Mon Dec  2 11:28:33 2013 kern.info kernel: [   45.880000] wlan0: send auth to 00:8e:f2:68:d1:bc (try 1/3)
Mon Dec  2 11:28:33 2013 kern.info kernel: [   45.990000] wlan0: send auth to 00:8e:f2:68:d1:bc (try 2/3)
Mon Dec  2 11:28:33 2013 kern.info kernel: [   46.090000] wlan0: send auth to 00:8e:f2:68:d1:bc (try 3/3)
Mon Dec  2 11:28:33 2013 kern.info kernel: [   46.150000] wlan0: authentication with 00:8e:f2:68:d1:bc timed out
Mon Dec  2 11:28:44 2013 kern.info kernel: [   57.480000] wlan0: authenticate with 00:8e:f2:68:d1:bc
Mon Dec  2 11:28:44 2013 kern.info kernel: [   57.520000] wlan0: send auth to 00:8e:f2:68:d1:bc (try 1/3)
Mon Dec  2 11:28:44 2013 kern.info kernel: [   57.550000] wlan0: authenticated
Mon Dec  2 11:28:44 2013 kern.info kernel: [   57.560000] wlan0: associate with 00:8e:f2:68:d1:bc (try 1/3)
Mon Dec  2 11:28:45 2013 kern.info kernel: [   57.640000] wlan0: RX AssocResp from 00:8e:f2:68:d1:bc (capab=0x411 status=0 aid=5)
Mon Dec  2 11:28:45 2013 kern.info kernel: [   57.640000] wlan0: associated
Mon Dec  2 11:28:59 2013 kern.info kernel: [   71.860000] wlan0: authenticate with 00:8e:f2:68:d1:bc
Mon Dec  2 11:28:59 2013 kern.info kernel: [   71.890000] wlan0: send auth to 00:8e:f2:68:d1:bc (try 1/3)
Mon Dec  2 11:28:59 2013 kern.info kernel: [   71.960000] wlan0: send auth to 00:8e:f2:68:d1:bc (try 2/3)
Mon Dec  2 11:28:59 2013 kern.info kernel: [   72.040000] wlan0: send auth to 00:8e:f2:68:d1:bc (try 3/3)
Mon Dec  2 11:28:59 2013 kern.info kernel: [   72.100000] wlan0: authentication with 00:8e:f2:68:d1:bc timed out
Mon Dec  2 11:29:16 2013 kern.info kernel: [   88.570000] wlan0: authenticate with 00:8e:f2:68:d1:bc
Mon Dec  2 11:29:16 2013 kern.info kernel: [   88.610000] wlan0: send auth to 00:8e:f2:68:d1:bc (try 1/3)
Mon Dec  2 11:29:16 2013 kern.info kernel: [   88.630000] wlan0: authenticated
Mon Dec  2 11:29:16 2013 kern.info kernel: [   88.650000] wlan0: associate with 00:8e:f2:68:d1:bc (try 1/3)
Mon Dec  2 11:29:16 2013 kern.info kernel: [   88.660000] wlan0: RX AssocResp from 00:8e:f2:68:d1:bc (capab=0x411 status=0 aid=5)
Mon Dec  2 11:29:16 2013 kern.info kernel: [   88.660000] wlan0: associated
Mon Dec  2 11:29:29 2013 kern.info kernel: [  101.850000] wlan0: authenticate with 00:8e:f2:68:d1:bc
Mon Dec  2 11:29:29 2013 kern.info kernel: [  101.880000] wlan0: send auth to 00:8e:f2:68:d1:bc (try 1/3)
Mon Dec  2 11:29:29 2013 kern.info kernel: [  101.920000] wlan0: authenticated
Mon Dec  2 11:29:29 2013 kern.info kernel: [  101.940000] wlan0: associate with 00:8e:f2:68:d1:bc (try 1/3)
Mon Dec  2 11:29:29 2013 kern.info kernel: [  101.960000] wlan0: RX AssocResp from 00:8e:f2:68:d1:bc (capab=0x411 status=0 aid=5)
Mon Dec  2 11:29:29 2013 kern.info kernel: [  101.960000] wlan0: associated
Tue Feb 25 07:31:40 2014 kern.info kernel: [  118.850000] wlan0: authenticate with 00:8e:f2:68:d1:bc
Tue Feb 25 07:31:40 2014 kern.info kernel: [  118.890000] wlan0: send auth to 00:8e:f2:68:d1:bc (try 1/3)
Tue Feb 25 07:31:40 2014 kern.info kernel: [  118.900000] wlan0: authenticated
Tue Feb 25 07:31:40 2014 kern.info kernel: [  118.910000] wlan0: associate with 00:8e:f2:68:d1:bc (try 1/3)
Tue Feb 25 07:31:40 2014 kern.info kernel: [  119.060000] wlan0: associate with 00:8e:f2:68:d1:bc (try 2/3)
Tue Feb 25 07:31:40 2014 kern.info kernel: [  119.060000] wlan0: RX AssocResp from 00:8e:f2:68:d1:bc (capab=0x411 status=0 aid=5)
Tue Feb 25 07:31:40 2014 kern.info kernel: [  119.070000] wlan0: associated
Tue Feb 25 07:31:45 2014 kern.info kernel: [  123.850000] wlan0: authenticate with 00:8e:f2:68:d1:bc
Tue Feb 25 07:31:45 2014 kern.info kernel: [  123.890000] wlan0: send auth to 00:8e:f2:68:d1:bc (try 1/3)
Tue Feb 25 07:31:45 2014 kern.info kernel: [  123.900000] wlan0: authenticated
Tue Feb 25 07:31:45 2014 kern.info kernel: [  123.910000] wlan0: associate with 00:8e:f2:68:d1:bc (try 1/3)
Tue Feb 25 07:31:45 2014 kern.info kernel: [  124.110000] wlan0: associate with 00:8e:f2:68:d1:bc (try 2/3)
Tue Feb 25 07:31:45 2014 kern.info kernel: [  124.230000] wlan0: associate with 00:8e:f2:68:d1:bc (try 3/3)
Tue Feb 25 07:31:45 2014 kern.info kernel: [  124.340000] wlan0: association with 00:8e:f2:68:d1:bc timed out
Tue Feb 25 07:31:55 2014 cron.err crond[575]: time disparity of 122162 minutes detected
Tue Feb 25 07:33:01 2014 cron.info crond[575]: crond: USER root pid 1391 cmd /usr/bin/cgminer-monitor
Tue Feb 25 07:33:11 2014 kern.info kernel: [  210.150000] wlan0: authenticate with 00:8e:f2:68:d1:bc
Tue Feb 25 07:33:11 2014 kern.info kernel: [  210.190000] wlan0: direct probe to 00:8e:f2:68:d1:bc (try 1/3)
Tue Feb 25 07:33:11 2014 kern.info kernel: [  210.400000] wlan0: direct probe to 00:8e:f2:68:d1:bc (try 2/3)
Tue Feb 25 07:33:11 2014 kern.info kernel: [  210.610000] wlan0: direct probe to 00:8e:f2:68:d1:bc (try 3/3)
Tue Feb 25 07:33:12 2014 kern.info kernel: [  210.820000] wlan0: authentication with 00:8e:f2:68:d1:bc timed out
Tue Feb 25 07:35:34 2014 kern.info kernel: [  352.780000] wlan0: authenticate with 00:8e:f2:68:d1:bc
Tue Feb 25 07:35:34 2014 kern.info kernel: [  352.820000] wlan0: send auth to 00:8e:f2:68:d1:bc (try 1/3)
Tue Feb 25 07:35:34 2014 kern.info kernel: [  352.860000] wlan0: authenticated
Tue Feb 25 07:35:34 2014 kern.info kernel: [  352.870000] wlan0: associate with 00:8e:f2:68:d1:bc (try 1/3)
Tue Feb 25 07:35:34 2014 kern.info kernel: [  352.880000] wlan0: RX AssocResp from 00:8e:f2:68:d1:bc (capab=0x411 status=0 aid=5)
Tue Feb 25 07:35:34 2014 kern.info kernel: [  352.890000] wlan0: associated
Tue Feb 25 07:36:01 2014 cron.info crond[575]: crond: USER root pid 1607 cmd /usr/bin/cgminer-monitor
Tue Feb 25 07:36:55 2014 kern.info kernel: [  434.530000] wlan0: authenticate with 00:8e:f2:68:d1:bc
Tue Feb 25 07:36:55 2014 kern.info kernel: [  434.570000] wlan0: send auth to 00:8e:f2:68:d1:bc (try 1/3)
Tue Feb 25 07:36:55 2014 kern.info kernel: [  434.610000] wlan0: authenticated
Tue Feb 25 07:36:55 2014 kern.info kernel: [  434.620000] wlan0: associate with 00:8e:f2:68:d1:bc (try 1/3)
Tue Feb 25 07:36:56 2014 kern.info kernel: [  434.800000] wlan0: associate with 00:8e:f2:68:d1:bc (try 2/3)
Tue Feb 25 07:36:56 2014 kern.info kernel: [  434.920000] wlan0: associate with 00:8e:f2:68:d1:bc (try 3/3)
Tue Feb 25 07:36:56 2014 kern.info kernel: [  435.010000] wlan0: association with 00:8e:f2:68:d1:bc timed out
Tue Feb 25 07:37:00 2014 kern.info kernel: [  439.580000] wlan0: authenticate with 00:8e:f2:68:d1:bc
Tue Feb 25 07:37:00 2014 kern.info kernel: [  439.620000] wlan0: send auth to 00:8e:f2:68:d1:bc (try 1/3)
Tue Feb 25 07:37:00 2014 kern.info kernel: [  439.630000] wlan0: authenticated
Tue Feb 25 07:37:00 2014 kern.info kernel: [  439.640000] wlan0: associate with 00:8e:f2:68:d1:bc (try 1/3)
Tue Feb 25 07:37:00 2014 kern.info kernel: [  439.650000] wlan0: RX AssocResp from 00:8e:f2:68:d1:bc (capab=0x411 status=0 aid=5)
Tue Feb 25 07:37:00 2014 kern.info kernel: [  439.650000] wlan0: associated
Tue Feb 25 07:37:02 2014 kern.info kernel: [  441.300000] eth1: link up (100Mbps/Full duplex)
Tue Feb 25 07:37:39 2014 kern.info kernel: [  477.810000] wlan0: authenticate with 00:8e:f2:68:d1:bc
Tue Feb 25 07:37:39 2014 kern.info kernel: [  477.840000] wlan0: send auth to 00:8e:f2:68:d1:bc (try 1/3)
Tue Feb 25 07:37:39 2014 kern.info kernel: [  477.850000] wlan0: authenticated
Tue Feb 25 07:37:39 2014 kern.info kernel: [  477.870000] wlan0: associate with 00:8e:f2:68:d1:bc (try 1/3)
Tue Feb 25 07:37:39 2014 kern.info kernel: [  477.890000] wlan0: RX AssocResp from 00:8e:f2:68:d1:bc (capab=0x411 status=0 aid=5)
Tue Feb 25 07:37:39 2014 kern.info kernel: [  477.900000] wlan0: associated
Tue Feb 25 07:37:50 2014 kern.info kernel: [  488.820000] wlan0: authenticate with 00:8e:f2:68:d1:bc
Tue Feb 25 07:37:50 2014 kern.info kernel: [  488.850000] wlan0: send auth to 00:8e:f2:68:d1:bc (try 1/3)
Tue Feb 25 07:37:50 2014 kern.info kernel: [  488.910000] wlan0: send auth to 00:8e:f2:68:d1:bc (try 2/3)
Tue Feb 25 07:37:50 2014 kern.info kernel: [  489.010000] wlan0: send auth to 00:8e:f2:68:d1:bc (try 3/3)
Tue Feb 25 07:37:50 2014 kern.info kernel: [  489.070000] wlan0: authenticated
Tue Feb 25 07:37:50 2014 kern.info kernel: [  489.180000] wlan0: associate with 00:8e:f2:68:d1:bc (try 1/3)
Tue Feb 25 07:37:50 2014 kern.info kernel: [  489.270000] wlan0: associate with 00:8e:f2:68:d1:bc (try 2/3)
Tue Feb 25 07:37:50 2014 kern.info kernel: [  489.340000] wlan0: associate with 00:8e:f2:68:d1:bc (try 3/3)
Tue Feb 25 07:37:50 2014 kern.info kernel: [  489.440000] wlan0: association with 00:8e:f2:68:d1:bc timed out
Tue Feb 25 07:38:34 2014 kern.info kernel: [  533.220000] wlan0: authenticate with 00:8e:f2:68:d1:bc
Tue Feb 25 07:38:34 2014 kern.info kernel: [  533.260000] wlan0: send auth to 00:8e:f2:68:d1:bc (try 1/3)
Tue Feb 25 07:38:34 2014 kern.info kernel: [  533.310000] wlan0: authenticated
Tue Feb 25 07:38:34 2014 kern.info kernel: [  533.320000] wlan0: associate with 00:8e:f2:68:d1:bc (try 1/3)
Tue Feb 25 07:38:34 2014 kern.info kernel: [  533.430000] wlan0: associate with 00:8e:f2:68:d1:bc (try 2/3)
Tue Feb 25 07:38:34 2014 kern.info kernel: [  533.440000] wlan0: RX AssocResp from 00:8e:f2:68:d1:bc (capab=0x411 status=0 aid=5)
Tue Feb 25 07:38:34 2014 kern.info kernel: [  533.440000] wlan0: associated
Tue Feb 25 07:38:43 2014 kern.info kernel: [  541.810000] wlan0: authenticate with 00:8e:f2:68:d1:bc
Tue Feb 25 07:38:43 2014 kern.info kernel: [  541.850000] wlan0: send auth to 00:8e:f2:68:d1:bc (try 1/3)
Tue Feb 25 07:38:43 2014 kern.info kernel: [  542.110000] wlan0: authenticated
Tue Feb 25 07:38:43 2014 kern.info kernel: [  542.120000] wlan0: associate with 00:8e:f2:68:d1:bc (try 1/3)
Tue Feb 25 07:38:43 2014 kern.info kernel: [  542.240000] wlan0: associate with 00:8e:f2:68:d1:bc (try 2/3)
Tue Feb 25 07:38:43 2014 kern.info kernel: [  542.430000] wlan0: associate with 00:8e:f2:68:d1:bc (try 3/3)
Tue Feb 25 07:38:43 2014 kern.info kernel: [  542.440000] wlan0: RX AssocResp from 00:8e:f2:68:d1:bc (capab=0x411 status=0 aid=5)
Tue Feb 25 07:38:43 2014 kern.info kernel: [  542.450000] wlan0: associated
Tue Feb 25 07:38:43 2014 kern.err kernel: [  542.460000] ath: phy0: Failed to stop TX DMA, queues=0x001!
Tue Feb 25 07:38:46 2014 kern.info kernel: [  545.290000] wlan0: authenticate with 00:8e:f2:68:d1:bc
Tue Feb 25 07:38:46 2014 kern.info kernel: [  545.330000] wlan0: send auth to 00:8e:f2:68:d1:bc (try 1/3)
Tue Feb 25 07:38:47 2014 kern.info kernel: [  546.010000] wlan0: send auth to 00:8e:f2:68:d1:bc (try 2/3)
Tue Feb 25 07:38:47 2014 kern.info kernel: [  546.330000] wlan0: send auth to 00:8e:f2:68:d1:bc (try 3/3)
Tue Feb 25 07:38:48 2014 kern.info kernel: [  547.010000] wlan0: authentication with 00:8e:f2:68:d1:bc timed out
Tue Feb 25 07:39:01 2014 cron.info crond[575]: crond: USER root pid 2089 cmd /usr/bin/cgminer-monitor

I have a problem with my antminer, it only hash for like 20 sec and dc-ed. the process keeps repeating and the beeping sounds can be heard. What should i do?

papamoi

sr. member

Activity: 378

Merit: 250

Quote from: bronan on February 24, 2014, 05:59:47 PM

not as root ?
huh

yes as root

bronan

hero member

Activity: 774

Merit: 500

Lazy Lurker Reads Alot

not as root ?
huh

papamoi

sr. member

Activity: 378

Merit: 250

Quote from: kano on February 24, 2014, 05:35:44 PM

I wish they hadn't removed all the extra cgminer settings (i.e. other than pool settings) from the luci configuration page when they ~~stole~~copied it from xiangfu's avalon configuration ...
It's a damn pain in the neck having to hack into the startup scripts to change any cgminer settings ...

i ve tried to modify the nptd (for the clock) following their instructions and using putty but got never access to init.d

as i wasn t allowed to cd it meaning not allowed to enter in init.d .

so yes even for basic things ...

kano

legendary

Activity: 4592

Merit: 1851

Linux since 1997 RedHat 4

I wish they hadn't removed all the extra cgminer settings (i.e. other than pool settings) from the luci configuration page when they ~~stole~~copied it from xiangfu's avalon configuration ...
It's a damn pain in the neck having to hack into the startup scripts to change any cgminer settings ...

bronan

hero member

Activity: 774

Merit: 500

Lazy Lurker Reads Alot

Is this an ant or usb miner ?

If its an S1 do set the country at the system settings and google for a local ntp server

My provider has its own time sever so took that
And i entered 2 more well known time servers ( most use ntp.x or time.x format)

Then check if you filled the proper wan settings
And most important if you used a free ip on your local lan

One other important setting is the network dns and the gateway
As a gateway in most cases you need to set the modem/router you have which you can access
If you got a good modem/router you could see your miner in the modem as being a ip you gave it.

As primary dns i allways fill the modem/router ip in my case being 192.168.2.1
The secondairy dns i filled my providers real DNS server which you can ask.
And my last one is the either 8.8.8.8 or the backup dns from google 8.8.4.4
then the broadcast address which means you local lan can find the miner should be alsmot similar to your modems ip except the last number that should be 254, in my example 192.168.2.254
(this is the normal end of a ip chain of 255 numbers starting from 0 to 254)

That covers almost instant every search request and your needed numbers if that does not help there is something else wrong.

papamoi

sr. member

Activity: 378

Merit: 250

ok

i had to put the ant in a dmz to get it connected but it seems not stable it has gone off trying to reboot it

any others having same issues?

S4VV4S

hero member

Activity: 1582

Merit: 502

papamoi

sr. member

Activity: 378

Merit: 250

ok guys

i m trying since few days and not possible to get this thing hashing:

this is waht i m getting in the sys log:

Mon Feb 24 21:25:16 2014 daemon.info sysinit: ntpd: setting clock to Mon Feb 24 21:25:16 EAT 2014 (offset 7311413.420634s)
Mon Feb 24 21:25:16 2014 daemon.info sysinit: --bitmain-options 115200:32:8:40:350:4d81 -o http://xxx:[email protected]:3333 -O xxxx:pass --api-listen --api-network
Mon Feb 24 21:25:16 2014 daemon.info sysinit: - init complete -
Mon Feb 24 21:25:54 2014 cron.err crond[576]: time disparity of 121857 minutes detected

i ve removed password and all

i m not able to get it hashing

anyone have the same log?

solution?

this is also the last part of the kernel log:

[ 13.110000] ath: EEPROM indicates default country code should be used
[ 13.110000] ath: doing EEPROM country->regdmn map search
[ 13.110000] ath: country maps to regdmn code: 0x3a
[ 13.110000] ath: Country alpha2 being used: US
[ 13.110000] ath: Regpair used: 0x3a
[ 13.120000] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[ 13.130000] cfg80211: Calling CRDA for country: US
[ 13.130000] cfg80211: Regulatory domain changed to country: US
[ 13.140000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 13.150000] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)
[ 13.150000] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm)
[ 13.160000] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 13.170000] cfg80211: (5490000 KHz - 5600000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 13.180000] cfg80211: (5650000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 13.190000] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)
[ 13.190000] ieee80211 phy0: Atheros AR9330 Rev:1 mem=0xb8100000, irq=2
[ 17.950000] device eth0 entered promiscuous mode
[ 20.080000] eth1: link up (100Mbps/Full duplex)
[ 21.300000] no int in filled
[ 22.770000] usb 1-1.1: USB disconnect, device number 3
[ 22.770000] bitmainbl 1-1.1:1.0: USB Bitmain asic #0 now disconnected
[ 23.050000] usb 1-1.1: new full-speed USB device number 4 using ehci-platform
[ 23.950000] bitmain 1-1.1:1.0: USB Bitmain asic device now attached to USB Bitmain asic-0
[ 23.960000] PIC microchip usb OK
[ 24.820000] bitmain 1-1.1:1.0: USB Bitmain asic #0 now disconnected

any ideas?

tHANKS

HerrHeimlich

member

Activity: 234

Merit: 10

Can you give me a hint where i have to configure this?

fhh

legendary

Activity: 1206

Merit: 1000

Quote from: HerrHeimlich on February 24, 2014, 09:30:54 AM

I need help with the WIFI-connection.

I established the connection:
- put on an antenna
- scanned for the wlan
- connected to the wlan
- gave a static ip to the network adapter
Result: it connects to the wlan and hashing begins
Problem: if I make a ping to the address there comes no response and if I want to join the webinterface over this address I can't open the site.

Has anybody of you an idea how to solve this?

Joerg

You have to put the interface in the LAN firewall zone

HerrHeimlich

member

Activity: 234

Merit: 10

I need help with the WIFI-connection.

I established the connection:
- put on an antenna
- scanned for the wlan
- connected to the wlan
- gave a static ip to the network adapter
Result: it connects to the wlan and hashing begins
Problem: if I make a ping to the address there comes no response and if I want to join the webinterface over this address I can't open the site.

Has anybody of you an idea how to solve this?

Joerg

S4VV4S

hero member

Activity: 1582

Merit: 502

Quote from: kamran11958 on February 24, 2014, 05:07:42 AM

Hi,

I am new to the website and have a question. I am planing t order couple of the miner, How can I make a rack for the miners? Can I have a shared PSU for all of them or it's better to have one per each? Can you give me some recommendation/suggestion on this? For a rack of 10 miners.

Thanks,

Personally I prefer to have one PSU for each ANt.
I have seen members that have up to 3 Ants on a PSU.
Whatever you choose make sure that you get a good quality PSU, preferably a GOLD one and make sure it has way more wattage than you Ant needs (360w-430w).

As for racks, have a look at this: https://bitcointalksearch.org/topic/--7216

kamran11958

newbie

Activity: 1

Merit: 0

Hi,

I am new to the website and have a question. I am planing t order couple of the miner, How can I make a rack for the miners? Can I have a shared PSU for all of them or it's better to have one per each? Can you give me some recommendation/suggestion on this? For a rack of 10 miners.

Thanks,

S4VV4S

hero member

Activity: 1582

Merit: 502

Quote from: ryliou on February 23, 2014, 08:45:36 PM

Quote from: tmwsiy on February 23, 2014, 09:32:09 AM

Quote from: palawan on February 22, 2014, 09:59:39 PM

Quote from: ryliou on February 22, 2014, 08:55:02 PM

Quote from: palawan on February 22, 2014, 03:56:42 PM

...
I configured both of my Antminer S1's from factory via wifi on my laptop (dell mini 9 netbook). I've never directly connected to either of my Antminer to a laptop/computer.

Good luck.

Could anyone/two of you do me a favor? Take screen shot of your ipconfig output.
mine have both 192.168.2.xx by cable and 192.168.1.xx by wireless, but still can't access Miner.
The network cable head green light is not even on for Miner, the rest of PC/Laptop are all on.

I probably need to ask seller for a replacement network/control card.

I'm not running Windows. I run Arch Linux and Linux Mint on my laptops. And all devices on my network are 192.168.55.x subnet now. That includes the miners, 3 laptops, cell phones, tablets, chromecast.

At any rate, that's a problem if there's no link light on the Antminer S1. First thing's first, you need physical connectivity before you can access the miner.

Did you connect the Antminer to your router and you're not getting a link light on the Antminer? and you're sure the cable is good?

I had a similar experience and had a moment of WTF. I just kept trying different cables until I found one that worked. It seems the female ethernet connector on the ant's do not mate up well with some connector/shield combinations on some cables.

Hi, changed 4 cables and still no light on both end of network socket.
I'm sure I need to ask Seller for replacement network/card.
Maybe the shipping without static protection caused it to short-circuit.

Have you tried connecting to your Ant through WiFi?
It should be the same as LAN.
Just modify your wifi adapter ipv4 settings. The Ant is already set up by factory (normally).

Also, I will ask you once again...
Have you tried connecting to your Ant with a different computer?

EDIT: I have no physical connection to my Ant.
The Ant is connected on the router.
I use WiFi to connect to my router and access the Ant.

mingophoria

full member

Activity: 154

Merit: 100

Quote from: kano on February 24, 2014, 02:46:26 AM

Quote from: mingophoria on February 24, 2014, 02:18:28 AM

can anyone please show me a picture where is the factory reset button for the S1 miner? thanks.

https://github.com/AntMiner/AntGen1/tree/master/manual

Thanks!

kano

legendary

Activity: 4592

Merit: 1851

Linux since 1997 RedHat 4

Quote from: mingophoria on February 24, 2014, 02:18:28 AM

can anyone please show me a picture where is the factory reset button for the S1 miner? thanks.

https://github.com/AntMiner/AntGen1/tree/master/manual

mingophoria

full member

Activity: 154

Merit: 100

can anyone please show me a picture where is the factory reset button for the S1 miner? thanks.

mozilafirefox

jr. member

Activity: 124

Merit: 1

Quote from: samsonn25 on February 23, 2014, 03:58:53 PM

Looks like it would work. You just need to keep consistent power to the router to extend the USB to WiFi signal. Now you have options for wireless connection and wired connection.

Only thing is you cant be on the go as much now with a Laptop traveling outside alot.

Quote from: tmwsiy on February 23, 2014, 05:33:24 PM

Quote from: minternj on February 23, 2014, 05:24:07 PM

Quote from: tmwsiy on February 23, 2014, 05:22:33 PM

Quote from: minternj on February 23, 2014, 03:22:53 PM

You just need to setup internet sharing from your computer, since that looks like a usb 3G type internet device. Depending on your OS, many different ways to do it. windows would be the simplest. just follow the wizard.

Pretty sure if he is plugging modem into his machine directly he will need another radio (or use the ethernet and connect his ant wired).

Simplest thing would be to get something like this (http://www.amazon.com/EW-7811UN-IEEE-802-11n-draft-USB/dp/B005CLMJLU)

and then setup internet connection sharing in whatever OS you are using.

Last i checked you can't plug usb into an ant. unless someone made an adapter for that control board? Easiest thing is to do ICS in windows.

Not suggesting you plug usb into ant. I am suggesting that the 3G radio is plugged into his desktop/laptop and you will need something with an 802.11 radio in that same machine to act as the access point piece. Or plug his ant into the ethernet port on that same machine and set the sharing up that way.

To have a gateway you will always need two interfaces (ethernet, wifi, wimax, 3g usb modem, etc)

Thanks for suggestion Guys,

Im gonna just try with this.
http://www.flipkart.com/tp-link-tl-mr3420-3g-4g-wireless-n-router/p/itmdet9bxmndehck?pid=RTRDET9AQR7EMM2G&otracker=from-search&srno=t_3&query=router&ref=17393eeb-0524-4869-9578-a6358749b0fb

It works like this, Plug my Usb modem into it. and it has multiple ethernet slots. from which one can go into my computer, and another can into my Antminer + Wifi.
you can see pics and Specifications there. To know how it does.

Darthswan

hero member

Activity: 818

Merit: 508

Quote from: freebit13 on February 24, 2014, 12:33:32 AM

Quote from: Darthswan on February 23, 2014, 05:13:12 PM

Has anyone done the firmware upgrade yet? Any problems one needs to know about? What is the performance like after the upgrade?

Thanks.

I upgraded the firmware last week and didn't notice any changes except that my miners started losing connection randomly and reporting my pool to be dead when it wasn't. I've gone back to the old firmware and not had trouble since...

At first, I noticed a low HWI%. Then over time it started to kick up. I'm thinking about going back to the previous firmware. I'm going to give it a day and see.

Topic: [Setup & Troubleshoot] Bitmain AntMiner S1 180GH/S miner - page 78. (Read 452359 times)