Pages:
Author

Topic: [ANN] Yet another GPU miner release! [YAC] (Read 53305 times)

hero member
Activity: 693
Merit: 500
March 30, 2014, 10:28:41 AM
Someone want to compile a 32bit version?
There will be a 32 bit version?

Windows 32 bit binaries are what are posted

https://github.com/thirtybird/yacminer/releases/
newbie
Activity: 14
Merit: 0
Someone want to compile a 32bit version?
There will be a 32 bit version?
sr. member
Activity: 274
Merit: 250
Long live yac Grin

The original scrypt-chacha coin.

I now prefer saying the first N-change coin. Wink
newbie
Activity: 28
Merit: 0
Be nice to see, I think it is helpful for me
newbie
Activity: 56
Merit: 0
Any idea Why my radeon 7970 hashing so poor guys? Its not even 100 khash/s, is it normal? (Windows 7, latest amd drivers, yacminer mikaelh's latest compile)

yacminer --scrypt -w 128 --lookup-gap 2 -I 17 --thread-concurrency 8192 -g 1 (I tried few settings, didnt work either)

I use these setting with the V7 CL:

yacminer --scrypt -w 256 --gpu-threads 2 --auto-gpu --expiry 1 --shaders 2048 --lookup-gap 2 --thread-concurrency 8192 --intensity 12 --worksize 256 --gpu-engine 900-1100 --gpu-memclock 1500

Getting about 265 kh/s per GPU
hero member
Activity: 809
Merit: 501
YAC is dead.

it's dead when it's at 1 satoshi.


I feel like "YAC is dead" should be turned into a bunch of memes--making it a reverse psychology kind of joke. It seems some people have the sentiment: yac is dying... yet they will continue to mine it as it is profitable with MULTIPLE cards/setups. I saw a lot of posts along those lines in your cudaminer thread, Christian. It is like "bite the hand that feeds."
hero member
Activity: 756
Merit: 502
YAC is dead.

it's dead when it's at 1 satoshi.
newbie
Activity: 28
Merit: 0
Got my 7970 running again by lowering intensity from 13 to 11 and increasing TC from 8192 (--thread-concurrency 8192) to 10240 (--shaders 2048).
Same worksize 256 and same g 2 and same --lookup-gap 2.
Deleted the bin files before starting yaminer.

Reduced hash rate by over 60%, so there is a lot more tweaking to do...

Pool went from 35Mh to 7Mh, guess all GPU's got killed by the N factor.

EDIT Still getting HW errors, trying lower intensities
hero member
Activity: 812
Merit: 1000
Be nice to see if nvidia could do this. Of course I can not get this to work with my cards to test :/

What cards?

I can mine yac just fine on nvidia but using cudaminer, naturally. Wink
Nvidia cards are quite decent at it. (except for fermi or older)
full member
Activity: 133
Merit: 100
8GB RAM, Win 8.1
hero member
Activity: 693
Merit: 500


Nice - looks like 6 R7 240 4GB cards hashing away! 

hCan you tell us How much system ram does the machine have?  People have asked if 8 GB is enough for 6x4GB cards, and I wasn't sure if it was.
full member
Activity: 120
Merit: 100
Gonna check it out..
hero member
Activity: 812
Merit: 1000
Long live yac Grin

The original scrypt-chacha coin.
full member
Activity: 133
Merit: 100
hero member
Activity: 693
Merit: 500
YAC is dead.

Love your optimism, but I'm not sure how it's relevant to mining software that's capable of mining a dozen scrypt-chacha coins, vertcoin, and 100+ scrypt coins.

Keep contributing your expert opinion though - it's very insightful!
member
Activity: 91
Merit: 10
YAC is dead.
hero member
Activity: 809
Merit: 501
Quote
[2014-03-19 11:12:42] Started yacminer 3.5.0-yac2
 [2014-03-19 11:12:42] Probing for an alive pool
 [2014-03-19 11:12:43] Pool 0 difficulty changed to 2
 [2014-03-19 11:12:49] GPU 0: bufsize for thread @ 1664MB based on buffer-size
 [2014-03-19 11:12:49] Network diff set to 1.42K
 [2014-03-19 11:12:49] Error -4: Enqueueing kernel onto command queue. (clEnqueu
eNDRangeKernel)
 [2014-03-19 11:12:49] GPU 0 failure, disabling!
 [2014-03-19 11:12:49] Thread 0 being disabled
 [2014-03-19 11:13:13] Stratum from pool 0 detected new block

using buffer-size
yacminer --scrypt-chacha --worksize 64 --lookup-gap 8 -g 1 -R 1856 --buffer-size 1664  -o stratum+tcp://yac.m-s-t.org:3333

Using "auto mode" - gives same error and produces
scrypt-chachaCaymanglg4tc50432w64l4.bin

"old settings" work ok

It just looks like you don't have the ability to allocate that much GPU ram - guessing only 2 GB of system memory too? 
Damn! I was pretty sure that my "testbed machine" is with 4GB... but after checking it has only 2Gb atm Cheesy, will try after increasing Smiley

You can just google the card to get the number of shaders. Looks like 2560 for the R9 290? I'd be surprised if your setup works without the amd drivers.

Download the latest AMD Catalyst driver here:
http://support.amd.com/en-us/download

Download the latest AMD APP SDK here:
http://developer.amd.com/tools-and-sdks/heterogeneous-computing/amd-accelerated-parallel-processing-app-sdk/downloads/

Also, you may find these guides to be useful:

http://www.cryptobadger.com/2013/04/build-a-litecoin-mining-rig-linux/
https://litecoin.info/Debian_Linux_cryptocoin_mining_rig_setup_guide


I believe when a card goes "Sick," your --gpu-engine and/or --gpu-memclock is/are too high. I don't think any other setting would cause that to happen.
legendary
Activity: 1151
Merit: 1001
Quote
[2014-03-19 11:12:42] Started yacminer 3.5.0-yac2
 [2014-03-19 11:12:42] Probing for an alive pool
 [2014-03-19 11:12:43] Pool 0 difficulty changed to 2
 [2014-03-19 11:12:49] GPU 0: bufsize for thread @ 1664MB based on buffer-size
 [2014-03-19 11:12:49] Network diff set to 1.42K
 [2014-03-19 11:12:49] Error -4: Enqueueing kernel onto command queue. (clEnqueu
eNDRangeKernel)
 [2014-03-19 11:12:49] GPU 0 failure, disabling!
 [2014-03-19 11:12:49] Thread 0 being disabled
 [2014-03-19 11:13:13] Stratum from pool 0 detected new block

using buffer-size
yacminer --scrypt-chacha --worksize 64 --lookup-gap 8 -g 1 -R 1856 --buffer-size 1664  -o stratum+tcp://yac.m-s-t.org:3333

Using "auto mode" - gives same error and produces
scrypt-chachaCaymanglg4tc50432w64l4.bin

"old settings" work ok

It just looks like you don't have the ability to allocate that much GPU ram - guessing only 2 GB of system memory too? 
Damn! I was pretty sure that my "testbed machine" is with 4GB... but after checking it has only 2Gb atm Cheesy, will try after increasing Smiley
hero member
Activity: 693
Merit: 500
So, if you aren't specifying --worksize, it defaults to 256, and I wouldn't use -R 1856 (try -R 6144,1792 or throw a --worksize 256,64).

I really can't answer questions about linux - you'll have to google it, or, as I said, run it with -T -D and look through the output, it does get output somewhere in there.

So, the AMD supplied linux drivers don't work for mining?  That really surprises me.  I know Ubuntu is Debian based, and a colleague is running numerous machines on debian using YACMiner, and has been quite successful, even while still learning what he was doing.

I'm not using the amd supplied ones (which cause trouble when upgrading, I avoid them as much as I can) but the ones supplied by the standard ubuntu distribution (do not work as well as xedger's).

Well, if you determine the drivers are the root cause, please let me know - you're in an area I really don't have the time to explore.
legendary
Activity: 2716
Merit: 1094
Black Belt Developer
So, if you aren't specifying --worksize, it defaults to 256, and I wouldn't use -R 1856 (try -R 6144,1792 or throw a --worksize 256,64).

I really can't answer questions about linux - you'll have to google it, or, as I said, run it with -T -D and look through the output, it does get output somewhere in there.

So, the AMD supplied linux drivers don't work for mining?  That really surprises me.  I know Ubuntu is Debian based, and a colleague is running numerous machines on debian using YACMiner, and has been quite successful, even while still learning what he was doing.

I'm not using the amd supplied ones (which cause trouble when upgrading, I avoid them as much as I can) but the ones supplied by the standard ubuntu distribution (do not work as well as xedger's).
Pages:
Jump to: