Author

Topic: CCminer(SP-MOD) Modded NVIDIA Maxwell / Pascal kernels. - page 892. (Read 2347659 times)

legendary
Activity: 1797
Merit: 1028
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
full member
Activity: 162
Merit: 102
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
full member
Activity: 181
Merit: 100
I guess that I should use cuda 7.5 while I am on lyra2v2.
sr. member
Activity: 329
Merit: 250
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
legendary
Activity: 1764
Merit: 1024
@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. Smiley

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.
hero member
Activity: 588
Merit: 501
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 Smiley
Great..... thx  Nicehash.  Smiley
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 Wink 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)
sr. member
Activity: 427
Merit: 250
@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.

legendary
Activity: 3164
Merit: 1003
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 Smiley
Great..... thx  Nicehash.  Smiley
I can't compile it....need it with windows 8.
sp_
legendary
Activity: 2954
Merit: 1087
Team Black developer
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

legendary
Activity: 1797
Merit: 1028
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
legendary
Activity: 1797
Merit: 1028
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
hero member
Activity: 588
Merit: 501
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 Smiley
sp_
legendary
Activity: 2954
Merit: 1087
Team Black developer
@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. Smiley
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
member
Activity: 95
Merit: 10
My 6 EVGA 750 ti SC cards (no bios mod) are running great for 577 days with no problems. I no longer over-clock since I stopped mining VTC and LTC back in the day.  Say 90 days of OC.  The GPU fans run at 61-67% GPU temps are 47-53C  I have a Biostar H81S2 Bitcoin motherboard, and Corsair AX760i Platinum PSU. The 6 cards are running windows 8.1 use a total of 435.3W for the rig (According to the digital PSU).

I get

39400 kH/s on Quark.
28720 kH/s on Lyra2v2
19190 kH/s on X11

They have 3 year warranties.  Granted I will finally break even in about 20 days.  And this rig has 8 GB ram and an i3 processor.  I would recommend going for the Celeron processor, a Gold PSU and 4 GB of RAM to save money (takes about 2.9 GB right now to run the OS and rig).   The only good thing about all of the extras is I can compile new versions of ccminer without slowdowns on mining.  Wink


Well had my first card fail.  Time to RMA it.
legendary
Activity: 1797
Merit: 1028
@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. Smiley

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
legendary
Activity: 3164
Merit: 1003
What speeds do you get on GTX 980 Ti and GTX 950 Lyra2REv2?
I get
GTX 980 Ti ... 17.450 khs
GTX 950 ... 5.480 khs
It should be 4x faster than a 750ti.. I get 6.8 mh on 750ti ....30mh on 980ti  that's 4x the hashrate on quark.
Now on Lyra2REv2..750ti I get 4.8mh..on 980ti it should be 21mh...but it's only 16mh... wtf

You need to make a new kernal that uses the extra power of the 980ti. My modded kernals run best on the 750ti.

What is the powerdraw at 17,5 MHASH?
That's r71 and the power draw I don't know and the new precision x 16 won't let me push the memory clock.
I can't make kernels. Smiley That's what I paid .5 btc for you to do. Wink
sp_
legendary
Activity: 2954
Merit: 1087
Team Black developer
What speeds do you get on GTX 980 Ti and GTX 950 Lyra2REv2?
I get
GTX 980 Ti ... 17.450 khs
GTX 950 ... 5.480 khs
It should be 4x faster than a 750ti.. I get 6.8 mh on 750ti ....30mh on 980ti  that's 4x the hashrate on quark.
Now on Lyra2REv2..750ti I get 4.8mh..on 980ti it should be 21mh...but it's only 16mh... wtf

You need to make a new kernal that uses the extra power of the 980ti. My modded kernals run best on the 750ti.

What is the powerdraw at 17,5 MHASH?
legendary
Activity: 3164
Merit: 1003
What speeds do you get on GTX 980 Ti and GTX 950 Lyra2REv2?

I get
GTX 980 Ti ... 17.450 khs
GTX 950 ... 5.480 khs
It should be 4x faster than a 750ti.. I get 6.8 mh on 750ti ....30mh on 980ti  that's 4x the hashrate on quark.

Now on Lyra2REv2..750ti I get 4.8mh..on 980ti it should be 21mh...but it's only 16mh... wtf
legendary
Activity: 1764
Merit: 1024
Difficult to ROI with the 980ti when you know that pascal is comming in q1 2016 with 16 times the speed of the Maxwell. (16nm)

16nm is the process size, it doesn't equate to a 16x increase in performance. Just a increase in efficiency.

A die shrink also means it'll also probably show up late and be expensive due to die yield issues. That's the whole reason we're still on 28nm. I'd say Q2, maybe slipping to early Q3.
newbie
Activity: 51
Merit: 0
Hi, guys i have an issue with second card overclocking.
command works good for gpu:0
Code:
nvidia-settings -a "[gpu:0]/GPUGraphicsClockOffset[1]=125"
and in response i can see something like "new parameter accepted"  (don't remember exactly)
but if i run for my second gpu:1
Code:
nvidia-settings -a "[gpu:1]/GPUGraphicsClockOffset[1]=125"
it will be just empty result.

I use next configs: /etc/X11/xorg.conf
Code:
Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    Option         "Coolbits" "12"
    BusID          "PCI:1:0:0"
EndSection

Section "Device"
    Identifier     "Device1"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    Option         "Coolbits" "12"
    BusID          "PCI:5:0:0"
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    Option         "Coolbits" "12"
    Option         "AllowEmptyInitialConfiguration" "True"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Section "Screen"
    Identifier     "Screen1"
    Device         "Device1"
    Monitor        "Monitor1"
    DefaultDepth    24
    Option         "Coolbits" "12"
    Option         "AllowEmptyInitialConfiguration" "True"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Bus id was checked by command "nvidia-xconfig --query-gpu-info"
Code:
GPU #0:                                                                                                                                                                                                                                             
  Name      : GeForce GTX 750 Ti                                                                                                                                                                                                                   
  UUID      : GPU-9e8890e0-1157-f92e-067e-827bf1cdfef8                                                                                                                                                                                             
  PCI BusID : PCI:1:0:0   

GPU #1:
  Name      : GeForce GTX 750 Ti
  UUID      : GPU-c1ca6da6-5e0c-22d9-9ef9-3ab94f3048a1
  PCI BusID : PCI:5:0:0


can't find what's wrong.
Jump to: