Cgminer-neoscrypt - Testing / optimisation / Windows 7, R9 270, Catalyst 13.12
-
It’s very confusing to find how to get neoscrypt mining going, and where to post problems. There is no one description of where things are and generally how to do them and confilicting posts. (posted this in the mining thread by mistake, last night)
I will try once more today to clear AMD and create the .bin files with AMD 13.12. + 3.7.7b today -
- what is the a minerd download, I could have fell back to that.?
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
https://forum.feathercoin.com/index.php?/topic/7934-error-61-clcreatebuffer-padbuffer8/#entry68753
Spent a few hours trying to set up, windows 7 x64, R9 270, Catalyst 13.12
cgminer-neoscrypt 3.7.7b downloaded from neoscrypt page 1.
I’ve tried various settings , and had to get past a couple of (config reading?) errors.
(Error -61: clCreateBuffer (padbuffer8))
After getting it going - I only get HW errors and no accepts.
Any ideas?
-
I’m running windows 7 64bit catalyst 13.12 without any problems, but I am uses an older AMD card.
I use a config file and a batch file.
My cgminer.conf file reads
{
“pools” : [
{
“url” : “stratum+tcp://stratum.pxc.theblocksfactory.com:3332”,
“user” : “XXXXX.1”,
“pass” : “x”
}]
,
“intensity” : “11”,
“vectors” : “1”,
“worksize” : “32”,
“api-mcast-port” : “4028”,
“api-port” : “4028”,
“expiry” : “120”,
“gpu-dyninterval” : “7”,
“gpu-platform” : “0”,
“gpu-threads” : “1”,
“log” : “5”,
“no-pool-disable” : true,
“queue” : “1”,
“scan-time” : “60”,
“shares” : “0”,
“kernel-path” : “/usr/local/bin”
}My Bat file is
cgminer.exe --neoscrypt -I 11 --auto-fan --auto-gpu --gpu-engine 1200 --gpu-memclock 1240 --temp-target 65
Obviously these settings are tailored to my GPU, but hope its of some use to you
-
Cheers Tmuir,
however my conf is virtually identical to yours. Plus, and where it changes, I have tried a range if Intensity from 3 to 14. (so that is unlikely to be the problem I am encountering).
Cross you fingers, my problem is due to a “different file” left by over by AMD 14.9 driver (other than the cgminer .bin(s), which I already deleted as part of testing (of course)).
-
It’s very confusing to find how to get neoscrypt mining going, and where to post problems. There is no one description of where things are and generally how to do them and confilicting posts. (posted this in the mining thread by mistake, last night)
Report issues at:
-
Cheers Tmuir,
however my conf is virtually identical to yours. Plus, and where it changes, I have tried a range if Intensity from 3 to 14. (so that is unlikely to be the problem I am encountering).
Cross you fingers, my problem is due to a “different file” left by over by AMD 14.9 driver (other than the cgminer .bin(s), which I already deleted as part of testing (of course)).
Intensities below 8 are reported to be illegal and will not be consired.
-
Thanks for the fingers crossing, cgminer-neo 3.7.7b now works.
Un-installed AMD driver, used http://www.wagnardmobile.com/DDU/downloads.html to clean AMD from system. Re-installed AMD 13.12.
Recreated bin, using same setup and bat file. Now accepting at 45 KHash/sec. Will update to 14.9 once I’ve had a rest.
-
I am having the same problem as wrapper when testing Neoscrypt gpu mining. I only get HW errors. Also, unless I set the intensity to between 8 and 19, cgminer will not work at all. I get error -61 with no flags set. I have tested this with multiple settings on a HD 7950 and a HD 7990, and get the same results. X11 and scrypt mining work fine with them. I am using AMD 14.9 on both. Any ideas as to the problem?
For 7000 +(r9 280x etc) and lower series cars you should be on 13.12 at the most for neo. R9 290s need to be run in 13.12 and then reinstall 14.xx drivers for them to hit 100+ KH
-
After reinstalling 13.12 and then upgrading - got cgminer working.
cgminer 3.7.7b, R9 270, AMD 14.9.1 beta - windows 7
I got 45KHash with 3.12 and upgraded to 14.9.1 beta and get 50 KHash
That doesn’t seem too bad as R9 270 = 1/3 of a R9 290 and is giving half the hash.
I’ll try vanilla 14.9.1 tomorrow - (A long and tortuous operation on windows) and test that wasn’t glitchy over night.
-
After reinstalling 13.12 and then upgrading - got cgminer working.
cgminer 3.7.7b, R9 270, AMD 14.9.1 beta - windows 7
I got 45KHash with 3.12 and upgraded to 14.9.1 beta and get 50 KHash
That doesn’t seem too bad as R9 270 = 1/3 of a R9 290 and is giving half the hash.
I’ll try vanilla 14.9.1 tomorrow - (A long and tortuous operation on windows) and test that wasn’t glitchy over night.
It only lasted 6 hours and lost contact with the GPU, I’ve turned it down to I - 13 giving ~ 45kHash/s. and left it on AMD 14.9.1. beta to continue testing why it failed. + raised a Github issue on https://github.com/vehre/neo-gpuminer
I’ve forked that project to have a look at some interface changes I thought might improve it, and if there were any enhancements, like better logs, and longer term analysis of performance, port some of 3.8 ? + extra tests, does it still work with scrypt / other algorithms, integration into a merchant solution / minerX. etc…
I’ll ( I suggest) https://github.com/vehre/neo-gpuminerest) raise a [Dev] cgminer-neoscrypt - thread later for further enhancements.
-
I’ve turned it down to Intensity 13 and left the windows 7 system on AMD 14.9.1. beta driver.
To continue testing why 3.7.7b failed. + updated the issue at Github issue on https://github.com/vehre/neo-gpuminer
It lasted 19.5 hours and terminal shut down.
To me this still indicates a problem, I would like to investigate, if it is the 14.9.1 beta AMD driver first.
That is, it would be good to “debug” the gpuminer get more information when it stops. It could then be a simple problem that is causing the glitch occasionally, so worth persueing
I’m a bit over run / too much other stuff to sort out - to do that (dig more into cgminer debug options) , will set up if anyone has more knowledge of gpuminer / do some research to find if there is a debug switch / compile a debug version…
-
It only lasted 6 hours and lost contact with the GPU, I’ve turned it down to I - 13 giving ~ 45kHash/s. and left it on AMD 14.9.1. beta to continue testing why it failed. + raised a Github issue on https://github.com/vehre/neo-gpuminer
I’ve forked that project to have a look at some interface changes I thought might improve it, and if there were any enhancements, like better logs, and longer term analysis of performance, port some of 3.8 ? + extra tests, does it still work with scrypt / other algorithms, integration into a merchant solution / minerX. etc…
I’ll ( I suggest) https://github.com/vehre/neo-gpuminerest) raise a [Dev] cgminer-neoscrypt - thread later for further enhancements.
It’s not the driver - I compiled my bin and ran on 14.9.1 beta and it works fine - the code is seriously half-broken.
-
It’s not the driver - I compiled my bin and ran on 14.9.1 beta and it works fine - the code is seriously half-broken.
Its a working GPU miner tho which is a million miles better than where we were.
-
Its a working GPU miner tho which is a million miles better than where we were.
Okay, fair.
-
Okay, fair.
That’s not to say that we would not appreciate any help with fixes,optimisation or enhancements. :)
-
That’s not to say that we would not appreciate any help with fixes,optimisation or enhancements. :)
I cleaned out a lot of the stupid in the CL file, but I need to find the change that triggers the 14.9 bug so I can release that.
-
I cleaned out a lot of the stupid in the CL file, but I need to find the change that triggers the 14.9 bug so I can release that.
Good to hear, that the application is improved. :)
Are you using github, so you can create pull requests to Avehre’s version of cgminer?
-
Good to hear, that the application is improved. :)
Are you using github, so you can create pull requests to Avehre’s version of cgminer?
No, but as I said, I’ll publish the code when I find that bit.
-
Ugh, shiiiiit. It’s a combination of things. Basically the block mix operation as well as how it’s called. Now I have to water down my salsa. (pun intended)
-
Ugh, shiiiiit. It’s a combination of things. Basically the block mix operation as well as how it’s called. Now I have to water down my salsa. (pun intended)
Shit works on 14.9: https://github.com/wolf9466/neo-gpuminer
I fixed just enough of that disaster to get it to work.
-
nice work, Wolf, linked to watch the github. “optimisation mode” enabled.
