CCminer(SP-MOD) Modded GPU kernels.

[scryptr]

Anyone using some 960s? What are you getting for Quark/X11/Neo?
I assume ccminer doesn't scale and needs to be tailored to each cards gen.

you can get 10mhash if you overclock. With standard clocks around 9.2 Mhash

GTX 960--

Mining Quark, I get 10.5Mh/s with +80mhz/240mhz core/mem on the 2gb 960 SSC card with default intensity.  It runs on Win 7 x64.

--scryptr

[joblo]

ultimately its about building - compiling - rolling out - streamlining ... all clones of one worker ... all with linux - all with exact same hardware - all with ccminer-spmod

Hey Guys...for some of us...this stuff is all greek.     I made no sense of any of it and would really like to keep up with the Jones here. It would be nice to see some Win-install files, just like you had release #s before. So much love would come your way!    

Thanks

A little quotation error corrected.

If you mean precompiled Windows binaries, they are still produced and available on the release page as
posted by SP. If you want to compile your own Windows binaries it not too difficult but very long and I might
be able to help. I've gone through it a couple of times and it can be done with all freeware, except for the OS of course.

In short you need Visual Studio Community and Cuda Tools, cminer source and lots of disk space. ccminer.sln is
the configuration file and you double click on it to open the "Solution" in VS. You can edit the properties to add
compute versions (similar to what Linux folks do with makefiles). Then Build Solution. Eventually if everything
works you should find a release directory with a freshly minted ccminer.exe file in it.

I can write up a better tutorial if you like but it will take some time.

[chrysophylax]

ultimately its about building - compiling - rolling out - streamlining ... all clones of one worker ... all with linux - all with exact same hardware - all with ccminer-spmod

Hey Guys...for some of us...this stuff is all greek.     I made no sense of any of it and would really like to keep up with the Jones here. It would be nice to see some Win-install files, just like you had release #s before. So much love would come your way!    

Thanks

A little quotation error corrected.

If you mean precompiled Windows binaries, they are still produced and available on the release page as
posted by SP. If you want to compile your own Windows binaries it not too difficult but very long and I might
be able to help. I've gone through it a couple of times and it can be done with all freeware, except for the OS of course.

In short you need Visual Studio Community and Cuda Tools, cminer source and lots of disk space. ccminer.sln is
the configuration file and you double click on it to open the "Solution" in VS. You can edit the properties to add
compute versions (similar to what Linux folks do with makefiles). Then Build Solution. Eventually if everything
works you should find a release directory with a freshly minted ccminer.exe file in it.

I can write up a better tutorial if you like but it will take some time.

that actually would be good ... and highly beneficial jo ...

i for one would like to learn how to build under windows ... hell - ill build a windows machine JUST for it ...

tutor me / us please ...

#crysx

[Eliovp]

ultimately its about building - compiling - rolling out - streamlining ... all clones of one worker ... all with linux - all with exact same hardware - all with ccminer-spmod

Hey Guys...for some of us...this stuff is all greek.     I made no sense of any of it and would really like to keep up with the Jones here. It would be nice to see some Win-install files, just like you had release #s before. So much love would come your way!    

Thanks

A little quotation error corrected.

If you mean precompiled Windows binaries, they are still produced and available on the release page as
posted by SP. If you want to compile your own Windows binaries it not too difficult but very long and I might
be able to help. I've gone through it a couple of times and it can be done with all freeware, except for the OS of course.

In short you need Visual Studio Community and Cuda Tools, cminer source and lots of disk space. ccminer.sln is
the configuration file and you double click on it to open the "Solution" in VS. You can edit the properties to add
compute versions (similar to what Linux folks do with makefiles). Then Build Solution. Eventually if everything
works you should find a release directory with a freshly minted ccminer.exe file in it.

I can write up a better tutorial if you like but it will take some time.

that actually would be good ... and highly beneficial jo ...

i for one would like to learn how to build under windows ... hell - ill build a windows machine JUST for it ...

tutor me / us please ...

#crysx

I have no experience in compiling ccminer for windows.

I do have some for sgminer under windows and i have found out that it's super easy with mingw.

There is even a tutorial for it in the master git branch under the winbuild dir.

Maybe most of those steps apply to ccminer aswell.

[CapnBDL]

ultimately its about building - compiling - rolling out - streamlining ... all clones of one worker ... all with linux - all with exact same hardware - all with ccminer-spmod

Hey Guys...for some of us...this stuff is all greek.     I made no sense of any of it and would really like to keep up with the Jones here. It would be nice to see some Win-install files, just like you had release #s before. So much love would come your way!    

Thanks

A little quotation error corrected.

If you mean precompiled Windows binaries, they are still produced and available on the release page as
posted by SP. If you want to compile your own Windows binaries it not too difficult but very long and I might
be able to help. I've gone through it a couple of times and it can be done with all freeware, except for the OS of course.

In short you need Visual Studio Community and Cuda Tools, cminer source and lots of disk space. ccminer.sln is
the configuration file and you double click on it to open the "Solution" in VS. You can edit the properties to add
compute versions (similar to what Linux folks do with makefiles). Then Build Solution. Eventually if everything
works you should find a release directory with a freshly minted ccminer.exe file in it.

I can write up a better tutorial if you like but it will take some time.

that actually would be good ... and highly beneficial jo ...

i for one would like to learn how to build under windows ... hell - ill build a windows machine JUST for it ...

tutor me / us please ...

#crysx

@joblo

Yes!  How much disk space do I need and will I be able to use the system while it compiles? I only have 1 and it's my mining machine, but I'd really like to learn to Windows compile.  

ASUS x77pro, Intel i7 3770, 16GB, 256 SSD, 1TB SSHD, 1TB HD, 2 TB NAS, Win8.1 pro, CUDA6.5 (have 7 too but not running). None of the HDs are completely empty tho, but I have combined space of ~.75 TB available on computer and ~1 TB on NAS. Running mine equipment is one S3+, three r-Box110s, two 1.3Mh Fury/Zeus, five RedFury USB sticks, three Gridseed duals, and I vid card mine (naturally) as well.

I think that's it. What else do I need to D/L, and install for Windows compiling? Thanks much joblo

[chrysophylax]

for sm_52 support you need this sdk : https://developer.nvidia.com/cuda-downloads-geforce-gtx9xx

else, ive fixed cuda 7.0 support on x11 in my linux branch but... we lose 180kH/s on a 750ti with the same code (compared to cuda 6.5) :/ so... i don't recommend it

so does this mean we have a version that is worse off in terms of 'lower end' card support? ...

or is it just a matter of time before the coding becomes on par with 6.5? ...

btw - where is your git Epsylon3? ...

#crysx

[joblo]

in this case - i did do clean - and that is part of the compile / installation script ... when i took sp's suggestion of copying back the previous makefile from the older v51 compile - the compilation went through without issue ...

clean or distclean? If you modify config files you need to do a distclean. Otherwise there must be an error
in Makefile.am. A diff of the files may make the error more apparent.

[chrysophylax]

in this case - i did do clean - and that is part of the compile / installation script ... when i took sp's suggestion of copying back the previous makefile from the older v51 compile - the compilation went through without issue ...

clean or distclean? If you modify config files you need to do a distclean. Otherwise there must be an error
in Makefile.am. A diff of the files may make the error more apparent.

always distclean ... my apologies ...

i didnt end up at the office today - had other personal errands to run ( unfortunately same with tomorrow - but will have time tomorrow afternoon ) - so i didnt get a chance to make changes and 'play' with the systems ...

you suggested centos 7 from memory ... is that straightforward enough to get cuda installed and running within centos? ...

as im much more familiar with rhel based systems ( centos / scientific linux / fedora ) than debian based systems ( ubuntu ) ...

#crysx

[joblo]

ultimately its about building - compiling - rolling out - streamlining ... all clones of one worker ... all with linux - all with exact same hardware - all with ccminer-spmod

Hey Guys...for some of us...this stuff is all greek.     I made no sense of any of it and would really like to keep up with the Jones here. It would be nice to see some Win-install files, just like you had release #s before. So much love would come your way!    

Thanks

A little quotation error corrected.

If you mean precompiled Windows binaries, they are still produced and available on the release page as
posted by SP. If you want to compile your own Windows binaries it not too difficult but very long and I might
be able to help. I've gone through it a couple of times and it can be done with all freeware, except for the OS of course.

In short you need Visual Studio Community and Cuda Tools, cminer source and lots of disk space. ccminer.sln is
the configuration file and you double click on it to open the "Solution" in VS. You can edit the properties to add
compute versions (similar to what Linux folks do with makefiles). Then Build Solution. Eventually if everything
works you should find a release directory with a freshly minted ccminer.exe file in it.

I can write up a better tutorial if you like but it will take some time.

that actually would be good ... and highly beneficial jo ...

i for one would like to learn how to build under windows ... hell - ill build a windows machine JUST for it ...

tutor me / us please ...

#crysx

@joblo

Yes!  How much disk space do I need and will I be able to use the system while it compiles? I only have 1 and it's my mining machine, but I'd really like to learn to Windows compile.  

ASUS x77pro, Intel i7 3770, 16GB, 256 SSD, 1TB SSHD, 1TB HD, 2 TB NAS, Win8.1 pro, CUDA6.5 (have 7 too but not running). None of the HDs are completely empty tho, but I have combined space of ~.75 TB available on computer and ~1 TB on NAS. Running mine equipment is one S3+, three r-Box110s, two 1.3Mh Fury/Zeus, five RedFury USB sticks, three Gridseed duals, and I vid card mine (naturally) as well.

I think that's it. What else do I need to D/L, and install for Windows compiling? Thanks much joblo

I can post a very rough draft outline which might get you going if you're resourcefull, but be patient.
I don't have specific numbers for disk space but vs_comunity seems to insist on it being on the
system partition although it states "accross all drives" in its requirements. It is probably better to put cuda on that
drive as well. Probably 10 GB combined but that might not take into account temporary bloat during installation.
The ccminer files can be on another drive. How much space
you require depends on how many compute versions are coded and how many old compiles you
leave lying around. Your PC will be usable while compiling unless you are running other CPU intensive stuff.
You can easily be mining while compiling.

Disclaimer: Use at your own risk. I am not responsible for any loss or damage to your computer or your sanity.

1. need at least 20 GB disk space

2. download vs_community, cudatools

3. install vs_community

4. install cuda

5. download and unpack ccminer

6. open ccminer.sln

7. verify release, 32

8. change config to customize compute version
   project->properties->configuration properties->cuda c/c++->device
   select code generation, edit

9 build solution

10 find ccminer.exe in release dir

[joblo]

you suggested centos 7 from memory ... is that straightforward enough to get cuda installed and running within centos? ...

I did succesfully compile ccminer on Centos 7 with Cuda 7 as a test but never actually ran it.
Given Epsylon3's recent post about cuda 7 I'd wait a while for that part of the upgrade. Your
experience with Centos 7 should be identical to Fedora, it's based on F19 IIRC.

[CapnBDL]

ultimately its about building - compiling - rolling out - streamlining ... all clones of one worker ... all with linux - all with exact same hardware - all with ccminer-spmod

Hey Guys...for some of us...this stuff is all greek.     I made no sense of any of it and would really like to keep up with the Jones here. It would be nice to see some Win-install files, just like you had release #s before. So much love would come your way!    

Thanks

A little quotation error corrected.

If you mean precompiled Windows binaries, they are still produced and available on the release page as
posted by SP. If you want to compile your own Windows binaries it not too difficult but very long and I might
be able to help. I've gone through it a couple of times and it can be done with all freeware, except for the OS of course.

In short you need Visual Studio Community and Cuda Tools, cminer source and lots of disk space. ccminer.sln is
the configuration file and you double click on it to open the "Solution" in VS. You can edit the properties to add
compute versions (similar to what Linux folks do with makefiles). Then Build Solution. Eventually if everything
works you should find a release directory with a freshly minted ccminer.exe file in it.

I can write up a better tutorial if you like but it will take some time.

that actually would be good ... and highly beneficial jo ...

i for one would like to learn how to build under windows ... hell - ill build a windows machine JUST for it ...

tutor me / us please ...

#crysx

@joblo

Yes!  How much disk space do I need and will I be able to use the system while it compiles? I only have 1 and it's my mining machine, but I'd really like to learn to Windows compile.  

ASUS x77pro, Intel i7 3770, 16GB, 256 SSD, 1TB SSHD, 1TB HD, 2 TB NAS, Win8.1 pro, CUDA6.5 (have 7 too but not running). None of the HDs are completely empty tho, but I have combined space of ~.75 TB available on computer and ~1 TB on NAS. Running mine equipment is one S3+, three r-Box110s, two 1.3Mh Fury/Zeus, five RedFury USB sticks, three Gridseed duals, and I vid card mine (naturally) as well.

I think that's it. What else do I need to D/L, and install for Windows compiling? Thanks much joblo

I can post a very rough draft outline which might get you going if you're resourcefull, but be patient.
I don't have specific numbers for disk space but vs_comunity seems to insist on it being on the
system partition although it states "accross all drives" in its requirements. It is probably better to put cuda on that
drive as well. Probably 10 GB combined but that might not take into account temporary bloat during installation.
The ccminer files can be on another drive. How much space
you require depends on how many compute versions are coded and how many old compiles you
leave lying around. Your PC will be usable while compiling unless you are running other CPU intensive stuff.
You can easily be mining while compiling.

Disclaimer: Use at your own risk. I am not responsible for any loss or damage to your computer or your sanity.

1. need at least 20 GB disk space

2. download vs_community, cudatools

3. install vs_community

4. install cuda

5. download and unpack ccminer

6. open ccminer.sln

7. verify release, 32

8. change config to customize compute version
   project->properties->configuration properties->cuda c/c++->device
   select code generation, edit

9 build solution

10 find ccminer.exe in release dir

Yeah...sounds easy, huh? Thanks...I'll give it a go. Should be interesting. Now...let's see...time to D/L a few things. Thank you for the help  !!!

[rednoW]

2 CapnBDL
It's ok )))

[CapnBDL]

What do ya know...ccminer.exe compile worked. Next question....what do I delete now...everything in that dir or do I keep it.

Thank you again....think I'll copy those instructions and save 'em someplace.

[joblo]

What do ya know...ccminer.exe compile worked. Next question....what do I delete now...everything in that dir or do I keep it.

Thank you again....think I'll copy those instructions and save 'em someplace.

That was fast. You only really need ccminer.exe. You can delete the rest of the tree.

Edit: For the really addventurous you can also compile in a VM. The only difference is don't
install the drivers with cuda. Probably shouln't do that in any case if you already have
newer drivers already iinstalled. I do that on a linux host because that system has the fastest cpu.

[CapnBDL]

What do ya know...ccminer.exe compile worked. Next question....what do I delete now...everything in that dir or do I keep it.

Thank you again....think I'll copy those instructions and save 'em someplace.

That was fast. You only really need ccminer.exe. You can delete the rest of the tree.

Edit: For the really addventurous you can also compile in a VM. The only difference is don't
install the drivers with cuda. Probably shouln't do that in any case if you already have
newer drivers already iinstalled. I do that on a linux host because that system has the fastest cpu.

As I said in an earlier post, I've tried to compile in the past, but I musta missed a step or something. Your explanation was very good, easy to follow. Already had the needed programs installed. I tired it with git-work ( or whatever it is) a few times also..didn't work out well. I've saved the instructions...we'll see if I can get it to work, in the future.  Thanks....


edit: now if I could just find out what the difference is between scryptN, scryptNf (same or not), and blake, blake2b (same or not)? And do those use the same miner setup? It gets confusing when the names are so close.   

[bensam1231]

Anyone using some 960s? What are you getting for Quark/X11/Neo?
I assume ccminer doesn't scale and needs to be tailored to each cards gen.

you can get 10mhash if you overclock. With standard clocks around 9.2 Mhash

GTX 960--

Mining Quark, I get 10.5Mh/s with +80mhz/240mhz core/mem on the 2gb 960 SSC card with default intensity.  It runs on Win 7 x64.

--scryptr

Thanks for the replies, so it's pretty much on par with it's price point ($200 vs $300 970).

Still looks like the 750tis are the best buy, but they suck balls for density.

Does it pay to OC memory at all? It doesn't seem like memory clocks matter at all with Nvidia compared to AMD.

[CapnBDL]

Anyone using some 960s? What are you getting for Quark/X11/Neo?
I assume ccminer doesn't scale and needs to be tailored to each cards gen.

you can get 10mhash if you overclock. With standard clocks around 9.2 Mhash

GTX 960--

Mining Quark, I get 10.5Mh/s with +80mhz/240mhz core/mem on the 2gb 960 SSC card with default intensity.  It runs on Win 7 x64.

--scryptr

Thanks for the replies, so it's pretty much on par with it's price point ($200 vs $300 970).

Still looks like the 750tis are the best buy, but they suck balls for density.

Does it pay to OC memory at all? It doesn't seem like memory clocks matter at all with Nvidia compared to AMD.

I can tell you that on my 750Ti...what you do with the mem clock matters quite a bit. Surprisingly, I underclock the mem on 1 of my settings to keep it stable.

[sambiohazard]

What do ya know...ccminer.exe compile worked. Next question....what do I delete now...everything in that dir or do I keep it.

Thank you again....think I'll copy those instructions and save 'em someplace.

That was fast. You only really need ccminer.exe. You can delete the rest of the tree.

Edit: For the really addventurous you can also compile in a VM. The only difference is don't
install the drivers with cuda. Probably shouln't do that in any case if you already have
newer drivers already iinstalled. I do that on a linux host because that system has the fastest cpu.

As I said in an earlier post, I've tried to compile in the past, but I musta missed a step or something. Your explanation was very good, easy to follow. Already had the needed programs installed. I tired it with git-work ( or whatever it is) a few times also..didn't work out well. I've saved the instructions...we'll see if I can get it to work, in the future.  Thanks....


edit: now if I could just find out what the difference is between scryptN, scryptNf (same or not), and blake, blake2b (same or not)? And do those use the same miner setup? It gets confusing when the names are so close.   

scrypt is good old scrypt with n factor of 1
scrypt-N uses double the memory per hash and this is fixed.(n factor fixed at 2)
scrypt-N factor has changing/increasing memory requirement with time and you have to change your .bat every time as GPU's memory is fixed.(N factor 2-16 with time, most i have seen)

Does this help? I dont know about blake.

[CapnBDL]

What do ya know...ccminer.exe compile worked. Next question....what do I delete now...everything in that dir or do I keep it.

Thank you again....think I'll copy those instructions and save 'em someplace.

That was fast. You only really need ccminer.exe. You can delete the rest of the tree.

Edit: For the really addventurous you can also compile in a VM. The only difference is don't
install the drivers with cuda. Probably shouln't do that in any case if you already have
newer drivers already iinstalled. I do that on a linux host because that system has the fastest cpu.

As I said in an earlier post, I've tried to compile in the past, but I musta missed a step or something. Your explanation was very good, easy to follow. Already had the needed programs installed. I tired it with git-work ( or whatever it is) a few times also..didn't work out well. I've saved the instructions...we'll see if I can get it to work, in the future.  Thanks....


edit: now if I could just find out what the difference is between scryptN, scryptNf (same or not), and blake, blake2b (same or not)? And do those use the same miner setup? It gets confusing when the names are so close.  

scrypt is good old scrypt with n factor of 1
scrypt-N uses double the memory per hash and this is fixed.(n factor fixed at 2)
scrypt-N factor has changing/increasing memory requirement with time and you have to change your .bat every time as GPU's memory is fixed.(N factor 2-16 with time, most i have seen)

Does this help? I dont know about blake.

Some....does that mean that they can be mined with the same program (ie, ccminer), but you have to use the 'switches' to adjust for the (sounds like) slight differences (mem requirements) in algo?

[pallas]

What do ya know...ccminer.exe compile worked. Next question....what do I delete now...everything in that dir or do I keep it.

Thank you again....think I'll copy those instructions and save 'em someplace.

That was fast. You only really need ccminer.exe. You can delete the rest of the tree.

Edit: For the really addventurous you can also compile in a VM. The only difference is don't
install the drivers with cuda. Probably shouln't do that in any case if you already have
newer drivers already iinstalled. I do that on a linux host because that system has the fastest cpu.

As I said in an earlier post, I've tried to compile in the past, but I musta missed a step or something. Your explanation was very good, easy to follow. Already had the needed programs installed. I tired it with git-work ( or whatever it is) a few times also..didn't work out well. I've saved the instructions...we'll see if I can get it to work, in the future.  Thanks....


edit: now if I could just find out what the difference is between scryptN, scryptNf (same or not), and blake, blake2b (same or not)? And do those use the same miner setup? It gets confusing when the names are so close.   

scrypt is good old scrypt with n factor of 1
scrypt-N uses double the memory per hash and this is fixed.(n factor fixed at 2)
scrypt-N factor has changing/increasing memory requirement with time and you have to change your .bat every time as GPU's memory is fixed.(N factor 2-16 with time, most i have seen)

Does this help? I dont know about blake.

Hmmm no.
Plain scrypt has an n-factor of 10.
Scrypt-n, as in vertcoin and many others, starts at 11 and goes up with time (see the vertcoin thread).
Scrypt with adaptive n-factor, or scrypt-jane, like in yacoin, has a different algorithm for the n-factor and different hash.