Latest posts of: nelsoncs

Bitcoin Forum

September 26, 2024, 09:53:18 PM

Welcome, Guest. Please login or register.

News: Latest Bitcoin Core release: 27.1 [Torrent]

Home

Help

Search

Login

Register

More

Show Posts
Pages: [1]

1

Bitcoin / Hardware / Re: ANTMINER S3 Discussion and Support Thread.

on: November 30, 2014, 04:15:56 AM

Quote from: jackbox on November 30, 2014, 03:59:04 AM Quote from: nelsoncs on November 30, 2014, 03:35:49 AM Quote from: Tupsu on November 30, 2014, 03:02:15 AM Quote from: jackbox on November 30, 2014, 02:58:03 AM I am sure it has been asked and answered but this thread is so long hard to go through it all. What is a good quality fan to replace the two fans on the S3+? I would want ones that push a lot of air, run lower rpm and are much quieter. My S3+ is very loud when the fans kick on to higher speeds. Use something better http://www.watercoolinguk.co.uk/p/Noctua-NA-SRC7-Low-Noise-Adapter-for-4-pin-PWM-fan_46291.html from the desc for this item: Connected between the fan and the power source adapter to reduce the speed and noise emissions. reduce speed == reduce cooling == increase heat. Seriously, this is a bad idea. Nope. They are high CFM fans that can push more air at lower speeds and lower db levels. HUh? sorry but the items shown are "adapters" not fans. they reduce the speed of a connected fan. clearly more air at lower speed would reduce air vibratinos and therefore reduce noise while reducing heat effectively, the adapters will not do that.

2

Bitcoin / Hardware / Re: ANTMINER S3 Discussion and Support Thread.

on: November 30, 2014, 03:35:49 AM

Quote from: Tupsu on November 30, 2014, 03:02:15 AM Quote from: jackbox on November 30, 2014, 02:58:03 AM I am sure it has been asked and answered but this thread is so long hard to go through it all. What is a good quality fan to replace the two fans on the S3+? I would want ones that push a lot of air, run lower rpm and are much quieter. My S3+ is very loud when the fans kick on to higher speeds. Use something better http://www.watercoolinguk.co.uk/p/Noctua-NA-SRC7-Low-Noise-Adapter-for-4-pin-PWM-fan_46291.html from the desc for this item: Connected between the fan and the power source adapter to reduce the speed and noise emissions. reduce speed == reduce cooling == increase heat. Seriously, this is a bad idea.

3

Bitcoin / Hardware / Re: ANTMINER S3 Discussion and Support Thread.

on: November 20, 2014, 10:51:39 PM

Quote from: mdude77 on November 20, 2014, 10:13:07 PM Quote from: nelsoncs on November 20, 2014, 08:24:02 PM Problem with antminer s3+ solo. My miners work fine for a pool. But when I try to run solo I get either a very, very slow hash rate and super high error rate(s), or the miners may also refuse to connect to the machine running bitcoin-qt/bitcoind and also may incorrectly report connections as being alive or dead. I have tried upgrading cgminer to the most recent version, to no avail. Often, cgminer quits after a few minutes. here is my cgminer command line (<> indicate substitutions to protect the innocent): --bitmain-options 115200:32:8:18:225:0882 -o http://192.168.0.2:8332 -O <somename>:<some password> --verbose --btc-address 1D7CFcY3gYMgNrns6ttRmomyGTLNzZ6XRA --api-listen --api-network --bitmain-checkn2diff --bitmain-hwerror --version-file /usr/bin/compile_time --queue 4096 here is my bitcoin-qt/bitcoind command line: -datadir=/home/<some_user_path>.bitcoin -rpcuser=<somename> -rpcpassword=<some password> -blocknotify=%s -alertnotify=%s The verbose flag did not seem to give any more info, I can find an open port :8332 on the bitcoind machine and netstat will report "ESTABLISHED" then "CLOSE_WAIT". Any suggestions on how to debug the rpc connection or cgminer would be greatly appreciated. I may have no hair left soon. The way you describe this, it sounds like you are running cgminer somewhere outside of your Ants. I'm pretty sure that's not going to work for you. Try editing the cgminer config inside the Ant to have the solo mining options to point it to your Bitcoin instance: cgminer -o http://<bitcoin IP>:<bitcoin port> -u <username> -p <password> --btc-address <your address> Also, CK (author of cgminer) has a public "solo mining pool" up.. if you don't mind the 0.5% fee: https://bitcointalk.org/index.php?topic=763510.0 M I see, no cgminer is only running on the antminers and bitcoind is running on a xeon based desktop. I will definitely check the "solo" pool. Thanks. so: antminer-->cgminer <-- local network --> bitcoind<--desktop.

4

Bitcoin / Hardware / Re: ANTMINER S3 Discussion and Support Thread.

on: November 20, 2014, 10:07:53 PM

Quote from: windpath on November 20, 2014, 09:57:56 PM Quote from: iglasses on November 20, 2014, 09:51:22 PM I have been involved in a few of the threads related to this topic. Solo mining with an Antminer is essentially hopeless. The only way to get it to run is to setup your own pool and even that is a freaking hassle far beyond what is reasonable or worthwhile for the average person. They run great on p2pool, have 8 S3's and a few S1's running for a while with 0 issues... I may give p2pool a try, I have more than one machine, so I can dedicate one to serving upa pool if I need to. As for antminers being "hopeless", the reason that I am trying this is I have seen my machines Find two blocks during the last four months, for which the pool I was in gave me diddly squat. Not that I have any thing against the pool, it is a great service, but obviously if I only find on more block the rest of my life (well antminer's life) I will be soooo much better off.

5

Bitcoin / Hardware / Re: ANTMINER S3 Discussion and Support Thread.

on: November 20, 2014, 10:00:25 PM

Quote from: MissouriMiner on November 20, 2014, 09:21:08 PM Quote from: nelsoncs on November 20, 2014, 08:54:31 PM Thanks for the suggestion, I failed to note I also have a bitcoin.conf file that contains that line. Adding it to the command line, now: bitcoind -datadir=/home/develop/utility/sophie/exec/.bitcoin -rpcuser=antminer -rpcpassword=yd39628 -rpcallowip=192.168.0.* -blocknotify=%s -alertnotify=%s does not change the failure. cgminer still quits, actually it appears to start, restart one or two times, then quit for good. Starting Nmap 6.46 ( http://nmap.org ) at 2014-11-20 12:52 PST Nmap scan report for 192.168.0.2 Host is up (0.0000050s latency). Not shown: 9997 closed ports PORT STATE SERVICE 22/tcp open ssh 8200/tcp open trivnet1 8332/tcp open unknown 8333/tcp open bitcoin Do you have a firewall running on the system running bitcoind? I have mine on a Linux host and had to add an iptables entry. And I added listen=1 to bitcoin.conf. I've tried solo mining with and S3 (and default cgminer code) and it works fine. yes, this is a linux machine but it is on my local network and the antminers are also on the same network, all are behind the same external firewall. sudo iptables --list Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination So, my ip_table is empty, no rules. Tried -listen=1 but getting the same behaviour. Thanks for the suggestion.

6

Bitcoin / Hardware / Re: ANTMINER S3 Discussion and Support Thread.

on: November 20, 2014, 08:54:31 PM

Thanks for the suggestion, I failed to note I also have a bitcoin.conf file that contains that line. Adding it to the command line, now: bitcoind -datadir=/home/develop/utility/sophie/exec/.bitcoin -rpcuser=antminer -rpcpassword=yd39628 -rpcallowip=192.168.0.* -blocknotify=%s -alertnotify=%s does not change the failure. cgminer still quits, actually it appears to start, restart one or two times, then quit for good. Starting Nmap 6.46 ( http://nmap.org ) at 2014-11-20 12:52 PST Nmap scan report for 192.168.0.2 Host is up (0.0000050s latency). Not shown: 9997 closed ports PORT STATE SERVICE 22/tcp open ssh 8200/tcp open trivnet1 8332/tcp open unknown 8333/tcp open bitcoin

7

Bitcoin / Hardware / Re: ANTMINER S3 Discussion and Support Thread.

on: November 20, 2014, 08:24:02 PM

Problem with antminer s3+ solo. My miners work fine for a pool. But when I try to run solo I get either a very, very slow hash rate and super high error rate(s), or the miners may also refuse to connect to the machine running bitcoin-qt/bitcoind and also may incorrectly report connections as being alive or dead. I have tried upgrading cgminer to the most recent version, to no avail. Often, cgminer quits after a few minutes. here is my cgminer command line (<> indicate substitutions to protect the innocent): --bitmain-options 115200:32:8:18:225:0882 -o http://192.168.0.2:8332 -O <somename>:<some password> --verbose --btc-address 1D7CFcY3gYMgNrns6ttRmomyGTLNzZ6XRA --api-listen --api-network --bitmain-checkn2diff --bitmain-hwerror --version-file /usr/bin/compile_time --queue 4096 here is my bitcoin-qt/bitcoind command line: -datadir=/home/<some_user_path>.bitcoin -rpcuser=<somename> -rpcpassword=<some password> -blocknotify=%s -alertnotify=%s The verbose flag did not seem to give any more info, I can find an open port :8332 on the bitcoind machine and netstat will report "ESTABLISHED" then "CLOSE_WAIT". Any suggestions on how to debug the rpc connection or cgminer would be greatly appreciated. I may have no hair left soon.

Pages: [1]

Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines