Quote from: xwebnetwork on April 06, 2014, 09:58:09 PM

Quote from: jakiman on April 06, 2014, 08:56:55 PM

Quote from: xwebnetwork on April 06, 2014, 08:26:45 PM

Quote from: batty634 on April 06, 2014, 07:43:30 PM

Thanks to everyone for the yacminer tips. Got it nicely hashing along now on two of my rigs. I had the same issue as others with 4 x 280x, needed to drop the buffer to 1760 and drop R until no hardware errors. Now the rig is running @ 200 kh/s

So you have 4 x 280X's running at 50KHs per with 8GB RAM? May I have your final settings?

Thanks!

Here you go, I was the first to post it which now everyone is using AFAIK. Grin

https://bitcointalk.org/index.php?topic=413978.msg6093996#msg6093996

280x(7970) @ 60Kh/s

55Kh/s at 1025/1500 @ 1.075v
60Kh/s at 1110/1500 @ 1.150v

1. Use latest YACMiner. https://github.com/Thirtybird/YACMiner/releases
2. Use following core settings: (Add other settings, more pools as needed)

Quote

yacminer.exe --scrypt-chacha -o -u -p -R 8000 -g 1 -w 128 --buffer-size 2656 --lookup-gap 3 --temp-cutoff 85 --nfmin 4 --nfmax 30 --starttime 1388361600

Note: This may ONLY work on a PC with 8GB "physical" RAM regardless of VM size. (I tried up to 32GB)
If you have 4GB RAM machine and it fails, try using a lower buffer-size of 1760 and -R of 6144 or 5888.
As the rawintensity is lower, you will end up with a lower hash rate of about 45Kh/s unfortunately.

If this helped: UXLaLvo8L4eV9uC355WRzTX88GA7iFja2g Grin

Some tutorial on YACMiner for everyone

YACMiner allows finer control of the intensity value so you can squeeze every bit of its hash rate which ultracoin-miner cannot.

--buffer-size cannot go over the size of your video card's RAM amount. It's usually around 10% less value.
-R is basically Intensity equivalent in cgminer. YACMiner allows for more granular in-between Intensity values. (e.g. 12 = 4096 & 13 = 8192)

Goal is to try and squeeze in as many threads (intensity) in to the amount of buffer without it going into dynamic memory.
So first try to find the largest max buffer size your system will work with. Go up in increments of 128 until it fails to start.
Depending on system RAM size, you may need to start as low as 50% of your single video card's RAM amount. (e.g. 3GB video card 1536)
Once you know the max buffer size that works, set it as that and leave it alone.

Now just adjust the -R value in increments of 128. Good to start from something low such as 4096 and work your way up.
If you set it too high, you will either get HW errors and much less WU or it'll just fail/lockup/crash etc. Dial it down if so.

Lastly, check your WU over at least 15-20minutes. Clocking higher might givss higher hash rate but WU might not go up.
You might end up using 5-10% more electricity but end up not actually doing any more real work. So keep an eye on WU.

Awesome. Worked like a charm. Slightly modified the clocks to 1000/1250 and still pulling 55KHs per.

Code:

--scrypt-chacha -o -u -p -R 8000 -g 1 -w 128 --buffer-size 2656 --lookup-gap 3 --temp-cutoff 85 --nfmin 4 --nfmax 30 --starttime 1388361600 --gpu-engine 1000 --gpu-memclock 1250 --auto-fan --temp-target 75 --temp-overheat 80 --temp-cutoff 85

Also, YACMiner does work with CGWatcher. Just need to rename the EXE to "Cgminer.exe". Furthermore, on my one Windows 8 Rig, one of the cards doesn't seem to play well with YAC. Works fine with CGMiner. Have rebooted but will keep on tweaking to figure it out. Thank you again!

same with me out of 6 cards 1 cards posted 0.000k/0.000kh/s...

tungz10

Posts

Merits