Bitcoin Forum

This is a modified version of cgminer that supports mining Yacoins. This release includes my latest OpenCL scrypt-chacha kernel (v7) and a fix for share difficulty calculation. No more spam about blocks being found all the time.

Original version by hanzac
https://bitcointalk.org/index.php?topic=232241.0

Changes:
 - Faster OpenCL kernel
 - Fixed share difficulty calculation
 - Rebased off of cgminer 3.3.1

Changes in -yac2:
 - Fixed network errors caused by too many sockets when pool supports long polling

Usage:
Good sample settings for a 7790 (with N = 2048):

Parameters work similarly as in normal scrypt mining except that more memory is needed depending on the N parameter currently used by the network. Try to find a maximal value for thread concurrency. Set worksize (-w) to 256 for HD 7000 series and 64 for older cards. Experiment with different values for lookup gap if you have your card has lots of cores. Increase intensity until you start seeing HW errors.

More settings have also been posted in the old thread.

Downloads

Windows x64 version
https://mega.co.nz/#!B10C3TZT!M6ZLMwG-QHKSJxVPMnWHb2A171la6qFpsOuNfSrhGyI
http://download.muuttuja.org/yacoin/yacminer/3.3.1-yac2/yacminer-3.3.1-yac2-windows-x64.zip

Windows x86 version
https://mega.co.nz/#!twsQwbaB!X8zL0wqsfGeO-ujuFZx62D6PmHY4D9HT82-qJ0McYME
http://download.muuttuja.org/yacoin/yacminer/3.3.1-yac2/yacminer-3.3.1-yac2-windows-x86.zip

Source code (.tar.xz)
https://mega.co.nz/#!Ip9CVICS!UJ7dRj9qdV2aAVtcEWFgj06YIlEWHgOMg0g0F1R2IWM
http://download.muuttuja.org/yacoin/yacminer/3.3.1-yac2/yacminer-3.3.1-yac2.tar.xz

Source code (.tar.bz2)
https://mega.co.nz/#!p8VhxLRS!V-xBLn_IJgMh1RlZZWYppRrjhbh6ax1Wbzlljnba6Nw
http://download.muuttuja.org/yacoin/yacminer/3.3.1-yac2/yacminer-3.3.1-yac2.tar.bz2

Linux compilation

You da man!

Thank you, trying it out now.

Thank you, any chance of getting a version that supports ybcoin too?
https://bitcointalk.org/index.php?topic=243046.0
https://github.com/ybcoin/ybcoin

I have no interest in Ybcoin since it's simply a clone of Yacoin for the Chinese market. Looks like the only thing one would have to change is the calculation of the Nfactor. No doubt someone has already figured that out and is happily mining at 10 Mh/s. Someone else can release a miner for Ybcoin if they want.

Links for x86 and x64 versions from mega are the same?

Thanks for working on this!

Oops, fixed. Thanks for pointing it out!

+1

Thank You.

Hm-m, this one is even faster than previous?!? Great work, thank's for sharing!

Thanks Mike. That block spam is hella annoying.

This is amazing, getting 84 kH/s with my good old 5770, these are my settings (not sure if best):
yacminer.exe --scrypt -w 64 -I 18  --lookup-gap 2 --thread-concurrency 5120 -g 1 -o http://yacpool.tk:8838 -u Y9JG2HQNMEc3N8nfPdJzT51xwKoQSzZSBJ -p x

"No more spam about blocks being found all the time."

very nice  ;D

With this settings i have a 123kh/s on 7790.
Amazing !   :o

Hi Mike, I am new to the code. Is the script.c or script-chacha.cl I need to modify?
Thanks,

I have only 111 kh/s with my 7850

Hey mikaelh, are you looking into the ways around keeping GPU's usable after the Aug N++?  Or is that something hanzac might be doing?  Or neither? :)

Well, let's re-iterate this once more. GPU mining is not going to magically stop at N = 8192. My miner should survive it just fine. I'm not going to benchmark it because people always keep finding new settings after N changes. Some people will use a higher lookup gap and others will find ways to use lower values. I might come up with some new tricks but at the moment I'm pretty happy how the code scales with the lookup gap.

My apologies, I thought I understood the way it works but obviously not.  I thought that the RAM on the GPU was the limitation and this couldn't be overcome.  I'm not sure I understand the lookup gap / TC correlation and the use of GPU RAM vs system RAM.

It's pretty hard to discuss the details of lookup gap without explaining the entire scrypt algorithm first. I did write a bit about lookup gap on the other forum:
http://yacointalk.com/index.php/topic,350.msg1511.html#msg1511

The miner allocates the scratchpad from GPU memory. You may need enough system RAM to support that, but that's a driver issue.

New version is up. -yac2 fixes a problem which has annoyed me greatly. I noticed that the miner always starts experiencing lots of network failures when mining on a pool for a while. I investigated the issue and I think the cause is that the miner does not close long polling connections. -yac2 fixes that by telling the cURL library to limit the number of long polling connections. It's not a perfect fix because the miner is still keeping more than one connection open but at least it shouldn't stall anymore.

Thank you for the update.

Sorry about nagging, but I am still interested in a Ybcoin version of the Yacminer.
Would a small YAC donation and promise of 5% of all mined Ybcoins spark your interest?

Tried and failed at updating the source myself, yes, that is how dumb I am.

Benchmarks of my AMD 7970 3GB running at 900MHz core, 1000MHz mem and 0.975V in Afterburner, with yacminer-3.3.1-yac2-windows-x64 in Win 7 64bit on http://yac2.ltcoin.net

150Kh/s --scrypt --thread-concurrency 8192 -I 13 -g 2 -w 256 --lookup-gap 4    (uses 0,8GB RAM)  
236.5Kh/s --scrypt --thread-concurrency 8192 -I 13 -g 2 -w 256 --lookup-gap 2  (uses 1,4GB RAM)  
103Kh/s --scrypt --thread-concurrency 8192 -I 13 -g 2 -w 256 --lookup-gap 1     (uses 2,4GB RAM)  

Benchmarks of my 7970 running at 900MHz core, 1500MHz mem and 0.975V in Afterburner, with yacminer-3.3.1-yac2-windows-x64 on http://yac2.ltcoin.net

151Kh/s --scrypt --thread-concurrency 8192 -I 13 -g 2 -w 256 --lookup-gap 4
237.7Kh/s --scrypt --thread-concurrency 8192 -I 13 -g 2 -w 256 --lookup-gap 2    
181Kh/s --scrypt --thread-concurrency 8192 -I 13 -g 2 -w 256 --lookup-gap 1 (140 for the card running Windows)


Higher thread concurrencies (900/1000/0.975):
229Kh/s --scrypt --thread-concurrency 38000 -I 13 -g 1 -w 256 --lookup-gap 2    (uses 2,6GB RAM)
233Kh/s --scrypt --thread-concurrency 38000 -I 15 -g 1 -w 256 --lookup-gap 2    (uses 2,6GB RAM)
233Kh/s --scrypt --thread-concurrency 38000 -I 17 -g 1 -w 256 --lookup-gap 2    (uses 2,6GB RAM)
Trying -g 2 crashes, increasing lookup gap kills he performance.

EDIT: At 1100/1500MHz I get: 287Khps, temp are getting to high though.

Fine, I might make one since there's popular demand. Easy enough to change 4 lines...

Can you use all of the same commands as cgminer?

Yup. It's based on cgminer with minimal changes to support Yacoin.

Ok great, I'll try to find some good settings for 7950s

Well, the Ybcminer has arrived:
https://bitcointalk.org/index.php?topic=249360.0

Please keep further discussion of Ybcminer or Ybcoin in the new thread.

thanks for the update had the network problem today

also found this minor cosmetic thing where i have extra blank lines above and below the bottom ----- line
https://i.imgur.com/XG0Jhfe.jpg

also not sure if i should be using more than the memory buffer of the card

for anyone wanting some nvidia settings, heres what im using for my 560ti

--scrypt --worksize 128 --lookup-gap 1 -I 11 --thread-concurrency 5376

Averaging 245 kh/s with 7950s

Used thread concurrency of 21712, gpu-powertune of 20, core speed of 1100 and mem speed of 1500

had this (v2) and the previous version crash the video driver on exit a few times now

Great work Mikaelh ! you made us all some money.. Some donations shoud come your way ;)

With the new n update, it seems I can't get my 7950s back in the 200 range.  Any ideas?

This is normal, every N incerase hashrate halves for everybody.
The problem now are the HW errors, getting lots of them with the same settings as with Nfactor=10, still trying new settings without any luck.

There isn't going to be another release of the miner any time soon. The best tuning options have already been implemented. Keep thread concurrency as high as possible and after that increase the lookup gap to allow higher intensities.

You may want to check how many HW errors exactly you're getting. If you're lucky like me, you could be getting only 3% HW errors. I'm still mining with the same settings on my 7790:

You can quite easily calculate the total number of difficulty-1 shares your GPU is producing with the following formula:

For example, if you've been mining for an hour at 59.3 kh/s, the number of difficulty-1 shares would be:

Now you can go and compare that number with the amount of HW errors you got.

Hi Mikael. Firstly, thanks for your releases. Could you make a prediction about the long term viability of GPU mining? Yacoin was originally designed to be a currency that could be mined with CPU efficiently. Is that a busted flush now? Or will continued increments in N lead to a situation where CPU miners compete with, or even outmine GPU for equivalent energy input? I'm sure it's difficult to say for certain, but your guess is likely to be more educated than others.

Just noticed that all my 7950 and 7970 don't have any errors at I=17 although 5870/5970 get them as soon as I set intensity at 12 or higher. I used various combinations of thread-concurrency, lookup-gap and threads but nothing works past I=11 for 5x70 cards for me (on several versions of Xubuntu Linux).
So this HW errors problem might be specific to <7xxx cards.

Don't think that's true.  I had HW errors on my 7950 until I upped the threadcount.  Now happily running at 123.2 kh/s

Before N increased I used the maximum threadcount my systems supported with lookup-gap = 2 (unless it was faster with a higher threadcount and lookup-gap = 3). I didn't change my configurations after N increased (other than trying to find parameters without HW errors on my 5x70, but results weren't good and I reverted to my previous configurations).

I use threadcount = 41216 on my 7950 and 7970 with lookup-gap = 2, 8000 or 12000 on my 5x70 (lookup-gap = 3 with threadcount = 12000).

I suppose results vary wildly with OS/drivers.

i tryed mining for a while (about 18 hours) didnt found any blocks with about 283kh/s per card. am i doing something wrong?

settings i use with solomining and Yacminer 3.3.1 x64

yacminer --scrypt -o 127.0.0.1:8112 -u yacoin -p x -I 12 -w 256 --thread-concurrency 8192 -g 2

If your HW error count isn't going up, your miner should be doing just fine. It's just a matter of the difficulty being high and being unlucky in general.

I have discovered a new sweet spot for thread concurrency. After setting it to 6912 (which is 14 * 512 - 256), I'm getting 61 kh/s on a 7790 (instead of 59.3 kh/s with a TC of 8000). My full settings are:

For other models in the HD 7000 series, I suggest the following formula for thread concurrrency with high intensities:

x should be the number of compute units if possible. That's 14 for my HD 7790. For the HD 7000 series, the number of compute units should be the number of shaders divided by 64. You can also try other values.

Note that these values will need to be adjusted when N changes because thread concurrency is automatically adjusted by the kernel. Right now it's being divided by 4, so setting TC to 6912 means that the real TC is 1728.

Sun 07 Jul 2013 21:54:40

http://yacexplorer.tk/graphs.htm (http://yacexplorer.tk/graphs.htm)

Well, my current theory is that N = 8192 will still be doable with lookup gap = 2 on my HD 7790. After that I will probably need to increase lookup gap when N hits 16384 near the end of September.

My HD 7790 has 896 cores and 1 GB of memory. I can allocate about 768 MB of that (which corresponds to thread concurrency = 12000 with lookup gap = 2). 896 is the absolute minimum value of TC needed to sustain 896 cores at N = 1024. The effective thread concurrency is divided by 2 for each Nfactor increase after N = 1024. At N = 8192, the lower bound of TC is 8 * 896 = 7168. My GPU still has enough memory for that but not after the next increase of N.

The exact technical details are fairly complicated so I'm not going to try to explain them here. I'm not even sure about all the details myself. Please note using the optimal value for TC is the key to being able to use high intensities with lookup gap = 2.

I will try to do some benchmarks and post some numbers to support my theory. That's going to take a while though.

If someone wants to help test the above formula, I calculated the suggested TC values for the HD 7000 series:

Use lookup gap = 2 and grab the thread concurrency from the table. Try increasing intensity as high as possible. You can ignore a few HW errors but if you start getting a lot of them, then it's not working.

It doesn't work for me with 7950 and 7970, with your formula I get more hashrate in yacminer but lots of HW errors (several times the accepted shares) and less than half of the effective hashrate I can get with optimal settings as reported by my p2pool node.

I have to use 16x the number of shaders to avoid HW errors on 79x0 and get the best result. I can use higher numbers but it doesn't improve the effective hashrate.

As I mine on p2pool I had to reduce my intensity to 16 from 17 to cope with longer processing times. I noticed that gpu-memdiff=60 is the sweet spot too now (-150 was optimal with previous N).

yacminer.exe --scrypt -w 64 -I 10 --thread-concurrency 5120
Using that for my 5770, get 23-24Kh/s. Can't go higher than I 10, thread concurrency seems to be at the sweet spot, got 20kH around TC 8000 and 4000. Switching to YBC for now

Alright, thanks for testing. I don't have a 7970, so I'm just guessing here.

Just to double check, can you tell me the difficulty on the p2pool? The HW error numbers are a bit difficult to interpret because they are difficulty-1 shares. You need to multiply your accepted shares with the difficulty reported by the miner before you can compare it with HW errors.

The HD 5770 has 10 compute units. You can try adding/subtracting values like 64, 128, 256 to/from 5120. I'm not sure how exactly it works for HD 5000 series.

On 5x70 the situation is noticeably different on my hardware, I need to have more than 20000 shaders to avoid hardware errors and low effective hashrate (20000 with lookup-gap 5 seems optimal with some but relatively few hardware errors). The hashrate is ~30% of what it was before.

Looking for this I noticed in my yacoin p2pool logs lots of:

I'm not sure of the formula for Target -> diff for scrypt-jane, but that's an interesting yacminer/p2pool diff mismatch. Doesn't affect my effective hashrate though.

Using the suggested TC by the table above with a 7950 does not work.

I get the best hashrate for a 7950 with this settings :
I  get 120Kh with the above settings. I was getting 230 before the N change.

Thanks for the extra info and explanation. Based on some rough back of the envelope calculations, assuming a GPU with 4GB vs. a Quad Core CPU, assuming the CPU cores are 10x as efficient as the GPU cores at hashing (correct me if that sounds barmy) . . . we're looking at about an NFactor of 19 (August 2017) before CPUs draw even with GPUs. At this point, about 95% of the GPU cores could be idling for lack of memory, and most of the memory on the PC could still be unused. Does that sound about right?

That's interesting. The numbers are missing leading zeros, but it does look like a target miss. If I add the leading zeros, I get:


I'm not sure if that's a bug in Yacminer or P2pool. Yacminer is working fine with pushpools and yacoind.

Yacminer (cgminer) uses the target 0x0000ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff as difficulty 1. It then calculates difficulty as diff1_target / target. That gives a nice integer number. Your P2pool's difficulty should be 16.

Yacoind uses the target 00000000ffff0000000000000000000000000000000000000000000000000000 as difficulty 1. It then uses a tricky algorithm that corresponds roughly to target / diff1_target. That produces a floating point number. Your P2pool's difficulty should be about 0.00024413 that way.

In either case, the difficulty is pretty low. If the number of HW errors is exceeding accepted shares with that difficulty, then it's definitely not good.

GPUs being 10x as efficient sounds a bit dubious but I don't have the numbers right now to check that. I'm not sure how you did your math either. Did you calculate when the efficiency of GPUs would meet with CPUs? Also you seem to be assuming that GPUs scale linearly when cores go idle which may not be the case. I actually did try idle cores but I don't remember the numbers unfortunately.

I'm wondering if the p2pool fork ( https://github.com/Rav3nPL/p2pool-yac.git ) was based on a recent enough p2pool: there was a bug with scrypt where p2pool didn't handle the difficulty correctly and sent a lower one to the miners. This kind of logs was exactly what we had with Litecoin.

HW errors can be limited, but 5x70 cards perform poorly : 7950 and 7970 are OK and I only had to tune memory and intensity for my particular setup to get hashrate/2 compared to the previous N value (as expected) but for 5870 and 5970 this is more like hashrate/3.

Yes, just using some rough numbers and simple assumptions as best I am able with my limited knowledge. Also assuming the hardware stays relatively the same.

Interesting that you say that some idle cores on the GPU would allow others to run faster . . .  less heat to dissipate I'm guessing . . . and I guess the GPU could cycle through its cores, so as one got hotter, it could switch to a cooler one.

Well, it's almost linear. I actually did a quick benchmark of it.


I would assume that power consumption would go down as well but I cannot measure that now. It is very unlikely that it would scale linearly though.

Here's an alternative table how the miner scales with lookup gap:


Power consumption is likely to remain the same but I haven't measured it.

As you can see, there are at least 2 options for scaling. One option reduces both the hashrate and the power consumption. The other option provides higher hashrates at the cost of high power consumption. These options can also be combined. And this is exactly why I don't back of the envelope calculations of when CPUs are going to break even with GPUs.

I've updated my settings on my 7850 with 1GB of RAM to the following :

yacminer --scrypt --worksize 256 --lookup-gap 3 -I 15 --thread-concurrency 18200 --gpu-engine 1100 --gpu-memclock 1250

this produces 61.15 KH/sec - higher intensities push it up slightly, but the WU/s go down.  I get no hardware errors with this configuration.  With a LUG of 2 best I could get was 76 KH/sec with a significant number of hardware errors. 

I've been tuning my thread-concurrency on each card by setting it to an outrageous number, and running cgminer.  It will then tell me what I'm trying to allocate memory wise (TRY), and what it could allocate(MAX).  I then use those two numbers to lower the TC down to (MAX/TRY) * TC and then subtract 256. 

My 5870 still gets about 51KH/sec using the same settings as N=10, just with a lower intensity.  Again, with no hardware errors.

In the code, what does the hardware error actually occur from?  is it running out of memory, hashes not adding up, or something else?

I did a brief test on my 7870, 7870xt and 7950.. The formula failed on all those.

I have tried differed TCs a bit, and currently I get 78 kH/s with 4096 TC on 7870xt, and 72 kH/s with 4096 TX on 7870. Both are clocked at 1150/1000 (GPU/Mem). These are the highest / best performing settings. Intensity is 11 on both. With higher intensity I get better hash rate, but there are more HW errors.

On my 7950 I now get 67 kH/s, I haven't been able to get better performance out of it. TC is at 7936, intensity 11.

BTW. I think it would be useful to add a percentage of HW errors of all processed blocks. That way one could see the effective hash rate when taking HW errors into account.

It comes from two (or more) threads using the same bit of memory. If the buffer allocated on the GPU is not enough for the active threads, then the threads will start wrapping around in the buffer. The threads will start overwriting each others intermediary values stored in the memory which screws up the hash calculation for those threads. The wrongly calculated hashes pop up as HW errors when they meet the minimum share difficulty and are double-checked by the miner.

Yup, I've been considering adding HW error percentage.

I'm so used to reddit - I really wanted to upvote this post.  Thanks for the answer!

would you mind posting your settings for your 5870?  i am unable to get mine to accept a single share there all HW errors

my both pools are using stratum so GPU miners are welcome:

http://yac.coinmine.pl
http://yacp.coinmine.pl

feeleep

yacminer --scrypt --worksize 64 --lookup-gap 2 -I 11 --thread-concurrency 8192

This is my active desktop machine with three monitors connected and set to give decent responsiveness.  If I up the intensity to 18 (as I same mumus was doing in another thread) I get well over 80 KH/s, but the machine is completely unusable for anything else, and gave more hardware errors than accepted shares.

Hi,

can anyone post the optimal settings for a 7950 please?
With --worksize 256 --lookup-gap 2 -I 15 --thread-concurrency 21712 i got 110 Kh/s

settings for a 560ti at N=11 10kh

--scrypt --worksize 128 --lookup-gap 2 -I 11 --thread-concurrency 8448

i5 2500 is doing just under 6kh

It depends on your card so you have to have a play, though you're not far off the mark.  I can only get 123 kh/s out of mine.

115 Kh/s is about the best that I can get out of mine too (with those settings). I'm using 1000MHz core and memory clocks. Higher memory clock doesn't seem to help much for me and I'm a bit reluctant to push the core clock higher with my current cooling.

rise YAC rise !

I really feel like I'm behind the curve on this.  I'm running 4 cards at only 75khps each. I just got another card and it's only running at 60. 

I tried --worksize 256 --lookup-gap 2 -I 15 --thread-concurrency 21712
but I only get HW errors.

Anyway, I'm willing to pay 200 YAC if you get my single card above 100, and 500 YAC if you get my 4 about 100.

If you're using 7950s I'd be happy to send you my cgminer config file. Just let me know.

Yep 7950s.
1 Asus, 4 Gigabytes (the old awesome f43s)

OK, pm'ed with a config file that works for me. I'd have thought that you should get well in excess of 500 with those five GPUs. Let me know if it works out.

what settings are you using for 7950?

"intensity" : "15",
"vectors" : "1",
"shaders" : "1792",
"worksize" : "256",
"lookup-gap" : "2",
"thread-concurrency" : "31712",
"gpu-threads" : "1",

Core clock and mem clock at 1000MHz. I think you can get more out of them with higher core clock frequency, but that's more than I'm happy overclocking (I'm a softie and want to keep them reasonably cool). Mem clock doesn't make a huge difference for me and clocking down should make a little difference to my electricity bill!

The vectors parameter is not used in scrypt, so you can safely let it out of your config.

Anyone having success getting this to work well with the new N change?  If so, please post your config and speeds.

Thanks

I try mining YAC with 7950 but i have only Rejected (target missed)  why ??? ???

i use cgminer

the same with me

anyone have working settings for 5850 and 5870?

Here's what I use for a meager 34.5k per 7950:

yacminer --scrypt -w 256 -I 12 --lookup-gap 2 -o http://yacp.coinmine.pl:8088 -u myusername -p mypassword --thread-concurrency 41216

friggin N change...

So, correct me if i'm wrong here, but i thought the whole point of YAC was that at the current difficulty the GPUs should only be getting 0 H/s.

If the GPU miners are still doing better than the CPU miners, doesn't this completely invalidate the purpose of YAC?

I'm using virtually identical settings for the same hash rate.  I was able to run at I 20 before the change giving me 124k each, so this means I'm now running at just over 25% that I was at N11.  Even once the diff drops again, this will mean that I'll me mining half that I was before.  If I've done my maths correctly that will mean it will be more profitable to mine scrypt alts instead.  I'll leave it a few days to be sure, but I'm pretty sure that even though the GPU still works, it's not worth mining YAC with it anymore as its more profitable to mine something else.  IF you really want YAC, GPU mine another alt and trade for it.

What clocks/voltages?

Windmaster and mikaelh both said they see no reason why the GPU miner should not continue to work.

So YAC is just FUD and lies then. fuck this coin.

You are confusing the test code that was written for Reaper but never released or even had much time spent on it to try to resolve it.  That is what did not work at N=12.  CGMiner with mikaelh's OpenCL implementation that was released months ago was always going to work with whatever N is.  Some people who don't listen kept trying to perpetuate the MYTH that GPU miners would stop working.

please find another coin - reading is fundamental to knowledge.  Those who don't are happy to walk out the door oblivious and misinformed.

1000/1500 and -10 on afterburner...

Yeah, earnings dropped half so I had to quit mining for now... sucks

What have i misread? The only thing that made Yac decent was the idea that after N = 9, GPU miners would be out of the picture.  But the truth is it has been getting owned from the start and continues to get owned by GPU miners. 

I have done my reading.  Perhaps you have not.  Or perhaps you have a GPU farm and don't give a shit about the idea of a CPU only coin.

How many more cpu only coins do you need? There are a half dozen of them at minimum... better that botnets rape them than those people who have GPUs right?

No, you don't. There is info in this thread about the fact that yacminer would also work for Nfactor > 12.
Your knowledge of this coin has some wrong assumptions.

Ok, i won't waste too much more of my time on your foolishness. But take a look at the original thread about YaCoin:
https://bitcointalk.org/index.php?topic=196196.0

This coin was marketed from the start as a GPU proof, CPU only coin. 

The fact that that is now invalidated, makes this coin just another scam coin like the rest.  And yes, i have read this thread, and it fully supports my argument.

You can read on the original thread :


I hate many things about YAC, but there is no such thing as GPU-proof. GPU are just general purpose ASICS. There is no coin that is GPU proof, there are just coins for which a GPU miner has not been created yet.

I'm using 7950 WF3s and they won't allow me to crank the TC past 24k, they just crash if I put them any higher. How are you guys managing to do that?

What are your settings/command string?

Intensity 12, thread concurrency 41216 and lookup-gap 2.
With these settings I get 35kh with a 7950 at core/memory clock 1040.

I have ~47\50Khs on HD7970.

yacminer.exe --scrypt -w 128 --lookup-gap 2 -I 13 --thread-concurrency 8192 -g 1 -o yac.coinmine.pl:9088 -u xxxxx.2 -p password

get 38 kh/s per 7950 gpu with yacminer-3.3.1-yac2-windows-x86  


but still 10:1 hw to accepted Ratio, dont know how to fix that

Did you try lower intensity? I have to run my 5770 on I 10.

My bat-file for HD7970

ybcminer --scrypt -w 256 --thread-concurrency 40960 --expiry 10 --Nfmin 4 --Nfmax 30 --StartT 1367991200 --gpu-threads 2 --lookup-gap 4 -I 12 --gpu-fan 90 --gpu-engine 11000 --gpu-memclock 1500 -o http://yac.ltcoin.net:5555 -u ***** -p *****
 pause

And i have 48-50 Khs.

 --Nfmin 4 --Nfmax 30 --StartT 1367991200

what is this for ?

YAC doubled itş value on cryptsy !!  :o

Anyone have suggested settings for Radeon HD 7750, 2gb ram? Stock settings

Not sure what's wrong, I've tried all sorts of settings on my old 5850 rig with WinXP (x86).

When connecting to any pool, the yacminer window shows I'm getting roughly 10KH/s, but the pool never shows any hash rate and i never get a single stale or accepted share, even though yacminer runs, says it is connected, and shows a hash rate.

I have no clue what I'm doing wrong.

Post the command you are using so we can take a look.

Ok, not sure how helpful it will be, as I've tried a variety of settings... the good configs resulting in an apparent good connection to the pool, showing a hash rate ranging from 1.5 kh/s with intensity 9, and around 10 kh/s at intensity 15.  But as I said, the pool site never shows me having connected, always leaves me at 0 shares, and says my hash rate is 0.


Here's my latest attempt without extra settings beyond the basics, so I could see what might be causing the problem:


I've tried specifying thread concurrency, lookup gap, etc., leaving them out, etc., in all sorts of combos.

Could I be running the wrong version of OpenCL perhaps?

I believe I have installed Catalyst 11.12, not sure which version of the OpenCL SDK that comes with, or which one I need...

You are using http and connecting to the stratum port.  Change your port to 8088 or change your protocol to stratum

Ok, tried turning on stratum, same result... so I turned on verbose output, and i get the following:

invalid nonce: HW error
over and over, after each line reporting hash rate, etc...

so I'm thinking I must have the wrong AMD driver and/or opencl version installed.

Anyone know what version I should be running on WinXP SP3 (32 bit) to make this work?

Thanks!

Edit: Not sure why this isn't working. Catalyst 11.12 with AMD APP SDK 2.6 works fine for me with cgminer and gui-miner scrypt... Maybe my PC just doesn't like the scrypt-jane algo. required for yac, lol.... This is very frustrating, as I'd like to use my GPU for YAC specifically.

Any suggestions?

With the verbose output you show, you should be seeing a lot of hw errors, it's quoted as "HW: xx" on the top right of your screen.
You just have to tune the thread concurrency value until you don't get HW errors or you get as few as possible.

limit you intensity to 2 for example and if it works try to increase it by 1 and recheck...

someone had success to run that scrypt-jane yacminer with 7870 ?

Just crazy, I have only 3Kh/s and always HW :(

Maximum without HW I can get only 1Kh/s

Used --Nfmin 4 --Nfmax 30 --StartT 1367991200 -s 1 --scrypt -w 256 --shaders 1024 --lookup-gap 1 -d 0 -I 10

and  --shaders 1280 -w 256 -I 9 --thread-concurrency 5120 -g 1

nothing helps:(

this one --shaders 1280 -w 256 -I 16 --thread-concurrency 5120 -g 1
giving ~15Khs, but only HW, nothing accepted.

Please suggest settings, maybe someone had success with 7870 cards?
I running it on Win7-64.

Thanks!

make (intensity) I 7 but only 500 H/s,

With my Sapphire 7850 OC 2GB I get about 1.22 kh/s with these settings:


Any increase in intensity causes pc to be slow and/or gives HW errors.

Finally got mine going. Though I'm not sure whether it's worth it at this point.

Thanks for the suggestions, guys. They definitely helped!

same problem, as you reported

what did you do?

thanks

I'm not sure this works rite.

I've got a 7870 that i'm trying to run this on and its getting around 4khs but never finds an accept.



I now the pool is setup right because i;ve got cuda cards that are finding shares and a cpus.

Lower your intensity until you stop getting HW errors

Although not Yacminer related, but i cant seem to get my YaCoin Wallet to sync at all, tried on two different machines and with no firewalls.

It still wont connect to anything.


Is the yacoin.conf i put in the roaming data folder.

Check the other thread for some valid peers, please keep the thread on-topic

Hey!
I dont know why, but that dont work with my GPU..
I have AMD 6780 and i can normaly mine in scrypt and sha256 too.. but these yacminer dont work for me.
When i mine with cgminer all my shares is rejected, and when i mine with yacminer i have lot of HW errors and no one accepted.
I have soon tested many options, and changed soon the new scrypt-chacha.cl file what 20853 byte is is.. but nothing is better.
I have tested both 64 bit and 32 bit version of the application.
What i use:
yacminer --scrypt -o http://yac.ltcoin.net:5555 -u ifa88 -p x

Any ideas?

your settings are likely too harsh - intensity should be around 8, and you need to specify thread-concurrency based on the amount of memory your graphics card has.  Tuning for YACoin is a fidely process, but this is what I have for my 5870, hopefully you can find decent settings from here.

Just thought I would post this here - I've done a little tweaking to YACMiner and have compiled Windows x86 binaries.  This update changes the display a bit so that it counts accepted/rejected shares*difficulty and the Utility(U) score is based on this submitted share size as well to make comparing different configurations easier especially if you're on a vardiff pool.  I also added a Found Blocks (FB) field into the display - it increments when you find a share larger than the block size, and as far as I can tell it will still increment even if the share is not accepted due to hardware error (still looking into whether this can be avoided).

source code is here https://github.com/Thirtybird/YACMiner (https://github.com/Thirtybird/YACMiner)

Binaries are
https://github.com/Thirtybird/YACMiner/releases/tag/3.3.2-yac2 (https://github.com/Thirtybird/YACMiner/releases/tag/3.3.2-yac2)
https://mega.co.nz/#!yoRVBCjR!P-cAHlRAHrb3vvhVJZf9yipD_ZdbasOevqOCogrY_U8 (https://mega.co.nz/#!yoRVBCjR!P-cAHlRAHrb3vvhVJZf9yipD_ZdbasOevqOCogrY_U8)

Thanks for the new version!
Could you maybe update the cgminer backend to a slightly newer version?
I simply don't get any visible output if I don't use -T. My cmd window is simply black. I once had that with an old cgminer too, a newer version fixed that (if I remember correctly).
Using Windows 8.1 x64 on this machine with a Radeon 5870m and 13.12 drivers.

Do me a favor, and try the --no-adl switch without the -T.  I had this on a laptop, and I recently saw someone made a fix for that, and I'm curious if that's the same problem you're encountering.

It's unlikely I'll update to a newer version of cgminer, because the majority of the changes that have been made have been to support ASIC's and ASIC drivers. 

http://users.atw.hu/ifa/yac.jpg
This is the resoult and this is bad.. :(

Any idea?

tuning for scrypt-chacha is a process.  You keep trying settings until they get better.  I'm surprised to see a HW error at I=8 though.  I would wager you haven't allocated enough memory.  Up the thread-concurrency until you've allocated as much memory as you can - Use GPU-Z to see how much is allocated.  Yacminer will tell you if you've tried to allocate too much.  When playing with a new card, I will set the thread concurreny way too high for the card and let it tell me what the max is.  I start from that number and work my way down until the card starts hashing.

Other things to try once you get that sorted out : G 2, worksize 128 and 256, overclocking. 

http://users.atw.hu/ifa/masodik.jpg
http://users.atw.hu/ifa/harmadik.jpg
First sucess:D
This is the option:
When i try the 9 intensity, i get only hw errors.
When i use normal script then i have 200-250khash speed with intensity 20 without HW error.

Your card is a 1GB card based on the 1 picture, but only 486 MB is being allocated.  I would double your thread-concurrency and see where the memory usage is.  The more memory allocated, the faster it can be pushed and not overwrite memory cells that are in use by ongoing calculations, which is what causes the HW errors.

Thanks, --no-adl works! :)

Implemented the ADL fix as requested, fixed the issue with found blocks being incremented even with an invalid nonce, and a couple other little things

source : https://github.com/Thirtybird/YACMiner (https://github.com/Thirtybird/YACMiner)

Binaries :

https://github.com/Thirtybird/YACMiner/releases/tag/3.3.3-yac2 (https://github.com/Thirtybird/YACMiner/releases/tag/3.3.3-yac2)
https://mega.co.nz/#!WtJG3I6I!f20qWxn90M1au9lap_cWsgMMQftOvcGNN2hYF5zz8S4 (https://mega.co.nz/#!WtJG3I6I!f20qWxn90M1au9lap_cWsgMMQftOvcGNN2hYF5zz8S4)

trying to mine with Sapphire Radeon 7950 but the yacminer doesn't show any accepted/rejected and it also shows HW with increasing numbers.
Somebody has good config for the miner to use with 7950?

Try these settings :

There seems to be a problem with yacminer, I also get hardware errors. I tried to lower the intensity as low as 10, but still get hardware errors. And the speed is 1.6 kh/s which is not really useful for anything.

Using an R9 290

Any users here with solutions?

Thirtybird and other developers, could it be there is something in the miner that lets it work with only some cards? or the SDK needs updating?

Guy

The highest intensity I have been able to go has been 9 - and that still generates some HW errors.   Low hash rates are to be expected, you just need to figure out which settings are best for your card.  If you buy me an R9 290, I'll send you the best configuration for it :D

Is anyone out there who are  succesfully mine YACOIN with cgminer ???
Is it possible to mine it with GPU or only with CPU ?

i cant get cpuminer nor cgminer to work.
Always get error message "no reply by empty server"
or
if hashes, then all package rejected, 0 accepted.


Help or advice (proper settings) needed !!!

Thank You in advance for ur replies...

Ok had a better look, it seems like the memory speed is forced to 150Mhz (can get  up to 1500Mhz).
I can go as high as intensity 10 without errors.


Thirtybird, wish I had the money to buy you a card, but so far can only afford sending you pull requests :)

I know cards throttle down gpu and memory clocks when idle, but it should absolutely go up when running YACMiner.  Try adding a "--gpu-memclock ####" to your command line.
The other option that will probably serve you well is "-g 2" or, maybe even "-g 3" (I've never owned a card that went to three threads, but I run low end gear).

Use GPU-z to verify the amount of memory being allocated on your card when it's running, and increase your thread-concurrency if you're not allocating almost all of the memory on your card.  YACMiner 3.3.4 will actually have an option to set the memory per thread to a specific amount instead of adjusting thread-concurrency.

Post your command line, I might offer another suggestion :)

Ok interesting,
first I forced the gpu-engine and gpu-memclock to the standard on my card, and they seem to be holding.

Now what was left was playing with the thread-concurrency.

I got two results. First, could either set it to 32765. And then I got around 1.5hk/s. Which is not fun.

Second, I tried pushing it up to 35960, but then something completely different happens! Hashing speed jumps up to around 40, but I ALL submissions are rejected with this error:



Here are my settings (thread concurrency varies according to story above)

The good news is: no HW errors, just rejects now.

Any thoughts why all the rejects?

BTW no need to use GPU-z, linux here, reports are pretty accurate from yacminer

If you push the TC too high, even under the max that can be allocated, it doesn't hash right.  Lower it down until you hit normal activity. Based on your numbers, you have a 4 GB card - 32765 TC works out to allocating 4,095.6 MB of GPU memory, so that'll be your top.  old versions of YACMinger & cgminer did not take # of threads (g parameter) into account when restricting your memory allocation;  (this is actually a change I have in the testing branch for 3.3.4 right now).

Two things I would try

1. w of 256 - I've seen no advantage to using 512
2. OVerclock that GPU engine - I've got my R7's running at 1300 MHz, up from stock clock of 1000 MHz.
3. Try a lookup_gap of 1 (and halve the thread-concurrency to match), see what the hash does.  You're allocating 2 GB per thread, so you may not need to waste CPU cycles to save memory space

alternately to #3
try g = 3 and maybe even 4 and reduce your thread-concurrency to match and try intensities 8, 9 & 10. 

the other thing in 3.3.4 I'm testing is a command line setting for memory allocation instead of it being based on LG and TC, so you don't have to keep doing math when you change one paramter.  It's currently written to allocate that number per thread, but I'm on the fence about whether that would be the max allocated and just allocate that parameter/number of threads in the code.

Regarding whether it's written to only work on some cards - I've gotten YAcminer (even 3.3.1, not compiled by me) to mine on a 5770, 5870, 7850, 7850M and R7 250.  Hash rates have been low on anything with 1GB of RAM, but at 2GB, I'm getting what I consider good results with even low end cards.  Sadly I don't have the budget to buy and try the higher end cards, but from what I have seen, high GPU frequency, and a large amount of memory have been the best performance combination, even on a card with a low number of shaders.  My R7 250 2GB DDR3 is 2.25x as fast at YACoin N=14 than my 7850 1GB DDR5.  That same 7850 has 3x the hashrate of of that R7 250 when mining N=10 coins aka litecoin,ftc, doge, etc. though.  Food for thought.

I have having trouble getting YACminer to a profitable hashrate compared to other coins like DOGECOIN.

I have a Radeon HD 6850 and am getting 0.750 Kh/s at best without much hardware error. I am using the following settings:

yacminer --scrypt --scrypt --worksize 64 --lookup-gap 2 -I 8 --thread-concurrency 8192 --temp-cutoff 95 --temp-overheat 90 --temp-target 75


Any suggestion on how to increase my hashrate would be great. Otherwise mining, Yacoin doesn't seem that profitable to me  :( Thanks!

Information was sent several days ago.  Were you successful?

That's as good as you're gonna get for YAC with that card... it is nearly unmineable at this point

I've updated YACminer again - this is a pretty major update.  I'm actually feeling pretty comfortable in the code now after staring at it for weeks and reviewing Kalroth's updates and sgminer.  There are a few more items on the to-do list, but those have a priority of "eventually".


Announcing YACMiner 3.4.0
Major update - includes new parameters for fine-tuning YACoin mining

--buffer-size
Specify the amount of memory to allocate per thread in MB.  For now, still set
thread-concurrency, but this parameter can allocate slightly more memory.
(you're likely to crash a lot when playing with this!)

--rawintensity
All of this is credited to Kalroth.

This new setting allows for a much finer grained intensity setting and also opens
up for dual cpu threads on devices not previously able to. Note: make sure to use
lower rawintensity values when you increase cpu threads (-g).

The original Intensity setting is currently used to spawn GPU threads as a
simple 2^value setting.
  I:8  =     128 threads
  I:8  =     256 threads
  I:9  =     512 threads
  I:10 =    1024 threads
  I:11 =    2048 threads
  I:12 =    4096 threads
  I:13 =    8192 threads
Notice how the higher settings increase thread count tremendously.

It's now much easier to control thread intensity specifically and it potentially
allows for a uniform way of setting the intensity on your system.

This change has been tested on R7, 5870, 7850 - all with better speeds than using
a regular intensity setting after a little tuning, but your mileage may vary.
If this doesn't work for you, or you do not want to spend time fine-tuning, the
regular intensity setting is still available.

You can also set this value through the ncurses interface by pressing:
G -> A -> select device id -> enter value.

Values need to be in multiples of 8 (at a minimum), and older cards appear to need
a multiple of 64.  Start with 256, 512, or 1024 and adjust in increments of 64 either
up or down.  Adjust this until you no longer receive HW errors in the GUI.

see the SCRYPT-README for full details on settings.

Minor changes include

• Network difficulty line only shows up when it actually changes
  fix for GPU fan going to 85% when saving and using a conf file
  cgminer.conf should now be yacoin.conf (rename your file if you use it!)
  Rewrote README as a .md file and updated SCRYPT-README to be more YACoin
  specific

https://github.com/Thirtybird/YACMiner/releases (https://github.com/Thirtybird/YACMiner/releases)

Hi Thirtybird,

thank you for your hard work.

Could you please release version 3.4.0 windows binaries?
You might update your first posting.

Regards,
Janus

The binary attachment to the release is for Windows.

The first post was not made by me, so I cannot update it.

Sorry, my mistake.

I want to use your miner for ultra coin.

How can I set those options:
--Nfmin 4 --Nfmax 30 --StartT 1388361600
yacminer tells me: unrecognized option

Can´t find anything about it in the readme.

Is the yacminer only for scrypt-jane or can I also use it for scrypt ?

Regards,
Janus

I'm not sure where you were getting those paameters.  YACMiner does not support those options and is used only for mining YACoin.  For scrypt, You might want to try https://github.com/veox/sgminer (https://github.com/veox/sgminer)

Hey Guys,
i have some problems with the gpu miner and my Sapphire R9 290, only mining HW`s.
Someone here as working settings to mine YaCoins with a R9 290 ?

Follow the tuning guide here - https://github.com/Thirtybird/YACMiner/blob/master/SCRYPT-README (https://github.com/Thirtybird/YACMiner/blob/master/SCRYPT-README)
you are using settings that consume too much memory and concurrent threads are overwriting other calculations.

Sharing my settings so others can view, analyze and give criticisms.

Hardware: AMD R9 270X @ 1100 MHz GPU, 1425 MHz Mem, i3-3225 @ 3.3 GHz, 8 GB DDR3 @ 1600 MHz
Software: Windows 8.1 64, Catalyst 13.12, yacminer 3.4.0-yac2-x86

yacminer --scrypt -o stratum+tcp://yac.m-s-t.org:3333 -u x -p x -I 8 --thread-concurrency 8192 --lookup-gap 2 -g 2

Get around 1.2Kh/s.

https://www.dropbox.com/s/3ghyulxvskezd3n/Capture.JPG (https://www.dropbox.com/s/3ghyulxvskezd3n/Capture.JPG)

That screenshot is a great way to help - your GPUz is showing that the memory YACMiner is using is not on the card, but using system RAM, which kills performance.  You will get better performance by reducing the number of threads to 1(change -g 2 to -g 1), and increasing the thread-concurrency to something like 13184 (this number may be too high for a 1 GB card, but you have to play with it).  Get TC as high as you can while still keeping all the memory usage in dedicated memory in GPU-z.  Once you've found that number, change "-I 8" to "-R 512" and slowly start increasing R (through ncurses using G->A) until you get your highest hashrate without getting HW errors.

Thanks for the reply. Think I have a problem with GPU-Z. Dedicated stays at 0 MB, always. Dynamic is the only thing that changes.
I have a 2 GB card.

Yeah, verified with HWiNFO 64. GPU-Z is reporting incorrectly.

Thirtybird. I noticed we're on the same pool. What are you using for --scan-time --expiry?

15 min run. scan-time 20 expiry 30.

https://dl.dropboxusercontent.com/u/9572834/Capture1.JPG

Well, with any card currently available, I think you get better performance with 1 thread, but for your card you will need to allocate 1.6 -1.7 GB to that thread. (double your TC to 28416 and adjust up or down from there).  You're trying to cram a bunch of work into half the available memory - YACoin mining benefits from more memory - give it to it!

Thanks for the tip on HWInfo64 - I will point windows 8 folks to that tool. 

--scan-time and --expiry : I don't set them, so whatever the default is.

Thing is, when I go higher than what's stated. It goes over to dynamic memory (I tried 16384 and it bombs). Think there's more in use than HWinfo states.
I'm on single thread, now. -R 512. I get some HW. But it seems OK.

Reason I ask about --scan-time and --expiry is of this link. http://www.reddit.com/r/dogecoin/comments/1ui3bx/increase_such_hashrate_1_to_5_scrypt_tweaking/ceicnyv (http://www.reddit.com/r/dogecoin/comments/1ui3bx/increase_such_hashrate_1_to_5_scrypt_tweaking/ceicnyv)


I know it's for Dogecoin. Isn't Yacoin 60s block time? Maybe stratum takes care of this for pools?
Learning as I go...

Tried 16384 again. It's working correctly. Going to try higher values. Weird.

If I go pass 19991, it switches from dedicated to dynamic. ~1470 of memory tops.

Thank you for the great work, Thirtybird. My hashrate is improved by 25% or so. :D The raw intensity is a great setting to have and your tip for using GPUz to tune thread concurrency is a good one. I haven't try other more refined changes though.

What I did was just start with some low intensity, use GPUz to check how far my thread concurrency (TC) can go, and then change raw intensity to TC/32 (I use lookup gap 2, g 1). I guess I can fine tune for further improvement, but haven't done that so far.

debido666, I don't know if this is related to your case, but sometimes, after using some bad miner settings, even though Windows seem to be ok or have recovered, I need to reboot for miner to work correctly with good settings.

https://dl.dropboxusercontent.com/u/9572834/Capture.JPG

My computer doesn't like GPU-Z. Because of Windows 8.1? UEFI enabled?

After a 12 hour test, getting 1.6 KH/s. With plenty of accepted shares. A few HW. Going to change it from 632 raw-intensity to 624.

Glad to hear it.  TC / 32 is right about where I am on my settings (just a bit under actually) on my 250's with G=1.  My 240 4GB cards are quite a bit different as I have to run them at G=2.  Their multiplier is ~1/38 - those are really the little cards that can.  320 shaders pumping out ~2.8KH/sec!

That was a good read - it's never something I've tweaked.  The default for scan-time is actually 30 seconds in YACMiner.  It may have been carried over from cgminer, or it may have been added by someone before I got it.

Expiry may offer an improvement, looking at my long-running thread on one machine, I've got 31 stales shares and 7 rejected shares over 65 hours on 4 cards.  That's a very low percentage considering I have over 4,000 accepted shares.  It may sneak in a couple more than the stock configuration, but I doubt it will be anything vastly outside the margin of error in luck-based mining...

And this...https://github.com/veox/sgminer/issues/22 (https://github.com/veox/sgminer/issues/22)

I don't get the new build to work on my 5870m with the latest beta drivers under windows 8.1 x64.
yacminer --scrypt -o stratum+tcp://yac.coinmine.pl:9088 -u pato.4 -p password --thread-concurrency 7168 --lookup-gap 2
with -I 7 runs without many errors, but only around 0.5 kh/s. If I increase -I to 10 or 9 I get nearly 2 kh/s, but only HW counting up.
Memory usage is just 650 MB (my card has 1 GB), but increasing --thread-concurrency to 8192 will crash the driver.
Instead of -I -R 256 runs, -R 512 increasing HW. Anything between 256 and 512 produces an error:
 [2014-02-13 23:10:28] Error -54: Enqueueing kernel onto command queue. (clEnque
ueNDRangeKernel)

Only 128, 256, 512, 1024, .... are valid -R configurations (but > 256 = HW errors :( )

Any ideas?

That's a bummer.  For best results on that card, allocate as much memory as you can.  If you can't allocate more than 512 MB on a 1GB card, you need to do the basics first and once that is sorted out, then tweak YACMiner.  If you can't sort that out, I would resort to stable non-beta drivers.

Pro-Tip: On 5XXX, 6XXX and maybe 7XXX series cards, you have to adjust -R in values of work-size.  You haven't specified it, so I'm guessing it's defaulting to 256 for your card.  Set worksize to 32 and adjust R in increments of 32 until you find the highest value for R that does not produce HW errors.  Oh, and lookup-gap - you'll need 4 or maybe even 8...

Thanks for the help.
The most stable/fast I find is this:
yacminer --scrypt -o stratum+tcp://yac.coinmine.pl:9088 -u pato.4 -p password --thread-concurrency 5050 --lookup-gap 1 -w 32 -R 288

This produces quite exactly 0.9 - 1.0 kh/s.

A higher lookup-gap reduces the speed, more than -R 288 increases the speed, but HW will increase more than accepted.

anyone know the command line to Scrypt R9 280x - GV-R928XOC-3GD?

Any chance you could not spam every thread with your question?  I offered you advice in one of them..

Hey,
So I have bene playing with Yacminer and I can't pass the 1 kh/s without getting HW errors on my Sapphire R9 290.
I was wondering, could I use ultracoin minier to mine yacoins? It uses scrypt-jane and I get on it stable 333 kh/s.

But I get rejects when connection to a pool.

Thirtybird, any thoughts on that?
Is there a difference in the source?

http://www.ultracoin.net/ultracoinminer.html

Guy

The difference is Ultracoin is at NFactor 10, and YACoin is at NFactor 14.  This means that YACoin takes 16 times as much memory to perform one calculation as Ultracoin.  Hashrate in theory should only be 16 time less, but no card out has enough memory to be able to completely utilize ALL the GPU power before it runs out of memory, so GPU hasrates are even lower than that.  

If you can't cross 1 KH/sec with YACoin without getting hardware errors, I suggest you read the recommendations in the SCRYPT-README file included with the YACMiner source and binaries https://github.com/Thirtybird/YACMiner/blob/master/SCRYPT-README (https://github.com/Thirtybird/YACMiner/blob/master/SCRYPT-README).  Configuring a miner (ANY miner) for a high N factor scrypt-chacha coin take practice, patience, and experimentation.  Configuring a miner for Ultracoin, or any scrypt (litecoin, dogecoin et. al) is child's play and you can usually cut and paste someone else's settings for any card and get in the ballpark for results.

I agree whole heartedly with that.

I can't get this to run for nothing without hardware errors. Tried lower intensity to lowest setting, xintensity to lowest setting. Don't know if I need rawintensity set. So dang frustrating. Literally been trying to mine this coin for 2 days now with my R7 250. Running perfect on my 750ti.

Just about ready to give up and move on to another coin.

The _ONLY_ way I recommend configuring YACMiner is using Raw Intensity.  Everything else is likely to be less than optimal.  Read the SCRYPT-README included with the package (the new one from 3.4.2 has some major updates), and check the yac wiki hardware page for some suggestions.  If that's a 2GB card, you can get 2.5 KH/sec out of it (or thereabouts, depends on manufacturer) - if it's a 1 GB card, not so much... YAC needs memory, and 1GB cards don't really cut it too well...

links for the help
https://bitcointalk.org/index.php?topic=475569.0
https://github.com/Thirtybird/YACMiner
http://yacoinwiki.tk/index.php/Mining_Hardware_Comparison

Thanks.

Will read up on the links.

I am trying to understand the readme. Just a lot of info for a noob like myself.

I take it when I use raw intensity that I do not use intensity or xintensity? Will try and figure out from there.

EDIT: Seems a simple reboot of the computer took care of the hardware errors. Maybe from running all the different scrypts on the card interfered with it. Over a day running and not 1 hardware error.

Do you know the reason why yacointalk.com is down? I mean why they have stopped the website?

Hmm, thought yacminer worked with the sj-**** variables to mine other variable n factor scrypt-jane coins (?)

Can't get mine to do UTC (was experimenting a bit with a new card...r9 270 2gb)

It does, so long as you're running 3.4.2.  I mined ThorCoin with it for giggles, and lottery tickets too.

Hmmm, I'll try again later tonight. Thanks.

let me know if you have problems.  BTW - the new version I'm working on fixes the scrypt support and adds N-Scrypt support, so you can actually use one program for pretty much any scrypt derivative coin :)

That would put you on cudaminer levels of awesome, but with failover support, and other goodies (more awesome :p)
I hate having all those crappy cgminer forks made by who knows who in my pc...not a dev, as to examine the source code myself anyway.

I was using 3.4.2 and 3.3.1. Somehow memory got stuck at 500mb even if card was not doing anything. I had to disable card in windows and than enable it again. It is working ok now. maybe something went wrong with my card or maybe the program. Just to let you know.

For R7 240 4GB (from wiki): --worksize 128 -g 2 --lookup-gap 2 -R 640 --thread-concurrency 24576

Isn't 24576 weird number? I use 25600 (20x1280) and it works great.

24576 is just 1536mb per thread with LG 2...I have to run 40696 with LG 3 on my 2gb cards for some reason. If I do the equivalent with LG 2 I get HW. lol :p

Aha, thank you.
I get it now, just  --rawintensity values need to be in multiples of 8 (at a minimum), and older cards appear to need a multiple of 64.

Can anybody recommend me a setting for my AMD 6990 :( m getting low Hashrate abt 1kh/s ..
help appreciated! ???

YACMiner has been updated to 3.5.0 today - see post in main thread

https://bitcointalk.org/index.php?topic=475569.msg5680450#msg5680450 (https://bitcointalk.org/index.php?topic=475569.msg5680450#msg5680450)

hello

i have some problem with yacminig.

my settings:
yacminer --scrypt-chacha -o stratum+tcp://yac.coinmine.pl:9088 --worksize 256 -I 8 --buffer-size 1576 --lookup-gap 2 -g 1 --thread-concurrency 16384 --auto-fan --temp-target 73 --temp-overheat 80 --temp-cutoff 85 --gpu-engine 1150 --gpu-memclock 1500 --gpu-powertune 0 -u xxx -p xxx
and i have 2 r9 270 sapphire toxic driver 2013.12 opsystem win7 x64 sp1 i use yacminer last 3.5.0

my problem two gpu running different speed and i think low speed

gpu 0 140-180 h/s :(
gpu 1 400-440 h/s 

all card not 1 kh/s

i read this forum trying many settings and not working i hope somebody have good idea.

thank you

Your settings are definitely all over the place, and not good.

yacminer --scrypt-chacha -o stratum+tcp://yac.coinmine.pl:9088 --worksize 256 -R 3072 --buffer-size 1576 --lookup-gap 8 --auto-fan --temp-target 73 --temp-overheat 80 --temp-cutoff 85 --gpu-engine 1150 --gpu-memclock 1500 --gpu-powertune 0 -u xxx -p xxx

I replaced -I 8 with -R 3072 to get more threads going on the card.
I replaced --lookup-gap 2 with --lookup-gap 8 to let you use more threads with only 1576 MB of GPU memory
I removed -g 1 as it's redundant
I removed --thread-concurrency 16384 as it's overridden by --buffer-size and --buffer-size is an easier setting to work with.

Post your new hash rate back here - I bet it's much higher!

hello
thank you so much the answer wery helpful my new hashrate (5s):5.307K (avg):5.214Kh/s
only settings i change the buffer size 1576-1570  1576 not workin for me gp0 also slow down and the system memory +2 gb filled 1570 working. this 5.2 right hasrate this card ?
thank you

5.2kh/s with no HW?

Those are 2 or 4gb cards?  :o

hello
toxic 2 gb version

http://www.sapphiretech.com/presentation/product/?cid=1&gid=3&sgid=1227&pid=2038&psn=&lid=1&leg=0 (http://www.sapphiretech.com/presentation/product/?cid=1&gid=3&sgid=1227&pid=2038&psn=&lid=1&leg=0)
bye

and yes no hw i start aprox 5 h ago

only reject 3 % aprox.

bye

Yes, that's a pretty good number for that card.  Thanks for letting us know your results!

ivanlabrie - yes, now that we can tune the cards a lot finer, we can get decent hashrates out of them.  At -R 3072 his intensity is halfway between -I 11 and -I 12.

Trying to understand the thought process...

-i 8 = 256 threads?
So i 11 = 2048 and 12 4096?

What I don't understand completely is the way ram allocation works for different algorithms and n factors.
For instance, say we want to configure an R9 270 4GB card to mine vertcoin and the n factor at the moment makes the algorithm use twice as much memory as it does today (like a year had passed).

The card has 1280 shaders, 4gb of ram. Max amount of threads it can run in this scenario should be calculated as follows (88% of the ram is usable in this theoretic scenario): T*(512/LG)=3700987 ->vram expressed in kb

Is that correct?
As for lookup gap, it depends on if the card has enough ram to allocate all threads in the buffer that saturate the shader count. How do I determine that? Trial and error?

I ask because I want to create a tool to auto-tune cards for different algos and n factors based on your logic.
Thanks!

Check your private messages

Gotcha :p

I think the readme has all the info I ask about lol...missed that.

hello
again thanx the help
one question left

the -R how calculate the number 3072 i cant understand
please explain me if possible.
thank you

Please read here : https://github.com/Thirtybird/YACMiner/blob/master/SCRYPT-README (https://github.com/Thirtybird/YACMiner/blob/master/SCRYPT-README) - Starting around line 93

Hi, i came from https://bitcointalk.org/index.php?topic=413978.11120 where you suggested to use yacminer
I bit adapted suggested settings for 270 cards written above, but getting rejects and 80 khash while mining Ultracoin

Thank you, trying it out now.

you need settings for scrypt-chacha in your config file.  do a "yacminer --help" or check out the scrypt-readme file for information on how to set the nfmin, nfmax, and starttime (per pool!) - I recommend setting them from the command line and saving your config file and working from there.

Ok now i set as required
Pool reports share is above target

Also tried tu run config in command line and it gives 2.5khs

I got up to 2.6kh/s with an R9 270 at 1120mhz core and 1480mhz memory.

Mining UTC I got it to do 92kh/s with the following config: yacminer.exe -o stratum+tcp://ultra.nitro.org:3337 -u ivanlabrie.1 -p x --scrypt-chacha --nfmin 4 --nfmax 30 --starttime 1388361600 --no-submit-stale --expiry 10 --scan-time 1 -d 3 --remove-disabled --queue 0 --gpu-engine 0-1100,0-1100,0-1100,0-1100 --gpu-memclock 1000,1000,1000,1200 --gpu-fan 70-100 --temp-target 85 --temp-cutoff 100 --temp-overheat 90 --auto-gpu --auto-fan --rawintensity 5120 --buffer-size 1400 -g 1 -w 256 --lookup-gap 2

your config file has misspelled "scrypt-chacha".

2.5 KH/sec - dunno what card that is, but that's in the neighborhood for YACoin.  If you're mining  a different coin (as your pool name suggests), you need to specify an nfmin, nfmax, and starttime on the commandline too.

Sorry,
I'm Mining UTC(Ultracoin) http://ultra.nitro.org, cards are R9 270 Gigabyte

Their suggested settings for 270, but it is for ultracoinminer
HD7870XT/270X ~75-85Kh/s


Fixed typo, and below produce 20 khs http://simplest-image-hosting.net/png-0-222scrot

For ultacoin, even with only 2 GB, you're still shader limited at N=11.  Your intensity is too low.  -R 3072 is roughly -I 11.5 (note: you can't use 11.5!)  Try using xintensity instead and set it to 32 or 128 or something. 

Your settings are great for N=12 though, so keep them handy for early april :)

With same settings, but instead "rawintensity" : "3072" i put "xintensity" . Tried "32" and then "128" no deference - 32 khash.  Hard to figure out what should be set to get at least 80khs

Does it say you're connected to a pool with NFactor 11 or NF=12 in the connection line?

Guys, with new N-factor, what parameters may i try to tweak for R9 270 (Ultracoin) ? Below my old setting generated 90-93 kh/s, and now they produce 46 kh/s with HW.

When using yacminer one of my cards seem to be lagging behind. Works fine with cgminer. Does anyone know a good fix for this?

http://static.dyp.im/gEx9aE3v8k/a931475e3d09957af5d9fccfc63b20dc.jpg

changed "lookup-gap" to 4, other settings remained same - 31kh/s and no HW. http://simplest-image-hosting.net/png-0-yacst

You've probably over-allocated memory and it's swapped into dynamic memory, which is slow... run hwinfo or gpuz and look at each cards' memory allocation

Sometimes a fresh boot fixes that. Sometimes you need to allocate less memory (buffer-size) or reduce -R

I lowered the buffer size and the intensity and it started to work again! Thanks all  :D

Hi have problem compiling my miner and the error as follows:




checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking target system type... x86_64-unknown-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for style of include used by make... GNU
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking dependency style of gcc... gcc3
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking minix/config.h usability... no
checking minix/config.h presence... no
checking for minix/config.h... no
checking whether it is safe to define __EXTENSIONS__... yes
checking build system type... (cached) x86_64-unknown-linux-gnu
checking host system type... (cached) x86_64-unknown-linux-gnu
checking whether to enable maintainer-specific portions of Makefiles... no
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ISO C89... (cached) none needed
checking dependency style of gcc... (cached) gcc3
checking for ranlib... ranlib
checking whether gcc needs -traditional... no
checking whether gcc and cc understand -c and -o together... yes
checking for ranlib... (cached) ranlib
checking sys/mman.h usability... yes
checking sys/mman.h presence... yes
checking for sys/mman.h... yes
checking wchar.h usability... yes
checking wchar.h presence... yes
checking for wchar.h... yes
checking for stdint.h... (cached) yes
checking for mprotect... yes
checking for sigaction... yes
checking for sigaltstack... yes
checking for siginterrupt... yes
checking for mmap... yes
checking for MAP_ANONYMOUS... yes
checking whether memchr works... yes
checking whether memmem is declared... yes
checking for memmem... yes
checking whether memmem works... yes
checking for C/C++ restrict keyword... __restrict
checking for uid_t in sys/types.h... yes
checking for inline... inline
checking whether the preprocessor supports include_next... yes
checking whether system header files limit the line length... no
checking for wchar_t... yes
checking for unsigned long long int... yes
checking for long long int... yes
checking whether stdint.h conforms to C99... yes
checking whether memmem is declared without a macro... yes
checking whether mempcpy is declared without a macro... yes
checking whether memrchr is declared without a macro... yes
checking whether rawmemchr is declared without a macro... yes
checking whether stpcpy is declared without a macro... yes
checking whether stpncpy is declared without a macro... yes
checking whether strchrnul is declared without a macro... yes
checking whether strdup is declared without a macro... yes
checking whether strncat is declared without a macro... yes
checking whether strndup is declared without a macro... yes
checking whether strnlen is declared without a macro... yes
checking whether strpbrk is declared without a macro... yes
checking whether strsep is declared without a macro... yes
checking whether strcasestr is declared without a macro... yes
checking whether strtok_r is declared without a macro... yes
checking whether strerror_r is declared without a macro... yes
checking whether strsignal is declared without a macro... yes
checking whether strverscmp is declared without a macro... yes
checking whether memmem works in linear time... yes
checking for memmem... (cached) yes
checking whether memmem works... (cached) yes
checking for struct sigaction.sa_sigaction... yes
checking for volatile sig_atomic_t... yes
checking for sighandler_t... yes
checking whether sigaction is declared without a macro... yes
checking whether sigaddset is declared without a macro... yes
checking whether sigdelset is declared without a macro... yes
checking whether sigemptyset is declared without a macro... yes
checking whether sigfillset is declared without a macro... yes
checking whether sigismember is declared without a macro... yes
checking whether sigpending is declared without a macro... yes
checking whether sigprocmask is declared without a macro... yes
checking for sigprocmask... yes
checking whether NULL can be used in arbitrary expressions... yes
checking for ANSI C header files... (cached) yes
checking syslog.h usability... yes
checking syslog.h presence... yes
checking for syslog.h... yes
checking for working alloca.h... yes
checking for alloca... yes
checking for OpenCL... no
checking for pthread_create in -lpthread... yes
checking for json_loads in -ljansson... no
checking for library containing addstr... no
configure: WARNING: Could not find curses library - if you want a TUI, install libncurses-dev or pdcurses-dev
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for LIBCURL... no
checking for LIBCURL... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating compat/Makefile
config.status: creating compat/jansson/Makefile
config.status: creating ccan/Makefile
config.status: creating lib/Makefile
config.status: creating config.h
config.status: executing depfiles commands



------------------------------------------------------------------------
yacminer 3.3.1-yac2
------------------------------------------------------------------------


Configuration Options Summary:

  curses.TUI...........: NOT FOUND. TUI support DISABLED
  OpenCL...............: NOT FOUND. GPU mining support DISABLED
configure: error: No mining configured in




Could anyone tell me how can i solve this problem? I have done all the setting including install lissl-dev, automaker and many more. Hope someone will help me solve this problem and i will be very tankful to your.

Well, YACMiner 3.3.1 was authored by someone else, and is REALLY depreciated.  Get the new version from the links in my signature and those include build instructions with the full list of dependancies

I get 11,95 kH/s on my 4xR9 280x

In my opinion this is somehow a little?

Or is this normal?

SET GPU_MAX_ALLOC_PERCENT=100
yacminer.exe --scrypt-chacha -o stratum+tcp://yac.coinmine.pl:9088 -u barbados-2 -p 1 --worksize 256 --lookup-gap 4 -g 1 -R 2048 --thread-concurrency 48640 --buffer-size 2656 --auto-fan --temp-cutoff 90 --temp-overheat 85 --gpu-fan 85-95 2>logfile.txt

It's a bit low...try my settings:

yacminer --scrypt-chacha -R 4424 -g 1 --buffer-size 2560 --lookup-gap 7 --worksize 256 --gpu-engine 1020 --gpu-memclock 1500 --temp-cutoff 95 --gpu-fan 0-100 --auto-gpu --temp-target 85 --temp-overheat 95 -o stratum+tcp://yac.coinmine.pl:9088 -u ivanlabrie.1 -p x

Thanks, I got 18,25 kH/s

What is a good figure for cards 280x?

3.6kh/s per card in my case.

Hi i am back again i am using the github from Thirtybird. But still have error as below:



checking minix/config.h usability... no
checking minix/config.h presence... no
checking for minix/config.h... no
checking whether it is safe to define __EXTENSIONS__... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ISO C89... (cached) none needed
checking dependency style of gcc... (cached) gcc3
checking for ranlib... ranlib
checking whether gcc needs -traditional... no
checking whether gcc and cc understand -c and -o together... yes
checking for ranlib... (cached) ranlib
checking sys/mman.h usability... yes
checking sys/mman.h presence... yes
checking for sys/mman.h... yes
checking wchar.h usability... yes
checking wchar.h presence... yes
checking for wchar.h... yes
checking for stdint.h... (cached) yes
checking for mprotect... yes
checking for sigaction... yes
checking for sigaltstack... yes
checking for siginterrupt... yes
checking for mmap... yes
checking for MAP_ANONYMOUS... yes
checking whether memchr works... yes
checking whether memmem is declared... yes
checking for memmem... yes
checking whether memmem works... yes
checking for C/C++ restrict keyword... __restrict
checking for uid_t in sys/types.h... yes
checking for inline... inline
checking whether the preprocessor supports include_next... yes
checking whether system header files limit the line length... no
checking for wchar_t... yes
checking for unsigned long long int... yes
checking for long long int... yes
checking whether stdint.h conforms to C99... yes
checking whether memmem is declared without a macro... yes
checking whether mempcpy is declared without a macro... yes
checking whether memrchr is declared without a macro... yes
checking whether rawmemchr is declared without a macro... yes
checking whether stpcpy is declared without a macro... yes
checking whether stpncpy is declared without a macro... yes
checking whether strchrnul is declared without a macro... yes
checking whether strdup is declared without a macro... yes
checking whether strncat is declared without a macro... yes
checking whether strndup is declared without a macro... yes
checking whether strnlen is declared without a macro... yes
checking whether strpbrk is declared without a macro... yes
checking whether strsep is declared without a macro... yes
checking whether strcasestr is declared without a macro... yes
checking whether strtok_r is declared without a macro... yes
checking whether strerror_r is declared without a macro... yes
checking whether strsignal is declared without a macro... yes
checking whether strverscmp is declared without a macro... yes
checking whether memmem works in linear time... yes
checking for memmem... (cached) yes
checking whether memmem works... (cached) yes
checking for struct sigaction.sa_sigaction... yes
checking for volatile sig_atomic_t... yes
checking for sighandler_t... yes
checking whether sigaction is declared without a macro... yes
checking whether sigaddset is declared without a macro... yes
checking whether sigdelset is declared without a macro... yes
checking whether sigemptyset is declared without a macro... yes
checking whether sigfillset is declared without a macro... yes
checking whether sigismember is declared without a macro... yes
checking whether sigpending is declared without a macro... yes
checking whether sigprocmask is declared without a macro... yes
checking for sigprocmask... yes
checking whether NULL can be used in arbitrary expressions... yes
checking for ANSI C header files... (cached) yes
checking syslog.h usability... yes
checking syslog.h presence... yes
checking for syslog.h... yes
checking for size_t... yes
checking for working alloca.h... yes
checking for alloca... yes
checking for OpenCL... no
checking for pthread_create in -lpthread... yes
checking for json_loads in -ljansson... no
checking for library containing addstr... -lncurses
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for LIBCURL... no
checking for LIBCURL... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating compat/Makefile
config.status: creating compat/jansson/Makefile
config.status: creating ccan/Makefile
config.status: creating lib/Makefile
config.status: creating config.h
config.status: config.h is unchanged
config.status: executing depfiles commands



------------------------------------------------------------------------
yacminer 3.5.0-yac2
------------------------------------------------------------------------


Configuration Options Summary:

  curses.TUI...........: FOUND: -lncurses
  OpenCL...............: NOT FOUND. GPU mining support DISABLED
configure: error: No mining configured in




I am using g2.2xlarge instance in AWS and previously i have installed cuda toolkit and all the necessarily stuff for it to work. But still this problem surface it. Could anyone tell me what should i do next to solve the error above? If this error solved then what to do next to if there is another error? And thanks to Thirtybird for help to reply my post but this time i really need your help to get this miner works. I will be very thankful to you if you could help me.

So....

to understand...

you're trying to compile the GPU miner to run on Amazon virtual servers?

Yes, and may in the further i will use it other graphic card that will be run in Linux operating system. For now i will run it in AWS first.

You should contact Amazon then and tell them you can't access the OpenCL GPU on their virtual servers.

OR

Understand that those servers don't offer OpenCL mining.  You're probably looking for the CPU miner (poke around my github, it's there too)

Hi finally it able to work as it show below:


------------------------------------------------------------------------
yacminer 3.5.0-yac2
------------------------------------------------------------------------


Configuration Options Summary:

  curses.TUI...........: FOUND: -lncurses
  OpenCL...............: FOUND. GPU mining support enabled
  scrypt...............: Enabled
  ADL..................: SDK NOT found, GPU monitoring support DISABLED

  Avalon.ASICs.........: Disabled
  BFL.ASICs............: Disabled
  BitForce.FPGAs.......: Disabled
  Icarus.FPGAs.........: Disabled
  ModMiner.FPGAs.......: Disabled
  Ztex.FPGAs...........: Disabled

Compilation............: make (or gmake)
  CPPFLAGS.............:
  CFLAGS...............: -g -O2
  LDFLAGS..............:  -lpthread
  LDADD................:  -lcurl   compat/jansson/libjansson.a -lpthread -lOpenCL    -lm

Installation...........: make install (as root if needed, with 'su' or 'sudo')
  prefix...............: /usr/local




But something is wrong which i tried to make it and it does not appeal "yacminer" file. All the files show below:



01-cgminer.rules           ccan              driver-avalon.c    libztex.c          scrypt140202.cl
aclocal.m4                 c++defs.h         driver-avalon.h    libztex.h          scrypt.c
adl.c                      ChangeLog         driver-bflsc.c     linux-usb-cgminer  scrypt-chacha.cl
adl_functions.h            code_flow.txt     driver-bitforce.c  logging.c          scrypt-chacha.cl.14
adl.h                      compat            driver-icarus.c    logging.h          scrypt.h
ADL_SDK                    compat.h          driver-modminer.c  ltmain.sh          scrypt-jane.c
api.c                      compile           driver-opencl.c    m4                 scrypt-jane.h
API.class                  config.guess      driver-opencl.h    Makefile           SCRYPT-README
api-example.c              config.h          driver-ztex.c      Makefile.am        sha2.c
api-example.php            config.h.in       elist.h            Makefile.in        sha2.h
API.java                   config.h.in~      example.conf       miner.h            stamp-h1
API-README                 config.log        findnonce.c        miner.php          usbutils.c
arg-nonnull.h              config.status     findnonce.h        missing            usbutils.h
ASIC-README                config.sub        FPGA-README        NEWS               uthash.h
AUTHORS                    configure         fpgautils.c        ocl.c              util.c
autogen.sh                 configure.ac      fpgautils.h        ocl.h              util.h
autom4te.cache             COPYING           GPU-README         phatk121016.cl     warn-on-use.h
bench_block.h              depcomp           hexdump.c          poclbm130302.cl    windows-build.txt
bitforce-firmware-flash.c  diablo130302.cl   install-sh         README.md          yacminer.c
bitstreams                 diakgcn121016.cl  lib                scrypt130511.cl    yacoin-schedule.txt



But when i use the yacminer 3.3.1 it appealed anybody knows why? And i will be very thankful to you. Another thing i use the yacminer 3.3.1 to mine and i found it very strange with the hash rate show below:




   yacminer version 3.3.1-yac2 - Started: [2014-04-30 13:30:24]
--------------------------------------------------------------------------------
 (5s):80.63M (avg):80.73Mh/s | A:0  R:0  HW:5  U:0.0/m  WU:1.8/m
 ST: 2  SS: 0  NB: 5  LW: 30  GF: 0  RF: 0
 Connected to yac.coinmine.pl diff 1 with stratum as user meodows92.meodows92
 Block: ea4cbc304a599bc8...  Diff:1  Started: [13:32:50]  Best share: 12
--------------------------------------------------------------------------------
 [P]ool management [G]PU management ettings [D]isplay options [Q]uit
 GPU 0:                | 80.90M/81.72Mh/s | A:0 R:0 HW:5 U:0.00/m I: 4
--------------------------------------------------------------------------------

 [2014-04-30 13:30:23] Started yacminer 3.3.1-yac2
 [2014-04-30 13:30:23] Probing for an alive pool
 [2014-04-30 13:30:25] Disabling extra threads due to dynamic mode.
 [2014-04-30 13:30:25] Tune dynamic intensity with --gpu-dyninterval
 [2014-04-30 13:30:25] Network diff set to 1
 [2014-04-30 13:30:26] Network diff set to 1
 [2014-04-30 13:30:26] Stratum from pool 0 detected new block
 [2014-04-30 13:30:26] Thread 1 being disabled
 [2014-04-30 13:31:30] Found block for pool 0!
 [2014-04-30 13:32:27] Found block for pool 0!
 [2014-04-30 13:32:27] Network diff set to 1
 [2014-04-30 13:32:27] Stratum from pool 0 detected new block
 [2014-04-30 13:32:44] Network diff set to 1
 [2014-04-30 13:32:44] Stratum from pool 0 detected new block
 [2014-04-30 13:32:50] Network diff set to 1
 [2014-04-30 13:32:50] Stratum from pool 0 detected new block
 [2014-04-30 13:32:55] Found block for pool 0!


It appeal to be the hash rate in a very large amount is in mega hash, it is true or i have to calculate my formula my own?
Anyways thanks to Thirtybird for your reply previously, although it doesn't help much and i found another way to solve it.

You didn't actually run "make" - there would be a bunch of .o files and a yacminer if you had.



yacminer 3.3.1 is not supported here - I had no hand in that software.  The parameters are different, you looked like you were mining SHA256

hello
 sorry disturb again but i cant solved the problem i working many hours the conf and not working

i try my old card radeon 4870 1 gb version set up yacmining but i cant

here my conf
yacminer --scrypt-chacha -o stratum+tcp://yac.coinmine.pl:9088 --worksize 128 -R 3200 --buffer-size 440 -g 1 --lookup-gap 4 --gpu-engine 750 --gpu-memclock 900 --gpu-powertune 0 -u xx -p xx

and many hardvare error i try lower raw intensity bit yacminer disabling the card only work R 1920 but also many hardware error and i try normal intensity -I 9 also hw errors  but speed 670 hs
the error message:  Error -54: Enqueueing kernel onto command queue.     (clEnqueueNDRangeKernel)
i read the readme but i cant understand how correct settings raw intensity
i use ati 13.9 driver last support this card x64 win
the card use 800 shaders
please help me.

thanx again

I use a R9 290 Saphire card and get only HW errors. Could anyone post a working config for this card please. I have 32GB RAM in my machine

Hello
I use a 7870 Saphire card and get only 1kh/s per card in my case.Is this normal?
here my conf
yacminer.exe --scrypt-chacha -o stratum+tcp://yac.coinmine.pl:9088 -u X -p 1 --worksize 256 --lookup-gap 4 -g 1 -R 800 --buffer-size 1760

I have 8GB RAM in my machine.

That actually sounds about right for the configuration you posted. 

As I understood, I can't get more from this card. Am I right?

You can try increasing the LG and the -R, but with only 2GB on the card, you really aren't going to be able to get too much more out of it.

Wonder how these will fare:

Overclockers UK are one of the leading UK retailers for computer hardware, and one of their managers, Gibbo has posted a few very interesting comments on the OCUK forums.

“980 / 970 4GB reference cards with 8GB coming at a later date with custom coolers,” Gibbo began, confirming earlier rumors hinting that we’ll be seeing 8GB Maxwell models after launch. “Can’t say any more but don’t expect a huge leap in performance over current single GPU stuff.” he added.

Regarding the GPU’s performance, “They replace 780, not 780Ti,” said Gibbo, likely to the disappointment of many. “Performance wise, my lips are sealed on how it compares to 780Ti, but of course 980 is quicker than 780 for sure!”

source:
http://www.redgamingtech.com/nvidias-gtx-980-maxwell-slower-gtx-780-ti-8gb-model-coming-later/

UPDATE

At geizhals.at, an EU based price-watch engine started listing a GeForce GTX 980.

The card would be dual-slot in configuration and has two 6-pin power connectors. Other then that noting is listed.
There is a mistake in the listing though as it states GM104 "Maxwell" which would be GM204.

Chip: GM104 "Maxwell"
Memory: 4 GB GDDR5, 256bit
Shader units / TMU / ROP: 2560/160/64
Fab: 28nm
Shader model 5.0
Interface: PCIe 3.0 x16
Slot: dual-slot
Power: 2x 6-pins PCIe
Anyway, nothing is certain with this information.

nothing is certain with this information.



source:
http://www.guru3d.com/news-story/geforce-gtx-980-starts-listing-in-pricewatch-engines.html

Anyone mining YAC with 280x? What's your settings and how much are you getting out of it?

I built Yacminer against the NVidia implementation of OpenCL just fooling around but I wasn't able to get more than two-thirds of what I could with Cudaminer- but at the same time, I'm not really familiar with tuning yacminer.   Has anyone tried this and achieved results worth mentioning?  It appears that NVidia's implementation of OpenCL limits the memory available to 1/4 of the total.  And also does not support OpenCL 1.2.   Anyone have recommended settings for the GTX 970?  Do I run multiple threads to take advantage of the memory limitations (something like -g 4)?

Gigabyte GTX 970
4GB RAM (1GB accessible by OpenCL)
1644 shading units

Or is this even worth pursuing?

Not likely worth pursuing.  CUDA is supposed to be significantly faster on nvidia cards than straight out openCL.  With that said, you could try to run -g 4 or you could launch 4 separate instances of YACMiner. 

You might want to ask specifics about cudaminer/cuda or nvidia settings in the Cudaminer thread - likely more people with nvidia cards there ;)

That's what I was afraid of.  I tried running 4 separate threads and didn't really improve the results much.  I suppose the only real benefit of NVidia OpenCL would be in the case where there is not a CUDA implementation of the algo, as with Neoscrypt.

I'm good on Cudaminer tweaking and settings.  Translating NVidia settings over to OpenCL is different story.   I was more curious to see how close I could get an NVidia OpenCL implementation of your Yacminer running against Cudaminer.  And also possibly running a NVidia compile of sgminer for algo switching support.  Seems like it'd be more productive to move the API from sgminer to cudaminer.

Your math matches mine 100%, and it should work.  If your drivers are something other than 13.12, that might be part of the problem - I've seen HW errors on configs that should work just fine on 14.X.

config for R9 270X for linux?

bump

I'm only getting 1.4 khs, and I'm told it should be much higher.

What were you told it should be?  NF=16 is tough when you've only got 3GB of memory

When running YAC, on one rig, it just quits on me after 5 minutes - an hour of time. With "pause" in the bat file, it just lists the location of the miner \pause and "press any key to continue".

No heating issues (under 75), the computer remains running, and I'm about to gouge my eyes out here because I can't figure out whats wrong with it. Is there any method or other software that can explain to me why its crashing? Just one of two rigs I'm using does this.

turn off curses (-T i think) and enable debug (-D)

I have ASUS R 9 290 4Gb. This is my bat file
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_USE_SYNC_OBJECTS 1
yacminer --scrypt-chacha --worksize 256 --lookup-gap 2 -g 1 --buffer-size 2656 -R 6411  -o stratum+tcp://wk10.botpool.net:4339 -u bankmyrik.bankmyrik -p x --nfmin 16 --nfmax 30 --starttime 1375817223
Bat i have HW errors. What my problem?

Well, I'm guessing you're mining zccoin, which is NF 16 - I'm guessing you've never mined a scrypt-chacha coin before?

Your buffer size is too low
Your lookup gap is too low
Your raw intensity is too high

read the primer on how to tune your miner for SC mining here : https://github.com/Thirtybird/YACMiner/blob/master/SCRYPT-README

there is also a config generator for ultracoin, which will work for your coin here : http://cfg.ultracoin.net/
it doesn't guarantee it will generate the fastest hashrate for your card, but it will be in the ballpark.

It"s in my first time and i have problem. Nothing goes... Please, help me. I have Asus R 9 290 4Gb, 6 Gb RAM, driver 14.5, Win 7 64 bit.
Please.

If what I provided doesn't help, and you're using YACMiner 3.5.0, then you're beyond the help I'm willing to provide for free (which is pretty far)

I use YACMiner 3.5.0 and  your help to set up, but have permanent HW. If you can, help me, please.

Post the new command line you're using and what you've tried changing

setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_USE_SYNC_OBJECTS 1
yacminer --scrypt-chacha --worksize 256 --lookup-gap 8 -g 1 --buffer-size 2800 -R 4424 --gpu-engine 947 --gpu-memclock 1250 -o stratum+tcp://wk10.botpool.net:4339 -u bankmyrik.bankmyrik -p x --nfmin 4 --nfmax 30 --starttime 1375817223

I change lookup gap , buffer size and R  but still HW.

And what command line did the config generator I recommended to you generate?

something like...

yacminer --scrypt-chacha --worksize 128 -g 1 --lookup-gap 8 --buffer-size 3532 -R 1664

Your R is still WAY too high, that's what causes HW errors

Error -4 Enqueing kernel onto command queue.

buffer size too high for system ram
not enough swap file
could be many things

Anyone still following this thread???

I am having issues with my R7 240 4GB cards... I am getting over 20% stale shares when mining YACoin. Anyone else run into that problem?