Use
-d, --devices gives a comma separated list of CUDA device IDs to operate on. Device IDs start counting from 0!
eg
ccminer ..................... -d 1 will work on second card only
-d 0 on first card only
Topic: [ANN] ccminer 2.3 - opensource - GPL (tpruvot) - page 29. (Read 500193 times)
Hi, noob question here...
I have two 1060 runing, how do i disable the primary card and let only the card 2 mining?
Thanks!
I have two 1060 runing, how do i disable the primary card and let only the card 2 mining?
Thanks!
yes, i added a second port, there was too much miners and the limit was set a bit too high. I twitted about that, seems ok now.
There was no changes, problem is elsewhere...
Hi,
2.2.3 cuda9 x64 has issue with tribus algo (compare 2.2.2 cuda9 x64). it has down hashrate up to 5-10%.
1070 55 -> 50
1060 36 -> 30
Please, fix it.
2.2.3 cuda9 x64 has issue with tribus algo (compare 2.2.2 cuda9 x64). it has down hashrate up to 5-10%.
1070 55 -> 50
1060 36 -> 30
Please, fix it.
I found 2.2.3 slower too, but I also recently updated nvidia drivers to 388.43.
Downgrading to 388.30, fixed the slower performance (at least in my setup).
If you are using 388.43, try to downgrade.
Hi,
2.2.3 cuda9 x64 has issue with tribus algo (compare 2.2.2 cuda9 x64). it has down hashrate up to 5-10%.
1070 55 -> 50
1060 36 -> 30
Please, fix it.
2.2.3 cuda9 x64 has issue with tribus algo (compare 2.2.2 cuda9 x64). it has down hashrate up to 5-10%.
1070 55 -> 50
1060 36 -> 30
Please, fix it.
There was no changes, problem is elsewhere...
Hi,
2.2.3 cuda9 x64 has issue with tribus algo (compare 2.2.2 cuda9 x64). it has down hashrate up to 5-10%.
1070 55 -> 50
1060 36 -> 30
Please, fix it.
Sorry but where can I download 2.2.3 ccminer ? I’ve searched never found it over github 2.2.3 cuda9 x64 has issue with tribus algo (compare 2.2.2 cuda9 x64). it has down hashrate up to 5-10%.
1070 55 -> 50
1060 36 -> 30
Please, fix it.
Can I use this to mine Homeblockcoin?
Hi,
2.2.3 cuda9 x64 has issue with tribus algo (compare 2.2.2 cuda9 x64). it has down hashrate up to 5-10%.
1070 55 -> 50
1060 36 -> 30
Please, fix it.
2.2.3 cuda9 x64 has issue with tribus algo (compare 2.2.2 cuda9 x64). it has down hashrate up to 5-10%.
1070 55 -> 50
1060 36 -> 30
Please, fix it.
Hello Guys,
i use CCminer v2.2.3 Windows - i am Mining "ETN" on that pool https://electroneum.hashvault.pro
after 10 - 20 minutes i get that fail :
unspecified launch failure cryptonight_core_cuda line 180
unspecified launch failure cryptonight_extra_cpu_final line 235
Please can fix that Problem some guy for me ?
i have 9 Times
1070 GTX OC STRIX O8G
TDP : 72%
CORE: 110
MEM: 500
get 5700-5900 H/s <-- what to mine say me, thats okay.
There are stand arround 80Watt - is that true?
Thanks for Helping
i use CCminer v2.2.3 Windows - i am Mining "ETN" on that pool https://electroneum.hashvault.pro
after 10 - 20 minutes i get that fail :
unspecified launch failure cryptonight_core_cuda line 180
unspecified launch failure cryptonight_extra_cpu_final line 235
Please can fix that Problem some guy for me ?
i have 9 Times
1070 GTX OC STRIX O8G
TDP : 72%
CORE: 110
MEM: 500
get 5700-5900 H/s <-- what to mine say me, thats okay.
There are stand arround 80Watt - is that true?
Thanks for Helping
have you tried this to see if it's working?
https://github.com/KlausT/ccminer-cryptonight
Hello Guys,
i use CCminer v2.2.3 Windows - i am Mining "ETN" on that pool https://electroneum.hashvault.pro
after 10 - 20 minutes i get that fail :
unspecified launch failure cryptonight_core_cuda line 180
unspecified launch failure cryptonight_extra_cpu_final line 235
Please can fix that Problem some guy for me ?
i have 9 Times
1070 GTX OC STRIX O8G
TDP : 72%
CORE: 110
MEM: 500
get 5700-5900 H/s <-- what to mine say me, thats okay.
There are stand arround 80Watt - is that true?
Thanks for Helping
i use CCminer v2.2.3 Windows - i am Mining "ETN" on that pool https://electroneum.hashvault.pro
after 10 - 20 minutes i get that fail :
unspecified launch failure cryptonight_core_cuda line 180
unspecified launch failure cryptonight_extra_cpu_final line 235
Please can fix that Problem some guy for me ?
i have 9 Times
1070 GTX OC STRIX O8G
TDP : 72%
CORE: 110
MEM: 500
get 5700-5900 H/s <-- what to mine say me, thats okay.
There are stand arround 80Watt - is that true?
Thanks for Helping
Finally I can fixed my stratum, sorry for annoy here, I was the only one to blame 
I am attempting to utilize this with Xubuntu 14.04.1, bit 3.13.0-37, nvidia driver 340.46, cuda 6.5. I have different renditions of ccminer arranged and working. I can assemble this without mistake. The issue comes when I am attempting to execute ccminer. It gives me this mistake message: "Cuda blunder in document 'blake32.cu' in line 273 : invalid gadget image.
" I get a similar sort of 'invalid gadget image' for different calculations as well. Would someone be able to please enable me to make sense of why I mama getting this mistake.
" I get a similar sort of 'invalid gadget image' for different calculations as well. Would someone be able to please enable me to make sense of why I mama getting this mistake.
So still no solution with my problem???
Why this ccminer consider 80% of shares as stale and doesn't send them to stratum? What job rebroadcast interval should be to avoid this problem? Or maybe another stratum setting
Why this ccminer consider 80% of shares as stale and doesn't send them to stratum? What job rebroadcast interval should be to avoid this problem? Or maybe another stratum setting
doesn't
Code:
--submit-stale ignore stale jobs checks, may create more rejected shares
yes "--submit-stale" param help, but my users surely don't set it and soon they will write that my pool is scam since shows wrong hashrate
Hum i see, maybe the stratum protocol need to be revised then, weird to get this many reject.
So still no solution with my problem???
Why this ccminer consider 80% of shares as stale and doesn't send them to stratum? What job rebroadcast interval should be to avoid this problem? Or maybe another stratum setting
Why this ccminer consider 80% of shares as stale and doesn't send them to stratum? What job rebroadcast interval should be to avoid this problem? Or maybe another stratum setting
doesn't
Code:
--submit-stale ignore stale jobs checks, may create more rejected shares
yes "--submit-stale" param help, but my users surely don't set it and soon they will write that my pool is scam since shows wrong hashrate
So still no solution with my problem???
Why this ccminer consider 80% of shares as stale and doesn't send them to stratum? What job rebroadcast interval should be to avoid this problem? Or maybe another stratum setting
Why this ccminer consider 80% of shares as stale and doesn't send them to stratum? What job rebroadcast interval should be to avoid this problem? Or maybe another stratum setting
doesn't
Code:
--submit-stale ignore stale jobs checks, may create more rejected shares
Yes _sp show us dem skills
(j/k)
Tried mining LUXcoin on 4*1060
It starts well, runs ~11mh/card, but after 10-15min the speed goes down to ~31MH, with 2 cards running at 5mh
The 2 slow cards are roatting, eg in stats I can see that there are 2 fast and slow cards, which chagne their speed fast-slow-fast-slow...
Any idea for the reason!?
I do see ccminer is running 100% on 1 core - the PC is bit outdated i3-530...
There is NO overheating, increased power limit, just in case ... ideas?
The drop is ~ 1mh/minute...
After 20min speed was down to 24MH, down from 43 at the beginning
CPU limited?!
It starts well, runs ~11mh/card, but after 10-15min the speed goes down to ~31MH, with 2 cards running at 5mh
The 2 slow cards are roatting, eg in stats I can see that there are 2 fast and slow cards, which chagne their speed fast-slow-fast-slow...
Any idea for the reason!?
I do see ccminer is running 100% on 1 core - the PC is bit outdated i3-530...
There is NO overheating, increased power limit, just in case ... ideas?
The drop is ~ 1mh/minute...
After 20min speed was down to 24MH, down from 43 at the beginning
CPU limited?!
So still no solution with my problem???
Why this ccminer consider 80% of shares as stale and doesn't send them to stratum? What job rebroadcast interval should be to avoid this problem? Or maybe another stratum setting
Why this ccminer consider 80% of shares as stale and doesn't send them to stratum? What job rebroadcast interval should be to avoid this problem? Or maybe another stratum setting
Jump to: