Pages:
Author

Topic: [ANN] ccminer 2.3 - opensource - GPL (tpruvot) - page 27. (Read 500113 times)

hero member
Activity: 675
Merit: 514
Dear Dev,
What should I change to be able to build the miner on Visual Studio 2017?
on 2013 working fine but on 2017 and many errors.
You need CUDA 9 when you want to use VS 2017.
Usually CUDA doesn't work with the latest VS versions.
legendary
Activity: 1484
Merit: 1082
ccminer/cpuminer developer
no, only plimit is reliable
newbie
Activity: 18
Merit: 0
Code:
--mem-clock=3505  Set the gpu memory max clock (346.72+ driver)
--gpu-clock=1150  Set the gpu engine max clock (346.72+ driver)
--pstate=0[,2]    Set the gpu power state (352.21+ driver)
--plimit=100W     Set the gpu power limit (352.21+ driver)
Do those options will auto-overclock my GPU, or are they work as the max limit (making sure clock/temp/power doesn't go above set value)?
legendary
Activity: 1484
Merit: 1082
ccminer/cpuminer developer
Is there a limit of GPUs when using ccMiner ?

I have a rig with 18 GPUs and the last 2 are giving an error when starting ccMiner.

[2017-12-09 15:29:09] GPU #-26224: unable to query application clocks
[2017-12-09 15:29:09] GPU #21872: unable to query application clocks

yes, 16 max, and less on windows i think due to drivers limitation
newbie
Activity: 3
Merit: 0
Hmmm, is it normal that I have more hs/s with -t 2 -i 5.1 (640 threads x 2 = 1280) 650-680 than with single thread and -i 10.3 (1280 threads) - nearly 550 h/s ?
I have single 1060 6 gb.
In 1st case I look at summary of 2 threads
[2017-12-10 04:04:28] accepted: 178/178 (diff 11.135), 649.20 H/s yes!
[2017-12-10 04:04:45] GPU T0: Gigabyte GTX 1060 6GB, 471.93 H/s
[2017-12-10 04:04:45] accepted: 179/179 (diff 10.517), 660.28 H/s yes!
[2017-12-10 04:04:45] accepted: 180/180 (diff 6.498), 660.28 H/s yes!
[2017-12-10 04:04:47] GPU T1: Gigabyte GTX 1060 6GB, 111.03 H/s
[2017-12-10 04:04:47] accepted: 181/181 (diff 17.201), 654.67 H/s yes!
[2017-12-10 04:04:55] GPU T1: Gigabyte GTX 1060 6GB, 414.54 H/s
[2017-12-10 04:04:55] accepted: 182/182 (diff 9.587), 664.49 H/s yes!
[2017-12-10 04:04:58] Stratum difficulty set to 8929 (8.929)

Am I missing smth?
Also without any  manual for intensity settings ccminer doesn't use all cuda cores of 1066 (1280 cores) and gives nearly 520 h/s.
jr. member
Activity: 109
Merit: 1
Does anyone know if mining Vert coin and Mona coin with ccminer 2.2.3 and suprnova require more GPU core clock, memory clock, or both?

For eg. I know it's more important, for Ethereum, to have as high memory clock as possible while with Decred, last I heard, you lower memory clocks because Decred only uses the core.

So what's the best way to go about with Mona and Vert Using Nvidia GTX 1070s?

I'm using a miner called ccminer 2.2-mod-r2-CUDA9 in Windows 8.1 for LYRA2RE2 mostly mining vertcoin on my own P2Pool node or occasionally the LYRA2RE2 algo port at Miningpoolhub which switches between mona and vertcoin based on profitability and difficulty. This ccminer is a Nanashi version available here:

https://github.com/Nanashi-Meiyo-Meijin/ccminer/releases

I currently use 1060 6GB (5 of), 1070 (4 of) and 1080 (1 of) and all of them are set to core +120, mem -500, powerlimit 105% using MSI afterburner.

The 1060s hash at around 26mh/s, the 1070s at around 40mh/s and the 1080 at around 52mh/s. My total varies between 345mh/s and 350mh/s.

I'm pretty sure that is quite a bit better than the tpruvot ccminer for Lyra2RE2 specifically, I have never used it for any other algorithms. If I want to mine Neoscrypt I use the Klaust version, but for anything else - for stability, reliability, etc I use tpruvot. Alexis seems to do better at some algorithms but I find it to be unstable, or it's reported hash-rate isn't actually accepted as being as high at whatever pool.



for lyra2v2 use ccminer alexis78.... 1060 6gb - around 27 tdp 70 OC 200, 1080ti tdp 65 oc 110 around 61-65
member
Activity: 83
Merit: 10
Is there a limit of GPUs when using ccMiner ?

I have a rig with 18 GPUs and the last 2 are giving an error when starting ccMiner.

[2017-12-09 15:29:09] GPU #-26224: unable to query application clocks
[2017-12-09 15:29:09] GPU #21872: unable to query application clocks


full member
Activity: 374
Merit: 101
I'm using a miner called ccminer 2.2-mod-r2-CUDA9 in Windows 8.1 for LYRA2RE2 mostly mining vertcoin on my own P2Pool node or occasionally the LYRA2RE2 algo port at Miningpoolhub which switches between mona and vertcoin based on profitability and difficulty. This ccminer is a Nanashi version available here:

https://github.com/Nanashi-Meiyo-Meijin/ccminer/releases

Did you try Palgin ccminer?
https://github.com/palginpav/ccminer/releases

In my mixed rig (1060+1070+1080ti) it performs better.
(lyra2rev2)
sr. member
Activity: 372
Merit: 250
The road of excess leads to the palace of wisdom
Does anyone know if mining Vert coin and Mona coin with ccminer 2.2.3 and suprnova require more GPU core clock, memory clock, or both?

For eg. I know it's more important, for Ethereum, to have as high memory clock as possible while with Decred, last I heard, you lower memory clocks because Decred only uses the core.

So what's the best way to go about with Mona and Vert Using Nvidia GTX 1070s?

I'm using a miner called ccminer 2.2-mod-r2-CUDA9 in Windows 8.1 for LYRA2RE2 mostly mining vertcoin on my own P2Pool node or occasionally the LYRA2RE2 algo port at Miningpoolhub which switches between mona and vertcoin based on profitability and difficulty. This ccminer is a Nanashi version available here:

https://github.com/Nanashi-Meiyo-Meijin/ccminer/releases

I currently use 1060 6GB (5 of), 1070 (4 of) and 1080 (1 of) and all of them are set to core +120, mem -500, powerlimit 105% using MSI afterburner.

The 1060s hash at around 26mh/s, the 1070s at around 40mh/s and the 1080 at around 52mh/s. My total varies between 345mh/s and 350mh/s.

I'm pretty sure that is quite a bit better than the tpruvot ccminer for Lyra2RE2 specifically, I have never used it for any other algorithms. If I want to mine Neoscrypt I use the Klaust version, but for anything else - for stability, reliability, etc I use tpruvot. Alexis seems to do better at some algorithms but I find it to be unstable, or it's reported hash-rate isn't actually accepted as being as high at whatever pool.

member
Activity: 82
Merit: 10
Dear Dev,
What should I change to be able to build the miner on Visual Studio 2017?
on 2013 working fine but on 2017 and many errors.
newbie
Activity: 31
Merit: 0
Just a note for those if you with cuda 8 installed, it won't build unless you edit the '-with-cuda=/usr/local/cuda' part in configure.sh

It took me ages to figure out why it wouldn't build, hopefully this helps anyone else with the same issue!
jr. member
Activity: 34
Merit: 2
Good Morning, someone can help-me?

I'm have 2x 1060 and 2 1070 using Simplemining.

I config the miner to use lyra2rev2, but don't work, get error.
Already checked my worker, and lines configuration a milion times.

Help-me?


legendary
Activity: 1232
Merit: 1247
When mining lyra2rev2 with multiple GTX 1070 it works for some hours and then suddenly fails with
"unspecified launch failure"
I have already lowered the intensity and power level  ....
Any ideas?
legendary
Activity: 1484
Merit: 1082
ccminer/cpuminer developer
was for a few alien pools... and keccak which didnt had really a standard 128 vs 256 regarding the pool :p

-m 0.5 = -f 2 but well... integers
legendary
Activity: 1470
Merit: 1114
-f, (and -m) will change nothing for you.. except doing problems -f 2 will reject half the shares, -m 2 will not submit half

What about -m 0.5? Will that submit twice as many? Wink

I have no idea what the real puspose is, probably a relic from the early days of Bitcoin. Certain reject reasons
will trigger an automatic change to -f but they never helped in my experience.

There may have been a time where a pool was misconfigured for a time and required -f to get shares accepted,
but then the pool was fixed and it was no longer needed.
legendary
Activity: 1484
Merit: 1082
ccminer/cpuminer developer
-f, (and -m) will change nothing for you.. except doing problems -f 2 will reject half the shares, -m 2 will not submit half
full member
Activity: 157
Merit: 100
Out of the box is where I live
I have tried cryptonight and my hash rate is almost one third of what I used to have with the previous version. I have also tried lyra2rev2 and I couldn't even start the miner, I get: Segmentation fault (core dumped)
full member
Activity: 157
Merit: 100
Out of the box is where I live
Thanks, it was right in my face Smiley

I tried to compile it and everything went fine, now trying it with cryptonight to compare with the previous version...
newbie
Activity: 7
Merit: 0
hello all,

I'm facing a similar issue. I have Ubuntu 16.04 running with CUDA 9. I'm trying to compile the latest version of ccminer and I get two errors:

/usr/local/cuda/bin/nvcc  -I. -I/usr/local/cuda/include -O3 -lineno -Xcompiler -Wall  -D_FORCE_INLINES - gencode=arch=compute_20,code=\"sm_50,compute_50\" -o scrypt/salsa_kernel.o -c scrypt/salsa_kernel.cu
nvcc fatal   : A single input file is required for a non-link phase when an outputfile is specified
Makefile:2253: recipe for target 'scrypt/salsa_kernel.o' failed
make[2]: *** [scrypt/salsa_kernel.o] Error 1

make[2]: Leaving directory '/home/laurent/Desktop/Mining/ccminer-1.8.2-tpruvot'
Makefile:1757: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/home/laurent/Desktop/Mining/ccminer-1.8.2-tpruvot'
Makefile:578: recipe for target 'all' failed
make: *** [all] Error 2

In my makefile.am I have:
nvcc_ARCH  = -gencode=arch=compute_50,code=\"sm_50,compute_50\"
nvcc_ARCH += -gencode=arch=compute_52,code=\"sm_52,compute_52\"
#nvcc_ARCH += -gencode=arch=compute_35,code=\"sm_35,compute_35\"
#nvcc_ARCH += -gencode=arch=compute_30,code=\"sm_30,compute_30\"
#nvcc_ARCH += -gencode=arch=compute_20,code=\"sm_21,compute_20\"

the compute_20 is not enabled but I see later on:
scrypt/salsa_kernel.o: scrypt/salsa_kernel.cu
$(NVCC) $(JANSSON_INCLUDES) -I. @CUDA_INCLUDES@ @CUDA_CFLAGS@ - gencode=arch=compute_20,code=\"sm_21,compute_20\" -o $@ -c $<

Somehow it seems to force the compute_20 even if it's in comment at the start of the file.

Any idea of what I should do?

Thanks

[/quote]
You already have CUDA 9 installed.
I mean the cuda 9 version of ccminer.
https://github.com/tpruvot/ccminer/archive/cuda-9.zip
[/quote]

Follow what Schleicher said that should fix your issue.. thanks again Schleicher!!!
full member
Activity: 157
Merit: 100
Out of the box is where I live
hello all,

I'm facing a similar issue. I have Ubuntu 16.04 running with CUDA 9. I'm trying to compile the latest version of ccminer and I get two errors:

/usr/local/cuda/bin/nvcc  -I. -I/usr/local/cuda/include -O3 -lineno -Xcompiler -Wall  -D_FORCE_INLINES - gencode=arch=compute_20,code=\"sm_50,compute_50\" -o scrypt/salsa_kernel.o -c scrypt/salsa_kernel.cu
nvcc fatal   : A single input file is required for a non-link phase when an outputfile is specified
Makefile:2253: recipe for target 'scrypt/salsa_kernel.o' failed
make[2]: *** [scrypt/salsa_kernel.o] Error 1

make[2]: Leaving directory '/home/laurent/Desktop/Mining/ccminer-1.8.2-tpruvot'
Makefile:1757: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/home/laurent/Desktop/Mining/ccminer-1.8.2-tpruvot'
Makefile:578: recipe for target 'all' failed
make: *** [all] Error 2

In my makefile.am I have:
nvcc_ARCH  = -gencode=arch=compute_50,code=\"sm_50,compute_50\"
nvcc_ARCH += -gencode=arch=compute_52,code=\"sm_52,compute_52\"
#nvcc_ARCH += -gencode=arch=compute_35,code=\"sm_35,compute_35\"
#nvcc_ARCH += -gencode=arch=compute_30,code=\"sm_30,compute_30\"
#nvcc_ARCH += -gencode=arch=compute_20,code=\"sm_21,compute_20\"

the compute_20 is not enabled but I see later on:
scrypt/salsa_kernel.o: scrypt/salsa_kernel.cu
$(NVCC) $(JANSSON_INCLUDES) -I. @CUDA_INCLUDES@ @CUDA_CFLAGS@ - gencode=arch=compute_20,code=\"sm_21,compute_20\" -o $@ -c $<

Somehow it seems to force the compute_20 even if it's in comment at the start of the file.

Any idea of what I should do?

Thanks
Pages:
Jump to: