[ANN] Yet another GPU miner release! [YAC]

[bitdwarf]

Works here, getting the expected rate at I 15 with no errors.

[1714813706]

1714813706

[1714813706]

1714813706

[1714813706]

1714813706

[1714813706]

1714813706

[mikaelh]

Trying it now...seems like yac either killed my card or my win 7 install got borked with your v5 kernel somehow (?)
I can't mine other coins either, getting tons of hw atm.
(this is when trying to mine ltc)

You will probably need to restart that computer.

[xavenged]

currently getting 230Kh/s from my 7950 no hardware errors with the following settings..

-I 17 -g 2 -w 256 --lookup-gap 2 --thread-concurrency 19712

time to try this out on the rig

Thanks again mikaelh!!!

[ivanlabrie]

Trying it now...seems like yac either killed my card or my win 7 install got borked with your v5 kernel somehow (?)
I can't mine other coins either, getting tons of hw atm.
(this is when trying to mine ltc)

You will probably need to restart that computer.

I did...but same thing.
Tried the new kernel and it works! Problem is I'm stuck at -i 12 since I can't up TC more than 12224 in my pc. (2gb system memory)

[limitless]

How much until GPU mining becomes useless?

[ivanlabrie]

How much until GPU mining becomes useless?

Doesn't seem really profitable when other coins give more than 0.017btc a day at 248kh/s (you can get 650kh/s with the same card and mine FTC)

I'm still mining it, despite my card doing 150kh/s (can't go over 12224 for TC since I only have 2gb of system memory)

[fenican]

CPU miners also got their hash rates cut in half.  We just need to be patient and wait for the difficulty to drop

[ghostlander]

Here's a new version which should fix HW errors for most people.

scrypt-chacha-v6.cl
https://mega.co.nz/#!NhFFxSzC!I7gIqnxyL7LLR5rP8E60bAjAQQFGueDHv1wygufQm0c

Remember to delete your *.bin files.

If you are still getting HW errors, you need to increase either thread concurrency or lookup gap.

Code:

C:\DOCUME~1\GHO~1.TH~\LOCALS~1\Temp\OCL34E.tmp.cl(135): error: bad argument
          type to opencl vload/vstore: expected pointer to scalar with
          addrSpace global/local/private/constant(vloa [2013-06-26 09:42:44] Failed to init GPU thread 0, disabling device 0
 [2013-06-26 09:42:44] Restarting the GPU from the menu will not fix this.
 [2013-06-26 09:42:44] Try restarting cgminer.

[mikaelh]

Code:

C:\DOCUME~1\GHO~1.TH~\LOCALS~1\Temp\OCL34E.tmp.cl(135): error: bad argument
          type to opencl vload/vstore: expected pointer to scalar with
          addrSpace global/local/private/constant(vloa [2013-06-26 09:42:44] Failed to init GPU thread 0, disabling device 0
 [2013-06-26 09:42:44] Restarting the GPU from the menu will not fix this.
 [2013-06-26 09:42:44] Try restarting cgminer.

What's your driver version? I think your OpenCL compiler may be too old. It's also possible to get rid of vstore but I'm not sure how that would affect performance.

[djkakadu]

7790 users!

Please post here new N=10 settings. I try many setups, always hw error.

MY N9 settings:
hashing avg.: 126.3kh/s
Parameters:

Code:

 --device 0 --scrypt --worksize 256 --lookup-gap 2 -I 11 --thread-concurrency 8192 -o adress -u name -p pass

[6strings]

If one had 360 khash before what should they expect now? Trying to tune my miner probably to maximize my hash rate. Best I can do before getting swamped with HW errors is about 160khash on a 7870LE Tahiti.

[paulthetafy]

It should literally be half the rate with all other settings being the same

[ghostlander]

Code:

C:\DOCUME~1\GHO~1.TH~\LOCALS~1\Temp\OCL34E.tmp.cl(135): error: bad argument
          type to opencl vload/vstore: expected pointer to scalar with
          addrSpace global/local/private/constant(vloa [2013-06-26 09:42:44] Failed to init GPU thread 0, disabling device 0
 [2013-06-26 09:42:44] Restarting the GPU from the menu will not fix this.
 [2013-06-26 09:42:44] Try restarting cgminer.

What's your driver version? I think your OpenCL compiler may be too old. It's also possible to get rid of vstore but I'm not sure how that would affect performance.

That's HD4870 on Windows XP, so the drivers and APP SDK are pretty old. This OpenCL 1.0 HW delivers ~100MH/s SHA-256 at 800MHz engine and maybe 120W power consumption. Not worth mining anymore unless you have free electricity. I think it can be used very well for scrypt-jane mining as it offers over 100GB/s of memory bandwidth.

[mikaelh]

7790 users!

Please post here new N=10 settings. I try many setups, always hw error.

MY N9 settings:
hashing avg.: 126.3kh/s
Parameters:

Code:

 --device 0 --scrypt --worksize 256 --lookup-gap 2 -I 11 --thread-concurrency 8192 -o adress -u name -p pass

My current settings for a 7790 are:

Code:

--scrypt -w 128 --lookup-gap 2 -I 17 --thread-concurrency 12000

This produces about 109 kH/s after the latest N change.

[mikaelh]

Code:

C:\DOCUME~1\GHO~1.TH~\LOCALS~1\Temp\OCL34E.tmp.cl(135): error: bad argument
          type to opencl vload/vstore: expected pointer to scalar with
          addrSpace global/local/private/constant(vloa [2013-06-26 09:42:44] Failed to init GPU thread 0, disabling device 0
 [2013-06-26 09:42:44] Restarting the GPU from the menu will not fix this.
 [2013-06-26 09:42:44] Try restarting cgminer.

What's your driver version? I think your OpenCL compiler may be too old. It's also possible to get rid of vstore but I'm not sure how that would affect performance.

That's HD4870 on Windows XP, so the drivers and APP SDK are pretty old. This OpenCL 1.0 HW delivers ~100MH/s SHA-256 at 800MHz engine and maybe 120W power consumption. Not worth mining anymore unless you have free electricity. I think it can be used very well for scrypt-jane mining as it offers over 100GB/s of memory bandwidth.

Here's a quick version that doesn't use vstore. Only recommended for people who cannot compile v6.

scrypt-chacha-v6-no-vstore
https://mega.co.nz/#!p9l20QLa!YbT2A0i0WqJS1moB6hGGaU4vRgJ7nChIKgs-2o1jB8k

[forsetifox]

Thanks for your continued development with this Mikaelh.

 

[Eli0t]

Thanks for your continued development with this Mikaelh.

 

+1

N=10 settings for 560ti with no HW errors and v6 cl, 24kh
--scrypt --worksize 128 --lookup-gap 1 -I 11 --thread-concurrency 4192

[ivanlabrie]

Thanks for your continued development with this Mikaelh.

 

+1

N=10 settings for 560ti with no HW errors and v6 cl, 24kh
--scrypt --worksize 128 --lookup-gap 1 -I 11 --thread-concurrency 4192

Try higher thread concurrency and lookup-gap and then you'll be able to increase intensity.
You need a cudaminer :p

I'm stuck at 223kh/s with my 7970...not too bad though. My pentium d does 1kh/s

[Eli0t]

Thanks for your continued development with this Mikaelh.

 

+1

N=10 settings for 560ti with no HW errors and v6 cl, 24kh
--scrypt --worksize 128 --lookup-gap 1 -I 11 --thread-concurrency 4192

Try higher thread concurrency and lookup-gap and then you'll be able to increase intensity.
You need a cudaminer :p

I'm stuck at 223kh/s with my 7970...not too bad though. My pentium d does 1kh/s

hehe yeah

was able to get I up to 15 with lookup-gap 2 and tc 8448 (crashed on 16) but the hashrate was still lower than lg 1 i 11

[darksoft]

Thanks for your continued development with this Mikaelh.

 

+1

N=10 settings for 560ti with no HW errors and v6 cl, 24kh
--scrypt --worksize 128 --lookup-gap 1 -I 11 --thread-concurrency 4192

Try higher thread concurrency and lookup-gap and then you'll be able to increase intensity.
You need a cudaminer :p

I'm stuck at 223kh/s with my 7970...not too bad though. My pentium d does 1kh/s

I'm getting that on my 7950's. Shouldn't the 7970 get a bit more? Just curious...