Bitcoin Forum
June 06, 2020, 02:58:23 PM *
News: Latest Bitcoin Core release: 0.19.1 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 2 3 4 5 6 7 8 9 10 [11] 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 ... 198 »
  Print  
Author Topic: [LOCKED] cpuminer-opt v3.12.3, open source optimized multi-algo CPU miner  (Read 442037 times)
pallas
Legendary
*
Offline Offline

Activity: 2338
Merit: 1091


Black Belt Developer


View Profile
January 26, 2016, 12:55:58 PM
 #201

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"

Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1591455503
Hero Member
*
Offline Offline

Posts: 1591455503

View Profile Personal Message (Offline)

Ignore
1591455503
Reply with quote  #2

1591455503
Report to moderator
1591455503
Hero Member
*
Offline Offline

Posts: 1591455503

View Profile Personal Message (Offline)

Ignore
1591455503
Reply with quote  #2

1591455503
Report to moderator
1591455503
Hero Member
*
Offline Offline

Posts: 1591455503

View Profile Personal Message (Offline)

Ignore
1591455503
Reply with quote  #2

1591455503
Report to moderator
zTheWolfz
Full Member
***
Offline Offline

Activity: 231
Merit: 150



View Profile
January 26, 2016, 01:58:08 PM
 #202

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"

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://bitcointalk.org/index.php?topic=1326803.msg13657053#msg13657053
pallas
Legendary
*
Offline Offline

Activity: 2338
Merit: 1091


Black Belt Developer


View Profile
January 26, 2016, 02:22:48 PM
 #203

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"

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://bitcointalk.org/index.php?topic=1326803.msg13657053#msg13657053


the cpu doesn't look to have AES: did you try compiling with -DNO_AES_NI?

pallas
Legendary
*
Offline Offline

Activity: 2338
Merit: 1091


Black Belt Developer


View Profile
January 26, 2016, 02:30:31 PM
 #204

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

joblo
Legendary
*
Offline Offline

Activity: 1470
Merit: 1106


View Profile
January 26, 2016, 05:09:51 PM
Last edit: January 26, 2016, 05:35:27 PM by joblo
 #205

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=<the best for your cpu>

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.

AKA JayDDee, cpuminer-opt developer. https://github.com/JayDDee/cpuminer-opt
https://bitcointalk.org/index.php?topic=5226770.msg53865575#msg53865575
BTC: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT,
joblo
Legendary
*
Offline Offline

Activity: 1470
Merit: 1106


View Profile
January 26, 2016, 05:12:28 PM
 #206

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

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.

AKA JayDDee, cpuminer-opt developer. https://github.com/JayDDee/cpuminer-opt
https://bitcointalk.org/index.php?topic=5226770.msg53865575#msg53865575
BTC: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT,
pallas
Legendary
*
Offline Offline

Activity: 2338
Merit: 1091


Black Belt Developer


View Profile
January 26, 2016, 05:43:38 PM
 #207

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

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.

bobben2
Full Member
***
Offline Offline

Activity: 236
Merit: 102


View Profile
January 26, 2016, 05:56:52 PM
 #208

./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!

Fellow miners, get your thens and thans in order and help other forum readers understand what you are writing. Remember the grammar basics:  A larger THAN B (comparator operator). If something THEN ....
zTheWolfz
Full Member
***
Offline Offline

Activity: 231
Merit: 150



View Profile
January 26, 2016, 06:41:39 PM
 #209

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"

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://bitcointalk.org/index.php?topic=1326803.msg13657053#msg13657053


the cpu doesn't look to have AES: did you try compiling with -DNO_AES_NI?
I just tried that and still get errors. maybe someone could help me on this one I'm a real noob with this stuff.

./configure CFLAGS="-march=?HuhHuh?? -Ofast" CXXFLAGS=$CFLAGS --with-crypto --with-curl HuhHuh??

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)

joblo
Legendary
*
Offline Offline

Activity: 1470
Merit: 1106


View Profile
January 26, 2016, 06:46:29 PM
 #210


Mining with an Intel GPU? I need to look into that.

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?

AKA JayDDee, cpuminer-opt developer. https://github.com/JayDDee/cpuminer-opt
https://bitcointalk.org/index.php?topic=5226770.msg53865575#msg53865575
BTC: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT,
zTheWolfz
Full Member
***
Offline Offline

Activity: 231
Merit: 150



View Profile
January 26, 2016, 06:57:04 PM
 #211

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
joblo
Legendary
*
Offline Offline

Activity: 1470
Merit: 1106


View Profile
January 26, 2016, 06:57:34 PM
 #212

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"

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://bitcointalk.org/index.php?topic=1326803.msg13657053#msg13657053


the cpu doesn't look to have AES: did you try compiling with -DNO_AES_NI?
I just tried that and still get errors. maybe someone could help me on this one I'm a real noob with this stuff.

./configure CFLAGS="-march=?HuhHuh?? -Ofast" CXXFLAGS=$CFLAGS --with-crypto --with-curl HuhHuh??

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)



First post your console session with your command line and error messages. *
And stick with the instructions in the READme.md file.

You've got an AMD Opteron 64 so try to find a match
https://gcc.gnu.org/onlinedocs/gcc-4.9.2/gcc/i386-and-x86-64-Options.html

* I can be prickly, so be careful with your questions, This is your first warning.
    I'm not trying to be mean, it just happens, so don't take it personally. Well
    formulated questions with supporting data and a demonstration you did
    your best to solve it will always get the best response (and not just from me).


AKA JayDDee, cpuminer-opt developer. https://github.com/JayDDee/cpuminer-opt
https://bitcointalk.org/index.php?topic=5226770.msg53865575#msg53865575
BTC: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT,
zTheWolfz
Full Member
***
Offline Offline

Activity: 231
Merit: 150



View Profile
January 26, 2016, 07:09:07 PM
 #213

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"

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://bitcointalk.org/index.php?topic=1326803.msg13657053#msg13657053


the cpu doesn't look to have AES: did you try compiling with -DNO_AES_NI?
I just tried that and still get errors. maybe someone could help me on this one I'm a real noob with this stuff.

./configure CFLAGS="-march=?HuhHuh?? -Ofast" CXXFLAGS=$CFLAGS --with-crypto --with-curl HuhHuh??

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)



First post your console session with your command line and error messages. *
And stick with the instructions in the READme.md file.

You've got an AMD Opteron 64 so try to find a match
https://gcc.gnu.org/onlinedocs/gcc-4.9.2/gcc/i386-and-x86-64-Options.html

* I can be prickly, so be careful with your questions, This is your first warning.
    I'm not trying to be mean, it just happens, so don't take it personally. Well
    formulated questions with supporting data and a demonstration you did
    your best to solve it will always get the best response (and not just from me).


Getting closer it does start but hangs at checking the CPU.

Code:
h8qg6@h8qg6-VirtualBox:~/Downloads/cpuminer-opt-3.0.3$ ./cpuminer -a x11 -o stratum+tcp://x11.usa.nicehash.com:3336 -u 18tvS3deKZK5q4eTtPRWYeEMWmGmuErHgz.H8QG6 -p d=0.01 -t 1

         **********  cpuminer-opt  v3.0.3  ***********
     BTC donation address: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT
     Forked from TPruvot's cpuminer-multi-1.2pre with credits
     to Lucas Jones, elmad, palmd, djm34, pooler, ig0tik3d,
     Wolf0 and Jeff Garzik.

Only quark and qubit support SSE at this time. Whenever mining
other algos with an SSE2 capable CPU the generic x86_64 miner
will be used.

Checking CPU capatibility...
joblo
Legendary
*
Offline Offline

Activity: 1470
Merit: 1106


View Profile
January 26, 2016, 07:45:04 PM
Last edit: January 26, 2016, 08:06:12 PM by joblo
 #214

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"

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://bitcointalk.org/index.php?topic=1326803.msg13657053#msg13657053


the cpu doesn't look to have AES: did you try compiling with -DNO_AES_NI?
I just tried that and still get errors. maybe someone could help me on this one I'm a real noob with this stuff.

./configure CFLAGS="-march=?HuhHuh?? -Ofast" CXXFLAGS=$CFLAGS --with-crypto --with-curl HuhHuh??

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)



First post your console session with your command line and error messages. *
And stick with the instructions in the READme.md file.

You've got an AMD Opteron 64 so try to find a match
https://gcc.gnu.org/onlinedocs/gcc-4.9.2/gcc/i386-and-x86-64-Options.html

* I can be prickly, so be careful with your questions, This is your first warning.
    I'm not trying to be mean, it just happens, so don't take it personally. Well
    formulated questions with supporting data and a demonstration you did
    your best to solve it will always get the best response (and not just from me).


Getting closer it does start but hangs at checking the CPU.

Code:
h8qg6@h8qg6-VirtualBox:~/Downloads/cpuminer-opt-3.0.3$ ./cpuminer -a x11 -o stratum+tcp://x11.usa.nicehash.com:3336 -u 18tvS3deKZK5q4eTtPRWYeEMWmGmuErHgz.H8QG6 -p d=0.01 -t 1

         **********  cpuminer-opt  v3.0.3  ***********
     BTC donation address: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT
     Forked from TPruvot's cpuminer-multi-1.2pre with credits
     to Lucas Jones, elmad, palmd, djm34, pooler, ig0tik3d,
     Wolf0 and Jeff Garzik.

Only quark and qubit support SSE at this time. Whenever mining
other algos with an SSE2 capable CPU the generic x86_64 miner
will be used.

Checking CPU capatibility...

Ok now I have something towork with. I have a workaround that requires some code changes.
I will explain the changes in detail so you shouldn't have any problems.

First backup the original.

Edit file cpu-miner.c and make the folllwing changes to block the actual check and hard code the
result.

Replace any calls to has_aesni(), has_sse2 with true
There might be a couple of each.

ex:
change "cpu_aesni = has_aesni();" to "cpu_aesni = true;"

