Current Version: 2.5.1 (Jun 25, 2020) -
ChangelogSource tarball: https://github.com/pooler/cpuminer/releases/download/v2.5.1/pooler-cpuminer-2.5.1.tar.gzBinaries for Windows:https://github.com/pooler/cpuminer/releases/download/v2.5.1/pooler-cpuminer-2.5.1-win32.zip (32-bit)
https://github.com/pooler/cpuminer/releases/download/v2.5.1/pooler-cpuminer-2.5.1-win64.zip (64-bit)
Binaries for Linux:https://github.com/pooler/cpuminer/releases/download/v2.5.1/pooler-cpuminer-2.5.1-linux-x86_64.tar.gz (x86-64)
Binaries for macOS:https://github.com/pooler/cpuminer/releases/download/v2.5.1/pooler-cpuminer-2.5.1-osx64.zip (64-bit)
SHA-256 Checksums337f04fdb32f34b85819d09d59f6d3cf62991ac2e656735c43661dd3d4c57631 pooler-cpuminer-2.5.1.tar.gz
5fc7219fbb72dad32d64f11cd579383e53d8872f95309594fad2a07554a541f7 pooler-cpuminer-2.5.1-linux-x86_64.tar.gz
595ff086193ff68d8923f716757cf6ba6bbf1b761ae8786f437e2834621bebc8 pooler-cpuminer-2.5.1-osx64.zip
8d2c14b46bda27e2efc971907164f3e301253fd3a2d23f02201a1b3a2cbeb156 pooler-cpuminer-2.5.1-win32.zip
a33f6d637a71a69b21d95aa0237e9e5227da62b437e986d28d964fd5395ace37 pooler-cpuminer-2.5.1-win64.zip
$ ./minerd --url=http://myminingpool.com:9332 --userpass=my.worker:password
$ ./minerd --url=stratum+tcp://myminingpool.com:3333 --userpass=my.worker:password
For more information:
Building instructionsInstalling dependencies for building on Debian, Ubuntu and other APT-based distros:
$ sudo apt-get install make libcurl4-openssl-dev
Installing dependencies for building on Fedora, RHEL, CentOS and other yum-based distros:
$ sudo yum install gcc make curl-devel
Installing dependencies for building on OpenSUSE and other ZYpp-based distros:
$ sudo zypper in gcc make libcurl-devel
Recipe for building on Linux:
$ wget https://github.com/pooler/cpuminer/releases/download/v2.5.1/pooler-cpuminer-2.5.1.tar.gz
$ tar xzf pooler-cpuminer-*.tar.gz
$ cd cpuminer-*
$ ./configure CFLAGS="-O3"
$ make
Should I call this miner "cpuminer" or "minerd"?
A: The software package is called "cpuminer". "minerd" ("miner daemon") is just the name of the executable file provided by the package.
Q: My antivirus flags the Windows binary as malware.
A: That's a known false positive. More information
here.
Q: When I click on minerd.exe a black window flashes up and then disappears.
A: This is a command-line application, it has no graphical interface. You'll need to learn how to use the command line interface (CLI) of your operating system first.
Q: Can I mine
(insert your cryptocoin here) with this miner?
A: Only if its proof-of-work algorithm is scrypt or SHA-256d. This miner does
not currently support other algorithms such as Keccak, scrypt-jane, X11, etc. Forks of this project may provide additional algorithms, but I do not maintain them and they are not discussed here, so if you have questions about them please contact their authors.
Q: When running
configure I get the error "C compiler cannot create executables".
A: Make sure you typed
CFLAGS="-O3" with a big O, not with a zero.
Q: autogen.sh dies with "error: possibly undefined macro: AC_MSG_ERROR".
Q: configure chokes on something like "LIBCURL_CHECK_CONFIG(, 7.15.2, ,'".
A: Make sure you have installed the development package for libcurl. If you have and you're still getting the error when compiling from git, try compiling from tarball instead.
Q: I'm trying to connect to a Stratum server, but I get "HTTP request failed: Empty reply from server".
A: Make sure you specified the correct protocol in the server URL (
stratum+tcp://).
Q: Is there any command-line option I can play with to make it mine faster?
A: No. The miner automatically picks the best settings for the CPU it is run on.
Q: What's the difference between the two algorithms,
scrypt and
sha256d?
A: They are completely different proof-of-work algorithms. You must use
scrypt for Litecoin, and you must use
sha256d for Bitcoin. The default algorithm is
scrypt, so for Bitcoin mining you have to specify
--algo=sha256d.
Q: Will this miner use a lot of RAM when using the scrypt algorithm?
A: No, that's a GPU thing.
Q: How do I make the miner write its output to a file instead of printing it to the screen?
A: Just redirect the standard error stream to file:
minerd [OPTIONS] 2> myfile
You may also want to use the
--quiet/
-q option to disable the per-thread hashmeter.
On *nix, you probably also want to use the
--background/
-B option to fork in the background.
Original post (December 19, 2011) follows. Please note that most of the technical details are now outdated.
I have recently rewritten the heart of the scrypt hashing function used by the jgarzik/ArtForz cpuminer in assembly language, to see if this could bring some more speed. Apparently it did.
The source code is now available at GitHub:
https://github.com/pooler/cpuminerThe build process for Linux should be the same as before.
In the new code I tried to take full advantage of SSE2 instructions, which are available since the Pentium 4. Unfortunately, AMD's implementation of these instructions is not as fast as Intel's... well, ok, sadly it's nearly two times slower. For this reason, I had to write separate versions of the hashing functions. You don't need to worry about this, though, since the new function should be able to auto-detect your cpu and automatically select the best algorithm.
Long polling patchThis release also includes a new --timeout option that I originally added to solve a problem with long polling. Apparently the LP thread doesn't behave nicely under certain network conditions, as reported by various users. So, if you experienced high stale rates with the previous miner, you should definitely try out this new version.
Many thanks to SockPuppet, aka shawnp0wers, who helped me nail down the issue!
Some Technical DetailsThe current release includes four different implementations of the scrypt core, each one designed for a different hardware.
- A fallback plain x86 version, to be used when SSE2 instructions are not available (Pentium III, Athlon XP and earlier processors).
- A 32-bit version using SSE2, for use on the Pentium 4, Pentium M, Core, Atom, plus all 64-bit cpus running in a 32-bit OS.
- A 64-bit version for Intel processors, i.e. Core 2, i3, i5, i7. This version can in most cases double the speed of the previous miner.
- A 64-bit version for AMD processors, i.e. Athlon 64, Phenom, Sempron and the like. The speed increase here can range from 5% to 80%.
The first two versions only get compiled in the 32-bit miner, the last two only in the 64-bit miner. The miner uses the CPUID instruction to choose which version to use.
Compiler FlagsOne cool aspect of assembly code is that users no more need to play with compiler flags to get the best performance. Configuring the build with just CFLAGS="-O3" is now more than enough to get efficient code. This also means that we no more need separate specialized binaries for Intel and AMD cpus. Just a 32-bit and a 64-bit version.
Final NotesSomeone on IRC asked me why I am releasing this miner, instead of keeping it for myself or for my pool. Well, that's exactly the point. It is important for Litecoin that everybody has access to the most efficient mining software!
Someone might worry about the effect of this release on market prices, but consider this: if everybody starts using the new miner, the hash rate will go up, but so will difficulty, so nothing will ultimately change. I actually think this new miner will be very beneficial to Litecoin, because it should make mining easier for beginners (see compiler flags).
As crazy_rabbit wrote in another thread, one big plus of Litecoin is that everybody can participate. Well, consider this: now you can effectively mine on an Atom!
Alright folks... I hope you enjoy the performance boost. Consider this as my Christmas present to the community!
Show Posts
