hi, just a report on notebook haswell cpu (4700MQ @ 3.4ghz 47W) with espers mining (hmq1725)
v3.3.x-v3.3.8 Start mining with AES-AVX optimizations =150/155 Kh/s ; 3.4ghz core/cache and ~46W no throttle (stable optimised voltage/temp 76° max )
since v3.4.x Start mining with SSE2 AES AVX AVX2 = 140/145 Kh/s ; 3.4ghz core / 3.2ghz cache and +47w with some cpu throttle down the hashrate to 130 Kh/s and +85°
i have a question, i wanna try to solo mine but your client crash when request/receiving getwork (tested with all 3.3.x/3.4.x)
log 3.4.5 crash
http://pastebin.com/ynJiLnsP
Topic: [ANN]: cpuminer-opt v3.8.8.1, open source optimized multi-algo CPU miner - page 139. (Read 444040 times)
September 05, 2016, 07:43:37 AM
September 04, 2016, 11:16:33 PM
thanks for the great work! 
Is it possible to opt the cryptolight algo
Is it possible to opt the cryptolight algo
September 04, 2016, 09:46:55 AM
@joblo, here is small 0.1 BTC donation for your excellent work on cpuminer-opt: https://blockchain.info/tx/6a77b6ea11cb901741b3d3dae4d714a28dc120f7591a6372a91af5924145ab96
Keep up the good work!
Best regards,
NiceHash team.
Keep up the good work!
Best regards,
NiceHash team.
Thank you very much..
September 04, 2016, 09:36:38 AM
@joblo, here is small 0.1 BTC donation for your excellent work on cpuminer-opt: https://blockchain.info/tx/6a77b6ea11cb901741b3d3dae4d714a28dc120f7591a6372a91af5924145ab96
Keep up the good work!
Best regards,
NiceHash team.
Keep up the good work!
Best regards,
NiceHash team.
September 04, 2016, 02:27:58 AM
@Joblo would it be cool with you if I mine to your BTC donation address at nicehash as donation time for your work? I'll mine one full day per week as donation. Every other user can do the same as well.
I just received an anonymous payment at my donation address. Thank you and any others who followed your suggestion.
That was from nicehash payout. Cryptonight mining has been quite good especially with the fixed rejection issues. 
September 03, 2016, 02:29:37 PM
i think i was 2 years ago 
September 03, 2016, 02:24:50 PM
Me nothing.... nobody mining M7 on nvidia? :-/
September 03, 2016, 01:53:36 PM
me too maybe the same source...
maybe the same source... September 03, 2016, 12:26:03 PM
@Joblo would it be cool with you if I mine to your BTC donation address at nicehash as donation time for your work? I'll mine one full day per week as donation. Every other user can do the same as well.
I just received an anonymous payment at my donation address. Thank you and any others who followed your suggestion.
September 02, 2016, 10:28:15 AM
Tried compiling on a non-aesni cpu (core2), but it tries to use aesni on cryptonight:
In file included from /usr/lib/gcc/x86_64-linux-gnu/5/include/x86intrin.h:43:0,
from algo/cryptonight/cryptonight-aesni.c:1:
algo/cryptonight/cryptonight-aesni.c: In function ‘ExpandAESKey256_sub2’:
/usr/lib/gcc/x86_64-linux-gnu/5/include/wmmintrin.h:87:1: error: inlining failed in call to always_inline ‘_mm_aeskeygenassist_si128’: target specific option mismatch
_mm_aeskeygenassist_si128 (__m128i __X, const int __C)
^
algo/cryptonight/cryptonight-aesni.c:26:7: error: called from here
tmp4 = _mm_aeskeygenassist_si128(*tmp1, 0x00);
^
In file included from /usr/lib/gcc/x86_64-linux-gnu/5/include/x86intrin.h:43:0,
from algo/cryptonight/cryptonight-aesni.c:1:
algo/cryptonight/cryptonight-aesni.c: In function ‘ExpandAESKey256_sub2’:
/usr/lib/gcc/x86_64-linux-gnu/5/include/wmmintrin.h:87:1: error: inlining failed in call to always_inline ‘_mm_aeskeygenassist_si128’: target specific option mismatch
_mm_aeskeygenassist_si128 (__m128i __X, const int __C)
^
algo/cryptonight/cryptonight-aesni.c:26:7: error: called from here
tmp4 = _mm_aeskeygenassist_si128(*tmp1, 0x00);
^
I'm getting the same error i'm using corei7 on windows 7 how do i compile with corei7-avx? i'm doing via cygwin....
Code:
./autogen.sh
Unescaped left brace in regex is deprecated, passed through in regex; marked by <-- HERE in m/\${ <-- HERE ([^ \t=:+{}]+)}/ at /usr/bin/automake-1.14 line 3930.
LIBCURL="-lcurldll" ./configure CFLAGS="-O3"
configure: error: Missing required libcurl >= 7.15.2 (I've installed libcurl?)
make
from aes.c:2:
aes.c: In function ‘ExpandAESKey256_sub2’:
/usr/lib/gcc/x86_64-pc-cygwin/5.4.0/include/wmmintrin.h:87:1: error: inlining failed in call to always_inline ‘_mm_aeskeygenassist_si128’: target specific option mismatch
_mm_aeskeygenassist_si128 (__m128i __X, const int __C)
^
aes.c:21:7: error: called from here
tmp4 = _mm_aeskeygenassist_si128(*tmp1, 0x00);
^
make[2]: *** [Makefile:569: hodlminer-aes.o] Error 1
make[2]: Leaving directory '/home/Laptop/hodlminer-wolf'
make[1]: *** [Makefile:632: all-recursive] Error 1
make[1]: Leaving directory '/home/Laptop/hodlminer-wolf'
make: *** [Makefile:384: all] Error 2
Please provide more information such as CPU, and compile procedure. The post you quoted was withan AMD CPU and appeared
to be a problem with the compiler detecting the correct CPU architecture.
September 02, 2016, 05:22:40 AM
Tried compiling on a non-aesni cpu (core2), but it tries to use aesni on cryptonight:
In file included from /usr/lib/gcc/x86_64-linux-gnu/5/include/x86intrin.h:43:0,
from algo/cryptonight/cryptonight-aesni.c:1:
algo/cryptonight/cryptonight-aesni.c: In function ‘ExpandAESKey256_sub2’:
/usr/lib/gcc/x86_64-linux-gnu/5/include/wmmintrin.h:87:1: error: inlining failed in call to always_inline ‘_mm_aeskeygenassist_si128’: target specific option mismatch
_mm_aeskeygenassist_si128 (__m128i __X, const int __C)
^
algo/cryptonight/cryptonight-aesni.c:26:7: error: called from here
tmp4 = _mm_aeskeygenassist_si128(*tmp1, 0x00);
^
In file included from /usr/lib/gcc/x86_64-linux-gnu/5/include/x86intrin.h:43:0,
from algo/cryptonight/cryptonight-aesni.c:1:
algo/cryptonight/cryptonight-aesni.c: In function ‘ExpandAESKey256_sub2’:
/usr/lib/gcc/x86_64-linux-gnu/5/include/wmmintrin.h:87:1: error: inlining failed in call to always_inline ‘_mm_aeskeygenassist_si128’: target specific option mismatch
_mm_aeskeygenassist_si128 (__m128i __X, const int __C)
^
algo/cryptonight/cryptonight-aesni.c:26:7: error: called from here
tmp4 = _mm_aeskeygenassist_si128(*tmp1, 0x00);
^
I'm getting the same error i'm using corei7 on windows 7 how do i compile with corei7-avx? i'm doing via cygwin....
Code:
./autogen.sh
Unescaped left brace in regex is deprecated, passed through in regex; marked by <-- HERE in m/\${ <-- HERE ([^ \t=:+{}]+)}/ at /usr/bin/automake-1.14 line 3930.
LIBCURL="-lcurldll" ./configure CFLAGS="-O3"
configure: error: Missing required libcurl >= 7.15.2 (I've installed libcurl?)
make
from aes.c:2:
aes.c: In function ‘ExpandAESKey256_sub2’:
/usr/lib/gcc/x86_64-pc-cygwin/5.4.0/include/wmmintrin.h:87:1: error: inlining failed in call to always_inline ‘_mm_aeskeygenassist_si128’: target specific option mismatch
_mm_aeskeygenassist_si128 (__m128i __X, const int __C)
^
aes.c:21:7: error: called from here
tmp4 = _mm_aeskeygenassist_si128(*tmp1, 0x00);
^
make[2]: *** [Makefile:569: hodlminer-aes.o] Error 1
make[2]: Leaving directory '/home/Laptop/hodlminer-wolf'
make[1]: *** [Makefile:632: all-recursive] Error 1
make[1]: Leaving directory '/home/Laptop/hodlminer-wolf'
make: *** [Makefile:384: all] Error 2
September 01, 2016, 03:03:18 AM
@joblo
indeed, found this (originally japanese) text:
so it seems my target needed is bdver2
cheers
indeed, found this (originally japanese) text:
Quote
A description of the GCC source code of "BDver4" before delving into the subject . AMD has publicly the development plan of the architecture than before , until "Excavator" has been revealed . "BDver1" is that of the first generation "Bulldozer" which appeared in 2011 . "BDver2" is "Piledriver" in , are those some of the improvements from the "Bulldozer" has been carried out , has been used in the current FX CPU Ya "Richland" APU. "BDver3" is a CPU core to be used in the "Kaveri" APU of AMD's plans to introduce at the end of this year in the "Steamroller".
so it seems my target needed is bdver2
cheers
August 31, 2016, 06:39:44 PM
The following change will be made to the share result output in the next release. There is a small change from
the initial proposal.
[2016-08-31 10:21:44] Accepted 10/10 (100%), 5026 H, 215.37 H/s
[2016-08-31 10:21:44] Rejected 10/11 (99.9%), 5026 H, 215.37 H/s
the initial proposal.
[2016-08-31 10:21:44] Accepted 10/10 (100%), 5026 H, 215.37 H/s
[2016-08-31 10:21:44] Rejected 10/11 (99.9%), 5026 H, 215.37 H/s
Small nit:
With the proposed change to the vocabulary after the timestamp, the following metric could also be adjusted.
In the case of an accepted share, you would see the total of accepted shares followed by the grand total of all shares submitted.
in the case of a rejected share, you would see the total of rejected shares followed by the grand total of all shares submitted.
could also change the percentage metric to display the rejection percentage when a share is rejected, instead of defaulting to the acceptance percentage for all shares irregardless of their status.
as follows:
[2016-08-31 10:21:44] Accepted 10/10 (100%), 5026 H, 215.37 H/s
[2016-08-31 10:21:56] Rejected 1/11 (0.1%), 5026 H, 215.37 H/s
...
It makes sense to do both, good idea.
August 31, 2016, 06:35:48 PM
The following change will be made to the share result output in the next release. There is a small change from
the initial proposal.
[2016-08-31 10:21:44] Accepted 10/10 (100%), 5026 H, 215.37 H/s
[2016-08-31 10:21:44] Rejected 10/11 (99.9%), 5026 H, 215.37 H/s
the initial proposal.
[2016-08-31 10:21:44] Accepted 10/10 (100%), 5026 H, 215.37 H/s
[2016-08-31 10:21:44] Rejected 10/11 (99.9%), 5026 H, 215.37 H/s
Small nit:
With the proposed change to the vocabulary after the timestamp, the following metric could also be adjusted.
In the case of an accepted share, you would see the total of accepted shares followed by the grand total of all shares submitted.
in the case of a rejected share, you would see the total of rejected shares followed by the grand total of all shares submitted.
could also change the percentage metric to display the rejection percentage when a share is rejected, instead of defaulting to the acceptance percentage for all shares irregardless of their status.
as follows:
[2016-08-31 10:21:44] Accepted 10/10 (100%), 5026 H, 215.37 H/s
[2016-08-31 10:21:56] Rejected 1/11 (0.1%), 5026 H, 215.37 H/s
...
August 31, 2016, 06:11:17 PM
This was my reference:
https://gcc.gnu.org/onlinedocs/gcc/x86-Options.html
If you have mingw installed you can confirm with:
gcc -Q -march=native --help=target | grep march
Edit: yours looks more like bdver2 or 3.
Edit2: Upon further thought there's probably no need to build bins for AMD. There is no AMD specific code so as
long as the feature set lines up the Intel builds should work just as well.
https://gcc.gnu.org/onlinedocs/gcc/x86-Options.html
If you have mingw installed you can confirm with:
gcc -Q -march=native --help=target | grep march
Edit: yours looks more like bdver2 or 3.
Edit2: Upon further thought there's probably no need to build bins for AMD. There is no AMD specific code so as
long as the feature set lines up the Intel builds should work just as well.
August 31, 2016, 06:08:36 PM
3.4.5 (cryptonight) works for me on windows 7 with hashwell & sandy bridge with nicehash&dwarf. No more screen full of stratum connection fails like in 3.4.4.
If I were you I would add xmr address to my sig.
If I were you I would add xmr address to my sig.
Thanks for testing. It looks like I have all Intel CPU nailed down.
AMD, not so sure. amdfam10 still won't compile, trips up in AES code. I haven't heard from any AMD users recently to know
what works and what doesn't.
XMR: 497qTtunbvPgUT6auQnLLacLPKNnxW9fADEYy1ugYYLXd5FuyCR3RwoT44hanwKYnyXXq8QtLTYAr1Q AKe3jCWPfN8oEK3W
working in which regard?
for my A6-6400K (amdfam10) i use core-avx-i, seems to result in the best hashrates
Working in the sense that there is a useable miner and it can use the CPU's best features.
Excellent tip but I'm surprised it works, amdfam10 doesn't have AVX. It doesn't have SSE4.1 or SSE4.2 either which is where
I think my compile is blowing up.
It's a good idea to try the Inlel builds on AMD CPUs.
the A6 is amdfam10 right? it definitely has AVX:
August 31, 2016, 06:03:46 PM
3.4.5 (cryptonight) works for me on windows 7 with hashwell & sandy bridge with nicehash&dwarf. No more screen full of stratum connection fails like in 3.4.4.
If I were you I would add xmr address to my sig.
If I were you I would add xmr address to my sig.
Thanks for testing. It looks like I have all Intel CPU nailed down.
AMD, not so sure. amdfam10 still won't compile, trips up in AES code. I haven't heard from any AMD users recently to know
what works and what doesn't.
XMR: 497qTtunbvPgUT6auQnLLacLPKNnxW9fADEYy1ugYYLXd5FuyCR3RwoT44hanwKYnyXXq8QtLTYAr1Q AKe3jCWPfN8oEK3W
working in which regard?
for my A6-6400K (amdfam10) i use core-avx-i, seems to result in the best hashrates
Working in the sense that there is a useable miner and it can use the CPU's best features.
Excellent tip but I'm surprised it works, amdfam10 doesn't have AVX. It doesn't have SSE4.1 or SSE4.2 either which is where
I think my compile is blowing up.
It's a good idea to try the Inlel builds on AMD CPUs.
August 31, 2016, 05:49:51 PM
3.4.5 (cryptonight) works for me on windows 7 with hashwell & sandy bridge with nicehash&dwarf. No more screen full of stratum connection fails like in 3.4.4.
If I were you I would add xmr address to my sig.
If I were you I would add xmr address to my sig.
Thanks for testing. It looks like I have all Intel CPU nailed down.
AMD, not so sure. amdfam10 still won't compile, trips up in AES code. I haven't heard from any AMD users recently to know
what works and what doesn't.
XMR: 497qTtunbvPgUT6auQnLLacLPKNnxW9fADEYy1ugYYLXd5FuyCR3RwoT44hanwKYnyXXq8QtLTYAr1Q AKe3jCWPfN8oEK3W
working in which regard?
for my A6-6400K (amdfam10) i use core-avx-i, seems to result in the best hashrates
August 31, 2016, 05:46:21 PM
3.4.5 (cryptonight) works for me on windows 7 with hashwell & sandy bridge with nicehash&dwarf. No more screen full of stratum connection fails like in 3.4.4.
If I were you I would add xmr address to my sig.
If I were you I would add xmr address to my sig.
Thanks for testing. It looks like I have all Intel CPU nailed down.
AMD, not so sure. amdfam10 still won't compile, trips up in AES code. I haven't heard from any AMD users recently to know
what works and what doesn't.
XMR: 497qTtunbvPgUT6auQnLLacLPKNnxW9fADEYy1ugYYLXd5FuyCR3RwoT44hanwKYnyXXq8QtLTYAr1Q AKe3jCWPfN8oEK3W
August 31, 2016, 04:56:04 PM
3.4.5 (cryptonight) works for me on windows 7 with hashwell & sandy bridge with nicehash&dwarf. No more screen full of stratum connection fails like in 3.4.4.
If I were you I would add xmr address to my sig.
If I were you I would add xmr address to my sig.
Jump to: