Topic: [ANN] ccminer 2.3 - opensource - GPL (tpruvot) - page 30. (Read 500193 times)

so will let you do it lol

Should be an easy copy and paste job from the Tromp kernel. No?

no, well i tried without success (and a big headache)

Are there any plans to add the MARS algorithm for Minexcoin?

Thank you guys, your help is much appreciated. I will look into this shortly. I am also kind of relieved to hear that the ccminer.exe I've been using is likely "harmless". Thanks for checking and letting me know...
Have a nice day 

Scryptr is absolutely right, this is a very different program, and i don't want to go off-topic with this. So i will post for you what's needed in the excavator topic. I'll send you a PM with the link.

That said the binaries of CCminer you got from the cryptomining blog *should* be safe, they've just probably been compiled by someone else, without the static libraries (hence a filesize much smaller)

Cheers.

THERE IS NO EQUIVALENT LINE--

Excavator is a powerful mining program that requires a configuration file.  It will overclock or underclock core and memory, and set power limits, all defined in the configuration file.  Excavator can launch a web interface for remote monitoring and control.  It will dual-mine with Ethereum when configured properly, but Lyra2v2 is not known to be compatible with dual-mining.

I haven't written a Lyra2v2 configuration for Excavator, currently CryptoNight is a better choice.  If I get the time, I will share a Lyra2v2 configuration.  However, this is a CCminer thread, and Epsylon3 does not like off-topic posts.

For what it is worth, CCminer autotunes and mines CryptoNight with less fuss and bother than Excavator, and slightly faster.  I get 750-780+ H/s at 6.25H/watt console with my 1080ti, and 630H/s at 9H/watt console with my 1070ti.  My 1070ti mines  CryptoNight slightly faster than my 980ti cards, and at about 1/2 the wattage.  CCminer reports hash-rate and wattage to the console window.  Excavator ports equivalent data to a web page.       --scryptr

EDIT:  Currently CCminer is significantly faster (+ ~40%, depending on GPU model) while mining CryptoNight when compared to Excavator.  However, the  script-level monitoring and control provided by Excavator make it a tempting rival.       --scryptr

Hi m1n1ngP4d4w4n,
thank you much for your response. You're right, I got mine from
http://cryptomining-blog.com/wp-content/download/ccminer-2.2-mod-r2.zip by way of http://cryptomining-blog.com/tag/lyra2rev2/
not from the official site, apparently. Is http://cryptomining-blog.com considered to be a shaddy website? I dunno...

I would love to try "excavator" optimized for lyra2rev2 @ NVIDIA GeForce GTX 1080 Ti instead but I have no clue which version to download and what the command line arguments are?

The best results I got so far (e.g. LAPool) were with the ccminer.exe:
> ccminer.exe -a lyra2v2 -o stratum+tcp://jp.lapool.me:4155 -u blablabla.worker1 -p foobar

What would be the equivalent line for "excavator"

Thanks in advance!

This miner is a fork of the original miner by Tpruvot, so you may not get any support here, that said alot of exe packager and compressor are being detected as virus & trojan by most antivirus so don't get too worried.

One thing that you should always check and be worried about, is the source of your miners, always get them directly from the developers depot or official post on this forum for example, not some shaddy websites.

https://github.com/Nanashi-Meiyo-Meijin/ccminer/releases, list both cuda8 and cuda9 version of the 2.2 R2, and none of them match the checksums you gave, so im betting you didn't got them from here. And that's bad. The binaries could have been compiled by some other guy and be perfectly safe, but never believe it, always get the originals if you aren't 100% of the source.

Also you have to know, at least to my knowledge and experience, this ccminer fork by nanashi isn't the best anymore to mine the lyra2v2 algo nowadays, i personally use excavator and it's working much better (15% more hash)

Try again with the good binaries if you want to use this ccminer fork for lyra2rev2 coins, otherwise i invite you to check out excavator.

Good luck.

...anyone have an idea, why Windows 10 Defender v1.257.1281.0 alarms “Win32/Tiggre!plock detected” in the ccminer.exe 2.2 mod r2 (ccMiner 2.2 fork by Nanashi Meiyo-Meijin For MonaCoin Mining)
and moves the file away into "quarantine"!!??

I am a bit worried I quess since I've been using the ccminer for quite a long time....

File name: ccminer.exe
File size: 11,913,216 Bytes
MD5: f42b688c88b28653356f4ce5ff046ab7
SHA-1: 3593d7f22eb82c82a20d1c051adcd62a4aa8490e
SHA-256: 5cb0f573ea02a2662bb580bcc3a8a59a4bd9df69e9683b60150dfdd8735932dd

what??? how it depends on coins source code???     it's all stratum fault, but nobody says here how to fix

Something with forks and source code

Hello?!?!
Have you even bothered looking for it ?? https://github.com/tpruvot/ccminer/releases/tag/v2.1-tpruvot

Hello,
How can i download sourcecode for v2.1.1 -linux branch?

Tried, same situation




Why ccminer-alexis works differently? It submits stale shares by default or what difference is?

Thank you, I did the way you said. It's currently running but I don't expect it to submit any shares. I think the problem is more related to ccminer or the card itself, it does this only for Lyra algorithm.

I supposed to get 1000 Kh/s(1 Mh/s) or even much much less but miner shows me 69-70 Mh/s, that's where the problem is.

I think your card is slow and producing stale shares. Make sure you don't use any 'static-diff' or nicehash stratum ports. Just go for the small diff./vardiff stratum (maybe even CPU ports). Also you could add the "--submit-stale" switch (depends on pool if it is accepted or not).

I added back-tick and I thought it worked but this time I get this;

Makefile:2665: recipe for target 'Algo256/cuda_groestl256.o' failed
make[2]: *** [Algo256/cuda_groestl256.o] Error 137
make[2]: *** Waiting for unfinished jobs....
mv -f equi/blake2/.deps/ccminer-blake2bx.Tpo equi/blake2/.deps/ccminer-blake2bx.Po
mv -f .deps/ccminer-scrypt.Tpo .deps/ccminer-scrypt.Po
ptxas info    : Overriding global maxrregcount 128 with entry-specific value 255 computed using thread count
ptxas info    : Overriding global maxrregcount 128 with entry-specific value 255 computed using thread count
ptxas info    : 0 bytes gmem, 17952 bytes cmem[3]
ptxas info    : Compiling entry function '_Z26streebog_gpu_hash_64_finalPmPj' for 'sm_37'
ptxas info    : Function properties for _Z26streebog_gpu_hash_64_finalPmPj
    120 bytes stack frame, 120 bytes spill stores, 132 bytes spill loads
ptxas info    : Used 255 registers, 16384 bytes smem, 336 bytes cmem[0]
ptxas info    : Compiling entry function '_Z20streebog_gpu_hash_64Pm' for 'sm_37'
ptxas info    : Function properties for _Z20streebog_gpu_hash_64Pm
    136 bytes stack frame, 192 bytes spill stores, 248 bytes spill loads
ptxas info    : Used 255 registers, 16384 bytes smem, 328 bytes cmem[0]
make[2]: Leaving directory '/home/maxo/ccminer'
Makefile:2197: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/home/maxo/ccminer'
Makefile:652: recipe for target 'all' failed
make: *** [all] Error 2

I did it like this;

nvcc_ARCH = -gencode=arch=compute_35,code=\"sm_37,compute_35\"

#nvcc_ARCH += -gencode=arch=compute_52,code=\"sm_52,compute_52\"
#nvcc_ARCH += -gencode=arch=compute_35,code=\"sm_35,compute_35\"
#nvcc_ARCH += -gencode=arch=compute_30,code=\"sm_30,compute_30\"
#nvcc_ARCH += -gencode=arch=compute_20,code=\"sm_21,compute_20\"

Ubuntu 16.04
Cuda 8.0

------

Update;

Seems like using ccminer-2.2.2 worked. ./build.sh finished without any problem.

But this time I'm not getting any "yes" or share submitted thing. I mine for hours and hours and no share gets submitted. Where I might be doing wrong this time?

https://bitcointalksearch.org/topic/m.11654778 > This guy had the same problem I have right now and seems like he solved it. On the other hand I get 70 Mh/s for Lyra, where I supposed to get XXX-XXXX Kh/s.

good, i'm using ....

Did you back-tick the "'s?  It's concat'ed together.