CCminer(SP-MOD) Modded GPU kernels.

[K1773R]

HEAD@windows never submits any shares.

you need to use --diff 128 (if it is related to lyra2re)

tested with x11 and x13. i see a big hashrate increase, tough never any submitted shares.

Works here. Is this on linux? wich card?

yes on linux.
GTX 680 SOC which is unfortunately not compute 5

[1715496211]

1715496211

[1715496211]

1715496211

[sp_]

HEAD@windows never submits any shares.

you need to use --diff 128 (if it is related to lyra2re)

tested with x11 and x13. i see a big hashrate increase, tough never any submitted shares.

Works here. Is this on linux? wich card?

yes on linux.
GTX 680 SOC which is unfortunately not compute 5

The head on Gtihub only works for compute 3.5 cards or newer.

http://en.wikipedia.org/wiki/CUDA

If you have 3.0 you can use the tpruvot version:

https://bitcointalk.org/index.php?topic=770064.0

[K1773R]

HEAD@windows never submits any shares.

you need to use --diff 128 (if it is related to lyra2re)

tested with x11 and x13. i see a big hashrate increase, tough never any submitted shares.

Works here. Is this on linux? wich card?

yes on linux.
GTX 680 SOC which is unfortunately not compute 5

The head on Gtihub only works for compute 3.5 cards or newer.

http://en.wikipedia.org/wiki/CUDA

If you have 3.0 you can use the tvpovet version:

https://bitcointalk.org/index.php?topic=770064.0

thanks.

[Epsylon3]

If you have 3.0 you can use the tvpovet version:

https://bitcointalk.org/index.php?topic=770064.0

Could you try to write once my name correctly ? tx

[sp_]

Version 20 is here (windows executable):

Faster x11 (+100KHASH(750ti))
faster x13,x14,x15,x17
fixed hashing for old cards.

http://www.filedropper.com/ccminer_1

source

https://github.com/sp-hash/ccminer


One exe this time. Compiled for compute30,32,35,50,52


cards supported:

GeForce GTX 770, GeForce GTX 760, GeForce GT 740, GeForce GTX 690, GeForce GTX 680, GeForce GTX 670, GeForce GTX 660 Ti, GeForce GTX 660, GeForce GTX 650 Ti BOOST, GeForce GTX 650 Ti, GeForce GTX 650, GeForce GTX 780M, GeForce GTX 770M, GeForce GTX 765M, GeForce GTX 760M, GeForce GTX 680MX, GeForce GTX 680M, GeForce GTX 675MX, GeForce GTX 670MX, GeForce GTX 660M, GeForce GT 750M, GeForce GT 650M, GeForce GT 745M, GeForce GT 645M, GeForce GT 740M, GeForce GT 730M, GeForce GT 640M, GeForce GT 640M LE, GeForce GT 735M, GeForce GT 730M, Quadro K5000, Quadro K4200, Quadro K4000, Quadro K2000, Quadro K2000D, Quadro K600, Quadro K420, Quadro K500M, Quadro K510M, Quadro K610M, Quadro K1000M, Quadro K2000M, Quadro K1100M, Quadro K2100M, Quadro K3000M, Quadro K3100M, Quadro K4000M, Quadro K5000M, Quadro K4100M, Quadro K5100M, Tesla K10
GeForce GTX TITAN Z, GeForce GTX TITAN Black, GeForce GTX TITAN, GeForce GTX 780 Ti, GeForce GTX 780, GeForce GT 640 (GDDR5), GeForce GT 630 v2, Quadro K6000, Quadro K5200, Tesla K40, Tesla K20x, Tesla K20
Tesla K80 GeForce GTX 750 Ti, GeForce GTX 750, GeForce GTX 860M, GeForce GTX 850M, GeForce 845M, GeForce 840M, GeForce 830M, Quadro K2200, Quadro K620, Quadro K620M GeForce GTX 980, GeForce GTX 970, GeForce GTX 980M, GeForce GTX 970M

[sp_]

Been test hashing on build20 on gtx650. Seems to be some frequent HW errors(compute 3.0). Will look into it.

[Bombadil]

Version 20 is here (windows executable):

Faster x11 (+100KHASH(750ti))
faster x13,x14,x15,x17
fixed hashing for old cards.

http://www.filedropper.com/ccminer_1

source

https://github.com/sp-hash/ccminer


One exe this time. Compiled for compute30,32,35,50,52

Can you also update the version, as reported by the API? My tool starts a new benchmark if it detects a new version, but it didn't now
Makes it easy to show differences between versions and authors.

Also, GTX760 (compute 3.0) doesn't work: http://snag.gy/2Vo9h.jpg

[jpouza]

Build20 running OK for now, nice be just one instance for mining, all in one

In X11:

3.2MH/s 750Ti@200+core/400+mems

9.6MH/s 980@150+core/0+ mems

980gtx temps at 55ºC@ EK WC.

Nice.

Cheers

[sp_]

Can you also update the version, as reported by the API? My tool starts a new benchmark if it detects a new version, but it didn't now
Makes it easy to show differences between versions and authors.
Also, GTX760 (compute 3.0) doesn't work: http://snag.gy/2Vo9h.jpg

Updated on github. Tried to fix 3.0, but changing the methods in cudahelper.h doesn't work. Must be something else. Will fix it later. Can anyone test on compute 3.5 please? how is the hash on 780ti?

[jpouza]

Wow, average hash reported by the pool improved, from 30MH/s to 35-40MH/s.

Nice.

[sp_]

Yes this version is bether on the pools when mining on high intensity. The old version only found one solution below target, this version is submitting 2 solutions. Code forked fronm 1.5.1 (tvprovot's work)

[Amph]

how much the last version, does on scrypt algo?

i've checked the source now, there isn't any scrypt algo available, you removed it?

p.s. ah silly me, scypt is in cudaminer, i always forgot that lol, mmh...old cudaminer isn't working right with 970, not optimized i supposed, it use T91

[exemplaar]

Yes this version is bether on the pools when mining on high intensity. The old version only found one solution below target, this version is submitting 2 solutions. Code forked fronm 1.5.1 (tvprovet's work)

Hi SP.

I'm mining X13 on regular pool (not multipool).The hashrate showing by the pool is lower than what the ccminer shows. And there is "set stratum difficulty to x.xxxx" message appearing quite a lot.
I tried versions from 17-20. The same scene. Hashrate is lower (from 14mhs on ccminer to only 8-9mhs on pool). I then tried older version 8 and it works better (13mhs miner 12mhs pool) I have standard setting in .bat file. Do i need a manual set up of diff per rig or is there something else that I'm missing? Switching back to version 8 now...
I would appreciate any help.
Thank you.

[djm34]

Build20 running OK for now, nice be just one instance for mining, all in one

In X11:

3.2MH/s 750Ti@200+core/400+mems

9.6MH/s 980@150+core/0+ mems

980gtx temps at 55ºC@ EK WC.

Nice.

Cheers

ok I checked the hashrate for the 780ti, not terrible honestly compared to the other card.

from my system: 980: 9.6MH/s/9.7MH/s
                       750ti 3.1MH/s
                       780ti 6.1MH/s
I think you have missed something, I don't think there should be so much difference

[sp_]

Yes this version is bether on the pools when mining on high intensity. The old version only found one solution below target, this version is submitting 2 solutions. Code forked fronm 1.5.1 (tvprovet's work)

Hi SP.
I'm mining X13 on regular pool (not multipool).The hashrate showing by the pool is lower than what the ccminer shows. And there is "set stratum difficulty to x.xxxx" message appearing quite a lot.
I tried versions from 17-20. The same scene. Hashrate is lower (from 14mhs on ccminer to only 8-9mhs on pool). I then tried older version 8 and it works better (13mhs miner 12mhs pool) I have standard setting in .bat file. Do i need a manual set up of diff per rig or is there something else that I'm missing? Switching back to version 8 now...
I would appreciate any help.
Thank you.

Wich card is this? you can to change the -i parameter. (intensity) If you are not using this card to display graphic -i 20.5 used to be the best for maxwell cards (750 -980). but it can crash if you have many cards.

The diff should be set in the password of the pool. Try the password -p d=0.02

[sp_]

from my system: 980: 9.6MH/s/9.7MH/s
                       750ti 3.1MH/s
                       780ti 6.1MH/s
I think you have missed something, I don't think there should be so much difference

780ti 6.1MH/s is pretty good. Did you try to increase the intesity to the limit? f.eks -i 19.9 or -i 20.5?
The default intesity in the miner is set to run on 1mb cards. But with compute 5.2 the default is increased. I case on the compute version and not the memory..

[sp_]

how much the last version, does on scrypt algo?
i've checked the source now, there isn't any scrypt algo available, you removed it?
p.s. ah silly me, scypt is in cudaminer, i always forgot that lol, mmh...old cudaminer isn't working right with 970, not optimized i supposed, it use T91

I have looked at the scrypt kernal. I think I can make it 30-50% faster on the maxwell with some work. But waste of time.

[djm34]

from my system: 980: 9.6MH/s/9.7MH/s
                       750ti 3.1MH/s
                       780ti 6.1MH/s
I think you have missed something, I don't think there should be so much difference

780ti 6.1MH/s is pretty good. Did you try to increase the intesity to the limit? f.eks -i 19.9 or -i 20.5?
The default intesity in the miner is set to run on 1mb cards. But with compute 5.2 the default is increased. I case on the compute version and not the memory..

didn't even know there was an intensity   I will check again

edit: 6.2MH at 19.9 and 6.08MH at 20.5

[sp_]

from my system: 980: 9.6MH/s/9.7MH/s
                       750ti 3.1MH/s
                       780ti 6.1MH/s
I think you have missed something, I don't think there should be so much difference

780ti 6.1MH/s is pretty good. Did you try to increase the intesity to the limit? f.eks -i 19.9 or -i 20.5?
The default intesity in the miner is set to run on 1mb cards. But with compute 5.2 the default is increased. I case on the compute version and not the memory..

didn't even know there was an intensity   I will check again
edit: 6.2MH at 19.9 and 6.08MH at 20.5

You probobly need to finetune it. try 18.0, 18,1,18,2.... 20.5

If you find the optimal, I will hardcode the value into the next release with compute 3.5

hehe

[sp_]

Time to make a neoscrypt port for NVIDIA. Can we beat the opencl code by WOLF0?

(nicehash)

NeoScrypt    3341   0.2021 GH/s   4.7595 BTC/GH/Day  738%   3.5289 BTC/GH/Day   5.2900 BTC/GH/Day   5.2900 BTC/GH/Day   View orders