[ANN] ccminer 2.3 - opensource - GPL (tpruvot) - page 13.

joblo

legendary

Activity: 1470

Merit: 1114

Quote from: scryptr on February 09, 2018, 06:29:42 PM

Quote from: pallas on February 09, 2018, 06:16:48 PM

Quote from: scryptr on February 09, 2018, 01:05:33 PM

Quote from: monrad on February 07, 2018, 06:37:54 PM

Guys, is this legit? https://github.com/MSFTserver/ccminer/releases

It seems to be released by tpruvot but on MSFTserver repository... and description doesn't seem to be from him. What do you guys think?

I CLONED THE REPOSITORY AND IT COMPILED--

Afterwards, I mined the new RavenCOIN (RVN) algorithm, x16r, on "yiimp.eu:3666". The binary for the wallet-qt synchronized rapidly on my Win7 x64 system, and received coins on payout.

CCminer 2.2.5 compiled on my Ubuntu 14.04 system under CUDA 8 (with both current patches). Intensity is adjustable; I had to lower it to 16 for CCminer 2.2.5 to run on my 6x 750ti rig. The default intensity is 19.

The notes read that CCminer 2.2.5 is a CUDA 9 creation. There is no CUDA 9 toolkit for Ubuntu 14.04. My 750ti rig kept crashing with a memory error in "line 41". I may post a screen capture of the error later.

Does anybody know how to squeeze CUDA 9 onto Ubuntu 14.04? Is there some code I could change in "line 41"? Thanks... --scryptr

First, you should use cuda 9.1.
Second, why don't you use the latest LTS? 14.04 is so old!

I AM RUNNING MODIFIED ETHOS--

I have also installed Excavator and XMR-STAK. EthOS is a customized 14.04 release, and it does well with few errors. It is very stable and reliable. --scryptr

I think you'd have to compile cuda 9 and a compatible driver for 14.04, but source code isn't open.

scryptr

legendary

Activity: 1797

Merit: 1028

Quote from: pallas on February 09, 2018, 06:16:48 PM

Quote from: scryptr on February 09, 2018, 01:05:33 PM

Quote from: monrad on February 07, 2018, 06:37:54 PM

Guys, is this legit? https://github.com/MSFTserver/ccminer/releases

It seems to be released by tpruvot but on MSFTserver repository... and description doesn't seem to be from him. What do you guys think?

I CLONED THE REPOSITORY AND IT COMPILED--

Afterwards, I mined the new RavenCOIN (RVN) algorithm, x16r, on "yiimp.eu:3666". The binary for the wallet-qt synchronized rapidly on my Win7 x64 system, and received coins on payout.

CCminer 2.2.5 compiled on my Ubuntu 14.04 system under CUDA 8 (with both current patches). Intensity is adjustable; I had to lower it to 16 for CCminer 2.2.5 to run on my 6x 750ti rig. The default intensity is 19.

The notes read that CCminer 2.2.5 is a CUDA 9 creation. There is no CUDA 9 toolkit for Ubuntu 14.04. My 750ti rig kept crashing with a memory error in "line 41". I may post a screen capture of the error later.

Does anybody know how to squeeze CUDA 9 onto Ubuntu 14.04? Is there some code I could change in "line 41"? Thanks... --scryptr

First, you should use cuda 9.1.
Second, why don't you use the latest LTS? 14.04 is so old!

I AM RUNNING MODIFIED ETHOS--

I have also installed Excavator and XMR-STAK. EthOS is a customized 14.04 release, and it does well with few errors. It is very stable and reliable. --scryptr

cyberdeath

newbie

Activity: 82

Merit: 0

Quote from: cyberdeath on February 09, 2018, 05:42:31 PM

The same config with 16 cards + without oc work well. so i don't think that there is trouble with intesivity.

Checked also ccminer on 18gpu config situation is same.
Checked also nicehash excavator with 18 cards works well but with 19 gpu config it dies )

pallas

legendary

Activity: 2716

Merit: 1094

Black Belt Developer

Quote from: scryptr on February 09, 2018, 01:05:33 PM

Quote from: monrad on February 07, 2018, 06:37:54 PM

Guys, is this legit? https://github.com/MSFTserver/ccminer/releases

It seems to be released by tpruvot but on MSFTserver repository... and description doesn't seem to be from him. What do you guys think?

I CLONED THE REPOSITORY AND IT COMPILED--

Afterwards, I mined the new RavenCOIN (RVN) algorithm, x16r, on "yiimp.eu:3666". The binary for the wallet-qt synchronized rapidly on my Win7 x64 system, and received coins on payout.

CCminer 2.2.5 compiled on my Ubuntu 14.04 system under CUDA 8 (with both current patches). Intensity is adjustable; I had to lower it to 16 for CCminer 2.2.5 to run on my 6x 750ti rig. The default intensity is 19.

The notes read that CCminer 2.2.5 is a CUDA 9 creation. There is no CUDA 9 toolkit for Ubuntu 14.04. My 750ti rig kept crashing with a memory error in "line 41". I may post a screen capture of the error later.

Does anybody know how to squeeze CUDA 9 onto Ubuntu 14.04? Is there some code I could change in "line 41"? Thanks... --scryptr

First, you should use cuda 9.1.
Second, why don't you use the latest LTS? 14.04 is so old!

cyberdeath

newbie

Activity: 82

Merit: 0

The same config with 16 cards + without oc work well. so i don't think that there is trouble with intesivity.

chrysophylax

legendary

Activity: 2912

Merit: 1091

--- ChainWorks Industries ---

Quote from: cyberdeath on February 09, 2018, 05:04:02 PM

Quote from: cyberdeath on February 09, 2018, 06:34:41 AM

Quote from: santan on February 08, 2018, 03:47:42 PM

Quote from: cyberdeath on February 08, 2018, 12:16:26 PM

I was not able to compile with 19 gpu's, i've got a lot of errors. 16 gpu's version compiled without any troubles.
I htink tpruvot must check this situation. Angry

You need to modify 2 more files...... check here.... https://github.com/tpruvot/ccminer/pull/54
It build without any error for me..... But i don't have 19 GPU rig to test.... Sad

Please try and let us know.

Thanks, just compiled x32 x64 versions without any troubles.
But haven't tested yet< because i have removed cards from rig.

Ccminer is very unstable with 19 gpu's and die very fast on lyra2z and skein algo, so ccminer is not usable with 19gpu's. I think only tpruvot can find solution(((
Strange thing, but on both algos miner dies on gpu0 but in case when i am using 16 gpu config, there is no troubles with gpu0 on ccminer x64 ver and x32 ver have different gpu troubels. In my situration gpu0 is p104-100

GPU #0: SM 6.1 P104-100 @ 1734 MHz (MEM 5005)
GPU #1: SM 6.1 Gigabyte GTX 1080 Ti @ 1633 MHz (MEM 5505)
GPU #2: SM 6.1 ASUS GTX 1060 3GB @ 1785 MHz (MEM 4004)
GPU #3: SM 6.1 MSI GTX 1080 @ 1823 MHz (MEM 5005)
GPU #4: SM 6.1 ASUS GTX 1060 3GB @ 1785 MHz (MEM 4004)
GPU #5: SM 6.1 P104-100 @ 1734 MHz (MEM 5005)
GPU #6: SM 6.1 ASUS GTX 1060 3GB @ 1785 MHz (MEM 4004)
GPU #7: SM 6.1 MSI GTX 1080 @ 1823 MHz (MEM 5005)
GPU #8: SM 6.1 P104-100 @ 1734 MHz (MEM 5005)
GPU #9: SM 6.1 MSI GTX 1080 @ 1823 MHz (MEM 5005)
GPU #10: SM 6.1 P104-100 @ 1734 MHz (MEM 5005)
GPU #11: SM 6.1 MSI GTX 1080 @ 1823 MHz (MEM 5005)
GPU #12: SM 6.1 P104-100 @ 1734 MHz (MEM 5005)
GPU #13: SM 6.1 Gigabyte GTX 1080 Ti @ 1633 MHz (MEM 5505)
GPU #14: SM 6.1 Gigabyte GTX 1080 Ti @ 1633 MHz (MEM 5505)
GPU #15: SM 6.1 Gigabyte GTX 1080 Ti @ 1633 MHz (MEM 5505)
GPU #16: SM 6.1 MSI GTX 1080 @ 1823 MHz (MEM 5005)
GPU #17: SM 6.1 P104-100 @ 1734 MHz (MEM 5005)
GPU #18: SM 6.1 Gigabyte GTX 1080 Ti @ 1633 MHz (MEM 5505)

Tried zm miner 0.5.8 it is awesome and works well. Tried ewbf cuda miner it is peace of shit.

It sounds to me like your intensities may be completely off.

A huge mix of cards means that they need to be set individually, even though ccminer-tpruvot may try and auto adjust these intensities for each card.

Just a thought, but it is what it seems like.

#crysx

cyberdeath

newbie

Activity: 82

Merit: 0

Quote from: cyberdeath on February 09, 2018, 06:34:41 AM

Quote from: santan on February 08, 2018, 03:47:42 PM

Quote from: cyberdeath on February 08, 2018, 12:16:26 PM

I was not able to compile with 19 gpu's, i've got a lot of errors. 16 gpu's version compiled without any troubles.
I htink tpruvot must check this situation. Angry

You need to modify 2 more files...... check here.... https://github.com/tpruvot/ccminer/pull/54
It build without any error for me..... But i don't have 19 GPU rig to test.... Sad

Please try and let us know.

Thanks, just compiled x32 x64 versions without any troubles.
But haven't tested yet< because i have removed cards from rig.

Ccminer is very unstable with 19 gpu's and die very fast on lyra2z and skein algo, so ccminer is not usable with 19gpu's. I think only tpruvot can find solution(((
Strange thing, but on both algos miner dies on gpu0 but in case when i am using 16 gpu config, there is no troubles with gpu0 on ccminer x64 ver and x32 ver have different gpu troubels. In my situration gpu0 is p104-100

GPU #0: SM 6.1 P104-100 @ 1734 MHz (MEM 5005)
GPU #1: SM 6.1 Gigabyte GTX 1080 Ti @ 1633 MHz (MEM 5505)
GPU #2: SM 6.1 ASUS GTX 1060 3GB @ 1785 MHz (MEM 4004)
GPU #3: SM 6.1 MSI GTX 1080 @ 1823 MHz (MEM 5005)
GPU #4: SM 6.1 ASUS GTX 1060 3GB @ 1785 MHz (MEM 4004)
GPU #5: SM 6.1 P104-100 @ 1734 MHz (MEM 5005)
GPU #6: SM 6.1 ASUS GTX 1060 3GB @ 1785 MHz (MEM 4004)
GPU #7: SM 6.1 MSI GTX 1080 @ 1823 MHz (MEM 5005)
GPU #8: SM 6.1 P104-100 @ 1734 MHz (MEM 5005)
GPU #9: SM 6.1 MSI GTX 1080 @ 1823 MHz (MEM 5005)
GPU #10: SM 6.1 P104-100 @ 1734 MHz (MEM 5005)
GPU #11: SM 6.1 MSI GTX 1080 @ 1823 MHz (MEM 5005)
GPU #12: SM 6.1 P104-100 @ 1734 MHz (MEM 5005)
GPU #13: SM 6.1 Gigabyte GTX 1080 Ti @ 1633 MHz (MEM 5505)
GPU #14: SM 6.1 Gigabyte GTX 1080 Ti @ 1633 MHz (MEM 5505)
GPU #15: SM 6.1 Gigabyte GTX 1080 Ti @ 1633 MHz (MEM 5505)
GPU #16: SM 6.1 MSI GTX 1080 @ 1823 MHz (MEM 5005)
GPU #17: SM 6.1 P104-100 @ 1734 MHz (MEM 5005)
GPU #18: SM 6.1 Gigabyte GTX 1080 Ti @ 1633 MHz (MEM 5505)

Tried zm miner 0.5.8 it is awesome and works well. Tried ewbf cuda miner it is peace of shit.

scryptr

legendary

Activity: 1797

Merit: 1028

Quote from: monrad on February 07, 2018, 06:37:54 PM

Guys, is this legit? https://github.com/MSFTserver/ccminer/releases

It seems to be released by tpruvot but on MSFTserver repository... and description doesn't seem to be from him. What do you guys think?

I CLONED THE REPOSITORY AND IT COMPILED--

Afterwards, I mined the new RavenCOIN (RVN) algorithm, x16r, on "yiimp.eu:3666". The binary for the wallet-qt synchronized rapidly on my Win7 x64 system, and received coins on payout.

CCminer 2.2.5 compiled on my Ubuntu 14.04 system under CUDA 8 (with both current patches). Intensity is adjustable; I had to lower it to 16 for CCminer 2.2.5 to run on my 6x 750ti rig. The default intensity is 19.

The notes read that CCminer 2.2.5 is a CUDA 9 creation. There is no CUDA 9 toolkit for Ubuntu 14.04. My 750ti rig kept crashing with a memory error in "line 41". I may post a screen capture of the error later.

Does anybody know how to squeeze CUDA 9 onto Ubuntu 14.04? Is there some code I could change in "line 41"? Thanks... --scryptr

cyberdeath

newbie

Activity: 82

Merit: 0

Quote from: santan on February 08, 2018, 03:47:42 PM

Quote from: cyberdeath on February 08, 2018, 12:16:26 PM

I was not able to compile with 19 gpu's, i've got a lot of errors. 16 gpu's version compiled without any troubles.
I htink tpruvot must check this situation. Angry

You need to modify 2 more files...... check here.... https://github.com/tpruvot/ccminer/pull/54
It build without any error for me..... But i don't have 19 GPU rig to test.... Sad

Please try and let us know.

Thanks, just compiled x32 x64 versions without any troubles.
But haven't tested yet< because i have removed cards from rig.

bensam1231

legendary

Activity: 1764

Merit: 1024

Quote from: scryptr on February 07, 2018, 12:05:26 PM

Quote from: DumaxFr on February 06, 2018, 09:59:01 PM

Quote from: DrStein99 on February 06, 2018, 03:10:34 AM

Quote from: scryptr on January 31, 2018, 01:12:46 AM

I'VE NOTICED THAT INTENSITY SETTINGS DON'T WORK--

In the most recent versions of CCminer (2.2+), intensity settings appear to be ignored, and a default setting is applied. Other users have posted about not being able to disable auto-tuning on algos like Scrypt pr CryptoNight.

Frankly, default or auto-tune settings are often the best, but I have noticed that some older tuning parameters are ignored. --scryptr

I have only been wrestling with ccminer for the last 4 hours, and can tell you for certain, every combination of INTENSITY parameter I threw at it, was ignored. The default settings are NOT the fastest for my cards. I have also been spending this whole time trying to learn this crazy "launch-config" parameter, digging through documents to find which of the 1,000 different technical specifications ccminer needs for me to accept. It's parameter list is confusing to say the least.

Intensity is hardcoded in implementations of many algos (for ccminer 2.2.4).
It's a good thing to avoid you posting on youtube that your rig is on fire

I DON'T POST ON YOUTUBE--

But I do enjoy custom-tuning my rigs. Perhaps Epsylon3 could "star" (mark with asterisk) the algorithms affected in his documentation. Then, make a note of explanation.

Scrypt, Scrypt-N, BoolBerry, CryptoNight all had difficult-to-master tuning parameters. Even NeoScrypt could be trouble as the code changed with optimization. Spending an hour on un-necessary, non-effective tuning could be avoided with a few documentation notes. --scryptr

Agreed, also intensity will NOT cause hardware failures. If you have a system that starts on fire as long as the GPU is operating within spec you've done something wrong. Mining software has never once been responsible for any miner fires, it's always people using inferior hardware or halfhazard setups, like daisy chaining splitters. Hardware will fail regardless as manufacturers usually don't test them super rigorously, which is why one of the secrets of mining is knowing the right brands to buy.

I find it hard to believe Epsylon would intentionally hardcode in a intensity value unless it's to artificially reduce performance of his miner. Tweaking intensity has been a staple of good mining for a long time.

santan

member

Activity: 102

Merit: 11

Quote from: cyberdeath on February 08, 2018, 12:16:26 PM

I was not able to compile with 19 gpu's, i've got a lot of errors. 16 gpu's version compiled without any troubles.
I htink tpruvot must check this situation. Angry

You need to modify 2 more files...... check here.... https://github.com/tpruvot/ccminer/pull/54
It build without any error for me..... But i don't have 19 GPU rig to test.... Sad

Please try and let us know.

knohult

newbie

Activity: 11

Merit: 0

Quote from: Epsylon3 on September 05, 2014, 02:00:05 AM

Welcome to the discussion thread for my ccminer fork.

https://imgur.com/BaLuHQy

What´s the boo and yes about?

cyberdeath

newbie

Activity: 82

Merit: 0

I was not able to compile with 19 gpu's, i've got a lot of errors. 16 gpu's version compiled without any troubles.
I htink tpruvot must check this situation. Angry

cyberdeath

newbie

Activity: 82

Merit: 0

Quote from: santan on February 08, 2018, 03:54:58 AM

Quote from: cyberdeath on February 07, 2018, 12:50:45 PM

Please add 17gpu+ mining support
Ccminer works well with 16 gpu system
But when adding 17's card, card identified incorrectly.
.......................
...........................
Please fix such issues with 17+ gpu's Thanks.

Change this Line in .......... Miner.h.........and Build new executable..... Enjoy!!

Code:

#define MAX_GPUS 16

Thanks, compiling.
But i think it will be better if tpruvot will modify src so every new release will have support for 19 gpus.
Because there are a lot of motherboards Asus b250 mining expert are on market.
So logically will be good if ccminer will support 19 gpu's by default.

santan

member

Activity: 102

Merit: 11

Quote from: cyberdeath on February 07, 2018, 12:50:45 PM

Please add 17gpu+ mining support
Ccminer works well with 16 gpu system
But when adding 17's card, card identified incorrectly.
.......................
...........................
Please fix such issues with 17+ gpu's Thanks.

Change this Line in .......... Miner.h.........and Build new executable..... Enjoy!!

Code:

#define MAX_GPUS 16

firemylasers

newbie

Activity: 3

Merit: 0

I can't get any recent version of ccminer to compile on OSX. I have previously successfully compiled 1.7.6-r10-nanashi, but multiple attempts at compiling several versions of v2.2.4 (windows source, linux source, windows release source) and someone else's fork of v2.2 have all failed with the following errors:

Code:

equi/cuda_equi.cu(2040): error: no instance of constructor "rt_error::rt_error" matches the argument list
            argument types are: (char [512])
          detected during instantiation of "void eq_cuda_context::solve(const char *, unsigned int, const char *, unsigned int, fn_cancel, fn_solution, fn_hashdone) [with RB=9U, SM=1248U, SSM=12U, THREADS=640U, PACKER=packer_cantor]" 
(2124): here

equi/cuda_equi.cu(2042): error: no instance of constructor "rt_error::rt_error" matches the argument list
            argument types are: (char [512])
          detected during instantiation of "void eq_cuda_context::solve(const char *, unsigned int, const char *, unsigned int, fn_cancel, fn_solution, fn_hashdone) [with RB=9U, SM=1248U, SSM=12U, THREADS=640U, PACKER=packer_cantor]" 
(2124): here

equi/cuda_equi.cu(2061): error: no instance of constructor "rt_error::rt_error" matches the argument list
            argument types are: (char [512])
          detected during instantiation of "void eq_cuda_context::solve(const char *, unsigned int, const char *, unsigned int, fn_cancel, fn_solution, fn_hashdone) [with RB=9U, SM=1248U, SSM=12U, THREADS=640U, PACKER=packer_cantor]" 
(2124): here

equi/cuda_equi.cu(1966): error: no instance of constructor "rt_error::rt_error" matches the argument list
            argument types are: (char [512])
          detected during instantiation of "eq_cuda_context::eq_cuda_context(int, int) [with RB=9U, SM=1248U, SSM=12U, THREADS=640U, PACKER=packer_cantor]" 
(2124): here

equi/cuda_equi.cu(1967): error: no instance of constructor "rt_error::rt_error" matches the argument list
            argument types are: (char [512])
          detected during instantiation of "eq_cuda_context::eq_cuda_context(int, int) [with RB=9U, SM=1248U, SSM=12U, THREADS=640U, PACKER=packer_cantor]" 
(2124): here

equi/cuda_equi.cu(1968): error: no instance of constructor "rt_error::rt_error" matches the argument list
            argument types are: (char [512])
          detected during instantiation of "eq_cuda_context::eq_cuda_context(int, int) [with RB=9U, SM=1248U, SSM=12U, THREADS=640U, PACKER=packer_cantor]" 
(2124): here

equi/cuda_equi.cu(2001): error: no instance of constructor "rt_error::rt_error" matches the argument list
            argument types are: (char [512])
          detected during instantiation of "eq_cuda_context::eq_cuda_context(int, int) [with RB=9U, SM=1248U, SSM=12U, THREADS=640U, PACKER=packer_cantor]" 
(2124): here

equi/cuda_equi.cu(2002): error: no instance of constructor "rt_error::rt_error" matches the argument list
            argument types are: (char [512])
          detected during instantiation of "eq_cuda_context::eq_cuda_context(int, int) [with RB=9U, SM=1248U, SSM=12U, THREADS=640U, PACKER=packer_cantor]" 
(2124): here

equi/cuda_equi.cu(2003): error: no instance of constructor "rt_error::rt_error" matches the argument list
            argument types are: (char [512])
          detected during instantiation of "eq_cuda_context::eq_cuda_context(int, int) [with RB=9U, SM=1248U, SSM=12U, THREADS=640U, PACKER=packer_cantor]" 
(2124): here

equi/cuda_equi.cu(2108): error: no instance of constructor "rt_error::rt_error" matches the argument list
            argument types are: (char [512])
          detected during instantiation of "void eq_cuda_context::freemem() [with RB=9U, SM=1248U, SSM=12U, THREADS=640U, PACKER=packer_cantor]" 
(2124): here

equi/cuda_equi.cu(2111): error: no instance of constructor "rt_error::rt_error" matches the argument list
            argument types are: (char [512])
          detected during instantiation of "void eq_cuda_context::freemem() [with RB=9U, SM=1248U, SSM=12U, THREADS=640U, PACKER=packer_cantor]" 
(2124): here

I've been unable to find any explanation online for these errors. A look through the source code was unproductive outside of revealing the origin of rt_error (equi/eqcuda.hpp appears to remap std::runtime_error to rt_error, not that this tells me much of anything). I've tried using different CUDA versions on the off chance that this was related to that, but 8.0, 9.0, and 9.1 all give the same error...

I'm honestly not sure how the heck to resolve the issue at this point. Does anyone have any ideas? Some help would be greatly appreciated. I've gone through the past 30 pages of the thread looking for answers and have found nothing helpful.

monrad

newbie

Activity: 10

Merit: 0

Guys, is this legit? https://github.com/MSFTserver/ccminer/releases

It seems to be released by tpruvot but on MSFTserver repository... and description doesn't seem to be from him. What do you guys think?

cyberdeath

newbie

Activity: 82

Merit: 0

Please add 17gpu+ mining support
Ccminer works well with 16 gpu system
But when adding 17's card, card identified incorrectly.

Here is what we have with ccminer -n on the system with 17 gpu's

c:\miner\Desktop\ccminer-x86-2.2.4-cuda9>ccminer -n
*** ccminer 2.2.4 for nVidia GPUs by tpruvot@github ***
Built with VC++ 2013 and nVidia CUDA SDK 9.0 32-bits

Originally based on Christian Buchner and Christian H. project
Include some kernels from alexis78, djm34, djEzo, tsiv and krnlx.

BTC donation address: 1AJdfCpLWPNoAMDfHF1wD5y8VgKSSTHxPo (tpruvot)

GPU #0: SM 6.1 P104-100 @ 1734 MHz (MEM 5005)
GPU #1: SM 6.1 Gigabyte GTX 1080 Ti @ 1633 MHz (MEM 5505)
GPU #2: SM 6.1 Gigabyte GTX 1080 Ti @ 1633 MHz (MEM 5505)
GPU #3: SM 6.1 MSI GTX 1080 @ 1823 MHz (MEM 5005)
GPU #4: SM 6.1 Gigabyte GTX 1080 Ti @ 1633 MHz (MEM 5505)
GPU #5: SM 6.1 MSI GTX 1080 @ 1823 MHz (MEM 5005)
GPU #6: SM 6.1 ASUS GTX 1060 3GB @ 1785 MHz (MEM 4004)
GPU #7: SM 6.1 MSI GTX 1080 @ 1823 MHz (MEM 5005)
GPU #8: SM 6.1 MSI P104-100 @ 1734 MHz (MEM 5005)
GPU #9: SM 6.1 Gigabyte GTX 1080 Ti @ 1633 MHz (MEM 5505)
GPU #10: SM 6.1 MSI GTX 1080 @ 1823 MHz (MEM 5005)
GPU #11: SM 6.1 GeForce GTX 1080 @ 1823 MHz (MEM 5005)
GPU #12: SM 6.1 P104-100 @ 1734 MHz (MEM 5005)
GPU #13: SM 6.1 Gigabyte P104-100 @ 1734 MHz (MEM 5005)
GPU #14: SM 6.1 P104-100 @ 1734 MHz (MEM 5005)
GPU #15: SM 6.1 GeForce GTX 1080 Ti @ 1633 MHz (MEM 5505)
GPU #0: SM 6.1 P104-100 @ 1734 MHz (MEM 5005)

c:\miner\Desktop\ccminer-x86-2.2.4-cuda9>

17th gpus has id 0
And while i'll try to miner on this sistem i get the following errors

[2018-02-07 09:49:41] Starting on stratum+tcp://pool.bsod.pw:2132
[2018-02-07 09:49:41] NVAPI GPU monitoring enabled.
[2018-02-07 09:49:41] 17 miner threads started, using 'lyra2z' algorithm.
[2018-02-07 09:49:48] Stratum difficulty set to 1 (0.00391)
[2018-02-07 09:49:48] lyra2z block 3856, diff 333.930
[2018-02-07 09:49:48] GPU #0: scanhash_lyra2Z:60 invalid device ordinal

Please fix such issues with 17+ gpu's Thanks.

scryptr

legendary

Activity: 1797

Merit: 1028

Quote from: DumaxFr on February 06, 2018, 09:59:01 PM

Quote from: DrStein99 on February 06, 2018, 03:10:34 AM

Quote from: scryptr on January 31, 2018, 01:12:46 AM

I'VE NOTICED THAT INTENSITY SETTINGS DON'T WORK--

In the most recent versions of CCminer (2.2+), intensity settings appear to be ignored, and a default setting is applied. Other users have posted about not being able to disable auto-tuning on algos like Scrypt pr CryptoNight.

Frankly, default or auto-tune settings are often the best, but I have noticed that some older tuning parameters are ignored. --scryptr

I have only been wrestling with ccminer for the last 4 hours, and can tell you for certain, every combination of INTENSITY parameter I threw at it, was ignored. The default settings are NOT the fastest for my cards. I have also been spending this whole time trying to learn this crazy "launch-config" parameter, digging through documents to find which of the 1,000 different technical specifications ccminer needs for me to accept. It's parameter list is confusing to say the least.

Intensity is hardcoded in implementations of many algos (for ccminer 2.2.4).
It's a good thing to avoid you posting on youtube that your rig is on fire

I DON'T POST ON YOUTUBE--

But I do enjoy custom-tuning my rigs. Perhaps Epsylon3 could "star" (mark with asterisk) the algorithms affected in his documentation. Then, make a note of explanation.

Scrypt, Scrypt-N, BoolBerry, CryptoNight all had difficult-to-master tuning parameters. Even NeoScrypt could be trouble as the code changed with optimization. Spending an hour on un-necessary, non-effective tuning could be avoided with a few documentation notes. --scryptr

caleb150

newbie

Activity: 126

Merit: 0

Where can I get the updated version of ccminer 2.2.5?

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