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

[hanzac]

It seems that under this weird circumstance, the GPU miner should be released.
Here it is:
Prebuilt binary for windows 64:
http://sourceforge.net/projects/hnindev/files/yaminer-beta-winx64-2.zip
Source code:
http://sourceforge.net/projects/hnindev/files/yaminer-beta-src-2.zip
Win32 binary built by Thirtybird: https://mega.co.nz/#!e1YVDBYZ!YSzn40ba5ciOVUeJjIcQnFxbvr0JhdYwkzqempL_l8Y
CL kernel v7 provided by mikaelh: https://bitcointalk.org/index.php?topic=232241.msg2595928#msg2595928
(Package Status: MINOR UPDATE, correct the program name issue, upgrade to cgminer 3.2.1, If you have working installation, no need to update.)

It's based on the cgminer scrypt mining, but there's some difference, the lookup-gap=2 + thread-concurrency parameters are just used to for allocate the pad buffer. The intensity (I) means the global work size 2^I, it seems to be related to the Nfactor & GPU stream cores & GPU memory size. For the GCN GPUs, set the worksize to 256 and for the pre-GCN GPUs, set the worksize to 64.

Some command lines only for reference:
For 5950
yacminer --device 0 --scrypt --worksize 64 --lookup-gap 2 -I 11 --thread-concurrency 8192 -o <URL> -u <username> -p <password>
Currently can hash 190KH/s (Nfactor=9)

For 6750
yacminer --device 0 --scrypt --worksize 64 --lookup-gap 2 -I 10 --thread-concurrency 2816 -o <URL> -u <username> -p <password>
Currently can hash 47KH/s (Nfactor=9)

For 7950
Some correction
[Under Linux]
yacminer --device 0 --scrypt --worksize 256 --lookup-gap 2 -I 12 --thread-concurrency 32768 -o <URL> -u <username> -p <password>
Currently can hash 230KH/s (Nfactor=9)
[Under Windows]
yacminer --device 0 --scrypt --worksize 256 --lookup-gap 2 -I 11 --thread-concurrency 8192 -o <URL> -u <username> -p <password>
Currently can hash ???KH/s (Nfactor=9)

When running under linux, maybe you need to set these environment variables:

export DISPLAY=:0
export GPU_MAX_ALLOC_PERCENT=100
export GPU_USE_SYNC_OBJECTS=1

[Compilation under linux]
It's quite easy if you've already complied cgminer once (have all the other dependency libraries installed)
Run:

chmod +x ./configure
./configure --enable-scrypt
make install

Then, it will be installed into the application's dir (typical /usr/local/bin).

[Known issue]

• Because using the latest cgminer 3.2.0 code base, the network thread seems has slow reaction to submit hash & get a response at the beginning. After a while, it will become normal.
• AMD Graphics drivers prior to 12.X may not work, so recommend using newer drivers.

[Q&As]
https://bitcointalk.org/index.php?topic=232241.msg2449944#msg2449944
https://bitcointalk.org/index.php?topic=232907.0  (Performance tuning, out-of-dated if you use the kernel supported Look-up gap & TC)

PS, my GPU miner is not quite fast comparing to some others, and it may not work for some other cards.

[BrewCrewFan]

Be nice to see if nvidia could do this. Of course I can not get this to work with my cards to test :/

[barwizi]

linux item downloads but says error with archive

[bitdwarf]

Posting to watch. Good luck anyone beating LTC GPU mining profitability with this.

[forsetifox]

Network hashrate: 73.8Mhash
Difficulty: .73573658

[hanzac]

linux item downloads but says error with archive

Oh, I upload again. There're some cgminer's files are very large. Try later.

[bitcash2013]

It seems that under this weird circumstance, the GPU miner should be released.
Here it is:
Prebuilt binary for windows 64:
http://sourceforge.net/projects/hnindev/files/yaminer-beta-winx64.zip
Source code for compiling under linux or win32
http://sourceforge.net/projects/hnindev/files/yaminer-beta-src.zip, (not fully tested, because under linux I used a older version of cgminer)

It's based on the cgminer scrypt mining, but there's some difference, the lookup-gap=2 + thread-concurrency parameters are just used to for allocate the pad buffer. The intensity (I) means the global work size 2^I, it seems to be related to the Nfactor & GPU stream cores & GPU memory size. For the GCN GPUs, set the worksize to 256 and for the pre-GCN GPUs, set the worksize to 64.

