Topic: [ANN] ccminer 2.3 - opensource - GPL (tpruvot) - page 158. (Read 500112 times)
I have 5 gt750 ti , they were sleeping for 8 months , cause i was moving to another house, but now are ready for work. Anything that is worth to mine or it is a lost cause now.
that look like your card memory was used... ive seen that with cudaminer... sometimes you need to restart it more than once to get all the memory available.
i suggest using autotune only after a clean boot... and only then use the found launch config.
Code is almost the same, i made a few changes for the 750ti and 9xx which were handled like a titan in cudaminer, but you are using a GTX 660, so its not that...
i suggest using autotune only after a clean boot... and only then use the found launch config.
Code is almost the same, i made a few changes for the 750ti and 9xx which were handled like a titan in cudaminer, but you are using a GTX 660, so its not that...
Could be higher device_backoff in ccminer or that device_singlememory is not optional in ccminer?
no, read my readme
Using CCminer hashing Neoscypt on GTX660/760 family,mining does not start with error; “sorry neoscrypt is not supported on devices SM 3.0″
Although the changelogs state that it should... shouldn't it?
http://cryptomining-blog.com/?s=ccminer+
1.64-supports Compute 3.0, 3.5, 5.0 and 5.2 GPUs, but note that not all algorithms may work on older GPUs
1.63-supports Compute 3.0, 3.5, 5.0 and 5.2 GPUs
Although the changelogs state that it should... shouldn't it?
http://cryptomining-blog.com/?s=ccminer+
1.64-supports Compute 3.0, 3.5, 5.0 and 5.2 GPUs, but note that not all algorithms may work on older GPUs
1.63-supports Compute 3.0, 3.5, 5.0 and 5.2 GPUs
that look like your card memory was used... ive seen that with cudaminer... sometimes you need to restart it more than once to get all the memory available.
i suggest using autotune only after a clean boot... and only then use the found launch config.
Code is almost the same, i made a few changes for the 750ti and 9xx which were handled like a titan in cudaminer, but you are using a GTX 660, so its not that...
i suggest using autotune only after a clean boot... and only then use the found launch config.
Code is almost the same, i made a few changes for the 750ti and 9xx which were handled like a titan in cudaminer, but you are using a GTX 660, so its not that...
I noticed that, when i let Cudaminer do it's autotuning, it finds a way better setting for my cards.
Where CCminer always ends up at k11x1, Cuda starts to work at k68x1 or k34x2. Resulting in being about 155% faster.
When i pass those settings to CCminer,it is perfectly capable to reach the same speeds.
Why is CCminer not capable of finding this setting on its own?
Where CCminer always ends up at k11x1, Cuda starts to work at k68x1 or k34x2. Resulting in being about 155% faster.
When i pass those settings to CCminer,it is perfectly capable to reach the same speeds.
Why is CCminer not capable of finding this setting on its own?
Code:
[2015-05-29 22:42:39] accepted: 0/1 (0.00%), 114.91 H/s booooo
[2015-05-29 22:58:02] GPU #0: GeForce GTX 660, 114.53 H/s
[2015-05-29 22:58:02] accepted: 0/2 (0.00%), 229.44 H/s booooo
You will get a lot of boo like that without the gbt check... That means somebody else found it before you. You can sometimes have more details in the wallet debug.log
Ok,thanks,i'm quite noob at scrypt-jane.
Well well look at what just happened :-)
Its a booo though... hope it will straighten out!
Is it normal behaviour that one cannot see the hashing rate when it's working?
Only see it with the block found...
edit: By looking at the hashrate, i realised that CCminer does this job about 20% faster compared to Cudaminer!
(Cudaminer starts out at 110 or 120 but quickly drops and holds at about 90,sometimes 80. CCminer seems to stick at 110)
Well well look at what just happened :-)
Code:
[2015-05-29 20:52:11] found => 800799bf bf990780
[2015-05-29 20:52:11] accepted: 0/1 (0.00%), 114.88 H/s booooo
Its a booo though... hope it will straighten out!
Is it normal behaviour that one cannot see the hashing rate when it's working?
Only see it with the block found...
edit: By looking at the hashrate, i realised that CCminer does this job about 20% faster compared to Cudaminer!
(Cudaminer starts out at 110 or 120 but quickly drops and holds at about 90,sometimes 80. CCminer seems to stick at 110)
its the purpose of these n= ... its the current scanned nonce
So... if it keeps doing this, for an hour now, is ccminer actually mining or not?
Because i get Cudaminer to go in a matter of seconds,and it could have had 1, or even 2 blocks if i were lucky by now!
Because i get Cudaminer to go in a matter of seconds,and it could have had 1, or even 2 blocks if i were lucky by now!
Code:
[2015-05-29 19:39:54] GPU #0: n=58
[2015-05-29 19:40:43] GPU #1: n=80001657
[2015-05-29 19:40:43] GPU #0: n=1658
[2015-05-29 19:41:32] GPU #1: n=80002c57
[2015-05-29 19:41:32] GPU #0: n=2c58
[2015-05-29 19:42:21] GPU #1: n=80004257
[2015-05-29 19:42:21] GPU #0: n=4258
[2015-05-29 19:43:10] GPU #1: n=80005857
[2015-05-29 19:43:10] GPU #0: n=5858
[2015-05-29 19:43:59] GPU #1: n=80006e57
[2015-05-29 19:43:59] GPU #0: n=6e58
[2015-05-29 19:44:48] GPU #1: n=80008457
[2015-05-29 19:44:48] GPU #0: n=8458
[2015-05-29 19:45:37] GPU #1: n=80009a57
[2015-05-29 19:45:37] GPU #0: n=9a58
[2015-05-29 19:46:26] GPU #1: n=8000b057
*CUT*
[2015-05-29 20:33:50] GPU #1: n=8005ac57
[2015-05-29 20:33:54] GPU #0: n=5ac58
[2015-05-29 20:34:39] GPU #1: n=8005c257
[2015-05-29 20:34:43] GPU #0: n=5c258
[2015-05-29 20:35:28] GPU #1: n=8005d857
[2015-05-29 20:35:32] GPU #0: n=5d858
[2015-05-29 20:36:17] GPU #1: n=8005ee57
[2015-05-29 20:36:21] GPU #0: n=5ee58
[2015-05-29 20:37:06] GPU #1: n=80060457
[2015-05-29 20:37:10] GPU #0: n=60458
[2015-05-29 20:37:55] GPU #1: n=80061a57
[2015-05-29 20:38:00] GPU #0: n=61a58
[2015-05-29 20:38:44] GPU #1: n=80063057
[2015-05-29 20:38:49] GPU #0: n=63058
[2015-05-29 20:39:33] GPU #1: n=80064657
[2015-05-29 20:39:38] GPU #0: n=64658
jane is very "slow" at this factor you have to be really patient... generally faster after a few minutes (only tested with -a scrypt-jane:CACH)
That works! It removes the error and i think there is work being done. But in normal mode,you still don't see anything happening.
Using -D again,i can see stuff like this going on;
When i terminate the batch job,ccminer crashes. But i can still answer the question;
When i choose Y, i could get a storm of messages like this;
I noticed that GPU 1 is not mentioned,don't know if this is important!
Would greatly appreciate a bit more help!
edit:both gpu's are 100% utilised,so the working part is Ok,just not the status/output part!
Using -D again,i can see stuff like this going on;
Code:
[2015-05-29 19:24:20] GPU #0: n=58
[2015-05-29 19:24:20] GPU #1: n=80000057
[2015-05-29 19:25:09] GPU #1: n=80001657
[2015-05-29 19:25:09] GPU #0: n=1658
[2015-05-29 19:25:58] GPU #1: n=80002c57
[2015-05-29 19:25:58] GPU #0: n=2c58
Code:
Terminate batch job (Y/N)?
Code:
[2015-05-29 19:29:34] CTRL_BREAK_EVENT received, exiting
[2015-05-29 19:29:36] GPU #0: start=00000319 end=00100318 range=000fffff
[2015-05-29 19:29:36] GPU #0: n=371
[2015-05-29 19:29:36] GPU #0: GeForce GTX 660, 88.00 kH/s
[2015-05-29 19:29:36] GPU #0: start=00000372 end=00100371 range=000fffff
[2015-05-29 19:29:36] GPU #0: n=3ca
[2015-05-29 19:29:36] GPU #0: GeForce GTX 660, 44.00 kH/s
[2015-05-29 19:29:36] GPU #0: start=000003cb end=001003ca range=000fffff
[2015-05-29 19:29:36] GPU #0: n=423
[2015-05-29 19:29:36] GPU #0: GeForce GTX 660, 88.00 kH/s
[2015-05-29 19:29:36] GPU #0: start=00000424 end=00100423 range=000fffff
[2015-05-29 19:29:36] GPU #0: n=47c
[2015-05-29 19:29:36] GPU #0: GeForce GTX 660, 88.00 kH/s
[2015-05-29 19:29:36] GPU #0: start=0000047d end=0010047c range=000fffff
[2015-05-29 19:29:36] GPU #0: n=4d5
[2015-05-29 19:29:36] GPU #0: GeForce GTX 660, 88.00 kH/s
[2015-05-29 19:29:36] GPU #0: start=000004d6 end=001004d5 range=000fffff
[2015-05-29 19:29:36] GPU #0: n=52e
[2015-05-29 19:29:36] GPU #0: GeForce GTX 660, 88.00 kH/s
[2015-05-29 19:29:36] GPU #0: start=0000052f end=0010052e range=000fffff
Would greatly appreciate a bit more help!
edit:both gpu's are 100% utilised,so the working part is Ok,just not the status/output part!
just try --no-gbt
i didnt test but its optional/recommended to check the current block height before the submit of found nonces (to prevent some booo)
i didnt test but its optional/recommended to check the current block height before the submit of found nonces (to prevent some booo)
Love your work!
But i've tried to solo UTC and nothing happens with CCminer. Good old Cudaminer does the job just fine. Though i'd rather use CC.
Tried 1.62,1.63,1.64, all the same.
Using the -D flag i immediately see an error...can you fix it? Thanks in advance!
JSON-RPC call failed: getblocktemplate [params]
Returns data needed to construct a block to work on:
"version" : block version
"previousblockhash" : hash of current highest block
"transactions" : contents of non-coinbase transactions that should be included in the next block
"coinbaseaux" : data that should be included in coinbase
"coinbasevalue" : maximum allowable input to coinbase transaction, including the generation award and transaction fees
"target" : hash target
"mintime" : minimum timestamp appropriate for next block
"curtime" : current timestamp
"mutable" : list of ways the block template may be changed
"noncerange" : range of valid nonces
"sigoplimit" : limit of sigops in blocks
"sizelimit" : limit of block size
"bits" : compressed target of next block
"height" : height of the next block
See https://en.bitcoin.it/wiki/BIP_0022 for full specification.
But i've tried to solo UTC and nothing happens with CCminer. Good old Cudaminer does the job just fine. Though i'd rather use CC.
Tried 1.62,1.63,1.64, all the same.
Using the -D flag i immediately see an error...can you fix it? Thanks in advance!
JSON-RPC call failed: getblocktemplate [params]
Returns data needed to construct a block to work on:
"version" : block version
"previousblockhash" : hash of current highest block
"transactions" : contents of non-coinbase transactions that should be included in the next block
"coinbaseaux" : data that should be included in coinbase
"coinbasevalue" : maximum allowable input to coinbase transaction, including the generation award and transaction fees
"target" : hash target
"mintime" : minimum timestamp appropriate for next block
"curtime" : current timestamp
"mutable" : list of ways the block template may be changed
"noncerange" : range of valid nonces
"sigoplimit" : limit of sigops in blocks
"sizelimit" : limit of block size
"bits" : compressed target of next block
"height" : height of the next block
See https://en.bitcoin.it/wiki/BIP_0022 for full specification.
i fixed the first case... for the second one... hmm need some more work/brain storm
just compiled the latest git, password is working now, but it doesn't seems to parse the -r (--retries) parameter properly, i set -r 0 (or --retries=0) and it just get ignore with the default value (retry indefinitely)
if i put in two pools it just loops the two pools indefinitely, regardless of the "retries" : "0" option
thanks!
Code:
[2015-05-28 07:49:35] Stratum authentication failed
[2015-05-28 07:49:35] Stratum connect timeout, failover...
[2015-05-28 07:49:35] No other pools to try...
[2015-05-28 07:49:35] ...retry after 30 seconds
[2015-05-28 07:50:06] Stratum authentication failed
[2015-05-28 07:50:06] Stratum connect timeout, failover...
[2015-05-28 07:50:06] No other pools to try...
[2015-05-28 07:50:06] ...retry after 30 seconds
if i put in two pools it just loops the two pools indefinitely, regardless of the "retries" : "0" option
Code:
[2015-05-28 07:54:02] Stratum authentication failed
[2015-05-28 07:54:02] Stratum connect timeout, failover...
[2015-05-28 07:54:02] Switch to stratum pool 1: eu
[2015-05-28 07:54:05] Stratum authentication failed
[2015-05-28 07:54:05] Stratum connect timeout, failover...
[2015-05-28 07:54:05] Switch to stratum pool 0: usa
thanks!
Multi pool doesnt means algo switching...
Ccminer is not ready for that yet..
Require changes in all the algos to free the gpu. Hmm in fact maybe not with cudaDeviceReset()
Ccminer is not ready for that yet..
Require changes in all the algos to free the gpu. Hmm in fact maybe not with cudaDeviceReset()
So I am trying to do some multialgo switching on nicehash, here is my test config file:
But, after attempting to connect to x11.eu.nicehash.com et predictably getting dropped, it attempts to mine x11 whilst connected to quark.eu.nicehash.com...
Seems it only cares about the first "algo" it finds...
Any ideas?
But, after attempting to connect to x11.eu.nicehash.com et predictably getting dropped, it attempts to mine x11 whilst connected to quark.eu.nicehash.com...
Seems it only cares about the first "algo" it finds...
Any ideas?
Code:
{
"pools" : [
{
"name": "nicehash x11",
"algo" : "x11",
"url" : "stratum+tcp://x11.eu.nicehash.com:4336",
"user" : "1xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
"pass" : "f0=0;f2=0;f3=3;f12=4",
"intensity" : 16
},
{
"name": "nicehash quark",
"algo" : "quark",
"url" : "stratum+tcp://quark.eu.nicehash.com:4345",
"user" : "1xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
"pass" : "f0=0;f2=0;f3=3;f12=4",
"intensity" : 18.1
}
],
"api-remote": false
}
its limited to 64 characters indeed, i was expecting this problem... will increase it to 128 in the next version
Jump to: