Topic: [ANN] cudaMiner & ccMiner CUDA based mining applications [Windows/Linux/MacOSX] - page 796. (Read 3426976 times)

interesting... a drop in performance =(

For me it worked, but resulted in poorer performance than 5.5.

Fan speed 44%? Put her to to the 'max'

I guess i should have asked which Panda coin he was talking about... The old or the new "scamcoin".

Edit: Either way, i don't think either of them are profitable. (That's my opinion)

No.

The one you linked is descibed as a "Scamcoin" released by woolong according to the panda coin thread https://bitcointalksearch.org/topic/annpand-originalrare-pandacoin-coinedupcryptorushswisscexopenex-399127 .   Page 33 for specifics.  The exchanges don't match up and the official forums say "PAND".

has anyone tried compiling with cuda 6.0 yet?

I think your earning is in the ball park given current difficulty.

Is anyone having problems with Maxcoin and cudaminer? I seem to be hashing but have tried 3 different pools with no success. My ATI cards and cgminer are all having their shares counted, so I know it's not the pool, I don't think.

Question, with cudaminer the acknowledgement of shares being made just reads out the hash speed right? doesn't say diff/accepted shares etc.?
This is normal yes?
Thanks!

I'm mining doge right now, and using cudamanager to run cudaminer (don't know if that has any bearing,) but the last two days, I've come home to this:


If I stop and restart the miner, it acts normally. My config looks like this:
cudaminer.exe -l K4x32 -m 1 -i 0 -H 1 -o stratum+tcp://stratum.rapidhash.net:3333 -O user.miner:password
The miner had been running for over 22 hours when I got home to this at 8pm. I'm running an i3-4130 with 8GB RAM on Windows 7 x64, using the 64-bit cudaminer 2014-2-4

That is the wrong Pandacoin.

The correct one has the tag "PANDA" not "PAND".

They can be found here:
https://cryptorush.in/index.php?p=trading&m=PANDA&b=BTC
and here:
https://cryptx.io/home

(Not doing to ask for donations because we should be helping each other out!)
Christian on the other hand deserves it. Feel free to donate to him.

I posted this in the 1gh.com thread, and someone recommended I ask my question here:

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.

I'm getting what I think is decent performance, I think... but not earning much in the way of maxcoins...seems to take a lot of effort just to earn tiny fractions.  

The command window indicates that hashes seem to average around 28280 khash/s unless I start doing stuff on my computer, then it gets slower.  Anyway, the temperature seems stable around 77 to 78 degrees, and it is operating at the gpu stated upper limits.  I'm getting quite a few yays, and only an occasional boo.  Here is a link to a screen shot of the command window and gpu z.

https://drive.google.com/file/d/0B1E0rFsXEmnBVDh6aWlGSVEzZk0/edit?usp=sharing

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?  

Also, while I'm here, I'm new to mining, and I'm trying to figure out how to set cudaminer to solo mine maxcoin.  The directions I've found are confusing at best.  Does anyone know of any clear, easy-to-understand, simplified setup instructions for a newbie like me?  If so, could you direct me to them?  If not, would you be a dear, and maybe explain it to me in terms I might understand?

Would appreciate your thoughts.

Thanks

Katherine

You might find it best to add additional nodes if they are listed for your particular wallet. Generally this are called "Super Nodes" these are the suggested nodes to work with. It looks like their is only on listed super-node currently.

84.251.34.142:44444

If you continue to have connection issues it may be better to pool mine as the work units are going to be smaller and connections tend to be a bit better managed.

Thank you, that's what I was afraid of. I guess it would be better not to have shut down cudaminer there.

means that your wallet may have lost the connection to the network, possibly when your miner was ready to submit some found block.

in such a case, the wallet responds to all requests with a 500 error code

Christian

When solo mining MRC for the last few hours I have gotten a couple of "submit_upstream_work json_rpc_call failed" errors (screen grab here: http://imgur.com/C2ekgAN ) which force me to restart cudaminer. I have the microCoin wallet open, but haven't mined any blocks. Does this message mean that I found a block but can't send it to the network?

Sure too expensive now but if you picked it up on or before black friday it could be had for $550. It doesn't consume that much more power than the R9 290. Especially when you take into account the hash/watt it almost comes out even. Undervolt and underclock if you want to match a 290.

-L2   377+180+185=742 khash/s (much less!)
-L3   270+140+147=557 khash/s (even less)

-b2048  531+246+263=1040 khash/s (pretty close, but still a little less)
-b8192  525+246+263=1034 khash/s (again, not much difference, but less)

1. I've only been mining with Nfactor=9 (N=1024). Does that change much, will it affect the optimal settings?
2. getmininginfo in the microcoin wallet always returns 0. Does anyone know how to see total network hashes/s?

Also consider running cudaminer with a 30 minute time limit, in a script that restarts it over and over. This will make it recover from GPU faults...

You can define a log rotation job with logrotate and specify a max file size. http://linux.die.net/man/8/logrotate

Logrotate is a daily cron, though it can be moved to be performed at other frequencies, hourly for example. If I were going to rotate cuda logs I would probably add my own hourly cron rather than modifying logrotate. I think both solutions would present problems if the process maintains an open file descriptor (like it does for stdout, and using > to redirect just redefines stdout) and never gets restarted.

A simple bash script could automatically trim files. Check line count with `wc -l`, if it's above your limit do `tail -n ` and redirect that back to the log, but it will currently do funky things if the file is open/being used by cudaminer. Using that method with a bash redirect will fill the file with 0s (or potentially random data) up to the file seek position maintained by the process. Redirecting the tail into a second file and replacing the first with the second is also no good, you'll stop getting output, but the process still has a fd so the system is still keeping track of a file and potentially writing data to disk, just not to any files you can actually see without mucking through /proc.

Adding an argument for log outputs would go a long way to fix this, but there are a few ways it could actually be handled. Honestly the easiest method (or my impression of the easiest, which is likely naïve as I'm a computer architecture hacker not a sys admin) would be to implement log rotation into cudaminer. Write a wrapper for the logging function, check the seek position (or file size, but that might be more costly), if it's above the limit do a bit of file manipulation (copy the file and reset seek or rename the file and open a new fd).

I'm probably just missing a simpler solution, but I'm a C programmer with a bad habit of reinventing the wheel.

I'm mining microcoin as well, on a pair of GTX770s.  Does the -L 1 -b 4096 make much of a performance difference?  I am getting about 350 KH/s per card.   I'm at work so I can't test it until I get home.  Just wondering if I should make any change.