[Dev] NeoScrypt GPU Miner - Public Beta Test

cisahasa

I spent about an hour the other night trying to get mingw to compile 3.7.6. The instructions in the windows.build.txt will definitely get you started - however, they are missing a lot of info. Most of the errors you’ll run into simply require you to google it run the appropriate “mingw-get install XXXXX” command. When you work through the windows build directions, make sure that you pay special attention when downloading libraries and moving files into specific locations for the build. You’ll save yourself a lot of headache if you pay close attention and don’t miss anything. Toward the end of the build, you’ll get an error from “make” regarding a missing jansson.h file. Take a look at the bfgminer windows build directions on github and find the “libjansson” section. It will walk you through manually building this and get rid of that error. Ignore the fact that it wants you to re-download it, these files are already located within the cgminer build directory inside of the “compat” directory.

Cheers.

you are correct, this is just what i hate, lot lot lot of info missing.

just started to install…

i think im fine if just using my installation manager to get past this mingw-get install XXXXX" command thing??

fragilefungi

I got the GPU miner running on my Geforce GTX 570 getting 36.50khash/sec. Stability was an issue at first, but I noticed that one of the threads on the CPU miner that was also running, wasn’t hashing effectively. I reduced the threads on the CPU miner by 1 and stability improved a bit. I tried changing the .bat file to

setx DISPLAY 0

setx GPU_MAX_ALLOC_PERCENT 50

setx GPU_USE_SYNC_OBJECTS 1

cgminer.exe --neoscrypt --worksize 256 --thread-concurrency 400 -I 10 -o

It might have made the stability a bit better, but it was only hashing 0.1khash/sec less and stability still isn’t great. Any tuning hints? I tried changing the intensity to dynamic but that dropped the hash to 6khash/sec and didn’t make it any better.

I think you should consider making a new fork for cpuminer21 because that is the last version is the last one by the cuda team that supports compute 2.0 and it is a design goal to make mining effective on as much equipment as possible.

I am currently back to mining x11 using cpuminer21 because it is just that much more stable even though I could probably be profitable with PXC after trading. I can run cpuminer with neoscrypt at 4 threads and still get 1600khash/sec running x11 on my gpu. Most importantly though, cpuminer21 seams to drop my hashrate before it drops my framerate. If I open up something that requires a lot of GPU the hashrate drops to 1300khash/sec and there isn’t a lot of screen freezes. I can’t even open this forum to make this post while running cgminer without getting a lot of waiting on the chrome not responding. I will probably turn cgminer back on later when I go to bed, but I can’t figure out how to hash neoscrypt while still being able to use my computer.

Alpha Wolf

Anyone given any thought of using cgminer 3.7.3 Kalroth that has xIntensity?

This is a pretty old version but I’m still using it for script mining because to me its the best out there.

More info can be found here

I get 480 kh/s per R9 270 non X with those config settings working LTC, Doge, or even PXC before this latest change.

xIntensity: Very new and still experimental and as far as I know only available from the kalroth release (see below). Seems to work flawlessly so far and gives a much more wide range of intensity. You can only use xintensity OR intensity NOT both. Calculated instead by the number of shaders your gpu has and multiplied by xintensity (Shaders*xI). So for example my 7870 and 270x have 1280 shaders, so any number I put in as the xintensity would be multiplied by 1280. both 80 (102400 which if you view above is equal to 16.7ish) and 111 (142080=17.25ish) seem to work really well on single thread I am not decided yet which is best will take some testing still . Due to this I have also been able to get 2 threads to work which was not possible in the past. Its actually more productive and less system intensive to run 2 threads. I managed to get mine to run at xintensity=4 gpu-threads=2. This was NOT possible using normal intensity increases, Thanks kalroth!

{
"pools" : [
        {
        "url" : "stratum+tcp://pool.ftc-c.com:10554",
        "user" : "Pn18tqfzFNPUcFjJRq1GRYdYDJjKTBNGpq",
        "pass" : "x"
        }
]
,
"xintensity" : "4,4",
"vectors" : "1,1",
"worksize" : "0,0",
"kernel" : "darkcoin,darkcoin",
"lookup-gap" : "2,2",
"gpu-threads" : "2,2",
"thread-concurrency" : "8193,8193",
"gpu-engine" : "1100,1100,",
"gpu-fan" : "auto,auto",
"gpu-memclock" : "1450,1450",
"gpu-memdiff" : "0,0",
"gpu-powertune" : "0,0",
"gpu-vddc" : "0.000,0.000",
"temp-cutoff" : "90,90",
"temp-overheat" : "85,85",
"temp-target" : "70,70",
"api-mcast-port" : "4028",
"api-port" : "4028",
"expiry" : "1",
"failover-only" : true,
"failover-switch-delay" : "30",
"gpu-dyninterval" : "7",
"gpu-platform" : "0",
"log" : "5",
"log-dateformat" : "0",
"no-pool-disable" : true,
"queue" : "0",
"scan-time" : "1",
"scrypt" : true,
"temp-hysteresis" : "3",
"shares" : "0",
"kernel-path" : "/usr/local/bin",
"device" : "0-1"
}

Alpha Wolf

I got the GPU miner running on my Geforce GTX 570 getting 36.50khash/sec. Stability was an issue at first, but I noticed that one of the threads on the CPU miner that was also running, wasn’t hashing effectively. I reduced the threads on the CPU miner by 1 and stability improved a bit. I tried changing the .bat file to

setx DISPLAY 0

setx GPU_MAX_ALLOC_PERCENT 50

setx GPU_USE_SYNC_OBJECTS 1

cgminer.exe --neoscrypt --worksize 256 --thread-concurrency 400 -I 10 -o

It might have made the stability a bit better, but it was only hashing 0.1khash/sec less and stability still isn’t great. Any tuning hints? I tried changing the intensity to dynamic but that dropped the hash to 6khash/sec and didn’t make it any better.

I think you should consider making a new fork for cpuminer21 because that is the last version is the last one by the cuda team that supports compute 2.0 and it is a design goal to make mining effective on as much equipment as possible.

I am currently back to mining x11 using cpuminer21 because it is just that much more stable even though I could probably be profitable with PXC after trading. I can run cpuminer with neoscrypt at 4 threads and still get 1600khash/sec running x11 on my gpu. Most importantly though, cpuminer21 seams to drop my hashrate before it drops my framerate. If I open up something that requires a lot of GPU the hashrate drops to 1300khash/sec and there isn’t a lot of screen freezes. I can’t even open this forum to make this post while running cgminer without getting a lot of waiting on the chrome not responding. I will probably turn cgminer back on later when I go to bed, but I can’t figure out how to hash neoscrypt while still being able to use my computer.

You can give my command line a try to see if it will help you,

I use this on a Geforce GTX 560M with cgminer version 3.7.5 works well with no HW errors and very few rejects.

Drop the --thread-concurrency 400 completely from the command line.

This produced the best kh/s of all settings tested with no HW errors and many less rejects, only get a few reject

every now and then now which is normal.

Edit: almost forgot in the folder that holds cgminer you will find a .bin file that will look something like this:

neoscrypt140909GeForce GTX 560Mgtc8128w128l4.bin

This you will want to move to a empty folder if you wish to save it or delete it before running the new commander line so it can

create a new neoscrypt140909GeForcexxxxxx.bin for your new settings. If you have done quite a few different command line settings

there will probably be more than one, move or remove them all.

cgminer.exe --neoscrypt --worksize 128 -I 10 -o stratum+tcp://p2pool.maeh.org:10554 -u Pn18tqfzFNPUcFjJRq1GRYdYDJjKTBNGpq -p x

einkerl

I’ve adapted bfgminers windows build.txt to compile the gpu miner for AMD cards.

Somebody please check my sloppy work and add what i surely forgot, it would be nice if somebody could add the instructions for Nvidia.

https://mega.co.nz/#!IN92iKzB!7T1QNhlHrC3ThjWHv55voOVBL5xBSLSyfV4VnuSxe-A

Also a link to version 3.7.7b that i compiled with these instructions

https://mega.co.nz/#!FcVTEQyQ!ozPVAzZJCIGm7-nbqB3E4y1xudHI62g6YVfF_YI_GUI

ghostlander

HD4890 doesn’t work. No support for cl_khr_byte_addressable_store, so no chance.

HD5870 works, but delivers 6KH/s only. Expected 1/2 of HD7970, i.e. 20KH/s at least.

Can pull 5KH/s out of a GT430 which is a low end card with a passive cooling.

vehre

What did you expect? The kernel in the regular cgminer has not gotten any optimizations. Unfortunately most of the time was spend in figuring the changes in the protocol.

To get more out of the HD5870 try to play with the worksize -w and intensity -I

I suggest starting with -w 128 and -I 8 and than increasing -I in steps of one untill the memory can’t get allocated anymore

and retry this series with -w 256 and -w 512, then choose the best result for your card and system.

Allways note down the number of hashes you get while running for an equal number of minutes.

fragilefungi

You can give my command line a try to see if it will help you,

I use this on a Geforce GTX 560M with cgminer version 3.7.5 works well with no HW errors and very few rejects.

Drop the --thread-concurrency 400 completely from the command line.

This produced the best kh/s of all settings tested with no HW errors and many less rejects, only get a few reject

every now and then now which is normal.

Edit: almost forgot in the folder that holds cgminer you will find a .bin file that will look something like this:

neoscrypt140909GeForce GTX 560Mgtc8128w128l4.bin

This you will want to move to a empty folder if you wish to save it or delete it before running the new commander line so it can

create a new neoscrypt140909GeForcexxxxxx.bin for your new settings. If you have done quite a few different command line settings

there will probably be more than one, move or remove them all.
cgminer.exe --neoscrypt --worksize 128 -I 10 -o stratum+tcp://p2pool.maeh.org:10554 -u Pn18tqfzFNPUcFjJRq1GRYdYDJjKTBNGpq -p x
Thanks! I dropped the --thread-concurrency 400 and put gpu max % back to 100. It is running a lot smoother. It still isn’t as smooth as ccminer21. Chrome browser is usable now, but there was still a waiting for application when I switched back to the forum. I don’t have any problems with low framerates or waiting for applications with ccminer21, but this is a good start.

vehre

You can’t be using the latest cgminer 3.7.7b, when thread-concurrency is supported by the neoscrypt kernel. 3.7.7b dropped that support in favour of computing the amount of memory needed itself.

Note, when scrypt was selected during configure (autogen.sh), then the command-line option will be accepted, but is not used for neoscrypt.

Alpha Wolf

@fragilefungi

My guess is its something to do with Chrome or the amount of memory your system has as for the lag.

Could also be the use of bandwidth causing the slow down. I use Firefox and play games online while

mining PXC, but its not a game that’s to demanding “Total Domination” on the video card tho and no real loss to my hash rate either.

fragilefungi

OK I just got 3.7.7b up and running. For my command line I used:

setx DISPLAY 0

setx GPU_MAX_ALLOC_PERCENT 100

setx GPU_USE_SYNC_OBJECTS 1

cgminer.exe --neoscrypt -I 11 -w32 -g 2 -o address -p x

I am getting 5khash/sec more than the previous version and I am pretty sure there is less lag. Progress!!!

Can I get some info on the FTC testnet? I am really not liking how the price of PXC is falling and would love to point this over to a FTC neoscrypt pool.

fragilefungi

I did notice one potential bug. When I start the gpu miner while the cpuminer is running, one of the cpu threads stops hashing. I turn the threads down to 3 and get the same hashrate as 4 in the cpuminer. Cpuminer runs fine on 4 threads doing neoscrypt if the gpu is mining x11. Any thoughts? It is only 3khash/sec but still it seems weird.

EDIT: I just tested Darkcoing cpuminer v1.3 running while cgminer 3.7.7b was also running. The darkcoin cpuminer worked better on 3 threads as well. Is it possible that cgminer needs to use a dedicated cpu thread to run?

Alpha Wolf

I played with 3.7.3 Kalroth some interesting output. xI:4 T:2 this version should be looked at as a contender I would think.

sgminer 4.1 worked about the same with a little less hash rate.

Coding it over to neoscript might be a pain since so much time has been put into other versions.

{
"pools" : [
	{
		"url" : "stratum+tcp://p2pool.maeh.org:10554",
		"user" : "Pn18tqfzFNPUcFjJRq1GRYdYDJjKTBNGpq",
		"pass" : "x"
	}
]
,
"xintensity" : "4",
"vectors" : "1",
"worksize" : "256",
"kernel" : "poclbm",
"lookup-gap" : "0",
"gpu-threads" : "2",
"thread-concurrency" : "0",
"gpu-engine" : "0-0",
"gpu-fan" : "0-0",
"gpu-memclock" : "0",
"gpu-memdiff" : "0",
"gpu-powertune" : "0",
"gpu-vddc" : "0.000",
"temp-cutoff" : "95",
"temp-overheat" : "0",
"temp-target" : "0",
"api-mcast-port" : "4028",
"api-port" : "4028",
"expiry" : "120",
"failover-switch-delay" : "60",
"gpu-dyninterval" : "7",
"gpu-platform" : "0",
"log" : "5",
"log-dateformat" : "0",
"no-pool-disable" : true,
"queue" : "1",
"scan-time" : "60",
"temp-hysteresis" : "3",
"shares" : "0",
"kernel-path" : "/usr/local/bin"
}

ghostlander

What did you expect? The kernel in the regular cgminer has not gotten any optimizations. Unfortunately most of the time was spend in figuring the changes in the protocol.

To get more out of the HD5870 try to play with the worksize -w and intensity -I

I suggest starting with -w 128 and -I 8 and than increasing -I in steps of one untill the memory can’t get allocated anymore
and retry this series with -w 256 and -w 512, then choose the best result for your card and system.

Allways note down the number of hashes you get while running for an equal number of minutes.

I’ve made enough research before posting. 6KH/s is as much as it can do with --thread-concurrency 8192 -w 128 -I 13. ATI/AMD cards of their VLIW5/VLIW4 architectures require more optimisation than newer GCN or NVIDIA CUDA cores. They also need much higher intensities for the best performance.

An older and weaker 9800GTX which has never been any good to mining produces 3.5KH/s without HW errors (-I 11) and 4.7KH/s with them (-I 12). HD5870 vs. 9800GTX under Scrypt is 400KH/s vs. 50KH/s.

kris_davison

Well levelling the playing field is a good thing it means it can be more “fair” and potentially cheaper to mine?

tmuir12

Just compiled 3.7.7b and I’ve only been running for a few minutes but it looks to be just ever so faster than the previous versions for me.

Will let it tun for a while and report back

daimyo

folks, can you upload a precompiled 3.7.7b ?

tmuir12

folks, can you upload a precompiled 3.7.7b ?

Here you go, for windows

https://www.dropbox.com/s/mbteys6opg4odlj/cgminer-3.7.7.bNeoscrypt.zip?dl=0

cisahasa

I’ve adapted bfgminers windows build.txt to compile the gpu miner for AMD cards.

Somebody please check my sloppy work and add what i surely forgot, it would be nice if somebody could add the instructions for Nvidia.

https://mega.co.nz/#!IN92iKzB!7T1QNhlHrC3ThjWHv55voOVBL5xBSLSyfV4VnuSxe-A

Also a link to version 3.7.7b that i compiled with these instructions

https://mega.co.nz/#!FcVTEQyQ!ozPVAzZJCIGm7-nbqB3E4y1xudHI62g6YVfF_YI_GUI

Copy libglib-2.0-0.dll from C:\Program Files\GTK2-Runtime\bin to C:\MinGW\bin

is this missing file intl.dll? -did not help

edit: reinstalled mingw and gpu mining is now found

compiled and hashing!

i used CFLAGS=“-O2 -msse2” instead of -02 -g

file size 519KB instead of 1436KB, what is changed? working fine…

leaving 280x/3.7.7b working with -g 2 -w 24 -I 13

daimyo

tmuir12, Chrome doesnt even let me download it… :D