Topic: [Guide] Dogie's Comprehensive Bitmain AntMiner S1 Setup [HD] - page 5. (Read 112444 times)
So i have double checked things, the antminer is connected to the internet (i can ping from it successfully) but the green LED is still blinking. Why?
Hmmm. I guess this means its a hardware error with the S1. I thought it may be something that happens when it heats up, however the temp i run the S1 at is constantly 46C - which should be fine.
Any thoughts? I am relatively inexperienced with the S1's.
Any thoughts? I am relatively inexperienced with the S1's.
Ok, after leaving switched off for a few hours it is now hashing away....
Do the pool servers ever go down, could my non-hashing S1 be caused by slushs pool being unavailable? Or does this not happen?
Do the pool servers ever go down, could my non-hashing S1 be caused by slushs pool being unavailable? Or does this not happen?
Very rarely will a pool server go down.
Ok, after leaving switched off for a few hours it is now hashing away....
Do the pool servers ever go down, could my non-hashing S1 be caused by slushs pool being unavailable? Or does this not happen?
Do the pool servers ever go down, could my non-hashing S1 be caused by slushs pool being unavailable? Or does this not happen?
I restarted it again - the time error seems to have gone away:
Last few lines of system log after boot:
Is it normal to say bitmain asic "now disconnected"? And is there any way to tell if the blades are ok - like registering with the control board? I was originally worried the blades may have stopped working.
EDIT: more info: I have the slow strobing green led to the left of the red led, the green led under the ethernet jack is on, and so it the ethernet lights.
Last few lines of system log after boot:
Code:
Wed Aug 6 19:28:19 2014 kern.info kernel: [ 32.240000] usb 1-1.1: USB disconnect, device number 4
Wed Aug 6 19:28:19 2014 kern.info kernel: [ 32.250000] bitmainbl 1-1.1:1.0: USB Bitmain asic #0 now disconnected
Wed Aug 6 19:28:19 2014 kern.info kernel: [ 32.500000] usb 1-1.1: new full-speed USB device number 5 using ehci-platform
Wed Aug 6 19:28:20 2014 kern.info kernel: [ 32.640000] bitmain 1-1.1:1.0: USB Bitmain asic device now attached to USB Bitmain asic-0
Wed Aug 6 19:28:20 2014 kern.warn kernel: [ 32.640000] PIC microchip usb OK
Wed Aug 6 19:28:26 2014 daemon.info sysinit: ntpd: resolved peer 3.openwrt.pool.ntp.org to 202.127.210.36
Wed Aug 6 19:28:26 2014 daemon.info sysinit: ntpd: sent query to 202.127.210.36
Wed Aug 6 19:28:29 2014 daemon.info sysinit: ntpd: resolved peer 2.openwrt.pool.ntp.org to 27.116.36.36
Wed Aug 6 19:28:29 2014 daemon.info sysinit: ntpd: sent query to 27.116.36.36
Wed Aug 6 19:28:35 2014 daemon.info sysinit: ntpd: resolved peer 1.openwrt.pool.ntp.org to 121.0.0.42
Wed Aug 6 19:28:35 2014 daemon.info sysinit: ntpd: sent query to 121.0.0.42
Wed Aug 6 19:28:38 2014 daemon.info sysinit: ntpd: resolved peer 0.openwrt.pool.ntp.org to 27.54.95.12
Wed Aug 6 19:28:38 2014 daemon.info sysinit: ntpd: sent query to 27.54.95.12
Wed Aug 6 19:28:38 2014 daemon.info sysinit: ntpd: reply from 27.116.36.36: reach 0x01 offset 25.300365 delay 8.860339 status 0x24 strat 3 refid 0xc0bd3611 rootdelay 0.048066
Wed Aug 6 19:28:38 2014 daemon.info sysinit: ntpd: reply from 121.0.0.42: reach 0x01 offset 28.392241 delay 2.890779 status 0x24 strat 3 refid 0x18205ad9 rootdelay 0.088243
Wed Aug 6 19:28:38 2014 daemon.info sysinit: Alarm clock
Wed Aug 6 19:28:38 2014 daemon.info sysinit: --bitmain-options 115200:32:8:40:350:4d81 -o stratum+tcp://stratum.bitcoin.cz:3333 -O XxXScarecrowXxX.worker1:LfDacYac -o stratum+tcp://stratum.bitcoin.cz:3333 -O XxXScarecrowXxX.worker2:Dolby13 --api-listen --api-network
Wed Aug 6 19:28:38 2014 daemon.info sysinit: - init complete -
Wed Aug 6 19:28:38 2014 kern.info kernel: [ 50.950000] bitmain 1-1.1:1.0: USB Bitmain asic #0 now disconnected
Is it normal to say bitmain asic "now disconnected"? And is there any way to tell if the blades are ok - like registering with the control board? I was originally worried the blades may have stopped working.
EDIT: more info: I have the slow strobing green led to the left of the red led, the green led under the ethernet jack is on, and so it the ethernet lights.
If i ssh to the S1 and query 'date' i get the correct time - since setting the timezone.
If yo u look at the very last entry of the system log it says "Wed Aug 6 18:42:35 2014 cron.err crond[575]: time disparity of 356113 minutes detected".
So the time is correct for my location but it still says there is a disparity? Whats with that?
The ntp servers i have listed are the default ones: 0.openwrt.pool.ntp.org etc...
Would a time discrepancy cause it not to mine - perhaps the pool is not letting me connect because of it - or not?
If yo u look at the very last entry of the system log it says "Wed Aug 6 18:42:35 2014 cron.err crond[575]: time disparity of 356113 minutes detected".
So the time is correct for my location but it still says there is a disparity? Whats with that?
The ntp servers i have listed are the default ones: 0.openwrt.pool.ntp.org etc...
Would a time discrepancy cause it not to mine - perhaps the pool is not letting me connect because of it - or not?
Are you not able to correct the time? Its saying its 250 days out, which may cause some big problems.
I also found that when the S1 was working it would only work if the stratum address was "stratum+tcp://stratum.bitcoin.cz:3333".
If i did not put the "stratum+tcp://" it would not work. Is this normal?
I have tried slushs pool and btcguild and both dont work.
If i did not put the "stratum+tcp://" it would not work. Is this normal?
I have tried slushs pool and btcguild and both dont work.
Hey folks,
I have a S1 that was working fine, then out of nowhere started beeping, i reset it and now it wont hash at all.
It shows nothing in the Miner Status screen.
I have done a hard rest, new firmware, re-entered pool info etc. The miner can ping the internet fine. All network infrastructure is the same as before.
I don't understand what it could be.
The blades couldn't both have just died could they?
The times are wrong - could this be a problem? Will the S1 mine if the time is set wrong?
I have pasted in my system log, although i cant see any errors that stand out:
My WAN config has ipv4: 192.168.1.99
netmask: 255.255.255.0
gateway: 192.168.1.1
broadcast: 192.168.1.255
dns: 8.8.8.8
Any thoughts?
I have a S1 that was working fine, then out of nowhere started beeping, i reset it and now it wont hash at all.
It shows nothing in the Miner Status screen.
I have done a hard rest, new firmware, re-entered pool info etc. The miner can ping the internet fine. All network infrastructure is the same as before.
I don't understand what it could be.
The blades couldn't both have just died could they?
The times are wrong - could this be a problem? Will the S1 mine if the time is set wrong?
I have pasted in my system log, although i cant see any errors that stand out:
Code:
Thu Jan 1 08:00:11 1970 kern.debug kernel: [ 0.000000] On node 0 totalpages: 16384
Thu Jan 1 08:00:11 1970 kern.debug kernel: [ 0.000000] free_area_init_node: node 0, pgdat 803005b0, node_mem_map 81000000
Thu Jan 1 08:00:11 1970 kern.debug kernel: [ 0.000000] Normal zone: 128 pages used for memmap
Thu Jan 1 08:00:11 1970 kern.debug kernel: [ 0.000000] Normal zone: 0 pages reserved
Thu Jan 1 08:00:11 1970 kern.debug kernel: [ 0.000000] Normal zone: 16384 pages, LIFO batch:3
Thu Jan 1 08:00:11 1970 kern.warn kernel: [ 0.000000] Primary instruction cache 64kB, VIPT, 4-way, linesize 32 bytes.
Thu Jan 1 08:00:11 1970 kern.warn kernel: [ 0.000000] Primary data cache 32kB, 4-way, VIPT, cache aliases, linesize 32 bytes
Thu Jan 1 08:00:11 1970 kern.debug kernel: [ 0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
Thu Jan 1 08:00:11 1970 kern.debug kernel: [ 0.000000] pcpu-alloc: [0] 0
Thu Jan 1 08:00:11 1970 kern.warn kernel: [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 16256
Thu Jan 1 08:00:11 1970 kern.notice kernel: [ 0.000000] Kernel command line: board=TL-WR741ND-v4 console=ttyATH0,115200 rootfstype=squashfs,jffs2 noinitrd
Thu Jan 1 08:00:11 1970 kern.info kernel: [ 0.000000] PID hash table entries: 256 (order: -2, 1024 bytes)
Thu Jan 1 08:00:11 1970 kern.info kernel: [ 0.000000] Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Thu Jan 1 08:00:11 1970 kern.info kernel: [ 0.000000] Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Thu Jan 1 08:00:11 1970 kern.info kernel: [ 0.000000] Writing ErrCtl register=00000000
Thu Jan 1 08:00:11 1970 kern.info kernel: [ 0.000000] Readback ErrCtl register=00000000
Thu Jan 1 08:00:11 1970 kern.info kernel: [ 0.000000] Memory: 61336k/65536k available (2187k kernel code, 4200k reserved, 588k data, 232k init, 0k highmem)
Thu Jan 1 08:00:11 1970 kern.info kernel: [ 0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Thu Jan 1 08:00:11 1970 kern.info kernel: [ 0.000000] NR_IRQS:51
Thu Jan 1 08:00:11 1970 kern.info kernel: [ 0.080000] Calibrating delay loop... 265.42 BogoMIPS (lpj=1327104)
Thu Jan 1 08:00:11 1970 kern.info kernel: [ 0.080000] pid_max: default: 32768 minimum: 301
Thu Jan 1 08:00:11 1970 kern.info kernel: [ 0.080000] Mount-cache hash table entries: 512
Thu Jan 1 08:00:11 1970 kern.info kernel: [ 0.090000] NET: Registered protocol family 16
Thu Jan 1 08:00:11 1970 kern.info kernel: [ 0.100000] MIPS: machine is TP-LINK TL-WR741ND v4
Thu Jan 1 08:00:11 1970 kern.info kernel: [ 0.550000] bio: create slabat 0
Thu Jan 1 08:00:11 1970 kern.info kernel: [ 0.560000] Switching to clocksource MIPS
Thu Jan 1 08:00:11 1970 kern.info kernel: [ 0.560000] NET: Registered protocol family 2
Thu Jan 1 08:00:11 1970 kern.info kernel: [ 0.570000] TCP established hash table entries: 512 (order: 0, 4096 bytes)
Thu Jan 1 08:00:11 1970 kern.info kernel: [ 0.570000] TCP bind hash table entries: 512 (order: -1, 2048 bytes)
Thu Jan 1 08:00:11 1970 kern.info kernel: [ 0.570000] TCP: Hash tables configured (established 512 bind 512)
Thu Jan 1 08:00:11 1970 kern.info kernel: [ 0.580000] TCP: reno registered
Thu Jan 1 08:00:11 1970 kern.info kernel: [ 0.580000] UDP hash table entries: 256 (order: 0, 4096 bytes)
Thu Jan 1 08:00:11 1970 kern.info kernel: [ 0.590000] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
Thu Jan 1 08:00:11 1970 kern.info kernel: [ 0.600000] NET: Registered protocol family 1
Thu Jan 1 08:00:11 1970 kern.debug kernel: [ 0.600000] PCI: CLS 0 bytes, default 32
Thu Jan 1 08:00:11 1970 kern.info kernel: [ 0.620000] squashfs: version 4.0 (2009/01/31) Phillip Lougher
Thu Jan 1 08:00:11 1970 kern.info kernel: [ 0.620000] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
Thu Jan 1 08:00:11 1970 kern.info kernel: [ 0.630000] msgmni has been set to 119
Thu Jan 1 08:00:11 1970 kern.info kernel: [ 0.640000] io scheduler noop registered
Thu Jan 1 08:00:11 1970 kern.info kernel: [ 0.640000] io scheduler deadline registered (default)
Thu Jan 1 08:00:11 1970 kern.info kernel: [ 0.640000] Serial: 8250/16550 driver, 1 ports, IRQ sharing disabled
Thu Jan 1 08:00:11 1970 kern.info kernel: [ 0.650000] ar933x-uart: ttyATH0 at MMIO 0x18020000 (irq = 11) is a AR933X UART
Thu Jan 1 08:00:11 1970 kern.info kernel: [ 0.660000] console [ttyATH0] enabled, bootconsole disabled
Thu Jan 1 08:00:11 1970 kern.info kernel: [ 0.670000] ath79-spi ath79-spi: master is unqueued, this is deprecated
Thu Jan 1 08:00:11 1970 kern.warn kernel: [ 0.680000] m25p80 spi0.0: found mx25l6405d, expected m25p80
Thu Jan 1 08:00:11 1970 kern.info kernel: [ 0.680000] m25p80 spi0.0: mx25l6405d (8192 Kbytes)
Thu Jan 1 08:00:11 1970 kern.notice kernel: [ 0.690000] 5 tp-link partitions found on MTD device spi0.0
Thu Jan 1 08:00:11 1970 kern.notice kernel: [ 0.690000] Creating 5 MTD partitions on "spi0.0":
Thu Jan 1 08:00:11 1970 kern.notice kernel: [ 0.700000] 0x000000000000-0x000000020000 : "u-boot"
Thu Jan 1 08:00:11 1970 kern.notice kernel: [ 0.700000] 0x000000020000-0x000000117d84 : "kernel"
Thu Jan 1 08:00:11 1970 kern.warn kernel: [ 0.710000] mtd: partition "kernel" must either start or end on erase block boundary or be smaller than an erase block -- forcing read-only
Thu Jan 1 08:00:11 1970 kern.notice kernel: [ 0.720000] 0x000000117d84-0x0000007f0000 : "rootfs"
Thu Jan 1 08:00:11 1970 kern.warn kernel: [ 0.730000] mtd: partition "rootfs" must either start or end on erase block boundary or be smaller than an erase block -- forcing read-only
Thu Jan 1 08:00:11 1970 kern.notice kernel: [ 0.740000] mtd: partition "rootfs" set to be root filesystem
Thu Jan 1 08:00:11 1970 kern.info kernel: [ 0.740000] mtd: partition "rootfs_data" created automatically, ofs=0x370000, len=0x480000
Thu Jan 1 08:00:11 1970 kern.notice kernel: [ 0.750000] 0x000000370000-0x0000007f0000 : "rootfs_data"
Thu Jan 1 08:00:11 1970 kern.notice kernel: [ 0.760000] 0x000000020000-0x0000007f0000 : "firmware"
Thu Jan 1 08:00:11 1970 kern.notice kernel: [ 0.770000] 0x0000007f0000-0x000000800000 : "art"
Thu Jan 1 08:00:11 1970 kern.info kernel: [ 0.790000] libphy: ag71xx_mdio: probed
Thu Jan 1 08:00:11 1970 kern.info kernel: [ 0.790000] eth0: Atheros AG71xx at 0xba000000, irq 5, mode:GMII
Thu Jan 1 08:00:11 1970 kern.info kernel: [ 1.340000] eth0: Found an AR7240/AR9330 built-in switch
Thu Jan 1 08:00:11 1970 kern.info kernel: [ 2.380000] eth1: Atheros AG71xx at 0xb9000000, irq 4, mode:MII
Thu Jan 1 08:00:11 1970 kern.info kernel: [ 2.930000] ag71xx ag71xx.0 eth1: connected to PHY at ag71xx-mdio.1:04 [uid=004dd041, driver=Generic PHY]
Thu Jan 1 08:00:11 1970 kern.info kernel: [ 2.940000] TCP: cubic registered
Thu Jan 1 08:00:11 1970 kern.info kernel: [ 2.940000] NET: Registered protocol family 17
Thu Jan 1 08:00:11 1970 kern.info kernel: [ 2.950000] 8021q: 802.1Q VLAN Support v1.8
Thu Jan 1 08:00:11 1970 kern.info kernel: [ 2.960000] VFS: Mounted root (squashfs filesystem) readonly on device 31:2.
Thu Jan 1 08:00:11 1970 kern.info kernel: [ 2.970000] Freeing unused kernel memory: 232K (80316000 - 80350000)
Thu Jan 1 08:00:11 1970 kern.info kernel: [ 5.800000] usbcore: registered new interface driver usbfs
Thu Jan 1 08:00:11 1970 kern.info kernel: [ 5.800000] usbcore: registered new interface driver hub
Thu Jan 1 08:00:11 1970 kern.info kernel: [ 5.810000] usbcore: registered new device driver usb
Thu Jan 1 08:00:11 1970 kern.info kernel: [ 5.810000] usbcore: registered new interface driver bitmain
Thu Jan 1 08:00:11 1970 kern.warn kernel: [ 5.820000] hash ok
Thu Jan 1 08:00:11 1970 kern.warn kernel: [ 5.820000] hashtest OK
Thu Jan 1 08:00:11 1970 kern.err kernel: [ 5.820000] bitmain-asic: success to register device
Thu Jan 1 08:00:11 1970 kern.info kernel: [ 5.830000] usbcore: registered new interface driver bitmainbl
Thu Jan 1 08:00:11 1970 kern.info kernel: [ 5.840000] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Thu Jan 1 08:00:11 1970 kern.info kernel: [ 5.850000] ehci-platform: EHCI generic platform driver
Thu Jan 1 08:00:11 1970 kern.info kernel: [ 5.850000] ehci-platform ehci-platform: EHCI Host Controller
Thu Jan 1 08:00:11 1970 kern.info kernel: [ 5.860000] ehci-platform ehci-platform: new USB bus registered, assigned bus number 1
Thu Jan 1 08:00:11 1970 kern.info kernel: [ 5.860000] ehci-platform ehci-platform: irq 3, io mem 0x1b000000
Thu Jan 1 08:00:11 1970 kern.info kernel: [ 5.890000] ehci-platform ehci-platform: USB 2.0 started, EHCI 1.00
Thu Jan 1 08:00:11 1970 kern.info kernel: [ 5.890000] hub 1-0:1.0: USB hub found
Thu Jan 1 08:00:11 1970 kern.info kernel: [ 5.890000] hub 1-0:1.0: 1 port detected
Thu Jan 1 08:00:11 1970 kern.info kernel: [ 6.230000] usb 1-1: new high-speed USB device number 2 using ehci-platform
Thu Jan 1 08:00:11 1970 kern.info kernel: [ 6.380000] hub 1-1:1.0: USB hub found
Thu Jan 1 08:00:11 1970 kern.info kernel: [ 6.380000] hub 1-1:1.0: 2 ports detected
Thu Jan 1 08:00:11 1970 kern.info kernel: [ 6.670000] usb 1-1.1: new full-speed USB device number 3 using ehci-platform
Thu Jan 1 08:00:11 1970 kern.info kernel: [ 6.800000] bitmainbl 1-1.1:1.0: USB Bitmain bootloader device now attached to USB Bitmain bootloader-0
Thu Jan 1 08:00:11 1970 kern.warn kernel: [ 6.810000] PIC microchip bootloader usb OK
Thu Jan 1 08:00:11 1970 kern.notice kernel: [ 10.550000] jffs2: notice: (327) jffs2_build_xattr_subsystem: complete building xattr subsystem, 25 of xdatum (0 unchecked, 24 orphan) and 39 of xref (0 dead, 24 orphan) found.
Mon Dec 2 11:28:00 2013 daemon.info sysinit: Mon Dec 2 03:28:00 UTC 2013
Mon Dec 2 11:28:00 2013 user.emerg syslog: kmodloader: loading kernel modules from /etc/modules.d/**
Mon Dec 2 11:28:00 2013 kern.info kernel: [ 12.820000] hidraw: raw HID events driver (C) Jiri Kosina
Mon Dec 2 11:28:00 2013 kern.info kernel: [ 12.830000] Loading modules backported from Linux version master-2013-06-27-0-gdcfa6d5
Mon Dec 2 11:28:00 2013 kern.info kernel: [ 12.830000] Backport generated by backports.git backports-20130617-4-ge3220f5
Mon Dec 2 11:28:00 2013 kern.info kernel: [ 12.850000] nf_conntrack version 0.5.0 (962 buckets, 3848 max)
Mon Dec 2 11:28:00 2013 kern.info kernel: [ 12.870000] usbcore: registered new interface driver usbhid
Mon Dec 2 11:28:00 2013 kern.info kernel: [ 12.880000] usbhid: USB HID core driver
Mon Dec 2 11:28:00 2013 kern.info kernel: [ 12.890000] usbcore: registered new interface driver usbserial
Mon Dec 2 11:28:00 2013 kern.info kernel: [ 12.890000] usbcore: registered new interface driver usbserial_generic
Mon Dec 2 11:28:00 2013 kern.info kernel: [ 12.900000] usbserial: USB Serial support registered for generic
Mon Dec 2 11:28:00 2013 kern.info kernel: [ 12.930000] xt_time: kernel timezone is -0000
Mon Dec 2 11:28:00 2013 kern.info kernel: [ 12.950000] cfg80211: Calling CRDA to update world regulatory domain
Mon Dec 2 11:28:00 2013 kern.info kernel: [ 12.960000] ip_tables: (C) 2000-2006 Netfilter Core Team
Mon Dec 2 11:28:00 2013 kern.info kernel: [ 12.970000] cfg80211: World regulatory domain updated:
Mon Dec 2 11:28:00 2013 kern.info kernel: [ 12.970000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Mon Dec 2 11:28:00 2013 kern.info kernel: [ 12.980000] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Mon Dec 2 11:28:00 2013 kern.info kernel: [ 12.980000] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Mon Dec 2 11:28:00 2013 kern.info kernel: [ 12.990000] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Mon Dec 2 11:28:00 2013 kern.info kernel: [ 13.000000] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Mon Dec 2 11:28:00 2013 kern.info kernel: [ 13.010000] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Mon Dec 2 11:28:00 2013 kern.debug kernel: [ 13.160000] ath: EEPROM regdomain: 0x0
Mon Dec 2 11:28:00 2013 kern.debug kernel: [ 13.160000] ath: EEPROM indicates default country code should be used
Mon Dec 2 11:28:00 2013 kern.debug kernel: [ 13.160000] ath: doing EEPROM country->regdmn map search
Mon Dec 2 11:28:00 2013 kern.debug kernel: [ 13.160000] ath: country maps to regdmn code: 0x3a
Mon Dec 2 11:28:00 2013 kern.debug kernel: [ 13.160000] ath: Country alpha2 being used: US
Mon Dec 2 11:28:00 2013 kern.debug kernel: [ 13.160000] ath: Regpair used: 0x3a
Mon Dec 2 11:28:00 2013 kern.debug kernel: [ 13.170000] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
Mon Dec 2 11:28:00 2013 kern.info kernel: [ 13.180000] cfg80211: Calling CRDA for country: US
Mon Dec 2 11:28:00 2013 kern.info kernel: [ 13.200000] cfg80211: Regulatory domain changed to country: US
Mon Dec 2 11:28:00 2013 kern.info kernel: [ 13.200000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Mon Dec 2 11:28:00 2013 kern.info kernel: [ 13.210000] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)
Mon Dec 2 11:28:00 2013 kern.info kernel: [ 13.220000] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm)
Mon Dec 2 11:28:00 2013 kern.info kernel: [ 13.220000] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Mon Dec 2 11:28:00 2013 kern.info kernel: [ 13.230000] cfg80211: (5490000 KHz - 5600000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Mon Dec 2 11:28:00 2013 kern.info kernel: [ 13.240000] cfg80211: (5650000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Mon Dec 2 11:28:00 2013 kern.info kernel: [ 13.250000] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)
Mon Dec 2 11:28:00 2013 kern.info kernel: [ 13.260000] ieee80211 phy0: Atheros AR9330 Rev:1 mem=0xb8100000, irq=2
Mon Dec 2 11:28:00 2013 user.info syslog: ran 16 iterations
Mon Dec 2 11:28:00 2013 daemon.info sysinit: kmod: ran 16 iterations
Mon Dec 2 11:28:04 2013 cron.info crond[575]: crond: crond (busybox 1.19.4) started, log level 5
Mon Dec 2 11:28:05 2013 daemon.notice netifd: Interface 'loopback' is now up
Mon Dec 2 11:28:05 2013 kern.info kernel: [ 17.840000] device eth0 entered promiscuous mode
Mon Dec 2 11:28:05 2013 daemon.notice netifd: Interface 'wan' is now up
Mon Dec 2 11:28:05 2013 authpriv.info dropbear[586]: Not backgrounding
Mon Dec 2 11:28:05 2013 daemon.notice netifd: lan (627): udhcpc (v1.19.4) started
Mon Dec 2 11:28:06 2013 daemon.notice netifd: lan (627): Sending discover...
Mon Dec 2 11:28:06 2013 user.notice firewall: Reloading firewall due to ifup of wan (eth1)
Mon Dec 2 11:28:07 2013 user.notice dnsmasq: DNS rebinding protection is active, will discard upstream RFC1918 responses!
Mon Dec 2 11:28:07 2013 user.notice dnsmasq: Allowing 127.0.0.0/8 responses
Mon Dec 2 11:28:08 2013 daemon.info sysinit: /etc/config/miner_pic.hex
Mon Dec 2 11:28:08 2013 kern.warn kernel: [ 20.850000] no int in filled
Mon Dec 2 11:28:08 2013 daemon.info dnsmasq[693]: started, version 2.66 cachesize 150
Mon Dec 2 11:28:08 2013 daemon.info dnsmasq[693]: compile time options: IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack no-ipset no-auth
Mon Dec 2 11:28:08 2013 daemon.info dnsmasq[693]: using local addresses only for domain lan
Mon Dec 2 11:28:08 2013 daemon.info dnsmasq[693]: reading /tmp/resolv.conf.auto
Mon Dec 2 11:28:08 2013 daemon.info dnsmasq[693]: using nameserver 8.8.8.8#53
Mon Dec 2 11:28:08 2013 daemon.info dnsmasq[693]: using local addresses only for domain lan
Mon Dec 2 11:28:08 2013 daemon.info dnsmasq[693]: read /etc/hosts - 1 addresses
Mon Dec 2 11:28:08 2013 daemon.info sysinit: pic update
Mon Dec 2 11:28:08 2013 daemon.info sysinit: open /dev/bitmainbl0 ok fd = 0x3
Mon Dec 2 11:28:08 2013 daemon.info sysinit: read data
Mon Dec 2 11:28:08 2013 daemon.info sysinit: [0]{0x1}, [1]{0x10}, [2]{0x1}, [3]{0x10}, [4]{0x1}, [5]{0}, [6]{0x10}, [7]{0x1}, [8]{0x10}, [9]{0x4}, [10]{0x4},
Mon Dec 2 11:28:08 2013 daemon.info sysinit: Version 1.0
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 (627): Sending discover...
Mon Dec 2 11:28:09 2013 kern.info kernel: [ 22.260000] usb 1-1.1: USB disconnect, device number 3
Mon Dec 2 11:28:09 2013 kern.info kernel: [ 22.270000] eth1: link up (100Mbps/Full duplex)
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: [ 23.150000] 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.300000] 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.310000] PIC microchip usb OK
Mon Dec 2 11:28:12 2013 daemon.notice netifd: lan (627): Sending discover...
Mon Dec 2 11:28:14 2013 daemon.info sysinit: ntpd: resolved peer 3.openwrt.pool.ntp.org to 121.0.0.41
Mon Dec 2 11:28:14 2013 daemon.info sysinit: ntpd: sent query to 121.0.0.41
Mon Dec 2 11:28:17 2013 daemon.info sysinit: ntpd: resolved peer 2.openwrt.pool.ntp.org to 27.54.95.12
Mon Dec 2 11:28:17 2013 daemon.info sysinit: ntpd: sent query to 27.54.95.12
Mon Dec 2 11:28:19 2013 daemon.info sysinit: ntpd: resolved peer 1.openwrt.pool.ntp.org to 202.127.210.36
Mon Dec 2 11:28:19 2013 daemon.info sysinit: ntpd: sent query to 202.127.210.36
Mon Dec 2 11:28:23 2013 daemon.info sysinit: ntpd: resolved peer 0.openwrt.pool.ntp.org to 27.54.95.11
Mon Dec 2 11:28:23 2013 daemon.info sysinit: ntpd: sent query to 27.54.95.11
Mon Dec 2 11:28:23 2013 daemon.info sysinit: Alarm clock
Mon Dec 2 11:28:23 2013 daemon.info sysinit: --bitmain-options 115200:32:8:40:350:4d81 -o stratum+tcp://stratum.bitcoin.cz:3333 -O XxXScarecrowXxX.worker1:LfDacYac --api-listen --api-network
Mon Dec 2 11:28:23 2013 daemon.info sysinit: - init complete -
Mon Dec 2 11:28:23 2013 kern.info kernel: [ 36.430000] bitmain 1-1.1:1.0: USB Bitmain asic #0 now disconnected
Wed Aug 6 18:42:35 2014 cron.err crond[575]: time disparity of 356113 minutes detected
My WAN config has ipv4: 192.168.1.99
netmask: 255.255.255.0
gateway: 192.168.1.1
broadcast: 192.168.1.255
dns: 8.8.8.8
Any thoughts?
I can't see any reason why there would be a difference between the two - its a single rail PSU.
Ok great thank you.
Hi, wonder if anyone can help me please.
I've just purchased a Corsair RM1000 modular gold PSU and 2 antminer S1's and was wondering about where to plug them into the power supply.
They haven't been delivered yet but want to know what to do when they arrive.
I've attached an image to show the rear of the psu and have marked outputs 1 & 2.
Can anyone please tell me if I have to connect one on each (1 & 2) or both on 1 or 2.
Sorry for noob question, have only mined with graphics cards before.
I've just purchased a Corsair RM1000 modular gold PSU and 2 antminer S1's and was wondering about where to plug them into the power supply.
They haven't been delivered yet but want to know what to do when they arrive.
I've attached an image to show the rear of the psu and have marked outputs 1 & 2.
Can anyone please tell me if I have to connect one on each (1 & 2) or both on 1 or 2.
Sorry for noob question, have only mined with graphics cards before.
I can't see any reason why there would be a difference between the two - its a single rail PSU.
Thank you!
I guess that I am naive, but I made the foolish assumption that Multipool was legit. Maybe it is, but as soon as I switched to BTC Guild, it started working!
Thank you again!
I guess that I am naive, but I made the foolish assumption that Multipool was legit. Maybe it is, but as soon as I switched to BTC Guild, it started working!
Thank you again!
It may or may not be, but in that particular case it wasn't crediting you for work you were doing correctly.
Hi, wonder if anyone can help me please.
I've just purchased a Corsair RM1000 modular gold PSU and 2 antminer S1's and was wondering about where to plug them into the power supply.
They haven't been delivered yet but want to know what to do when they arrive.
I've attached an image to show the rear of the psu and have marked outputs 1 & 2.
Can anyone please tell me if I have to connect one on each (1 & 2) or both on 1 or 2.
Sorry for noob question, have only mined with graphics cards before.
I've just purchased a Corsair RM1000 modular gold PSU and 2 antminer S1's and was wondering about where to plug them into the power supply.
They haven't been delivered yet but want to know what to do when they arrive.
I've attached an image to show the rear of the psu and have marked outputs 1 & 2.
Can anyone please tell me if I have to connect one on each (1 & 2) or both on 1 or 2.
Sorry for noob question, have only mined with graphics cards before.
Thank you for your reply. I have restarted them several times over. No go. Consistently hashing but producing rejects and not showing up as mining on my Multipool mining portal.
Any additional thoughts or guidance are appreciated.
Robert
Any additional thoughts or guidance are appreciated.
Robert
Take a screenshot of the entire status page please
Miner 1: http://imgur.com/ZrN5dWR
Miner 2: http://imgur.com/MAcJnmz
Miner3: http://imgur.com/e8wphGo
Change pool to btcguild or something sensible, its the pool rejecting/stealing your work. Everything else is fine.
Thank you!
I guess that I am naive, but I made the foolish assumption that Multipool was legit. Maybe it is, but as soon as I switched to BTC Guild, it started working!
Thank you again!
Thank you for your reply. I have restarted them several times over. No go. Consistently hashing but producing rejects and not showing up as mining on my Multipool mining portal.
Any additional thoughts or guidance are appreciated.
Robert
Any additional thoughts or guidance are appreciated.
Robert
Take a screenshot of the entire status page please
Miner 1: http://imgur.com/ZrN5dWR
Miner 2: http://imgur.com/MAcJnmz
Miner3: http://imgur.com/e8wphGo
Change pool to btcguild or something sensible, its the pool rejecting/stealing your work. Everything else is fine.
Thank you for your reply. I have restarted them several times over. No go. Consistently hashing but producing rejects and not showing up as mining on my Multipool mining portal.
Any additional thoughts or guidance are appreciated.
Robert
Any additional thoughts or guidance are appreciated.
Robert
Take a screenshot of the entire status page please
Miner 1: http://imgur.com/ZrN5dWR
Miner 2: http://imgur.com/MAcJnmz
Miner3: http://imgur.com/e8wphGo
Thank you for your reply. I have restarted them several times over. No go. Consistently hashing but producing rejects and not showing up as mining on my Multipool mining portal.
Any additional thoughts or guidance are appreciated.
Robert
Any additional thoughts or guidance are appreciated.
Robert
Take a screenshot of the entire status page please
Thank you for your reply. I have restarted them several times over. No go. Consistently hashing but producing rejects and not showing up as mining on my Multipool mining portal.
Any additional thoughts or guidance are appreciated.
Robert
Any additional thoughts or guidance are appreciated.
Robert
Hi kind folks,
I have three S1s running and hashing - however they are only producing rejects. They are all hashing between 140 and 180, but not producing any "Accepted."
Here isa summary of my status pages for each miner:
Accepted Rejected HW Utility Discarded Stale LocalWork WU DiffA DiffR DiffS BestShare
0 594 406 0 86 58 68,392 2,316 0 38,016 1536 48,928
0 1,257 133 0 364 116 159,495 2,098 0 80,448 6400 107,015
0 393 2 0 376 4 183,404 2,444 0 100,608 256 149,481
Any thoughts and guidance on this would be greatly appreciated!
Thank you, sincerely!
Rob
I have three S1s running and hashing - however they are only producing rejects. They are all hashing between 140 and 180, but not producing any "Accepted."
Here isa summary of my status pages for each miner:
Accepted Rejected HW Utility Discarded Stale LocalWork WU DiffA DiffR DiffS BestShare
0 594 406 0 86 58 68,392 2,316 0 38,016 1536 48,928
0 1,257 133 0 364 116 159,495 2,098 0 80,448 6400 107,015
0 393 2 0 376 4 183,404 2,444 0 100,608 256 149,481
Any thoughts and guidance on this would be greatly appreciated!
Thank you, sincerely!
Rob
Restart them all.
Hi kind folks,
I have three S1s running and hashing - however they are only producing rejects. They are all hashing between 140 and 180, but not producing any "Accepted."
Here isa summary of my status pages for each miner:
Accepted Rejected HW Utility Discarded Stale LocalWork WU DiffA DiffR DiffS BestShare
0 594 406 0 86 58 68,392 2,316 0 38,016 1536 48,928
0 1,257 133 0 364 116 159,495 2,098 0 80,448 6400 107,015
0 393 2 0 376 4 183,404 2,444 0 100,608 256 149,481
Any thoughts and guidance on this would be greatly appreciated!
Thank you, sincerely!
Rob
I have three S1s running and hashing - however they are only producing rejects. They are all hashing between 140 and 180, but not producing any "Accepted."
Here isa summary of my status pages for each miner:
Accepted Rejected HW Utility Discarded Stale LocalWork WU DiffA DiffR DiffS BestShare
0 594 406 0 86 58 68,392 2,316 0 38,016 1536 48,928
0 1,257 133 0 364 116 159,495 2,098 0 80,448 6400 107,015
0 393 2 0 376 4 183,404 2,444 0 100,608 256 149,481
Any thoughts and guidance on this would be greatly appreciated!
Thank you, sincerely!
Rob
Jump to: