Turned out to be nothing to do with your code.
While I was installing a larger water cooling system, I also took the GPU cards out to dust, and when I re-installed them, I managed to swap their positions (accidently). For what ever reason, BFGminer picks them both up immediately, AND I am getting better performance in all OpenCL tools now. I'm qualifying this to hardware being picky.
Thanks for the help.
Topic: BFGMiner 5.5.0: CPU/GPU/FPGA/ASIC mining software, GBT+Stratum, RPC, Linux/Win64 - page 50. (Read 834507 times)
March 13, 2015, 04:48:57 PM
March 13, 2015, 10:04:10 AM
Having an odd issue since I upgraded to 5.1.0, but some times BFGminer only sees one GPU/card. No other application has this problem, even other OpenCL tools (e.g. video coders) or games in CrossfireX. I can't even seem to manage to forcibly get it to see the other.
System is on a 990FX chipset, two R9 280X cards, on Windows 8.1 Pro, with scrypt GPU mining and GPU auto-detect at the command line. No, this issue doesn't happen in Ubuntu, but this machine has other duties via Windows that need the CPU overnight, which is also when I mine.
Upgraded from what? 5.0?System is on a 990FX chipset, two R9 280X cards, on Windows 8.1 Pro, with scrypt GPU mining and GPU auto-detect at the command line. No, this issue doesn't happen in Ubuntu, but this machine has other duties via Windows that need the CPU overnight, which is also when I mine.
Can you bisect the issue?
http://luke.dashjr.org/tmp/code/webisect/webisect.php
Enter something unique for session name, then put in the two versions (formatted as in the example) and follow instructions.
March 12, 2015, 10:44:10 PM
Having an odd issue since I upgraded to 5.1.0, but some times BFGminer only sees one GPU/card. No other application has this problem, even other OpenCL tools (e.g. video coders) or games in CrossfireX. I can't even seem to manage to forcibly get it to see the other.
System is on a 990FX chipset, two R9 280X cards, on Windows 8.1 Pro, with scrypt GPU mining and GPU auto-detect at the command line. No, this issue doesn't happen in Ubuntu, but this machine has other duties via Windows that need the CPU overnight, which is also when I mine.
System is on a 990FX chipset, two R9 280X cards, on Windows 8.1 Pro, with scrypt GPU mining and GPU auto-detect at the command line. No, this issue doesn't happen in Ubuntu, but this machine has other duties via Windows that need the CPU overnight, which is also when I mine.
March 11, 2015, 10:30:03 AM
AntMiner U3 support needs some pretty major improvements to the "icarus" driver that serves as the base for many FPGA and ASIC devices.
If you can help test (I don't have all the devices!), please do. List of stuff that needs testing is on https://github.com/luke-jr/bfgminer/pull/603
Windows binaries are available from http://luke.dashjr.org/tmp/code/webisect/webisect.php?dobuild=icarus_ms
If you can help test (I don't have all the devices!), please do. List of stuff that needs testing is on https://github.com/luke-jr/bfgminer/pull/603
Windows binaries are available from http://luke.dashjr.org/tmp/code/webisect/webisect.php?dobuild=icarus_ms
By my read of that pull, have you been successful getting the U3 to work on linux?
Thanks.
March 10, 2015, 09:00:54 PM
AntMiner U3 support needs some pretty major improvements to the "icarus" driver that serves as the base for many FPGA and ASIC devices.
If you can help test (I don't have all the devices!), please do. List of stuff that needs testing is on https://github.com/luke-jr/bfgminer/pull/603
Windows binaries are available from http://luke.dashjr.org/tmp/code/webisect/webisect.php?dobuild=icarus_ms
If you can help test (I don't have all the devices!), please do. List of stuff that needs testing is on https://github.com/luke-jr/bfgminer/pull/603
Windows binaries are available from http://luke.dashjr.org/tmp/code/webisect/webisect.php?dobuild=icarus_ms
By my read of that pull, have you been successful getting the U3 to work on linux?
March 10, 2015, 08:45:11 PM
AntMiner U3 support needs some pretty major improvements to the "icarus" driver that serves as the base for many FPGA and ASIC devices.
If you can help test (I don't have all the devices!), please do. List of stuff that needs testing is on https://github.com/luke-jr/bfgminer/pull/603
Windows binaries are available from http://luke.dashjr.org/tmp/code/webisect/webisect.php?dobuild=icarus_ms
If you can help test (I don't have all the devices!), please do. List of stuff that needs testing is on https://github.com/luke-jr/bfgminer/pull/603
Windows binaries are available from http://luke.dashjr.org/tmp/code/webisect/webisect.php?dobuild=icarus_ms
By my read of that pull, have you been successful getting the U3 to work on linux?
March 10, 2015, 12:23:55 PM
The #allblocks keyword makes it submit all blocks locally, no matter what pool it was found for.
This helps the block propagate faster and prevents the pool from performing the selfish mining attack.
thanks This helps the block propagate faster and prevents the pool from performing the selfish mining attack.
March 10, 2015, 08:27:33 AM
Why when I solo mine am I connected to two pools:
I'm using the code you mentioned on the BFGMiner GitHub page (with modifications specific to me, of course):
What is the "#allblocks" pool?
When possible, BFGMiner automatically configures itself for solo mining.Code:
0: Enabled GBT Quota 1 Pool 0: http://localhost:8332 User:bitcoinrpc
1: Enabled GBT Quota 0 Pool 1: http://localhost:8332/#allblocks User:bitcoinrpc
I'm using the code you mentioned on the BFGMiner GitHub page (with modifications specific to me, of course):
Code:
bfgminer -o http://localhost:8332 -u username -p password \
--generate-to 1QATWksNFGeUJCWBrN4g6hGM178Lovm7Wh \
--coinbase-sig "rig1: This is Joe's block!"
What is the "#allblocks" pool?
The #allblocks keyword makes it submit all blocks locally, no matter what pool it was found for.
This helps the block propagate faster and prevents the pool from performing the selfish mining attack.
March 10, 2015, 12:45:11 AM
Why when I solo mine am I connected to two pools:
I'm using the code you mentioned on the BFGMiner GitHub page (with modifications specific to me, of course):
What is the "#allblocks" pool?
Code:
0: Enabled GBT Quota 1 Pool 0: http://localhost:8332 User:bitcoinrpc
1: Enabled GBT Quota 0 Pool 1: http://localhost:8332/#allblocks User:bitcoinrpc
I'm using the code you mentioned on the BFGMiner GitHub page (with modifications specific to me, of course):
Code:
bfgminer -o http://localhost:8332 -u username -p password \
--generate-to 1QATWksNFGeUJCWBrN4g6hGM178Lovm7Wh \
--coinbase-sig "rig1: This is Joe's block!"
What is the "#allblocks" pool?
March 09, 2015, 03:22:27 PM
--request-diff does not appear to function for me, where has been 1.0, 2.0, 2, 6 in my efforts to get it working. No matter what value I input the pool starts me at 1k difficulty. Would it depend on the pool I'm connecting to whether or not that command gets accepted? The difficulty auto-adjusts down after several minutes, but I would like to avoid that period of auto adjustment. Using a single nanofury usb stick. Thanks.
It's just a request. Pools can just ignore it (and most do). 
March 09, 2015, 02:50:45 PM
--request-diff does not appear to function for me, where has been 1.0, 2.0, 2, 6 in my efforts to get it working. No matter what value I input the pool starts me at 1k difficulty. Would it depend on the pool I'm connecting to whether or not that command gets accepted? The difficulty auto-adjusts down after several minutes, but I would like to avoid that period of auto adjustment. Using a single nanofury usb stick. Thanks.
March 06, 2015, 02:44:27 AM
5.1 update problem
HTTP request failed: Protocol "stratum+tcp" not supported or disabled in libcurl
easyminer running BFL machine.
This message is normal (libcurl does not support stratum, so BFG uses its own).HTTP request failed: Protocol "stratum+tcp" not supported or disabled in libcurl
easyminer running BFL machine.
Is there an actual problem?
Will not connect after 5.1 update
Will not connect to ghash pool
Been running with no hitches on the same settings for over a year now
Updated this morning and get this error code , wont connect.
bfgminer --debuglog --log-file debug.log
Thank you Luke,
The problem seems to have miraculously subsided.
Left the miner overnight on retry at 5 minute intervals and by morning it had reconnected and was hashing......
?!?
So all good for now and I will def do a log for you if it happens again
Many thanks.
March 05, 2015, 11:48:51 AM
BTC Guild just posted its under attack as well.
March 05, 2015, 11:44:10 AM
Ghash is possibly under ddos attack since yesterday.
Good point...Eligius received notification that we will be constantly under DDoS as well (although wizkid057 has things setup well enough that we don't even really notice).
March 05, 2015, 11:27:17 AM
Ghash is possibly under ddos attack since yesterday.
March 05, 2015, 10:36:23 AM
5.1 update problem
HTTP request failed: Protocol "stratum+tcp" not supported or disabled in libcurl
easyminer running BFL machine.
This message is normal (libcurl does not support stratum, so BFG uses its own).HTTP request failed: Protocol "stratum+tcp" not supported or disabled in libcurl
easyminer running BFL machine.
Is there an actual problem?
Will not connect after 5.1 update
Will not connect to ghash pool
Been running with no hitches on the same settings for over a year now
Updated this morning and get this error code , wont connect.
bfgminer --debuglog --log-file debug.log
March 05, 2015, 10:14:10 AM
5.1 update problem
HTTP request failed: Protocol "stratum+tcp" not supported or disabled in libcurl
easyminer running BFL machine.
This message is normal (libcurl does not support stratum, so BFG uses its own).HTTP request failed: Protocol "stratum+tcp" not supported or disabled in libcurl
easyminer running BFL machine.
Is there an actual problem?
Will not connect after 5.1 update
Will not connect to ghash pool
Been running with no hitches on the same settings for over a year now
Updated this morning and get this error code , wont connect.
March 05, 2015, 08:45:41 AM
5.1 update problem
HTTP request failed: Protocol "stratum+tcp" not supported or disabled in libcurl
easyminer running BFL machine.
This message is normal (libcurl does not support stratum, so BFG uses its own).HTTP request failed: Protocol "stratum+tcp" not supported or disabled in libcurl
easyminer running BFL machine.
Is there an actual problem?
March 05, 2015, 08:37:25 AM
5.1 update problem
HTTP request failed: Protocol "stratum+tcp" not supported or disabled in libcurl
easyminer running BFL machine.
HTTP request failed: Protocol "stratum+tcp" not supported or disabled in libcurl
easyminer running BFL machine.
March 03, 2015, 10:35:27 AM
Many thanks. May I ask what is the quick test to know that my system is practically useful? I mean how fast it should be as I read in the CPU README, you said it not worth it to try. As I am new to bitcoin miner, please advice what I would expect and should do/do not. Thanks, John.
Bitcoin mining with a CPU, no matter what kind of CPU, will never be practically useful for more than testing. Jump to: