I tried to solo mine a dead scrypt coin with low difficulty. I was the only miner and in few seconds I found 13 blocks, I can see them in the wallet. But I see that bfgminer reports, it detected 27 new blocks on the network. That is a bug in bfgminer, only 14 new blocks were there (13 blocks solved and one, the last one, unsolved). New blocks (NB:) and accepted blocks were seen in ncurses screen and I can see them in final report:
[2014-08-16 21:25:40] Runtime: 0 hrs : 0 mins : 44 secs
[2014-08-16 21:25:40] Average hashrate: 1.5 Megahash/s
[2014-08-16 21:25:40] Solved blocks: 13
[2014-08-16 21:25:40] Best share difficulty: 77m
[2014-08-16 21:25:40] Share submissions: 13
[2014-08-16 21:25:40] Accepted shares: 13
[2014-08-16 21:25:40] Rejected shares: 0 + 0 stale (0.00%)
[2014-08-16 21:25:40] Accepted difficulty shares: 0
[2014-08-16 21:25:40] Rejected difficulty shares: 0
[2014-08-16 21:25:40] Hardware errors: 0
[2014-08-16 21:25:40] Network transfer: 621.0 / 262.7 kB ( 15.5 / 6.6 kB/s)
[2014-08-16 21:25:40] Efficiency (accepted shares * difficulty / 2 KB): 0.00
[2014-08-16 21:25:40] Utility (accepted shares / min): 19.48/min
[2014-08-16 21:25:40] Unable to get work from server occasions: 0
[2014-08-16 21:25:40] Work items generated locally: 0
[2014-08-16 21:25:40] Submitting work remotely delay occasions: 0
[2014-08-16 21:25:40] New blocks detected on network: 27
And these are messages during mining:
[2014-08-16 21:37:11] Found block for pool 0!
[2014-08-16 21:37:11] Accepted 01c69dd4 ZUS 0bi Diff 2m/2m
[2014-08-16 21:37:11] New block detected on network
ZUS0 | 20s: 0.20 avg: 1.44 u: 0.51 Mh/s | A:1 R:0+0(none) HW:0/none
[2014-08-16 21:37:11] New block detected on network
20s: 0.49 avg: 1.27 u: 0.45 Mh/s | A:1 R:0+0(none) HW:0/none
[2014-08-16 21:37:14] Found block for pool 0!
[2014-08-16 21:37:14] Accepted 011f1b60 ZUS 0as Diff 3m/2m
[2014-08-16 21:37:14] New block detected on network
ZUS0 | 20s: 0.20 avg: 1.22 u: 0.86 Mh/s | A:2 R:0+0(none) HW:0/none
[2014-08-16 21:37:14] New block detected on network
[2014-08-16 21:37:17] Found block for pool 0!
[2014-08-16 21:37:17] Accepted 018790f8 ZUS 0be Diff 2m/2m
[2014-08-16 21:37:17] New block detected on network
ZUS0 | 20s: 0.31 avg: 1.44 u: 1.12 Mh/s | A:3 R:0+0(none) HW:0/none
[2014-08-16 21:37:17] New block detected on network
|
|
|
|
Gentlemen, I can remotely crash bfgminer, core dump is 100% repeatable: $ printf 'stats' | nc bfgminer 4028 or $ printf '{"command":"stats"}' | nc bfgminer 4028bfgminer is the latest from GIT running at older Ubuntu host and it is mining some SCRYPT coin with one ZEUS miner connected to USB port. Other commands I tried work OK, like this one: $ printf 'summary' | nc bfgminer 4028 I found this problem when I tried to monitor this host... Some debug example:
[2014-08-16 16:17:01] ZUS 0aa: Got work 139 from get queue to get work for thread 0
[2014-08-16 16:17:01] PROOF OF WORK RESULT: true (yay!!!)
[2014-08-16 16:17:01] Accepted 00304fa1 ZUS 0as Diff 20m/3m
[2014-08-16 16:17:09] API: connection from 10.11.10.101 - Accepted
Segmentation fault (core dumped) command: (5) 'stats'
This is fast and dirty workaround, I know it is bad but it address crashes and I can use miner API: $ git diff -u api.c
diff --git a/api.c b/api.c
index 1bfd9bb..5aff5f3 100644
--- a/api.c
+++ b/api.c
@@ -3012,7 +3012,7 @@ static void minerstats(struct io_data *io_data, __maybe_unused SOCKETTYPE c
if (cgpu && cgpu->drv) {
if (cgpu->drv->get_api_stats)
- extra = cgpu->drv->get_api_stats(cgpu);
+ extra = NULL;
else
extra = NULL;
This condition is part of a loop, bfgminer crashes when index j is 1 and it points to zeusminer driver, some structure is not initialized. Loop is run 48 times (or 8 times when zeusminer:chips=1). My ZEUSMINER is Blizzard, it has 6 ASIC chips. I tried to add parameter --set-device zeusminer:chips=1 but it doesn't help... |
|
|
|
What's the "-s" in command line used for?
Thanks.
anyone can help on this?  Thank you. -s, --scantime=N upper bound on time spent scanning current work when long polling is unavailable, in seconds (default: 5) |
|
|
|
I want to report, that cpuminer found a block and I cannot see it in the "listtransactions" report... I mined Franko (FRK), GBT mode with address and no signature. I don't have cpuminer detail log but I have debug.log from frankod. cpuminer and server are running on the same PC. From the log file I have I assume it is some problem with frankod... cpuminer: [2014-05-25 16:54:33] 4 miner threads started, using 'scrypt' algorithm.
[2014-05-26 07:13:06] accepted: 1/1 (100.00%), 15.11 khash/s (yay!!!)
debug.log (frankod): (2014-05-26 07:12:58)
received block 4ab88852eb336e3a41b69deb2ef2839f67ef42fc3c91c99b818234aa590321f0
Difficulty Retarget - Kimoto Gravity Well
PastRateAdjustmentRatio = 0.914426
Before: 1d012d37 000000012d370000000000000000000000000000000000000000000000000000
After: 1d012d2c 000000012d2c5e4c2f497d0fd4dc657cc90a0638d3d2ecd9a1906b4b6c9bb015
Committing 1 changed transactions to coin database...
SetBestChain: new best=4ab88852eb336e3a41b69deb2ef2839f67ef42fc3c91c99b818234aa590321f0 height=741280 log2_work=51.204934 tx=866957 date=2014-05-26 05:12:58 progress=0.999998
ProcessBlock: ACCEPTED
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
ThreadRPCServer method=submitblock
Difficulty Retarget - Kimoto Gravity Well
PastRateAdjustmentRatio = 0.914426
Before: 1d012d37 000000012d370000000000000000000000000000000000000000000000000000
After: 1d012d2c 000000012d2c5e4c2f497d0fd4dc657cc90a0638d3d2ecd9a1906b4b6c9bb015
ProcessBlock: ACCEPTED
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
CreateNewBlock(): total size 1000
Difficulty Retarget - Kimoto Gravity Well
PastRateAdjustmentRatio = 0.919932
Before: 1d012d2c 000000012d2c0000000000000000000000000000000000000000000000000000
After: 1d012b8b 000000012b8b374f0329161f9add3c0ca4587e6b74f0329161f9add3c0ca4585
(2014-05-26 07:13:02)
received block b17f7ab98a1fe9739ddecba1fb992b61cc12ab8438390ee54d62bfddb99cbe6b
Difficulty Retarget - Kimoto Gravity Well
PastRateAdjustmentRatio = 0.919932
Before: 1d012d2c 000000012d2c0000000000000000000000000000000000000000000000000000
After: 1d012b8b 000000012b8b374f0329161f9add3c0ca4587e6b74f0329161f9add3c0ca4585
Committing 1 changed transactions to coin database...
SetBestChain: new best=b17f7ab98a1fe9739ddecba1fb992b61cc12ab8438390ee54d62bfddb99cbe6b height=741281 log2_work=51.204936 tx=866958 date=2014-05-26 05:13:02 progress=0.999992
ProcessBlock: ACCEPTED
Block founded by my cpuminer should be between blocks 741280 add 741281 but it is not there. I see ProcessBlock: ACCEPTED but block is missing and I cannot explain it... $ frankod getblockhash 741280
4ab88852eb336e3a41b69deb2ef2839f67ef42fc3c91c99b818234aa590321f0
$ frankod getblockhash 741281
b17f7ab98a1fe9739ddecba1fb992b61cc12ab8438390ee54d62bfddb99cbe6b
After this experience, I will mine with --no-gbt parameter... I found similar situation when block was really accepted. debug.log is different in this case, I see message Committing 1 changed transactions to coin database...: received getdata for: block 10718ea1b6085cd6dd23b885432299e2b6caca83f3ae31fc7899c90dd41cc7b2
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
ThreadRPCServer method=submitblock
Difficulty Retarget - Kimoto Gravity Well
PastRateAdjustmentRatio = 0.96709
Before: 1d013248 0000000132480000000000000000000000000000000000000000000000000000
After: 1d01319b 00000001319ba70336589c6b80db65bd2a63711babab573fca3edee7e2639b2b
AddToWallet 028ebced569d05b28f8fc4c79eaeb5753da593025b2fd8cccceba625faccef05 new
Committing 1 changed transactions to coin database...
SetBestChain: new best=5453e3528d550b8fd297cc6f3780b25a3aab3a97f3a5b6a8c2ab6d18a3cbe4b9 height=739480 log2_work=51.200899 tx=864616 date=2014-05-25 14:03:53 progress=0.999998
ProcessBlock: ACCEPTED
|
|
|
|
|
I found that Franko (FRK) coin works in GBT mode well.
I tried to mine with several cpuminers those were mining to the same address and had no signature configured and those miners were finding different blocks, I was not observing collisions. I still don't understand that signature feature...
|
|
|
|
I patched Powercoin with submitblock; I get the code from Noblecoin... I am not sure that the patch is perfect but it "works", I can mine in GBT mode. I see these problems now: 1) block is accepted but it is not assigned to address defined by cpuminer (listreceivedbyaddress reports 0.00) 2) block is added to total balance and it is visible in listtransactions 3) cpuminer reports this: [2014-05-24 20:38:13] accepted: 0/1 (0.00%), 4.24 khash/s (booooo)
And these are details: [2014-05-24 20:38:13] DEBUG: hash <= target
Hash: 0000011765198ac5ad42387fa26ced7b4ca049e17f6c2bef46f316a0379c5a06
Target: 000001d950000000000000000000000000000000000000000000000000000000
[2014-05-24 20:38:13] JSON protocol request:
{"method": "submitblock", "params": ["0100000007ee5bd17c4de91cf366b17a1f7972f6e7
b3554fb30d10df961e6a861601797373c351cf872223622531d84580ee236be2ff11016d9bfff875
5bacd4a1060fe514e7805350d9011ec0000112010100000001000000000000000000000000000000
0000000000000000000000000000000000ffffffff140318c9020f3536323663633765062f503253
482fffffffff0100286bee000000001976a91494049e424a5cdcfdb0bb3b07fee1abecfda382cc88
ac00000000"], "id":1}
* Re-using existing connection! (#0) with host testcoin
* Connected to testcoin (192.168.222.80) port 9863 (#0)
* Server auth using Basic with user 'PWC'
> POST / HTTP/1.1
Authorization: Basic UFdDOnJwY1BTTHBhc3M=
Host: testcoin:9863
Accept-Encoding: deflate, gzip
Content-Type: application/json
Content-Length: 423
User-Agent: cpuminer/2.4
X-Mining-Extensions: midstate
< HTTP/1.1 200 OK
< Date: Sat, 24 May 2014 18:39:02 +0000
< Connection: keep-alive
< Content-Length: 36
< Content-Type: application/json
< Server: powercoin-json-rpc/v0.6.3.0-unk-beta
<
* Connection #0 to host testcoin left intact
[2014-05-24 20:38:13] JSON protocol response:
{
"error": null,
"result": true,
"id": 1
}
[2014-05-24 20:38:13] accepted: 0/1 (0.00%), 4.24 khash/s (booooo)
Is there some explanation, why cpuminer reports 0/1 (0.00%) and not 1/1 (100.00%)?? |
|
|
|
Interesting... :-( Is it possible to test availability of submitblock method by a submit of random data after cpuminer start?
It is certainly possible, but it would be a bit pointless in my opinion. If a server provides a getblocktemplate method but no submitblock method, then it is violating the official specifications. I checked that Powercoin has really no code to support submitblock method. But it supports getblocktemplate method... XENcoin has newer code than Powercoin but it is similar case. Craftcoin is even newer but has similar problem... :-( BTW, the submitblock method is defined in source file src/bitcoinrpc.cpp. If it is not there, coin cannot accept GBT blocks. |
|
|
|
When cpuminer tries to submit GBT block, block is rejected with 404 error.
Apparently your daemon does not implement the submitblock method, even though it is part of the non-optional sections of BIP 22. As a matter of fact, I've mined several blocks on the Litecoin testnet, so I know that the GBT implementation of 2.4 is not (entirely) broken. Interesting... :-( Is it possible to test availability of submitblock method by a submit of random data after cpuminer start? |
|
|
|
I am sorry to write this but GBT submit doesn't work. I haven't found any new block from the time I run cpuminer 2.4. When I use "--no-gbt", blocks are found and accepted... I use powercoin ( https://github.com/Powercoin/Powercoin) to test it. Powercoin is dead coin with very low difficulty, good to test solo mining. Powercoin code was not updated for a while so it could be a source of problem but I assume code is good enough to replicate this problem. When cpuminer tries to submit GBT block, block is rejected with 404 error. [2014-05-24 10:42:20] HTTP request failed: The requested URL returned error: 404
[2014-05-24 10:42:20] submit_upstream_work json_rpc_call failed
I tried to mine with "--coinbase-addr=xx" and "--coinbase-addr=xx --coinbase-sig=yy" and blocks are rejected in both cases. When I mine with "--no-gbt", blocks are accepted [2014-05-24 11:02:52] accepted: 1/1 (100.00%), 4.83 khash/s (yay!!!)
Example of "rejected" GBT block: [2014-05-24 10:57:55] JSON protocol request:
{"method": "submitblock", "params": ["01000000e65ab64270079fbca476b71bfce63f647b
9fd6ad518606cac7fc1399f0b1602f8f6bd269a664a8b6b0c0db263ee954192316678c33d0c1f9a0
0ee00f1842204f317b805350d9011ea0000de5010100000001000000000000000000000000000000
0000000000000000000000000000000000ffffffff140305c9020f3564656162353063062f503253
482fffffffff0100286bee000000001976a914f650f1ee4beb5f988696abddb3150a9f4bfdb93288
ac00000000"], "id":1}
* Re-using existing connection! (#0) with host powerminer
* Connected to powerminer (54.87.211.179) port 9863 (#0)
* Server auth using Basic with user 'PWC'
> POST / HTTP/1.1
Authorization: Basic TU0uUFdDOjlKUVh1VFVjNmVrNzRGV2EyeUVYN1JIYzg1ckhEV0M3Wkp3bWpCdjdwU3Ni
Host: powerminer:9863
Accept-Encoding: deflate, gzip
Content-Type: application/json
Content-Length: 423
User-Agent: cpuminer/2.4
X-Mining-Extensions: midstate
* The requested URL returned error: 404
* Closing connection #0
|
|
|
|
New cpuminer added support for GBT. I try to test solo mining and I try to mine XNC ( https://github.com/xencoin/Xencoin) because difficulty is low. When I try to mine with bfgminer (and faster GPU), I finish with error --coinbase-addr: Invalid address. Addrress is correct, it is XNC address. I run something like this: $ bfgminer -V
bfgminer 3.99.0
$ bfgminer --scrypt -o http://10.11.12.13:4335 -O USER:PASSWORD --coinbase-addr XxCAD3sbkxLD8NMqx1gLaPNib819HHdfJ5
[2014-05-21 16:38:35] bfgminer: --coinbase-addr: Invalid address
I would like to play with --coinbase-sig but before that I have to find how to run bfgminer with coinbase-addr... I think there is some problem in bfgminer related to validation of coinbase address. As I recall, BFGMiner validates the coinbase address to be a well-formed BITCOIN address, so if you are mining an alt coin, solo mining with GBT won't work. I'm not sure how you could validate the payout address in a way that would work for all possible alt coins. cpuminer 2.4 solved address validation is some way. Address XxCAD3sbkxLD8NMqx1gLaPNib819HHdfJ5 is accepted and address was rejected when I tried to damage it (add/remove characters, change character). This command accepts address: $ minerd -V
cpuminer 2.4
built on May 21 2014
features: x86_64 SSE2 AVX AVX2 XOP
libcurl/7.26.0 OpenSSL/1.0.1e zlib/1.2.7 libidn/1.25 libssh2/1.4.2 librtmp/2.3
libjansson 2.3.1
$ minerd -a scrypt -t1 -o http://10.11.12.13:4335 -O USER:PASSWORD --coinbase-addr XxCAD3sbkxLD8NMqx1gLaPNib819HHdfJ5
[2014-05-21 17:04:21] 1 miner threads started, using 'scrypt' algorithm.
[2014-05-21 17:04:51] HTTP request failed: connect() timed out!
[2014-05-21 17:04:51] json_rpc_call failed, retry after 30 seconds
It failed, because login information is not correct. It works, tested with real parameters. To test address validation, it is not necessary to login.. |
|
|
|
New cpuminer added support for GBT. I try to test solo mining and I try to mine XNC ( https://github.com/xencoin/Xencoin) because difficulty is low. When I try to mine with bfgminer (and faster GPU), I finish with error --coinbase-addr: Invalid address. Addrress is correct, it is XNC address. I run something like this: $ bfgminer -V
bfgminer 3.99.0
$ bfgminer --scrypt -o http://10.11.12.13:4335 -O USER:PASSWORD --coinbase-addr XxCAD3sbkxLD8NMqx1gLaPNib819HHdfJ5
[2014-05-21 16:38:35] bfgminer: --coinbase-addr: Invalid address
I would like to play with --coinbase-sig but before that I have to find how to run bfgminer with coinbase-addr... I think there is some problem in bfgminer related to validation of coinbase address. |
|
|
|
|
I have the last point related to signatures that I miss. What signature is used in the case when it is not specified at cpuminer command line (--coinbase-sig parameter is missing)?
|
|
|
|
I don't see the problem. The "signature" can be any string you like. For example, if you have three miners, you can use signatures "1", "2" and "3". Signatures don't have to be globally unique, they just need to be different for all miners using the same payout address and mining at the same time.
OK, I don't like the idea to publish ballast that is not important but I can mine with parameters like these: --coinbase-addr=$CBADDRESS --coinbase-sig=$(hostname | sha256sum | cut -c1-64)
Anyway, is it technically possible to add a parameter that will work like signature but will be used only by miner and will not be published in the block-chain as signature? Block-chain, it is huge data structure replicated to millions of disks and every useless ballast there consumes significant disk space... |
|
|
|
I found bfgminer notice, that when several clients are connected to the same "coin server" and are mining to the same address, then parameter --coinbase-sig has to be added https://github.com/luke-jr/bfgminer, section SOLO MINING. Is it true that --coinbase-sig with unique parameter has to be added when more clients are connected with the same address? Yes. If you intend to have multiple miners mining solo to the same address, each of them should specify a different signature. Alternatively, you can specify a different address for each miner. Thank you for confirmation. That is bad news... I have a problem with a signature, it will be put to blockchain and everyone can see it. Is there other possibility to mine with the same address but without creating public message in the blockchain? Could be this addressed with new parameter that will work like signature but it will not be stored to blockchain? It will be just a local ID for mining client, I can use client hostname or IP address or something like that... |
|
|
|
Version 2.4- Support for getblocktemplate (GBT, BIP 22). With getwork deprecated and soon to be removed from Bitcoin, it was important to get this implemented, especially for testing solo mining. The getblocktemplate method is now used by default for protocol HTTP, but the miner should automatically switch to getwork if the newer method is not available. To force the miner to use getwork, a --no-gbt option is provided.
I found that for solo mining with cpuminer V1.4 I have to extend command line with parameter --no-gbt or --coinbase-addr otherwise it will not connect to the "coin server": [2014-05-21 13:05:06] No payout address provided
[2014-05-21 13:05:06] json_rpc_call failed, retry after 30 seconds
BTW, I think this is a cpuminer bug that it doesn't try to switch to getwork protocol and stays in never-ending loop waiting for a miracle... I added --coinbase-addr because I think it can address a problem with wallet design, where it is not possible to export default key (at least I failed to find how to do it) and I have to keep backup of binary wallet that is far from perfect. I test it at the moment, no block was found so far and that could be an indicator that something is wrong... Maybe I have only bad luck... I found bfgminer notice, that when several clients are connected to the same "coin server" and are mining to the same address, than parameter --coinbase-sig has to be added https://github.com/luke-jr/bfgminer, section SOLO MINING. Is it true that --coinbase-sig with unique parameter has to be added when more clients are connected with the same address?? So far, I just configured all my clients with the same --coinbase-addr address but I am not sure if this is good idea because it is possible that they work on the same units and my computing power is reduces compared to configuration with --no-gbt (operation mode of older cpuminer)... |
|
|
|
Thank you for the advice. I tried that and I really get some address and I dumped private key for that address. noblecoind getaccountaddress "" | xargs noblecoind dumpprivkey I imported the private key on different PC. And it proved that address is not correct because I cannot see mined block on second PC, mined coins were not transferred. Any other idea how to do paper backup of mined block (how to export private key for mined block)? How about this? http://bitcoin.stackexchange.com/questions/5685/how-do-i-list-all-of-my-addresses-in-namecoind I tried noblecoind listreceivedbyaddress 0 true before. Some address is printed but it is not the address to backup mined coins... I cannot see mined coins in the output from command "noblecoind listreceivedbyaddress 0 true", only coins those were received from a mining pool. |
|
|
|
Could someone advice how to create a backup of my private keys from NOBLE wallet? I tried to solo mine NOBLE coins and I was lucky, my PC really found a block after several days. I can see mined block with commands noblecoind getinfo
noblecoind listtransactions
I want to dump my private key for a paper backup with command dumpprivkey but that command needs an address. And I don't see the address in the output from listtransactions, generated block has only transactions ID, txid. I tried command gettransaction to find address but there is no address at the command reply. My other try was command listreceivedbyaddress but that commands doesn't list mined blocks at all, even when parameters are added (listreceivedbyaddress 1 true). Could someone help me to find a way to create a backup of mined block (marked as GENERATE in listtransaction output)? I know how to do a backup of coins received from the pool to address, that is easy (noblecoind dumpprivkey address). to see your wallet address use this: noblecoind getaccountaddress "" it will print your default wallet address, and then you can export your private key using dumpprivkey command Thank you for the advice. I tried that and I really get some address and I dumped private key for that address. noblecoind getaccountaddress "" | xargs noblecoind dumpprivkey I imported the private key on different PC. And it proved that address is not correct because I cannot see mined block on second PC, mined coins were not transferred. Any other idea how to do paper backup of mined block (how to export private key for mined block)? |
|
|
|
Could someone advice how to create a backup of my private keys from NOBLE wallet? I tried to solo mine NOBLE coins and I was lucky, my PC really found a block after several days. I can see mined block with commands noblecoind getinfo
noblecoind listtransactions
I want to dump my private key for a paper backup with command dumpprivkey but that command needs an address. And I don't see the address in the output from listtransactions, generated block has only transactions ID, txid. I tried command gettransaction to find address but there is no address at the command reply. My other try was command listreceivedbyaddress but that commands doesn't list mined blocks at all, even when parameters are added (listreceivedbyaddress 1 true). Could someone help me to find a way to create a backup of mined block (marked as GENERATE in listtransaction output)? I know how to do a backup of coins received from the pool to address, that is easy (noblecoind dumpprivkey address). |
|
|
|
|
There are several coins those are not updated at CoinChoose statistics that means coin clients are not synchronized with the current block chains (the number is the last block reported by CoinChoose):
ANC 134939
EXC 21951
GDC 316779
GLC 259584
NAN 0
NRB 109501
ORB 418665
SPT 78722
XNC 262966
|
|
|
|
Is there an easy way to replug AntMiner U1 device in bfgminer? New cgminer introduced a menu to work with broken USB devices. From time to time, U1 device dies, it is not mining and it is not dead, like in this example, AMU 3 device was mining for some time at 2GHps but it is not mining for a while (or mining at low hashrate): 4 | 8.35/ 8.33/ 6.61Gh/s | A:3492 R:1+0(.03%) HW:0/none
--------------------------------------------------------------------------------
AMU 0: | 2.06/ 2.06/ 1.99Gh/s | A:1015 R:0+0(none) HW:0/none
AMU 1: | 2.07/ 2.06/ 2.01Gh/s | A:1084 R:1+0(.09%) HW:0/none
AMU 2: | 2.06/ 2.06/ 1.99Gh/s | A:1081 R:0+0(none) HW:0/none
AMU 3: | 2.10/ 2.14/ 0.62Gh/s | A: 314 R:0+0(none) HW:0/none
--------------------------------------------------------------------------------
I am not sure what is a problem but devices were running at 2GHps for several days but they make trouble today... ;-) I know, I can restart bfgminer, it will fix the problem. That's odd, BFGMiner's watchdog should automatically restart it in this case... Any idea what's going on that stops it? I guess the device runs at edge of electrical or thermal limits. You see 4 devices in the rig, and one of them is the worst one. The situation illustrates what happens when the worst device "fails". AMU3 device is not completely dead but it runs with low hashrate. I can fix this situation when I quit bfgminer and start it again. After restart, all devices were mining at 2GHps for a while but the AMU3 device switched to slower mode again. I fixed that by decreasing hashrate of the whole rig from 2000 to 1950 MHps... |
|
|
|
|
Show Posts
