New price for AntMiner S1: 0.818 0.63 btc each one, shipping cost included.
whoever has bought S1 recently will get coupons, which are expected to reach user accounts on Apr 25th and Apr 26th. Happy Mining  Has anyone received a coupon from BITMAIN for recent S1 buys? Got my latest S1 just a few days ago, but no coupons yet  The price drops + coupons might sway me for another S1 or 2 (with thoughts of under-clocking + under-volting to compensate for its thirst for KWhs) Cheers Got my coupon Cheers When did u bought miners? Bitmain seems teasing people with this and nothing. I did 4.4.14 5 miners and nothing. Is that recent purchase or not?.... My most recent S1 was bought about a week ago. I bought also at about middle and end of March, but it doesn't look like these were counted for the coupon. Perhaps yours is still 'in the pipeline'. Cheers |
|
|
|
New price for AntMiner S1: 0.818 0.63 btc each one, shipping cost included.
whoever has bought S1 recently will get coupons, which are expected to reach user accounts on Apr 25th and Apr 26th. Happy Mining Has anyone received a coupon from BITMAIN for recent S1 buys? Got my latest S1 just a few days ago, but no coupons yet The price drops + coupons might sway me for another S1 or 2 (with thoughts of under-clocking + under-volting to compensate for its thirst for KWhs) Cheers Got my coupon Cheers |
|
|
|
New price for AntMiner S1: 0.818 0.63 btc each one, shipping cost included.
whoever has bought S1 recently will get coupons, which are expected to reach user accounts on Apr 25th and Apr 26th. Happy Mining Has anyone received a coupon from BITMAIN for recent S1 buys? Got my latest S1 just a few days ago, but no coupons yet The price drops + coupons might sway me for another S1 or 2 (with thoughts of under-clocking + under-volting to compensate for its thirst for KWhs) Cheers |
|
|
|
How fast does bitmain ship their miners? I ordered a couple of days ago and payed instantly, but the site still says unshipped. Or do they just not update the shipment status on their webpage?
Bitmain are fast, however you need to factor weekends and holidays (that also affect shipping/courier companies). I ordered on 18 Apr, it was shipped on 19 Apr, however it hit the weekend and Easter, so was delivered on 23 Apr (today). All configured and working by now (had the PS and other stuff waiting). Cheers |
|
|
|
It can take some time for the mining software (I think that you are using BFGMiner as per your previous thread) to establish communications with the pool server. Being on WiFi might be another contributor. You could try a separate utility to make sure that you get a reasonable connection to the pool (I tried WinMtr http://winmtr.net/, note that you enter just the url, without the port). It's a good idea to have more than a single pool configured, with fallback to a backup pool if the primary pool has issues (pools have issues, faults, DDOS attacks and natural disasters), so having 'backup' would mean that your mining resources are put to some. Check with your pool(s) what is the current recommended server address. Some pools modify their settings so the address that you used 6 months ago may no longer be current (recently discovered that Eclipse mining did that, so some of my fallback settings found the pool 'dead'). What is the specific message that you are getting? (a screen image, or text copy can help) Cheers |
|
|
|
BITMAIN needs to ship them with all boards removed from slots and individually bubble wrapped and carefully packed and stacked inside the case. then play football with the packing prototype and then unwrap, assemble and test for full functionality.
or else more bad press resumes. pity. S1's were bullet proof for sadist shippers and moron handlers
You seem to refer to the S2, while this is the S1 thread (as you suggest, it is 'bullet proof' with no plug-in boards, however it does not have the hash rate, efficiency and enclosure of the S2). Looks like Bitmain went back to the drawing board to improve the S2, that's probably why there are plenty of price cuts on the S1. Just got another S1, all working without any dramas. Cheers |
|
|
|
Hey
I have an issue with an Antminer S1!
i bought 3 of them together, and had been running them successfully for 2 weeks. Upon a routine restart, one of them stopped mining.
Using 2 supplies for the blades, both Cooler Master CM 350 Plus. The other two are working perfectly.
Have tried changing and verifying all the settings including the NTP servers, using google DNS servers, different mining pools, different power supplies, using only one blade, reconnecting the wiring from the blades, have also performed a hard reset, changed my time zone to the appropriate one but nothing is working. It powers up, control board shows both the green lights and the red light, however no lights come on the blades. I can login via the web GUI and also using SSH. I have also pinged via the device and network connection is good. Also the device status page shows nothing in the ASIC area!
I have tried every freaking thing possible, but this wont work! I am attaching the logs, any help would be appreciated!
P.S. I think its not recognizing the blades as kernel log shows USB device read error!
From your status line, looks like your blades are not detected (or you did not wait long enough, as this screen capture is after 1m)
Could be interconnecting cables to the blades, power supplie(s), corrupt firmware?
Waited for more than a hour, still no further lines appear in Kernel Log. Checked interconnecting cables as well as power supply! Have not done anything to the firmware. I thought a hard reset would rectify any firmware related issues! I also think the blades are not being detected! Any further ideas? A hard reset will only fix configuration issues, but if the application is corrupt, that would not help. If you have a few S1's you could do some swapping between them, to try and isolate the problem. Another area that you may want to explore is your power supply. It's unclear from your post how you power this Ant - do you use a single Cooler Master CM 350 Plus? (that maybe marginal), or two of these (one per blade)? Some web sites claim that it is a 2 rail power supply, however others http://www.hardwaresecrets.com/article/Cooler-Master-Elite-Power-350-W-Power-Supply-Review/1184/6 claim that it is really a single rail (both rails "hard joined"). Assuming that you are using 2 Cooler Master CM 350 Plus PSUs, one per blade, this should be enough (23A x 12V=276W per blade > 360/2=180W for nominal hash rate). Are you using some mechanism to turn both PSUs on simultaneously? Try swapping power supplies between good Ants and the sick one. You could also try running it with a single blade. If your firmware is stuffed (probably due to 'brownout condition' with a marginal power supply, then you might need to re-flash it (hopefully the basic part of your controller is still alive and capable of being re-flashed). You can download the latest firmware from Bitmain's web site (I would try to swap controller boards first to support the 'bad firmware' idea). Good luck I am using two separate power supplies, one per blade! I also tried switching to other working supplies, but nothing worked! I have also flashed to latest firmware but even that did not help! Also, what do you mean by swap controller boards? I mean how can i do that? And thanks in advance for your help! Maybe you can try running it with a single blade first? (disconnect all cables to the 2nd blade, the one without the small controller board, including power) Do you have a higher capacity power supply than this CoolerMaster? Maybe the 'sick' Ant has a slightly higher initial current requirement that causes your power supply to go into some self-protection mode. I did not try swapping the controller board between ants myself, but it should simply mean disconnecting cables and mounting hardware and moving the controller from a working Ant to the 'sick' one. You could do this to confirm that the controller board is the cause of the problem (if moving 'known good' controller to 'sick' Ant revives it, and moving the 'suspect' controller into a 'known good' Ant makes it fail, it will be highly likely that this is the cause, at the expense of some fiddling and loss of hashing time). As your controller is at least partially alive (you can connect to its web gui and re-flash it), I'm not convinced that this is the primary cause however. Good luck Any updates on your issue? |
|
|
|
|
I think that the fins on the small adhesive heatsinks should be oriented vertically rather than horizontally, to improve convective air-flow (doesn't matter if you use a fan to blow on the sides of the S1).
Another option is to buy the 'bare' heatsinks (8.8x8.8x5mm), and purchase the double sided thermal interface separately. I bought the heatsinks on eBay (AU $1.20 for a pack of 20) and the double sided thermal interface from a local electronics shop (a pack of 2 sheets for AU$12.95 from Jaycar). This costs a bit lower than the US$16 per antminer S1 kit, but probably requires a bit more work in cutting and attaching the adhesive to the heatsinks. It is probably safer to shutdown and disconnect the Antminer S1 when you do this rather than risk a pre-mature death for the sake of a few milli-BTC...
There was a temp drop of about 2-3 deg C after installation of these just on the ASICS.
Cheers
|
|
|
|
So I've had my AntMiner U2 running at 2 gh/s for around 3 weeks now (since I got it) without any overclocks, which I was very impressed with. I do not have it runing 24/7, but it's more of a hobby than a full-time thing so I just have it running whenever I'm on the computer, which is still 4-6 hours a day. But now, it's going super slow. BFGMiner says it's running a bit under 400mh/s, and in the past 10 hours I've only gotten 3080 accepted shares. The only reason I've left it on all night was because I knew heat wouldn't be a problem, as it's not even heating up to what it used to be getting to. I have tried both using every USB 3.0 ports on my computer and my powered USB hub (plugged into my wall) but still get the same ~400mh/s. I'm super confused, because it's been working forever now and is just now doing this. Plus, BFGMiner no longer recognizes my device as "antminer" anymore. I have to manually go into BFGMiner using M and + and add the device using "erupter:all" or "erupter:\.\COM6". I've tried unplugging it and replugging it in and restarting my machine serveral times. Here's my normal Start.bat file: bfgminer.exe -o http://api.bitcoin.cz:8332 -u XXX -p XXX -S antminer:all --set-device antminer:clock=x0781 and this is the one I must use if I don't want to manually add the "erupter" in: bfgminer.exe -o http://api.bitcoin.cz:8332 -u NoahWL1.worker1 -p 5UD3rghG -S erupter:all --set-device erupter:clock=x0781. An help will be appreciated, thanks! EDIT: Somewhere else someone suggested using this: bfgminer.exe -o http://api.bitcoin.cz:8332 -u XXX -p XXX -S all --icarus-options 115200:1:1 --icarus-timing 3.0=100 and I got the same results. I then changed it to bfgminer.exe -o http://api.bitcoin.cz:8332 -u XXX -p XXX -S all --icarus-options 115200:2:2 --icarus-timing 3.0=100 and on average got a bit over 700 mh/s, which is better but still nowhere near the 2gh/s I used to be getting. I don't think that you need the api part in the address, nor do you need icarus related parameters. Assuming that you are trying to mine on Slush's pool ( http://mining.bitcoin.cz/) then you need something like: bfgminer.exe -o stratum+tcp://stratum.bitcoin.cz:3333 -u User -p Password -S antminer:all --set-device antminer:clock=x0981 The last part is for overclocking the AntMiner U2 to a safe rate of about 2.06 GH/s. You may want to cool it with a fan. This assumes also that you installed the Silabs driver for the AntMiner ( http://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx). Cheers |
|
|
|
Hey
I have an issue with an Antminer S1!
i bought 3 of them together, and had been running them successfully for 2 weeks. Upon a routine restart, one of them stopped mining.
Using 2 supplies for the blades, both Cooler Master CM 350 Plus. The other two are working perfectly.
Have tried changing and verifying all the settings including the NTP servers, using google DNS servers, different mining pools, different power supplies, using only one blade, reconnecting the wiring from the blades, have also performed a hard reset, changed my time zone to the appropriate one but nothing is working. It powers up, control board shows both the green lights and the red light, however no lights come on the blades. I can login via the web GUI and also using SSH. I have also pinged via the device and network connection is good. Also the device status page shows nothing in the ASIC area!
I have tried every freaking thing possible, but this wont work! I am attaching the logs, any help would be appreciated!
P.S. I think its not recognizing the blades as kernel log shows USB device read error!
I checked Kernel Logs on 2 Ants, and am getting some extra stuff after your last line [ 20.310000] eth1: link up (100Mbps/Full duplex)
[ 21.500000] usb 1-1.1: USB disconnect, device number 3
[ 21.500000] bitmain 1-1.1:1.0: USB Bitmain asic #0 now disconnected
[ 21.790000] usb 1-1.1: new full-speed USB device number 4 using ehci-platform
[ 21.940000] bitmainbl 1-1.1:1.0: USB Bitmain bootloader device now attached to USB Bitmain bootloader-0
[ 21.950000] PIC microchip bootloader usb OK
[ 31.380000] no int in filled
[ 32.750000] usb 1-1.1: USB disconnect, device number 4
[ 32.760000] bitmainbl 1-1.1:1.0: USB Bitmain asic #0 now disconnected
[ 33.010000] usb 1-1.1: new full-speed USB device number 5 using ehci-platform
[ 33.150000] bitmain 1-1.1:1.0: USB Bitmain asic device now attached to USB Bitmain asic-0
[ 33.160000] PIC microchip usb OK
[ 62.630000] bitmain 1-1.1:1.0: USB Bitmain asic #0 now disconnected
Are you getting anything else at the end of the Kernel Log? From your status line, looks like your blades are not detected (or you did not wait long enough, as this screen capture is after 1m) Could be interconnecting cables to the blades, power supplie(s), corrupt firmware? Good luck Waited for more than a hour, still no further lines appear in Kernel Log. Checked interconnecting cables as well as power supply! Have not done anything to the firmware. I thought a hard reset would rectify any firmware related issues! I also think the blades are not being detected! Any further ideas? A hard reset will only fix configuration issues, but if the application is corrupt, that would not help. If you have a few S1's you could do some swapping between them, to try and isolate the problem. Another area that you may want to explore is your power supply. It's unclear from your post how you power this Ant - do you use a single Cooler Master CM 350 Plus? (that maybe marginal), or two of these (one per blade)? Some web sites claim that it is a 2 rail power supply, however others http://www.hardwaresecrets.com/article/Cooler-Master-Elite-Power-350-W-Power-Supply-Review/1184/6 claim that it is really a single rail (both rails "hard joined"). Assuming that you are using 2 Cooler Master CM 350 Plus PSUs, one per blade, this should be enough (23A x 12V=276W per blade > 360/2=180W for nominal hash rate). Are you using some mechanism to turn both PSUs on simultaneously? Try swapping power supplies between good Ants and the sick one. You could also try running it with a single blade. If your firmware is stuffed (probably due to 'brownout condition' with a marginal power supply, then you might need to re-flash it (hopefully the basic part of your controller is still alive and capable of being re-flashed). You can download the latest firmware from Bitmain's web site (I would try to swap controller boards first to support the 'bad firmware' idea). Good luck |
|
|
|
Hey I have an issue with an Antminer S1! i bought 3 of them together, and had been running them successfully for 2 weeks. Upon a routine restart, one of them stopped mining. Using 2 supplies for the blades, both Cooler Master CM 350 Plus. The other two are working perfectly. Have tried changing and verifying all the settings including the NTP servers, using google DNS servers, different mining pools, different power supplies, using only one blade, reconnecting the wiring from the blades, have also performed a hard reset, changed my time zone to the appropriate one but nothing is working. It powers up, control board shows both the green lights and the red light, however no lights come on the blades. I can login via the web GUI and also using SSH. I have also pinged via the device and network connection is good. Also the device status page shows nothing in the ASIC area! I have tried every freaking thing possible, but this wont work! I am attaching the logs, any help would be appreciated! P.S. I think its not recognizing the blades as kernel log shows USB device read error! Thu Jan 1 05:30:11 1970 kern.err kernel: [ 8.580000] hub 1-1:1.0: unable to enumerate USB device on port 1
Thu Jan 1 05:30:11 1970 kern.notice kernel: [ 10.580000] jffs2: notice: (324) jffs2_build_xattr_subsystem: complete building xattr subsystem, 35 of xdatum (0 unchecked, 34 orphan) and 113 of xref (0 dead, 99 orphan) found.
Sat Apr 19 18:14:00 2014 daemon.info sysinit: Sat Apr 19 12:44:00 UTC 2014
Sat Apr 19 18:14:00 2014 user.emerg syslog: kmodloader: loading kernel modules from /etc/modules.d/**
Sat Apr 19 18:14:00 2014 kern.info kernel: [ 12.830000] hidraw: raw HID events driver (C) Jiri Kosina
Sat Apr 19 18:14:00 2014 kern.info kernel: [ 12.840000] Loading modules backported from Linux version master-2013-06-27-0-gdcfa6d5
Sat Apr 19 18:14:00 2014 kern.info kernel: [ 12.840000] Backport generated by backports.git backports-20130617-4-ge3220f5
Sat Apr 19 18:14:00 2014 kern.info kernel: [ 12.860000] nf_conntrack version 0.5.0 (962 buckets, 3848 max)
Sat Apr 19 18:14:00 2014 kern.info kernel: [ 12.880000] usbcore: registered new interface driver usbhid
Sat Apr 19 18:14:00 2014 kern.info kernel: [ 12.890000] usbhid: USB HID core driver
Sat Apr 19 18:14:00 2014 kern.info kernel: [ 12.900000] usbcore: registered new interface driver usbserial
Sat Apr 19 18:14:00 2014 kern.info kernel: [ 12.900000] usbcore: registered new interface driver usbserial_generic
Sat Apr 19 18:14:00 2014 kern.info kernel: [ 12.910000] usbserial: USB Serial support registered for generic
Sat Apr 19 18:14:00 2014 kern.info kernel: [ 12.940000] xt_time: kernel timezone is -0000
Sat Apr 19 18:14:00 2014 kern.info kernel: [ 12.960000] cfg80211: Calling CRDA to update world regulatory domain
Sat Apr 19 18:14:00 2014 kern.info kernel: [ 12.970000] cfg80211: World regulatory domain updated:
Sat Apr 19 18:14:00 2014 kern.info kernel: [ 12.970000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Sat Apr 19 18:14:00 2014 kern.info kernel: [ 12.980000] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Sat Apr 19 18:14:00 2014 kern.info kernel: [ 12.990000] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Sat Apr 19 18:14:00 2014 kern.info kernel: [ 13.000000] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Sat Apr 19 18:14:00 2014 kern.info kernel: [ 13.000000] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Sat Apr 19 18:14:00 2014 kern.info kernel: [ 13.010000] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Sat Apr 19 18:14:00 2014 kern.info kernel: [ 13.030000] ip_tables: (C) 2000-2006 Netfilter Core Team
Sat Apr 19 18:14:00 2014 kern.debug kernel: [ 13.150000] ath: EEPROM regdomain: 0x0
Sat Apr 19 18:14:00 2014 kern.debug kernel: [ 13.150000] ath: EEPROM indicates default country code should be used
Sat Apr 19 18:14:00 2014 kern.debug kernel: [ 13.150000] ath: doing EEPROM country->regdmn map search
Sat Apr 19 18:14:00 2014 kern.debug kernel: [ 13.150000] ath: country maps to regdmn code: 0x3a
Sat Apr 19 18:14:00 2014 kern.debug kernel: [ 13.150000] ath: Country alpha2 being used: US
Sat Apr 19 18:14:00 2014 kern.debug kernel: [ 13.150000] ath: Regpair used: 0x3a
Sat Apr 19 18:14:00 2014 kern.debug kernel: [ 13.170000] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
Sat Apr 19 18:14:00 2014 kern.info kernel: [ 13.170000] cfg80211: Calling CRDA for country: US
Sat Apr 19 18:14:00 2014 user.info syslog: ran 16 iterations
Sat Apr 19 18:14:00 2014 daemon.info sysinit: kmod: ran 16 iterations
Sat Apr 19 18:14:00 2014 kern.info kernel: [ 13.180000] ieee80211 phy0: Atheros AR9330 Rev:1 mem=0xb8100000, irq=2
Sat Apr 19 18:14:00 2014 kern.info kernel: [ 13.190000] cfg80211: Regulatory domain changed to country: US
Sat Apr 19 18:14:00 2014 kern.info kernel: [ 13.190000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Sat Apr 19 18:14:00 2014 kern.info kernel: [ 13.200000] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)
Sat Apr 19 18:14:00 2014 kern.info kernel: [ 13.210000] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm)
Sat Apr 19 18:14:00 2014 kern.info kernel: [ 13.210000] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Sat Apr 19 18:14:00 2014 kern.info kernel: [ 13.220000] cfg80211: (5490000 KHz - 5600000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Sat Apr 19 18:14:00 2014 kern.info kernel: [ 13.230000] cfg80211: (5650000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Sat Apr 19 18:14:00 2014 kern.info kernel: [ 13.240000] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)
Sat Apr 19 18:14:04 2014 cron.info crond[569]: crond: crond (busybox 1.19.4) started, log level 8
Sat Apr 19 18:14:05 2014 authpriv.info dropbear[580]: Not backgrounding
Sat Apr 19 18:14:05 2014 daemon.notice netifd: Interface 'loopback' is now up
Sat Apr 19 18:14:05 2014 kern.info kernel: [ 18.000000] device eth0 entered promiscuous mode
Sat Apr 19 18:14:05 2014 daemon.notice netifd: Interface 'wan' is now up
Sat Apr 19 18:14:06 2014 daemon.notice netifd: lan (630): udhcpc (v1.19.4) started
Sat Apr 19 18:14:06 2014 daemon.notice netifd: lan (630): Sending discover...
Sat Apr 19 18:14:06 2014 user.notice firewall: Reloading firewall due to ifup of wan (eth1)
Sat Apr 19 18:14:07 2014 kern.info kernel: [ 20.200000] eth1: link up (100Mbps/Full duplex)
Sat Apr 19 18:14:07 2014 user.notice dnsmasq: DNS rebinding protection is active, will discard upstream RFC1918 responses!
Sat Apr 19 18:14:07 2014 user.notice dnsmasq: Allowing 127.0.0.0/8 responses
Sat Apr 19 18:14:08 2014 daemon.info sysinit: /etc/config/miner_pic.hex
Sat Apr 19 18:14:08 2014 daemon.info sysinit: Unable to open /dev/bitmainbl0: No such file or directory
Sat Apr 19 18:14:08 2014 daemon.info sysinit: pic update
Sat Apr 19 18:14:08 2014 daemon.info dnsmasq[687]: started, version 2.66 cachesize 150
Sat Apr 19 18:14:08 2014 daemon.info dnsmasq[687]: compile time options: IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack no-ipset no-auth
Sat Apr 19 18:14:08 2014 daemon.info dnsmasq[687]: using local addresses only for domain lan
Sat Apr 19 18:14:08 2014 daemon.info dnsmasq[687]: reading /tmp/resolv.conf.auto
Sat Apr 19 18:14:08 2014 daemon.info dnsmasq[687]: using nameserver 8.8.4.4#53
Sat Apr 19 18:14:08 2014 daemon.info dnsmasq[687]: using nameserver 8.8.8.8#53
Sat Apr 19 18:14:08 2014 daemon.info dnsmasq[687]: using local addresses only for domain lan
Sat Apr 19 18:14:08 2014 daemon.info dnsmasq[687]: read /etc/hosts - 1 addresses
Sat Apr 19 18:14:08 2014 daemon.info sysinit: setting up led WAN
Sat Apr 19 18:14:08 2014 daemon.info sysinit: setting up led WANL
Sat Apr 19 18:14:08 2014 daemon.info sysinit: setting up led LAN1
Sat Apr 19 18:14:08 2014 daemon.info sysinit: setting up led LAN2
Sat Apr 19 18:14:08 2014 daemon.info sysinit: setting up led LAN3
Sat Apr 19 18:14:08 2014 daemon.info sysinit: setting up led LAN4
Sat Apr 19 18:14:08 2014 daemon.info sysinit: setting up led WLAN
Sat Apr 19 18:14:09 2014 daemon.notice netifd: lan (630): Sending discover...
Sat Apr 19 18:14:12 2014 daemon.notice netifd: lan (630): Sending discover...
Sat Apr 19 18:14:13 2014 daemon.info sysinit: ntpd: resolved peer 3.openwrt.pool.ntp.org to 113.30.137.34
Sat Apr 19 18:14:13 2014 daemon.info sysinit: ntpd: sent query to 113.30.137.34
Sat Apr 19 18:14:13 2014 daemon.info sysinit: ntpd: resolved peer 2.openwrt.pool.ntp.org to 120.88.47.10
Sat Apr 19 18:14:13 2014 daemon.info sysinit: ntpd: sent query to 120.88.47.10
Sat Apr 19 18:14:13 2014 daemon.info sysinit: ntpd: resolved peer 1.openwrt.pool.ntp.org to 202.71.136.67
Sat Apr 19 18:14:13 2014 daemon.info sysinit: ntpd: sent query to 202.71.136.67
Sat Apr 19 18:14:13 2014 daemon.info sysinit: ntpd: resolved peer 0.openwrt.pool.ntp.org to 202.71.136.67
Sat Apr 19 18:14:13 2014 daemon.info sysinit: ntpd: sent query to 202.71.136.67
Sat Apr 19 18:14:13 2014 daemon.info sysinit: ntpd: reply from 113.30.137.34: reach 0x01 offset 36.857360 delay 0.048175 status 0x24 strat 3 refid 0x78582e0a rootdelay 0.180255
Sat Apr 19 18:14:13 2014 daemon.info sysinit: ntpd: reply from 202.71.136.67: reach 0x01 offset 36.858557 delay 0.047955 status 0x24 strat 2 refid 0xcbb9453c rootdelay 0.212467
Sat Apr 19 18:14:13 2014 daemon.info sysinit: ntpd: reply from 202.71.136.67: reach 0x01 offset 36.855676 delay 0.053626 status 0x24 strat 2 refid 0xcbb9453c rootdelay 0.212467
Sat Apr 19 18:14:13 2014 daemon.info sysinit: ntpd: reply from 120.88.47.10: reach 0x01 offset 36.851049 delay 0.074254 status 0x24 strat 2 refid 0xd8dafeca rootdelay 0.251148
Sat Apr 19 18:14:14 2014 daemon.info sysinit: ntpd: sent query to 120.88.47.10
Sat Apr 19 18:14:14 2014 daemon.info sysinit: ntpd: reply from 120.88.47.10: reach 0x03 offset 36.851943 delay 0.074140 status 0x24 strat 2 refid 0xd8dafeca rootdelay 0.251148
Sat Apr 19 18:14:15 2014 daemon.info sysinit: ntpd: sent query to 113.30.137.34
Sat Apr 19 18:14:15 2014 daemon.info sysinit: ntpd: sent query to 202.71.136.67
Sat Apr 19 18:14:15 2014 daemon.info sysinit: ntpd: sent query to 202.71.136.67
Sat Apr 19 18:14:15 2014 daemon.info sysinit: ntpd: reply from 202.71.136.67: reach 0x03 offset 36.859349 delay 0.058185 status 0x24 strat 2 refid 0xcbb9453c rootdelay 0.212467
Sat Apr 19 18:14:15 2014 daemon.info sysinit: ntpd: reply from 113.30.137.34: reach 0x03 offset 36.852194 delay 0.059390 status 0x24 strat 3 refid 0x78582e0a rootdelay 0.180255
Sat Apr 19 18:14:15 2014 daemon.info sysinit: ntpd: reply from 202.71.136.67: reach 0x03 offset 36.862054 delay 0.059097 status 0x24 strat 2 refid 0xcbb9453c rootdelay 0.212467
Sat Apr 19 18:14:16 2014 daemon.info sysinit: ntpd: sent query to 113.30.137.34
Sat Apr 19 18:14:16 2014 daemon.info sysinit: ntpd: sent query to 120.88.47.10
Sat Apr 19 18:14:16 2014 daemon.info sysinit: ntpd: sent query to 202.71.136.67
Sat Apr 19 18:14:16 2014 daemon.info sysinit: ntpd: reply from 113.30.137.34: reach 0x07 offset 36.858112 delay 0.049128 status 0x24 strat 3 refid 0x78582e0a rootdelay 0.180255
Sat Apr 19 18:14:16 2014 daemon.info sysinit: ntpd: reply from 202.71.136.67: reach 0x07 offset 36.865055 delay 0.053632 status 0x24 strat 2 refid 0xcbb9453c rootdelay 0.212467
Sat Apr 19 18:14:16 2014 daemon.info sysinit: ntpd: reply from 120.88.47.10: reach 0x07 offset 36.855325 delay 0.073973 status 0x24 strat 2 refid 0xd8dafeca rootdelay 0.251148
Sat Apr 19 18:14:54 2014 daemon.info sysinit: ntpd: sent query to 113.30.137.34
Sat Apr 19 18:14:54 2014 daemon.info sysinit: ntpd: sent query to 120.88.47.10
Sat Apr 19 18:14:54 2014 daemon.info sysinit: ntpd: sent query to 202.71.136.67
Sat Apr 19 18:14:54 2014 daemon.info sysinit: ntpd: sent query to 202.71.136.67
Sat Apr 19 18:14:54 2014 daemon.info sysinit: ntpd: reply from 113.30.137.34: reach 0x0f offset 0.019282 delay 0.051603 status 0x24 strat 3 refid 0x78582e0a rootdelay 0.180255
Sat Apr 19 18:14:54 2014 daemon.info sysinit: ntpd: reply from 202.71.136.67: reach 0x07 offset 0.025133 delay 0.053730 status 0x24 strat 2 refid 0xcbb9453c rootdelay 0.212467
Sat Apr 19 18:14:54 2014 daemon.info sysinit: ntpd: reply from 202.71.136.67: reach 0x0f offset 0.025799 delay 0.057612 status 0x24 strat 2 refid 0xcbb9453c rootdelay 0.212467
Sat Apr 19 18:14:54 2014 daemon.info sysinit: ntpd: reply from 120.88.47.10: reach 0x0f offset 0.017386 delay 0.075951 status 0x24 strat 2 refid 0xd8dafeca rootdelay 0.251148
Sat Apr 19 18:14:56 2014 daemon.info sysinit: ntpd: sent query to 113.30.137.34
Sat Apr 19 18:14:56 2014 daemon.info sysinit: ntpd: sent query to 120.88.47.10
Sat Apr 19 18:14:56 2014 daemon.info sysinit: ntpd: sent query to 202.71.136.67
Sat Apr 19 18:14:56 2014 daemon.info sysinit: ntpd: sent query to 202.71.136.67
Sat Apr 19 18:14:56 2014 daemon.info sysinit: ntpd: reply from 113.30.137.34: reach 0x1f offset 0.017267 delay 0.054003 status 0x24 strat 3 refid 0x78582e0a rootdelay 0.180255
Sat Apr 19 18:14:56 2014 daemon.info sysinit: ntpd: reply from 202.71.136.67: reach 0x0f offset 0.024557 delay 0.054533 status 0x24 strat 2 refid 0xcbb9453c rootdelay 0.212467
Sat Apr 19 18:14:56 2014 daemon.info sysinit: ntpd: reply from 202.71.136.67: reach 0x1f offset 0.023411 delay 0.061723 status 0x24 strat 2 refid 0xcbb9453c rootdelay 0.212467
Sat Apr 19 18:14:56 2014 daemon.info sysinit: ntpd: reply from 120.88.47.10: reach 0x1f offset 0.013718 delay 0.079036 status 0x24 strat 2 refid 0xd8dafeca rootdelay 0.251148
Sat Apr 19 18:14:57 2014 daemon.info sysinit: ntpd: sent query to 202.71.136.67
Sat Apr 19 18:14:57 2014 daemon.info sysinit: ntpd: reply from 202.71.136.67: reach 0x1f offset 0.018893 delay 0.052906 status 0x24 strat 2 refid 0xcbb9453c rootdelay 0.212467
Sat Apr 19 18:14:58 2014 daemon.info sysinit: ntpd: sent query to 113.30.137.34
Sat Apr 19 18:14:58 2014 daemon.info sysinit: ntpd: sent query to 120.88.47.10
Sat Apr 19 18:14:58 2014 daemon.info sysinit: ntpd: sent query to 202.71.136.67
Sat Apr 19 18:14:58 2014 daemon.info sysinit: ntpd: reply from 113.30.137.34: reach 0x3f offset 0.019186 delay 0.049614 status 0x24 strat 3 refid 0x78582e0a rootdelay 0.180255
Sat Apr 19 18:14:58 2014 daemon.info sysinit: ntpd: reply from 202.71.136.67: reach 0x3f offset 0.021659 delay 0.057334 status 0x24 strat 2 refid 0xcbb9453c rootdelay 0.212467
Sat Apr 19 18:14:58 2014 daemon.info sysinit: ntpd: reply from 120.88.47.10: reach 0x3f offset 0.014466 delay 0.076696 status 0x24 strat 2 refid 0xd8dafeca rootdelay 0.251148
Sat Apr 19 18:14:59 2014 daemon.info sysinit: ntpd: sent query to 120.88.47.10
Sat Apr 19 18:14:59 2014 daemon.info sysinit: ntpd: sent query to 202.71.136.67
Sat Apr 19 18:14:59 2014 daemon.info sysinit: ntpd: reply from 202.71.136.67: reach 0x3f offset 0.019082 delay 0.055716 status 0x24 strat 2 refid 0xcbb9453c rootdelay 0.212467
Sat Apr 19 18:14:59 2014 daemon.info sysinit: ntpd: reply from 120.88.47.10: reach 0x7f offset 0.013746 delay 0.075203 status 0x24 strat 2 refid 0xd8dafeca rootdelay 0.251148
Sat Apr 19 18:15:00 2014 daemon.info sysinit: ntpd: sent query to 113.30.137.34
Sat Apr 19 18:15:00 2014 daemon.info sysinit: ntpd: sent query to 120.88.47.10
Sat Apr 19 18:15:00 2014 daemon.info sysinit: ntpd: sent query to 202.71.136.67
Sat Apr 19 18:15:00 2014 daemon.info sysinit: ntpd: sent query to 202.71.136.67
Sat Apr 19 18:15:00 2014 daemon.info sysinit: ntpd: reply from 113.30.137.34: reach 0x7f offset 0.017041 delay 0.053958 status 0x24 strat 3 refid 0x78582e0a rootdelay 0.180255
Sat Apr 19 18:15:00 2014 daemon.info sysinit: ntpd: reply from 202.71.136.67: reach 0x7f offset 0.020372 delay 0.058390 status 0x24 strat 2 refid 0xcbb9453c rootdelay 0.212467
Sat Apr 19 18:15:00 2014 daemon.info sysinit: ntpd: reply from 202.71.136.67: reach 0x7f offset 0.021874 delay 0.060055 status 0x24 strat 2 refid 0xcbb9453c rootdelay 0.212467
Sat Apr 19 18:15:00 2014 daemon.info sysinit: ntpd: reply from 120.88.47.10: reach 0xff offset 0.015910 delay 0.073849 status 0x24 strat 2 refid 0xd8dafeca rootdelay 0.251148
Sat Apr 19 18:15:01 2014 daemon.info sysinit: ntpd: sent query to 113.30.137.34
Sat Apr 19 18:15:01 2014 daemon.info sysinit: ntpd: sent query to 120.88.47.10
Sat Apr 19 18:15:01 2014 daemon.info sysinit: ntpd: sent query to 202.71.136.67
Sat Apr 19 18:15:01 2014 daemon.info sysinit: ntpd: reply from 113.30.137.34: reach 0xff offset 0.016989 delay 0.053360 status 0x24 strat 3 refid 0x78582e0a rootdelay 0.180255
Sat Apr 19 18:15:01 2014 daemon.info sysinit: ntpd: reply from 202.71.136.67: reach 0xff offset 0.024194 delay 0.057041 status 0x24 strat 2 refid 0xcbb9453c rootdelay 0.212467
Sat Apr 19 18:15:01 2014 daemon.info sysinit: ntpd: reply from 120.88.47.10: reach 0xff offset 0.016087 delay 0.073585 status 0x24 strat 2 refid 0xd8dafeca rootdelay 0.251148
Sat Apr 19 18:15:02 2014 daemon.info sysinit: ntpd: sent query to 113.30.137.34
Sat Apr 19 18:15:02 2014 daemon.info sysinit: ntpd: sent query to 120.88.47.10
Sat Apr 19 18:15:02 2014 daemon.info sysinit: ntpd: sent query to 202.71.136.67
Sat Apr 19 18:15:02 2014 daemon.info sysinit: ntpd: sent query to 202.71.136.67
Sat Apr 19 18:15:03 2014 daemon.info sysinit: ntpd: reply from 113.30.137.34: reach 0xff offset 0.019319 delay 0.049187 status 0x24 strat 3 refid 0x78582e0a rootdelay 0.180255
Sat Apr 19 18:15:03 2014 daemon.info sysinit: ntpd: reply from 202.71.136.67: reach 0xff offset 0.021312 delay 0.053450 status 0x24 strat 2 refid 0xcbb9453c rootdelay 0.212467
Sat Apr 19 18:15:03 2014 daemon.info sysinit: ntpd: reply from 202.71.136.67: reach 0xff offset 0.019759 delay 0.061267 status 0x24 strat 2 refid 0xcbb9453c rootdelay 0.212467
Sat Apr 19 18:15:03 2014 daemon.info sysinit: ntpd: reply from 120.88.47.10: reach 0xff offset 0.015300 delay 0.074049 status 0x24 strat 2 refid 0xd8dafeca rootdelay 0.251148
Sat Apr 19 18:15:04 2014 daemon.info sysinit: ntpd: sent query to 113.30.137.34
Sat Apr 19 18:15:04 2014 daemon.info sysinit: ntpd: sent query to 202.71.136.67
Sat Apr 19 18:15:04 2014 daemon.info sysinit: ntpd: sent query to 202.71.136.67
Sat Apr 19 18:15:04 2014 daemon.info sysinit: ntpd: reply from 113.30.137.34: reach 0xff offset 0.017143 delay 0.053154 status 0x24 strat 3 refid 0x78582e0a rootdelay 0.180255
Sat Apr 19 18:15:04 2014 daemon.info sysinit: ntpd: reply from 202.71.136.67: reach 0xff offset 0.020956 delay 0.053642 status 0x24 strat 2 refid 0xcbb9453c rootdelay 0.212467
Sat Apr 19 18:15:04 2014 daemon.info sysinit: ntpd: reply from 202.71.136.67: reach 0xff offset 0.017294 delay 0.055849 status 0x24 strat 2 refid 0xcbb9453c rootdelay 0.212467
Sat Apr 19 18:15:04 2014 daemon.info sysinit: --bitmain-options 115200:32:8:40:350:4d81 -o stratum+tcp://us1.ghash.io:3333 -O devesh.worker1:1234 -o stratum+tcp://uk1.ghash.io:3333 -O devesh.worker1:1234 -o stratum+tcp://stratum.50btc.com:3333 -O info@bitmaintech.com:1234 --api-listen --api-network
Sat Apr 19 18:15:04 2014 daemon.info sysinit: - init complete -
Sat Apr 19 18:15:38 2014 cron.info crond[569]: crond: USER root pid 874 cmd /usr/bin/cgminer-monitor
[ 0.000000] Linux version 3.10.12 (xxl@ubuntu) (gcc version 4.6.4 (OpenWrt/Linaro GCC 4.6-2013.05 r38031) ) #2 Fri Feb 7 18:50:12 CST 2014
[ 0.000000] MyLoader: sysp=1bec2fee, boardp=fdd6ef6f, parts=fc031564
[ 0.000000] bootconsole [early0] enabled
[ 0.000000] CPU revision is: 00019374 (MIPS 24Kc)
[ 0.000000] SoC: Atheros AR9330 rev 1
[ 0.000000] Clocks: CPU:400.000MHz, DDR:400.000MHz, AHB:200.000MHz, Ref:25.000MHz
[ 0.000000] Determined physical RAM map:
[ 0.000000] memory: 04000000 @ 00000000 (usable)
[ 0.000000] Initrd not found or empty - disabling initrd
[ 0.000000] Zone ranges:
[ 0.000000] Normal [mem 0x00000000-0x03ffffff]
[ 0.000000] Movable zone start for each node
[ 0.000000] Early memory node ranges
[ 0.000000] node 0: [mem 0x00000000-0x03ffffff]
[ 0.000000] On node 0 totalpages: 16384
[ 0.000000] free_area_init_node: node 0, pgdat 803005b0, node_mem_map 81000000
[ 0.000000] Normal zone: 128 pages used for memmap
[ 0.000000] Normal zone: 0 pages reserved
[ 0.000000] Normal zone: 16384 pages, LIFO batch:3
[ 0.000000] Primary instruction cache 64kB, VIPT, 4-way, linesize 32 bytes.
[ 0.000000] Primary data cache 32kB, 4-way, VIPT, cache aliases, linesize 32 bytes
[ 0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
[ 0.000000] pcpu-alloc: [0] 0
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 16256
[ 0.000000] Kernel command line: board=TL-WR741ND-v4 console=ttyATH0,115200 rootfstype=squashfs,jffs2 noinitrd
[ 0.000000] PID hash table entries: 256 (order: -2, 1024 bytes)
[ 0.000000] Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
[ 0.000000] Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
[ 0.000000] Writing ErrCtl register=00000000
[ 0.000000] Readback ErrCtl register=00000000
[ 0.000000] Memory: 61336k/65536k available (2187k kernel code, 4200k reserved, 588k data, 232k init, 0k highmem)
[ 0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[ 0.000000] NR_IRQS:51
[ 0.080000] Calibrating delay loop... 265.42 BogoMIPS (lpj=1327104)
[ 0.080000] pid_max: default: 32768 minimum: 301
[ 0.080000] Mount-cache hash table entries: 512
[ 0.090000] NET: Registered protocol family 16
[ 0.100000] MIPS: machine is TP-LINK TL-WR741ND v4
[ 0.100000] MAC FF:FF:FF:FF:FF:FF
[ 0.100000] MAC 20:59:a0:b1:fd:90
[ 0.560000] bio: create slab <bio-0> at 0
[ 0.560000] Switching to clocksource MIPS
[ 0.570000] NET: Registered protocol family 2
[ 0.570000] TCP established hash table entries: 512 (order: 0, 4096 bytes)
[ 0.580000] TCP bind hash table entries: 512 (order: -1, 2048 bytes)
[ 0.580000] TCP: Hash tables configured (established 512 bind 512)
[ 0.590000] TCP: reno registered
[ 0.590000] UDP hash table entries: 256 (order: 0, 4096 bytes)
[ 0.600000] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[ 0.610000] NET: Registered protocol family 1
[ 0.610000] PCI: CLS 0 bytes, default 32
[ 0.630000] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[ 0.630000] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
[ 0.640000] msgmni has been set to 119
[ 0.650000] io scheduler noop registered
[ 0.650000] io scheduler deadline registered (default)
[ 0.650000] Serial: 8250/16550 driver, 1 ports, IRQ sharing disabled
[ 0.660000] ar933x-uart: ttyATH0 at MMIO 0x18020000 (irq = 11) is a AR933X UART
[ 0.670000] console [ttyATH0] enabled, bootconsole disabled
[ 0.680000] ath79-spi ath79-spi: master is unqueued, this is deprecated
[ 0.690000] m25p80 spi0.0: found gd25q64, expected m25p80
[ 0.690000] m25p80 spi0.0: gd25q64 (8192 Kbytes)
[ 0.700000] 5 tp-link partitions found on MTD device spi0.0
[ 0.700000] Creating 5 MTD partitions on "spi0.0":
[ 0.710000] 0x000000000000-0x000000020000 : "u-boot"
[ 0.710000] 0x000000020000-0x000000117d84 : "kernel"
[ 0.720000] mtd: partition "kernel" must either start or end on erase block boundary or be smaller than an erase block -- forcing read-only
[ 0.730000] 0x000000117d84-0x0000007f0000 : "rootfs"
[ 0.730000] mtd: partition "rootfs" must either start or end on erase block boundary or be smaller than an erase block -- forcing read-only
[ 0.750000] mtd: partition "rootfs" set to be root filesystem
[ 0.750000] mtd: partition "rootfs_data" created automatically, ofs=0x370000, len=0x480000
[ 0.760000] 0x000000370000-0x0000007f0000 : "rootfs_data"
[ 0.770000] 0x000000020000-0x0000007f0000 : "firmware"
[ 0.770000] 0x0000007f0000-0x000000800000 : "art"
[ 0.790000] libphy: ag71xx_mdio: probed
[ 0.800000] eth0: Atheros AG71xx at 0xba000000, irq 5, mode:GMII
[ 1.350000] eth0: Found an AR7240/AR9330 built-in switch
[ 2.390000] eth1: Atheros AG71xx at 0xb9000000, irq 4, mode:MII
[ 2.940000] ag71xx ag71xx.0 eth1: connected to PHY at ag71xx-mdio.1:04 [uid=004dd041, driver=Generic PHY]
[ 2.950000] TCP: cubic registered
[ 2.950000] NET: Registered protocol family 17
[ 2.960000] 8021q: 802.1Q VLAN Support v1.8
[ 2.970000] VFS: Mounted root (squashfs filesystem) readonly on device 31:2.
[ 2.980000] Freeing unused kernel memory: 232K (80316000 - 80350000)
[ 5.810000] usbcore: registered new interface driver usbfs
[ 5.810000] usbcore: registered new interface driver hub
[ 5.820000] usbcore: registered new device driver usb
[ 5.820000] usbcore: registered new interface driver bitmain
[ 5.830000] hash ok
[ 5.830000] hashtest OK
[ 5.830000] bitmain-asic: success to register device
[ 5.840000] usbcore: registered new interface driver bitmainbl
[ 5.850000] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 5.860000] ehci-platform: EHCI generic platform driver
[ 5.860000] ehci-platform ehci-platform: EHCI Host Controller
[ 5.870000] ehci-platform ehci-platform: new USB bus registered, assigned bus number 1
[ 5.870000] ehci-platform ehci-platform: irq 3, io mem 0x1b000000
[ 5.900000] ehci-platform ehci-platform: USB 2.0 started, EHCI 1.00
[ 5.900000] hub 1-0:1.0: USB hub found
[ 5.900000] hub 1-0:1.0: 1 port detected
[ 6.240000] usb 1-1: new high-speed USB device number 2 using ehci-platform
[ 6.390000] hub 1-1:1.0: USB hub found
[ 6.390000] hub 1-1:1.0: 2 ports detected
[ 6.680000] usb 1-1.1: new full-speed USB device number 3 using ehci-platform
[ 6.780000] usb 1-1.1: device descriptor read/64, error -32
[ 6.970000] usb 1-1.1: device descriptor read/64, error -32
[ 7.160000] usb 1-1.1: new full-speed USB device number 4 using ehci-platform
[ 7.260000] usb 1-1.1: device descriptor read/64, error -32
[ 7.450000] usb 1-1.1: device descriptor read/64, error -32
[ 7.640000] usb 1-1.1: new full-speed USB device number 5 using ehci-platform
[ 8.060000] usb 1-1.1: device not accepting address 5, error -32
[ 8.160000] usb 1-1.1: new full-speed USB device number 6 using ehci-platform
[ 8.580000] usb 1-1.1: device not accepting address 6, error -32
[ 8.580000] hub 1-1:1.0: unable to enumerate USB device on port 1
[ 10.580000] jffs2: notice: (324) jffs2_build_xattr_subsystem: complete building xattr subsystem, 35 of xdatum (0 unchecked, 34 orphan) and 113 of xref (0 dead, 99 orphan) found.
[ 12.830000] hidraw: raw HID events driver (C) Jiri Kosina
[ 12.840000] Loading modules backported from Linux version master-2013-06-27-0-gdcfa6d5
[ 12.840000] Backport generated by backports.git backports-20130617-4-ge3220f5
[ 12.860000] nf_conntrack version 0.5.0 (962 buckets, 3848 max)
[ 12.880000] usbcore: registered new interface driver usbhid
[ 12.890000] usbhid: USB HID core driver
[ 12.900000] usbcore: registered new interface driver usbserial
[ 12.900000] usbcore: registered new interface driver usbserial_generic
[ 12.910000] usbserial: USB Serial support registered for generic
[ 12.940000] xt_time: kernel timezone is -0000
[ 12.960000] cfg80211: Calling CRDA to update world regulatory domain
[ 12.970000] cfg80211: World regulatory domain updated:
[ 12.970000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 12.980000] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 12.990000] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 13.000000] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 13.000000] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 13.010000] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 13.030000] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 13.150000] ath: EEPROM regdomain: 0x0
[ 13.150000] ath: EEPROM indicates default country code should be used
[ 13.150000] ath: doing EEPROM country->regdmn map search
[ 13.150000] ath: country maps to regdmn code: 0x3a
[ 13.150000] ath: Country alpha2 being used: US
[ 13.150000] ath: Regpair used: 0x3a
[ 13.170000] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[ 13.170000] cfg80211: Calling CRDA for country: US
[ 13.180000] ieee80211 phy0: Atheros AR9330 Rev:1 mem=0xb8100000, irq=2
[ 13.190000] cfg80211: Regulatory domain changed to country: US
[ 13.190000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 13.200000] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)
[ 13.210000] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm)
[ 13.210000] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 13.220000] cfg80211: (5490000 KHz - 5600000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 13.230000] cfg80211: (5650000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 13.240000] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)
[ 18.000000] device eth0 entered promiscuous mode
[ 20.200000] eth1: link up (100Mbps/Full duplex)
 I checked Kernel Logs on 2 Ants, and am getting some extra stuff after your last line [ 20.310000] eth1: link up (100Mbps/Full duplex)
[ 21.500000] usb 1-1.1: USB disconnect, device number 3
[ 21.500000] bitmain 1-1.1:1.0: USB Bitmain asic #0 now disconnected
[ 21.790000] usb 1-1.1: new full-speed USB device number 4 using ehci-platform
[ 21.940000] bitmainbl 1-1.1:1.0: USB Bitmain bootloader device now attached to USB Bitmain bootloader-0
[ 21.950000] PIC microchip bootloader usb OK
[ 31.380000] no int in filled
[ 32.750000] usb 1-1.1: USB disconnect, device number 4
[ 32.760000] bitmainbl 1-1.1:1.0: USB Bitmain asic #0 now disconnected
[ 33.010000] usb 1-1.1: new full-speed USB device number 5 using ehci-platform
[ 33.150000] bitmain 1-1.1:1.0: USB Bitmain asic device now attached to USB Bitmain asic-0
[ 33.160000] PIC microchip usb OK
[ 62.630000] bitmain 1-1.1:1.0: USB Bitmain asic #0 now disconnected
Are you getting anything else at the end of the Kernel Log? From your status line, looks like your blades are not detected (or you did not wait long enough, as this screen capture is after 1m) Could be interconnecting cables to the blades, power supplie(s), corrupt firmware? Good luck |
|
|
|
Don't worry about that, we all make our silly mistakes, hopefully to learn from them  (I had a similar typo error when starting my first Antminer S1, dreading that it was DOA, ended up being a typing error in the worker parameters) Enjoy your hashing adventure Cheers |
|
|
|
Kabopar - Well that makes sense, as I have probably confused myself in the process of trying to get it working.
I tried using the config you suggested, and its not finding my URL. The address is correct (eu-stratum.btcguild.com:3333), I am just wondering if the prefixes are correct?
Just for clarity, the Antminer is plugged straight into laptop. I want to be able to get one working first before even thinking about buying a rig steup
On BFGminer, I'm using http://stratum-lb-usa48.btcguild.com:3333 for BTCguild. Perhaps you need to add the "http://". The BTC Guild support page says that its addresses are Host (USA) stratum.btcguild.com:3333 Host (EU) eu-stratum.btcguild.com:3333 In some cases I used "stratum+tcp://stratum.bitcoin.cz:3333", so it looks like the "http://" may not be mandatory, however it would be easy to try. Regarding running the Antminer U2 directly from a laptop port, there is the possibility that it requires more current than the port can provide. I don't think that I tried to run it ever from a laptop or PC port. Cheers |
|
|
|
how wide is the address space of your router (some routers are set for say 192.168.1 - 50, so if the Ant is set to a fixed IP of 192.168.1.99 as per the sticker it might not be 'seen' by the router). Sushi's guide https://bitcointalk.org/index.php?topic=344970.0 points to some IP scan software ( http://www.advanced-ip-scanner.com/). Try to see if the wifi is active (there are simple wifi scanners such as inSSIDer that might help http://www.metageek.net/products/inssider/). Can you swap the control board with a known working Ant? If you are trying to run it standalone against a PC, you should set the PC temporarily to a fixed IP in the same space as the Ant and connect them with a crossover cable, or through a hub/switch. An ethernet switch would give you a clue if the connection is alive through the status lights of the port that the Ant is connected to. If all else fails, try to contact Bitmain (see email addresses at https://www.bitmaintech.com/about.htm) Good luck |
|
|
|
cgminer.exe -set-device antminer:clock=x0981 -o http://eu-stratum-btcguild.com:3333 -u (username) -p (password) -S antminer:all that just causes CMD to open then close quickly. when I ran it through exe and input variables via CMD, that's when I just got the blank screen with occassional blinking cursor Looks like your short-cut or batch file is a mix of cgminer and bfgminer. Both can be used for the antminer U2, as long as you set the appropriate drivers and correct parameters. Assuming that you are running Windows: Drivers: For cgminer use the win-usb driver most probably with the assistance of the Zadig utility. Bfgminer uses the silabs VCP DRIVERS. Not Zadig/win-usb. If you wish to shift to bfgminer, remove the win-usb driver by going to device manager with it plugged in, right-click choose driver settings make sure the checkbox for delete driver is ticked, then install the Silabs VCP driver from http://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx. Either Cgminer or Bfgminer configuration can be controlled by command line/short-cut/batch file parameters, or by entries in their configuration file (default is cgminer.conf for cgminer and bfgminer.conf for bfgminer). for bfgminer the Antminer U1/2 parameters in a batch file would look like: bfgminer.exe -S antminer:all --set-device antminer:clock=x0981 (replace x0981 with the clock setting of your choice, see the Antminer manual at https://www.bitmaintech.com/userfiles/download/AntMiner%20U1%20user%20guide.pdf) you can add your pool and user settings there as well -o stratum+tcp://stratum.bitcoin.cz:3333 -u User -p Pwd (or when bfgminer starts, then save the configuration file to avoid future reentry). There is plenty of information at this forum on setting Antminer U1/U2 devices. Make sure that you run them on a well powered USB hub with some cooling. Cheers |
|
|
|
well: I get 360 watts on a 120 volt seasonic 750 platinum psu for 350ghz at the k-watt plug I get 379 watts " " " " " " " " " 375ghz at the k-watt plug I get 396 -401 watts --------------------------------------------- 400 ghz at the k-watt plug but that is my most efficient psu my worst is a 1000 watt bronze it gets 423 watts for 400ghz I dumped a server 750 watt since it did 475 watts for 400ghz minor typo - you probably meant MHz (not ghz) LOL:) |
|
|
|
Got my two boards, they look great, but both heatsinks immediately fell off. I thought that maybe they just shook loose during shipping, so I pressed them back on as firmly as I could -- but one of them fell off with a clunk just as I got hashing a few minutes later. Now I'm debating whether to drill some holes or just run them heatsink-side-up.
It's not a huge problem, but was there a reason you didn't screw the heatsinks in place?
Despite earlier photos showing the heatsink below, Barntech later suggested to position the board with the heatsink on top, to avoid the 'separation' that you described. I started with the heatsink below, later turned the boards so it is on top on my 4 Av16 boards. No separation so far on mine. Drilling holes might be risky, as you could bridge internal ground and power layers. The first and easy step is to turn the boards so the heatsinks face up. You may want to consult Barntech (check out the drillbit forum at http://drillbitsystem.com/forum/, you may want to register there so that you may post your issue) about any adhesive or way of re-attaching the heatsinks to ensure good thermal transfer and avoid pre-mature thermal death of your ASICS. Cheers |
|
|
|
Got my two new 16boards connected power, link down to up and plugged in usb at the down board, windoze now can see one extra 8boards aka 16. the special cgminer can see the extra boards but it's not hashing? i obviously missing something, clock init settings?
ed. drivers drivers drivers and int:500:1:900 with --drillbit-options int:52:2:950. ok the 8 and 16 dont want work together
ok it shows 5 8boards and two 16boards but --drillbit-options Eight:int:52:2:950,Av16:int:750:1:950 does not seem to work it blinks then quits ed. the only i can get these boards to work is by splitting them up into two batch files like this:cgminer --drillbit-options int:750:1:950 --usb drb:6 -o http://stratum.bitcoin.cz:3333 -u user -p password --usb drb:7 -o http://stratum.bitcoin.cz:3333 -u user0 -p password and the other batch using --usb drb:1 to drb:5 These boards are not fully 'hot plug'. Unless you can bring power to all of your Av16 boards at once, checkout the suggestion at http://drillbitsystem.com/forum/index.php?topic=309.15 about a power-up sequence to get all Av16 boards running. I have now 4 Av16 boards and a single drillbit8 board. I run the drillbit8 board on a separate instance of cgminer 4.0.1 and the Av16 boards on an instance of cgminer 4.2.1. The Av16 boards are detected as a single entity with a "DRB 0: A 4..." designation meaning that it is a group of 4 boards. The Av16 are now running with a setting of "Av16:int:750:1:1000" (in cgminer.conf), getting about 87.5 GH/s, with a temp of 51-52 deg C. Cheers doing the same , how would i specify to only use drb 1 to 5 for the one and 6 and 7 (the 16boards) the other the 8boards --drillbit-options int:52:2:950 -o http://stratum.bitcoin.cz:3333 -u user3 -p password --usb drb:1 --usb drb:2 --usb drb:3 --usb drb:4 --usb drb:5 the two av16 cgminer --drillbit-options int:750:1:1000 -o http://stratum.bitcoin.cz:3333 -u user -p password --usb drb:6 --usb drb:7 funny thing is if the 8boards stops the other wants to take over and pics up the 8baords even when i only specified drb:6 and 7 For the Eight board, my cgminer.conf file uses "drillbit-options" : "Eight:int:53:2:950", "usb" : ":1" (the "usb": part tells it to look just for 1 device) For the Av16 boards the conf file has "drillbit-options" : "Av16:int:750:1:1000", "usb" : ":1" (again, cgminer sees this 'bunch' as a single USB device). The 'Eight' or 'Av16' tells this instance which device type to apply this for. I just happen to use different versions of cgminer for these 2 (currently running 4 instances of cgminer and 2 of bfgminer on the same pc to control a garden variety of miners including Drillbit Thumbs (bf), Drillbit AvThumbs, Drillbit Eight, Drillbit Av16's, Blue/Red Fury, Antminer U1/2's... Cheers |
|
|
|
Got my two new 16boards connected power, link down to up and plugged in usb at the down board, windoze now can see one extra 8boards aka 16. the special cgminer can see the extra boards but it's not hashing? i obviously missing something, clock init settings?
ed. drivers drivers drivers and int:500:1:900 with --drillbit-options int:52:2:950. ok the 8 and 16 dont want work together
ok it shows 5 8boards and two 16boards but --drillbit-options Eight:int:52:2:950,Av16:int:750:1:950 does not seem to work it blinks then quits ed. the only i can get these boards to work is by splitting them up into two batch files like this:cgminer --drillbit-options int:750:1:950 --usb drb:6 -o http://stratum.bitcoin.cz:3333 -u user -p password --usb drb:7 -o http://stratum.bitcoin.cz:3333 -u user0 -p password and the other batch using --usb drb:1 to drb:5 These boards are not fully 'hot plug'. Unless you can bring power to all of your Av16 boards at once, checkout the suggestion at http://drillbitsystem.com/forum/index.php?topic=309.15 about a power-up sequence to get all Av16 boards running. I have now 4 Av16 boards and a single drillbit8 board. I run the drillbit8 board on a separate instance of cgminer 4.0.1 and the Av16 boards on an instance of cgminer 4.2.1. The Av16 boards are detected as a single entity with a "DRB 0: A 4..." designation meaning that it is a group of 4 boards. The Av16 are now running with a setting of "Av16:int:750:1:1000" (in cgminer.conf), getting about 87.5 GH/s, with a temp of 51-52 deg C. Cheers |
|
|
|
Ages ago, when people still used GPU's for bitcoin mining, the AMD family of GPUs was much more capable than the Nvidia ones. Nowadays using GPUs for BTC mining is over, they consume more electricity than they can generate. A mobile GPU could achieve something like 20 MH/s (see https://en.bitcoin.it/wiki/Mining_hardware_comparison). Don't waste your time or try killing your laptop... Cheers |
|
|
|
|
Show Posts
