Bitcoin Forum

This is an updated version of cgminer 3.3.1 that supports mining any Scrypt, Adaptive-N-Scrypt, or Scrypt-chacha (aka "scrypt-jane") hashing algorithm.  This release includes the latest OpenCL scrypt-chacha kernel by mikaelh (v7) and a number of improvements from the version of CGMiner it was forked from (3.3.1)

Latest Version: 3.5.0 - Updated 3/13/2014

Source
https://github.com/Thirtybird/YACMiner (https://github.com/Thirtybird/YACMiner)
Windows Binaries
https://github.com/Thirtybird/YACMiner/releases (https://github.com/Thirtybird/YACMiner/releases)

Changes:

• Display updated and fixed to account for vardiff
• ADL code has been updated and some fixes for various cards have been included
• Added fine-tuning parameters for mining high N-factor coins (Raw Intensity, Buffer-size) (starting with 3.4.0)
• Ability to mine other SC coins, and save the settings per-pool (starting with 3.4.2)
• Ability to mine Scrypt and N-Scrypt coins (starting with 3.5.0)

Usage:
sample settings for a R7 250 (384 shaders) 2GB card (with N = 14 / 32,768) being able to allocate 1,648 MB of GPU memory: 2.5 KH/sec with overclocking

Good sample settings for a 7850 (1024 shaders) 1GB card (with N = 14 / 32,768) being able to allocate 760 MB of GPU memory: 1.45 KH/sec with overclocking

At higher NFactors, cards with high shader counts should be set to use a higher lookup gap in order to keep them busy as they may be short on memory.  If you've got a 1GB card, and are mining YACoin, your lookup-gap will likely be 8.  2GB cards will probably be ranging from 4 through 8 depending on how many shaders your card has.

Parameters work similarly as in normal scrypt mining except that much more memory is needed depending on the N parameter currently used by the network. Try to find the highest value for thread concurrency you can achieve before the thread memory gets shifted from dedicated memory to synamic memory (use GPUz or HWInfo to monitor this). Set worksize (-w) to 32, 64, 128 or 256 - the RawIntensity for most cards needs to be a multiple of this value, and you can do a bit more fine tuning with a lower work size.  This may be different for the R7 & R9 cards, however, these may allow their Raw Intensity to be adjusted in multiples of 8 instead of a multiple of work size.

Your starting point for setting the Raw Intensity will be based on the amount of memory the card has.  Increase Raw Intensity until you start seeing HW errors then back it down until you aren't receiving any.  The following table is merely a guideline on where to start.

Future Plans - see https://github.com/Thirtybird/YACMiner/wiki/Plan (https://github.com/Thirtybird/YACMiner/wiki/Plan)

• Ability to save configurations per card per hashing algorithm (to easily allow failover pools that are a different coin/NFActor)
• Easy-mode configuration - specify just the buffer-size and let YACMiner figure out the other settings

Attribution:
Original version by mikaelh
http://yacointalk.com/forum/index.php/topic,350.0.html
Original version by hanzac
https://bitcointalk.org/index.php?topic=232241.0

Do you have any guide to make executables for Linux? I'm very newbie in Linux unfortunately.

Keep up the good work m8. You deserve many donations. People don't yet realize what little bit of wonder you are doing with this piece of software.
I hope many can donate so you'll buy more cards for yourself.

Hi what it means -R  how to write 7970

https://github.com/Thirtybird/YACMiner/blob/master/SCRYPT-README

Hi

I'm trying to configure yacminer batchfile to mine Bitleu and i'm having trouble writing it. I have this:

setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_USE_SYNC_OBJECTS 1

C:\Users\q6600\Desktop\BITLEU\YAC/yacminer.exe --scrypt -o 127.0.0.1:22640 -u user -p pass --intensity 16 --gpu-engine 870 --gpu-memclock 1145 --worksize 256 --thread-concurrency 5824 --failover-only --queue=0 --scan-time=0 --expiry=1 -g 1

pause

I get HW=going up with every new block detected by network.

any tips for me?

thanks

yep, you need --nfmin and --nfmax and --startime on your command line

YACMiner has been updated to 3.5.0 today!

Version 3.5.0-yac2 - 13th March 2014
*** MAJOR CHANGES AHEAD ***
- Application can now mine scrypt, N-Scrypt, and scrypt-chacha based coins
- The command-line options for setting the algorithm have changed!
   --scrypt - Mine scrypt based coins
   --scrypt-chacha (this is the equivilant of what --scrypt used to do!)
   --nscrypt - Mine N-Scrypt based coins (vertcoin)
- Scrypt and N-Scrypt have different kernels.  You can use the N-Scrypt
 kernel for mining Scrypt if you like by passing "--kernel nscrypt" on
 the command line.  The converse does not work though.
- buffer-size is now fully completed, and thread concurrency is no longer
 needed.  thread-concurrency is still a valid option if you want to use it.
- Implemented new defaults if you do not provide a buffer-size or
 thread-concurrency.  It will attempt to allocate 88% of the GPU memory.
- lookup-gap now defaults to 4 if it is not set.
- W/U is back on the hashmeter at the top of the curses display
- Rejected count is now the number of rejected shares instead of the value
 of the sum of all the rejected shares
- Fixed OpenCL 1.2+ patch regarding BFI_INT patch still being done.
- cleanup code and extraneous files in project.
- More updates to the readme.md and scrypt-readme for further documentation.

Amazing news! Seems like the ideal miner for my dedicated mining Os.

Wow, very nice! Thanks, I´m going to try it right now.

Thirtybird, could you give some working running command for 79xx and/or R9 GPUs for both scryptN and scrypt. I´m not being successful to mining VTC with your miner.

Thanks.

You need to say how much memory the card has... post YOUR command line and I'll explain the differences that need to be made.

Fantastic update!

Using this mining microCoin and have been able to increase my system happy hashrate (ie no crashing) on each R9-270 card from 75 to 92 khash/s.  That is a big increase. 

Mrc is at N factor 11, right?

Mind sharing your settings?

I can't get right settings for 7950, what settings should i use?

Here are the relevant settings I am using for my MSI R9-270 2GB to obtain 90-93khash/s on microCoin.  Hope it is useful.

--gpu-engine 1100,1100 --gpu-memclock 1200,1200 --rawintensity 5120 --buffer-size 1400 -g 1 -w 256 --lookup-gap 2

One of my systems with 3 cards has since my post bluescreened so I might need to tweak it more to run stable.

thanks for help, but that didn't work for me on yac

It's for MRC/UTC, N 11.

Will try asap.

You need to say how much memory the card has... post YOUR command line and I'll explain the differences that need to be made.

I tried the command line you posted above for R7 250. my card has 3GB memory

YAC: R7 240 4GB 2.9 Kh/s

MicroCoin: crappy 7950 3GB 110 Kh/s

still testing

for MRC weird A and U (U=80)

It's going to be wild speculation - you WILL need to experiment on your own, unless someone wants to loan me one for a week or so, then I'll have the perfect command line :)


You've got so many shaders and can't use them all at lower lookup-gap values, so we try here to use them to trade off for the lack of memory by increasing the lookup-gap.  8 is probably a decent place to start (we like 1,2,4 & 8, the others are oddball sizes).  I'm assuming you can allocate 2,560 MB in one thread (i.e. you have more than 4 GB system memory - if you don't you are going to have a bad time), and at lookup gap of 8, that amount of memory can only support 5,120 simultaneous threads at N=14, so that's the value for -R.

Another theory would be to try lookup-gap 12 and -R 7168 - I don't think the extra work being don by the extra 2048 shaders will make up for the extra 4 runs through on the lookup gap, but like I said... wild speculation :)

Nice settings!  The R7 240 4GB is spot on for my findings.

On your MRC miner - if your 7950 has 1792 shaders, I would see if you can take the --rawintensity to 7168 - everything else being the same.  6400 would be where I would be if I had 1600 shaders.  A secret I'll share is that for settings that aren't memory limited, I just use "-X 4" and don't even do the math to figure out the -R :)

U of 80 isn't unreasonable for 110 KH/sec - if you're getting a lot of rejects or HW errors, that will suffer.  If you're getting HW errors, (I would be surprised),lower the -R.  That value also normalizes over a long period of time - some start off like gangbusters, some start out REALLY low, but they all work their way to an average after a couple days.

Interesting...thanks for sharing master  8)

It sems that A and U are simply multiplied by 16 when mining MRC.

7950 is down to 80 Mh/s again with --rawintensity 6400 or 7168  >:(   club 3d  :'(

ok tell me if this is normal, i used your suggested command line, first time i don't see any HW but rate is just 5kh/s is this normal for my card?

That's a pretty great rate for a card mining YAC....  compare it to all the cards on the YACoin wiki http://yacoinwiki.tk/index.php/Mining_Hardware_Comparison (http://yacoinwiki.tk/index.php/Mining_Hardware_Comparison) and you'll find it compares really really well...  Now that you aren't getting HW errors, overclock it until it's unstabe!  (and then bring it back down until it is stable...)

enjoy your hash mate - none of my cards get over 3 KH/sec

There's more math to it than that, but if your pool doesn't use vardiff then, yes, they will be different by a multiple of whatever the pool difficulty is.

5kh/s out of a 7950?

That's pretty crazy... ???

It's only got 3 GB - I'd guess > 7KH/sec if it had 4 GB and overclocked well

That'd be insane...I mean, haven't seena any do so well, but haven't tried it myself either. hmmm

Ok thank you that helped a lot. yeah i get 4.97kh/s stable with no HW
I will post screenshot after some attempts of tuning

I have been trying the new yacminer version on bitleu, but so far I got only driver crash.
I have been using this config on the previous version 3.4.2-yac2 without any problem on a R9 290x
What would I need to change, to get it work with the new version ?
I changed so far scrypt into scrypt-chacha.

{
"pools" : [
   {
      "url" : "127.0.0.1:8877",
      "nfmin" : "4",
      "nfmax" : "30",
      "starttime" : "1394480376",
      "user" : "dom",
      "pass" : "password"
   }
]
,
"xintensity" : "96",
"vectors" : "1",
"worksize" : "512",
"kernel" : "scrypt-chacha",
"lookup-gap" : "2",
"thread-concurrency" : "16897",
"shaders" : "2816",
"gpu-engine" : "1030",

Thanks for your help.

that should be all you have to change.  start with xintensity of 4

I can't seem to pass the -R or --rawintensity flag in a conf or in an .sh file in linux.
Every time I use it it closes on startup ????

./utc_mine.sh: line 1: 18391 Segmentation fault

Add -T and -D look for messages about what went wrong

Did so:

./utc_mine.sh: line 1: 27978 Segmentation fault      

Settings: --scrypt-chacha --nfmin 4 --nfmax 30 --starttime 1388361600 --no-submit-stale --expiry 10 --scan-time 1 --queue 0 --gpu-engine 0-947 --gpu-memclock 1375 --gpu-fan 70-100 --temp-target 85 --temp-cutoff 100 --temp-overheat 90 --auto-gpu --auto-fan --rawintensity 4096 --buffer-size 1024 -g 2 -w 256 --lookup-gap 2 -T -D

Maybe I did something wrong when compiling it?

SMOS 1.3

#!/bin/sh
mine stop
sleep 5
cd /home
apt-get install libudev-dev+
ln -s /usr/local/lib/libjansson.so.4 /usr/lib/libjansson.so.4
ln -s /lib/x86_64-linux-gnu/libudev.so.0 /lib/x86_64-linux-gnu/libudev.so.1
ln -s /lib/x86_64-linux-gnu/libudev.so.0.13.0 /lib/x86_64-linux-gnu/libudev.so.1
git clone https://github.com/Thirtybird/YACMiner/
mv /home/YACMiner /opt/miners/YACMiner
cp /opt/ADL/include/*.h /opt/miners/YACMiner/ADL_SDK/
cd /opt/miners/YACMiner
chmod +x ./autogen.sh
./autogen.sh --enable-scrypt --enable-opencl
make
sleep 5
clear
cd /root/
echo '/opt/miners/YACMiner/yacminer -o stratum+tcp://ultra.nitro.org:3337 -u diegolisandro.1 -p x --scrypt-chacha --nfmin 4 --nfmax 30 --starttime 1388361600 --no-submit-stale --expiry 10 --scan-time 1 --queue 0 --gpu-engine 0-1000 --gpu-memclock 1500 --gpu-fan 70-100 --temp-target 85 --temp-cutoff 100 --temp-overheat 90 --auto-gpu --auto-fan --intensity 12 --thread-concurrency 16384 -g 2 -w 256 --lookup-gap 2' > utc_mine.sh
chmod +x utc_mine.sh
clear

Further edit: I definitely did something wrong, linux noob...I don't see fan speeds nor temperatures, so something related to ADL. :/

Thought you said it crashed on startup?

run "./yacminer -n" (dont use any scripts on anything) - does that work? 

it compiles and that runs on my ubuntu box, just doing the git clone, running autogen.sh, and make.

It runs, but I can't get raw intensity going.

Last person who told me this was actually launching a diffeent version of yacminer someone on his machine as he wasn't using the "./" before yacminer when launching.  launch with a -V to get the correct version number.  Try launching with a -I set and change to raw intensity through the interface (so long as you have curses) - it's on the same menu as intensity, so hit "G" and then hit "A" if it's on the menu.  If it isn't , what the heck are you doing???  8)

I compiled 3.5...how would I be using a different version? :p
I'm a noob with linux but I don't do magic xD

Ok, I can change rawintensity whilst it's running. 5120 worked, got up to 145kh/s per r9 290 at stock under linux 32bit, using 4gb of ram only. I can't start it with it set though.

How do you compile it to get temperature readings? I'm at a loss...copied ADL in there and it didn't work.

Yep, just need to have the headers in the ADL_SDK directory.  when you run autogen.sh you'll get a summary and it will say whether ADL was found or not.  I do have issues if I launch it through RDP where fan and temp isn't available (because it detects rdp as a video driver or something so opencl devices and adl devices don't match) - someone else has the same thing with linux, but this is how it's always been for me (even with version of cgminer etc.)

Well, all the pre-installed miners do report temps. :/
Maybe I need to compile them with a monitor first before going headless?

pre-installed??

I tried it but it didn't work. The program just hanged then the driver crashed.
I try it from a version I compiled from the source as well with the binaries (hoping I made a mistake somewhere...) but in both cases yacminer crashed.

For MRC Works with 7950 with 6GB RAM, but not with 4GB RAM computers.
Any tips  ???

For me rI only works when I set it manually on kubuntu. Yacminer 3.5.0-yac2; R7 240 1x 4GB, ADL is installed.

I have got an older gpu driver, but that should not interfere with yacminer?

Pre-installed as in, I'm using Smos, a BAMT fork thing.

It's a pre built iso with mining soft, I'm sure you know it (?)

did you post your command line somewhere?

nope - pure windows guy here.  I have one linux box that I test compilation on, but it's my HTPC and I dont have the proprietary amd gpu drivers on it, so it doesn't mine.

:(

No prob, mining heavycoin now...I'll try compiling it on my main rig using linux and then flashing that iso to the pendrives at the farm.

Thanks anyway, you rock.

#!/bin/sh
export DISPLAY=:0
export GPU_MAX_ALLOC_PERCENT=100
export GPU_USE_SYNC_OBJECTS=1
export GPU_MAX_HEAP_SIZE=100
cd /home/bab5/YACMiner-master
./yacminer --scrypt-chacha -I 8 --thread-concurrency 24576 --worksize 128 -g 2 --lookup-gap 2 --gpu-engine 1100 --gpu-memclock 1000

If I put -R 640 or similar in there this happens:

bab5@bab5-desktop:~$ ./yac_mine.sh
 [2014-03-17 08:33:31] ./yacminer: -R:                     
bab5@bab5-desktop:~$

Mining Bitleu with yacminer, I am getting these results:

7950-> 2.8mh
r9 270 -> 1,6 mh

can somebody confirm if these are optimal, or what is a benchmark number for these cards? i have no idea if i am doing below or average hashrate:))))

who can help me config 270x and 7970 mining bileu :(

Well, if that's the ONLY output, then based on that, it's only one of a couple things :

 [2014-03-17 10:36:55] yacminer: -R: requires an argument
 [2014-03-17 10:50:18] yacminer: -R: Invalid value passed to set raw intensity
 [2014-03-17 10:37:02] yacminer: -R: unrecognized option
 [2014-03-17 10:53:42] yacminer: -R: Invalid parameters for raw intensity

Two of which are produced by any code I've had to touch(part of libccan), and the code for -I is identical for parsing the parameters.  If the library wasn't working or was different from what's included in the source, then -I would not work either, so I'm leaning towards the second or third option, and my guess would be that it isn't the latest code or you're executing a different binary if you compiled 3.5.0 yourself.  run

./yacminer -V
and
./yacminer --help

let's see that output...

With that said though, There is a missing return value in the set_rawintensity routine (all the other ones return NULL, this one could return garbage I guess).  I've added that return value and committed it.  If you've checked the other issues and know that's not it, pull the latest version from github, compile it and try that.  I'd like to know either way if it works or does not.

So tried updating my system, saw that it did not update anymore, changed server and it worked again. So tried after that to recompile. Did not work. At least I dodged the embarassment of forgotten updates. :D

Next thing downloaded everything from github again, recompiled and then no error. But still just I set, so removed I from script and now its rI.

Awesome, somebody can buy himself some cocktail or asian takeout when I get some coins together. Thank you!

For completion the requested infos:

bab5@bab5-desktop:~/YACMiner-master$ ./yacminer --help
yacminer 3.5.0-yac2
Built with GPU scrypt mining support.
Usage: ./yacminer [-BDdGEgIXRKklmpPQqsTouvwOchnV]
Options for both config file and command line:
--api-allow <arg>   Allow API access only to the given list of [G:]IP[/Prefix] addresses[/subnets]
--api-description <arg> Description placed in the API status header, default: cgminer version
--api-groups <arg>  API one letter groups G:cmd:cmd[,P:cmd:*...] defining the cmds a groups can use
--api-listen        Enable API, default: disabled
--api-network       Allow API (if enabled) to listen on/for any address, default: only 127.0.0.1
--api-port <arg>    Port number of miner API (default: 4028)
--auto-fan          Automatically adjust all GPU fan speeds to maintain a target temperature
--auto-gpu          Automatically adjust all GPU engine clock speeds to maintain a target temperature
--balance           Change multipool strategy from failover to even share balance
--benchmark         Run cgminer in benchmark mode - produces no shares
--buffer-size|-B <arg> Set OpenCL Buffer size in MB for scrypt mining, comma separated
--compact           Use compact display without per device statistics
--debug|-D          Enable debug output
--device|-d <arg>   Select device to use, one value, range and/or comma separated (e.g. 0-2,4) default: all
--disable-gpu|-G    Disable GPU mining even if suitable devices exist
--disable-rejecting Automatically disable pools that continually reject shares
--expiry|-E <arg>   Upper bound on how many seconds after getting work we consider a share from it stale (default: 60)
--failover-only     Don't leak work to backup pools when primary pool is lagging
--fix-protocol      Do not redirect to a different getwork protocol (eg. stratum)
--gpu-dyninterval <arg> Set the refresh interval in ms for GPUs using dynamic intensity (default: 7)
--gpu-platform <arg> Select OpenCL platform ID to use for GPU mining (default: -1)
--gpu-threads|-g <arg> Number of threads per GPU - one value or comma separated list (e.g. 1,2,1)
--gpu-engine <arg>  GPU engine (over)clock range in Mhz - one value, range and/or comma separated list (e.g. 850-900,900,750-850)
--gpu-fan <arg>     GPU fan percentage range - one value, range and/or comma separated list (e.g. 0-85,85,65)
--gpu-map <arg>     Map OpenCL to ADL device order manually, paired CSV (e.g. 1:0,2:1 maps OpenCL 1 to ADL 0, 2 to 1)
--gpu-memclock <arg> Set the GPU memory (over)clock in Mhz - one value for all or separate by commas for per card
--gpu-memdiff <arg> Set a fixed difference in clock speed between the GPU and memory in auto-gpu mode
--gpu-powertune <arg> Set the GPU powertune percentage - one value for all or separate by commas for per card
--gpu-reorder       Attempt to reorder GPU devices according to PCI Bus ID
--gpu-vddc <arg>    Set the GPU voltage in Volts - one value for all or separate by commas for per card
--lookup-gap <arg>  Set GPU lookup gap for scrypt mining, comma separated
--intensity|-I <arg> Intensity of GPU scanning (d or -10 -> 20, default: d to maintain desktop interactivity)
--xintensity|-X <arg> Shader based intensity of GPU scanning (1 to 9999), overrides --intensity|-I.
--rawintensity|-R <arg> Raw intensity of GPU scanning (1 to 2147483647), overrides --intensity|-I and --xintensity|-X.
--kernel-path|-K <arg> Specify a path to where bitstream and kernel files are (default: "/usr/local/bin")
--kernel|-k <arg>   Override sha256 kernel to use (diablo, poclbm, phatk or diakgcn) - one value or comma separated
--load-balance      Change multipool strategy from failover to efficiency based balance
--log|-l <arg>      Interval in seconds between log output (default: 5)
--lowmem            Minimise caching of shares for low memory applications
--monitor|-m <arg>  Use custom pipe cmd for output messages
--net-delay         Impose small delays in networking to not overload slow routers
--nfmin <arg>       Set min N factor for mining scrypt-chacha and N-Scrypt coins (4 to 40)
--nfmax <arg>       Set max N factor for mining scrypt-chacha and N-Scrypt coins (4 to 40)
--no-adl            Disable the ATI display library used for monitoring and setting GPU parameters
--no-restart        Do not attempt to restart GPUs that hang
--no-submit-stale   Don't submit shares if they are detected as stale
--nscrypt           Use the adaptive N-Factor scrypt algorithm for mining
--pass|-p <arg>     Password for bitcoin JSON-RPC server
--per-device-stats  Force verbose mode and output per-device statistics
--protocol-dump|-P  Verbose dump of protocol-level activities
--queue|-Q <arg>    Minimum number of work items to have queued (0+) (default: 1)
--quiet|-q          Disable logging output, display status and errors
--real-quiet        Disable all output
--remove-disabled   Remove disabled devices entirely, as if they didn't exist
--rotate <arg>      Change multipool strategy from failover to regularly rotate at N minutes (default: 0)
--round-robin       Change multipool strategy from failover to round robin on failure
--scan-time|-s <arg> Upper bound on time spent scanning current work, in seconds (default: 15)
--sched-start <arg> Set a time of day in HH:MM to start mining (a once off without a stop time)
--sched-stop <arg>  Set a time of day in HH:MM to stop mining (will quit without a start time)
--scrypt            Use the scrypt algorithm for mining
--scrypt-chacha     Use the scrypt-chacha algorithm for mining (aka scrypt-jane)
--shaders <arg>     GPU shaders per card for tuning scrypt, comma separated
--sharelog <arg>    Append share log to file
--shares <arg>      Quit after mining N shares (default: unlimited)
--socks-proxy <arg> Set socks4 proxy (host:port)
--starttime <arg>   Set nStartTime for mining scrypt-jane and N-Scrypt coins
--syslog            Use system log for output messages (default: standard error)
--temp-cutoff <arg> Temperature where a device will be automatically disabled, one value or comma separated list (default: 95)
--temp-hysteresis <arg> Set how much the temperature can fluctuate outside limits when automanaging speeds (default: 3)
--temp-overheat <arg> Overheat temperature when automatically managing fan and GPU speeds, one value or comma separated list (default: 85)
--temp-target <arg> Target temperature when automatically managing fan and GPU speeds, one value or comma separated list (default: 75)
--text-only|-T      Disable ncurses formatted screen output
--thread-concurrency <arg> Set GPU thread concurrency for scrypt mining, comma separated
--url|-o <arg>      URL for bitcoin JSON-RPC server
--user|-u <arg>     Username for bitcoin JSON-RPC server
--vectors|-v <arg>  Override detected optimal vector (1, 2 or 4) - one value or comma separated list
--verbose           Log verbose output to stderr as well as status output
--worksize|-w <arg> Override detected optimal worksize - one value or comma separated list
--userpass|-O <arg> Username:Password pair for bitcoin JSON-RPC server
--worktime          Display extra work time debug information
Options for command line only:
--config|-c <arg>   Load a JSON-format configuration file
See example.conf for an example configuration.
--default-config <arg> Specify the filename of the default config file
Loaded at start and used when saving without a name.
--help|-h           Print this message
--ndevs|-n          Display number of detected GPUs, OpenCL platform information, and exit
--version|-V        Display version and exit
bab5@bab5-desktop:~/YACMiner-master$

So, I'm going to chalk that up to a bug in the code that is now fixed in source - Thanks for the help in squashing it!

Been messing with it for hours now and I cant use any of the Nfmin,Nfmax or StartT settings or yac miner will just close in milliseconds. As soon as I remove these parameters it starts but will be useless for me  :'(

^{yacminer --scrypt-chacha --worksize 256 --thread-concurrency 16384 -g2 -I 12 --lookup-gap 4
-o stratum+tcp://mrceu.nut2pools.com:6000 -u user.d -p xxx --Nfmin 4 --Nfmax 30 --StartT 1389028879}

Can anyone please help me point out whats wrong here ? Tried the other kernel, --scrypt etc.

change Nfmin to nfmin, Nfmax to nfmax and StartT to starttime

One little bug I have noticed is that in 1 out of ~5 launches the config settings for gpu-engine and gpu-memclock are not used, the GPUs end up running at their stock values.  I have noticed it on 3 of my systems.

Not a big issue as you ca either just re-launch or change the settings from within but just bringing it to light.

the same parameters that fail will work  .. randomly?  OR different parameters will work?  Can I guess that you're on linux?

Thank You so much  :) God knows how long it would have taken me to figure it out ;D

Just long enough to read the release notes or the documentation, or the "--help" screen maybe? :D

Actually went through both of them but just did'nt catch the small difference difference  :)

I'm on windows8 64bit and windows7 64bit using the binaries.

Yeah its weird, most times the parameters work, but sometimes they just don't seem to get passed along.

Finally, someone I can relate to :)  post your command line.  I'm wondering if it's something I noticed a long time ago (with all miners) and just took as a fact of life..

With that said, I did have one card that just wouldn't even clock up when starting a miner - had to force it set with afterburner, but it's been behaving after driver re-installs and upgrade to 13.12.

Buy more RAM  ;)

As Thirtybird suggested --rawintensity 7168 works great. GPU 1150, MEM 1300, --buffer-size around 2000 gives around 120 Kh/s.



What would be best coin for my R7 240 4GB to mine (YAC= 2.9 Kh/s; MRC= 23 Kh/s; ...; ...)?

I mine yac on them...also on a GTX 780. Total= 14kh/s, soon to be 18 once I get a GTX 750 Ti.

Where should i put the yacoin.conf file? I have tried in .cgminer, .yacminer or even at run directory, but yacminer still won't find it??

Thanks in advance.

filename should be yacminer.conf and in the running directory.  Ya, I got that wrong in the release notes, sorry.

I have tried it before. And it doesn't work either. :(
Btw, you don't need to be sorry. Your miner is amazing, just I can't still tune it for my AMDs. Its hard, to be honest.

Well, fire it up with command line parameters and then hit "S" and then hit "W" - it should prompt you to save a filename.  Just hit enter and it should write out your config file into your working directory. 

So I just put together another mining system, this time with R7-240s for YACoin and having some trouble on my initial test runs.
MB: Gigabyte 990A UD3P (has 4x PCIE16x, 2x PCIE1x)
Memory: 4GB
GPU: 6x Sapphire R7-240 4GB (direct on MB for the 4 PCIE16x, 2 powered risers for the 2x PCIE1x)

If I use values like supplied by Bitcodo, on load yacminer flashes some error about the kernel and all 6 video cards are 'OFF' as soon as YACminer loads.  

IF I set --buffer-size between 1200-2000 4-5 of the cards will run while 1-2cards are OFF.

In order to get the cards running I have to lower --buffersize all the way down around 1000 which seems wastefully low.  Then they will hash at ~1.8khash but with pretty much equal amount of accepted and HW errors.  If I drop --rawintesity down to 1024 it seems to run without HW errors but hashrates of 1.2 make it a waste of time.

It sounds like pretty much everyone with the 4GB cards are all Sapphire brand so I assume it must be something with system not the videocards that is screwing up the performance.  My guess is that maybe 4GB system memory isn't enough for 6 4GB cards?  

4GB is not enough for even 2 4GB cards.  Wtih 4 GB system RAM, you can run 2 4GB cards with 2 threads (-g 2) and 1 2GB cards with -g 1.  This is on Window 7 and from personal experience.  Now that I have 8 GB system memory, I can run 4 R7 240 4GB cards each with 1 thread, and life is wonderful.  Whether I could do 6 or not, I do not know.  Someone said to try increasing your virtual memory (i.e. paging file), which may help you get it kicked off.  Seriously though, 24GB in graphics cards on 4GB system RAM is probably too disparate a ratio.

You need a lot of system RAM. I have 8GB and sometimes I get low disk space warning (small disk) so it might be that is trying to make bigger paging file. I also sometimes get -4 warning from miners (something about kernel and queue), but everything works OK. I am mining YAC with msi r7 240 4gb low profile + microcoin with 7950.

edit: r7 can do --buffer-size 3750

That's interesting.  Part of the fun of Scrypt-Jane is that it is much more system dependent.  I have no issue with 6x7950(2GB) doing normal Scrypt with only 4GB of system ram.  The error code I get is the same as you mentioned bitcodo.

I'll add another 4GB of RAM and adjust the paging file and see what happens...

I'm really struggling to get a decent YAC rate out of my three MSI R9 290 (4Gb) cards; the best I've managed so far without a load of hardware errors is a little over 5kH per card which seems too low to me!

I've tried to go through the tuning guide in the readme, have tried 2, 4, and 8 for lookup gap, but still can't do any better.  Can anyone help please? :)

My "best" settings so far:


Edit: I'm running Windows 7 64-bit with 8Gb of system RAM, using the above settings Task Manager shows 1419/8153 memory in use (so well over 6Gb of physical memory available)

Thank you for keep improving the miner, Thirtybird. :) I've just updated though haven't really tried to do more tuning.

I'm getting like 1.6-1.7kh/s from a R7 240 2GB (buffer size 1752, lookup gap 3, g 1, w 256, raw intensity 1280, gpu engine 780, gpu memclock 780, gpu powertune -17), which is some way off what others are getting. I'm underclocking the RAM because performance is somehow very similar when I use stock settings.

Your settings look pretty close to me.  YAC favor cards with lots of memory, and relative to how many threads you have (2560), 4GB is actually not much i the way of memory.

Your ideal settings (no HW errors) will be one of these (based on 3600 buffer-size)
LG   rI
6   5296
7   6227
8   7200
9   7680
10   8694
11   9804
12   10240

You may need to round down to the nearest multiplier of --worksize (Depending on your driver).  Obviously, the more you can allocate with buffer size, the higher your rI can go

Thats a good config.  That R7 240 can clock up to 1100 MHz though, and that's where the difference is I'm sure.  ~2.1KH/sec is about right for that card with a good overclock.  I've found very little difference in speed with RAM speed changes - for me it's all been about the core GPU speed.

@Thirtybird
do you have config for sapphire 290 trix oc?
also can we use this miner for ultracoin?

no, I do not - you can work it out though.  You need to post the maximum memory you can allocate via --buffer-size and what coin you're mining.  If you're allocating around 3552, it will likely be LG=8 and rI of 6912 or so for YACoin.  With the same buffer-size of 3552, UTC would be shader limited, and I would recommend xI of 32 or xI of 64 or so.

we can.  In fact, I do mine UTC with it. (and YACoin [of course], and vertcoin, and middlecoin, and wafflepool, and even Thorcoin and BitLeu)

If it's scrypt, Adaptive-N-Scrypt, or scrypt-chacha(even if you call it scrypt-jane), it'll mine it.

this should be the default bamt miner.

my rig has 24gb ram and using this config with cgminer:

and getting 177 kh/s

If you're mining UTC, that's fine - like I said, you're shader limited ... for now :)  When you hit N=12, you'll need to make changes.

The same config with YACMiner will work (because I kept all the legacy settings available), you'll just have to get used to calling it scrypt-chacha :)


When N changes in 2 weeks, you're going to want to set --buffer-size as high as you can get it (while still keeping it in dedicated GPU memory - see my scrypt-readme file on my github for how to do that) and then if you can get it high enough, you can go to lookup-gap 3 to keep using -X, otherwise at LG=2 you're memory limited and will want to start using --rawintensity (-R) to set intensity instead of -X.  IF that's as much as you can allocate, you're stuck with LG=4 when N=12.

Thanks - I'm just so used to my R9 290s significantly outperforming my GTX 780s I assumed I must be missing something!  I also got a bit excited when I got over 10k on my first attempt before noticing all the hardware errors... :(

What's the relationship between buffer size and raw intensity at the various lookup gaps?  Besides LG 8 being double the buffer size of course, that one I can manage myself!

i tried this setting for vertcoin but i am getting all  rejects :/
also 15kh/s when mining ultra

Those settings were not for vertcoin, so of course it wouldnt work!
15 KH/sec on UTC with those settings - on an R9 290?  Only way that's possible is if your thread is going into dynamic memory instead of dedicated memory - lower the buffer-size if you find that to be the case (I detailed that in the scrypt-readme I pointed you to).  My laptop gets 35 KH/sec with those settings, so you've got something to figure out my friend.

Update:

I have had success in running 6x Sapphire R7-240 4GB with 8GB system ram with windows7 x64.

Buffer = 1519, g = 2, rawintensity=768, lookupgap = 2 >>>> each card hashing YAC at 2.9-3.0 khash/s.  Any other intensity values gave less hash and more HW errors (768 = shadersx2).

Still would be better with more system memory as I get about 5% HW errors still.  With 4 cards I could run Buffer=1600 and have one card  with like 2% HW errors.  WIth 6 cards if I set Buffer >= 1520 I get the kernel4 error and 1 or more cards switch to OFF.

I tried it with 16GB system memory and could run Buffer = 2700 before kernel4 errors.  At this setting I got 0 HW errors on any cards...but needed that ram back in other systems. (I can't remember if I had g=1 or g=2 for this test).

I think with 12GB ram you could run 6x R7-240 4GB cards at max hash with 0 HW errors.

I think you did some math incorrect. Those cards have 320 shaders on them.  I just got confirmation that a user has gotten 6xR7 240 4GB cards running on a windows machine with G=1 with 8 GB of memory.  I'm doing that with 4 cards, so It's certainly in the realm of possibility with 8 GB.  System memory only dictates how large a buffer you can assign - HW errors come from setting too high a -R within a single thread.  When I ran mine with -g 2, -R should be 640.  Minimum buffer size for -g 2 -R 640 at N=14 is 1280.

hi, cant seem to find the settings for UTC for the current n-factor.. what does buffer size means?

It mean show much vram you're allocating for the miner to use.

You can more often than not find the sweetspot using 80%-90% of the total ram. Do the math and experiment, then set lookup gap to 1,2,3,4 following the guidelines in the readme.

For UTC you can still use lg 3 or 4 with most higher end cards, and more or less get away with -R equal to 4 times the shader count and -g 1. lg 3 will demand you cut down on -R but you'll have to experiment yourself.
I find getting more than 0 HW unacceptable.

Someone is mining YAC with 280x ? I need a example configs for: OS Win7(x64), 10GB RAM
My videocard has 3GB Ram

Appreciate any example :)

Not worth it to mine yac with it...I can do 4kh/s but you'd make more money mining something else with 280x cards.

Config:

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

Thank you, i will try those settings. Cheers

p.s. 10x for advice

I'm mining MRC and UTC, try for 2 hours, still can't figure out the config for my 7850 rig.

6 * MSI 7850 1G, with 8G system memery.

Any help please.

yacminer --scrypt-chacha --worksize 128 -g 1 --lookup-gap 5 --buffer-size 706 -R 3456 -o stratum+tcp://<pool address>:<port> -u <username> -p <password> --nfmin 4 --nfmax 30 --starttime 1388361600

Thank you very much for your suggestion.

It still doesn't work. :( The DOS window does show up and list 6 rigs , 0 K for each one. and the system don't work for a while, then the DOS window close itself or I have to reboot the system.

there's my config for the last n-factor that working fine:
-o stratum+tcp://mrcus.nut2pools.com:6000 -u abc -p abc --scrypt --Nfmin 4 --Nfmax 30 --StartT 1389028879 --queue 0 --scan-time 2 --expiry 4 -I 10 -g 1 --thread-concurrency 8192 --lookup-gap 2 --shaders 1024 --temp-target 80 --temp-overheat 90

Could you please give me some further advice?

Start working with 1 device at a time "--device 0".  Lower the "--buffer-size" a bit until you get the device to start.  If there's no errors and warnings, that's likely the best place to start - if you get messages, I would need to know what it's saying.  That config you posted does not look like it would have worked well for any coin at N=11, and certainly won't at N=12.

http://c:\asss.jpg

I tried "--device 5" and get it working on about 3K speed when "--buffer-size 670", but only get HW. Even I tried "--buffer-size 480" but no A showing up. There's no message come up.

That config I post was working for MRC when N=10. Means last and last N-factor. My mistake.:)

If you're allocating less memory, you have to raise the lookup-gap or lower the intensity.  If you cant only get it started at BS=670, then try lookup-gap 6 and -R 3840

It get the same result: no message, around 3.8Kh , only HW return.

My config:
yacminer -o stratum+tcp://mrcus.nut2pools.com:6000 -u abc -p abc --nfmin 4 --nfmax 30 --starttime 1389028879 --scrypt-chacha --worksize 128 -g 1 --lookup-gap 6 --buffer-size 670 -R 3840 --device 5 --temp-target 80 --temp-overheat 90

So confused   :(

Post your system specs please...ram, board, cpu, gpus.  ;)

and driver version... if it's 14.x we have a winner (well, loser)

sys: Win7 64
cpu: E3v2
board: H61 BTC
mem: 2 * 4G
driver: 13.12

rig:
AMD Radeon HD 7850
Transistors: 2800M
Shaders:1024
Bus Width: 256Bit
Bandwidth:153.6GB/s
Memory size: 1024M

 :'( for the win

If you're only getting 3.8KH/sec and HW errors abound, it sounds like you're mining a pool at NF=14 (look on the pool connection line, look for NF=XX).  The settings I gave you are for NF=12, if you're on an NF=14 coin, then they will not work.  I pasted those exact settings on my machine with a 7850 1GB card and it hashed properly.

You're leaving out something important (like multiple pools configured, and not configured properly) or have something wrong with your machine, or are just trolling us.  Run with your settings, hit "S" to bring up the settings menu, then "W" to write out a config.  Save it to some file and paste the ENTIRE contents here. 

As you said, I removed multiple pools from config, then make some progress, YACminer return both A and HW instead of HW only.

-lookup-gap 6 --buffer-size 670 -R 3840:
get 15Kh/s , return A and HW

-lookup-gap 5 --buffer-size 670 -R 3840:
get 17kh/s, return A and HW

The config file is:
{
"pools" : [
   {
      "url" : "stratum+tcp://mrcus.nut2pools.com:6000",
      "nfmin" : "4",
      "nfmax" : "30",
      "starttime" : "1389028879",
      "user" : "abc",
      "pass" : "abc"
   }
]
,
"rawintensity" : "3840,3840,3840,3840,3840,3840",
"vectors" : "1,1,1,1,1,1",
"worksize" : "128,128,128,128,128,128",
"kernel" : "scrypt-chacha,scrypt-chacha,scrypt-chacha,scrypt-chacha,scrypt-chacha,scrypt-chacha",
"lookup-gap" : "6,6,6,6,6,6",
"buffer-size" : "670,670,670,670,670,670",
"shaders" : "0,0,0,0,0,0",
"gpu-engine" : "0-0,0-0,0-0,0-0,0-0,0-0",
"gpu-fan" : "0-0,0-0,0-0,0-0,0-0,0-0",
"gpu-memclock" : "0,0,0,0,0,0",
"gpu-memdiff" : "0,0,0,0,0,0",
"gpu-powertune" : "0,0,0,0,0,0",
"gpu-vddc" : "0.000,0.000,0.000,0.000,0.000,0.000",
"temp-cutoff" : "95,95,95,95,95,95",
"temp-overheat" : "90,90,90,90,90,90",
"temp-target" : "80,80,80,80,80,80",
"api-port" : "4028",
"expiry" : "60",
"gpu-dyninterval" : "7",
"gpu-platform" : "0",
"log" : "5",
"no-pool-disable" : true,
"queue" : "1",
"scan-time" : "15",
"scrypt" : true,
"scrypt-chacha" : true,
"temp-hysteresis" : "3",
"shares" : "0",
"kernel-path" : "/usr/local/bin"
}

The pool is all right because of my 280x machines working fine, and its N=12 .

Thank you for your patience, I'm not so good at English, and really in trouble with the config.  I'm so sorry if there were any misunderstanding.
I appreciate YACminer and try to use it with my 7850s, that's it.

I'm considering whether to use "-g 2" cooperating with other parameters could solve the HW issue?

Thanks.

That exact config should _not_ give HW errors for Microcoin.  Lookup-Gap 6, Buffer-size 670, raw intensity (-R) 3840 is likely the top config for that card.

Hoping maybe you can help me out...
I have an ASUS R7 240 with 320 shaders and 2GB ram. My system has 3gb of RAM total. Running Ubuntu and thats the only thing running. Any combination I try, the best I can get is a 1:6 ratio of errors to accepts.


--worksize 256 --gpu-engine 1100 --gpu-memclock 1000 --gpu-powertune 20 --no-submit-stale --lookup-gap 2 -R 1280 --scrypt-chacha -g 1

That goes straight into HW immediately. Any ideas?

Of course it does.  2GB is not enough to run a lookup-gap of 2.  You didn't post your buffer-size setting, so I'm guessing, but depending on how much memory you can allocate, you can run LG=4 or LG=3 with a reduced -R parameter (might be faster).  So, try a buffer-size of 1712 and LG=13.  If you can't allocate a BS of 1712, allocate as much as you can and start lowering your R until you stop getting HW errors.  Then, so long as you can allocate at least 1280 for buffer-size, try again with a lookup-gap of 4 and -xI of 32 instead of -R 1280.  Then pick whichever setting gives the higher hashrate and pay attention to your U: value.

If you can't allocate 1280, well, that's a whole different set of problems...

Ok here is where we are at now:

The following yields 1.8khs with U: 1.5 avg:
--lookup-gap 4 --xintensity 32 --scrypt-chacha -g 1 --buffer-size 1708

The following yields 1.795khs with U: 1.76 avg:
--lookup-gap 4 --xintensity 32 --scrypt-chacha -g 1 (allowing the card to set buffer size results in 1496mb usage)

The following yields .6khs with U: 0 (didn't accept a share in 2 minutes so stopped it):
--lookup-gap 13 -R 1280 --scrypt-chacha -g 1 --buffer-size 1704

So I feel like this is much closer to being right on but I'm wondering how we can get it over the 2khs mark...I'm also running the following:

--worksize 256 --gpu-engine 1100 --gpu-memclock 1000 --gpu-powertune 20

Forgot to include that...

You need more system ram...I use 8gb for my 4 r7 240 2gb cards and get 2.35kh/s out of each.

lookup-gap 3 did the trick for me and my sapphire crap cards.

Ok so dropping the LG to 3 on --xintensity 32 --scrypt-chacha -g 1 --buffer-size 1708 I'm knocking around 2.2khs with a U of around 1.8 still...this is looking much better...thanks to both of you. Yes I plan on dropping some more RAM soon into this cpu/board but gotta make the money to do so. Thanks again!

You may get the occassional HW error with those settings FYI.  But it's real close (hence why I recommended BS=1712).  Don't forget to crank up the GPU and memory clock!  My cards run between 1065 and 1100 GPU clock with 1000 memory clock on all of them.

1100/1000mhz here, you need special software or bios mods to get so high.

What cards are you running?  My Sapphire R7 240s can be set to that level and above within yacminer.  1150 is as far as I have tried.

I am running 1100 / 1100 just fine yacminer on ubuntu. Everything is holding steady guys! Thanks again for the help.

My crappy sapphire cards had a top limit of 1040 or something like that, can't remember since I bios modded them long ago.

I'm running the ASUS 2gb models.

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

I'll experiment with mine if I get some spare time and get back to you.

This is for yacoin, right?

Make sure you get thirtybird's updated yacminer build.

Many Thanks !!! yes yacoin and I use thirtubirds build

Ok, try this:

-R 7424 --buffer-size 3712 -g 1 -w 256

What kind of hashrate were you getting on that card with those settings?  What LG?

Oh forgot LG! lg 8...Close to 4kh/s with a mild oc.

I'm folding right now, curecoin where it's at for miners. (or yacoin ;) but I prefer to buy atm)

Wow, all those extra shaders really do NOT buy you much...

Not really...the 280x isn't too far behind, and neither is a gtx 750 ti at 3.5kh/s.

any experience with 290x ?
I cannot get it to work properly for YAC's higher n-factor. We get too many HW errors (more than accepted shares)
Works superb with MRC's 11 N factor, but for YAC we cannot get it right.

Try any of these settings:

--buffer-size 3712 --lookup-gap 4 -R 3712 -g 1 -w 256

or

--buffer-size 3712 --lookup-gap 8 -R 7424 -g 1 -w 256

Start from there and move up or down the -R value in 64 increments till you get 0 HW.

Thanks,

Will try that tonight and will report if succesfull.

N-factor change today. Do I have to change my settings for the r7 240 4GB, are there some new magical settings?

LG=3 and buffer-size over 3420

Please, can You give me some advice for 7850 with 2 GB VRAM and for 7660D with 2 GB VRAM. PC have 6 GB of RAM. For Yacoin.

buffer-size 1753
lookup-gap 8
rawintensity 1753

Can someone please post parameters for R7 240 4GB at N=15 ?
I can not get it over 820h/s without hardware errors.

can you not read back LITTERALLY three posts from yours?

Now that the Nfactor is over 14 I've tried experimenting with lower nfactor coins (ultra, micro, bdc) and nothing really looks that profitable with a R7 240 @ 2GB of ram...anyone got any suggestions on what they would do?

I tried that trom ivanlabrie and it crashed my driver. But it works with lookup gap raised to 3 (3 posts back, as you stated).
I got 1Kh with this:

--buffer-size 3712 --lookup-gap 3 -R 4992 -g 1 -w 256

Thanks.

Yeah, I'm doing something like that but I still get the odd hw...meh.
I'm back to folding for now, might get back into yacoin if I figure it out but for now I don't have time to tweak it sadly.

Maybe ZCC or YBC.  My R7 250 2 GB are still on YAC.  Not as effective, but no worse off than any other 2 GB card


Set your R to 1280 - you want R to be 4 time the number of shaders on the card.  Hashrate goes down if it's in excess of 4x unless its an even multiple of 4x the number of shaders (2560 gives the same hash rate as 1280 - it's pretty weird)

Thirtybird, how hard is it to modify your miner to incorporate new algorithm?

probably not terribly hard, but potentially extremely hard.  I was able to re-enable SHA256 and Scrypt, and Add N-Scrypt.  If someone's already done it in another miner, then it's on the easier side :)

Wondering if you can try to implement CryptoNight algorithm into your miner? There is an open source bounty out: https://bitcointalk.org/index.php?topic=656841

CryptoNight is suppose to be memory intensive, so it might be like mining YAC.

Just to benchmark, on a single core one thread cheap Pentium CPU, I got 25H/s using the non AES-NI enabled CryptoNight miner. (AES-NI enabled CPU hash is much higher) On your CPU Yacminer mining YAC, I got 55H/s.
The high end GPU only get 500H/s, but for YAC even the low end GPU get 1KH/s at current Nfactor. (low end currently not so good at CryptoNight, r7 240 only gets about 50H/s when I tested)

Even at current N = 15, GPU is still more effective than CPU at mining YAC, but for mining CryotoNight coins like XMR, there is no advantage. But I think its because the code is not optimized.

Can you take a look at this algorithm and see if its possible to make open source miner for it?



Edit: Here is Wolf's open source CPU miner for CryptoNight as reference: https://bitcointalk.org/index.php?topic=632724

I'm assuming you can try to decipher how the hashing function works in his miner and try to port it over to your miner.

I'm also assuming that the way that your miner talks to the pool doesn't change even though it would need to talk to a pool mining a CryotoNote coin and not a Bitcoin protocol coin.

I have Radeon 6970(2GB).

Please, can you tell me for sure whether it's suitable for mining of yacoins?
I've already tried to run yacminer v3.5 with diff settings on my system (Win7 x86, 2GB of RAM),
but I got HW-errors.

I will be very grateful for any advice.

I wrote a tool that is hosted on the ultracoin website for configuring your miner.

Go to http://www.ultracoin.net/configgen_raw.html (http://www.ultracoin.net/configgen_raw.html) and put in your card, how much memory it has and select NFactor = 15 and click the button.  Start with the settings it gives you at the top - something like this for a 2GB card


Also, read all the text that's there - I wrote and/or updated all of that to be specific to mining high NFactor scrypt coins.  It's not easy unless you're an expert, and there aren't many experts.

(PLEASE NOTE : REMOVE THE NFMIN, NFMAX, AND STARTTIME IN ANY CONFIG IT GENERATES FOR YOU AS THEY ARE SPECIFIC TO ULTRACOIN)

Hi.
I have a problem with mining YAC on my Radeon 7950 card.
My command-line options are:
yacminer --scrypt-chacha -d 0 --worksize 128 --lookup-gap 8 -g 2 --buffer-size 1295 -R 2560 -o stratum+tcp://yac.coinmine.pl:9088 -u X.1 -p Y --nfmin 4 --nfmax 30 --starttime 1388361600

also I`ve tried another options:
yacminer --scrypt-chacha --worksize 128 -g 1 --lookup-gap 8 --buffer-size 2590 -R 5120 -o stratum+tcp://yac.coinmine.pl:9088 -u X.1 -p Y --nfmin 4 --nfmax 30 --starttime 1388361600

But in both cases i receive:

Rejected 626b9dc7 Diff 1/1 GPU 0  (Share is above target)
Rejected 90b24df8 Diff 2/1 GPU 0  (Share is above target)
Rejected eaa24967 Diff 3/1 GPU 0  (Share is above target)
Rejected 5ca82134 Diff 17/1 GPU 0  (Share is above target)

The 'A' counter is zero, but the 'R' counter in yacminer main window is increasing.


The hardware configuration is:
2xR7950/3GB RAM (tested only on one card is you see)
4 GB of system RAM
Windows 7 64bit
Catalyst 13.9 drivers
AMD APP SDK 2.8.10 64bit
yacminer 3.5.0.

where I could be mistaken?

That's the wrong starttime for YACoin.  The starttime for YAC should be 1367991200 (you've put in Ultracoin's starttime), so you were mining at nFactor of 13 instead of 15.  Be prepared to change your other settings to work with NF=15... (You will get HW errors unless you lower your -R)

Hi

Can someone please say what's max. hashrate from one R7 240 4GB at NF=15 (YAC mining) today ?
And, what is the min. amount of system RAM required to mining without HW errors?

1.196 Kh/s today. Let's see what tomorrow brings.
8 GB works for 4 cards.
Next time you should at least read the last 2 pages.

So low hashrate ? Really?
At Nf(14) its value was ~2.9 Kh/s. Do you still continue mining YAC ?
Yes, I read the last 2 pages, but I meant min amount RAM for 1 card.

catalyst 14.x drivers dont work with this miner???

never had any luck with them, nope.

is there any other n-factor miner which works with 14.x ?

Hi all,

I am running yacminer from https://github.com/Thirtybird/YACMiner

My GPU is Gigabyte HD 7950 and driver is 14.10

Looks like I am not getting any shares even after couple of hours running. Any help ???????????????

./yacminer --scrypt-chacha --worksize 256 --lookup-gap 2 -g 1 -R 1792 --thread-concurrency 14080 --buffer-size 1664 -o  stratum+tcp://yac.m-s-t.org:3333 -u RiseOfTH.1 -p th --nfmin 4 --nfmax 30 --starttime 1367991200

5s):1.861K (avg):1.891Kh/s | A:0  R:0  HW:5  U:0.00/m  WU:1.41/m  FB:0
 ST: 2  SS: 0  NB: 5  LW: 35  GF: 0  RF: 0
 Connected to yac.m-s-t.org diff 2 NF 15 with stratum as user RiseOfTH.1
 Block: 47a3fbd9d4a1fe97...  Diff:248  Started: [03:31:33]  Best share: 4

 [P]ool management [G]PU management ettings [D]isplay options [Q]uit
 GPU 0:  62.0C 2851RPM | 1.900K/1.916Kh/s | A:0 R:0 HW:5 U:0.00/m T:1 rI:1792

 [2014-07-24 03:29:05] Started yacminer 3.5.0-yac2
 [2014-07-24 03:29:05] Probing for an alive pool
 [2014-07-24 03:29:09] Pool 0 difficulty changed to 2
 [2014-07-24 03:29:10] GPU 0: bufsize for thread @ 1664MB based on buffer-size
 [2014-07-24 03:29:10] Network diff set to 248
 [2014-07-24 03:30:11] Stratum from pool 0 detected new block
 [2014-07-24 03:30:31] Stratum from pool 0 detected new block
 [2014-07-24 03:31:06] Stratum from pool 0 detected new block
 [2014-07-24 03:31:33] Stratum from pool 0 detected new block

Uninstall 14.10 drivers and install 13.12.  Noone has had any luck with any 14.X drivers

Thanks for reply :)

I have tried with 13.12 with same problem.

But I am able to mine X11 coins like DarkCoin.

Also, I have tried other Scrypt-jane coins like CACHEcoin but having same problem.

okay, I overlooked an item on your config

./yacminer --scrypt-chacha --worksize 256 --lookup-gap 2 -g 1 -R 1792 --thread-concurrency 14080 --buffer-size 1664 -o  stratum+tcp://yac.m-s-t.org:3333 -u RiseOfTH.1 -p th --nfmin 4 --nfmax 30 --starttime 1367991200

--lookup-gap of 2 is WAY too low.  with that buffer size you need a LG of 8 and a -R of 1664 to avoid HW errors at NF=15

these coins require way more memory than you're trying to give it, so you have to go big on the LG. 

Please,update YACminer for driver 14

Anyone who wants to do it has the ability - the code is all on github.  I no longer have the time or ambition to work on it.

what is scrypt-jane(scrypt-chacha) nfactor?

is scrypt jane(scrypt chacha) nfactor is 12 ?how much the scrypt jane(scrypt chacha) nfactor?please excuse me my english is bad.

https://docs.google.com/spreadsheet/ccc?key=0Aj3vcsuY-JFNdC1ITWJrSG9VeWp6QXppbVgxcm0tbGc&usp=drive_web#gid=0 (https://docs.google.com/spreadsheet/ccc?key=0Aj3vcsuY-JFNdC1ITWJrSG9VeWp6QXppbVgxcm0tbGc&usp=drive_web#gid=0)





 ???

can you explain

Because , you could post where we can follow your work. sgminer v5 thread? Any tests with R7 240 4GB?  :)

Don't get your hopes up yet :P

Are you sure you're posting in the right thread?  Are you saying you've updated YACMiner, or are you just trolling?

The link to the github for this software is in my signature:

https://github.com/Thirtybird/YACMiner

Ahhh.  Other then the chacha-flexible branch of yacminer, I haven't really touched it since Mikaelh did some optimizing, and only then it was just updates so that lookup-gap wasn't compiled into the binary and could be changed in the host during runtime.

I'm guessing because looping and incrementing is easier to grok than bitwise comparison?  Heck, looking at what you've written, I had to do the manual look-and-see to even know that it comes up with the same answer, but then again, C is not my native language.  Today I learned the CLZ function... wouldn't a simpler formula:


or even


give the same result as flipping the number and bitwise-anding it?

The nice thing about working with factors of 2 - there will only ever be a single 1 in the binary, so not much really matters.  In VS, the following does give the right answer for all the iterations of N.


either way, I'm glad someone is interested in improving this portion of the miner.

I just tested with latest 14.12 omega drivers, I have 2x 290, one works fine even 5% faster, but the GPU in primary slot whatever I try give me:
Error -4: Enqueueing kernel onto command queue. (clEnqueueNDRangeKernel)

Also I had to drop GPU memory usage a lot by 15% (from ~3500Mb to 3070Mb) but still speed is better by 5%

With 13.12 both works fine

So far I tried -d 0 and 1 and only the one in second slot works, also tried connecting monitor just to intel integrated GPU and not using ATI for display, same...

Anyone have any idea can I try something?

I've noticed you can always allocate more memory to a single GPU than you can get away with allocating to 4.  On my rig, I was able to allocate 3800 to one card, but had to drop below 3600 to allocate to all 4.  I can't explain why, and I can't explain why the new drivers do what they do, I'm riding on 13.12 until I pull the plug on my farm.  I have also, noted that on every 4 card rig I have, GPU 2 need to run at either a lower frequency or a lower intensity or with a lower memory allocation.  Always assumed it was because it was the one driving the display, but didn't dig into it.

750 ti 3.25 kh/s
970gtx 9.5 kh/s

And the bit the AMD whore is really interested in.....R9280X 4.2kh/s, HD7950 3.8kh/s

No, 1100 & 1500mem

How are you getting on with NF14........worked any of your magic yet?

What u got Freya hashing at?

I acquired some GTX 750Ti 2GB but I can't seem to set them up properly.
The best I did was :
Which gives me only around 2,5 kH/s they should be doing more than 3k at this freq.
GPU 1350MHz, MEM 1525MHz
I have 5 cards running on 8G of RAM

When I try settings like:

-l t60x2 -H 2 -m 1 -i 0 -L 4
-l t5x24 -H 2 -m 1 -i 0 -L 4

I get "Cuda error" than "Driver Error" or the machine freezes. :(

Am I missing some command line like SETX....

@Kingpin


Here is what I use on my 750ti rig when mining UTC, gets a solid 3.2kh/s

cudaminer -s 10 --algo=scrypt-jane:UTC -H 2 -i 0 -m 1 -l t25x4 -L 4 -b 16384 -o stratum+tcp://stratum.tumblingblock.com:5555 -u **** -p x

Thanks, I am trying all types of settings but I get Errors.
I think it is something connected with Microsoft Visual C++.
I am using Windows 8 and Latest drivers, what else should I install or maybe my cudaminer is not right?

@King_pin

I use windows 7 on the 750ti rig and cudaminer 2014-02-28

Maybe you could try Kopiemtu.  Burn to a flash drive, ssh in, mine stop, monitor stop then change to cudaminer directory and start your command line.  I use Kopiemtu when I mine BBR but cudaminer works for UTC at similar speeds.

Just noticed were in the YACminer thread-sorry for going off topic.

I did not found a solution to my problem, but a workaround!
It appears for some reason when I go above -l t24x2 with -L 4 the dirver crashes only on my Windows 8 rigs.
IDK if it is a bad Windows, or something else, but I could not fix it. :(
I installed Windows 7 + Visual C 2010 + 337.88 drivers, and everything is working perfectly! :)
I am using now:
which gives me around 3.6kH/s @ 1222/1500 MHz

Any1 got good configs for NF15?
Seems that 950h/s is too low for an r9 280x (i have it undervolted to 0.95 at ~930 core 1375 mem)
I was expecting ~1.3kh/s

Best regards!

Hello , YACMiner has a bug . When I switch pool (use Key P + S + pool) , N Factor will auto change to 16 .  Backup pool can't run correctly . Please fix it.

Is not a bug, use  --nfmin  --nfmax  --starttime for each pool

Thanks  :). It's ok

Correct, but I'm still here if something if hugely wrong...


agreed - these are set for each pool you specify

Hi , I'm mining scrypt jane N Factor =14
6970 speed 4.7 khs (core/mem 900/400)
7950 speed 4.2 khs (core/mem 1000/400)
Who can explain why 6970 run faster than 7950?

Post your configs for each - SC N=14 is memory intensive, so the faster GPU doesn't always win.  Also, you may be having hardware errors you didn't mention (or notice)

hello..
have someone good  setup for sapphire 280x vapor-x for yacminer..
or some miner for scrypt-jane

Thanks

And me with the same question !

Thank you so much !

Hello...
Anyone have config for r9 270...
 I only get 2.6KHz per card with this config :
--scrypt-chacha --worksize 128 -g 1 --lookup-gap 8 --buffer-size 1648 -R 3200

I run with 1100- 1500 .
I think it have a litte speed when compare with 7950 and r9 280x. Speed should be ~ 3-3.5kh :(.

r9 270 - 3.17 Kh/s - core/mem 1150/500
7950  - 5.03 Kh/s - core/mem 1120/500

using kernel mod , bought from platinum4.

Link broken

LEOCoin is the only coin at NF=14 I know about

Whether it is or isn't I couldn't tell you, but they've made some very bold statements that I chuckled at.  People are mining it though, and the top 15 at the official pool have a combined  reported 3,500 KHash/sec right now.  If a decent card pulls 5 KH/sec, that's 700 GPUs in the top 15 at one pool...

The hashrate thrown at it is mind boggling  :o

this works, doesnt change to nf16. use starttime with pool, not below where gpu paramethers are.

"pools" : [
   {
      "url" : "stratum+tcp://leopool.org:3333",
      "nfmin" : "4",
      "nfmax" : "30",
      "starttime" : "1402845776",
      "user" : "user.worker",
      "pass" : "x"
   },
   {
      "url" : "stratum+tcp://leopool.net:3333",
      "nfmin" : "4",
      "nfmax" : "30",
      "starttime" : "1402845776",
      "user" : "user.worker",
      "pass" : "x"
   }
]
,
"rawintensity" : "",
"worksize" : "",
"kernel" : "scrypt-chacha",
"lookup-gap" : "",
"buffer-size" : "",
"gpu-threads" : "1",
"gpu-engine" : "",
"gpu-memclock" : "",
"gpu-powertune" : "",
"auto-fan" : true,
"temp-cutoff" : "",
"temp-overheat" : "",
"temp-target" : "",
"no-submit-stale" : true,
"expiry" : "1",
"queue" : "0",
"scan-time" : "1",
"scrypt-chacha" : true
}

someone has settings for 280x me alone HW

Can you explain meaning of "starttime" with value of "1402845776"?

Thirtybird,

  Thank you for doing the work on this miner.. I have been using cgminer-3.7.2-sj-0.03 for the last week because I could not get yours going at first.  Now I have it running finally.

however, I will have a hard time monitoring all my rigs because the rpc response does not give the speed of the card.  

here is a dump of yacminer json response for one dev;


I had trouble with with cgminer-3.7.2-sj-0.03 version at first because it also reports 0 Mh as yours does. However, I was able to calculate speed in the following by dividing the  [Total MH] by [Device Elapsed]

json dump of cgminer-3.7.2-sj-0.03


If you could add the Device Elapsed to the dev call, or better yet the MHS av and MHS 5s, that would be awsome... and a tip of course would be included.

if cachecoin catches on, your miner could quickly become very popular and I am sure others would appreciate being able to monitor the rigs remotely.

Jim


edit:
  I starting using the miners summary elapsed time to guestimate the card speeds...  the raw intensity and other very important chacha settings are also not in the json :(

I am still trying to tune...  it is difficult to get ZERO HW errors..  seams like as soon as I go faster than about 700h i get errors after a few minutes

currently:

"rawintensity" : "1536",
"buffer-size" : "1856",  
"lookup-gap" : "8",
"gpu-engine" : "1000",
"gpu-memclock" : "1250",
"gpu-threads" : "1",
"worksize" : "64",




as a comparison, here is cgminer:

Hi,

there is not a solution of CPU mining "windows 7" for CACHeCoin?

feature request:

add ability to change the rawintensity thru thru the API via rpc.

ability is already there to change the intensity, but not the rI.

This would aid in tuning as you woulddn't have to restart... and I can do it for all my rigs with a click.

Odd, I can change the Raw intensity while it's running - granted through the console, not the API.  Never used the API myself.  Honestly, I'm not likely to do any more dev work on this, but everything I have done is in the github repository.

Thanks for the response....  can you be bribed :)

integrate chacha into sgminer?...  yes, that sounds good

On NF16 I'm getting 205 h/s from R9 270x with ~14% HW errors (on 140A there is 1R and 20HW)

Can i ask: I have 2 R9 270x 2Gb and 2 R9 270x 4Gb. What's different settings i have to set? buffersize? but if i try to set buffersize for 4Gb card twice more than for 2Gb, i got a kernel error and card are OFF. May be i have to lower -R ? I have only 4Gb of RAM (Win7 64bit)

R7 240 4 GB card - 342 h/s
R7 250 2 GB card - 205 h/s

no HW errors on either

Is there any good coin for mining right now  ??? That is profitable  ???

Did you rewrite the kernel as well, or just find some good settings?

Nvidia maxwell cards hashrate don't depend on vram at all ...

eg. a 750ti 2 GB hashes as fast as a 750ti 4 GB

but it seems like the code is limited to use a max of ~1.05 GB.

With so little vram usage how come they still hash that fast?

That's using the opencl kernel that's published in my github (on one of the branches - chacha-flexible I believe) and a lot of time tweaking the settings of the miner and the card frequencies.  I have an updated kernel that I haven't used on the 250 2GB cards (because I've dismantled the miner that used them) that gave a 2.5% increase to the 4GB cards, so maybe 210 is possible.

FWIW Wolf0 - the 64 bit pointer stuff appeared to slow my miners down actually, so I'm not using it, and still on catalyst 13.12

can you share your bat? i have R9 270X. thanks.

what active coin's are out there atm which are be woth mining besides CACH?

YACoin
ZCCCoin
Ultracoin
LeoCoin

check out the NFactor spreadsheet in my signature - it gives a comprehensive list of the active Scrypt-Chacha coins that are out there and their N Factor change schedule.

Does anyone have an r9 270x config for nf 14? Keep getting HW :(

http://cfg.ultracoin.net/

Thanks! I am aware of that, but when I punch in the listed config, one of the 4 cards is only hashing at 60 h/s and then crashes yacminer. Furthermore, each card is only getting around 2 khs on each card which is pretty poor performance considering I'm getting 3.6 khs on 750ti's. When I allow the auto-buffer in 3.5.0, it buffs 446 MB. What should the rawintensity be with that buffer?

What I have to consider before compiling it for a special coin on my linux machine? For example for Ultracoin. Is there a config file which has to be changed (nstarttime for example) before start to compile? Thank you

446 MB?  you are trying to mine with a 512 MB card??  If your card has more than 512MB (which I would guess it does), you probably haven't done the commands to allow you to allocate more than 512MB.  There is a very detailed readme that comes with the miner (SCRYPT-README) that gives you lots of information on how to tune your setup.  If you've deleted it, it's always on my github source site

https://github.com/Thirtybird/YACMiner/blob/master/SCRYPT-README

Yes, I'm familiar with the readme

The config suggests 824 with 2 threads. I seem to have 1 of 4 270x's that don't mine properly with the config; its finicky (Getting like 50 hs) so I tried to let yacminer decide the buffer and it decided on 446 MB. Didn't help too much. Using -g 1 crashes the miner as well. If i restart it enough, sometimes it will start mining but it didn't make it through the night last night.

timeout /t 30
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_USE_SYNC_OBJECTS 1
del *bin
yacminer --scrypt-chacha -o stratum+tcp://xxxxxxxxx -u xxxxxx -p x --nfmin 4 --nfmax 30 --starttime 1402845776 --worksize 128 --lookup-gap 8 -g 2 --buffer-size 824 -R 1600

Furthermore, I cannot get past 2 khs, and it seems to be more stable on 1.8 khs. Is this all I can squeeze out of 270xs?

If you haven't run GPUz, I highly recommend it for troubleshooting.  YACMiner is looking at how much memory it sees, and allocates 90% of it if you do not specify (512 * .9 = 460), so you're having trouble where you cannot allocate all of the cards memory.  It will also show you how much memory is allocated to dedicated memory vs dynamic memory.  If your hashing buffer winds up spilling into dynamic memory, your hashrate is going to be dismal. 

My notes for NF=14 had my 2GB R7 250's hashing at 2.7 KH/sec, so you should be able to at least match that once you get your problems sorted out.

2.7?! I barely get that outta my 280x's.. What AMD driver do you recommend? 14.6 is the one I'm using.

GPUz is a cool tool, but it is showing me everything is correct as far as I can tell. Each card has 2 GB, memclock at 1400, gpu-engine at 955. I'm starting to mess with the lookup-gap, but I thought that was just set by the NF number. ..

13.12
My R7 240 4GB cards NF=14 at 2.8-2.9 KH/sec (depending on the card) even though they have fewer shaders.  It's all a matter of allocating the largest buffer-size you can and then testing each of the lookup-gaps with the corresponding max R for each one to see which one to settle on.  The 4GB card can run a lookup-gap of 2, whereas I had to go with LG=3 on the 2GB card.  It's all in the tuning guide I linked you to

13.12? Why such an old driver?

I'll continue to play.

It's what was out when I started this experiment and the 14.x drivers gave HW errors mining scrypt-chacha when I tried them.  Now at this point, I don't feel like tinkering with them because "they just work"

@ Thirtybird

Don't laugh at me. I get bored (and sometimes I am dangerous).

I am playing with Windows 10 and trying a 750ti with your miner. Long story short, new Nvidia driver supports OpenCL so I am playing with it to see if this will work.

When running the miner I have just a basic setting, besides the nfMin = 4 nfMax = 30 nTimeStamp = 1388949883, I just run the -I and change it higher until I get a HW error.

It does find the card and mines but it does not connect to the pool. The miner shows it and running but the pool does not show the miner active and I do not get hash rate at the pool.

Is there some setting I might try that might be specific.

Again, I am just experimenting to kill time and see if it works.

EDIT: Under Windows 7 with the exact same bat and Nvidia driver it does not find the card. Says no OpenCL device found or something like that.

Wolf0

Here is what I think you mean. Again I only have a setting of -I 8

http://s8.postimg.org/tr4ah96s5/Capture.png

Is it possible that it just was minign so slow that it never found any shares for submitting?  I seem to remember something about the nVidia cards supporting OpenCL (Even from the beginning), but they were horribly slow at it.  Post a screenshot of the thing mining?  That will show connection status and mining speeds and the like

 Here is a screen shot but something I did not notice until I put the log in the bat (thanks Wolf0). The miner shows that it is at a N-Factor 17 but here is my exact bat that I run for N-Factor 16:

yacminer --scrypt-chacha --nfmin 4 --nfmax 30 --starttime 1388949883 -d 1 -o stratum+tcp://pool:port -O xxxxxxx:x -D -l 5

http://s15.postimg.org/tm4fm0v2z/Capture.png

That's kind of interesting.  If you look at the pool line it is showing "diff 2 NF 16" but your debug output shows NFactor 17.  My miner on my system (that I know submits shares) actually shows "Nfactor: 17" in the debug output too, so that's likely inaccurate, or based on 2^NF instead of the scrypt-chacha funky math of 2^(NF+1) or something like that - it's been a while, but it's always been confusing (thanks pocopoco!).  I think you've got it working, but at that hash rate, you're likely not submitting shares, or are hitting HW errors instead of accepted shares.  

Since you did not specify buffer_size or lookup gap on the command line, the default values are going to pick ~90% of the GPU VRam it can see and a lookup-gap of 4, which is not ideal for NF=16, and is probably giving you HW errors.  What buffer size does it tell you it's allocating for the card when it starts up?  (likely need to turn debug off first)

You are correct on the look-up gap of 4 and the buffer is being set at 448. After a while of mining I do get a HW error.

If I change the starttime I get a high hash rate but all rejects.

My 270x max out at 2.2 khs on Nfactor 14...

setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_USE_SYNC_OBJECTS 1
del *bin
yacminer --scrypt-chacha  --worksize 128 -g 1 --lookup-gap 8 -R 3200 --buffer-size 1696 --gpu-memclock 1400 --gpu-engine 1000

I've tried 13.12, 14.6, and 15.3 drivers, no noticeable changes. The buffersize is the largest I can make it. Is there anything else I can play with to get more juice outta these cards? Thanks in advance.

Do not play with starttime - that is specific to the coin!  You need to work on setting the highest buffer-size you can and get a higher lookup gap going.  Stop using Intensity and use rawintensity instead I=8 is equivilent to R=256, at that lookup gap and nFactor, your -rI should be 112, so no wonder you're getting HW errors.

You really need to read the tuning guide if you want any chance at being successful
https://github.com/Thirtybird/YACMiner/blob/master/SCRYPT-README

Uncertain - I would try every lookup gap and the corresponding Raw Intensity and see which nets you the biggest hashrate.  There is a way to calculate your maximum R given buffer size and lookup gap, but I'll leave that for you to find :)  (it's published in at least 2 separate places in 2 different programming languages)

Your target to beat is 2.7 KH/sec, which my $100 R7 250 2GB card did at NF=14

I understand the -R flag is multiplicatives of the worksize. I have it at 3328. I can get the miner at 3 khs, but it crashes the driver (13.12) after a few minutes. I'll probably need to dial down the engine.

Nfactor 14 = 4Mb per hash if lookup-gap=1   and 0,5Mb if lookup-gap=8

if buffersize=1696 and lookup-gap=8 rawintensity must be = 1696/(4/8)-1 = 3391

try maximum increase buffer size first
then calculate rawintensity for selected lookup-gap

try another lookup-gap

and try this
setx GPU_MAX_HEAP_SIZE 100
setx GPU_FORCE_64BIT_PTR 1

example --lookup-gap 4 -R 1695 -B 1696

Tested yacminer with latest win 10 preview + amd driver from windows update 15.5 beta and it works just alocating memory is low 2800MB for 4GB card ... in win 8.1 no go with new drivers

I would like to mine scrypt jane N Factor and I want to know what downloads I need?  Also, what I need to use?  Like a Graphics card or a Miner like Titan?  Let me know...I Mine for a Hobbie and Haven't seen anyone mine scrypt jane N Factor as Good as you...Thanks

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?

Go with lookup-gap 6 or 7

Dosn"t work

Try buffer size 3600 -R 7600 --lookup-gap 8

Do not work... Any ideas? Please, tell me your bat file. And catalist driver is 13.12?

I had that card before,remember that settings work for me...drivers was 14.7,but 13.12 should work ok,and 8gb of system memory...ok,wait sec,isnt there on nfmin going 12,is zccoin?

Check my reply to your post in the other thread you posted this exact same problem on.

Also, make sure you're using YACMiner 3.5.0 and not 3.3.1 - they are vastly different!  You can find binaries and source at the github link in my signature

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.

One question leocoin change nfactor to 15 what I need to change beside -R, i have win 64bit 4x R9 270X Vapor 2GB and 8GB ram.

probably lookup gap too

Thanks a lot Thirtybird will try that.

Thirtybird when nfactor changes how many time speed goes down?

on example of leocoin i get from 4,5kh to 1,2kh....and still didnt menage to stay without hw

Me too man, what card do you have?

Have 280x toxic and 270x asus 4gb,..270x are great,they give also same hashrate without hw...on 280x about 10% are hw

Can you post your conf for 270x?

setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_USE_SYNC_OBJECTS 1


yacminer --scrypt-chacha --worksize 256 -g 1 --lookup-gap 7  --starttime 1402845776 -R 2280 -o stratum+tcp://leo2moon.com:3333 -u xxx  -p x --nfmin 4 --nfmax 30

Thanks man, I just need to lower -R because your cards are with 4GB and mine with 2GB.

Yeah,you right...you welcome;)

something better for 280:


yacminer --scrypt-chacha --worksize 128 -g 1 --lookup-gap 8 --starttime 1402845776 --buffer-size 2590 -R 2560

How much you get hash from that?

max 1.2 K, but I have problems on few rigs.... it do not work....

What hashrate do you get with R9 280x on scrypt nFactor (nf 14)?

Mining leo at nf15 1.215kH/s no HW...
However i wonder does Wolf0 have something better and optimized for new drivers :)

He does.  It forces 64 bit pointers, and requires some variable settings and different dll's.  It ran slower on my cards out of the box than the published kernel.  It might be different on 280x/290/290x, and cards with horsepower to spare, but that's not what I run.

It works well with n-factor 15? Or it was for n-factor 14?

either, or both.

Hi all I just downloaded the latest version but I need proper guidelines to config my batch (YacCoin with latest Yacminer )
Here it's my specs:

Windows 7 x64
GPU: XFX R9 270X overclocked with Afterburner (1200/1500/+20%)
CPU: i5 3570k STOCK Speed
RAM: 8GB Double Channel Corsair

I have Asus R 9 380 4Gb driver 14. 7, Win 7 64 bit YACMiner 3. 5. 0 boys help run miner. 3 days trying to do !! make a batch file for my card. Here is my batch file
 This is my miner photo  http://prntscr.com/axtk1a
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_USE_SYNC_OBJECTS 1
yacminer --scrypt-chacha --worksize 256 --lookup-gap 8 -g 1 --buffer-size 2656 -R 6411 -o stratum+tcp://wk9.botpool.net:4339 -u alexsm751.work1 -p x --nfmin 12 --nfmax 30 --starttime 1375817223
what needs to change? I tried to help guys !!! I've tried for three days. I am very worried
Regards, Tatiana

What coin are you trying to mine?

This batch file for ZCC coins

Sorry, I don't know about ZCC. Try to ask in ZCC topic (https://bitcointalk.org/index.php?topic=268575.0)

Excuse me, you can make a batch file for coins YAC?
yacminer --scrypt-chacha --worksize 256 -g 1 --lookup-gap 2 --buffer-size 1700 -R 1280 ?