[Dev] NeoScrypt GPU Miner - Public Beta Test
-
I’m only getting this,
14.7 rc3 drivers
[19:21:15] Specified platform that does not exist
[19:21:15] clDevicesNum returned error, no GPUs usable
[19:21:15] All devices disabled, cannot mine! -
Wolf0s newest Hawaii update is really only meant for 290s and up. The 280x has a Tahiti architecture.
-
Wolf0s newest Hawaii update is really only meant for 290s and up. The 280x has a Tahiti architecture.
I’ve only seen it help on Hawaii - doesn’t mean there aren’t magic settings for other cards.
-
Hmm, well I cant get anything other than HW errors either for now. Some people seeing result others cant get it to work. Lets wait and see.
As I said before, I did manage to mod an older version by replacing the neoscrypt.cl with the new one and updating to: --worksize 112 -I 15 -g 1 --thread-concurrency 16384, gave my slower 290 about 12KH/s more and my faster one saw little to no boost.
-
Hmm, well I cant get anything other than HW errors either for now. Some people seeing result others cant get it to work. Lets wait and see.
As I said before, I did manage to mod an older version by replacing the neoscrypt.cl with the new one and updating to: --worksize 112 -I 15 -g 1 --thread-concurrency 16384, gave my slower 290 about 12KH/s more and my faster one saw little to no boost.
Wolf’s builds sgminer binaries with static-linked libraries, so putting in AMD OCL DLLs into the sgminer folder won’t work I am afraid :( You must not be using the right AMD Catalyst drivers.
Edit: Also, he has mentioned before to use multiples of 64 for the worksize. 112 is not a multiple of 64.
Edit: His sgminer build for Hawaii will not work with Catalyst 14.9.x or above.
-
Wolf’s builds sgminer binaries with static-linked libraries, so putting in AMD OCL DLLs into the sgminer folder won’t work I am afraid :( You must not be using the right AMD Catalyst drivers.
Edit: Also, he has mentioned before to use multiples of 64 for the worksize. 112 is not a multiple of 64.
Edit: His sgminer build for Hawaii will not work with Catalyst 14.9.x or above.
It might work - it’ll probably be dead slow, though.
-
Wolf’s builds sgminer binaries with static-linked libraries, so putting in AMD OCL DLLs into the sgminer folder won’t work I am afraid :( You must not be using the right AMD Catalyst drivers.
Edit: Also, he has mentioned before to use multiples of 64 for the worksize. 112 is not a multiple of 64.
Edit: His sgminer build for Hawaii will not work with Catalyst 14.9.x or above.
I think what makes more sense is that it will use the version I linked, regardless of what you have - I need to get an updated Windows version of the driver files to build against.
-
Wolf’s builds sgminer binaries with static-linked libraries, so putting in AMD OCL DLLs into the sgminer folder won’t work I am afraid :( You must not be using the right AMD Catalyst drivers.
Edit: Also, he has mentioned before to use multiples of 64 for the worksize. 112 is not a multiple of 64.
Edit: His sgminer build for Hawaii will not work with Catalyst 14.9.x or above.
Tried 14.4, 14.6, 14.9 all 100% HW errors with his stock config. For straight 290s w112 is about 3% faster than w64 even in the older build, this is not the case for 7970,50, 280x…etc.
-
Tried 14.4, 14.6, 14.9 all 100% HW errors with his stock config. For straight 290s w112 is about 3% faster than w64 even in the older build, this is not the case for 7970,50, 280x…etc.
Yeah - you’ll probably have to build it for now - I’m finding the right files.
-
Tried 14.4, 14.6, 14.9 all 100% HW errors with his stock config. For straight 290s w112 is about 3% faster than w64 even in the older build, this is not the case for 7970,50, 280x…etc.
Unless you are using the exact same environment as him, no configuration will work well. I already brought this issue up to Wolf, and he’s looking into building sgminer either with dynamic links, or static-built against windows 14.6 drivers. I REALLY hope he builds dynamic so that we can use 14.9.x or 14.11 drivers and just swap in 14.6 RC2 OCLs. I game on my miner with the 290x, so it’s a big thing for me to revert back to older drivers and lose game-specific fixes.
-
Well, in previous releases the worksize multiple of 64 thing has been complete hogwash… No reason to start assuming it makes a difference now.
-
Well, in previous releases the worksize multiple of 64 thing has been complete hogwash… No reason to start assuming it makes a difference now.
As the kernel gets better, it will become more true.
-
Anyone else get this with GPU temps? (GPU # 4) I never saw it before using wolf0’s kernel…
-
And topic is dead…
-
Since the neo-scrypt development is stalled, and waiting for wolf’s latest kernel and SGminer modifications to get compiled for windows with the proper files, it appears that this thread is as well.
-
I’m not too well, so can’t mess about too much. I’ve tried sgminer.exe windows compile with R9 270 again. It just stops immediately after starting up. Gone back to cgminer 3.7.7
Is that because sgminer doesn’t work with p2pool’s stratum?
–xintensity 3 -g 2 -w 256 --thread-concurrency 8192
-
noticed that sgminer will not support p2pools
but there is a easy way around that problem
point your miner to miningrigrental, set your price so high no one rents, then set up pool where your rig mines when its not rented(now any p2pool will work)
-
I’m not too well, so can’t mess about too much. I’ve tried sgminer.exe windows compile with R9 270 again. It just stops immediately after starting up. Gone back to cgminer 3.7.7
Is that because sgminer doesn’t work with p2pool’s stratum?
–xintensity 3 -g 2 -w 256 --thread-concurrency 8192
yes sad there is no support of p2p or solo with the version of sgminer/ neoscrypt as of yet. :-
-
Re: confirm no support for p2pool / stratum.
Cheers Wolf, save me doing anything further now, as limited. Also, as Wellenreiter and I have done a lot to make p2pool work and host base public nodes, I’ll have to stick with the old version.
-
I’ve tested p2pool with one of the first versions of Neoscrypt sgminer.
Situation is as follows:
- Using ‘stratum+tcp://p2pool.neoscrypt.de:19327’ without additional parameter fails
- Using ‘http://p2pool.neoscrypt.de:19327’ works as pool automatically switches to the long poll protocol
- Using ‘stratum+tcp://p2pool.neoscrypt.de:19327’ AND ‘–no-extranonce’ works. the pool and the miner are using stratum protocol.
The reason of that behaviour is, that sgminer uses an extension to the original stratum protocol definition called ‘extranonce’ when started without the ‘–no-extranonce’ which is not supported by p2pool nodes.
I think, that the extranonce extension was created to support ASIC mining, so the miner can generate more work on it’s own.
As the Neoscrypt algorithm is currently not implemented on ASICS, there is no disadvantage to disable the extranonce feature in sgminer.
As I’m using a NVIDIA card, I can’t test with the current version of sgminer and the latest kernel.
If somebody could try and post the results here it would be great :)
just direct your miner to p2pool.neoscrypt.de:19327 and specify the --no-extranonce parameter in the start command for your sgminer
