CCminer(SP-MOD) Modded GPU kernels.

[sp_]

Get the latest. Build 38 should work now.

Groestl is used in quark and x11 etc.

[sp_]

1.5.38(sp-MOD) is available here: (8-feb-2015)

https://github.com/sp-hash/ccminer/releases/tag/1.5.38

The sourcecode is available here:

https://github.com/sp-hash/ccminer

[rednoW]

Thanx for new release! It works. quark performance is nearly the same with r36 abd r37.
One moment - i don't now if it worth to point at - x13 don't work on default settings on Hamsterpool.
It works fine on Yaamp and Nicehash though ... )))

[chrysophylax]

1.5.38(sp-MOD) is available here: (8-feb-2015)

https://github.com/sp-hash/ccminer/releases/tag/1.5.38

The sourcecode is available here:

https://github.com/sp-hash/ccminer

compiles and runs really well sp ...

will test on the rest of the farm tomorrow ...

tanx ...

#crysx

[sp_]

Thanx for new release! It works. quark performance is nearly the same with r36 abd r37.

yes. for compute 5.0 (750,750ti) the speed is the same, but for compute 5.2 much faster. release37 had a drop in the speed for 960,970,980 cards.

[scryptr]

Thanx for new release! It works. quark performance is nearly the same with r36 abd r37.

yes. for compute 5.0 (750,750ti) the speed is the same, but for compute 5.2 much faster. release37 had a drop in the speed for 960,970,980 cards.

I am getting many "result does not validate on cpu" errors in various algos.  However, shares are still accepted.  In setting up auto-switching yaamp by using the "-r 0" round-robin flag on my Windows commandline, I have been seeing results on more algos than I usually mine.  The version running is v38, on a GTX 960.           --scryptr   

[sp_]

Wich algos?

[scryptr]

Wich algos?

Was?  Ins algos x11,x13,x14, und fresh.  Vielleicht mehr...

Aber, es tut mir leid, ins Englisch, die worte "which" ein "h" haben.       --scryptr

[go6ooo1212]

I saw same error on X15 today with r38

[scryptr]

YAAMP ROUND-ROBIN CONFIGURATION--

The following is a working Windows Batch File for a GTX 960 using the yaamp auto-switch.  The "-r 0" flag allows yaamp to cycle through algorithms until the high-paying algorithm is served up.  The long "password" should be comma separated and have no spaces except immediately after the "-p".  Each line is broken by the formatting process on this blog after the "-p" password flag.  I inserted 1 extra blank line between each 1-line command statement for clarity.

There is no such simple solution on Linux, primarily because BASH does not have a goto command.  Save this text as "looper.bat".  Code follows:

:loop

ccminer.exe -r 0 -a x11 -o stratum+tcp://yaamp.com:3533 -u name -p x11=5.4,x13=4.2,x14=4.1,x15=3.6,quark=9.8,lyra2=0.7,fresh=6.1

ccminer.exe -r 0 -a x13   -o stratum+tcp://yaamp.com:3633 -u name -p x11=5.4,x13=4.2,x14=4.1,x15=3.6,quark=9.8,lyra2=0.7,fresh=6.1

ccminer.exe -r 0 -a x14   -o stratum+tcp://yaamp.com:3933 -u name -p x11=5.4,x13=4.2,x14=4.1,x15=3.6,quark=9.8,lyra2=0.7,fresh=6.1

ccminer.exe -r 0 -a x15   -o stratum+tcp://yaamp.com:3733 -u name -p x11=5.4,x13=4.2,x14=4.1,x15=3.6,quark=9.8,lyra2=0.7,fresh=6.1

ccminer.exe -r 0 -a quark -i 20 -o stratum+tcp://yaamp.com:4033 -u name -p x11=5.4,x13=4.2,x14=4.1,x15=3.6,quark=9.8,lyra2=0.7,fresh=6.1

ccminer.exe -r 0 -a lyra2 -o stratum+tcp://yaamp.com:4433 -u name -p x11=5.4,x13=4.2,x14=4.1,x15=3.6,quark=9.8,lyra2=0.7,fresh=6.1

ccminer.exe -r 0 -a fresh -i 20 -o stratum+tcp://yaamp.com:4133 -u name -p x11=5.4,x13=4.2,x14=4.1,x15=3.6,quark=9.8,lyra2=0.7,fresh=6.1

goto loop

[ocminer]

Has anyone got build instructions  from source on Windows 8 ?

[ocminer]

Has anyone got build instructions  from source on Windows 8 ?

Compiling on Windows (at least, most software - that is, software that doesn't come with MSVC project files) is not easy.

I know, i already compiled a lot on Windows but this one seems to have some strange issues...

[sp_]

Thanx for new release! It works. quark performance is nearly the same with r36 abd r37.

yes. for compute 5.0 (750,750ti) the speed is the same, but for compute 5.2 much faster. release37 had a drop in the speed for 960,970,980 cards.

I am getting many "result does not validate on cpu" errors in various algos.  However, shares are still accepted.  In setting up auto-switching yaamp by using the "-r 0" round-robin flag on my Windows commandline, I have been seeing results on more algos than I usually mine.  The version running is v38, on a GTX 960.           --scryptr   

Works on 750ti. You can remove compute 5.2 in the projectfile and try to recompile until I find out whats wrong. Or revert to an earlier build

[Schleicher]

Has anyone got build instructions  from source on Windows 8 ?

Install Visual Studio Express 2013 for Windows Desktop
Install Nvidia CUDA 6.5 Toolkit
Download the ccminer source code
Open the ccminer.sln file
Make sure the compiler is set to "release" and "Win32"
Rebuild solution

Then you should see the ccminer.exe in the release folder

[bathrobehero]

The sha256 algo implementation might come in handy because a coin with modified sha256 is coming from earlz no less:

https://bitcointalk.org/index.php?topic=950084

[Epsylon3]

Has anyone got build instructions  from source on Windows 8 ?

Install Visual Studio Express 2013 for Windows Desktop
Install Nvidia CUDA 6.5 Toolkit
Download the ccminer source code
Open the ccminer.sln file
Make sure the compiler is set to "release" and "Win32"
Rebuild solution

Then you should see the ccminer.exe in the release folder

And you know what, its the same since XP and works also on Windows 10 ! :p

[scotte]

 am solo mining DGB in the hope that they go up in value.
I got one "yay" this morning and this went into my wallet which is the official version and I got 2386.045241 DBG
I got another "yay" this afternoon but nothing went to my wallet, I can see things like "AddToWallet" and "ProcessBlock: ACCEPTED" and "generated 2385.965241"  in the debug file for the wallet
I am using ccminer sp version from a few days ago from git which I compiled myself,
My question is what do I look for in the log to tell me what the problem is?
Does my wallet need to be unlocked during mining, although I am fairly sure it was locked when I got the 1st "yay" this morning
I've spent a couple of hours googling this issue and not found anything relevant, apologies if this is a noob question that I should know.

[exemplaar]

am solo mining DGB in the hope that they go up in value.
I got one "yay" this morning and this went into my wallet which is the official version and I got 2386.045241 DBG
I got another "yay" this afternoon but nothing went to my wallet, I can see things like "AddToWallet" and "ProcessBlock: ACCEPTED" and "generated 2385.965241"  in the debug file for the wallet
I am using ccminer sp version from a few days ago from git which I compiled myself,
My question is what do I look for in the log to tell me what the problem is?
Does my wallet need to be unlocked during mining, although I am fairly sure it was locked when I got the 1st "yay" this morning
I've spent a couple of hours googling this issue and not found anything relevant, apologies if this is a noob question that I should know.

sounds low level, but maybe was orphaned block?

[ocminer]

Has anyone got build instructions  from source on Windows 8 ?

Install Visual Studio Express 2013 for Windows Desktop
Install Nvidia CUDA 6.5 Toolkit
Download the ccminer source code
Open the ccminer.sln file
Make sure the compiler is set to "release" and "Win32"
Rebuild solution

Then you should see the ccminer.exe in the release folder

Works - partly ...

Can someone tell me which flag I have to set to get it compile with curl ssl support in MSVC 2013 Express ?

When I try to connect I get HTTP request failed, protocol https not supported or disabled in libcurl.

Of course my local libcurl lib is ssl enabled and the one in the "compat" dir also from what I see.. So it is probably an option somewhere ?

[scotte]

am solo mining DGB in the hope that they go up in value.
I got one "yay" this morning and this went into my wallet which is the official version and I got 2386.045241 DBG
I got another "yay" this afternoon but nothing went to my wallet, I can see things like "AddToWallet" and "ProcessBlock: ACCEPTED" and "generated 2385.965241"  in the debug file for the wallet
I am using ccminer sp version from a few days ago from git which I compiled myself,
My question is what do I look for in the log to tell me what the problem is?
Does my wallet need to be unlocked during mining, although I am fairly sure it was locked when I got the 1st "yay" this morning
I've spent a couple of hours googling this issue and not found anything relevant, apologies if this is a noob question that I should know.

sounds low level, but maybe was orphaned block?

not sure if I can tell what it is, is there an accepted failure rate, what % is the norm?