Quote from: joblo on October 13, 2016, 04:18:44 PM

Quote from: Nik4691 on October 13, 2016, 04:04:35 PM

Quote from: joblo on October 13, 2016, 03:49:39 PM

Quote from: Nik4691 on October 13, 2016, 03:39:41 PM

Quote from: shakeandbake on October 13, 2016, 12:52:14 PM

Just a note about this - I was reading about this issue a number of days ago and someone mentioned that AES may not actually be enabled even though it says that it is? I just can't imagine that dual 6-core L5640 processors would perform like this without something being wrong. I tried doling things out via numactl and that didn't have any impact to speak of.

I don't use this miner for cryptonight, but i did a test and it seems it don't uses AES-NI.
Claymore's miner gives me about 300 h/s and Wolf0's about 280 h/s. This one only 170 h/s (total).
This, with an 8core AMD FX at 4GHz.
Considering that my old PHENOM without AES-NI gave me about the same h/s per core, i imagine that this is the case.

Compiled your own? AMD CPU have been a challenge to get properly compiled. I can't do it as I don't have any AMDs.
AMD users have reported problems compiling with "-march=native". A couple of AMD users have posted tips in this
thread that may help. What's the L3 cache size? (see my previous post).

I used the binaries in windows 7 x64 cpuminer-opt-3.4.7-windows.
I mine VERIUM now (-a scrypt:1048576) and the results seems legit (comparable with others with Intel or AMD processors with AES-NI).
I did some benchmarks with other algos too and it seems that AES-NI are working, but not on cryptonight.

The btver1 build does not include AES. Try the Intel builds or try compiling using the tips it README.md.

A, yes, that did the trick. Using the cpuminer-corei7-avx the hashrate is up there with Claymore's and Wolf0's miners (280 h/s).
But using -a scrypt:1048576 the hashrate is the same as with cpuminer-btver1 core.