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

[eruman34]

yes :/ drivers changed something, may be fixed in 2 years, like the 1050 Ti Power readings

Please add 19 gpu support it's been already 1 year
And any chance to do Tensority algoritm?


Thanks/BR

[1715392312]

1715392312

[1715392312]

1715392312

[1715392312]

1715392312

[1715392312]

1715392312

[1715392312]

1715392312

[1715392312]

1715392312

[Yurexxx]

Can somebody compile 2.2.5 buld for cuda 9.2 please?

[Dodo74]

he is an sacmer  RELARIUM (RLM) coin creator !!!!!!!!!!!!!!!

[DumaxFr]

yes :/ drivers changed something, may be fixed in 2 years, like the 1050 Ti Power readings

Please add 19 gpu support it's been already 1 year
And any chance to do Tensority algoritm?


Thanks/BR

Tensority was developped by Bitmain ...
I don't see the reason why a GPU miner would like to implement an ASIC oriented algo

[projenix]

Hello guys,

Just a quick heads up, the latest code in the repo does not compile on my machine (Linux, gcc5, g++7) and gives a bunch of syntax errors related to /include/C++/6/something

I can get you the exact errors when I get back home, just wanted to send the word out first.

Cheers,

[Epsylon3]

try cuda 9.2 if you want latest OS/gcc

*** ccminer 2.2.6 for nVidia GPUs by tpruvot@github ***
    Built with the nVidia CUDA Toolkit 9.2 64-bits

VERSION="18.04 LTS (Bionic Beaver)"

g++ --version
g++ (Ubuntu 7.3.0-16ubuntu3) 7.3.0

gcc --version
gcc (Ubuntu 7.3.0-16ubuntu3) 7.3.0

[CryptoFreedom101]

What is the best miner for Lyra2z, currently?

[danielocdh]

I simply run

Code:

ccminer-x64.exe --benchmark -a cryptonight

My output:

Code:

*** ccminer 2.2.5 for nVidia GPUs by tpruvot@github ***
    Built with VC++ 2013 and nVidia CUDA SDK 9.0 64-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)

[2018-05-30 20:35:47] Using JSON-RPC 2.0
[2018-05-30 20:35:48] NVML GPU monitoring enabled.
[2018-05-30 20:35:48] NVAPI GPU monitoring enabled.
[2018-05-30 20:35:48] GPU #1: Intensity set to 9, 512 threads (32x16)
[2018-05-30 20:35:48] 6 miner threads started, using 'cryptolight' algorithm.
[2018-05-30 20:35:48] GPU #0: Intensity set to 9, 512 threads (32x16)
[2018-05-30 20:35:48] GPU #2: Intensity set to 9, 512 threads (32x16)
[2018-05-30 20:35:48] GPU #4: Intensity set to 9, 512 threads (32x16)
[2018-05-30 20:35:48] GPU #5: Intensity set to 9, 512 threads (32x16)
[2018-05-30 20:35:48] GPU #3: Intensity set to 9, 512 threads (32x16)
[2018-05-30 20:35:59] GPU #5: ASUS GTX 1070, 819.64 H/s
[2018-05-30 20:35:59] GPU #3: Zotac GTX 1070, 791.51 H/s
[2018-05-30 20:35:59] GPU #4: EVGA GTX 1070, 813.49 H/s
[2018-05-30 20:36:08] GPU #5: ASUS GTX 1070, 793.82 H/s
[2018-05-30 20:36:08] Total: 0.00 H/s
[2018-05-30 20:36:09] GPU #3: Zotac GTX 1070, 797.62 H/s
[2018-05-30 20:36:10] GPU #4: EVGA GTX 1070, 730.74 H/s
[2018-05-30 20:36:13] GPU #5: ASUS GTX 1070, 809.25 H/s
[2018-05-30 20:36:13] Total: 0.00 H/s
[2018-05-30 20:36:13] CTRL_C_EVENT received, exiting

My specs:
Celeron G39000
4gb of ram
mobo Z270XP-SLI

Some more info:
I'm able to reproduce with 2 systems with 6x 1070s each, and 1 system with 4x 1060s
I was able to reproduce on a testing system with AMD A6 9500 (GA-AX370-Gaming 5 mobo) and different amounts/combinations of 1060s and 1070s
If I run a single card (-d 0) the "total" is correct, if I run 2 cards (-d 0,1 OR -d 0,5 OR any other combination of cards) the total becomes 0 again

[kgminer]

Hello experts

