Quote from: t-nelson on September 25, 2015, 05:06:05 AM

Quote from: zTheWolfz on September 25, 2015, 02:17:08 AM

Quote from: t-nelson on September 24, 2015, 11:12:34 PM

Quote from: scryptr on September 24, 2015, 10:42:42 PM

Quote from: t-nelson on September 24, 2015, 10:36:59 PM

Quote from: pallas on September 24, 2015, 08:30:13 PM

Possible fix for neoscrypt solo mining by tpruvot:

https://github.com/tpruvot/ccminer/commit/8ec5dd7d8e8ffea2bb710d0013ea657473de1f51

Yeah we worked it out on IRC. I'm 100% sure this needs fixed in the wallets, not the miner. I'm willing to add it based on a non-default flag for the time being though.

THANK YOU!--

You may very well be right about the wallet. I can get DJM34's CCminer launched, and communicate initially with the wallet, but I never get any card hash reports, only an initial blue neoscrypt block number report to the console. With sp_'s CCminer, I cannot even get that far, just a red error message.

--scryptr

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

Not sure this would be of any help, but this version of cgminer 3.7.8 works with all cards I have tested so far. From GTX260 up to GTX960.
http://cryptomining-blog.com/3715-new-cgminer-3-7-8-with-improved-neoscrypt-performance/
Only problem is the slow hashrate it gives, max is 80kh/s for a 960 Shocked

around 35kh/s on a 760 and 80kh/a on AMD R270 non X model OCed. 1100/1450

That'd likely have to be on someone else's plate. My CUDA chops are noob at best and will remain that way until I'm happy with core code.

EDIT: This dumbass forum needs markup syntax checking...

I think you have already found the problem and info needed. Was only thinking out loud that there might be a Linux version
somewhere with files much like the ones for ccminer and .cpp to have a closer look at what they did in there builds.

Thanks for your time in looking into these problems.