vs3
|
|
May 11, 2014, 06:18:45 AM |
|
Lately I've been having weird issues with bfgminer mostly when the connection with eligius drops - if at some point the pool disconnects then after the reconnect or switch to another pool my miners just never start hashing again. Saw this in the log today: [2014-05-10 20:55:08] Accepted 04f7b06f NFY 1c pool 3 Diff 51/16 [2014-05-10 20:55:08] Accepted 0d3bef9f NFY 1a pool 3 Diff 19/16 [2014-05-10 20:55:08] Accepted 00380c0c NFY 1a pool 3 Diff 1.17k/16 [2014-05-10 20:55:08] Accepted 054b4b91 NFY 1d pool 3 Diff 48/16 [2014-05-10 20:56:08] Stratum connection to pool 3 interrupted [2014-05-10 20:56:08] Pool 3 http://stratum.mining.eligius.st:3334 not responding! [2014-05-10 20:56:08] Switching to pool 1 stratum+tcp://mint.bitminter.com:3333 [2014-05-10 20:56:08] pool 1 JSON stratum auth failed: [ 20, "Unknown method 'mining.get_transactions'", null ] [2014-05-10 20:56:08] Pool 1 stratum+tcp://mint.bitminter.com:3333 not responding! [2014-05-10 20:56:08] Switching to pool 2 stratum+tcp://stratum.mining.eligius.st:3334 [2014-05-10 20:56:08] pool 1 JSON stratum auth failed: [ 20, "Unknown method 'mining.get_transactions'", null ] [2014-05-10 20:56:31] Pool 2 stratum+tcp://stratum.mining.eligius.st:3334 not responding! [2014-05-10 20:56:39] Pool 1 stratum+tcp://mint.bitminter.com:3333 alive, testing stability [2014-05-10 20:56:46] Switching to pool 1 stratum+tcp://mint.bitminter.com:3333 [2014-05-10 21:06:14] Stratum from pool 1 detected new block [2014-05-10 21:17:22] Stratum from pool 1 detected new block [2014-05-10 21:35:19] Stratum from pool 1 detected new block [2014-05-10 21:36:36] Stratum from pool 1 detected new block [2014-05-10 21:46:19] Stratum from pool 1 detected new block [2014-05-10 21:59:46] Stratum from pool 1 detected new block [2014-05-10 22:07:13] Stratum from pool 1 detected new block
for the record - I have the following pools: 0,2,3 - eligius, 1 - bitminter this was when running build: 3177195928193c7f744eee45885a3c3e1f8df49e-win32-gradual but it's been happening for a while (maybe last 1-2 months) Am I doing something possibly wrong? Or in the alternative - which debug logs/options should I turn on to get more details for further troubleshooting?
|
|
|
|
Luke-Jr (OP)
Legendary
Offline
Activity: 2576
Merit: 1186
|
|
May 11, 2014, 07:41:55 AM |
|
Lately I've been having weird issues with bfgminer mostly when the connection with eligius drops - if at some point the pool disconnects then after the reconnect or switch to another pool my miners just never start hashing again. Saw this in the log today: [2014-05-10 20:55:08] Accepted 04f7b06f NFY 1c pool 3 Diff 51/16 [2014-05-10 20:55:08] Accepted 0d3bef9f NFY 1a pool 3 Diff 19/16 [2014-05-10 20:55:08] Accepted 00380c0c NFY 1a pool 3 Diff 1.17k/16 [2014-05-10 20:55:08] Accepted 054b4b91 NFY 1d pool 3 Diff 48/16 [2014-05-10 20:56:08] Stratum connection to pool 3 interrupted [2014-05-10 20:56:08] Pool 3 http://stratum.mining.eligius.st:3334 not responding! [2014-05-10 20:56:08] Switching to pool 1 stratum+tcp://mint.bitminter.com:3333 [2014-05-10 20:56:08] pool 1 JSON stratum auth failed: [ 20, "Unknown method 'mining.get_transactions'", null ] [2014-05-10 20:56:08] Pool 1 stratum+tcp://mint.bitminter.com:3333 not responding! [2014-05-10 20:56:08] Switching to pool 2 stratum+tcp://stratum.mining.eligius.st:3334 [2014-05-10 20:56:08] pool 1 JSON stratum auth failed: [ 20, "Unknown method 'mining.get_transactions'", null ] [2014-05-10 20:56:31] Pool 2 stratum+tcp://stratum.mining.eligius.st:3334 not responding! [2014-05-10 20:56:39] Pool 1 stratum+tcp://mint.bitminter.com:3333 alive, testing stability [2014-05-10 20:56:46] Switching to pool 1 stratum+tcp://mint.bitminter.com:3333 [2014-05-10 21:06:14] Stratum from pool 1 detected new block [2014-05-10 21:17:22] Stratum from pool 1 detected new block [2014-05-10 21:35:19] Stratum from pool 1 detected new block [2014-05-10 21:36:36] Stratum from pool 1 detected new block [2014-05-10 21:46:19] Stratum from pool 1 detected new block [2014-05-10 21:59:46] Stratum from pool 1 detected new block [2014-05-10 22:07:13] Stratum from pool 1 detected new block
for the record - I have the following pools: 0,2,3 - eligius, 1 - bitminter this was when running build: 3177195928193c7f744eee45885a3c3e1f8df49e-win32-gradual but it's been happening for a while (maybe last 1-2 months) Am I doing something possibly wrong? Or in the alternative - which debug logs/options should I turn on to get more details for further troubleshooting? Try updating from git. I believe I just fixed this earlier tonight.
|
|
|
|
leptar
Member
Offline
Activity: 91
Merit: 10
|
|
May 11, 2014, 06:20:19 PM |
|
With BFGminer in win7 how can i see the associated devices assigned com ports? I found the info 3 months ago and bookmarked it but that link is dead... This was done via the command line.. TIA.
|
|
|
|
Luke-Jr (OP)
Legendary
Offline
Activity: 2576
Merit: 1186
|
|
May 11, 2014, 06:24:41 PM |
|
With BFGminer in win7 how can i see the associated devices assigned com ports? I found the info 3 months ago and bookmarked it but that link is dead... This was done via the command line.. TIA. bfgminer-rpc devdetails maybe?
|
|
|
|
leptar
Member
Offline
Activity: 91
Merit: 10
|
|
May 12, 2014, 12:16:33 AM |
|
Thanks, i got a socket connection refused...
Last time i did it i had to prt it to a file because it just showed me the ant's amu0-amu51 and their assigned com ports then it just exited..
I have a couple of ants that are acting up.. i swapped them out on the hub and it's the port not the ant, so i'm thinking it might be a conflict between ports.
I want to assign it a different port to make sure..
thanks again.
|
|
|
|
nwoolls
|
|
May 12, 2014, 07:43:04 PM |
|
If anyone has access to a G-Blade please PM me. I'd like to test driver support for it. Thanks!
Bueller....Bueller....
|
MultiMiner: Any Miner, Any Where, on Any Device | Xgminer: Mine with popular miners on Mac OS X
|
|
|
BRADLEYPLOOF
|
|
May 12, 2014, 07:52:52 PM |
|
If anyone has access to a G-Blade please PM me. I'd like to test driver support for it. Thanks!
Bueller....Bueller.... +1EDIT: If you buy me one, I'll let you use it for a while... Edit2: Wont' they give you one if you're a Dev? *shakes fist*
|
|
|
|
nwoolls
|
|
May 12, 2014, 08:01:18 PM |
|
If anyone has access to a G-Blade please PM me. I'd like to test driver support for it. Thanks!
Bueller....Bueller.... +1EDIT: If you buy me one, I'll let you use it for a while... Edit2: Wont' they give you one if you're a Dev? *shakes fist* The HW folks that I have relationships with aren't selling them anymore. It seems to me that the GS chips are being discounted and replaced by newer generations. I may reach out and see if I can get one but I'm not sure who is still reselling them.
|
MultiMiner: Any Miner, Any Where, on Any Device | Xgminer: Mine with popular miners on Mac OS X
|
|
|
FunkiMonki
Newbie
Offline
Activity: 6
Merit: 0
|
|
May 12, 2014, 08:47:17 PM |
|
I'd like to use BFGMiner as the stratum proxy for all my hardware - I'd like to reduce all the machines separately connecting to the internet - and see if it improves my accepteds/lost/dupes/stales Antminer x2 & Avalon x1 connects to the machine running the proxy ok - though it doesn't seem to show the full hashrate on the proxy machine. My old Raspberry Pi rig runnings ASICs of a USB hub seems to have an issue Whenever I point it at [Proxy Machine]192.168.2.x:3333 just like with the other H/W it produces one of the following errors and crashes out on the RaspberryPi: SSM: Not using a stratum server upstream! SSM: Failed to subdivide upstream stratum notify! I've recompiled BFGMiner 3.10.0 with all the options as far as I'm aware on the on the RPi. I've even ensured the API interface it active on all machines: bfgminer --scan noauto --stratum-port 3333 -o stratum+tcp://[pool] -u [user] -p x --api-listen --api-port 4028 --api-allow W:127.0.0.1, --log 5 --scan opencl:noauto Not sure where else to look - as searching the internet just takes me to the github source documents What options have I missed? The only related thing I did find was about 'extranonces2 space' which I don't understand. Any suggestions would be lovely!
|
|
|
|
vabchgent
|
|
May 13, 2014, 01:16:33 AM |
|
If anyone has access to a G-Blade please PM me. I'd like to test driver support for it. Thanks!
Bueller....Bueller.... +1EDIT: If you buy me one, I'll let you use it for a while... Edit2: Wont' they give you one if you're a Dev? *shakes fist* The HW folks that I have relationships with aren't selling them anymore. It seems to me that the GS chips are being discounted and replaced by newer generations. I may reach out and see if I can get one but I'm not sure who is still reselling them. gaw miners http://www.gawminers.com/and Zoomhash http://zoomhash.com/
|
|
|
|
Oldminer
Legendary
Offline
Activity: 1022
Merit: 1001
|
|
May 13, 2014, 03:40:43 AM Last edit: May 13, 2014, 06:11:19 AM by Oldminer |
|
Does anyone know the command arguments to use with Multiminer to mine with both gridseed & GPU? I've tried all sorts of different combinations and can only seem to get one or the other mining ie both are detected but only the GPU or Gridseeds mine
|
|
|
|
wolfey2014
|
|
May 16, 2014, 06:53:04 PM Last edit: May 16, 2014, 10:07:18 PM by wolfey2014 |
|
some update 2014 miner bug fixed
download
LINK REMOVED
CAUTION!!!!BEWARE!!!!DO NOT DOWNLOAD!!!! Bmining is a brand new NEWB! CAUTION! Who is the author of this software 'upgrade'? Says corrects minor bug....Really? Maybe it causes a HUGE BUG! BEWARE! The member is a newb....CAUTION! DO NOT CLICK ANY LINKS FROM bmining! IT is attempting to spread MALWARE OR VIRUSES!
|
I Modify Miners Professionally! PM me for details!
|
|
|
Luke-Jr (OP)
Legendary
Offline
Activity: 2576
Merit: 1186
|
|
May 18, 2014, 03:55:35 AM |
|
however, i noticed: out of the 64 chips total, 64 were recognized however only 60 were hashing/returning nonces. to rule out hardware state, i power cycled and tried again. same thing. to see if the Gen 2 detection was the culprit or something in between i did the following. git clone https://github.com/luke-jr/bfgminer bfgminer-nxt-2 && cd bfgminer-nxt-2
git checkout a355ac63b5671abd7a373151b683cd4e6be9ae2d //known solid, been running for months
git cherry-pick 9d647767620ef121452db7f1ebf1d6be524ea4d8 //added Rev.2 detection/
git cherry-pick 61a2b9aacb4ff779d8c5cd29c9eab3e346aeb8be //fixed hashrate reporting for Rev.2 chips
./autogen.sh
CFLAGS="-O2" ./configure --without-libusb --without-hidapi
make -j2
sudo ./bfgminer -o stratum.btcguild.com:3333 -O user:pass --set BFY:osc6_bits=55 --set BFY:baud=500000 this resulted in a version of my previous stable build with the addition of the Rev.2 detection and reporting. Lo and behold the same 4 chips that were not returning results before, were NOT returning results with this modified version of my stable. Can you pastebin a debuglog?
|
|
|
|
Taugeran
|
|
May 18, 2014, 04:40:21 AM |
|
however, i noticed: out of the 64 chips total, 64 were recognized however only 60 were hashing/returning nonces. to rule out hardware state, i power cycled and tried again. same thing. to see if the Gen 2 detection was the culprit or something in between i did the following. git clone https://github.com/luke-jr/bfgminer bfgminer-nxt-2 && cd bfgminer-nxt-2
git checkout a355ac63b5671abd7a373151b683cd4e6be9ae2d //known solid, been running for months
git cherry-pick 9d647767620ef121452db7f1ebf1d6be524ea4d8 //added Rev.2 detection/
git cherry-pick 61a2b9aacb4ff779d8c5cd29c9eab3e346aeb8be //fixed hashrate reporting for Rev.2 chips
./autogen.sh
CFLAGS="-O2" ./configure --without-libusb --without-hidapi
make -j2
sudo ./bfgminer -o stratum.btcguild.com:3333 -O user:pass --set BFY:osc6_bits=55 --set BFY:baud=500000 this resulted in a version of my previous stable build with the addition of the Rev.2 detection and reporting. Lo and behold the same 4 chips that were not returning results before, were NOT returning results with this modified version of my stable. Can you pastebin a debuglog? Yes gimme a little while.
|
Bitfury HW & Habañero : 1.625Th/s tips/Donations: 1NoS89H3Mr6U5CmP4VwWzU2318JEMxHL1 Come join Coinbase
|
|
|
informer
|
|
May 18, 2014, 02:23:27 PM |
|
So, I caught steal on some ASIC Blades V2 and thought I'd try my hand at mining. I've been able to successfully setup mining_proxy on BTCGuild but at the encouragement of some new friends I've met in the community I thought I would try some other mining platforms and was told bfgminer was the way to go. After a day of research I finally discovered that although bfgminer supports ASIC Blades, it doesn't do so natively in the downloads I found, and needs to be compiled. So, naturally I start working from the windows-build.txt being on a Win64 platform. Everything was going fine all the way down through every single step. Except for the last one. "./compile". Each time I removed every single download, reinstalled everything and walks through the steps, I would get stuck at:
checking whether HASH_ITER is declared... no configure: error: Could not find HASH_ITER - please install uthash-dev 1.9.4+
Ok, so I backed up the latest version of utash-dev in the \include folder and finally found a 1.9.4 version and exported it there. still, no joy. Has anyone else come across this? If so, were you able to overcome the issue and how did you do it?
|
|
|
|
BCwinning
|
|
May 18, 2014, 03:43:37 PM |
|
I have 2 antminer u2's I'm running but I would like to clock each one individually and set the parameters in the conf file. I'm sure my syntax is wrong and hope someone can steer me right. A few pages back a poster shows some examples of it on linux which is what I'm going off of. I'm on windows but it shouldn't matter if I get the syntax correct? Default working config file shows "scan" : [ "amu:all" ], "set-device" : [ "antminer:clock=x0A01" So I edited it to reflect this "scan" : [ "amu:\\\\.\\COM5" ], "set-device" : [ "antminer:clock=x0A01" works like it should, it launches and runs the device on com5 at the speed specified. The two issues I'm having is adding the 2nd device under scan seems to break and attempting to change the syntax under set device breaks it no matter how I edit it. The syntax I was attempting "antminer:\\\\.\\COM5:clock=x0A01" So basically I edited the conf file to look like this and it won't run... "scan" : [ "amu:\\\\.\\COM5" "amu:\\\\.\\COM7" ], "set-device" : [ "antminer:\\\\.\\COM5:clock=x0A01" "antminer:\\\\.\\COM7:clock=x0B81" I'm sure it's stupid like extra quotations or something..
|
The New World Order thanks you for your support of Bitcoin and encourages your continuing support so that they may track your expenditures easier.
|
|
|
Taugeran
|
|
May 18, 2014, 05:12:15 PM |
|
I have 2 antminer u2's I'm running but I would like to clock each one individually and set the parameters in the conf file. I'm sure my syntax is wrong and hope someone can steer me right. A few pages back a poster shows some examples of it on linux which is what I'm going off of. I'm on windows but it shouldn't matter if I get the syntax correct? Default working config file shows "scan" : [ "amu:all" ], "set-device" : [ "antminer:clock=x0A01" So I edited it to reflect this "scan" : [ "amu:\\\\.\\COM5" ], "set-device" : [ "antminer:clock=x0A01" works like it should, it launches and runs the device on com5 at the speed specified. The two issues I'm having is adding the 2nd device under scan seems to break and attempting to change the syntax under set device breaks it no matter how I edit it. The syntax I was attempting "antminer:\\\\.\\COM5:clock=x0A01" So basically I edited the conf file to look like this and it won't run... "scan" : [ "amu:\\\\.\\COM5" "amu:\\\\.\\COM7" ], "set-device" : [ "antminer:\\\\.\\COM5:clock=x0A01" "antminer:\\\\.\\COM7:clock=x0B81" I'm sure it's stupid like extra quotations or something.. Set device device specific settings should be: antminer@\\\\.\\COM5:clock=
|
Bitfury HW & Habañero : 1.625Th/s tips/Donations: 1NoS89H3Mr6U5CmP4VwWzU2318JEMxHL1 Come join Coinbase
|
|
|
Mudbankkeith
|
|
May 18, 2014, 05:39:55 PM |
|
I have 2 antminer u2's I'm running but I would like to clock each one individually and set the parameters in the conf file. I'm sure my syntax is wrong and hope someone can steer me right. A few pages back a poster shows some examples of it on linux which is what I'm going off of. I'm on windows but it shouldn't matter if I get the syntax correct? Default working config file shows "scan" : [ "amu:all" ], "set-device" : [ "antminer:clock=x0A01" So I edited it to reflect this "scan" : [ "amu:\\\\.\\COM5" ], "set-device" : [ "antminer:clock=x0A01" works like it should, it launches and runs the device on com5 at the speed specified. The two issues I'm having is adding the 2nd device under scan seems to break and attempting to change the syntax under set device breaks it no matter how I edit it. The syntax I was attempting "antminer:\\\\.\\COM5:clock=x0A01" So basically I edited the conf file to look like this and it won't run... "scan" : [ "amu:\\\\.\\COM5" "amu:\\\\.\\COM7" ], "set-device" : [ "antminer:\\\\.\\COM5:clock=x0A01" "antminer:\\\\.\\COM7:clock=x0B81" I'm sure it's stupid like extra quotations or something.. Set device device specific settings should be: antminer@\\\\.\\COM5:clock= For windows its just as easy to forget the config files, then just use two separate batch files plug in first stick:- bfgminer.exe --set-device antminer:clock=x0A01 --icarus-options 115200:2:2 -o http://stratum.bitcoin.cz:3333 -O worker:password -S antminer:all then plug in second stick:- bfgminer.exe --set-device antminer:clock=x0981 --icarus-options 115200:2:2 -o http://stratum.bitcoin.cz:3333 -O worker:password -S antminer:all etc...... x0A01 for 2.1Gh x0981 for 2.0Gh x0901 for 1.9Gh
|
BTc donations welcome:- 13c2KuzWCaWFTXF171Zn1HrKhMYARPKv97
|
|
|
Luke-Jr (OP)
Legendary
Offline
Activity: 2576
Merit: 1186
|
|
May 18, 2014, 09:19:24 PM |
|
I caught steal on some ASIC Blades V2... I don't think the Block Erupter Blades even pay for electricity anymore? :p After a day of research I finally discovered that although bfgminer supports ASIC Blades, it doesn't do so natively in the downloads I found, and needs to be compiled. Win32 version does support it. There is currently no way to build a Win64 version with support, due to limitations of libmicrohttpd. So, naturally I start working from the windows-build.txt being on a Win64 platform. Everything was going fine all the way down through every single step. Except for the last one. "./compile". Each time I removed every single download, reinstalled everything and walks through the steps, I would get stuck at:
checking whether HASH_ITER is declared... no configure: error: Could not find HASH_ITER - please install uthash-dev 1.9.4+
Ok, so I backed up the latest version of utash-dev in the \include folder and finally found a 1.9.4 version and exported it there. still, no joy. Has anyone else come across this? If so, were you able to overcome the issue and how did you do it? Figure out where your uthash.h file is, and try ./configure CFLAGS='-I C:\path\with\uthash.h\inside\it'
|
|
|
|
Hawkix
|
|
May 18, 2014, 10:03:54 PM |
|
Possible BUG:
Mining solo to bitcoind via GBT and having additional STRATUM pool for new block notifications does not work. The stratum thread is closed very soon with "Pool 1: Connection not needed, suspending" message.
|
|
|
|
|