Could someone please advise on what command line arguments I can use to mine on only 2 Nvidia cards out of 13 total cards(6 AMD+7 Nvidia)

I am trying to use ccminer for the first time

My rig configuration

13 GPUs (7 Nvidia & 6 AMD)
I am planning to use only 2 Nvidia cards for ccminer to mine altcoins and leave rest to claymore to mine dual coins

so claymore would mine on 6 (AMD) + (0 - 5) Nvidia cards

[danielocdh]

Hello experts

Could someone please advise on what command line arguments I can use to mine on only 2 Nvidia cards out of 13 total cards(6 AMD+7 Nvidia)

I am trying to use ccminer for the first time

My rig configuration

13 GPUs (7 Nvidia & 6 AMD)
I am planning to use only 2 Nvidia cards for ccminer to mine altcoins and leave rest to claymore to mine dual coins

so claymore would mine on 6 (AMD) + (0 - 5) Nvidia cards

Use:
ccminer-x64.exe --help
to see all the options
You would end up using:
ccminer-x64.exe -n
to list devices and their number, then use -d with the desired numbers, like:
ccminer-x64.exe -d 0,4
and add the rest of your options to the command

[kgminer]

Hello experts

Could someone please advise on what command line arguments I can use to mine on only 2 Nvidia cards out of 13 total cards(6 AMD+7 Nvidia)

I am trying to use ccminer for the first time

My rig configuration

13 GPUs (7 Nvidia & 6 AMD)
I am planning to use only 2 Nvidia cards for ccminer to mine altcoins and leave rest to claymore to mine dual coins

so claymore would mine on 6 (AMD) + (0 - 5) Nvidia cards

Use:
ccminer-x64.exe --help
to see all the options
You would end up using:
ccminer-x64.exe -n
to list devices and their number, then use -d with the desired numbers, like:
ccminer-x64.exe -d 0,4
and add the rest of your options to the command

Awesome thank you

Also, I am looking to set
1) minimum\max fan speed or static fan speed
2) OC settings for 1060, that would be 600 memory clock and 100 core clock
3) power limit, like in MSI afterburner I use 65 what would be the value of --plimit here

[Larz952002]

Perhaps this has already been gone over but I have searched the web and cannot find a solution.   HMQ1725 keeps giving me illegal memory errors.  I am running 7x1070, all drivers are updated.  I have 68000 virtual memory which was the only fix is did come across online.  I have reseated the cards.  This is the only Algo that gives me this issue.  Is there someone that knows what I need to do to fix this?

[Keko Fdez]

Hi guys!

Maybe this is the wrong place to ask but have a question about CREA mining.

I have started mining the coin like 10 hrs ago using yiimp.eu pool. My rig is 6 GTX 1070 Ti giving 5.1 GH/S and I am using ccminer 2.2.5 which is supposed to be without dev fee.

According to whattomine and crypt0zone I should be getting around 5 coins per hour (later it changed to 4.81) so in 10 hours it should be somewhere near 48-50 but I would happily accept somewhere between 43 and 45 due to pool hashrate fluctuations, rejected shares and console hashrate inaccuracies plus 2% fee from yiimp.eu

So far after 10 hours I have only mined 27.79. So what the hell is going on? Is yiimp taking 50% fees or what am I missing?

Miner is been running stable with no issues.



Also how is it possible that the miner is constantly submitting shares but the are gaps of 25 minutes, 40 minutes even 65 minutes without a single payment to my wallet?



I’m switching coin for the time being and not using yiimp again until this is clarified cos it does seem very doggy.

If anyone can help I would really appreaciate it.

[chup]

Hi guys!

Maybe this is the wrong place to ask but have a question about CREA mining.

I have started mining the coin like 10 hrs ago using yiimp.eu pool. My rig is 6 GTX 1070 Ti giving 5.1 GH/S and I am using ccminer 2.2.5 which is supposed to be without dev fee.

According to whattomine and crypt0zone I should be getting around 5 coins per hour (later it changed to 4.81) so in 10 hours it should be somewhere near 48-50 but I would happily accept somewhere between 43 and 45 due to pool hashrate fluctuations, rejected shares and console hashrate inaccuracies plus 2% fee from yiimp.eu

1. 10 hours is not enough to calculate average earnings.
2. Whattomine is not accurate.
3. To receive pool payment, pool should solve block. But there are other pools also, so they are solving blocks too. Therefore, irregular payment gaps exists.

[Keko Fdez]

Hi guys!

Maybe this is the wrong place to ask but have a question about CREA mining.

I have started mining the coin like 10 hrs ago using yiimp.eu pool. My rig is 6 GTX 1070 Ti giving 5.1 GH/S and I am using ccminer 2.2.5 which is supposed to be without dev fee.

According to whattomine and crypt0zone I should be getting around 5 coins per hour (later it changed to 4.81) so in 10 hours it should be somewhere near 48-50 but I would happily accept somewhere between 43 and 45 due to pool hashrate fluctuations, rejected shares and console hashrate inaccuracies plus 2% fee from yiimp.eu

1. 10 hours is not enough to calculate average earnings.
2. Whattomine is not accurate.
3. To receive pool payment, pool should solve block. But there are other pools also, so they are solving blocks too. Therefore, irregular payment gaps exists.

Yeah I understand all that but it seems to be too many coins missing. I mean it’s half of it. I would never expect to get exactly what whattomine says neither crypt0zone but somewhere near. Also my miner was doing 5.1 GH/S steady at the console, 5.0 GH/S steady in the pool and I run the calculations with 4.8 GH/S to give it some margin but it’s extremely off the figures.

The pool solved 134 block in the past 24 hrs so that’s 5,5 block average per hour.

I have switched back to RVN coin anyway, and funnily enough just been mining for 5 hours and numbers are spot on.

Not blaming anyone, don’t take me wrong but trying to understand such a big gap on payouts and such a big difference in rewards cos at the end of the day it means I have wasted 10 hours to get 30 coins instead of 50 so pretty much to break even

Thanks for replying and taking the time

[DumaxFr]

Hi guys!

Maybe this is the wrong place to ask but have a question about CREA mining.

I have started mining the coin like 10 hrs ago using yiimp.eu pool. My rig is 6 GTX 1070 Ti giving 5.1 GH/S and I am using ccminer 2.2.5 which is supposed to be without dev fee.

According to whattomine and crypt0zone I should be getting around 5 coins per hour (later it changed to 4.81) so in 10 hours it should be somewhere near 48-50 but I would happily accept somewhere between 43 and 45 due to pool hashrate fluctuations, rejected shares and console hashrate inaccuracies plus 2% fee from yiimp.eu

1. 10 hours is not enough to calculate average earnings.
2. Whattomine is not accurate.
3. To receive pool payment, pool should solve block. But there are other pools also, so they are solving blocks too. Therefore, irregular payment gaps exists.

Yeah I understand all that but it seems to be too many coins missing. I mean it’s half of it. I would never expect to get exactly what whattomine says neither crypt0zone but somewhere near. Also my miner was doing 5.1 GH/S steady at the console, 5.0 GH/S steady in the pool and I run the calculations with 4.8 GH/S to give it some margin but it’s extremely off the figures.

The pool solved 134 block in the past 24 hrs so that’s 5,5 block average per hour.

I have switched back to RVN coin anyway, and funnily enough just been mining for 5 hours and numbers are spot on.

Not blaming anyone, don’t take me wrong but trying to understand such a big gap on payouts and such a big difference in rewards cos at the end of the day it means I have wasted 10 hours to get 30 coins instead of 50 so pretty much to break even

Thanks for replying and taking the time

Just use 24h difficulty in whattomine and you will find your numbers

[chup]

Thanks for replying and taking the time

You're welcome. Just remember - Your earnings depends on how You're mining, but not as much as HOW AND WHEN You will sell what You mined. 

[papabiz]

Question:

When I build in release mode (x64) the miner starts propperly and starts hashing, but when building and running in debug (x64) I get 0 mh/s. I build with sm_52, having a 1080 ti.
Hashing should work in debug mode aswell, so this is some weird behaviour.

Anyone got it working in debugging mode?

[Epsylon3]

its should work too, only the x86 debug seems broken with recent cuda, doesnt allow gpu "profiling" etc...

But the only purpose of these debug builds is to allow step to step debugging...

[papabiz]

its should work too, only the x86 debug seems broken with recent cuda, doesnt allow gpu "profiling" etc...

But the only purpose of these debug builds is to allow step to step debugging...

Thats indeed what I am trying to achive, implement new algos and so on.
It helps me understand the design of the code easier by stepping interesting parts
I am using the x64 debug build when I run it...

I tried adding all sm_XX to the debug build aswell, but no luck there

EDIT:
I just tried running a diff algo, it hashes but output and hasing rate is weird.
Take a look at the pic