For the HD5000 and HD6000: can you send the output of “clinfo” for these card? I am most interested in the extensions section. There needs to be the extension cl_khr_byte_addressable_store available or we stand no chance to get the cl-kernel running on this cards.

Ups, only read the last two messages here after merging Wolf0’s kernel into the master-branch. So master-github is now on 3.7.8 including wolf’s current kernel.

I have tested it on an Nvidia GPU and had no issues, but running only for short periods of time. Let’s monitor that.

Did you notice any extra performance with 3.7.7c? I just compiled it tonight and didn’t notice any difference. One thing I will mention for anyone who decides to try 3.7.7c, is that it was actually overwriting my 13.x bin files with new 14.x ones. You need to follow the directions from seand52 about copying AMD driver files on this other post unless you want 100% hardware errors (or grab 3.7.7c from my dropbox):

https://forum.feathercoin.com/index.php?/topic/7978-hw-errors/

https://www.dropbox.com/s/waedf2ghtc33zun/NeoScrypt-3.7.7c.zip?dl=0

Please read the git log before complaining. 3.7.7c is a stability release that does not strive for any further speed up.

Please add support for old cards, 5800 6800 6900 series. Please!

Cards that lack the byte-addressable capability can’t be used for neoscrypt currently. Rewriting the algorithm to get rid of the necessity of byte addressing is not in the currenty scope.

Thanks :)

that file says '-thread-concurrency,******but when i try that it says unrecognized **

what is the way to set concurrency in this neo miner?

Thread-concurrency is obsolete now. The thread-concurrency and intensity flags both controlled the same, allowing one to override the necessities of the other and therefore possibly allowing for memory corruption and bad results.

Has anyone compiled https://github.com/vehre/neo-gpuminer from source on Linux and successfully mined PXC or FTC on the testnet? All I get are hw errors, with any settings I’ve tried. Specifying no options to cgminer beyond a stratum connection and user/pass, or using even a bare minimum of -I 12 -w 32 -g 2 doesn’t help. I’m on 14.6 catalyst drivers with APP SDK 2.9.

I’m happy to provide any additional logs/info/settings or help troubleshoot if anyone has any suggestions.

The bare minimum would be -I 8 -w 128 and -g 1

I am mining PXC on the life net and have no problems yet. FTC is not yet on neoscrypt therefore mining on testnet is ok and should work, although I haven’t tested.

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.

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:

https://github.com/vehre/neo-gpuminer/issues

Hi curiosity81,

what developerS? As far as I know, is there only one actively (more or less) doing development on cgminer for neoscrypt.

Anyway, on a 32-bit system size_t usually is a 32 bit value. I.e., any data one wants to store in there has to be less than 2^32. What happens, when that value is exceeded is undefined. In your case the system resided to use 0, which shouldn’t be. I will take a look into it, as soon as possible.

Could you meanwhile file an issue at:

https://github.com/vehre/neo-gpuminer/issues

so that I don’t forget about this?

As a work around try to start cgminer with a low intensity, i.e., start with -I 8 and raise it untill cgminer can’t alloc the buffer anmore. The default of cgminer is to use dynamic mode, with tries to allocate a buffer as large as the one you pointed out, but I did not think about system with 32-bit. I am sorry for the bother.

Regards,

Andre

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.

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.