Is Bitmain responding to anyone either via the message system here or via email?
I've got 1/3 of payments collected for a U2 order but nobody really wants to move funds until Bitmain updates us on the status of the U2. The website says shipping should have started yesterday, two other members appear to have either units in-hand or in transit now, and we're stalled due to lack of communication.
they have been pretty quiet for 2-3 days now, other than to state they are packing up S2 units. I imagine they are working pretty hard on that since its a bit of a step up from small psu-less devices |
|
|
|
Well, this week i predict 0.00000000 BTC divs.
So if I understand current situation, and where we are in the cycle, sample chips were shipped to the many clients/manufacturers last week or yesterday. And also ASICminer is testing them. Questions are : Were the sample chips sent out for free?(Wasp, did you pay anything for samples? If yes, what was the price per Gh?). And meanwhile if AM is testing/hashing with them, where are they mining? I imagine the sample chips were likely free for wasp and any other big designers. $100 worth of chips is worth giving away if that person comes back looking for 10,000 more |
|
|
|
Ran out of shelves, had to make do.
I'm sure someone has asked, but what do you use to power the ants? Have you a quick howto/faq describing the parts for the server PSU and cabling? I'm currently using consumer Corsair 600W per overclocked ant and I'd like something cleaner. I can run dedicated 20A 120v circuits, so hopefully something that works with this. Thanks in advance he uses Delta DPS-2000BB server PSUs. (2000W) 200v-240v only In this picture I only have each Delta powering 4 overclocked Ants, but my normal set-up is 6 overclocked ants per PSU. (OC to 375) what sort of wiring are you using? 8AWG or even thicker? 150+ Amps is a lot of power to run over a weak wire |
|
|
|
awsome mod.
I applied it and set the clock at 325.
165 Gh pulling 277watts at the wall
normally 190gh pulls 380watts
Good to know. This mod makes the S1s theoretically cheaper per Ghash than the S2 without sacrificing much power consumption.
According to Jim above's volt mod experience S2 are still much better for power consumption for not much more BTC which i foresee batch 3 to be priced around $3000. 1000gh / 165 = 6.061 x 277 wall watts = 1678 watts 6.061 x S1's = 5.41 BTC Now add the cost of all the power supplies needed for 6 x S1's and the S2 batch 3 will clearly be the smarter option by far. only keep in mind that for the next 2-3 month window, having 1.2TH/2.4kW is better than 1TH/1kW. |
|
|
|
 the system logs of my s1 that's has zero hashrate [/Wed Dec 31 19:00:11 1969 kern.info kernel: [ 0.650000] ar933x-uart: ttyATH0 at MMIO 0x18020000 (irq = 11) is a AR933X UART
