CCminer(SP-MOD) Modded GPU kernels.

[pallas]

profitability for the usual algos is going down, anyone knows some new one (or old one to revive) worth working on?

[chrysophylax]

profitability for the usual algos is going down, anyone knows some new one (or old one to revive) worth working on?

yup ... x11 ...

not becuase granite is x11 - or anything ... just sayin ...

...

#crysx

[Genoil]

Sorry for going offtopic, but I know there's quite a few Linux coders in here with GTX750. Would anyone care to compile and run this kernelon Linux with a GTX750(Ti) (some small mods are required to build it on Linux, such as the random() function and nullptr)? Then change cmd line parameter from 1024 to 1536 and tell me if there's a difference or not?

Background info here: https://devtalk.nvidia.com/default/topic/878455/gtx750ti-and-buffers-gt-1gb-on-win7

Thx

[scryptr]

profitability for the usual algos is going down, anyone knows some new one (or old one to revive) worth working on?

NEOSCRYPT--

There are couple coins with NeoScrypt algo that have low difficulty and good volume (diff<1, vol~2.5 BTC).  UFOCoin is one of them.  I still cannot solo-mine FeatherCoin with sp_'s CCminer, and receive communications errors with the wallet.  It may be the error that T-Nelson pointed out, where a 168 bit data block is transmitted as a 128 bit data block?

SecureCoin blocks keep coming in with the Quark algo.  I might download the UFOCoin wallet and try it, but I think that there is still some code to tidy up.       --scryptr

[t-nelson]

Sorry for going offtopic, but I know there's quite a few Linux coders in here with GTX750. Would anyone care to compile and run this kernelon Linux with a GTX750(Ti) (some small mods are required to build it on Linux, such as the random() function and nullptr)? Then change cmd line parameter from 1024 to 1536 and tell me if there's a difference or not?

Background info here: https://devtalk.nvidia.com/default/topic/878455/gtx750ti-and-buffers-gt-1gb-on-win7

Thx

Driver: 352.39

Code:

miner0@miner0:/dist$ ./a.out 
Creating buffer of size 1073741824 bytes...
75.266914 GB/s
miner0@miner0:/dist$ ./a.out 
Creating buffer of size 1610612736 bytes...
23.446905 GB/s

EDIT:  Results are the same with CUDA Toolkit 6.5 and 7.5.

[flipclip]

where do you see these "git numbers" ? git is not svn...

It is from github at the very top of the page where it says "#### commits ## branches ## releases ..." an example would be from your fork "git 566" is "commit fade2b74".  And yes it is very confusing. 

[scryptr]

where do you see these "git numbers" ? git is not svn...

It is from github at the very top of the page where it says "#### commits ## branches ## releases ..." an example would be from your fork "git 566" is "commit fade2b74".  And yes it is very confusing.  

COMMIT NUMBERS--

I usually refer to commits/builds by the commit number.  It is at the upper left of the page.  Commit numbers are sequential.  The do not, however, help with git "checkout" commands, like the hash value on the upper right.  I still do not understand git checkout syntax well, but I use the commit number when referring to a specific build between releases while posting.

--scryptr

[t-nelson]

where do you see these "git numbers" ? git is not svn...

It is from github at the very top of the page where it says "#### commits ## branches ## releases ..." an example would be from your fork "git 566" is "commit fade2b74".  And yes it is very confusing.  

COMMIT NUMBERS--

I usually refer to commits/builds by the commit number.  It is at the upper left of the page.  Commit numbers are sequential.  The do not, however, help with git "checkout" commands, like the hash value on the upper right.  I still do not understand git checkout syntax well, but I use the commit number when referring to a specific build between releases while posting.

--scryptr

To clarify, that is the commit count, not an index, and is a GitHub feature, nothing to do with git.  This number is mostly useless as it can be invalidated in a number of ways.  With git, generally we refer to a commit by the first 7 chars of the sha1 hash.

Example:
r69 -> 989737b6a5149f1539fa6783106dd755ebeaeb7c -> 989737b

[scryptr]

where do you see these "git numbers" ? git is not svn...

It is from github at the very top of the page where it says "#### commits ## branches ## releases ..." an example would be from your fork "git 566" is "commit fade2b74".  And yes it is very confusing.  

COMMIT NUMBERS--

I usually refer to commits/builds by the commit number.  It is at the upper left of the page.  Commit numbers are sequential.  The do not, however, help with git "checkout" commands, like the hash value on the upper right.  I still do not understand git checkout syntax well, but I use the commit number when referring to a specific build between releases while posting.

--scryptr

To clarify, that is the commit count, not an index, and is a GitHub feature, nothing to do with git.  This number is mostly useless as it can be invalidated in a number of ways.  With git, generally we refer to a commit by the first 7 chars of the sha1 hash.

Example:
r69 -> 989737b6a5149f1539fa6783106dd755ebeaeb7c -> 989737b

THANKS FOR CLARIFICATION--

I use the commit number for its value as an index.  I apprecate the information, I know that the programmer needs a specific point to grab the code.  The reader needs a sequential number to see about where the stuff is between releases.

--scryptr

P.S.  I think solo-mining is still broken with NeoScrypt.       --scryptr

[theLosers106]

Hi,

I'm a newbie to mining with nVidia GPUs and would like some help getting mine working.. I've had some experience with sgminer but couldn't get ccminer to work.. I'm mainly trying to mine VertCoin (Lyra2REv2) on NiceHash but I never get any accepted shares and my GPU load is very low.. I'm on Windows 10 right now with the latest driver and with the latest copy of the executable. Any help would be really appreciated.

-- theLosers106

[sp_]

ccminer.exe -u 1CTiNJyoUmbdMRACtteRWXhGqtSETYd6Vd -p s -a lyra2v2 -o stratum+tcp://lyra2rev2.eu.nicehash.com:3347

[scryptr]

Hi,

I'm a newbie to mining with nVidia GPUs and would like some help getting mine working.. I've had some experience with sgminer but couldn't get ccminer to work.. I'm mainly trying to mine VertCoin (Lyra2REv2) on NiceHash but I never get any accepted shares and my GPU load is very low.. I'm on Windows 10 right now with the latest driver and with the latest copy of the executable. Any help would be really appreciated.

-- theLosers106

FOR STARTERS--

The command line for ccminer should be:  

"ccminer -a lyra2v2 -o stratum+tcp://yourpool.com:port -u username.wrkr1 -p x"

Make sure that your pool url and the port for Lyra2v2 match properly.  The syntax for username, workers, and passwords vary per pool, but each pool usually explains that on the web.  The algorithm is not called "lyra2rev2" in ccminer, sgminer uses that term.       --scryptr

[zTheWolfz]

T-Nelson : Transaction ID: a0eab413368c05e439aecb7325e26aa283e80102cdb1cc36f82470e5259dda92-000
Sp_ : Transaction ID: dae739822e580e450b0cb4921a99a39311f66e11e75eca68ee0a71558830031a-000
I don't solo mine much now days but I still have this one hobby coin I like to mine at times.
Its good that the support can be there when I do want to play around.
Thanks guys for your hard work.
Can I get a private miner for that price. 

Thank you for your support. You just need to donate this amount 10 times and then you will get a profitable private miner.

2x that size already sent to you 8 to go, or can it work that way?
BTW this is a full 24 hours work for all my hardware you received. I make on avg. 0.01 per day.
this is before the power cost, the cost of the hardware & AC to cool them, not included.
If I would actually do the math I would probably see I'm in the whole to start with.  
not that it matters I just like doing this. I have to do something with all this hardware I have,
it can't just let it set idle or power off.

[theLosers106]

ccminer.exe -u 1CTiNJyoUmbdMRACtteRWXhGqtSETYd6Vd -p s -a lyra2v2 -o stratum+tcp://lyra2rev2.eu.nicehash.com:3347

Hi,

I'm a newbie to mining with nVidia GPUs and would like some help getting mine working.. I've had some experience with sgminer but couldn't get ccminer to work.. I'm mainly trying to mine VertCoin (Lyra2REv2) on NiceHash but I never get any accepted shares and my GPU load is very low.. I'm on Windows 10 right now with the latest driver and with the latest copy of the executable. Any help would be really appreciated.

-- theLosers106

FOR STARTERS--

The command line for ccminer should be:  

"ccminer -a lyra2v2 -0 stratum+tcp://yourpool.com:port -u username.wrkr1 -p x"

Make sure that your pool url and the port for Lyra2v2 match properly.  The syntax for username, workers, and passwords vary per pool, but each pool usually explains that on the web.  The algorithm is not called "lyra2rev2" in ccminer, sgminer uses that term.       --scryptr

Thanks for the quick reply.. Yes I have that same config but still can't get it to work.. If it helps I'm trying to mine on a 820m GPU while waiting for my 960 to arrive.. just wanted to try it out first on my laptop..

[zTheWolfz]

Hi,

I'm a newbie to mining with nVidia GPUs and would like some help getting mine working.. I've had some experience with sgminer but couldn't get ccminer to work.. I'm mainly trying to mine VertCoin (Lyra2REv2) on NiceHash but I never get any accepted shares and my GPU load is very low.. I'm on Windows 10 right now with the latest driver and with the latest copy of the executable. Any help would be really appreciated.

-- theLosers106

Would help to know the hardware used. This ccminer only works with maxwell cards.
Cards below Maxwell will only idle after load of the software.

Code:

The NVIDIA GeForce 820M (or GT 820M) is an entry-level DirectX 12 compatible graphics card announced in January 2014. 
Its core is based on the 28nm GF117 chip (Fermi architecture) and is equipped with 64-bit DDR3 memory. 

[t-nelson]

profitability for the usual algos is going down, anyone knows some new one (or old one to revive) worth working on?

NEOSCRYPT--

There are couple coins with NeoScrypt algo that have low difficulty and good volume (diff<1, vol~2.5 BTC).  UFOCoin is one of them.  I still cannot solo-mine FeatherCoin with sp_'s CCminer, and receive communications errors with the wallet.  It may be the error that T-Nelson pointed out, where a 168 bit data block is transmitted as a 128 bit data block?

SecureCoin blocks keep coming in with the Quark algo.  I might download the UFOCoin wallet and try it, but I think that there is still some code to tidy up.       --scryptr

Looking at the code for Feathercoin and Phoenixcoin, they seem derivative and to send an 84byte blockheader since switching from scrypt to neoscrypt on a fifth and fourth hardfork, respectively.  However, from what I can gather, neoscrypt wants an 80byte header, as ccminer handles.  I'm not sure if they're sending "padding" for the nonce or it's a bug on their end, there are no comments in the code for assistance.  Does this work in djm34 or tpruvpot forks?

UFOCoin uses scrypt, so should have a 128byte header and work.  From a brief glance anyway.  It could be some other bug.

[t-nelson]

where do you see these "git numbers" ? git is not svn...

It is from github at the very top of the page where it says "#### commits ## branches ## releases ..." an example would be from your fork "git 566" is "commit fade2b74".  And yes it is very confusing.  

COMMIT NUMBERS--

I usually refer to commits/builds by the commit number.  It is at the upper left of the page.  Commit numbers are sequential.  The do not, however, help with git "checkout" commands, like the hash value on the upper right.  I still do not understand git checkout syntax well, but I use the commit number when referring to a specific build between releases while posting.

--scryptr

To clarify, that is the commit count, not an index, and is a GitHub feature, nothing to do with git.  This number is mostly useless as it can be invalidated in a number of ways.  With git, generally we refer to a commit by the first 7 chars of the sha1 hash.

Example:
r69 -> 989737b6a5149f1539fa6783106dd755ebeaeb7c -> 989737b

THANKS FOR CLARIFICATION--

I use the commit number for its value as an index.  I apprecate the information, I know that the programmer needs a specific point to grab the code.  The reader needs a sequential number to see about where the stuff is between releases.

--scryptr

P.S.  I think solo-mining is still broken with NeoScrypt.       --scryptr

Do what you want, but so far as historical record goes, it's completely useless.  I could squash the entire git history to 1 commit and that counter would go back to 1.  Or rebase away some commits in the middle and reduce it by 500.  Anyone who reads that number in the future may or may not wind up looking at the same commit (nevermind the fact that you'll have to manually count commits to find it).  IMO, making up your own nomenclature only serves to confuse anyone trying to help themselves and thus is a detriment to the community.  The SHA1 is right there to c/p.

[theLosers106]

Hi,

I'm a newbie to mining with nVidia GPUs and would like some help getting mine working.. I've had some experience with sgminer but couldn't get ccminer to work.. I'm mainly trying to mine VertCoin (Lyra2REv2) on NiceHash but I never get any accepted shares and my GPU load is very low.. I'm on Windows 10 right now with the latest driver and with the latest copy of the executable. Any help would be really appreciated.

-- theLosers106

Would help to know the hardware used. This ccminer only works with maxwell cards.
Cards below Maxwell will only idle after load of the software.

Code:

The NVIDIA GeForce 820M (or GT 820M) is an entry-level DirectX 12 compatible graphics card announced in January 2014. 
Its core is based on the 28nm GF117 chip (Fermi architecture) and is equipped with 64-bit DDR3 memory. 

I see.. That's the problem.. so my new 960 should work with this ccminer right? If I still want to run ccminer on my 820m, which fork of the ccminer should I use or is it not possible?

[scryptr]

ccminer.exe -u 1CTiNJyoUmbdMRACtteRWXhGqtSETYd6Vd -p s -a lyra2v2 -o stratum+tcp://lyra2rev2.eu.nicehash.com:3347

Hi,

I'm a newbie to mining with nVidia GPUs and would like some help getting mine working.. I've had some experience with sgminer but couldn't get ccminer to work.. I'm mainly trying to mine VertCoin (Lyra2REv2) on NiceHash but I never get any accepted shares and my GPU load is very low.. I'm on Windows 10 right now with the latest driver and with the latest copy of the executable. Any help would be really appreciated.

-- theLosers106

FOR STARTERS--

The command line for ccminer should be:  

"ccminer -a lyra2v2 -o stratum+tcp://yourpool.com:port -u username.wrkr1 -p x"

Make sure that your pool url and the port for Lyra2v2 match properly.  The syntax for username, workers, and passwords vary per pool, but each pool usually explains that on the web.  The algorithm is not called "lyra2rev2" in ccminer, sgminer uses that term.       --scryptr

Thanks for the quick reply.. Yes I have that same config but still can't get it to work.. If it helps I'm trying to mine on a 820m GPU while waiting for my 960 to arrive.. just wanted to try it out first on my laptop..

TYPO-

The zero should have been a small "-o".  Apologies.       --scryptr

[Genoil]

Sorry for going offtopic, but I know there's quite a few Linux coders in here with GTX750. Would anyone care to compile and run this kernelon Linux with a GTX750(Ti) (some small mods are required to build it on Linux, such as the random() function and nullptr)? Then change cmd line parameter from 1024 to 1536 and tell me if there's a difference or not?

Background info here: https://devtalk.nvidia.com/default/topic/878455/gtx750ti-and-buffers-gt-1gb-on-win7

Thx

Driver: 352.39

Code:

miner0@miner0:/dist$ ./a.out 
Creating buffer of size 1073741824 bytes...
75.266914 GB/s
miner0@miner0:/dist$ ./a.out 
Creating buffer of size 1610612736 bytes...
23.446905 GB/s

EDIT:  Results are the same with CUDA Toolkit 6.5 and 7.5.

Thanks a lot for testing. The kernel is supposed to be an extremely simplified version of the ethash (Ethereum) algo to point out a bug with Windows/GTX750Ti. But it seems it is a little bit more complicated. Well, unless you experience a similar bandwidth drop between running ethminer in benchmark vs. real mining mode. But there are quite a few people happily miner ETH on Linux with GTX750, so it's back to the drawing table I guess to find the bug.

--edit--

on second look, it's actually much better than what I observe on Windows, where the bandwidth drops much faster. ~6GB/s at 1536M of buffer