Author

Topic: Setting correct GPU-threads causes error in vertminer (Read 6048 times)

sr. member
Activity: 364
Merit: 250
I tried 8193 on a whim, and same thing.  I really appreciate all of your help, but I think you're perhaps barking up the wrong tree.  My thoughts are that this may be an adaptive n-scrypt specific issue, or perhaps a bug in vertminer.
My answer was directly towards the error -5 that you're getting, which in cgminer (vertminer is obviously a child of cgminer) is mostly due to misconfiguration of the TC value.

Try lowering intensity alongside your TC value see what happens.

Nevermind, just read your latest post, I see you did that.
newbie
Activity: 39
Merit: 0
On another whim, I dropped my TC and intensity way down, and I can get it start with 2 GPU-threads, but as soon as I pass 4000 TC, it gives the same error.
newbie
Activity: 39
Merit: 0
First thing first, add the following to the start of your batch file:
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_USE_SYNC_OBJECTS 1

Those would be for windows, I use linux; and I already have the same commands albeit correct for linux in all of my startup scripts.

Quote from: Starscream
Now, you need to understand that the number of threads you should be using is dictated by your card (not all cards can run well with 1 thread same as not all cards can run well with 2 threads) so find out which is best for your card (by finding out I mean try it out for yourself).

These rigs are rigs that I have countless hours of tweaking on normal scrypt and have determined that 2 GPU threads is by far the best.  I gain about 30% going from 1 to 2.

Quote from: Starscream

Next, the number of TC (thread-concurrency) in your settings is capped by how many threads you're using and by how much RAM you got in your system (to determine how much TC you need to set: Shaders*n+1 (this formula will give you, generally speaking, the best resaults), n can and will be any number you choose but is subject to the limits of your cards/settings, although YMMV).

Again, countless hours of tweaking on these rigs and I have identified my optimal TC, but this is adaptive n-scrypt mining so the normal rules don't necessarily apply.

Quote from: Starscream
So, for your OP, if with 1 thread you see low KH/s than you should change your TC.

If with 2 threads you still get error -5 (after adding the setx commands) than you should lower your TC. A common TC value that works well with -g 2 is 8193.

I tried 8193 on a whim, and same thing.  I really appreciate all of your help, but I think you're perhaps barking up the wrong tree.  My thoughts are that this may be an adaptive n-scrypt specific issue, or perhaps a bug in vertminer.
sr. member
Activity: 364
Merit: 250
6 gb... Is that not enough?

Edit: Just checked. When it's up and running it's used 0.7gb, with the rest free... So, presumably it's not a RAM shortage?

First thing first, add the following to the start of your batch file:
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_USE_SYNC_OBJECTS 1

Now, you need to understand that the number of threads you should be using is dictated by your card (not all cards can run well with 1 thread same as not all cards can run well with 2 threads) so find out which is best for your card (by finding out I mean try it out for yourself).
Next, the number of TC (thread-concurrency) in your settings is capped by how many threads you're using and by how much RAM you got in your system (to determine how much TC you need to set: Shaders*n+1 (this formula will give you, generally speaking, the best resaults), n can and will be any number you choose but is subject to the limits of your cards/settings, although YMMV).

So, for your OP, if with 1 thread you see low KH/s than you should change your TC.

If with 2 threads you still get error -5 (after adding the setx commands) than you should lower your TC. A common TC value that works well with -g 2 is 8193.

Also note that with 2 threads and lower TC you might also need to lower your intensity, although with your card I'm not sure of it, but keep that in mind.
newbie
Activity: 39
Merit: 0
6 gb... Is that not enough?

Edit: Just checked. When it's up and running it's used 0.7gb, with the rest free... So, presumably it's not a RAM shortage?
newbie
Activity: 37
Merit: 0
How much RAM do you have?  I got a similar error when trying to run with 4GB.  Upping to 16GB fixed it (8 would probably work just as well).

I had to tweak settings way down to get it to run with 4GB, and I got maybe 60% the hash rate I am now.
newbie
Activity: 39
Merit: 0
I've tried vertminer with my HD6970 (gigabyte).  If I set gpu-threads at 1, it works at about 60% of it's anticipated hashrate (yes, n-scrypt halving taken into account) based on what the the card does under windows using the precompiled windows binary.  When I set it to gpu-threads : 2, I get

Error -5: Enqueueing kernel onto command queue. (clEnqueueNDRangeKernel)
GPU 0 failure, disabling!


Any thoughts?
Jump to: