Topic: Signatum (skunk) ccminer-krnlx 30+mh 1070, 52.5+ mh 1080ti [FREE,OPENSOURCE] - page 13. (Read 39453 times)

Doesn't seem to work for me!!

I've created a separate folder in Home on my nvOC setup, copied the ccminer to that folder and tried to run!!

miner not being getting detected, so i tried to run it using ./ccminer command, seems its expecting CUDA 7.5 or something!!

Anybody tested this?? please help

Hi,

I've some question about "Intensity" option that I not set in bash script. It's automatic set to 19 as following below log:

[2017-08-08 10:59:04] Starting on stratum+tcp://sigt.pool.mn:8732
[2017-08-08 10:59:04] 6 miner threads started, using 'skunk' algorithm.
[2017-08-08 10:59:07] Stratum difficulty set to 0.00390625
[2017-08-08 10:59:07] skunk block 28955, diff 32703.377
[2017-08-08 10:59:07] GPU #1: Intensity set to 19, 524288 cuda threads!!!!
[2017-08-08 10:59:07] GPU #1: Intensity set to 19, 524288 cuda threads
[2017-08-08 10:59:07] GPU #0: Intensity set to 19, 524288 cuda threads!!!!
[2017-08-08 10:59:07] GPU #0: Intensity set to 19, 524288 cuda threads[2017-08-08 10:59:11] GPU #0: GeForce GTX 1080 Ti, 285.22 kH/s
[2017-08-08 10:59:11] GPU #3: GeForce GTX 1080 Ti, 284.48 kH/s
[2017-08-08 10:59:11] GPU #4: GeForce GTX 1080 Ti, 281.38 kH/s
[2017-08-08 10:59:11] GPU #2: GeForce GTX 1080 Ti, 279.85 kH/s
[2017-08-08 10:59:11] GPU #5: GeForce GTX 1080 Ti, 276.46 kH/s
[2017-08-08 10:59:11] GPU #1: GeForce GTX 1080 Ti, 275.47 kH/s
[2017-08-08 10:59:07] GPU #4: Intensity set to 19, 524288 cuda threads!!!!
[2017-08-08 10:59:07] GPU #4: Intensity set to 19, 524288 cuda threads
[2017-08-08 10:59:07] GPU #2: Intensity set to 19, 524288 cuda threads!!!!
[2017-08-08 10:59:07] GPU #2: Intensity set to 19, 524288 cuda threads
[2017-08-08 10:59:07] GPU #3: Intensity set to 19, 524288 cuda threads!!!!
[2017-08-08 10:59:07] GPU #3: Intensity set to 19, 524288 cuda threads
[2017-08-08 10:59:07] GPU #5: Intensity set to 19, 524288 cuda threads!!!!
[2017-08-08 10:59:07] GPU #5: Intensity set to 19, 524288 cuda threads


I've try to set 20 or 25. System crash and reboot. Please suggest me how to tune it? My hash rate only 40-45 per card. My system use Ubuntu 14.04, Cuda 8 and Nvidia Driver  381.22

Hmm..not sure what to make of this...

32bit: bf3afb527ef9fcc198545e21401346d1bbb4140b8cb6e84b6b488046cb13fae4
64bit: d95fd19dd9acf42459287d1e9c4aaf728e4c2a584a905fa269dfb23f4384d388

The 64bit 55MB file looks clean, but the 32bit is coming back with Malware.Heuristic!ET#98% (rdm+) which is odd.  Going to run a full scan with another AV to see if anything comes back.

what's your gcc and CUDA version? Did you add nvcc_ARCH += -gencode=arch=compute_61,code=\"sm_61,compute_61\" to Makefile.am?

Just run whatever AV software you have. If windows defender picks it up then probably everything else will aswell. If you had wallets on those systems I suggest you transfer coins to another address with a wallet generated on a known clean system. And keep an eye out on your email and such for suspicious activity.

just tried this.

win 10 didn't throw up any flags, so i guess it's clean.

i get the same speed as spmod on my 1070s at 60%tdp (my sweet spot setting for these cards) - 28.

not sure if it's this compile or the coin's network that's being hammered, or the miner overall,  but it was very slow to start submitting shares.  took well over a minute on yimp before i saw a white line, and almost two on nova.

Nahh im srs. I mean, ok, i deleted the files, but what if trojan horse got somewhere after i ran the app?

Should avira be enough?

Dynamite it !!

Fu*k,

I seen ppl reporting this one having a Trojan and i downloaded and tried this version on 3 of my rigs.

Any idea how to clean my pc properly now in case it was infected? :/

Out of curiosity, can you upload your version to VT to see what flags it throws? It should get detected as PUA or Bitcoin mining software by some of the AV's at the minimum.

Hi guys, can you provide your results with this miner for 1080ti? My setup: 1999MHz core, 5005 mem, 100% tdp.

I'm getting 51.5...51.75 Mh/s (Win10, Pentium G4600 CPU) with these settings using palgin's mod v 1.1, so I'm just wondering if there're any improvements here. Thanks.

My 10 card rig works ok, 13 card rig crashes.
My build is for linux, so it's normal to have a different size.
I get +5 mh for each card (1080ti), too bad that it doesnt work on the 13 cards rig

compiled with compute_50 and 52
https://github.com/xnoom/ccminer-skunk/releases/tag/cuda7.5-compute_50_52

My windows builds are 45 and 55 MB too.  Epsylon3's 64bit build is only 14 MB...but he knows what he is doing.  This one is Linux?  I really don't know but the first Window 64bit build posted here was removed by Windows Defender for me. My own build came back clean on the AV so hoping the source is clean.

So I posted the above earlier, two previous binaries that were shared were 45 and 55mb by a Hero Member here

Now this one below is 30mb from a noob account?


Anyone out there care to explain the difference?

do you have a rig with more than 8cards?does it work?

So i finnaly managed to compile this miner for linux ( i use nvOC for mining )

For all those who cant get this compiled, here is my compiled version:

https://ufile.io/kxlay
https://www.file-upload.com/6m9ekmvm6qrz

Many thanks to all who contributed.

I managed to build the cuda 8.0 windows version x86/x64. For test I installed also the cuda 7.5 sdk,
but I'm in no way have a clue beside pushing buttons and changing switches, so what need's to be changed to compile against the 7.5 SDK?

I think it is a real hit because it was a specific trojan not the usual warning that it is "risky software" because it is associated with mining.  With the SIGT hype/greed and the malware infected versions of sp mods going around it is probably best for everyone to build themselves.  Unless the trojan is in the source itself, which could be easy to hide since lots of people are not familiar with the code. I did a quick look and did not see anything, but that isn't saying much to vouch for the safety.  Epsylon3 provided a build, I would think he would catch anything in the source though.

Tried that too, but ends with


so I've tried 'libssl-dev'



but


still giving me BIGNUM error!!

Have I missed something??

Thanks