CCminer(SP-MOD) Modded GPU kernels.

[sp_]

@sp_, I don't see Digibyte on your coinspool. It shows up as Trinity.

MYR-GR ALGO--
I was able to set-up and solo-mine DigiByte (DGB) coin.  My 750ti cards got 15Mh/s, my 960 cards got 30Mh/s, and my 270 cards got 45Mh/s.  I spent a few hours on it, but DGB is a high difficulty coin, and the value dropped rapidly as I mined.  I didn't hit a bllock.  It is difficult to find the network hash rate for DGB on each algo, too.       --scryptr

You can get the diffs from the wallet though with getmininginfo:
"blocks" : 1299118,
"difficulty_sha256d" : 4866313.40426662,
"difficulty_scrypt" : 334.38890218,
"difficulty_groestl" : 723.73364105,
"difficulty_skein" : 4203.55432105,
"difficulty_qubit" : 139.71485676,
But yeah, with that diff you need ~34 Mh/s (myr-gr) to find one block a day and the diff jumps around a lot.

My gtx 970 does:
Skein: 300MHASH
MYR-GR: 47MHASH
Qubit: 10MHASH
With the current difficulty mining my-gr and one gtx 970 you will make around 3012 DGB = $0.8 per day.
Not worth it..

Yes I checked it out...not worth it...every algo down....we're almost mining air.

MYR-GR BROKEN--
I continued to work with the Myriad-Groestl (myr-gr) algo and can confirm that it is broken.  Mining with release dot 71 at DigiHash.co, the official DigiByte developer's pool, I got about 1.5Mh/s poolside with my GTX 960, while in my console the display read 30.5Mh/s.  I also tried DigiByte's "EasyMiner".  It uses an older version of CCminer, v1.5.24.  It got 26Mh/s poolside and in my console, with fluctuation poolside. I earned 71 DigiBytes (DGB) overnight with my GTX 960 using EasyMiner.
I am now trying to solo-mine Diamond coin (DMD), with Diamond-Groestl (dmd-gr).  There are good solo-mining  instructions on the web for both Diamond coin and DigiByte coin.  My GTX 960 SC gets 16.2Mh/s with +80/240, my 750ti FTW cards get 8Mh/s stock for dmd-gr algo.       --scryptr

Username:
Password:
Algorithm:
URL (difficulty 0.01):
URL (difficulty 0.1):
URL (difficulty 32):
your digibyte-groestl wallet address
anything
groestlmyriad
stratum+tcp://digihash.co:3010
stratum+tcp://digihash.co:3034
stratum+tcp://digihash.co:3258


Default difficulty in release 71 is 1.
Default difficulty in release at github is 256


So if you use release 71-github use

--diff 8 stratum+tcp://digihash.co:3258

[NiceHashSupport]

Anybody what's the best miner control for nicehash only.  thx

Upcoming NiceHash Miner. Soon will have support for NVIDIA GPUs. Maybe we put on new beta even today

[scryptr]

DIAMOND-GROESTL OK! --

I checked the  Diamond-Groestl (dmd-gr) out at CryptoPools Diamond mine and it works well.  Pool and local-console hash rates were in agreement at default difficulty.  My GTX 960 mined at 16Mh/s, and the pool rates were usually within +/- 5% with fluctuation. 

I'll look at Myriad-Groestl again later.       --scryptr

[scryptr]

MYRIAD-GROESTL BROKEN--


Although I tried several difficulty correction factors ("--diff" or "-f") ranging from 8 to .25, I could not get algo "myr-gr" to work properly on DigiHash.co.  I cloned from git release dot 71, and tried both the .1 difficulty and the 32 difficulty pools.  All rejects, "low difficulty share".

--scryptr

[sp_]

MYRIAD-GROESTL BROKEN--
Although I tried several difficulty correction factors ("--diff" or "-f") ranging from 8 to .25, I could not get algo "myr-gr" to work properly on DigiHash.co.  I cloned from git release dot 71, and tried both the .1 difficulty and the 32 difficulty pools.  All rejects, "low difficulty share".
--scryptr

The pool is broken. They are changing the difficulty dynamicly to make you use their own mining software

You can mine myr-gt trinity here:

http://coinspool.cu.cc/info_trinity

works like a charm


I just pointed some gigahash of myr-gt to the pool to show you

[tbearhere]

Anybody what's the best miner control for nicehash only.  thx

Upcoming NiceHash Miner. Soon will have support for NVIDIA GPUs. Maybe we put on new beta even today

Great..... thx  Nicehash.  
I can't compile it....need it with windows 8.

[hashbrown9000]

@sp_, I mined Trinity at coinspool last night at around 1.13 GH for about two hours, but it didn't seem like the pool was going to credit me any coins even though i was getting accepts in the miner.  Only diff .0039xxxx was working for me to avoid "above target share" errors.  Should I just leave all my gigahashes there and see what happens?  b/t/w I was using commit number 1124.

[NiceHashSupport]

Anybody what's the best miner control for nicehash only.  thx

Upcoming NiceHash Miner. Soon will have support for NVIDIA GPUs. Maybe we put on new beta even today

Great..... thx  Nicehash.  
I can't compile it....need it with windows 8.

No need to compile. Binaries have been released.

https://github.com/nicehash/NiceHashMiner

Try it out We made it powerful enough, so you can adjust your own intensity parameters if you like (but that requires fiddling with json config: https://github.com/nicehash/NiceHashMiner#options)

[bensam1231]

@sp_, I don't see Digibyte on your coinspool. It shows up as Trinity.

MYR-GR ALGO--
I was able to set-up and solo-mine DigiByte (DGB) coin.  My 750ti cards got 15Mh/s, my 960 cards got 30Mh/s, and my 270 cards got 45Mh/s.  I spent a few hours on it, but DGB is a high difficulty coin, and the value dropped rapidly as I mined.  I didn't hit a bllock.  It is difficult to find the network hash rate for DGB on each algo, too.       --scryptr

You can get the diffs from the wallet though with getmininginfo:
"blocks" : 1299118,
"difficulty_sha256d" : 4866313.40426662,
"difficulty_scrypt" : 334.38890218,
"difficulty_groestl" : 723.73364105,
"difficulty_skein" : 4203.55432105,
"difficulty_qubit" : 139.71485676,
But yeah, with that diff you need ~34 Mh/s (myr-gr) to find one block a day and the diff jumps around a lot.

My gtx 970 does:

Skein: 300MHASH
MYR-GR: 47MHASH
Qubit: 10MHASH

With the current difficulty mining my-gr and one gtx 970 you will make around 3012 DGB = $0.8 per day.

Not worth it..

Yes I checked it out...not worth it...every algo down....we're almost mining air.

MYR-GR BROKEN--

I continued to work with the Myriad-Groestl (myr-gr) algo and can confirm that it is broken.  Mining with release dot 71 at DigiHash.co, the official DigiByte developer's pool, I got about 1.5Mh/s poolside with my GTX 960, while in my console the display read 30.5Mh/s.  I also tried DigiByte's "EasyMiner".  It uses an older version of CCminer, v1.5.24.  It got 26Mh/s poolside and in my console, with fluctuation poolside. I earned 71 DigiBytes (DGB) overnight with my GTX 960 using EasyMiner.

I am now trying to solo-mine Diamond coin (DMD), with Diamond-Groestl (dmd-gr).  There are good solo-mining  instructions on the web for both Diamond coin and DigiByte coin.  My GTX 960 SC gets 16.2Mh/s with +80/240, my 750ti FTW cards get 8Mh/s stock for dmd-gr algo.       --scryptr

Tpruvot version displays correctly poolside, but has lower hash.

MYRIAD-GROESTL BROKEN--
Although I tried several difficulty correction factors ("--diff" or "-f") ranging from 8 to .25, I could not get algo "myr-gr" to work properly on DigiHash.co.  I cloned from git release dot 71, and tried both the .1 difficulty and the 32 difficulty pools.  All rejects, "low difficulty share".
--scryptr

The pool is broken. They are changing the difficulty dynamicly to make you use their own mining software

You can mine myr-gt trinity here:

http://coinspool.cu.cc/info_trinity

works like a charm


I just pointed some gigahash of myr-gt to the pool to show you

It doesn't work on other Myr-gr DGB pools though. Not sure what trinity is, but it's not worth mining. There are a few DGB pools besides theblockfactory.

[skunk]

since i was curious about the evolution of the miner, i've performed some benchmarks on a 960 with various popular building with both cuda 6.5 and 7.5...

Code:

cuda 6.5.19

version    x11       x13   neoscrypt   qubit     quark    lyra2v2
-----------------------------------------------------------------
1.5.61   4896.75   3817.49   307.50   7370.82   9901.39   4975.50
1.5.62   4830.94   3824.48   308.17   7367.76   9832.79   4892.54
1.5.63   4829.33   3827.89   307.98   7329.33   9942.74   5064.79
1.5.64   4830.37   3828.82   305.08   7364.21   9939.97   5022.05
1.5.65   4833.80   3829.02   308.03   7316.46   9935.27   5128.57
1.5.66   4841.17   3828.98   308.19   7309.84   9945.59   4964.04
1.5.67   4843.54   3842.94   304.59   7307.92   9895.11   5311.58
1.5.68   4871.72   3849.88   304.81   7333.10   9897.92   5284.52
1.5.69   4871.32   3846.09   305.23   7316.51   9926.38   5291.48
1.5.70   4850.56   3840.83   300.97   7325.78   9928.29   5274.59
1.5.71   4864.87   3848.43   302.00   7311.15   9938.50   5434.95
HEAD     4859.92   3846.95   279.25   7309.49   9943.24   5442.70


cuda 7.5.18

version    x11       x13   neoscrypt   qubit     quark    lyra2v2
-----------------------------------------------------------------
1.5.61   4545.64   3557.33    na      6833.08   9649.00   5137.34
1.5.62   4548.16   3536.73    na      6765.00   9741.35   5082.66
1.5.63   4549.85   3552.70    na      6766.62   9595.26   5254.05
1.5.64   4469.91   3544.88    na      6766.10   9772.69   5268.54
1.5.65   4537.04   3558.38    na      6760.28   9845.07   5329.07
1.5.66   4379.26   3547.62    na      6816.86   9779.27   5404.03
1.5.67   4572.08   3575.58    na      6764.94   9649.66   5782.35
1.5.68   4568.98   3576.28    na      6763.20  10016.10   5752.82
1.5.69   4564.96   3576.59    na      6760.18   9971.33   5747.59
1.5.70   4566.48   3564.19    na      6775.10   9936.68   5737.31
1.5.71   4529.04   3568.78    na      6756.01   9961.33   5505.06
HEAD     4564.34   3580.72    na      6748.33  10013.80   5506.37

edit: this is under linux

[DragonSlayer]

I guess that I should use cuda 7.5 while I am on lyra2v2.

[cidman]

what should i use for settings on lyra2REv2 on nicehash
i tried --diff .5 like i use on gimmiecoins but i get share above target so i tried lower settings and at .01 nothing gets accepted and everything i tried above goes same problem

ccminer.exe -a lyra2v2 -o stratum+tcp://lyra2re.usa.nicehash.com:3342 -u address -p x -t 1 -d gtx750ti --diff .011

[scryptr]

what should i use for settings on lyra2REv2 on nicehash
i tried --diff .5 like i use on gimmiecoins but i get share above target so i tried lower settings and at .01 nothing gets accepted and everything i tried above goes same problem

ccminer.exe -a lyra2v2 -o stratum+tcp://lyra2re.usa.nicehash.com:3342 -u address -p x -t 1 -d gtx750ti --diff .011

NICEHASH ALGO NAME--

NiceHash does not require a "diff" setting.  This was argued out in the thread after the release of Lyra 2 revision 2.  NiceHash uses the SGminer syntax for naming their Lyra2v2 pool!

Your launch string should be as follows:

ccminer.exe -a lyra2v2 -o stratum+tcp://lyra2rev2.usa.nicehash.com:3347 -u address -p x -t 1 -d gtx750ti

In your string above, there is a typo.  You called the algo correctly for CCminer, but the pool name was not correct.  No difficulty correction is needed.


--scryptr

[cidman]

what should i use for settings on lyra2REv2 on nicehash
i tried --diff .5 like i use on gimmiecoins but i get share above target so i tried lower settings and at .01 nothing gets accepted and everything i tried above goes same problem

ccminer.exe -a lyra2v2 -o stratum+tcp://lyra2re.usa.nicehash.com:3342 -u address -p x -t 1 -d gtx750ti --diff .011

NICEHASH ALGO NAME--

NiceHash does not require a "diff" setting.  This was argued out in the thread after the release of Lyra 2 revision 2.  NiceHash uses the SGminer syntax for naming their Lyra2v2 pool!

Your launch string should be as follows:

ccminer.exe -a lyra2v2 -o stratum+tcp://lyra2rev2.usa.nicehash.com:3347 -u address -p x -t 1 -d gtx750ti

In your string above, there is a typo.  You called the algo correctly for CCminer, but the pool name was not correct.  No difficulty correction is needed.


--scryptr

lol thx yea guess i pulled the wrong stratum when setting up just now
quark payouts just dropped below what id consider worth it so switching to lyra
all working well now and all 750ti cards running higher than i remember on the 71 release at 4.4-4.5Mh lyra2REv2
next time ill make sure i double check all settings thx again

[DragonSlayer]

This is kind of a vs2013 question.  I installed cuda 7.5, so now I have both on the pc.  How to I tell vs to use 7.5 instead of default which is 6.5?

[sp_]

since i was curious about the evolution of the miner, i've performed some benchmarks on a 960 with various popular building with both cuda 6.5 and 7.5...

Code:

cuda 6.5.19

version    x11       x13   neoscrypt   qubit     quark    lyra2v2
-----------------------------------------------------------------
1.5.61   4896.75   3817.49   307.50   7370.82   9901.39   4975.50
1.5.62   4830.94   3824.48   308.17   7367.76   9832.79   4892.54
1.5.63   4829.33   3827.89   307.98   7329.33   9942.74   5064.79
1.5.64   4830.37   3828.82   305.08   7364.21   9939.97   5022.05
1.5.65   4833.80   3829.02   308.03   7316.46   9935.27   5128.57
1.5.66   4841.17   3828.98   308.19   7309.84   9945.59   4964.04
1.5.67   4843.54   3842.94   304.59   7307.92   9895.11   5311.58
1.5.68   4871.72   3849.88   304.81   7333.10   9897.92   5284.52
1.5.69   4871.32   3846.09   305.23   7316.51   9926.38   5291.48
1.5.70   4850.56   3840.83   300.97   7325.78   9928.29   5274.59
1.5.71   4864.87   3848.43   302.00   7311.15   9938.50   5434.95
HEAD     4859.92   3846.95   279.25   7309.49   9943.24   5442.70


cuda 7.5.18

version    x11       x13   neoscrypt   qubit     quark    lyra2v2
-----------------------------------------------------------------
1.5.61   4545.64   3557.33    na      6833.08   9649.00   5137.34
1.5.62   4548.16   3536.73    na      6765.00   9741.35   5082.66
1.5.63   4549.85   3552.70    na      6766.62   9595.26   5254.05
1.5.64   4469.91   3544.88    na      6766.10   9772.69   5268.54
1.5.65   4537.04   3558.38    na      6760.28   9845.07   5329.07
1.5.66   4379.26   3547.62    na      6816.86   9779.27   5404.03
1.5.67   4572.08   3575.58    na      6764.94   9649.66   5782.35
1.5.68   4568.98   3576.28    na      6763.20  10016.10   5752.82
1.5.69   4564.96   3576.59    na      6760.18   9971.33   5747.59
1.5.70   4566.48   3564.19    na      6775.10   9936.68   5737.31
1.5.71   4529.04   3568.78    na      6756.01   9961.33   5505.06
HEAD     4564.34   3580.72    na      6748.33  10013.80   5506.37

edit: this is under linux

What card is this (memclock/coreclock)? And how long did you run the benchmark

You get bether rates under windows x86 builds. Asus strix 960 should do above 6MHASH on lyra2v2 and 10.7 in quark. (cuda 6.5)

Qubit and neoscrypt has been untouched in the last 10 releases. (compute 5.2 cards) They are running the exact same kernals as in release 61.

For more accurate benchmarking you should use the --timelimit option.

ccminer -a quark --benchmark --timelimit 500  (will mine for 500 seconds and then exit)

If your card trottle, (hashrate is decreasing over time) The gpu-clock is downlocked automaticly and hashrate is lost. To avoid trottling reduce the intenstiy, increase the tdp in the bios, increase the temp limits of the card. (overclock) make sure that you always run in p0 mode.

Interesting that my junior asus strix 750ti with +200 on the mem-clock/gpu-clock is almost running faster than your gtx 960 in lyra. I get 5.4MHASH.

(640 shaders vs 1024)

[lawrencelyl]

What intensity value were you using to hit 5.4MH/s on 750Ti apart from +200 core/mem overclock?

[sp_]

Try -i 12.

[bensam1231]

Down and down everything goes, this is the worst I've seen algos in a long time...

[sp_]

Down and down everything goes, this is the worst I've seen algos in a long time...

Thats why you need to mine algos that aren't supported by nicehash / multipools..

I have continued to mod pentablake now. 90MHASH on the gtx970..

the opensource does 15MHASH on the 750ti.

So with my modded kernal 1 gtx970 is producing the same as 6 750ti's running the opensource kernal.

@200 MHASH i get around 82 Joincoins/day (0.02BTC / day)

Pentablake is X5. (5 rounds of (blake-512 16 rounds))


The 80MHASH@970 kernal is for sale.  it does 32MHASH on the 750ti. (More than 100% faster than the open source)

The price is 0.3BTC

pm for details.