[LOCKED] cpuminer-opt v3.12.3, open source optimized multi-algo CPU miner

[adamantasaurus]

Hey All,

I downloaded the windows binaries but when I extract it and then open any of the cpuminer app files nothing happens a window opens for one second and then closes how do I get this miner running?

Thanks

[spider703]

Hey All,

I downloaded the windows binaries but when I extract it and then open any of the cpuminer app files nothing happens a window opens for one second and then closes how do I get this miner running?

Thanks

cpuminer-aes-avx -a m7m -o stratum+tcp://m7m.mine.zpool.ca:6033 -u 1J6ERS9LjhRhXkifkVfdpbP56aY7TLqEoe -p x -t 4
t4 - this 4 core

[joblo]

A pull request has been received to change the dockerfile.

There are 2 changes, one to address an issue with line continuation, but also a change that claims to
reduce the image size.

Since I know very little about docker I defer to the community for review of the change. If there are any
concerns with the change, please raise them. If there are no objections the changes will be included in
the next release.

https://github.com/JayDDee/cpuminer-opt/pull/41

[NameTaken]

A pull request has been received to change the dockerfile.

There are 2 changes, one to address an issue with line continuation, but also a change that claims to
reduce the image size.

Since I know very little about docker I defer to the community for review of the change. If there are any
concerns with the change, please raise them. If there are no objections the changes will be included in
the next release.

https://github.com/JayDDee/cpuminer-opt/pull/41

The Docker image could be smaller by using Alpine Linux as the base. Alpine uses libressl by default but also have openssl-1.0.2 in its repo so I'm not sure about any impact on performance.

[filoozom]

A pull request has been received to change the dockerfile.

There are 2 changes, one to address an issue with line continuation, but also a change that claims to
reduce the image size.

Since I know very little about docker I defer to the community for review of the change. If there are any
concerns with the change, please raise them. If there are no objections the changes will be included in
the next release.

https://github.com/JayDDee/cpuminer-opt/pull/41

The Docker image could be smaller by using Alpine Linux as the base. Alpine uses libressl by default but also have openssl-1.0.2 in its repo so I'm not sure about any impact on performance.

Yes, it could, but didn't quite manage to compile it on alpine yet. If you have more info, please share!

Just for info, this image with the multi-stage build process is 55Mb compressed compared to 160Mb for all other images on Docker Hub.
You can try it easily over here: https://hub.docker.com/r/filoozom/cpuminer-opt/

[NameTaken]

A pull request has been received to change the dockerfile.

There are 2 changes, one to address an issue with line continuation, but also a change that claims to
reduce the image size.

Since I know very little about docker I defer to the community for review of the change. If there are any
concerns with the change, please raise them. If there are no objections the changes will be included in
the next release.

https://github.com/JayDDee/cpuminer-opt/pull/41

The Docker image could be smaller by using Alpine Linux as the base. Alpine uses libressl by default but also have openssl-1.0.2 in its repo so I'm not sure about any impact on performance.

Yes, it could, but didn't quite manage to compile it on alpine yet. If you have more info, please share!

I just tried compiling but got the error

Code:

In file included from algo/echo/aes_ni/hash.c:21:0:
algo/echo/aes_ni/vperm.h:53:7: note: called from here
  x  = _mm_shuffle_epi8(*((__m128i*)table + 0), x);\
       ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
algo/echo/aes_ni/hash.c:385:4: note: in expansion of macro 'TRANSFORM'
    TRANSFORM(_state[i][j], _k_opt, t1, t2);
    ^~~~~~~~~
In file included from algo/echo/aes_ni/vperm.h:20:0,
                 from algo/echo/aes_ni/hash.c:21:
/usr/lib/gcc/x86_64-alpine-linux-musl/6.4.0/include/tmmintrin.h:136:1: error: inlining failed in call to always_inline '_mm_shuffle_epi8': target specific option mismatch
 _mm_shuffle_epi8 (__m128i __X, __m128i __Y)
 ^~~~~~~~~~~~~~~~
In file included from algo/echo/aes_ni/hash.c:21:0:
algo/echo/aes_ni/vperm.h:52:5: note: called from here
  t1 = _mm_shuffle_epi8(*((__m128i*)table + 1), t1);\

algo/echo/aes_ni/hash.c:385:4: note: in expansion of macro 'TRANSFORM'
    TRANSFORM(_state[i][j], _k_opt, t1, t2);
    ^~~~~~~~~
source='algo/hodl/aes.c' object='algo/hodl/cpuminer-aes.o' libtool=no \
DEPDIR=.deps depmode=none /bin/sh ./depcomp \
gcc -DHAVE_CONFIG_H -I.  -Iyes/include -Iyes/include -fno-strict-aliasing  -I. -Iyes/include -Iyes/include -Wno-pointer-sign -Wno-pointer-to-int-cast   -g -O2  -Iyes/include -Iyes/include -c -o algo/hodl/cpuminer-aes.o `test -f 'algo/hodl/aes.c' || echo './'`algo/hodl/aes.c
make[2]: *** [Makefile:2491: algo/echo/aes_ni/cpuminer-hash.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: Leaving directory '/cpuminer-opt'
make[1]: *** [Makefile:3506: all-recursive] Error 1
make[1]: Leaving directory '/cpuminer-opt'
make: *** [Makefile:665: all] Error 2

[v3t3r4n0]

Hello guys. I am a domestic miner and I live in Brazil - Rio de Janeiro. My English is not very good. Congratulations Mr. Joblo for the excellent work with the multi-algorithm mining. I am a GNU / Linux Debian user. cpuminer-opt works perfectly on Debian and I'm very satisfied. I recently bought a PC with the AMD Ryzen 7 1700 processor. I intend to do some testing on Windows 10. I would like an orientation. There are 5 executable files in the Windows binary package. To perform the XMR mining and not underutilize the performance of my AMD Ryzen should I test each of the executables and check the performance or would one of you recommend me a specific executable? I thank you all.

[joblo]

Hello guys. I am a domestic miner and I live in Brazil - Rio de Janeiro. My English is not very good. Congratulations Mr. Joblo for the excellent work with the multi-algorithm mining. I am a GNU / Linux Debian user. cpuminer-opt works perfectly on Debian and I'm very satisfied. I recently bought a PC with the AMD Ryzen 7 1700 processor. I intend to do some testing on Windows 10. I would like an orientation. There are 5 executable files in the Windows binary package. To perform the XMR mining and not underutilize the performance of my AMD Ryzen should I test each of the executables and check the performance or would one of you recommend me a specific executable? I thank you all.

You answered your own question, use the fastest one that doesn't crash. In the case of Ryzen it should be AES-AVX2.
However, none of the builds can take advantage of SHA acceleration on supported algos, you need to compile on Linux to get that.

[felixbrucker]

A pull request has been received to change the dockerfile.

There are 2 changes, one to address an issue with line continuation, but also a change that claims to
reduce the image size.

Since I know very little about docker I defer to the community for review of the change. If there are any
concerns with the change, please raise them. If there are no objections the changes will be included in
the next release.

https://github.com/JayDDee/cpuminer-opt/pull/41

LGTM

[kicherkarl]

I just want to share my little test results.

algo: lyra2z
CPU: Ryzen 1800x stock settings
options: -t 16

AVX: 600 kH/s, 67°C
AVX2: 852 kH/s, 72°C

Is there any overview over the options? Or where can I find them in code?
at which temperatures are you mining?

[joblo]

I just tried compiling but got the error

Code:

In file included from algo/echo/aes_ni/hash.c:21:0:
algo/echo/aes_ni/vperm.h:53:7: note: called from here
  x  = _mm_shuffle_epi8(*((__m128i*)table + 0), x);\
       ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
algo/echo/aes_ni/hash.c:385:4: note: in expansion of macro 'TRANSFORM'
    TRANSFORM(_state[i][j], _k_opt, t1, t2);
    ^~~~~~~~~
In file included from algo/echo/aes_ni/vperm.h:20:0,
                 from algo/echo/aes_ni/hash.c:21:
/usr/lib/gcc/x86_64-alpine-linux-musl/6.4.0/include/tmmintrin.h:136:1: error: inlining failed in call to always_inline '_mm_shuffle_epi8': target specific option mismatch
 _mm_shuffle_epi8 (__m128i __X, __m128i __Y)
 ^~~~~~~~~~~~~~~~
In file included from algo/echo/aes_ni/hash.c:21:0:
algo/echo/aes_ni/vperm.h:52:5: note: called from here
  t1 = _mm_shuffle_epi8(*((__m128i*)table + 1), t1);\

algo/echo/aes_ni/hash.c:385:4: note: in expansion of macro 'TRANSFORM'
    TRANSFORM(_state[i][j], _k_opt, t1, t2);
    ^~~~~~~~~
source='algo/hodl/aes.c' object='algo/hodl/cpuminer-aes.o' libtool=no \
DEPDIR=.deps depmode=none /bin/sh ./depcomp \
gcc -DHAVE_CONFIG_H -I.  -Iyes/include -Iyes/include -fno-strict-aliasing  -I. -Iyes/include -Iyes/include -Wno-pointer-sign -Wno-pointer-to-int-cast   -g -O2  -Iyes/include -Iyes/include -c -o algo/hodl/cpuminer-aes.o `test -f 'algo/hodl/aes.c' || echo './'`algo/hodl/aes.c
make[2]: *** [Makefile:2491: algo/echo/aes_ni/cpuminer-hash.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: Leaving directory '/cpuminer-opt'
make[1]: *** [Makefile:3506: all-recursive] Error 1
make[1]: Leaving directory '/cpuminer-opt'
make: *** [Makefile:665: all] Error 2

This could be CPU related, especially if it's an AMD, and even worse an old AMD. I have found that many strange compile errors
with SIMD intrinsics are due to architecture issues where the intrinsic isn't recognized as such and gets "implicitly declared" at compile
time assuming type int instead of __m128i. After that any reference to the intrinsic causes the compiler to spit out strange error messages.
You can confirm this is you find previous implicit declaration warnings related to SIMD intrinsic functions.

[joblo]

A pull request has been received to change the dockerfile.

There are 2 changes, one to address an issue with line continuation, but also a change that claims to
reduce the image size.

Since I know very little about docker I defer to the community for review of the change. If there are any
concerns with the change, please raise them. If there are no objections the changes will be included in
the next release.

https://github.com/JayDDee/cpuminer-opt/pull/41

LGTM

Then it's good enough for me. It will be included in the next release but might be merged in git before then
as there are no immediate plans for a new release.

[stevascha]

hi joblo, how to use hyperthreading in v3.7.2? especially ivybridge

[cappy176]

Hey guys so Im trying to run the miner but with every cpuminer sse aes sse42 etc etc. It crashes after a few seconds says cpuminer is not responding and closes my .bat file like it froze does anyone know what I can do to fix this?

Also I'm trying to mine using an old acer desktop with windows 10 and AMD cempron 145 processor 2.80 ghz if that info helps?

Thank you

[4ward]

Hey guys so Im trying to run the miner but with every cpuminer sse aes sse42 etc etc. It crashes after a few seconds says cpuminer is not responding and closes my .bat file like it froze does anyone know what I can do to fix this?

Also I'm trying to mine using an old acer desktop with windows 10 and AMD cempron 145 processor 2.80 ghz if that info helps?

Thank you

Legacy version 3.5.9.1 May provide better performance on some algos with older CPUs that
don't have AES NI. Most users should not use it.

Your cpu doesn't support AES, so try the legacy version

[joblo]

Hey guys so Im trying to run the miner but with every cpuminer sse aes sse42 etc etc. It crashes after a few seconds says cpuminer is not responding and closes my .bat file like it froze does anyone know what I can do to fix this?

Also I'm trying to mine using an old acer desktop with windows 10 and AMD cempron 145 processor 2.80 ghz if that info helps?

Thank you

Legacy version 3.5.9.1 May provide better performance on some algos with older CPUs that
don't have AES NI. Most users should not use it.

Your cpu doesn't support AES, so try the legacy version

Thanks for pitching in helping new users. Your close this time but not quite correct.

The legacy version doesn't help with incompatible CPUs, it just provides a little better performance on compatible non-AES CPUs.

The real problem is described in the errrata section in the OP but was not included in the README.txt included with the Windows
binary package. It will be added in the next release. Here it is:

AMD CPUs older than Piledriver, including Athlon x2 and Phenom II x4, are not
supported by cpuminer-opt due to an incompatible implementation of SSE2 on
these CPUs. Some algos may crash the miner with an invalid instruction.
Users are recommended to use an unoptimized miner such as cpuminer-multi.

Also it's a Sempron which, like Intel's Celeron, has fewer features than the high end CPUs of the same vintage.

The bottom line is the CPU is not compatible with cpuminer-opt.

[lncm]

I'm using precompiled windows binaries with a Ryzen 7 1700, trying to mine Verium.

My bat file starts with cpuminer-aes-avx2 -a scrypt:1048576 -o stratum+tcp://eu2.poolinat0r.com:7103

However, it only uses SSE 2 as far as I can see.



What am I doing wrong?

Where can I download precompiled binaries optimized for ryzen?

Thanks.

[4ward]

I'm using precompiled windows binaries with a Ryzen 7 1700, trying to mine Verium.

My bat file starts with cpuminer-aes-avx2 -a scrypt:1048576 -o stratum+tcp://eu2.poolinat0r.com:7103

However, it only uses SSE 2 as far as I can see.



What am I doing wrong?

Where can I download precompiled binaries optimized for ryzen?

Thanks.

because the algo supports only sse2

[lncm]

I'm using precompiled windows binaries with a Ryzen 7 1700, trying to mine Verium.

My bat file starts with cpuminer-aes-avx2 -a scrypt:1048576 -o stratum+tcp://eu2.poolinat0r.com:7103

However, it only uses SSE 2 as far as I can see.



What am I doing wrong?

Where can I download precompiled binaries optimized for ryzen?

Thanks.

because the algo supports only sse2

Oh, I see. Is this the correct algo, then?

I'm asking because my old Xeon E5645 with v3.4.6. gives me almost double H/s per core than my Ryzen 1700, so I guess something is wrong.

[4ward]

I'm using precompiled windows binaries with a Ryzen 7 1700, trying to mine Verium.

My bat file starts with cpuminer-aes-avx2 -a scrypt:1048576 -o stratum+tcp://eu2.poolinat0r.com:7103

However, it only uses SSE 2 as far as I can see.



What am I doing wrong?

Where can I download precompiled binaries optimized for ryzen?

Thanks.

because the algo supports only sse2

Oh, I see. Is this the correct algo, then?

I'm asking because my old Xeon E5645 with v3.4.6. gives me almost double H/s per core than my Ryzen 1700, so I guess something is wrong.

Yes, thats the correct algo from what i remember.
And the speed might depend on instruction implementation in the processor, hyperthreading, core speed and cache size.
I don't know how much the specific algo benefit from each of those, but it might be logical

On some algos i get higher hash rate on core i7-6700@3.4GHz probably due to HT and larger cache, while some are faster on core i5-7600@4.5Ghz due to higher clock