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

[th3.r00t]

I'm looking at updating the errata for old AMD CPUs and would like more precision on which CPUs work
and which don't.

Athlon 64 x2 and Phenom II x4 are confirmed not to work. It appears anything less than Bulldozer, which
introduced AVX, will not work with all algos.

If no one has data that says otherwise I'll update the errata in the OP.

These CPUs are working fine with legacy versions on zr5 algo.
I haven't tested other algos, since I have no interest in them.
m7m also works if I recall corectly - will test that on a weekend.

Thanks, that helps localize the incompatible code, it's not in code used by zr5 or m7m.
Let me know if something is broken using an AVX enabled AMD CPU, that would be
unexpected.

If that can help you identify (and hopefully fix) broken algos, I will do a full test tomorrow on all algos supported on zpool.ca.
That includes Linux and Windows builds of legacy versions (since they are faster on these CPUs).

[joblo]

I'm looking at updating the errata for old AMD CPUs and would like more precision on which CPUs work
and which don't.

Athlon 64 x2 and Phenom II x4 are confirmed not to work. It appears anything less than Bulldozer, which
introduced AVX, will not work with all algos.

If no one has data that says otherwise I'll update the errata in the OP.

These CPUs are working fine with legacy versions on zr5 algo.
I haven't tested other algos, since I have no interest in them.
m7m also works if I recall corectly - will test that on a weekend.

Thanks, that helps localize the incompatible code, it's not in code used by zr5 or m7m.
Let me know if something is broken using an AVX enabled AMD CPU, that would be
unexpected.

If that can help you identify (and hopefully fix) broken algos, I will do a full test tomorrow on all algos supported on zpool.ca.
That includes Linux and Windows builds of legacy versions (since they are faster on these CPUs).

I appreciate the effort but It's not something that I can fix easilly, so the work would only be for information purposes.
My main focus is on the newer architectures so I want to make sure all algos work on AVX enabled AMD CPUs.
Any problems with them would need to be fixed.

[giagge]

Anyone have result with Ryzen and Hexxcoin ?  .

[joblo]

Anyone have result with Ryzen and Hexxcoin ?  .

There are a couple of threads discussing Ryzen but the only results I've seen are for cryptonight
which are in line with Intel based on L3 cache size.

I'd like to see a test with lyra2z330 as a real memory stress test regardless of cache. I'd also like to see
a test with deep to give those 16 threads a good workout. They represent the extremes of I/O bound
and compute bound algos.

[esfomeado]

Is there any tutorial of how to compile this on Windows?

Thanks

[joblo]

cpuminer-opt-3.5.13 is released, see OP.

There is a smalll optimization but more importantly for those interested in solo mining
there is a major fix to getwork.

I am unable to test the fix but I encourage users to try with their favorite coin and report
their results:

1. Basic info on test environment: CPU, OS, algo, coin,

2. Information for each miner used: version, compiled from source or binaries, link if not well known

2. Does solo mining using the wallet miner work?

3. Does cpuminer-opt work solo mining? Provide details including console session showing command line options.

4. Is there another miner available that works solo mining? Provide details.

5. Any technical info available about the algo/coin that affects solo mining, ie similarities/differences with other algos
    that produce different test results.

[matejbilahora]

Anyone have result with Ryzen and Hexxcoin ?   .

I think it would be nice if some could compile new version incl. new ryzen cpu. I am trying to get it to work, but somehow ryzen is not so good as intel cpus for mining.

[marte1982]

hi please help....i have need of dependencies for linux of this miner  https://github.com/JayDDee/cpuminer-opt
thanks to all for your support

[joblo]

Anyone have result with Ryzen and Hexxcoin ?   .

I think it would be nice if some could compile new version incl. new ryzen cpu. I am trying to get it to work, but somehow ryzen is not so good as intel cpus for mining.

Try cpuminer-aes-avx2.exe, that should work. If not try cpuminer-aes-avx.exe.

[joblo]

hi please help....i have need of dependencies for linux of this miner  https://github.com/JayDDee/cpuminer-opt
thanks to all for your support

RELEASE_NOTES

[HexxoDev]

HexxCoin/Lyra2z330 solo tested with 3.5.13
Switching to getwork works now without coinaddress, but still not able to find blocks.

[giagge]

Anyone have result with Ryzen and Hexxcoin ?   .

I think it would be nice if some could compile new version incl. new ryzen cpu. I am trying to get it to work, but somehow ryzen is not so good as intel cpus for mining.

Ohhh  , its the same result with my i5 6600 with only 4 core ...

I think ryzen have a real good performance for this , but not optimized .

[joblo]

HexxCoin/Lyra2z330 solo tested with 3.5.13
Switching to getwork works now without coinaddress, but still not able to find blocks.

Thanks for testing. Can you show me the output? How long did you test vs expected block time?
Is there another miner where solo works for this algo?

[HexxoDev]

HexxCoin/Lyra2z330 solo tested with 3.5.13
Switching to getwork works now without coinaddress, but still not able to find blocks.

Thanks for testing. Can you show me the output? How long did you test vs expected block time?
Is there another miner where solo works for this algo?