Some typical command lines:
For 5950
cgminer --device 0 --scrypt --worksize 64 --lookup-gap 2 -I 11 --thread-concurrency 8192 -o <URL> -u <username> -p <password>
Currently can hash 190KH/s (Nfactor=9)

For 6750
cgminer --device 0 --scrypt --worksize 64 --lookup-gap 2 -I 10 --thread-concurrency 2816 -o <URL> -u <username> -p <password>
Currently can hash 47KH/s (Nfactor=9)

For 7950
cgminer --device 0 --scrypt --worksize 256 --lookup-gap 2 -I 12 --thread-concurrency 32768 -o <URL> -u <username> -p <password>
Currently can hash 230KH/s (Nfactor=9)

When running under linux, maybe you need to set these environment variables:
export DISPLAY=:0
export GPU_MAX_ALLOC_PERCENT=100
export GPU_USE_SYNC_OBJECTS=1

PS, my GPU miner is not quite fast comparing to some others, and it may not work for some other cards.

YAC is dieing

[mtrlt]

Does it work after N hits 8192?

[hanzac]

Does it work after N hits 8192?

Give a shot, I find it can mine at 4.6 KH/s with 7950.

With intensity 10, it can do about 9.2 KH/s.

[nfuse]

do you maybe have the settings for an 7970 ?

[BlazinBeaches]

What settings for 7970?  I'm having trouble getting it to work, also what's a good p2pool

[Hydroponica]

Does it work after N hits 8192?

Give a shot, I find it can mine at 4.6 KH/s with 7950.

4.6 KH/s with a 7950...And why the fuck would I want to do that? That is far from mining fine, with a 7950..

[hanzac]

What settings for 7970?  I'm having trouble getting it to work, also what's a good p2pool

7970 should be the same with 7950, what's the trouble, does it print HW errors?

[BlazinBeaches]

What settings for 7970?  I'm having trouble getting it to work, also what's a good p2pool

7970 should be the same with 7950, what's the trouble, does it print HW errors?

The hashrates for the cards are at zero and it crashes the display driver

[nfuse]

What settings for 7970?  I'm having trouble getting it to work, also what's a good p2pool

7970 should be the same with 7950, what's the trouble, does it print HW errors?

yes settings of 7950 do not work, my display drivers go mad but with cgminer -- scrypt --worksize 256 --lookup-gap 2 -I 11 --thread-concurrency 8192 i got arround 144 per card and just found my first block.

[hanzac]

What settings for 7970?  I'm having trouble getting it to work, also what's a good p2pool

7970 should be the same with 7950, what's the trouble, does it print HW errors?

All the hashrates for the cards are at zero and it crashes the display driver

This might be the problem of driver. Here I'm using AMD-APP-SDK-v2.8-Windows-64 & Display driver: 13-1_vista_win7_win8_64_dd_ccc_whql

[nfuse]

What settings for 7970?  I'm having trouble getting it to work, also what's a good p2pool

7970 should be the same with 7950, what's the trouble, does it print HW errors?

All the hashrates for the cards are at zero and it crashes the display driver

This might be the problem of driver. Here I'm using AMD-APP-SDK-v2.8-Windows-64 & Display driver: 13-1_vista_win7_win8_64_dd_ccc_whql

nope got the same but windows 8 / 64b everything above I -11 crashes the driver.

[hanzac]

What settings for 7970?  I'm having trouble getting it to work, also what's a good p2pool

7970 should be the same with 7950, what's the trouble, does it print HW errors?

yes settings of 7950 do not work, my display drivers go mad but with cgminer -- scrypt --worksize 256 --lookup-gap 2 -I 11 --thread-concurrency 8192 i got arround 144 per card and just found my first block.

I'm sorry, I run my 7950 under linux. with setting these:
export DISPLAY=:0
export GPU_MAX_ALLOC_PERCENT=100
export GPU_USE_SYNC_OBJECTS=1

I can set thread-concurrency 32768.

I don't know if under windows, you can set GPU_MAX_ALLOC_PERCENT ...

[TheSwede75]

Wait.. There are people actually mining YAK still? That should be the thread topic. Cause it's freaking unbelievable!

[obermensch]

Someone want to compile a 32bit version?