Wed Dec 31 19:00:11 1969 kern.info kernel: [ 0.660000] console [ttyATH0] enabled, bootconsole disabled
Wed Dec 31 19:00:11 1969 kern.info kernel: [ 0.670000] ath79-spi ath79-spi: master is unqueued, this is deprecated
Wed Dec 31 19:00:11 1969 kern.warn kernel: [ 0.680000] m25p80 spi0.0: found mx25l6405d, expected m25p80
Wed Dec 31 19:00:11 1969 kern.info kernel: [ 0.680000] m25p80 spi0.0: mx25l6405d (8192 Kbytes)
Wed Dec 31 19:00:11 1969 kern.notice kernel: [ 0.690000] 5 tp-link partitions found on MTD device spi0.0
Wed Dec 31 19:00:11 1969 kern.notice kernel: [ 0.690000] Creating 5 MTD partitions on "spi0.0":
Wed Dec 31 19:00:11 1969 kern.notice kernel: [ 0.700000] 0x000000000000-0x000000020000 : "u-boot"
Wed Dec 31 19:00:11 1969 kern.notice kernel: [ 0.700000] 0x000000020000-0x000000117d84 : "kernel"
Wed Dec 31 19:00:11 1969 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
Wed Dec 31 19:00:11 1969 kern.notice kernel: [ 0.720000] 0x000000117d84-0x0000007f0000 : "rootfs"
Wed Dec 31 19:00:11 1969 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
Wed Dec 31 19:00:11 1969 kern.notice kernel: [ 0.740000] mtd: partition "rootfs" set to be root filesystem
Wed Dec 31 19:00:11 1969 kern.info kernel: [ 0.740000] mtd: partition "rootfs_data" created automatically, ofs=0x370000, len=0x480000
Wed Dec 31 19:00:11 1969 kern.notice kernel: [ 0.750000] 0x000000370000-0x0000007f0000 : "rootfs_data"
Wed Dec 31 19:00:11 1969 kern.notice kernel: [ 0.760000] 0x000000020000-0x0000007f0000 : "firmware"
Wed Dec 31 19:00:11 1969 kern.notice kernel: [ 0.770000] 0x0000007f0000-0x000000800000 : "art"
Wed Dec 31 19:00:11 1969 kern.info kernel: [ 0.790000] libphy: ag71xx_mdio: probed
Wed Dec 31 19:00:11 1969 kern.info kernel: [ 0.790000] eth0: Atheros AG71xx at 0xba000000, irq 5, mode:GMII
Wed Dec 31 19:00:11 1969 kern.info kernel: [ 1.340000] eth0: Found an AR7240/AR9330 built-in switch
Wed Dec 31 19:00:11 1969 kern.info kernel: [ 2.380000] eth1: Atheros AG71xx at 0xb9000000, irq 4, mode:MII
Wed Dec 31 19:00:11 1969 kern.info kernel: [ 2.930000] ag71xx ag71xx.0 eth1: connected to PHY at ag71xx-mdio.1:04 [uid=004dd041, driver=Generic PHY]
Wed Dec 31 19:00:11 1969 kern.info kernel: [ 2.940000] TCP: cubic registered
Wed Dec 31 19:00:11 1969 kern.info kernel: [ 2.940000] NET: Registered protocol family 17
Wed Dec 31 19:00:11 1969 kern.info kernel: [ 2.950000] 8021q: 802.1Q VLAN Support v1.8
Wed Dec 31 19:00:11 1969 kern.info kernel: [ 2.960000] VFS: Mounted root (squashfs filesystem) readonly on device 31:2.
Wed Dec 31 19:00:11 1969 kern.info kernel: [ 2.970000] Freeing unused kernel memory: 232K (80316000 - 80350000)
Wed Dec 31 19:00:11 1969 kern.info kernel: [ 5.800000] usbcore: registered new interface driver usbfs
Wed Dec 31 19:00:11 1969 kern.info kernel: [ 5.800000] usbcore: registered new interface driver hub
Wed Dec 31 19:00:11 1969 kern.info kernel: [ 5.810000] usbcore: registered new device driver usb
Wed Dec 31 19:00:11 1969 kern.info kernel: [ 5.810000] usbcore: registered new interface driver bitmain
Wed Dec 31 19:00:11 1969 kern.warn kernel: [ 5.820000] hash ok
Wed Dec 31 19:00:11 1969 kern.warn kernel: [ 5.820000] hashtest OK
Wed Dec 31 19:00:11 1969 kern.err kernel: [ 5.820000] bitmain-asic: success to register device
Wed Dec 31 19:00:11 1969 kern.info kernel: [ 5.830000] usbcore: registered new interface driver bitmainbl
Wed Dec 31 19:00:11 1969 kern.info kernel: [ 5.840000] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Wed Dec 31 19:00:11 1969 kern.info kernel: [ 5.850000] ehci-platform: EHCI generic platform driver
Wed Dec 31 19:00:11 1969 kern.info kernel: [ 5.850000] ehci-platform ehci-platform: EHCI Host Controller
Wed Dec 31 19:00:11 1969 kern.info kernel: [ 5.860000] ehci-platform ehci-platform: new USB bus registered, assigned bus number 1
Wed Dec 31 19:00:11 1969 kern.info kernel: [ 5.870000] ehci-platform ehci-platform: irq 3, io mem 0x1b000000
Wed Dec 31 19:00:11 1969 kern.info kernel: [ 5.890000] ehci-platform ehci-platform: USB 2.0 started, EHCI 1.00
Wed Dec 31 19:00:11 1969 kern.info kernel: [ 5.890000] hub 1-0:1.0: USB hub found
Wed Dec 31 19:00:11 1969 kern.info kernel: [ 5.890000] hub 1-0:1.0: 1 port detected
Wed Dec 31 19:00:11 1969 kern.info kernel: [ 6.230000] usb 1-1: new high-speed USB device number 2 using ehci-platform
Wed Dec 31 19:00:11 1969 kern.info kernel: [ 6.380000] hub 1-1:1.0: USB hub found
Wed Dec 31 19:00:11 1969 kern.info kernel: [ 6.380000] hub 1-1:1.0: 2 ports detected
Wed Dec 31 19:00:11 1969 kern.notice kernel: [ 10.580000] jffs2: notice: (324) jffs2_build_xattr_subsystem: complete building xattr subsystem, 41 of xdatum (0 unchecked, 40 orphan) and 142 of xref (0 dead, 127 orphan) found.
Mon Mar 31 11:43:00 2014 daemon.info sysinit: Mon Mar 31 15:43:00 UTC 2014
Mon Mar 31 11:43:00 2014 user.emerg syslog: kmodloader: loading kernel modules from /etc/modules.d/**
Mon Mar 31 11:43:00 2014 kern.info kernel: [ 12.920000] hidraw: raw HID events driver (C) Jiri Kosina
Mon Mar 31 11:43:00 2014 kern.info kernel: [ 12.920000] Loading modules backported from Linux version master-2013-06-27-0-gdcfa6d5
Mon Mar 31 11:43:00 2014 kern.info kernel: [ 12.930000] Backport generated by backports.git backports-20130617-4-ge3220f5
Mon Mar 31 11:43:00 2014 kern.info kernel: [ 12.940000] nf_conntrack version 0.5.0 (962 buckets, 3848 max)
Mon Mar 31 11:43:00 2014 kern.info kernel: [ 12.970000] usbcore: registered new interface driver usbhid
Mon Mar 31 11:43:00 2014 kern.info kernel: [ 12.970000] usbhid: USB HID core driver
Mon Mar 31 11:43:00 2014 kern.info kernel: [ 12.980000] usbcore: registered new interface driver usbserial
Mon Mar 31 11:43:00 2014 kern.info kernel: [ 12.990000] usbcore: registered new interface driver usbserial_generic
Mon Mar 31 11:43:00 2014 kern.info kernel: [ 12.990000] usbserial: USB Serial support registered for generic
Mon Mar 31 11:43:00 2014 kern.info kernel: [ 13.020000] xt_time: kernel timezone is -0000
Mon Mar 31 11:43:00 2014 kern.info kernel: [ 13.060000] cfg80211: Calling CRDA to update world regulatory domain
Mon Mar 31 11:43:00 2014 kern.info kernel: [ 13.060000] cfg80211: World regulatory domain updated:
Mon Mar 31 11:43:00 2014 kern.info kernel: [ 13.070000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Mon Mar 31 11:43:00 2014 kern.info kernel: [ 13.080000] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Mon Mar 31 11:43:00 2014 kern.info kernel: [ 13.080000] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Mon Mar 31 11:43:00 2014 kern.info kernel: [ 13.090000] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Mon Mar 31 11:43:00 2014 kern.info kernel: [ 13.100000] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Mon Mar 31 11:43:00 2014 kern.info kernel: [ 13.110000] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Mon Mar 31 11:43:00 2014 kern.info kernel: [ 13.120000] ip_tables: (C) 2000-2006 Netfilter Core Team
Mon Mar 31 11:43:00 2014 kern.debug kernel: [ 13.250000] ath: EEPROM regdomain: 0x0
Mon Mar 31 11:43:00 2014 kern.debug kernel: [ 13.250000] ath: EEPROM indicates default country code should be used
Mon Mar 31 11:43:00 2014 kern.debug kernel: [ 13.250000] ath: doing EEPROM country->regdmn map search
Mon Mar 31 11:43:00 2014 kern.debug kernel: [ 13.250000] ath: country maps to regdmn code: 0x3a
Mon Mar 31 11:43:00 2014 kern.debug kernel: [ 13.250000] ath: Country alpha2 being used: US
Mon Mar 31 11:43:00 2014 kern.debug kernel: [ 13.250000] ath: Regpair used: 0x3a
Mon Mar 31 11:43:00 2014 kern.debug kernel: [ 13.260000] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
Mon Mar 31 11:43:00 2014 kern.info kernel: [ 13.270000] cfg80211: Calling CRDA for country: US
Mon Mar 31 11:43:00 2014 kern.info kernel: [ 13.270000] cfg80211: Regulatory domain changed to country: US
Mon Mar 31 11:43:00 2014 kern.info kernel: [ 13.280000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Mon Mar 31 11:43:00 2014 kern.info kernel: [ 13.290000] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)
Mon Mar 31 11:43:00 2014 kern.info kernel: [ 13.300000] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm)
Mon Mar 31 11:43:00 2014 kern.info kernel: [ 13.300000] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Mon Mar 31 11:43:00 2014 kern.info kernel: [ 13.310000] cfg80211: (5490000 KHz - 5600000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Mon Mar 31 11:43:00 2014 kern.info kernel: [ 13.320000] cfg80211: (5650000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Mon Mar 31 11:43:00 2014 kern.info kernel: [ 13.330000] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)
Mon Mar 31 11:43:00 2014 kern.info kernel: [ 13.340000] ieee80211 phy0: Atheros AR9330 Rev:1 mem=0xb8100000, irq=2
Mon Mar 31 11:43:00 2014 user.info syslog: ran 16 iterations
Mon Mar 31 11:43:00 2014 daemon.info sysinit: kmod: ran 16 iterations
Mon Mar 31 11:43:04 2014 cron.info crond[569]: crond: crond (busybox 1.19.4) started, log level 8
Mon Mar 31 11:43:05 2014 daemon.notice netifd: Interface 'loopback' is now up
Mon Mar 31 11:43:05 2014 kern.info kernel: [ 17.950000] device eth0 entered promiscuous mode
Mon Mar 31 11:43:05 2014 daemon.notice netifd: Interface 'wan' is now up
Mon Mar 31 11:43:05 2014 authpriv.info dropbear[580]: Not backgrounding
Mon Mar 31 11:43:05 2014 daemon.notice netifd: lan (617): udhcpc (v1.19.4) started
Mon Mar 31 11:43:06 2014 daemon.notice netifd: lan (617): Sending discover...
Mon Mar 31 11:43:06 2014 user.notice firewall: Reloading firewall due to ifup of wan (eth1)
Mon Mar 31 11:43:07 2014 kern.info kernel: [ 20.100000] eth1: link up (100Mbps/Full duplex)
Mon Mar 31 11:43:07 2014 user.notice dnsmasq: DNS rebinding protection is active, will discard upstream RFC1918 responses!
Mon Mar 31 11:43:07 2014 user.notice dnsmasq: Allowing 127.0.0.0/8 responses
Mon Mar 31 11:43:08 2014 daemon.info dnsmasq[689]: started, version 2.66 cachesize 150
Mon Mar 31 11:43:08 2014 daemon.info dnsmasq[689]: 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 Mar 31 11:43:08 2014 daemon.info dnsmasq[689]: using local addresses only for domain lan
Mon Mar 31 11:43:08 2014 daemon.info dnsmasq[689]: reading /tmp/resolv.conf.auto
Mon Mar 31 11:43:08 2014 daemon.info dnsmasq[689]: using nameserver 192.168.2.1#53
Mon Mar 31 11:43:08 2014 daemon.info dnsmasq[689]: using local addresses only for domain lan
Mon Mar 31 11:43:08 2014 daemon.info dnsmasq[689]: read /etc/hosts - 1 addresses
Mon Mar 31 11:43:08 2014 daemon.info sysinit: /etc/config/miner_pic.hex
Mon Mar 31 11:43:08 2014 daemon.info sysinit: Unable to open /dev/bitmainbl0: No such file or directory
Mon Mar 31 11:43:08 2014 daemon.info sysinit: pic update
Mon Mar 31 11:43:08 2014 daemon.info sysinit: setting up led WAN
Mon Mar 31 11:43:08 2014 daemon.info sysinit: setting up led WANL
Mon Mar 31 11:43:08 2014 daemon.info sysinit: setting up led LAN1
Mon Mar 31 11:43:08 2014 daemon.info sysinit: setting up led LAN2
Mon Mar 31 11:43:08 2014 daemon.info sysinit: setting up led LAN3
Mon Mar 31 11:43:08 2014 daemon.info sysinit: setting up led LAN4
Mon Mar 31 11:43:08 2014 daemon.info sysinit: setting up led WLAN
Mon Mar 31 11:43:09 2014 daemon.notice netifd: lan (617): Sending discover...
Mon Mar 31 11:43:12 2014 daemon.notice netifd: lan (617): Sending discover...
Mon Mar 31 11:43:12 2014 daemon.info sysinit: ntpd: resolved peer 3.openwrt.pool.ntp.org to 206.186.121.125
Mon Mar 31 11:43:12 2014 daemon.info sysinit: ntpd: sent query to 206.186.121.125
Mon Mar 31 11:43:13 2014 daemon.info sysinit: ntpd: resolved peer 2.openwrt.pool.ntp.org to 206.108.0.131
Mon Mar 31 11:43:13 2014 daemon.info sysinit: ntpd: sent query to 206.108.0.131
Mon Mar 31 11:43:13 2014 daemon.info sysinit: ntpd: resolved peer 1.openwrt.pool.ntp.org to 67.215.197.151
Mon Mar 31 11:43:13 2014 daemon.info sysinit: ntpd: sent query to 67.215.197.151
Mon Mar 31 11:43:14 2014 daemon.info sysinit: ntpd: resolved peer 0.openwrt.pool.ntp.org to 198.50.209.202
Mon Mar 31 11:43:14 2014 daemon.info sysinit: ntpd: sent query to 198.50.209.202
Mon Mar 31 11:43:14 2014 daemon.info sysinit: ntpd: reply from 206.186.121.125: reach 0x01 offset 62.000103 delay 2.299706 status 0x24 strat 2 refid 0x1896cb96 rootdelay 0.009018
Mon Mar 31 11:43:14 2014 daemon.info sysinit: ntpd: reply from 206.108.0.131: reach 0x01 offset 62.559352 delay 1.177639 status 0x24 strat 1 refid 0x50505300 rootdelay 0.000000
Mon Mar 31 11:43:14 2014 daemon.info sysinit: ntpd: reply from 67.215.197.151: reach 0x01 offset 62.672879 delay 0.962987 status 0x24 strat 2 refid 0xd8ab7824 rootdelay 0.018143
Mon Mar 31 11:43:14 2014 daemon.info sysinit: ntpd: reply from 198.50.209.202: reach 0x01 offset 63.135136 delay 0.040115 status 0x24 strat 3 refid 0x80643887 rootdelay 0.009461
Mon Mar 31 11:43:15 2014 daemon.info sysinit: ntpd: sent query to 206.186.121.125
Mon Mar 31 11:43:15 2014 daemon.info sysinit: ntpd: sent query to 206.108.0.131
Mon Mar 31 11:43:15 2014 daemon.info sysinit: ntpd: sent query to 67.215.197.151
Mon Mar 31 11:43:15 2014 daemon.info sysinit: ntpd: sent query to 198.50.209.202
Mon Mar 31 11:43:15 2014 daemon.info sysinit: ntpd: reply from 206.186.121.125: reach 0x03 offset 63.133026 delay 0.033123 status 0x24 strat 2 refid 0x1896cb96 rootdelay 0.009018
Mon Mar 31 11:43:15 2014 daemon.info sysinit: ntpd: reply from 206.108.0.131: reach 0x03 offset 63.132975 delay 0.033267 status 0x24 strat 1 refid 0x50505300 rootdelay 0.000000
Mon Mar 31 11:43:15 2014 daemon.info sysinit: ntpd: reply from 67.215.197.151: reach 0x03 offset 63.135321 delay 0.043926 status 0x24 strat 2 refid 0xd8ab7824 rootdelay 0.018143
Mon Mar 31 11:43:15 2014 daemon.info sysinit: ntpd: reply from 198.50.209.202: reach 0x03 offset 63.137362 delay 0.044243 status 0x24 strat 3 refid 0x80643887 rootdelay 0.009461
Mon Mar 31 11:43:16 2014 daemon.info sysinit: ntpd: sent query to 206.186.121.125
Mon Mar 31 11:43:16 2014 daemon.info sysinit: ntpd: sent query to 67.215.197.151
Mon Mar 31 11:43:17 2014 daemon.info sysinit: ntpd: reply from 206.186.121.125: reach 0x07 offset 63.132578 delay 0.032586 status 0x24 strat 2 refid 0x1896cb96 rootdelay 0.009018
Mon Mar 31 11:43:17 2014 daemon.info sysinit: ntpd: reply from 67.215.197.151: reach 0x07 offset 63.134666 delay 0.041811 status 0x24 strat 2 refid 0xd8ab7824 rootdelay 0.018143
Mon Mar 31 11:43:18 2014 daemon.info sysinit: ntpd: sent query to 206.186.121.125
Mon Mar 31 11:43:18 2014 daemon.info sysinit: ntpd: sent query to 206.108.0.131
Mon Mar 31 11:43:18 2014 daemon.info sysinit: ntpd: sent query to 67.215.197.151
Mon Mar 31 11:43:18 2014 daemon.info sysinit: ntpd: sent query to 198.50.209.202
Mon Mar 31 11:43:18 2014 daemon.info sysinit: ntpd: reply from 206.186.121.125: reach 0x0f offset 63.131501 delay 0.034086 status 0x24 strat 2 refid 0x1896cb96 rootdelay 0.009018
Mon Mar 31 11:43:18 2014 daemon.info sysinit: ntpd: reply from 206.108.0.131: reach 0x07 offset 63.131927 delay 0.034293 status 0x24 strat 1 refid 0x50505300 rootdelay 0.000000
Mon Mar 31 11:43:18 2014 daemon.info sysinit: ntpd: reply from 198.50.209.202: reach 0x07 offset 63.137826 delay 0.042555 status 0x24 strat 3 refid 0x80643887 rootdelay 0.009461
Mon Mar 31 11:43:18 2014 daemon.info sysinit: ntpd: reply from 67.215.197.151: reach 0x0f offset 63.134811 delay 0.044772 status 0x24 strat 2 refid 0xd8ab7824 rootdelay 0.018143
Mon Mar 31 11:43:19 2014 daemon.info sysinit: ntpd: sent query to 206.186.121.125
Mon Mar 31 11:43:19 2014 daemon.info sysinit: ntpd: sent query to 206.108.0.131
Mon Mar 31 11:43:19 2014 daemon.info sysinit: ntpd: sent query to 67.215.197.151
Mon Mar 31 11:43:19 2014 daemon.info sysinit: ntpd: sent query to 198.50.209.202
Mon Mar 31 11:43:19 2014 daemon.info sysinit: ntpd: reply from 206.186.121.125: reach 0x1f offset 63.132505 delay 0.035210 status 0x24 strat 2 refid 0x1896cb96 rootdelay 0.009018
Mon Mar 31 11:43:19 2014 daemon.info sysinit: ntpd: reply from 206.108.0.131: reach 0x0f offset 63.132456 delay 0.035414 status 0x24 strat 1 refid 0x50505300 rootdelay 0.000000
Mon Mar 31 11:43:19 2014 daemon.info sysinit: ntpd: reply from 198.50.209.202: reach 0x0f offset 63.136858 delay 0.041736 status 0x24 strat 3 refid 0x80643887 rootdelay 0.009461
Mon Mar 31 11:43:19 2014 daemon.info sysinit: ntpd: reply from 67.215.197.151: reach 0x1f offset 63.135846 delay 0.043975 status 0x24 strat 2 refid 0xd8ab7824 rootdelay 0.018143
Mon Mar 31 11:43:20 2014 daemon.info sysinit: ntpd: sent query to 206.108.0.131
Mon Mar 31 11:43:20 2014 daemon.info sysinit: ntpd: sent query to 198.50.209.202
Mon Mar 31 11:44:23 2014 daemon.info sysinit: ntpd: reply from 206.108.0.131: reach 0x1f offset 63.131849 delay 0.033145 status 0x24 strat 1 refid 0x50505300 rootdelay 0.000000
Mon Mar 31 11:44:23 2014 daemon.info sysinit: ntpd: setting clock to Mon Mar 31 11:44:23 EDT 2014 (offset 63.060448s)
Mon Mar 31 11:44:23 2014 daemon.info sysinit: --bitmain-options 115200:32:8:40:350:4d81 -o http://btc.e-pool.net:8800 -O 1MWhaSUrp3Cd8PQYGr3YNyperSRVmYDad7:1234 --api-listen --api-network
Mon Mar 31 11:44:23 2014 daemon.info sysinit: - init complete -
Mon Mar 31 11:45:04 2014 cron.info crond[569]: crond: USER root pid 1046 cmd /usr/bin/cgminer-monitor
Mon Mar 31 11:48:01 2014 cron.info crond[569]: crond: USER root pid 1324 cmd /usr/bin/cgminer-monitor
Mon Mar 31 11:51:01 2014 cron.info crond[569]: crond: USER root pid 1371 cmd /usr/bin/cgminer-monitor
Mon Mar 31 11:54:01 2014 cron.info crond[569]: crond: USER root pid 1421 cmd /usr/bin/cgminer-monitor
Mon Mar 31 11:57:01 2014 cron.info crond[569]: crond: USER root pid 1583 cmd /usr/bin/cgminer-monitor
code] here is a similar (same?) issue with an avalon a few months back. Your issue is definitely with the network or network settings, and not the actual function of the miner (other than settings) https://bitcointalk.org/index.php?topic=416940.40post your network settings and if DHCP is disabled. It seems certainly a network settings issue and not with the pool settings [img  ][/img] [img  ][/img] heres what i would try in his order: 1) clear the 'ipv4 broadcast' box. sometimes it works, but i have always cleared it on every antminer of mine and its worked on multiple networks fault-free 2) remove the 'stratum+tcp'. your pool address can start with 'pool.' and work just fine. probably not your issue, but a way to simplify the pool info 3) double-check that your router ip is actually 192.168.2.1 - just in case it is a 192.168.1.1 since that would cause big issues 4) reboot. looking at your stats page, im trying to recall whether it will show chip stats if not hashing, or if your chips perhaps are not hashing. whats your power supply? seems unlikely but some units under a 600W rating do not work well for antminers |
|
|
|
So, in your opinion, would DTS's solution to underclock the miner and include a provision in the TOS that modifying the clock speed would void the warranty work?
If I was Ken, I'd just throw a cooler on it and treat it like a graphics card as far as warranty - modifications void it. You can't really say that though if you need to mod the product to get it to work in the first place. it would likely require selling the product as 420GH/400W in order to be manageable with a copper heatsink and fan. You could say modification to an H80i voids warranty but can allow 20% of overclocking. (however, this simple mod woulod be employed by most buyers rendering the heatsink a waste of funds. I think clear warnings about heatsink installation would be sufficient reasonable effort in a civil (common-sense) situation. failure rates should be pretty low, but there will always be that one person whose only tools are a tiny phillips or a pocket knife or that globs on thermal paste |
|
|
|
the system logs of my s1 that's has zero hashrate [/Wed Dec 31 19:00:11 1969 kern.info kernel: [ 0.650000] ar933x-uart: ttyATH0 at MMIO 0x18020000 (irq = 11) is a AR933X UART
Wed Dec 31 19:00:11 1969 kern.info kernel: [ 0.660000] console [ttyATH0] enabled, bootconsole disabled
Wed Dec 31 19:00:11 1969 kern.info kernel: [ 0.670000] ath79-spi ath79-spi: master is unqueued, this is deprecated
Wed Dec 31 19:00:11 1969 kern.warn kernel: [ 0.680000] m25p80 spi0.0: found mx25l6405d, expected m25p80
Wed Dec 31 19:00:11 1969 kern.info kernel: [ 0.680000] m25p80 spi0.0: mx25l6405d (8192 Kbytes)
Wed Dec 31 19:00:11 1969 kern.notice kernel: [ 0.690000] 5 tp-link partitions found on MTD device spi0.0
Wed Dec 31 19:00:11 1969 kern.notice kernel: [ 0.690000] Creating 5 MTD partitions on "spi0.0":
Wed Dec 31 19:00:11 1969 kern.notice kernel: [ 0.700000] 0x000000000000-0x000000020000 : "u-boot"
Wed Dec 31 19:00:11 1969 kern.notice kernel: [ 0.700000] 0x000000020000-0x000000117d84 : "kernel"
Wed Dec 31 19:00:11 1969 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
Wed Dec 31 19:00:11 1969 kern.notice kernel: [ 0.720000] 0x000000117d84-0x0000007f0000 : "rootfs"
Wed Dec 31 19:00:11 1969 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
Wed Dec 31 19:00:11 1969 kern.notice kernel: [ 0.740000] mtd: partition "rootfs" set to be root filesystem
Wed Dec 31 19:00:11 1969 kern.info kernel: [ 0.740000] mtd: partition "rootfs_data" created automatically, ofs=0x370000, len=0x480000
Wed Dec 31 19:00:11 1969 kern.notice kernel: [ 0.750000] 0x000000370000-0x0000007f0000 : "rootfs_data"
Wed Dec 31 19:00:11 1969 kern.notice kernel: [ 0.760000] 0x000000020000-0x0000007f0000 : "firmware"
Wed Dec 31 19:00:11 1969 kern.notice kernel: [ 0.770000] 0x0000007f0000-0x000000800000 : "art"
Wed Dec 31 19:00:11 1969 kern.info kernel: [ 0.790000] libphy: ag71xx_mdio: probed
Wed Dec 31 19:00:11 1969 kern.info kernel: [ 0.790000] eth0: Atheros AG71xx at 0xba000000, irq 5, mode:GMII
Wed Dec 31 19:00:11 1969 kern.info kernel: [ 1.340000] eth0: Found an AR7240/AR9330 built-in switch
Wed Dec 31 19:00:11 1969 kern.info kernel: [ 2.380000] eth1: Atheros AG71xx at 0xb9000000, irq 4, mode:MII
Wed Dec 31 19:00:11 1969 kern.info kernel: [ 2.930000] ag71xx ag71xx.0 eth1: connected to PHY at ag71xx-mdio.1:04 [uid=004dd041, driver=Generic PHY]
Wed Dec 31 19:00:11 1969 kern.info kernel: [ 2.940000] TCP: cubic registered
Wed Dec 31 19:00:11 1969 kern.info kernel: [ 2.940000] NET: Registered protocol family 17
Wed Dec 31 19:00:11 1969 kern.info kernel: [ 2.950000] 8021q: 802.1Q VLAN Support v1.8
Wed Dec 31 19:00:11 1969 kern.info kernel: [ 2.960000] VFS: Mounted root (squashfs filesystem) readonly on device 31:2.
Wed Dec 31 19:00:11 1969 kern.info kernel: [ 2.970000] Freeing unused kernel memory: 232K (80316000 - 80350000)
Wed Dec 31 19:00:11 1969 kern.info kernel: [ 5.800000] usbcore: registered new interface driver usbfs
Wed Dec 31 19:00:11 1969 kern.info kernel: [ 5.800000] usbcore: registered new interface driver hub
Wed Dec 31 19:00:11 1969 kern.info kernel: [ 5.810000] usbcore: registered new device driver usb
Wed Dec 31 19:00:11 1969 kern.info kernel: [ 5.810000] usbcore: registered new interface driver bitmain
Wed Dec 31 19:00:11 1969 kern.warn kernel: [ 5.820000] hash ok
Wed Dec 31 19:00:11 1969 kern.warn kernel: [ 5.820000] hashtest OK
Wed Dec 31 19:00:11 1969 kern.err kernel: [ 5.820000] bitmain-asic: success to register device
Wed Dec 31 19:00:11 1969 kern.info kernel: [ 5.830000] usbcore: registered new interface driver bitmainbl
Wed Dec 31 19:00:11 1969 kern.info kernel: [ 5.840000] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Wed Dec 31 19:00:11 1969 kern.info kernel: [ 5.850000] ehci-platform: EHCI generic platform driver
Wed Dec 31 19:00:11 1969 kern.info kernel: [ 5.850000] ehci-platform ehci-platform: EHCI Host Controller
Wed Dec 31 19:00:11 1969 kern.info kernel: [ 5.860000] ehci-platform ehci-platform: new USB bus registered, assigned bus number 1
Wed Dec 31 19:00:11 1969 kern.info kernel: [ 5.870000] ehci-platform ehci-platform: irq 3, io mem 0x1b000000
Wed Dec 31 19:00:11 1969 kern.info kernel: [ 5.890000] ehci-platform ehci-platform: USB 2.0 started, EHCI 1.00
Wed Dec 31 19:00:11 1969 kern.info kernel: [ 5.890000] hub 1-0:1.0: USB hub found
Wed Dec 31 19:00:11 1969 kern.info kernel: [ 5.890000] hub 1-0:1.0: 1 port detected
Wed Dec 31 19:00:11 1969 kern.info kernel: [ 6.230000] usb 1-1: new high-speed USB device number 2 using ehci-platform
Wed Dec 31 19:00:11 1969 kern.info kernel: [ 6.380000] hub 1-1:1.0: USB hub found
Wed Dec 31 19:00:11 1969 kern.info kernel: [ 6.380000] hub 1-1:1.0: 2 ports detected
Wed Dec 31 19:00:11 1969 kern.notice kernel: [ 10.580000] jffs2: notice: (324) jffs2_build_xattr_subsystem: complete building xattr subsystem, 41 of xdatum (0 unchecked, 40 orphan) and 142 of xref (0 dead, 127 orphan) found.
Mon Mar 31 11:43:00 2014 daemon.info sysinit: Mon Mar 31 15:43:00 UTC 2014
Mon Mar 31 11:43:00 2014 user.emerg syslog: kmodloader: loading kernel modules from /etc/modules.d/**
Mon Mar 31 11:43:00 2014 kern.info kernel: [ 12.920000] hidraw: raw HID events driver (C) Jiri Kosina
Mon Mar 31 11:43:00 2014 kern.info kernel: [ 12.920000] Loading modules backported from Linux version master-2013-06-27-0-gdcfa6d5
Mon Mar 31 11:43:00 2014 kern.info kernel: [ 12.930000] Backport generated by backports.git backports-20130617-4-ge3220f5
Mon Mar 31 11:43:00 2014 kern.info kernel: [ 12.940000] nf_conntrack version 0.5.0 (962 buckets, 3848 max)
Mon Mar 31 11:43:00 2014 kern.info kernel: [ 12.970000] usbcore: registered new interface driver usbhid
Mon Mar 31 11:43:00 2014 kern.info kernel: [ 12.970000] usbhid: USB HID core driver
Mon Mar 31 11:43:00 2014 kern.info kernel: [ 12.980000] usbcore: registered new interface driver usbserial
Mon Mar 31 11:43:00 2014 kern.info kernel: [ 12.990000] usbcore: registered new interface driver usbserial_generic
Mon Mar 31 11:43:00 2014 kern.info kernel: [ 12.990000] usbserial: USB Serial support registered for generic
Mon Mar 31 11:43:00 2014 kern.info kernel: [ 13.020000] xt_time: kernel timezone is -0000
Mon Mar 31 11:43:00 2014 kern.info kernel: [ 13.060000] cfg80211: Calling CRDA to update world regulatory domain
Mon Mar 31 11:43:00 2014 kern.info kernel: [ 13.060000] cfg80211: World regulatory domain updated:
Mon Mar 31 11:43:00 2014 kern.info kernel: [ 13.070000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Mon Mar 31 11:43:00 2014 kern.info kernel: [ 13.080000] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Mon Mar 31 11:43:00 2014 kern.info kernel: [ 13.080000] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Mon Mar 31 11:43:00 2014 kern.info kernel: [ 13.090000] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Mon Mar 31 11:43:00 2014 kern.info kernel: [ 13.100000] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Mon Mar 31 11:43:00 2014 kern.info kernel: [ 13.110000] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Mon Mar 31 11:43:00 2014 kern.info kernel: [ 13.120000] ip_tables: (C) 2000-2006 Netfilter Core Team
Mon Mar 31 11:43:00 2014 kern.debug kernel: [ 13.250000] ath: EEPROM regdomain: 0x0
Mon Mar 31 11:43:00 2014 kern.debug kernel: [ 13.250000] ath: EEPROM indicates default country code should be used
Mon Mar 31 11:43:00 2014 kern.debug kernel: [ 13.250000] ath: doing EEPROM country->regdmn map search
Mon Mar 31 11:43:00 2014 kern.debug kernel: [ 13.250000] ath: country maps to regdmn code: 0x3a
Mon Mar 31 11:43:00 2014 kern.debug kernel: [ 13.250000] ath: Country alpha2 being used: US
Mon Mar 31 11:43:00 2014 kern.debug kernel: [ 13.250000] ath: Regpair used: 0x3a
Mon Mar 31 11:43:00 2014 kern.debug kernel: [ 13.260000] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
Mon Mar 31 11:43:00 2014 kern.info kernel: [ 13.270000] cfg80211: Calling CRDA for country: US
Mon Mar 31 11:43:00 2014 kern.info kernel: [ 13.270000] cfg80211: Regulatory domain changed to country: US
Mon Mar 31 11:43:00 2014 kern.info kernel: [ 13.280000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Mon Mar 31 11:43:00 2014 kern.info kernel: [ 13.290000] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)
Mon Mar 31 11:43:00 2014 kern.info kernel: [ 13.300000] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm)
Mon Mar 31 11:43:00 2014 kern.info kernel: [ 13.300000] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Mon Mar 31 11:43:00 2014 kern.info kernel: [ 13.310000] cfg80211: (5490000 KHz - 5600000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Mon Mar 31 11:43:00 2014 kern.info kernel: [ 13.320000] cfg80211: (5650000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Mon Mar 31 11:43:00 2014 kern.info kernel: [ 13.330000] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)
Mon Mar 31 11:43:00 2014 kern.info kernel: [ 13.340000] ieee80211 phy0: Atheros AR9330 Rev:1 mem=0xb8100000, irq=2
Mon Mar 31 11:43:00 2014 user.info syslog: ran 16 iterations
Mon Mar 31 11:43:00 2014 daemon.info sysinit: kmod: ran 16 iterations
Mon Mar 31 11:43:04 2014 cron.info crond[569]: crond: crond (busybox 1.19.4) started, log level 8
Mon Mar 31 11:43:05 2014 daemon.notice netifd: Interface 'loopback' is now up
Mon Mar 31 11:43:05 2014 kern.info kernel: [ 17.950000] device eth0 entered promiscuous mode
Mon Mar 31 11:43:05 2014 daemon.notice netifd: Interface 'wan' is now up
Mon Mar 31 11:43:05 2014 authpriv.info dropbear[580]: Not backgrounding
Mon Mar 31 11:43:05 2014 daemon.notice netifd: lan (617): udhcpc (v1.19.4) started
Mon Mar 31 11:43:06 2014 daemon.notice netifd: lan (617): Sending discover...
Mon Mar 31 11:43:06 2014 user.notice firewall: Reloading firewall due to ifup of wan (eth1)
Mon Mar 31 11:43:07 2014 kern.info kernel: [ 20.100000] eth1: link up (100Mbps/Full duplex)
Mon Mar 31 11:43:07 2014 user.notice dnsmasq: DNS rebinding protection is active, will discard upstream RFC1918 responses!
Mon Mar 31 11:43:07 2014 user.notice dnsmasq: Allowing 127.0.0.0/8 responses
Mon Mar 31 11:43:08 2014 daemon.info dnsmasq[689]: started, version 2.66 cachesize 150
Mon Mar 31 11:43:08 2014 daemon.info dnsmasq[689]: 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 Mar 31 11:43:08 2014 daemon.info dnsmasq[689]: using local addresses only for domain lan
Mon Mar 31 11:43:08 2014 daemon.info dnsmasq[689]: reading /tmp/resolv.conf.auto
Mon Mar 31 11:43:08 2014 daemon.info dnsmasq[689]: using nameserver 192.168.2.1#53
Mon Mar 31 11:43:08 2014 daemon.info dnsmasq[689]: using local addresses only for domain lan
Mon Mar 31 11:43:08 2014 daemon.info dnsmasq[689]: read /etc/hosts - 1 addresses
Mon Mar 31 11:43:08 2014 daemon.info sysinit: /etc/config/miner_pic.hex
Mon Mar 31 11:43:08 2014 daemon.info sysinit: Unable to open /dev/bitmainbl0: No such file or directory
Mon Mar 31 11:43:08 2014 daemon.info sysinit: pic update
Mon Mar 31 11:43:08 2014 daemon.info sysinit: setting up led WAN
Mon Mar 31 11:43:08 2014 daemon.info sysinit: setting up led WANL
Mon Mar 31 11:43:08 2014 daemon.info sysinit: setting up led LAN1
Mon Mar 31 11:43:08 2014 daemon.info sysinit: setting up led LAN2
Mon Mar 31 11:43:08 2014 daemon.info sysinit: setting up led LAN3
Mon Mar 31 11:43:08 2014 daemon.info sysinit: setting up led LAN4
Mon Mar 31 11:43:08 2014 daemon.info sysinit: setting up led WLAN
Mon Mar 31 11:43:09 2014 daemon.notice netifd: lan (617): Sending discover...
Mon Mar 31 11:43:12 2014 daemon.notice netifd: lan (617): Sending discover...
Mon Mar 31 11:43:12 2014 daemon.info sysinit: ntpd: resolved peer 3.openwrt.pool.ntp.org to 206.186.121.125
Mon Mar 31 11:43:12 2014 daemon.info sysinit: ntpd: sent query to 206.186.121.125
Mon Mar 31 11:43:13 2014 daemon.info sysinit: ntpd: resolved peer 2.openwrt.pool.ntp.org to 206.108.0.131
Mon Mar 31 11:43:13 2014 daemon.info sysinit: ntpd: sent query to 206.108.0.131
Mon Mar 31 11:43:13 2014 daemon.info sysinit: ntpd: resolved peer 1.openwrt.pool.ntp.org to 67.215.197.151
Mon Mar 31 11:43:13 2014 daemon.info sysinit: ntpd: sent query to 67.215.197.151
Mon Mar 31 11:43:14 2014 daemon.info sysinit: ntpd: resolved peer 0.openwrt.pool.ntp.org to 198.50.209.202
Mon Mar 31 11:43:14 2014 daemon.info sysinit: ntpd: sent query to 198.50.209.202
Mon Mar 31 11:43:14 2014 daemon.info sysinit: ntpd: reply from 206.186.121.125: reach 0x01 offset 62.000103 delay 2.299706 status 0x24 strat 2 refid 0x1896cb96 rootdelay 0.009018
Mon Mar 31 11:43:14 2014 daemon.info sysinit: ntpd: reply from 206.108.0.131: reach 0x01 offset 62.559352 delay 1.177639 status 0x24 strat 1 refid 0x50505300 rootdelay 0.000000
Mon Mar 31 11:43:14 2014 daemon.info sysinit: ntpd: reply from 67.215.197.151: reach 0x01 offset 62.672879 delay 0.962987 status 0x24 strat 2 refid 0xd8ab7824 rootdelay 0.018143
Mon Mar 31 11:43:14 2014 daemon.info sysinit: ntpd: reply from 198.50.209.202: reach 0x01 offset 63.135136 delay 0.040115 status 0x24 strat 3 refid 0x80643887 rootdelay 0.009461
Mon Mar 31 11:43:15 2014 daemon.info sysinit: ntpd: sent query to 206.186.121.125
Mon Mar 31 11:43:15 2014 daemon.info sysinit: ntpd: sent query to 206.108.0.131
Mon Mar 31 11:43:15 2014 daemon.info sysinit: ntpd: sent query to 67.215.197.151
Mon Mar 31 11:43:15 2014 daemon.info sysinit: ntpd: sent query to 198.50.209.202
Mon Mar 31 11:43:15 2014 daemon.info sysinit: ntpd: reply from 206.186.121.125: reach 0x03 offset 63.133026 delay 0.033123 status 0x24 strat 2 refid 0x1896cb96 rootdelay 0.009018
Mon Mar 31 11:43:15 2014 daemon.info sysinit: ntpd: reply from 206.108.0.131: reach 0x03 offset 63.132975 delay 0.033267 status 0x24 strat 1 refid 0x50505300 rootdelay 0.000000
Mon Mar 31 11:43:15 2014 daemon.info sysinit: ntpd: reply from 67.215.197.151: reach 0x03 offset 63.135321 delay 0.043926 status 0x24 strat 2 refid 0xd8ab7824 rootdelay 0.018143
Mon Mar 31 11:43:15 2014 daemon.info sysinit: ntpd: reply from 198.50.209.202: reach 0x03 offset 63.137362 delay 0.044243 status 0x24 strat 3 refid 0x80643887 rootdelay 0.009461
Mon Mar 31 11:43:16 2014 daemon.info sysinit: ntpd: sent query to 206.186.121.125
Mon Mar 31 11:43:16 2014 daemon.info sysinit: ntpd: sent query to 67.215.197.151
Mon Mar 31 11:43:17 2014 daemon.info sysinit: ntpd: reply from 206.186.121.125: reach 0x07 offset 63.132578 delay 0.032586 status 0x24 strat 2 refid 0x1896cb96 rootdelay 0.009018
Mon Mar 31 11:43:17 2014 daemon.info sysinit: ntpd: reply from 67.215.197.151: reach 0x07 offset 63.134666 delay 0.041811 status 0x24 strat 2 refid 0xd8ab7824 rootdelay 0.018143
Mon Mar 31 11:43:18 2014 daemon.info sysinit: ntpd: sent query to 206.186.121.125
Mon Mar 31 11:43:18 2014 daemon.info sysinit: ntpd: sent query to 206.108.0.131
Mon Mar 31 11:43:18 2014 daemon.info sysinit: ntpd: sent query to 67.215.197.151
Mon Mar 31 11:43:18 2014 daemon.info sysinit: ntpd: sent query to 198.50.209.202
Mon Mar 31 11:43:18 2014 daemon.info sysinit: ntpd: reply from 206.186.121.125: reach 0x0f offset 63.131501 delay 0.034086 status 0x24 strat 2 refid 0x1896cb96 rootdelay 0.009018
Mon Mar 31 11:43:18 2014 daemon.info sysinit: ntpd: reply from 206.108.0.131: reach 0x07 offset 63.131927 delay 0.034293 status 0x24 strat 1 refid 0x50505300 rootdelay 0.000000
Mon Mar 31 11:43:18 2014 daemon.info sysinit: ntpd: reply from 198.50.209.202: reach 0x07 offset 63.137826 delay 0.042555 status 0x24 strat 3 refid 0x80643887 rootdelay 0.009461
Mon Mar 31 11:43:18 2014 daemon.info sysinit: ntpd: reply from 67.215.197.151: reach 0x0f offset 63.134811 delay 0.044772 status 0x24 strat 2 refid 0xd8ab7824 rootdelay 0.018143
Mon Mar 31 11:43:19 2014 daemon.info sysinit: ntpd: sent query to 206.186.121.125
Mon Mar 31 11:43:19 2014 daemon.info sysinit: ntpd: sent query to 206.108.0.131
Mon Mar 31 11:43:19 2014 daemon.info sysinit: ntpd: sent query to 67.215.197.151
Mon Mar 31 11:43:19 2014 daemon.info sysinit: ntpd: sent query to 198.50.209.202
Mon Mar 31 11:43:19 2014 daemon.info sysinit: ntpd: reply from 206.186.121.125: reach 0x1f offset 63.132505 delay 0.035210 status 0x24 strat 2 refid 0x1896cb96 rootdelay 0.009018
Mon Mar 31 11:43:19 2014 daemon.info sysinit: ntpd: reply from 206.108.0.131: reach 0x0f offset 63.132456 delay 0.035414 status 0x24 strat 1 refid 0x50505300 rootdelay 0.000000
Mon Mar 31 11:43:19 2014 daemon.info sysinit: ntpd: reply from 198.50.209.202: reach 0x0f offset 63.136858 delay 0.041736 status 0x24 strat 3 refid 0x80643887 rootdelay 0.009461
Mon Mar 31 11:43:19 2014 daemon.info sysinit: ntpd: reply from 67.215.197.151: reach 0x1f offset 63.135846 delay 0.043975 status 0x24 strat 2 refid 0xd8ab7824 rootdelay 0.018143
Mon Mar 31 11:43:20 2014 daemon.info sysinit: ntpd: sent query to 206.108.0.131
Mon Mar 31 11:43:20 2014 daemon.info sysinit: ntpd: sent query to 198.50.209.202
Mon Mar 31 11:44:23 2014 daemon.info sysinit: ntpd: reply from 206.108.0.131: reach 0x1f offset 63.131849 delay 0.033145 status 0x24 strat 1 refid 0x50505300 rootdelay 0.000000
Mon Mar 31 11:44:23 2014 daemon.info sysinit: ntpd: setting clock to Mon Mar 31 11:44:23 EDT 2014 (offset 63.060448s)
Mon Mar 31 11:44:23 2014 daemon.info sysinit: --bitmain-options 115200:32:8:40:350:4d81 -o http://btc.e-pool.net:8800 -O 1MWhaSUrp3Cd8PQYGr3YNyperSRVmYDad7:1234 --api-listen --api-network
Mon Mar 31 11:44:23 2014 daemon.info sysinit: - init complete -
Mon Mar 31 11:45:04 2014 cron.info crond[569]: crond: USER root pid 1046 cmd /usr/bin/cgminer-monitor
Mon Mar 31 11:48:01 2014 cron.info crond[569]: crond: USER root pid 1324 cmd /usr/bin/cgminer-monitor
Mon Mar 31 11:51:01 2014 cron.info crond[569]: crond: USER root pid 1371 cmd /usr/bin/cgminer-monitor
Mon Mar 31 11:54:01 2014 cron.info crond[569]: crond: USER root pid 1421 cmd /usr/bin/cgminer-monitor
Mon Mar 31 11:57:01 2014 cron.info crond[569]: crond: USER root pid 1583 cmd /usr/bin/cgminer-monitor
code] here is a similar (same?) issue with an avalon a few months back. Your issue is definitely with the network or network settings, and not the actual function of the miner (other than settings) https://bitcointalk.org/index.php?topic=416940.40post your network settings and if DHCP is disabled. It seems certainly a network settings issue and not with the pool settings |
|
|
|
...
Of course it is, this is our development board from hashfast. We are in the process of tooling our production line to build 5,000 boards in April.
So wait, you post a pic of a dev board as proof of the product you claim to be shipping *now*? Unless you're shipping dev boards, I'd say that's fucking sleazy. How about a pic of the stuff you claim to be shipping? The pictures show our stock of boards and the product ready to be shipped. how much will it cost to produce 5000 boards? I imagine costs will be in the range of $800-1000 per board since the hashfast chips will likely cost $500-700 each. That means at least $3.5M in upfront costs, likely $4M+ |
|
|
|
any photos of s2?  ? Still no pics  unboxing it will be like, being a kid on christmas morning, it'll be a surprise.  +1  They might get pics up once the packaging is all sorted out - thats number 1 priority compared to putting some photos online. otherwise, thursday should have some people receiving and posting images. |
|
|
|
Keep an eye out for a casascius bearer bar. Some of those were created with zero balance ready to be funded.
I have one of them (and another coming this week) stunning bars though still no reason to use them over a paper wallet. I told the exact thing to someone trying to sell a bearer bar with 2.001BTC on it. The bar itself can fetch around 1BTC but an opened bar will only fetch ~0.4BTC. By putting 2BTC on the bar, its likely that noone would pay more than ~2.6BTC for it since it means either sealing away 2BTC for as long as the bar is protected as a collectible, or opening the bar to retrieve the BTC but being stuck with an opened bar. |
|
|
|
it does NOT ship with cooling solution (it suggests the H80i), but has absolutely no warranty because the units are 'tested' - how can you not offer a basic warranty for a product that has an exposed chip and ask that the customer apply the heatsink/WC themselves? its begging for the chip to be scratched or the heatsink mounted poorly
In the EU, a 2 year warranty is standard regardless of what the manufacturer or reseller says. This is true, but if the product requires user 'installation' and they fudge it, the warranty would not apply. Warranty covers defects that lay within scope of the product design. If the product requires cooling to operate (similar to a electric kettle needing water inside so it doesn't burn out) and the user opts to not cool or install the product correctly then they lay outside the scope of the warranty. I would urge Ken to make the demands of the product explicitly clear on the packaging AND the product description on the website. Leaving this information off of the specifications will allow the consumer to litigate based on false advertising. your example is a bit incorrect - its more like selling a kettle that cannot handle tap water and MUST be primed and operated with reverse-osmosis water to prevent failure due to calcium scaling that could easily be caused by a careless user. (not to mention most kettles have a form of temperature or fuse fail-safe) law tends to side with the victim, and generally views the case in a way similar to an untrained individual or child-like naivety to determine whether fault lies with the buyer or with the seller. If this product fails catastrophically (fire) or is simply damaged (capacitor leaks or chip melts) because the 'average person' thought it was plug-and-play at a cursory glance, then most courts would enforce a warranty. Reasonable efforts to prevent this are necessary in this sort of law, which means that at a minimum there should be a big warning sticker on the chip or sealing the antistatic bag shut that says 'do not use without cooling --- website.com/how-to-cool' |
|
|
|
Maybe I posted this question in the wrong forum or maybe the way I want to monitor can't be done!
Any suggestions anyone?
I imagine you ask because you want to do something like pencil mod one board, or one section of chips, to see the difference? AFAIK there is no way to do this. Your best method would be to record the 20min average at current setings, then change and re-record 20min average. If you have a few machines you can try different changes on each to see the differences. but no, i dont think there is any way to monitor more accurately than the entire S1 hashrate |
|
|
|
Price is now $1999 for our Prospector it seems
thats good. $2999 was insulting. $2000 might be low enough to get some sales, though with current BTC prices thats about 4.5BTC (you could have 5 antminers for that price) Would those 5 Ant's come with power supply? Also need to factor in power & costs no. neither does the VMC product. which brings me back to my other concern it does NOT ship with cooling solution (it suggests the H80i), but has absolutely no warranty because the units are 'tested' - how can you not offer a basic warranty for a product that has an exposed chip and ask that the customer apply the heatsink/WC themselves? its begging for the chip to be scratched or the heatsink mounted poorly this board is less plug-and-play than an antminer, and as mentioned there are 1TH/1000W devices from china for ~7BTC |
|
|
|
how about read at least 1 page or more on the forums? when did they remove the 50-post limit for leaving the newbie subforum?the short answer is yes, and no. the long answer is easy to find if you bother |
|
|
|
wow you really are a sucker huh? If i read this correctly, you actually admit that after both his messages about a coin pump the coin briefly rose in value. when it rose, he sold but you did not. he did not steal your money. hell, he barely even played you. You paid good money hoping you could make more than that from shitty altcoin pump-dump schemes.
Yup... as they say Look Around the Poker Table; If You Can’t See the Sucker, You’re It
NWO, I'm sorry he stole you, but look at the bright side, you've learned a (fairly expensive) lesson but it could have been much worse. I think I remember the post in which this guy solicited members for his group and I think he didn't talk about a 1BTC entrance fee. Never trust, never pay for secrets/information, almost always it is scam.
welcome to the real world. Don't buy designer leather jackets from the guy in the parking lot |
|
|
|
Make offers and post pictures please. Not looking for very expensive coin, at most a coin with 1 BTC loaded in it...mainly looking for a way that I can send BTC to the coin for long term investment and not be able to open the coin's wallet in a panic sell situation due to the grading...  Also, as I am waiting on some important PMs from BTC bulk sellers, please do not PM me regarding this coin ad. Just post a comment for time being please. Oh and if you're interested in selling $500+ of BTC at bitstamp prices FOR CASH at anytime, please let me know. Buying thousands weekly! thats a silly idea. lets say you took a nice brass 1BTC token - its worth about 1.5BTC in good condition you now load 5BTC onto it - it holds 6BTC total You now have two options wen you need the funds: 1) sell the coin to someone who actually cares that there is more than 1BTC on it. They will be buying it for the intact hologram and visual appeal. They will offer you a smaller premium because you modified the coin's balance - perhaps 6.25BTC 2) you remove the hologram to access the funds leaving you with a useless brass token - you will only get 0.1-0.2BTC selling it. either way, adding value to the coin actually makes it less valuable. create a paper wallet instead. |
|
|
|
Another one I like as well... http://btcinvest.net/en/bitcoin-mining-profit-calculator.phpWith the price drop (therefore increasing amount of BTC to purchase ANY miner) it is impossible almost impossible to find any calculator that shows buying ANY mining gear (not singling out ST here) will be profitable (i.e., you will earn more BTC than you paid). That is really a shame as I SO wanted to get some of their miners but cannot rationalize the expense  Why not just buy btc? lol? I have purchased some. Not nearly as interesting as mining, though. the antminer S1 is perhaps the only system that is well-priced at the moment in BTC. everything else is based in $ which makes them unattractive at btc prices under $500. |
|
|
|
Price is now $1999 for our Prospector it seems
thats good. $2999 was insulting. $2000 might be low enough to get some sales, though with current BTC prices thats about 4.5BTC (you could have 5 antminers for that price) |
|
|
|
Hi, At the expence of sounding like a newbee, i am a bit at a loss. After browsing trough the comments, i am still trying to figure out where to get the 3.3V line from on the DPS-2000BB. AFAIK, pci-e slot draws 12v and 3.3v. I am using the USB RISERS - https://www.hashratestore.com/shop/cables/usb-pcie-riser-powered-molex-60-cm . Apart from the standard pci-e 6 AND 6/8 PIN SETUP (12V), it also uses 4 pin molex which carries 12v G G 5v. However, according to this: Except for a potential maximum 10W from the PCIe +3.3V slot, all remaining power consumption will be on a +12V output.there should be 3.3v comming from the molex and there isnt. I can only conclude that instead of 3.3v it uses the 5v from the molex in the same way. The PCIe X16 slot supplies 75W of which 10W comes from the +3.3V output (3.0A)The following questions comes to my mind: 1 - How many WATT/AMP can i pull from the DPS-2000BB 5V line ?? 2 - If not, can i use a molex from PSU powering the RIGS ? I do apologize in advance if this has been covered before. Cheers, Mac It uses a voltage regulator to make 3.3v. ok, do you mean the usb-pcie-riser uses a voltage regulator ? That would mean i would use the molex as follows: 12v G G 12V instead of 12V G G 5V and the riser does the rest. Or do i need to adapt one to get the 3.3v from the 12v line ? Cheers, Mac Yes, the usb riser has a regulator on the 16x board that plugs into the bottom of the power supply. I do not know right off of my head if it converts the 5v to 3.3 or the 12v to 3.3 but logic would tell me it uses the 5v, otherwise it would probably get really hot. You would need to look at the regulator and make sure that it can accept 12v input and then see how hot it gets if you feed it with 12v. The regulator is going to dissipate almost 3x the watts that the card uses at 3.3v if you feed it with 12v, so it may only work for a little while, then burn out the regulator. looking at my usb riser right now - yes the 5V is used, and is connected to the flat 3-pin chip, presumably to drop down to 3.3V as mentioned. putting 12V through that is a TERRIBLE idea. |
|
|
|
|
Show Posts