There is currently no other miner than yours.
So we cant test it else.
Using false algo would give same results.  <---hint..

It shows block we are on and nethashrate, all seems like it is working.
Still, shown hashrate is about 1.5x compared to possible hashrate at pool.
It is doing some hash but not valid work.
Hashrate is extremely reacting to cpu load, not like with pool.
Edit:
Using 2 instances solo + pool cpuminer.
Pool cpuminer speed stays at 100% even when solo miner is "hashing".
It is not really giving any real load to cpu.


[2017-03-11 18:48:29] 1 miner threads started, using 'lyra2z330' algorithm.
[2017-03-11 18:48:30] API bind to port 4048 failed - trying again in 20sec
[2017-03-11 18:48:30] Current block is 19930
[2017-03-11 18:48:30] No payout address provided, switching to getwork
[2017-03-11 18:48:32] CPU #0: 2 H, 64.10 H/s
[2017-03-11 18:48:35] CPU #0: 2 H, 64.10 H/s
[2017-03-11 18:48:37] CPU #0: 2 H, 64.10 H/s
[2017-03-11 18:48:39] CPU #0: 2 H, 64.10 H/s
[2017-03-11 18:48:41] CPU #0: 2 H, 64.10 H/s

[Rachelin]

It's very great for this version . I tried many algo for many coins. It's faster than old version 15%-20%.
Thank you, Dev

[HexxoDev]

Input needed!
Im trying to help user to setup cloud mining.
Currently I have no fresh linux setup to use.

This is a "hands free" guess:

sudo apt-get update -y
sudo apt-get upgrade -y
sudo apt-get install -y build-essential libssl-dev libcurl4-openssl-dev libjansson-dev libgmp-dev automake screen git
git clone https://github.com/JayDDee/cpuminer-opt
cd cpuminer-opt
./build.sh
screen -d -m  ./cpuminer -a lyra2z330 -o stratum+tcp://hexx.suprnova.cc:2876 -u myuser -p mypassword


Please modify and repost

[joblo]

HexxCoin/Lyra2z330 solo tested with 3.5.13
Switching to getwork works now without coinaddress, but still not able to find blocks.

Thanks for testing. Can you show me the output? How long did you test vs expected block time?
Is there another miner where solo works for this algo?

There is currently no other miner than yours.
So we cant test it else.
Using false algo would give same results.  <---hint..

It shows block we are on and nethashrate, all seems like it is working.
Still, shown hashrate is about 1.5x compared to possible hashrate at pool.
It is doing some hash but not valid work.
Hashrate is extremely reacting to cpu load, not like with pool.
Edit:
Using 2 instances solo + pool cpuminer.
Pool cpuminer speed stays at 100% even when solo miner is "hashing".
It is not really giving any real load to cpu.


[2017-03-11 18:48:29] 1 miner threads started, using 'lyra2z330' algorithm.
[2017-03-11 18:48:30] API bind to port 4048 failed - trying again in 20sec
[2017-03-11 18:48:30] Current block is 19930
[2017-03-11 18:48:30] No payout address provided, switching to getwork
[2017-03-11 18:48:32] CPU #0: 2 H, 64.10 H/s
[2017-03-11 18:48:35] CPU #0: 2 H, 64.10 H/s
[2017-03-11 18:48:37] CPU #0: 2 H, 64.10 H/s
[2017-03-11 18:48:39] CPU #0: 2 H, 64.10 H/s
[2017-03-11 18:48:41] CPU #0: 2 H, 64.10 H/s

Excellent info. I'll take another look at the code to see why it's not hashing correctly. That part
should have nothing to do with getwork so it might be something simple.

Edit: In the meantime you might be able to mod the zcoin miner by optiminer even if you have no
coding skills.

https://github.com/Optiminer/cpuminer-xzc

Just change the rows arg in algo/lyra2rev2.c line 25 to 330.

Code:

old:	LYRA2(wholeMatrix, hash, 32, input, 80, input, 80, 2, height, 256);

new:	LYRA2(wholeMatrix, hash, 32, input, 80, input, 80, 2, 330, 256);

Just remember to use -a lyra2v2 on the command line, he just modified lyra2v2 to work for zcoin,
now you can modify it to work for lyra2z330. If getwork works it gives me something to compare with.

[giagge]

I use cpuminer-opt-3.5.12-windows for hexxcoin on suprnova , its ok ? .

[joblo]

I use cpuminer-opt-3.5.12-windows for hexxcoin on suprnova , its ok ? .

Thanks. The discussion with hexxodev is about solo mining, nothing to do with pool mining using
stratum. I don't want anyone following the advice I give to him unless they know what they are doing.

[joblo]

@hexxodev

I think I've found another bug in getwork. You may want to do this before modding the zcoin miner.
It's a one line change in cpu-miner.c line 289.

Code:

bool std_work_decode( const json_t *val, struct work *work)
{
    int i;
    int data_size   = algo_gate.work_data_size;
    int target_size = sizeof(work->target);
//    int adata_sz    = ARRAY_SIZE(work->data);
    int adata_sz    = data_size / 4;
    int atarget_sz  = ARRAY_SIZE(work->target);