sry, didnt read last 30 pages of thread, but..

anyone still on keccak mining?

seems that last WHQL driver 334.89 almost destroyed remains of performance on mine gtx 550ti

at -l F1536x16 -L 256 earlier it was about 39MHash, and now on same settings, same pool (tried different pools btw) it gives just about 16 MHash

:sadtrombone.wav:

So my 3 ASUS ROG MARS cards with 2 GTX 760 chips on one PCB arrived.

Album link here!

Some impressions:
-cool red blinking MARS logo on top. Even cooler than the GTX 780 TI's.
-nice metal back plates, but the plates do take space and so the air convection in the narrow space between adjacent cards is degraded.
-nvidia-smi under Linux (hacked with nvml_fix) shows a TDP limit of 214W per GPU. REALLY?! That's then 428 W per card.

....

Christian

I know it is not really the place to ask that, but is there an "official" cgminer (or equivalent) since the original dev dumped support for gpu ? (for the moment the only thing which look serious is vertminer... for the rest it just seems everyone are doing their own business without caring about what the others do... what a mess... lol).

Don't mind the username, it's been edited.
I call a bug where it gets stuck sometimes for hours without any accepts, rejects or anything.

Is there anything I can do myself to fix this or is it a bug with cudaminer?

Launch command:
cudaminer-2014-02-09\x64\cudaminer.exe -a keccak -i 1 -l K1152x28 -L 512 -o stratum+tcp://maxpool.1gh.com:17333 -O 123:x -D
https://dl.dropboxusercontent.com/u/54281287/cudaminer_4.PNG
https://dl.dropboxusercontent.com/u/54281287/cudaminer_5.PNG
It seems to get stuck like this a lot.

I'm mining MaxCoin with 1GH.com using Cudaminer, and I have an NVIDIA Quadro 4000 graphics card that I'm using. Oh, and I'm on a windows 7, 64 bit computer. Things seem to be working, but I want to be sure that I'm not potentially burning up my graphics card.  I originally set my connection string set to:

cudaminer.exe -H 1 -l F512x16 -a keccak -o stratum+tcp://maxpool.1gh.com:17333/ -u account -p password

Later I replaced F512x16 to F256x16 to see if it would run cooler.  The hash rate changed to about 27750 khash/s, but the temperature stayed exactly the same.  Usage changed from 97% to 95%.

Oh, one thing, I get an 'error message when it first starts up that  says "Given launch config 'F256x16' requires too much memory.  But then it goes ahead and starts running anyway with those parameters.  I do get that message with almost every configuration I've tried.  It only disappeared when I set it to F16x16, which was depressingly slooooooowwwwwwwwww.
.....
.....
Can someone who understands this stuff tell me if I'm within a good range to maintain optimal performance while keeping my graphics card in good shape???  Or am I risking wearing it out?  Is there a more appropriate setting for my graphics card that I could be certain would not overtax it, but still maintain a good hash rate?

Also, I've been letting the program run pretty consistently all day (probably over 16 hours I think), and I've only earned 0.16 MAX.  That seems kind of low, doesn't it? 

I am currently eyeing the Asus GTX 760 Mars dual GPU cards. It would allow me to run six mid range nVidia GPU cores in one mainboard, taking three double width slots. Hmm....

My second dedicated mining rig currently has an ugly hodge-podge of cards on it.

Christian

what is your config in .bat file?

EDIT: and which coin are you mining?

Maybe we'll move this to its own topic? Lets wait and see for a while how this takes off.

i won't be doing any prime number based coins in cudaminer. Too hard. I've got a life, you know ;-)

So.. Any takers?

Can't get the cudaminer-2014-02-04.zip to download from mega - any other (trustworthy) hosts?

I figured I'd throw another one into the mix (a bit simpler than the other ones):

One more tip for the latest maxcoin build.

For the kernel launch configuration: Take the total number of CUDA cores on your card, multiply by 2, and append x32 for the K kernel and x16 for the F kernel. Don't bother with the T kernel for the moment.

This should give somewhat higher performance than the original 1000x32 or 1024x32 configurations suggested in the README, especially on the biger cards like GTX 660Ti, GTX 780, etc...

Use -L 512 with these huge launch configurations or out of memory is guaranteed. But on the other hand, these out of memory errors don't prevent keccak hashing (the program just continues...). Cleaning up these unnecessary memory allocations would be the next item on my "finish the keccak feature" TODO list.

Christian

Compiled for what OS?