Topic: [ANN]: cpuminer-opt v3.8.8.1, open source optimized multi-algo CPU miner - page 188. (Read 444067 times)
January 26, 2016, 02:09:07 PM
January 26, 2016, 01:57:34 PM
January 26, 2016, 01:57:04 PM
This line seems to have worked will know in a few mins. if it mines. I'm guessing this could be tweaked more if this get its started?
./configure CFLAGS="-march=bdver1 -Ofast" CXXFLAGS=$CFLAGS --with-crypto --with-curl
./configure CFLAGS="-march=bdver1 -Ofast" CXXFLAGS=$CFLAGS --with-crypto --with-curl
January 26, 2016, 01:46:29 PM
No source? I want to import the Intel GPU mining. I wanna expand my territory.
Went googling, found out cgminer 3.7 supports Intel GPU mining. Hard to find files,
recent version dropped support.
Found a source file and a windows binary that only does blake256. Haven't got the
source compiled yet but gave the binary a spin with wine and blake at zpool.
It found the GPU, connected to the pool and started hashing, but... all rejects.
Maybe an incompatible form of blake. It's a start.
Why is iy everytime I say I'm going to give windows another shot something
really, really interesting pops up?
January 26, 2016, 01:41:39 PM
a little speedup by better compiling:
Intel(R) Core(TM) i5 CPU 760 @ 2.80GHz
AES_NI: No.
SSE2: No, start mining without optimizations...
[....]
[2016-01-26 13:39:37] accepted: 7/7 (100.00%), 224.92 kH/s yes!
about 5-10% more by using this commandline (to be adapted to your own cpu):
./configure CFLAGS="-march=nehalem -Ofast -DNO_AES_NI" CXXFLAGS=$CFLAGS --with-crypto --with-curl
and remember to "make clean"
Intel(R) Core(TM) i5 CPU 760 @ 2.80GHz
AES_NI: No.
SSE2: No, start mining without optimizations...
[....]
[2016-01-26 13:39:37] accepted: 7/7 (100.00%), 224.92 kH/s yes!
about 5-10% more by using this commandline (to be adapted to your own cpu):
./configure CFLAGS="-march=nehalem -Ofast -DNO_AES_NI" CXXFLAGS=$CFLAGS --with-crypto --with-curl
and remember to "make clean"
Think any of this would help me to get a completion compile on the problem AMD system I posted about a few pages back?
https://bitcointalksearch.org/topic/m.13657053
the cpu doesn't look to have AES: did you try compiling with -DNO_AES_NI?
./configure CFLAGS="-march=?
?? -Ofast" CXXFLAGS=$CFLAGS --with-crypto --with-curl ??Code:
Processors Information
-------------------------------------------------------------------------
Processor 1 ID = 0
Number of cores 8 (max 8)
Number of threads 8 (max 8)
Name AMD Opteron 6124
Codename Magny-Cours
Specification AMD Opteron(tm) Processor 6124 HE
Package Socket G34 (1974)
CPUID F.9.1
Extended CPUID 10.9
Core Stepping HY-D1
Technology 45 nm
TDP Limit 74.4 Watts
Core Speed 1039.8 MHz
Multiplier x Bus Speed 4.0 x 259.9 MHz
HT Link speed 2859.4 MHz
Stock frequency 1800 MHz
Instructions sets MMX (+), 3DNow! (+), SSE, SSE2, SSE3, SSE4A, x86-64, AMD-V
L1 Data cache 8 x 64 KBytes, 2-way set associative, 64-byte line size
L1 Instruction cache 8 x 64 KBytes, 2-way set associative, 64-byte line size
L2 cache 8 x 512 KBytes, 16-way set associative, 64-byte line size
L3 cache 10 MBytes, 96-way set associative, 64-byte line size
FID/VID Control yes
FID range 4.0x - 9.0x
Max VID 1.050 V
# of P-States 5
P-State FID 0x2 - VID 0x2F - IDD 6 (9.00x - 0.962 V)
P-State FID 0x0 - VID 0x31 - IDD 6 (8.00x - 0.937 V)
P-State FID 0x10A - VID 0x34 - IDD 5 (6.50x - 0.900 V)
P-State FID 0x106 - VID 0x35 - IDD 4 (5.50x - 0.887 V)
P-State FID 0x100 - VID 0x37 - IDD 4 (4.00x - 0.862 V)
Package Type 0x3
Model 25
String 1 0x0
String 2 0x0
Page 0x0
CmpCap 8
ApicIdCoreSize 16
TDC Limit 48 Amps
Boosted P-States 0
Max non-turbo ratio 9.00x
Max turbo ratio 9.00x
Max CPU COF 18
Core Performance Boost no
P-State 0, FID 0x2 - VID 0x2F (9.00x - 0.962 V)
P-State 1, FID 0x0 - VID 0x31 (8.00x - 0.937 V)
P-State 2, FID 0x10A - VID 0x34 (6.50x - 0.900 V)
P-State 3, FID 0x106 - VID 0x35 (5.50x - 0.887 V)
P-State 4, FID 0x100 - VID 0x37 (4.00x - 0.862 V)
Attached device PCI device at bus 0, device 24, function 0
Attached device PCI device at bus 0, device 24, function 1
Attached device PCI device at bus 0, device 24, function 2
Attached device PCI device at bus 0, device 24, function 3
Attached device PCI device at bus 0, device 24, function 4
TSC 2339.8 MHz
Temperature 0 29°C (84°F) [0xE8] (Core #0)
Power 0 27.60 W (Package)
January 26, 2016, 12:56:52 PM
./configure CFLAGS="-march=native -Ofast" CXXFLAGS=$CFLAGS --with-crypto --with-curl
...
Checking CPU capatibility...
Intel(R) Core(TM) i5-4570S CPU @ 2.90GHz
AES_NI: Yes, start mining with AES_NI optimizations...
[2016-01-26 18:53:10] Starting Stratum on stratum+tcp://hashpower.co:3533
[2016-01-26 18:53:10] 4 miner threads started, using 'x11' algorithm.
[2016-01-26 18:53:10] Stratum difficulty set to 0.016
[2016-01-26 18:53:10] hashpower.co:3533 x11 block 108404
....
[2016-01-26 18:56:41] CPU #1: 120.05 kH/s
[2016-01-26 18:56:41] CPU #0: 108.78 kH/s
[2016-01-26 18:56:41] CPU #3: 122.82 kH/s
[2016-01-26 18:56:41] CPU #2: 124.79 kH/s
[2016-01-26 18:56:56] CPU #0: 111.53 kH/s
[2016-01-26 18:56:56] accepted: 2/2 (100.00%), 479.18 kH/s yes!
[2016-01-26 18:57:19] CPU #3: 124.94 kH/s
[2016-01-26 18:57:19] accepted: 3/3 (100.00%), 481.30 kH/s yes!
[2016-01-26 18:57:30] CPU #3: 126.10 kH/s
[2016-01-26 18:57:30] accepted: 4/4 (100.00%), 482.45 kH/s yes!
...
Checking CPU capatibility...
Intel(R) Core(TM) i5-4570S CPU @ 2.90GHz
AES_NI: Yes, start mining with AES_NI optimizations...
[2016-01-26 18:53:10] Starting Stratum on stratum+tcp://hashpower.co:3533
[2016-01-26 18:53:10] 4 miner threads started, using 'x11' algorithm.
[2016-01-26 18:53:10] Stratum difficulty set to 0.016
[2016-01-26 18:53:10] hashpower.co:3533 x11 block 108404
....
[2016-01-26 18:56:41] CPU #1: 120.05 kH/s
[2016-01-26 18:56:41] CPU #0: 108.78 kH/s
[2016-01-26 18:56:41] CPU #3: 122.82 kH/s
[2016-01-26 18:56:41] CPU #2: 124.79 kH/s
[2016-01-26 18:56:56] CPU #0: 111.53 kH/s
[2016-01-26 18:56:56] accepted: 2/2 (100.00%), 479.18 kH/s yes!
[2016-01-26 18:57:19] CPU #3: 124.94 kH/s
[2016-01-26 18:57:19] accepted: 3/3 (100.00%), 481.30 kH/s yes!
[2016-01-26 18:57:30] CPU #3: 126.10 kH/s
[2016-01-26 18:57:30] accepted: 4/4 (100.00%), 482.45 kH/s yes!
January 26, 2016, 12:43:38 PM
Even more (x11):
[2016-01-26 15:00:11] accepted: 6/6 (100.00%), 229.12 kH/s yes!
With:
./configure CFLAGS="-march=nehalem -Ofast -fomit-frame-pointer -Wno-write-strings -funroll-loops -fvariable-expansion-in-unroller -ftree-loop-if-convert-stores -fmerge-all-constants -fbranch-target-load-optimize -fsched2-use-superblocks -DNO_AES_NI -DSPH_SMALL_FOOTPRINT_HAVAL -DSPH_KECCAK_UNROLL=1 -DSPH_KECCAK_NOCOPY -DSPH_KECCAK_INTERLEAVE=0 -DSPH_SMALL_FOOTPRINT_SHA2" CXXFLAGS=$CFLAGS --with-crypto --with-curl
YMMV
[2016-01-26 15:00:11] accepted: 6/6 (100.00%), 229.12 kH/s yes!
With:
./configure CFLAGS="-march=nehalem -Ofast -fomit-frame-pointer -Wno-write-strings -funroll-loops -fvariable-expansion-in-unroller -ftree-loop-if-convert-stores -fmerge-all-constants -fbranch-target-load-optimize -fsched2-use-superblocks -DNO_AES_NI -DSPH_SMALL_FOOTPRINT_HAVAL -DSPH_KECCAK_UNROLL=1 -DSPH_KECCAK_NOCOPY -DSPH_KECCAK_INTERLEAVE=0 -DSPH_SMALL_FOOTPRINT_SHA2" CXXFLAGS=$CFLAGS --with-crypto --with-curl
YMMV
Did you get that from Wolf0's cryptonight? Yet another thing to look into is all those compiler switches.
Some are obvious by their name but other I have no clue, yet.
Some from Wolf0, some I found myself, some I don't remember...
Some are included into the generic -O optimisation switch: the best to try are -O3 and -Ofast.
The defines could be integrated into the code as defaults, if they benefit most cpus.
January 26, 2016, 12:12:28 PM
Even more (x11):
[2016-01-26 15:00:11] accepted: 6/6 (100.00%), 229.12 kH/s yes!
With:
./configure CFLAGS="-march=nehalem -Ofast -fomit-frame-pointer -Wno-write-strings -funroll-loops -fvariable-expansion-in-unroller -ftree-loop-if-convert-stores -fmerge-all-constants -fbranch-target-load-optimize -fsched2-use-superblocks -DNO_AES_NI -DSPH_SMALL_FOOTPRINT_HAVAL -DSPH_KECCAK_UNROLL=1 -DSPH_KECCAK_NOCOPY -DSPH_KECCAK_INTERLEAVE=0 -DSPH_SMALL_FOOTPRINT_SHA2" CXXFLAGS=$CFLAGS --with-crypto --with-curl
YMMV
[2016-01-26 15:00:11] accepted: 6/6 (100.00%), 229.12 kH/s yes!
With:
./configure CFLAGS="-march=nehalem -Ofast -fomit-frame-pointer -Wno-write-strings -funroll-loops -fvariable-expansion-in-unroller -ftree-loop-if-convert-stores -fmerge-all-constants -fbranch-target-load-optimize -fsched2-use-superblocks -DNO_AES_NI -DSPH_SMALL_FOOTPRINT_HAVAL -DSPH_KECCAK_UNROLL=1 -DSPH_KECCAK_NOCOPY -DSPH_KECCAK_INTERLEAVE=0 -DSPH_SMALL_FOOTPRINT_SHA2" CXXFLAGS=$CFLAGS --with-crypto --with-curl
YMMV
Did you get that from Wolf0's cryptonight? Yet another thing to look into is all those compiler switches.
Some are obvious by their name but other I have no clue, yet.
January 26, 2016, 12:09:51 PM
It doesn't support AES, it's a Nehalem.
I think the miner should be compiled with the best "-march" as it will impact the performance of most kernels, regardless how far your optimisations will go.
On a side note, I've found out that -march=native may lead to slower binaries than -march=
I think the miner should be compiled with the best "-march" as it will impact the performance of most kernels, regardless how far your optimisations will go.
On a side note, I've found out that -march=native may lead to slower binaries than -march=
AFAIK corei7-avx is tops do you know of anything better?
The best is your right chipset name:
https://gcc.gnu.org/onlinedocs/gcc-4.9.2/gcc/i386-and-x86-64-Options.html
I was looking for something like that. It works down to nocona, only one generation
older than core2 and the first with X86_64. It looks like the legacy code can be tossed
unless I want to try supporting 32 bit. Naaah.
I will include a link to that page in the build instructions.
Edit: Core2 includes SSE4.1 and I recall seeing some hooks for that in the code. I may be able
to define a new second tier for core 2 and better and improve their performance.
Edit2: I tried haswell down to sandybride and none worked. corei7-avx worked. I'll do some
performance comparisons to see if it makes a difference on my haswell.
January 26, 2016, 09:30:31 AM
Even more (x11):
[2016-01-26 15:00:11] accepted: 6/6 (100.00%), 229.12 kH/s yes!
With:
./configure CFLAGS="-march=nehalem -Ofast -fomit-frame-pointer -Wno-write-strings -funroll-loops -fvariable-expansion-in-unroller -ftree-loop-if-convert-stores -fmerge-all-constants -fbranch-target-load-optimize -fsched2-use-superblocks -DNO_AES_NI -DSPH_SMALL_FOOTPRINT_HAVAL -DSPH_KECCAK_UNROLL=1 -DSPH_KECCAK_NOCOPY -DSPH_KECCAK_INTERLEAVE=0 -DSPH_SMALL_FOOTPRINT_SHA2" CXXFLAGS=$CFLAGS --with-crypto --with-curl
YMMV
[2016-01-26 15:00:11] accepted: 6/6 (100.00%), 229.12 kH/s yes!
With:
./configure CFLAGS="-march=nehalem -Ofast -fomit-frame-pointer -Wno-write-strings -funroll-loops -fvariable-expansion-in-unroller -ftree-loop-if-convert-stores -fmerge-all-constants -fbranch-target-load-optimize -fsched2-use-superblocks -DNO_AES_NI -DSPH_SMALL_FOOTPRINT_HAVAL -DSPH_KECCAK_UNROLL=1 -DSPH_KECCAK_NOCOPY -DSPH_KECCAK_INTERLEAVE=0 -DSPH_SMALL_FOOTPRINT_SHA2" CXXFLAGS=$CFLAGS --with-crypto --with-curl
YMMV
January 26, 2016, 09:22:48 AM
a little speedup by better compiling:
Intel(R) Core(TM) i5 CPU 760 @ 2.80GHz
AES_NI: No.
SSE2: No, start mining without optimizations...
[....]
[2016-01-26 13:39:37] accepted: 7/7 (100.00%), 224.92 kH/s yes!
about 5-10% more by using this commandline (to be adapted to your own cpu):
./configure CFLAGS="-march=nehalem -Ofast -DNO_AES_NI" CXXFLAGS=$CFLAGS --with-crypto --with-curl
and remember to "make clean"
Intel(R) Core(TM) i5 CPU 760 @ 2.80GHz
AES_NI: No.
SSE2: No, start mining without optimizations...
[....]
[2016-01-26 13:39:37] accepted: 7/7 (100.00%), 224.92 kH/s yes!
about 5-10% more by using this commandline (to be adapted to your own cpu):
./configure CFLAGS="-march=nehalem -Ofast -DNO_AES_NI" CXXFLAGS=$CFLAGS --with-crypto --with-curl
and remember to "make clean"
Think any of this would help me to get a completion compile on the problem AMD system I posted about a few pages back?
https://bitcointalksearch.org/topic/m.13657053
the cpu doesn't look to have AES: did you try compiling with -DNO_AES_NI?
January 26, 2016, 08:58:08 AM
a little speedup by better compiling:
Intel(R) Core(TM) i5 CPU 760 @ 2.80GHz
AES_NI: No.
SSE2: No, start mining without optimizations...
[....]
[2016-01-26 13:39:37] accepted: 7/7 (100.00%), 224.92 kH/s yes!
about 5-10% more by using this commandline (to be adapted to your own cpu):
./configure CFLAGS="-march=nehalem -Ofast -DNO_AES_NI" CXXFLAGS=$CFLAGS --with-crypto --with-curl
and remember to "make clean"
Intel(R) Core(TM) i5 CPU 760 @ 2.80GHz
AES_NI: No.
SSE2: No, start mining without optimizations...
[....]
[2016-01-26 13:39:37] accepted: 7/7 (100.00%), 224.92 kH/s yes!
about 5-10% more by using this commandline (to be adapted to your own cpu):
./configure CFLAGS="-march=nehalem -Ofast -DNO_AES_NI" CXXFLAGS=$CFLAGS --with-crypto --with-curl
and remember to "make clean"
Think any of this would help me to get a completion compile on the problem AMD system I posted about a few pages back?
https://bitcointalksearch.org/topic/m.13657053
January 26, 2016, 07:55:58 AM
a little speedup by better compiling:
Intel(R) Core(TM) i5 CPU 760 @ 2.80GHz
AES_NI: No.
SSE2: No, start mining without optimizations...
[....]
[2016-01-26 13:39:37] accepted: 7/7 (100.00%), 224.92 kH/s yes!
about 5-10% more by using this commandline (to be adapted to your own cpu):
./configure CFLAGS="-march=nehalem -Ofast -DNO_AES_NI" CXXFLAGS=$CFLAGS --with-crypto --with-curl
and remember to "make clean"
Intel(R) Core(TM) i5 CPU 760 @ 2.80GHz
AES_NI: No.
SSE2: No, start mining without optimizations...
[....]
[2016-01-26 13:39:37] accepted: 7/7 (100.00%), 224.92 kH/s yes!
about 5-10% more by using this commandline (to be adapted to your own cpu):
./configure CFLAGS="-march=nehalem -Ofast -DNO_AES_NI" CXXFLAGS=$CFLAGS --with-crypto --with-curl
and remember to "make clean"
January 26, 2016, 06:50:36 AM
It doesn't support AES, it's a Nehalem.
I think the miner should be compiled with the best "-march" as it will impact the performance of most kernels, regardless how far your optimisations will go.
On a side note, I've found out that -march=native may lead to slower binaries than -march=
I think the miner should be compiled with the best "-march" as it will impact the performance of most kernels, regardless how far your optimisations will go.
On a side note, I've found out that -march=native may lead to slower binaries than -march=
AFAIK corei7-avx is tops do you know of anything better?
The best is your right chipset name:
https://gcc.gnu.org/onlinedocs/gcc-4.9.2/gcc/i386-and-x86-64-Options.html
January 26, 2016, 06:20:45 AM
not exactly : http://ccminer.org/slackex/
Cool. I didn't mean slack was obsolete, just that people who like it are old school.
I've played with it but never any real work. At one time I had 8 different distros
multibooted on 2 20GB HDDs running on a pentium 1. Now the're all in VMs.
A guy I used to work with was a slackware fan. Give him the keyboard, toss the mouse,
and he could do magic. He's was also pretty sharp in networking, knew his protocols
inside out.
I started using Linux with Slackware 2.0 :-)
RH 5.2 for me, bought the CDs. I discovered Slack around v5 or 6, when PV was sick
and out of action for a while.
January 26, 2016, 06:05:38 AM
Is it correct that "SSE2: No"?
AFAICS, it runs fast anyway.
Checking CPU capatibility...
Intel(R) Core(TM) i5 CPU 760 @ 2.80GHz
AES_NI: No.
SSE2: No, start mining without optimizations...
[2016-01-26 10:17:55] Starting Stratum on stratum+tcp://hashpower.co:3533
[2016-01-26 10:17:56] 4 miner threads started, using 'x11' algorithm.
[2016-01-26 10:17:56] Stratum difficulty set to 0.016
[2016-01-26 10:17:56] hashpower.co:3533 x11 block 1821843
[2016-01-26 10:17:56] hashpower.co:3533 x11 block 108239
[2016-01-26 10:18:01] CPU #1: 57.09 kH/s
[2016-01-26 10:18:01] CPU #0: 56.81 kH/s
[2016-01-26 10:18:01] CPU #2: 53.73 kH/s
[2016-01-26 10:18:02] CPU #3: 52.40 kH/s
[2016-01-26 10:18:18] CPU #0: 56.23 kH/s
[2016-01-26 10:18:18] CPU #3: 53.29 kH/s
[2016-01-26 10:18:18] CPU #1: 56.55 kH/s
[2016-01-26 10:18:18] CPU #2: 56.11 kH/s
AFAICS, it runs fast anyway.
Checking CPU capatibility...
Intel(R) Core(TM) i5 CPU 760 @ 2.80GHz
AES_NI: No.
SSE2: No, start mining without optimizations...
[2016-01-26 10:17:55] Starting Stratum on stratum+tcp://hashpower.co:3533
[2016-01-26 10:17:56] 4 miner threads started, using 'x11' algorithm.
[2016-01-26 10:17:56] Stratum difficulty set to 0.016
[2016-01-26 10:17:56] hashpower.co:3533 x11 block 1821843
[2016-01-26 10:17:56] hashpower.co:3533 x11 block 108239
[2016-01-26 10:18:01] CPU #1: 57.09 kH/s
[2016-01-26 10:18:01] CPU #0: 56.81 kH/s
[2016-01-26 10:18:01] CPU #2: 53.73 kH/s
[2016-01-26 10:18:02] CPU #3: 52.40 kH/s
[2016-01-26 10:18:18] CPU #0: 56.23 kH/s
[2016-01-26 10:18:18] CPU #3: 53.29 kH/s
[2016-01-26 10:18:18] CPU #1: 56.55 kH/s
[2016-01-26 10:18:18] CPU #2: 56.11 kH/s
Nope, it's a bug. I think it will be irelevant when I implement X86_64 compiling.
But "-march=x86_64" won't configure. I don't know if it's the wrong target name or
if GCC has dumped support for it. Maybe I need to install some compat packages.
Edit: just checking your output again. even though it says no for SSE2 it should
still the SSE2 kernel. Formyour hashrate it appears to be normal for and i5 SSE2.
I guess the early corei didn't have AES_NI. Do you want to give it try to make sure?
Just edit cpu-miner.c:1949 and hardcode cpu_aesni=true. Then compile with AES_NI
enabled and let me know if it works.
Thanks
I intalled the x86_64 cross compiler and it still doesn't work.
January 26, 2016, 06:04:25 AM
Is it correct that "SSE2: No"?
AFAICS, it runs fast anyway.
Checking CPU capatibility...
Intel(R) Core(TM) i5 CPU 760 @ 2.80GHz
AES_NI: No.
SSE2: No, start mining without optimizations...
[2016-01-26 10:17:55] Starting Stratum on stratum+tcp://hashpower.co:3533
[2016-01-26 10:17:56] 4 miner threads started, using 'x11' algorithm.
[2016-01-26 10:17:56] Stratum difficulty set to 0.016
[2016-01-26 10:17:56] hashpower.co:3533 x11 block 1821843
[2016-01-26 10:17:56] hashpower.co:3533 x11 block 108239
[2016-01-26 10:18:01] CPU #1: 57.09 kH/s
[2016-01-26 10:18:01] CPU #0: 56.81 kH/s
[2016-01-26 10:18:01] CPU #2: 53.73 kH/s
[2016-01-26 10:18:02] CPU #3: 52.40 kH/s
[2016-01-26 10:18:18] CPU #0: 56.23 kH/s
[2016-01-26 10:18:18] CPU #3: 53.29 kH/s
[2016-01-26 10:18:18] CPU #1: 56.55 kH/s
[2016-01-26 10:18:18] CPU #2: 56.11 kH/s
AFAICS, it runs fast anyway.
Checking CPU capatibility...
Intel(R) Core(TM) i5 CPU 760 @ 2.80GHz
AES_NI: No.
SSE2: No, start mining without optimizations...
[2016-01-26 10:17:55] Starting Stratum on stratum+tcp://hashpower.co:3533
[2016-01-26 10:17:56] 4 miner threads started, using 'x11' algorithm.
[2016-01-26 10:17:56] Stratum difficulty set to 0.016
[2016-01-26 10:17:56] hashpower.co:3533 x11 block 1821843
[2016-01-26 10:17:56] hashpower.co:3533 x11 block 108239
[2016-01-26 10:18:01] CPU #1: 57.09 kH/s
[2016-01-26 10:18:01] CPU #0: 56.81 kH/s
[2016-01-26 10:18:01] CPU #2: 53.73 kH/s
[2016-01-26 10:18:02] CPU #3: 52.40 kH/s
[2016-01-26 10:18:18] CPU #0: 56.23 kH/s
[2016-01-26 10:18:18] CPU #3: 53.29 kH/s
[2016-01-26 10:18:18] CPU #1: 56.55 kH/s
[2016-01-26 10:18:18] CPU #2: 56.11 kH/s
Nope, it's a bug. I think it will be irelevant when I implement X86_64 compiling.
But "-march=x86_64" won't configure. I don't know if it's the wrong target name or
if GCC has dumped support for it. Maybe I need to install some compat packages.
Edit: just checking your output again. even though it says no for SSE2 it should
still the SSE2 kernel. Formyour hashrate it appears to be normal for and i5 SSE2.
I guess the early corei didn't have AES_NI. Do you want to give it try to make sure?
Just edit cpu-miner.c:1949 and hardcode cpu_aesni=true. Then compile with AES_NI
enabled and let me know if it works.
Thanks
It doesn't support AES, it's a Nehalem.
I think the miner should be compiled with the best "-march" as it will impact the performance of most kernels, regardless how far your optimisations will go.
On a side note, I've found out that -march=native may lead to slower binaries than -march=
AFAIK corei7-avx is tops do you know of anything better?
January 26, 2016, 05:57:24 AM
Is it correct that "SSE2: No"?
AFAICS, it runs fast anyway.
Checking CPU capatibility...
Intel(R) Core(TM) i5 CPU 760 @ 2.80GHz
AES_NI: No.
SSE2: No, start mining without optimizations...
[2016-01-26 10:17:55] Starting Stratum on stratum+tcp://hashpower.co:3533
[2016-01-26 10:17:56] 4 miner threads started, using 'x11' algorithm.
[2016-01-26 10:17:56] Stratum difficulty set to 0.016
[2016-01-26 10:17:56] hashpower.co:3533 x11 block 1821843
[2016-01-26 10:17:56] hashpower.co:3533 x11 block 108239
[2016-01-26 10:18:01] CPU #1: 57.09 kH/s
[2016-01-26 10:18:01] CPU #0: 56.81 kH/s
[2016-01-26 10:18:01] CPU #2: 53.73 kH/s
[2016-01-26 10:18:02] CPU #3: 52.40 kH/s
[2016-01-26 10:18:18] CPU #0: 56.23 kH/s
[2016-01-26 10:18:18] CPU #3: 53.29 kH/s
[2016-01-26 10:18:18] CPU #1: 56.55 kH/s
[2016-01-26 10:18:18] CPU #2: 56.11 kH/s
AFAICS, it runs fast anyway.
Checking CPU capatibility...
Intel(R) Core(TM) i5 CPU 760 @ 2.80GHz
AES_NI: No.
SSE2: No, start mining without optimizations...
[2016-01-26 10:17:55] Starting Stratum on stratum+tcp://hashpower.co:3533
[2016-01-26 10:17:56] 4 miner threads started, using 'x11' algorithm.
[2016-01-26 10:17:56] Stratum difficulty set to 0.016
[2016-01-26 10:17:56] hashpower.co:3533 x11 block 1821843
[2016-01-26 10:17:56] hashpower.co:3533 x11 block 108239
[2016-01-26 10:18:01] CPU #1: 57.09 kH/s
[2016-01-26 10:18:01] CPU #0: 56.81 kH/s
[2016-01-26 10:18:01] CPU #2: 53.73 kH/s
[2016-01-26 10:18:02] CPU #3: 52.40 kH/s
[2016-01-26 10:18:18] CPU #0: 56.23 kH/s
[2016-01-26 10:18:18] CPU #3: 53.29 kH/s
[2016-01-26 10:18:18] CPU #1: 56.55 kH/s
[2016-01-26 10:18:18] CPU #2: 56.11 kH/s
Nope, it's a bug. I think it will be irelevant when I implement X86_64 compiling.
But "-march=x86_64" won't configure. I don't know if it's the wrong target name or
if GCC has dumped support for it. Maybe I need to install some compat packages.
Edit: just checking your output again. even though it says no for SSE2 it should
still the SSE2 kernel. Formyour hashrate it appears to be normal for and i5 SSE2.
I guess the early corei didn't have AES_NI. Do you want to give it try to make sure?
Just edit cpu-miner.c:1949 and hardcode cpu_aesni=true. Then compile with AES_NI
enabled and let me know if it works.
Thanks
It doesn't support AES, it's a Nehalem.
I think the miner should be compiled with the best "-march" as it will impact the performance of most kernels, regardless how far your optimisations will go.
On a side note, I've found out that -march=native may lead to slower binaries than -march=
January 26, 2016, 05:41:19 AM
No source? I want to import the Intel GPU mining. I wanna expand my territory.
January 26, 2016, 05:16:21 AM
Is it correct that "SSE2: No"?
AFAICS, it runs fast anyway.
Checking CPU capatibility...
Intel(R) Core(TM) i5 CPU 760 @ 2.80GHz
AES_NI: No.
SSE2: No, start mining without optimizations...
[2016-01-26 10:17:55] Starting Stratum on stratum+tcp://hashpower.co:3533
[2016-01-26 10:17:56] 4 miner threads started, using 'x11' algorithm.
[2016-01-26 10:17:56] Stratum difficulty set to 0.016
[2016-01-26 10:17:56] hashpower.co:3533 x11 block 1821843
[2016-01-26 10:17:56] hashpower.co:3533 x11 block 108239
[2016-01-26 10:18:01] CPU #1: 57.09 kH/s
[2016-01-26 10:18:01] CPU #0: 56.81 kH/s
[2016-01-26 10:18:01] CPU #2: 53.73 kH/s
[2016-01-26 10:18:02] CPU #3: 52.40 kH/s
[2016-01-26 10:18:18] CPU #0: 56.23 kH/s
[2016-01-26 10:18:18] CPU #3: 53.29 kH/s
[2016-01-26 10:18:18] CPU #1: 56.55 kH/s
[2016-01-26 10:18:18] CPU #2: 56.11 kH/s
AFAICS, it runs fast anyway.
Checking CPU capatibility...
Intel(R) Core(TM) i5 CPU 760 @ 2.80GHz
AES_NI: No.
SSE2: No, start mining without optimizations...
[2016-01-26 10:17:55] Starting Stratum on stratum+tcp://hashpower.co:3533
[2016-01-26 10:17:56] 4 miner threads started, using 'x11' algorithm.
[2016-01-26 10:17:56] Stratum difficulty set to 0.016
[2016-01-26 10:17:56] hashpower.co:3533 x11 block 1821843
[2016-01-26 10:17:56] hashpower.co:3533 x11 block 108239
[2016-01-26 10:18:01] CPU #1: 57.09 kH/s
[2016-01-26 10:18:01] CPU #0: 56.81 kH/s
[2016-01-26 10:18:01] CPU #2: 53.73 kH/s
[2016-01-26 10:18:02] CPU #3: 52.40 kH/s
[2016-01-26 10:18:18] CPU #0: 56.23 kH/s
[2016-01-26 10:18:18] CPU #3: 53.29 kH/s
[2016-01-26 10:18:18] CPU #1: 56.55 kH/s
[2016-01-26 10:18:18] CPU #2: 56.11 kH/s
Nope, it's a bug. I think it will be irelevant when I implement X86_64 compiling.
But "-march=x86_64" won't configure. I don't know if it's the wrong target name or
if GCC has dumped support for it. Maybe I need to install some compat packages.
Edit: just checking your output again. even though it says no for SSE2 it should
still the SSE2 kernel. Formyour hashrate it appears to be normal for and i5 SSE2.
I guess the early corei didn't have AES_NI. Do you want to give it try to make sure?
Just edit cpu-miner.c:1949 and hardcode cpu_aesni=true. Then compile with AES_NI
enabled and let me know if it works.
Thanks
Edit2: I intalled the x86_64 cross compiler and it still doesn;t work.
Jump to: