Topic: [ANN]: cpuminer-opt v3.8.8.1, open source optimized multi-algo CPU miner - page 160. (Read 444040 times)

I continue to encourage Windows users to compile their own. That is always the best way

How would I go about doing that? LOL. Is there a "free" Windows compiler out there? I have Xeon E5640.

I do have access to Visual Studio Community 2015; supposed to be the same as Professional without CodeLens.

On the other hand, is there some "newbie" guide to doing this with a fresh install of say, Debian 8.4? (Or would you recommend Ubuntu?)

I just made a Debian 8.4 VM. Maybe I'll do it over again.

This is compiled on windows with a free compiler, but it is a pain to set up if you don't know what you are doing. It can compile using mingw-w64 and msys, but you need to first compile all of the dependencies and link everything correctly.

That was not the case for me using msys and mingw_w64. Nothing to compile except cpuminer-opt itself.

joblo

legendary

Activity: 1470

Merit: 1114

I continue to encourage Windows users to compile their own. That is always the best way

How would I go about doing that? LOL. Is there a "free" Windows compiler out there? I have Xeon E5640.

I do have access to Visual Studio Community 2015; supposed to be the same as Professional without CodeLens.

On the other hand, is there some "newbie" guide to doing this with a fresh install of say, Debian 8.4? (Or would you recommend Ubuntu?)

I just made a Debian 8.4 VM. Maybe I'll do it over again.

cpuminer-opt doesn't compile on any form of VS.

There are two viable options.

1. Compile natively on Windows with mingw and msys. Instructions are in the README.md file.
Installing msys and mingw_w64 can be a bit confusing. They are two seperate installs with different installers
but they are built to work together.

2. Install a Linux VM and compile and run cpuminer from the vm, full speed. I would recommend Ubuntu or
Mint. Fedora and centos are also good choices. Debian is not for newbies but if you already have it installed
go with it. Once the OS is installed you have to install the development tools. I don't have the minimalist command
to get everything (note to self to do that), I usually start with gcc and any of its dependencies and iterate from there
until it works. In addition to the develpopment tools there are some libraries that need to be installed. They are listed
in README.md.

Usng a VM may be preferable if you intend to mine hodl with an older CPU because that doesn't work on Windows.

ctgiant

sr. member

Activity: 298

Merit: 250

I continue to encourage Windows users to compile their own. That is always the best way

How would I go about doing that? LOL. Is there a "free" Windows compiler out there? I have Xeon E5640.

I do have access to Visual Studio Community 2015; supposed to be the same as Professional without CodeLens.

On the other hand, is there some "newbie" guide to doing this with a fresh install of say, Debian 8.4? (Or would you recommend Ubuntu?)

I just made a Debian 8.4 VM. Maybe I'll do it over again.

This is compiled on windows with a free compiler, but it is a pain to set up if you don't know what you are doing. It can compile using mingw-w64 and msys, but you need to first compile all of the dependencies and link everything correctly.

hmage

member

Activity: 83

Merit: 10

On the other hand, is there some "newbie" guide to doing this with a fresh install of say, Debian 8.4? (Or would you recommend Ubuntu?)

I just made a Debian 8.4 VM. Maybe I'll do it over again.

Simple way to do it on fresh Debian or Ubuntu is this (assuming sudo is already configured):

Code:

sudo apt-get install git build-essential libssl-dev libcurl4-openssl-dev libjansson-dev libgmp-dev automake
git clone https://github.com/hmage/cpuminer-opt
cd cpuminer-opt
./build.sh

With git it's easier to get the source code in command line than from joblo's google drive — there are no direct links to tar.gz.

Dabs

legendary

Activity: 3416

Merit: 1912

The Concierge of Crypto

Quote from: NeuroticFish on June 03, 2016, 11:03:51 AM

I continue to encourage Windows users to compile their own. That is always the best way

How would I go about doing that? LOL. Is there a "free" Windows compiler out there? I have Xeon E5640.

I do have access to Visual Studio Community 2015; supposed to be the same as Professional without CodeLens.

On the other hand, is there some "newbie" guide to doing this with a fresh install of say, Debian 8.4? (Or would you recommend Ubuntu?)

I just made a Debian 8.4 VM. Maybe I'll do it over again.

joblo

legendary

Activity: 1470

Merit: 1114

Thank you very much. This is important information. As mentioned in a subsequent post
your CPU actually uses the nehalem compile arch, the westmere build is incompatible.

This solves part of the mystery. There are two compile targets for 1st generation corei CPUs,
Nehalem which will not run the miners' AES code, and Westmere which will.

For now I don't have the means and time to try my own compile, but whenever I can help with a run/test, just PM me and I'll give is a try.
And you... keep up the good work

! Thank you.

And thank you for the kind words. If you ever get the urge to try to compile your owm I'm here to help.

joblo

legendary

Activity: 1470

Merit: 1114

Ok, once more around the block with capabilities checks.

Edit: made some changes and added more examples.

Edit2: changed checking order to all AES variables first. For this quasi-debug release it
wil continue to perform all checks. The production version will only check SSE2 in AES fails.
For the debug release SSE2 support is taken literally but in the production version it will
mean (SSE2 && !AES) to the YES/NO response is more appropriate.

I am trying out a more detailed permissive check that will display all variables used
and hopefuly give an informative message to the user. I hope this balances out the need
for technical info and user-friendliness. The only risk is that the miner will always attempt
to mine and may crash if incompatible.

Here are some examples of the output most users are likely to see. I don't check for the newer features like AVX2
because they are not used in the decision making that determines the final message.

AES:

Code:

Checking CPU capatibility...
        Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz
   CPU arch has AES...........YES.
   CPU arch has AVX...........YES.
   SW built for AES & AVX.....YES.
   Algo supports AES & AVX....YES.
   System supports AES & AVX..YES.
   CPU arch has SSE2..........YES.                   
   SW built for SSE2..........YES.
   System supports SSE2.......YES.
Start mining with AES-AVX optimizations...

SSE2:

Code:

Checking CPU capatibility...
        Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz
   CPU arch has AES...........NO.
   CPU arch has AVX...........NO.
   CPU arch has SSE2..........YES.
   SW built for AES & AVX.....NO.
   SW built for SSE2..........YES.
   Algo supports AES & AVX....YES.
   System supports AES & AVX..NO.
   System supports SSE2.......YES.
AES not available, starting mining with SSE2 optimizations...

Nehalem CPU using Westmere build:

Code:

Checking CPU capatibility...
        Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz
   CPU arch has AES...........YES.
   CPU arch has AVX...........NO.
   CPU arch has SSE2..........YES.
   SW built for AES & AVX.....YES.
   SW built for SSE2..........YES.
   Algo supports AES & AVX....YES.
   System supports AES & AVX..NO.
   System supports SSE2.......YES.
Unsupported CPU or SW configuration, miner will likely crash!

This will hopefully solve the issue for good. Only when this code has proven itself
will I consider turning enforcement back on.

At this time there are no pressing issues to prompt a new release. Too many releases in the past week.

I'll wait for more feedback from users especially those with 1st gen corei CPUs before releasing.
However I can provide the source code to those who can compile their own and are willing to share
their test results. This change only affects the CPU capabilities check at miner startup so if you don't
have any problems with that you don't need this and can wait for the general release.

NeuroticFish

legendary

Activity: 3668

Merit: 6382

Looking for campaign manager? Contact icopress!

Quote from: hmage on June 03, 2016, 10:02:05 AM

Thank you very much. This is important information. As mentioned in a subsequent post
your CPU actually uses the nehalem compile arch, the westmere build is incompatible.

This solves part of the mystery. There are two compile targets for 1st generation corei CPUs,
Nehalem which will not run the miners' AES code, and Westmere which will.

For now I don't have the means and time to try my own compile, but whenever I can help with a run/test, just PM me and I'll give is a try.
And you... keep up the good work

! Thank you.

joblo

legendary

Activity: 1470

Merit: 1114

Quote from: joblo on June 03, 2016, 09:13:10 AM

Quote from: hmage on June 03, 2016, 09:07:29 AM

Quote from: joblo on June 03, 2016, 09:13:10 AM

whitespace cleaner tool

Code:

alias trimfile="sed -r 's~[[:space:]]+\$~~g' -i"

To keep merge compatibility with joblo's google-drive dumps, I don't touch much. Cleaning up whitespace without joblo doing it in upstream will result in a lot of merge conflicts.

What's the intended purpose? Whitespace is good.

Whitespace is good. Endspace at end of lines is not good. http://vim.wikia.com/wiki/Remove_unwanted_spaces

So that command will only strip trailing whitespace, ok.

Edit: I ran the sed command on a test file and it did nothing, it didn't strip any whitespace.

hmage

member

Activity: 83

Merit: 10

Quote from: hmage on June 03, 2016, 09:07:29 AM

Quote from: hmage on June 03, 2016, 09:07:29 AM

whitespace cleaner tool

Code:

alias trimfile="sed -r 's~[[:space:]]+\$~~g' -i"

To keep merge compatibility with joblo's google-drive dumps, I don't touch much. Cleaning up whitespace without joblo doing it in upstream will result in a lot of merge conflicts.

What's the intended purpose? Whitespace is good.

Whitespace is good. Endspace at end of lines is not good. http://vim.wikia.com/wiki/Remove_unwanted_spaces

joblo

legendary

Activity: 1470

Merit: 1114

Quote from: ljglug on June 03, 2016, 06:51:10 AM

whitespace cleaner tool

Code:

alias trimfile="sed -r 's~[[:space:]]+\$~~g' -i"

To keep merge compatibility with joblo's google-drive dumps, I don't touch much. Cleaning up whitespace without joblo doing it in upstream will result in a lot of merge conflicts.

What's the intended purpose? Whitespace is good.

joblo

legendary

Activity: 1470

Merit: 1114

xeon e5 2670 X2 @361K HMQ1725

This speed is not abnormal?

Yes.

hmage

member

Activity: 83

Merit: 10