relayd
Member
Offline
Activity: 81
Merit: 12
|
|
August 14, 2017, 02:33:24 AM |
|
Nice, nearly 19 MH/s on a GTX 1060 6GB with intensity at 18 with -202 memory clock ccminer-x86-2.2: https://github.com/tpruvot/ccminer/releasesWas getting 17 MH/s with just about every miner before that on exact same settings. Power has some drops however, any idea why it keeps happening? Have same thing with krnlx. Goes from 91-89 to 34-35 every minute or so, seem to utilize more power as well compared to others which are 83-86. Would this cause any issues long term? ccminer-x86-2.2:3 other miners compared earlier:
|
|
|
|
|
|
According to NIST and ECRYPT II, the cryptographic algorithms used in
Bitcoin are expected to be strong until at least 2030. (After that, it
will not be too difficult to transition to different algorithms.)
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
Epsylon3 (OP)
Legendary
Offline
Activity: 1484
Merit: 1082
ccminer/cpuminer developer
|
|
August 14, 2017, 02:36:57 AM |
|
The diff change can trigger a small pause (500ms) that generally doesnt hurt
|
|
|
|
damniatx
Member
Offline
Activity: 109
Merit: 10
|
|
August 14, 2017, 02:47:36 AM |
|
The diff change can trigger a small pause (500ms) that generally doesnt hurt are you looking to add NEXUS (SHA3) algo in the future ?
|
|
|
|
relayd
Member
Offline
Activity: 81
Merit: 12
|
|
August 14, 2017, 02:48:40 AM |
|
Intensity 17 for ccminer 2.2 seems to lower power draw and temps nicely, 83-84% power, 66-67C with 67% Fan Speed.
Hash is still above others @ 17.7-17.8 MH/s or so.
Thanks for your work btw, too bad so many violate the GPL3 licensing with the private builds.
|
|
|
|
Epsylon3 (OP)
Legendary
Offline
Activity: 1484
Merit: 1082
ccminer/cpuminer developer
|
|
August 14, 2017, 02:51:11 AM |
|
yep :/ ZEC bounty empoisoned the opensource work... new devs gave ideas to sp
even nicehash stopped publishing their work
damniatx: no... i already tried, their wallet is weird and not compatible with bitcoin style protocols
|
|
|
|
relayd
Member
Offline
Activity: 81
Merit: 12
|
|
August 14, 2017, 02:56:56 AM |
|
Not a single miner I have tried is reported accurately on suprnova.cc, so I am guessing it has to be supernova. I see reported hash from 11 MH/s to 45 MH/s and I keep at 17MH/s in reality.
SIGT has been a very hard coin to predict in general no calculators are right either, only way to track is by how much you get paid in the end.
|
|
|
|
Epsylon3 (OP)
Legendary
Offline
Activity: 1484
Merit: 1082
ccminer/cpuminer developer
|
|
August 14, 2017, 02:59:09 AM |
|
yes, i guess ocminer tweaked it on a 1060. A message about that in its channel generaly fix it
|
|
|
|
car1999
|
|
August 14, 2017, 06:29:11 AM |
|
I built 2.2 with cuda 8.0 on ubuntu 16.04 64, the rig has 9 cards, but I always run in to below error. if I use -d 0.1.2.3.4.5.6.7 or -d 1,2,3,4,5,6,7,8, it works well.: *** ccminer 2.2 for nVidia GPUs by tpruvot@github ***^M Built with the nVidia CUDA Toolkit 8.0 64-bits^M ^M Originally based on Christian Buchner and Christian H. project^M Include some algos from alexis78, djm34, sp, tsiv and klausT.^M ^M BTC donation address: 1AJdfCpLWPNoAMDfHF1wD5y8VgKSSTHxPo (tpruvot)^M ^M [2017-08-14 02:23:29]^[[36m Starting on stratum+tcp://sigt.suprnova.cc:7106^[[0m^M [2017-08-14 02:23:29] NVML GPU monitoring enabled.^[[0m^M [2017-08-14 02:23:29] 9 miner threads started, using 'skunk' algorithm.^[[0m^M [2017-08-14 02:23:31]^[[33m Stratum difficulty set to 1^[[0m^M [2017-08-14 02:23:31] GPU #3: Intensity set to 20, 1048576 cuda threads^[[0m^M [2017-08-14 02:23:31] GPU #5: Intensity set to 18, 262144 cuda threads^[[0m^M [2017-08-14 02:23:31] GPU #1: Intensity set to 21, 2097152 cuda threads^[[0m^M [2017-08-14 02:23:31] GPU #4: Intensity set to 20, 1048576 cuda threads^[[0m^M [2017-08-14 02:23:31] GPU #6: Intensity set to 18, 262144 cuda threads^[[0m^M [2017-08-14 02:23:31] GPU #2: Intensity set to 18, 262144 cuda threads^[[0m^M [2017-08-14 02:23:31] GPU #8: Intensity set to 18, 262144 cuda threads^[[0m^M [2017-08-14 02:23:31] GPU #0: Intensity set to 21, 2097152 cuda threads^[[0m^M [2017-08-14 02:23:31] GPU #7: Intensity set to 18, 262144 cuda threads^[[0m^M [2017-08-14 02:23:37] GPU #1: GeForce GTX 1080, 713.70 kH/s^[[0m^M [2017-08-14 02:23:37] GPU #3: GeForce GTX 1070, 708.17 kH/s^[[0m^M [2017-08-14 02:23:37] GPU #3: GeForce GTX 1070, 708.17 kH/s^[[0m^M [2017-08-14 02:23:37]^[[33m GPU #3: unspecified launch failure^[[0m^M [2017-08-14 02:23:37]^[[33m GPU #3: skunk_setBlock_80:693 unspecified launch failure^[[0m^M [2017-08-14 02:23:37]^[[33m GPU #3: result does not validate on CPU!^[[0m^M [2017-08-14 02:23:37]^[[33m GPU #3: result does not validate on CPU!^[[0m^M [2017-08-14 02:23:37]^[[33m GPU #3: result does not validate on CPU!^[[0m^M [2017-08-14 02:23:37]^[[33m GPU #3: result does not validate on CPU!^[[0m^M [2017-08-14 02:23:37]^[[33m GPU #3: result does not validate on CPU!^[[0m^M [2017-08-14 02:23:37]^[[33m GPU #3: result does not validate on CPU!^[[0m^M [2017-08-14 02:23:37]^[[33m GPU #3: result does not validate on CPU!^[[0m^M [2017-08-14 02:23:37]^[[33m GPU #3: result does not validate on CPU!^[[0m^M [2017-08-14 02:23:37]^[[33m GPU #3: result does not validate on CPU!^[[0m^M [2017-08-14 02:23:37]^[[33m GPU #3: result does not validate on CPU!^[[0m^M [2017-08-14 02:23:37]^[[33m GPU #3: result does not validate on CPU!^[[0m^M [2017-08-14 02:23:37]^[[33m GPU #3: result does not validate on CPU!^[[0m^M [2017-08-14 02:23:37]^[[33m GPU #3: result does not validate on CPU!^[[0m^M [2017-08-14 02:23:37]^[[33m GPU #3: result does not validate on CPU!^[[0m^M [2017-08-14 02:23:37]^[[33m GPU #3: result does not validate on CPU!^[[0m^M [/code/
|
|
|
|
car1999
|
|
August 14, 2017, 06:30:29 AM |
|
I built 2.2 with cuda 8.0 on ubuntu 16.04 64, the rig has 9 cards, but I always run in to below error. if I use -d 0.1.2.3.4.5.6.7 or -d 1,2,3,4,5,6,7,8 to run 8 cards only, it works well.: *** ccminer 2.2 for nVidia GPUs by tpruvot@github ***^M Built with the nVidia CUDA Toolkit 8.0 64-bits^M ^M Originally based on Christian Buchner and Christian H. project^M Include some algos from alexis78, djm34, sp, tsiv and klausT.^M ^M BTC donation address: 1AJdfCpLWPNoAMDfHF1wD5y8VgKSSTHxPo (tpruvot)^M ^M [2017-08-14 02:23:29]^[[36m Starting on stratum+tcp://sigt.suprnova.cc:7106^[[0m^M [2017-08-14 02:23:29] NVML GPU monitoring enabled.^[[0m^M [2017-08-14 02:23:29] 9 miner threads started, using 'skunk' algorithm.^[[0m^M [2017-08-14 02:23:31]^[[33m Stratum difficulty set to 1^[[0m^M [2017-08-14 02:23:31] GPU #3: Intensity set to 20, 1048576 cuda threads^[[0m^M [2017-08-14 02:23:31] GPU #5: Intensity set to 18, 262144 cuda threads^[[0m^M [2017-08-14 02:23:31] GPU #1: Intensity set to 21, 2097152 cuda threads^[[0m^M [2017-08-14 02:23:31] GPU #4: Intensity set to 20, 1048576 cuda threads^[[0m^M [2017-08-14 02:23:31] GPU #6: Intensity set to 18, 262144 cuda threads^[[0m^M [2017-08-14 02:23:31] GPU #2: Intensity set to 18, 262144 cuda threads^[[0m^M [2017-08-14 02:23:31] GPU #8: Intensity set to 18, 262144 cuda threads^[[0m^M [2017-08-14 02:23:31] GPU #0: Intensity set to 21, 2097152 cuda threads^[[0m^M [2017-08-14 02:23:31] GPU #7: Intensity set to 18, 262144 cuda threads^[[0m^M [2017-08-14 02:23:37] GPU #1: GeForce GTX 1080, 713.70 kH/s^[[0m^M [2017-08-14 02:23:37] GPU #3: GeForce GTX 1070, 708.17 kH/s^[[0m^M [2017-08-14 02:23:37] GPU #3: GeForce GTX 1070, 708.17 kH/s^[[0m^M [2017-08-14 02:23:37]^[[33m GPU #3: unspecified launch failure^[[0m^M [2017-08-14 02:23:37]^[[33m GPU #3: skunk_setBlock_80:693 unspecified launch failure^[[0m^M [2017-08-14 02:23:37]^[[33m GPU #3: result does not validate on CPU!^[[0m^M [2017-08-14 02:23:37]^[[33m GPU #3: result does not validate on CPU!^[[0m^M [2017-08-14 02:23:37]^[[33m GPU #3: result does not validate on CPU!^[[0m^M [2017-08-14 02:23:37]^[[33m GPU #3: result does not validate on CPU!^[[0m^M [2017-08-14 02:23:37]^[[33m GPU #3: result does not validate on CPU!^[[0m^M [2017-08-14 02:23:37]^[[33m GPU #3: result does not validate on CPU!^[[0m^M [2017-08-14 02:23:37]^[[33m GPU #3: result does not validate on CPU!^[[0m^M [2017-08-14 02:23:37]^[[33m GPU #3: result does not validate on CPU!^[[0m^M [2017-08-14 02:23:37]^[[33m GPU #3: result does not validate on CPU!^[[0m^M [2017-08-14 02:23:37]^[[33m GPU #3: result does not validate on CPU!^[[0m^M [2017-08-14 02:23:37]^[[33m GPU #3: result does not validate on CPU!^[[0m^M [2017-08-14 02:23:37]^[[33m GPU #3: result does not validate on CPU!^[[0m^M [2017-08-14 02:23:37]^[[33m GPU #3: result does not validate on CPU!^[[0m^M [2017-08-14 02:23:37]^[[33m GPU #3: result does not validate on CPU!^[[0m^M [2017-08-14 02:23:37]^[[33m GPU #3: result does not validate on CPU!^[[0m^M [/code/
|
|
|
|
yunihuni
Member
Offline
Activity: 70
Merit: 10
|
|
August 14, 2017, 06:35:42 AM |
|
skunk algo
spmod5 228mh cc 2.2 244mh
|
|
|
|
|
Amph
Legendary
Offline
Activity: 3206
Merit: 1069
|
|
August 14, 2017, 08:06:33 AM |
|
skunk algo
spmod5 228mh cc 2.2 244mh
what about the reported speed on pool side? ok i see it's suprnova fault...
|
|
|
|
yunihuni
Member
Offline
Activity: 70
Merit: 10
|
|
August 14, 2017, 09:39:03 AM |
|
skunk algo
spmod5 228mh cc 2.2 244mh
what about the reported speed on pool side? ok i see it's suprnova fault... Might be. I hope @ocminer fix that.
|
|
|
|
fr4nkthetank
Legendary
Offline
Activity: 2294
Merit: 1182
Now the money is free, and so the people will be
|
|
August 14, 2017, 01:02:31 PM |
|
Just wanted to say thanks for all the hard work. works smooth and all seems good pool side for me.
|
|
|
|
the.vlado
|
|
August 15, 2017, 09:21:56 PM |
|
Is it possible to build ccminer with Visual Studio 2015 (Microsoft Visual Studio 14.0) and CUDA_8.0.61.2_windows?
Yes, it's possible. But you'll need to do some additional work, such as make changes in Algo256/cuda_blake256.cu and neoscrypt/cuda_neoscrypt.cu to make it compatible with VS2015. Also you'll need to rebuild libcurl.x64.lib and openssl.x64.lib from sources for VS2015 compatible. For libcurl you can follow this guide - How to Build and Use Libcurl with VS2015 on Windows and openssl.lib you could try to build by yourself, or download it precompiled. Hi Decker, Thank you for reply. Maybe I will try that one day. For now I gave up from VS 2015. I'he installed VS 2013. Now I can compile and run ccminer, it will connect to the pool and receive blocks. But card is at 0% and mining is not happening. Any reason why is that happening? tnx
|
|
|
|
daberti
|
|
August 15, 2017, 10:13:23 PM |
|
First things first. Did you try to compile Cuda Samples (vs2013 ones) against VS2013?
|
|
|
|
Wyse
Newbie
Offline
Activity: 8
Merit: 0
|
|
August 16, 2017, 12:08:37 PM |
|
I believe the intensity flag (-i) is not working properly when using the cryptonight algorithm. No matter what value I set the GPU usage always stays at 99-100%, while when mining with the skunk algorithm it works great and progressively reduces its GPU usage the lower I go.
|
|
|
|
nizzuu
Full Member
Offline
Activity: 187
Merit: 100
Cryptocurrency enthusiast
|
|
August 16, 2017, 02:59:03 PM |
|
I believe the intensity flag (-i) is not working properly when using the cryptonight algorithm. No matter what value I set the GPU usage always stays at 99-100%, while when mining with the skunk algorithm it works great and progressively reduces its GPU usage the lower I go.
You should use --bfactor and --launch-config keys to tune miner on this algo. See algo section in readme.
|
|
|
|
the.vlado
|
|
August 16, 2017, 09:56:12 PM |
|
First things first. Did you try to compile Cuda Samples (vs2013 ones) against VS2013?
Hi, that is good start. Yes, I just did that now. Exe files are created. I can also create ccminer.exe file and when I use it, it is mining. But it is not working when I execute it from VS. I tried in CUDA debug mode and in normal mode without debug. GPU is at 0% all the time.
|
|
|
|
daberti
|
|
August 16, 2017, 11:31:39 PM Last edit: August 16, 2017, 11:43:21 PM by daberti |
|
First things first. Did you try to compile Cuda Samples (vs2013 ones) against VS2013?
Hi, that is good start. Yes, I just did that now. Exe files are created. I can also create ccminer.exe file and when I use it, it is mining. But it is not working when I execute it from VS. I tried in CUDA debug mode and in normal mode without debug. GPU is at 0% all the time. You have to pick the .exe from the source tree and put in a directory of your choice and NOT execute it from VS. Also bear in mind that antivirus software(or Win's own firewall) may somehow prevent you from actually mining. Bottom line: did you choose the Release and x64 compiling asset?
|
|
|
|
|