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

You should be just fine.

EDIT: If you can though get a PSU with more wattage.
Much better.

Specs show 200w (not OCed).
http://www.amazon.com/ASICMiner-Block-Erupter-Cube-Miner/dp/B00H8K3MZU

Probably

Edit:  Sell the cube to some poor sucker unless your power is free.  The cube consumes more power than it produces in coins, even if not OCed.

What is the wattage requirements for the BE Cube?

I am pretty sure the answer is no, but would it be possible to run 1 S1 (possible OC) and 1 BE Cube (on low) with a Corsair Builder 750 PSU?

OK fixed now




what is the freq_value for the 393.75 chip freq does anyone know

Interesting.  I only powered down for 30 secs when i did it.  Didn't want to miss any mining time.   Does it need to be cleaned?

well at the time of the post i was only getting like 90ghs after a powerdown and 10 min wait i am now getting 171ghs that is very slowly falling and now i see this


Chain#   ASIC#   Frequency   Fan     Temp                             ASIC status
1                 8               350            2280         44           xxxxxxxx xxxxxoxo xoxoxoxo oooooooo
2               32              350               0              49      oooooooo oooooooo oooooooo oooooooo

^^^ What he said. Try it.
Also if you get xxxxx yet your hashing speeds are normal then you are fine.

Have you tried powering down?  Mine did that a couple of days ago.  I lost 16 of them.  I just powered down the psu and waited for a couple of minutes, and powered it back up.  Everything was fine.

... and I updated the cgminer binary again to add some more commits to fix a solo mining problem on the ant:
https://bitcointalksearch.org/topic/m.5856097

can anyone explain to me what is going on this unit has only been running for like a 4 days at stock settings



AntMiner
Chain#   ASIC#   Frequency   Fan             Temp                                 ASIC status
1                 2                 350          1200              41           xxxxxxxx xxxxxxxx xxxxxxxx xxxxxooo
2                 32               350             0                 42      oooooooo oooooooo oooooooo oooooooo

Try using the WiFi connection.

Still happening.  Ping stats from the computer on the same switch show no network outage.

Okay I have something odd going on.  But first something funny, the Ants that I received had ips set up on them and mining addresses set up in them, they were not default IP, so someone got some free hashing power as I went through and set up each one.  Anyway, one of my miners is functioning oddly, the Ethernet plug in has had its green light on sold on occasion and the unit will not be mining.  Additionally I have it, as well as all of them, set up on wireless. Each miner has a wireless ip and an Ethernet ip that do not match up on each machine (should I set the ether to the same ip as the wifi?), but this one miner I cannot access through wireless, it is mining, I can access it through the Ethernet just not the wireless.  Any idea's why this one unit times out and cannot be accessed wireless?  

So continuing on with my errors..

I know my HW error rate is acceptable on the unit in question
But my other two units have green lights on under the LAN connector and the one with the HW error doesn't have it on

They are all mining at 180GHS but is it something I should be worried about?
I think it may not be reading the fan/temp properly? The fan is always 400 rpm more than the other units

Thanks,

Hi,

Uhmm this one will be ok for 1 Ant. If you think you'll get another ant in the future; you can choose:
http://www.ebay.co.uk/itm/Dell-PowerEdge-2800-Server-POWER-SUPPLY-7000815-0000-D3014-930W-PSU-dw1-/251478903791?pt=UK_Computing_PowerSupplies_EH&hash=item3a8d4f8bef

This one will power 2 ants... It will cost you around 20-22GBP.

One note! These PSU's have a max amount of watts you can use on each output pin.. So if you have a complete ant (both blades) on 1 output pin...then you'll be pulling >360W on a pin that has a max of 312W (in case of the 930W PSU). You'll fry it... like I did

If you have teamviewer i can help you

I got 3 antminers and they all have the same problem of not being able to start hashing.  I have tried several things from the thread with no success.

Sat Mar 22 16:05:08 2014 daemon.info dnsmasq[694]: 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 Mar 22 16:05:08 2014 daemon.info dnsmasq[694]: using local addresses only for domain lan
Sat Mar 22 16:05:08 2014 daemon.info dnsmasq[694]: reading /tmp/resolv.conf.auto
Sat Mar 22 16:05:08 2014 daemon.info dnsmasq[694]: using nameserver 8.8.4.4#53
Sat Mar 22 16:05:08 2014 daemon.info dnsmasq[694]: using nameserver 8.8.8.8#53
Sat Mar 22 16:05:08 2014 daemon.info dnsmasq[694]: using local addresses only for domain lan
Sat Mar 22 16:05:08 2014 daemon.info dnsmasq[694]: read /etc/hosts - 1 addresses
Sat Mar 22 16:05:08 2014 daemon.info sysinit: /etc/config/miner_pic.hex
Sat Mar 22 16:05:08 2014 kern.info kernel: [   21.230000] usb 1-1.1: USB disconnect, device number 3
Sat Mar 22 16:05:08 2014 kern.info kernel: [   21.240000] bitmain 1-1.1:1.0: USB Bitmain asic #0 now disconnected
Sat Mar 22 16:05:08 2014 kern.info kernel: [   21.490000] usb 1-1.1: new full-speed USB device number 4 using ehci-platform
Sat Mar 22 16:05:08 2014 kern.info kernel: [   21.630000] bitmainbl 1-1.1:1.0: USB Bitmain bootloader device now attached to USB Bitmain bootloader-0
Sat Mar 22 16:05:08 2014 kern.warn kernel: [   21.640000] PIC microchip bootloader usb OK
Sat Mar 22 16:05:09 2014 daemon.notice netifd: lan (637): Sending discover...
Sat Mar 22 16:05:12 2014 daemon.notice netifd: lan (637): Sending discover...
Sat Mar 22 16:05:18 2014 kern.warn kernel: [   30.980000] no int in filled
Sat Mar 22 16:05:18 2014 daemon.info sysinit: pic update
Sat Mar 22 16:05:18 2014 daemon.info sysinit: open /dev/bitmain0 to restart pic
Sat Mar 22 16:05:18 2014 daemon.info sysinit: open /dev/bitmainbl0 ok fd = 0x4
Sat Mar 22 16:05:18 2014 daemon.info sysinit: read data
Sat Mar 22 16:05:18 2014 daemon.info sysinit:

• {0x1}, [1]{0x10}, [2]{0x1}, [3]{0x10}, [4]{0x1}, [5]{0}, [6]{0x10}, [7]{0x1}, [8]{0x10}, [9]{0x4}, [10]{0x4},

Sat Mar 22 16:05:18 2014 daemon.info sysinit: Version 1.0
Sat Mar 22 16:05:18 2014 daemon.info sysinit: open pic update file fail
Sat Mar 22 16:05:18 2014 daemon.info sysinit: Control bootloader to app
Sat Mar 22 16:05:18 2014 daemon.info sysinit: setting up led WAN
Sat Mar 22 16:05:18 2014 daemon.info sysinit: setting up led WANL
Sat Mar 22 16:05:18 2014 daemon.info sysinit: setting up led LAN1
Sat Mar 22 16:05:18 2014 daemon.info sysinit: setting up led LAN2
Sat Mar 22 16:05:18 2014 daemon.info sysinit: setting up led LAN3
Sat Mar 22 16:05:18 2014 daemon.info sysinit: setting up led LAN4
Sat Mar 22 16:05:18 2014 daemon.info sysinit: setting up led WLAN
Sat Mar 22 16:05:19 2014 kern.info kernel: [   32.300000] usb 1-1.1: USB disconnect, device number 4
Sat Mar 22 16:05:19 2014 kern.info kernel: [   32.400000] bitmainbl 1-1.1:1.0: USB Bitmain asic #0 now disconnected
Sat Mar 22 16:05:20 2014 kern.info kernel: [   32.810000] usb 1-1.1: new full-speed USB device number 5 using ehci-platform
Sat Mar 22 16:05:20 2014 kern.info kernel: [   32.950000] bitmain 1-1.1:1.0: USB Bitmain asic device now attached to USB Bitmain asic-0
Sat Mar 22 16:05:20 2014 kern.warn kernel: [   32.950000] PIC microchip usb OK
Sat Mar 22 16:05:23 2014 daemon.info sysinit: ntpd: resolved peer 3.openwrt.pool.ntp.org to 198.60.22.240
Sat Mar 22 16:05:23 2014 daemon.info sysinit: ntpd: sent query to 198.60.22.240
Sat Mar 22 16:05:23 2014 daemon.info sysinit: ntpd: resolved peer 2.openwrt.pool.ntp.org to 66.228.59.187
Sat Mar 22 16:05:23 2014 daemon.info sysinit: ntpd: sent query to 66.228.59.187
Sat Mar 22 16:05:23 2014 daemon.info sysinit: ntpd: resolved peer 1.openwrt.pool.ntp.org to 173.230.158.30
Sat Mar 22 16:05:23 2014 daemon.info sysinit: ntpd: sent query to 173.230.158.30
Sat Mar 22 16:05:23 2014 daemon.info sysinit: ntpd: resolved peer 0.openwrt.pool.ntp.org to 168.158.178.5
Sat Mar 22 16:05:23 2014 daemon.info sysinit: ntpd: sent query to 168.158.178.5
Sat Mar 22 16:05:32 2014 daemon.info sysinit: Alarm clock
Sat Mar 22 16:05:33 2014 daemon.info sysinit: --bitmain-options 115200:32:8:40:350:4d81 -o stratum.btcguild.com:3333 -O bursting_1:123 --api-listen --api-network
Sat Mar 22 16:05:33 2014 daemon.info sysinit: - init complete -
Sat Mar 22 16:05:33 2014 kern.info kernel: [   45.940000] bitmain 1-1.1:1.0: USB Bitmain asic #0 now disconnected
Sat Mar 22 16:06:01 2014 cron.info crond[567]: crond: USER root pid 864 cmd /usr/bin/cgminer-monitor


When I attempt pinging I get this:
PING openwrt.org (78.24.191.177): 56 data bytes

--- openwrt.org ping statistics ---
5 packets transmitted, 0 packets received, 100% packet loss

When I disable the NTP client in the system, nothing changes.  My guess is the NTP, but even when I change the candidates, it still just uses openwrt anyways.  I have been working with this for several hours now and I'm at a complete loss, so any is is appreciated.

I'm using the EVGA 1000w P2.  Currently only powering one, will eventually be powering two.

What PSU are you using?