You can also set each one to false if the feature isn't supported but try true for both to start.

remove the call to "check_cpu_capability()" on line 3157. Just delete the line.

Save, compile and run. Let me know how it goes.

Edit:It seems your CPU does not have AES_NI to you will likely have to set cpu_aesni to false
in cpu-miner.c and use -DNO_AES_NI.

AKA JayDDee, cpuminer-opt developer. https://github.com/JayDDee/cpuminer-opt
https://bitcointalk.org/index.php?topic=5226770.msg53865575#msg53865575
BTC: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT,
joblo
Legendary
*
Offline Offline

Activity: 1470
Merit: 1106


View Profile
January 26, 2016, 07:58:57 PM
 #215

Time for another story.

The company I worked for produced lage scale mission critical control systems
to institutional customers. They had an emergency response team that provided
24 hour service with a guarantee the customer was talking to an engineer within
5 minutes of the initial call.

The training for this team was interesting and included getting a call from a senior
engineer posing as a cleaner.

He would call and report that hes just a cleaner working near the computer room
and heard alarms. He went into the room and saw a poster with the phone number
to call in case of an emergency.

You can imagine how it went from there. It even involved getting the cleaner to change
circuit packs. One particular trainer would exploit any ambiguity or imprecision in the
instructions to deliverately do the wrong thing. Lots of fun.

AKA JayDDee, cpuminer-opt developer. https://github.com/JayDDee/cpuminer-opt
https://bitcointalk.org/index.php?topic=5226770.msg53865575#msg53865575
BTC: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT,
joblo
Legendary
*
Offline Offline

Activity: 1470
Merit: 1106


View Profile
January 26, 2016, 08:39:16 PM
 #216

I owuld open discussion  with devs and dev wannabes regarding initializing structs.

It may be trivial but considering my inexperience with c/c++ I'm not clear and
a couple of points.

initializing of contexts is a frequent thing in cpuminer and is done by assigning
each field one by one, very inefficient.

There are some shortcuts where a copy if an initialized contex is saved and used
to reinitialze using memcpy, much more efficient.

However I am considering whether assigning a nul version of the struct would be
better.

Ex:

typedef struct {blah, blah,blah} ctx_t;
// init null_ctx at compile time
const ctx_t null_ctx = { null_blah, null_blah, null_blah };
// init my_ctx at run time
ctx_t my_ctx = null_ctx;

Am I on the right track? It might not beat memset but it can handle
non-zero null fields.

AKA JayDDee, cpuminer-opt developer. https://github.com/JayDDee/cpuminer-opt
https://bitcointalk.org/index.php?topic=5226770.msg53865575#msg53865575
BTC: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT,
pallas
Legendary
*
Offline Offline

Activity: 2338
Merit: 1091


Black Belt Developer


View Profile
January 26, 2016, 09:08:23 PM
 #217

Honestly I don't think it makes any noticeable difference.
Initialisation is a very little part of the whole hash computation.

joblo
Legendary
*
Offline Offline

Activity: 1470
Merit: 1106


View Profile
January 26, 2016, 09:20:44 PM
 #218

InteI GPU mining with cgminer.

I got the source compiled and it too only does blake256. I tried it and got all rejects
on blake but it works on blakecoin, woopee. But wait, it's not mining with the IGPU
but with my Nvidia GPUs. Crap.

A device query doesn't find the Intel IGPU.

Thoughts?

AKA JayDDee, cpuminer-opt developer. https://github.com/JayDDee/cpuminer-opt
https://bitcointalk.org/index.php?topic=5226770.msg53865575#msg53865575
BTC: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT,
joblo
Legendary
*
Offline Offline

Activity: 1470
Merit: 1106


View Profile
January 26, 2016, 09:24:28 PM
 #219

Honestly I don't think it makes any noticeable difference.
Initialisation is a very little part of the whole hash computation.

I found a measurable difference (<1%) taking the initialisation out of the loop especially the longer
chains with many ctxs to manage. I expect this to have even less. Low priority, I've got better things
to work on.

AKA JayDDee, cpuminer-opt developer. https://github.com/JayDDee/cpuminer-opt
https://bitcointalk.org/index.php?topic=5226770.msg53865575#msg53865575
BTC: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT,
joblo
Legendary
*
Offline Offline

Activity: 1470
Merit: 1106


View Profile
January 26, 2016, 11:41:56 PM
Last edit: January 27, 2016, 03:53:57 AM by joblo
 #220

Tossed away everything I had done with cryptonight and started form scratch.
It took 2 hours to get my first share 180 KH/s.

V3.0.4 coming right up.

Done

Get v3.0.5

Edit: Thanks Wolf0

Edit: I may have overstated the hash rate, more like 170.

AKA JayDDee, cpuminer-opt developer. https://github.com/JayDDee/cpuminer-opt
https://bitcointalk.org/index.php?topic=5226770.msg53865575#msg53865575
BTC: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT,
Pages: « 1 2 3 4 5 6 7 8 9 10 [11] 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 ... 198 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!