[ANN] ccminer 2.3 - opensource - GPL (tpruvot)

[groove_master]

I tried running the ccminer x64 for equihash, and the max gpu load was 90-91%. Is it not really compatible yet, or I need to add some tweaks into the .bat file?

The intensity setting doesn't seem to work.

[1713263871]

1713263871

[1713263871]

1713263871

[1713263871]

1713263871

[1713263871]

1713263871

[NameTaken]

I tried running the ccminer x64 for equihash, and the max gpu load was 90-91%. Is it not really compatible yet, or I need to add some tweaks into the .bat file?

Ccminer is unoptimized for Equihash.

[groove_master]

I tried running the ccminer x64 for equihash, and the max gpu load was 90-91%. Is it not really compatible yet, or I need to add some tweaks into the .bat file?

Ccminer is unoptimized for Equihash.

That's what I thought, thanks.

[santan]

I tried running the ccminer x64 for equihash, and the max gpu load was 90-91%. Is it not really compatible yet, or I need to add some tweaks into the .bat file?

Ccminer is unoptimized for Equihash.

Try the switch .............   -t 2 ......  if you have 1 card
 or multiply by 2 with the total number of cards in your rig.... to have double thread ..... like .... -t 8.... for a rig with 4 gpu.
Most likely all the miners are using this approach inside.....

[santan]

@Epsylon3 .. @pallas........Or Anybody else, please help me .........

I wanted to add share info into a file (only for the submitted shares)......... Currently i succeeded to write the share diff only into a file.
How can we add.......  blockheader info too.... or their individual parts, ....

sctx->xnonce1, sctx->xnonce2, merkle_root, work->nonces, sctx->job.coinbase, sctx->job.ntime, sctx->job.prevhash...... into the output file...

Code:

//===Util.cpp=======================================
void filelog(FILE *file1, const char *fmt, ...)
{
va_list ap;
va_start(ap, fmt);
char *f; const time_t now = time(NULL);
struct tm tm;
localtime_r(&now, &tm);
f = (char*)alloca(40 + (int)strlen(fmt) + 2);
sprintf(f, "[%d-%02d-%02d %02d:%02d:%02d]%s %s%s\n",
tm.tm_year + 1900, tm.tm_mon + 1, tm.tm_mday,
tm.tm_hour, tm.tm_min, tm.tm_sec,
"", fmt, ""
);
vfprintf(file1, f, ap); /* write to file */

va_end(ap);
}
//======ccminer.cpp===================================
filelog(file1, "accepted: %lu/%lu (%s)",
p->accepted_count, p->accepted_count + p->rejected_count, suppl);
fflush(file1);

[DrStein99]

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.

[lankyman]

so much to read in this thread, and cant see an actual answer as to what this message is?
Stratum extranonce answer id was not correct!

i get this using klaust ccminer and algo lyre2v2

[cyberdeath]

Please add support for 19x gpu systems, it is not possible to mine on b250 mining expert mobo (
thanks

[DumaxFr]

Hello,

Is ccminer 2.2.4 ready for linux or windows only ?
I would like to mine -phi algo

There is a better phi miner by anorganix.

if read tpruvot commits, you can see that phi in 2.2.4 was imported from anorganix's one

[DumaxFr]

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

[konqueror]

Hello,

Is ccminer 2.2.4 ready for linux or windows only ?
I would like to mine -phi algo

There is a better phi miner by anorganix.

if read tpruvot commits, you can see that phi in 2.2.4 was imported from anorganix's one

This does not mean both have the same speed
The anorganix performes better, at least for me but of course you can make your own tests

[caleb150]

Where can I get the updated version of ccminer 2.2.5?

[scryptr]

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

[cyberdeath]

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.

[monrad]

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?

[firemylasers]

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<RB, SM, SSM, THREADS, PACKER>::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<RB, SM, SSM, THREADS, PACKER>::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<RB, SM, SSM, THREADS, PACKER>::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<RB, SM, SSM, THREADS, PACKER>::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<RB, SM, SSM, THREADS, PACKER>::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<RB, SM, SSM, THREADS, PACKER>::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<RB, SM, SSM, THREADS, PACKER>::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<RB, SM, SSM, THREADS, PACKER>::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<RB, SM, SSM, THREADS, PACKER>::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<RB, SM, SSM, THREADS, PACKER>::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<RB, SM, SSM, THREADS, PACKER>::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.

[santan]

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

[cyberdeath]

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.

[cyberdeath]

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. 

[knohult]

Welcome to the discussion thread for my ccminer fork.

https://imgur.com/BaLuHQy

What´s the boo and yes about?