Thanks, coblee. I've compiled it and am running the new litecoind version on my p2pool node. Took like 30-40 minutes to load! But, now that it is loaded it seems to be running smoothly.
What to do now with the very large .dat files? Are they part of litecoin forever or can they be purged?
addr.dat and debug.log can be safely removed. (But stop the client first!) |
|
|
|
I wish minerd had a backup pool option!
That's actually pretty easy to implement using a wrapper script. Here's a very basic example: https://gist.github.com/2053044This is just a very simple example that makes the miner fail over to a different pool if the current one fails a given number of times. Using commands such as timeout you can implement all the strategies you want. The possibilities are endless. I'm sure there must be a way of doing that on other operating systems, too. |
|
|
|
Pooler, is the lack of reaper v13 having long polling hurting you at all with the increased stales?
Yes, of course. Long polling is crucial to reduce the number of stale shares to a minimum. My reaper client has been getting an average of 350kh, but my account is only reading it as 250kh?  ?? Are there any problems with litecoinpool and reaper since the client is getting such high rates now? Remember that speed estimates are computed over the last 10-15 minutes; is it possible that you didn't wait long enough for the estimate to settle? |
|
|
|
UPDATE! NOW WITH C&C ABILITIES!
Great! I've always wanted to play Command & Conquer while mining!  |
|
|
|
@pooler Thanks for the helped! What to do for the next step? I seen the Installation Instructions(install.txt) but couldn't process 'make' after this: ./configure CFLAGS="-O3"
checking build system type... i386-apple-darwin10.8.0
<snip>
checking for gcc... no
checking for cc... no
checking for cl.exe... no
configure: error: in `/Users/bitbird/cpuminer-2.1.5':
configure: error: no acceptable C compiler found in $PATH
See `config.log' for more details Well, it looks like you're missing the C compiler. Unfortunately I don't know much about how things work on Macs, so I'll let someone else help you there. In the meantime, have you tried using one of the precompiled binaries? |
|
|
|
Don't know how to setup it on my Mac OS 10.6..  ./autogen.sh
./autogen.sh: line 8: aclocal: command not found You don't need to build from the git repo, there's a tarball available. |
|
|
|
Clearly updating the miner in the GUI is a little more involved than dumping the latest version of pooler into the folder and let-er rip, any ideas?
Depends on what's been changed. In most cases it should work just like that. I'm pretty sure I did not change the output format in the latest release, so the GUI should work with 2.1.5. I tested it briefly on Linux and it seems to work. |
|
|
|
Hey guys, I'm mining LTCs woth the standard Litecoin Wallet with the 2.1.4 cpuminer "minerd.exe" and its dll libraries in the wallet directory, I have an AMD phenom x6 1090t@3.4 ghz and the maximum hashing speed I can reach is 17 kh/s, on Win7 32bit. Do you think it's a fair value? Upgrading to 64bit win7 could help me reaching an higher hashing speed?
Using a 64-bit you would probably be able to double that hash rate. My Phenom X6 @ 3.5 GHz does about 39 kh/s. |
|
|
|
A Mac OS X 10.7 binary is now also available, thanks phraust! |
|
|
|
As was heralded by aaa801, here is Version 2.1.5- New optimizations for Sandy Bridge (recent Intel processors) and Bulldozer (AMD FX series). The speedup should range from 25% for Intel to 45% for AMD, but only in 64-bit mode.
- Building on Windows should now be possible without having to perform satanic rituals.
- Building on Solaris using gcc should now work out of the box. (Thanks to pontius!)
The source code is, as always, available at GitHub. Binaries will be available soon available here. Many thanks go to aaa801, shakti, and xurious for letting me use their CPUs during the development process!  |
|
|
|
I think the OP is right when he says that another thread was needed. Coblee's thread was intended for discussion on Litecoin development. Yet it is getting "spammed" with too many "I can't get the GPU miner to work, what should I do?" posts, that don't belong in there. |
|
|
|
Do any of the current LTC miners work with Fedora, Debian and ArchLinux?
Is that a rhetorical question? If it is not, the answer is yes, cpuminer should work on pretty much all Linux distros. It even works on Solaris/SPARC, I think that's enough said.  |
|
|
|
does 8.04 khash/s(like 2khash/s per thread) look right for an opeteron 2374HE @ 2.2ghz? just hopeing i didnt do something wrong in the compile
Being based on the K10 microarchitecture ( specs), that processor should be able to do about 16 kh/s in 64-bit mode. If you're in 32-bit mode, I'd say 8 kh/s is fine. |
|
|
|
Current algorithm is:
1) Calculate B = SHA256(A)
2) Calculate C = scrypt(B)
3) Calculate D = SHA256(B, C)
4) Return D
Not really. SHA256 is part of scrypt. The sequence looks more like this: 1) PBKDF2 using HMAC-SHA-256 2) Memory-hard mixing loop using salsa20/8 3) PBKDF2 using HMAC-SHA-256 Something I've wondered:
Why are you using N=1024, r=1, and p=1 for scrypt? Why didn't the recommended values from the paper, N=1024, r=8, p=1 get used?
If I remember correctly, ArtForz said that the parameters (1024, 1, 1) resulted in a lower GPU/CPU performance ratio. Some analysis by him can be found here: https://bitcointalk.org/index.php?topic=45849.0What looks interesting is that they still claim the SC2 algorithm to be GPU-resistant. I'm not at all convinced. Any technical opinion on this? |
|
|
|
|
Show Posts
