T12x32 is way to big for scrypt-jane. That's what you should use on regular scrypt coins. For yacoin that kind of config would require something like 50GB of GPU ram.
Autotune is not perfect. Look at the chart (run with -D to show debug info) then try configs that are just outside the populated area of the chart, until you've explored all the edges and found your limits. When you go too far it will print something like this: "GPU #0:Launch config 'T11x2' requires too much memory!"
I'm using T20x1 on my 780 and getting 3.4 kHash. T10x2 works well for me as well.
Thanks for the tips. I've tried some but T10x1 seems to be the best still. T20x1 doesn't perform well at all on my 780 - only 1.2 kH/s :\
Driver issue maybe? Running 331.92 here.
I'm running OS 10.9 on a hackintosh, so I don't know that I can help you out there. Although I did try it out on two gtx 670s at work today and they got 2 kH/s each with autotune with 331.20 on Linux. Are you running CUDA 5.5?
For those of you attempting to hash QQC or YBC or any other scrypt-N coin... you're probably going to need to modify some code and recompile. It looks to me like the time value used to calculate the N is hardcoded to Yacoin's start time. See GetNfactor() in scrypt-jane.cpp. edit: just reread the last two pages and I see that some of you have already done that. doh
Can someone please explain this to me? It looks contradictory.
-C, --texture-cache comma separated list of flags (0/1) specifying which of the CUDA devices shall use the texture cache for mining. Kepler devices will profit.
This says kepler devices will profit.
GPU #0: GeForce GTX 770 with compute capability 3.0
GPU #0: the 'K' kernel ignores the texture cache argument
My 770 is a kepler device, but cudaminer says that my kernel ignores the texture cache...
So which is it and how will my device profit from a launch option which is ignored?
Are you using the latest version from git or a binary release? I see a commit message on Dec 28th that says "add back support for chunked memory allocation and texture cache to Kepler kernel. Slight speed-ups with -C 1 are seen." which implies he removed it at one point, possibly when upgrading to CUDA 5.5.
I cant use all my vram either. cbuchner1 what setring are you using to get 3.2kh/s? And is it using all available memory?
I just checked my yacoin. What is immature? I have 99.88 immature yacoins over night. Well in 5 hours but I dont know what it means
My yacoin config.
./cudaminer -u coercion.1 -p x -a scrypt-jane -o 127.0.0.1:9942 -l T21x1 -H 1
I just realized I can't run 21x1 since I pulled today. I ran that config all last night and now I can only run T20x1.
Immature means you can't spend them yet because they need to be included in more blocks so a fork doesn't screw you or anyone you transact with.