Bitcoin Forum
June 23, 2017, 10:42:30 PM *
News: Latest stable version of Bitcoin Core: 0.14.2  [Torrent].
 
   Home   Help Search Donate Login Register  
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 62 63 »
  Print  
Author Topic: An (even more) optimized version of cpuminer (pooler's cpuminer, CPU-only)  (Read 1673615 times)
linelec
Full Member
***
Offline Offline

Activity: 210


View Profile WWW
May 05, 2014, 05:28:22 PM
 #981


Please provide the contents of config.log and the full output of make (use a pastebin).

Ok,

http://pastebin.com/TR9wbbnw

Quote
Are you building from the tarball or from the git repo?

From tarball, "pooler-cpuminer-2.3.3.tar.gz"

/EDIT/

Compiled on RaspBerry PI with the same distribution, Slackware14.1 ARM, it work  Grin  Huh

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

Activity: 675


View Profile
May 05, 2014, 08:12:30 PM
 #982

Please provide the contents of config.log and the full output of make (use a pastebin).

Ok, http://pastebin.com/TR9wbbnw

Quote
Are you building from the tarball or from the git repo?

From tarball, "pooler-cpuminer-2.3.3.tar.gz"

Please also provide the full output of "make clean && make", as well as the output of the following:
Code:
gcc -dM -E - < /dev/null | sort

EDIT: You are using the x86_64 version of Slackware 14.1, right? Please provide the output of "uname -a".

BTC: 15MRTcUweNVJbhTyH5rq9aeSdyigFrskqE · LTC: LTCPooLqTK1SANSNeTR63GbGwabTKEkuS7
linelec
Full Member
***
Offline Offline

Activity: 210


View Profile WWW
May 06, 2014, 02:03:44 AM
 #983



Please also provide the full output of "make clean && make"

http://pastebin.com/jvXKaNPy

Quote
as well as the output of the following:
Code:
gcc -dM -E - < /dev/null | sort

http://pastebin.com/kYzxAmj4


Quote
EDIT: You are using the x86_64 version of Slackware 14.1, right? Please provide the output of "uname -a".

Funny that you mention that - I've just realised today that the AMD Sempron was a 64  Embarrassed

3.10.17 #2 SMP Fri Feb 14 16:45:28 CST 2014 x86_64 AMD Sempron(tm) Processor LE-1200 AuthenticAMD GNU/Linux

So I run a Slackware 32 on a 64 CPU  Shocked

pooler
Hero Member
*****
Offline Offline

Activity: 675


View Profile
May 06, 2014, 10:41:11 AM
 #984

3.10.17 #2 SMP Fri Feb 14 16:45:28 CST 2014 x86_64 AMD Sempron(tm) Processor LE-1200 AuthenticAMD GNU/Linux

So I run a Slackware 32 on a 64 CPU  Shocked

It looks like something is wrong with your environment. You say that you're on an x86 version of Slackware, and gcc seems to confirm that:
Code:
Target: i486-slackware-linux
But then why do arch and uname report "x86_64" as the architecture?

Out of curiosity, I tried installing Slackware 14.1 in QEMU, and arch reported i686 as expected. I was able to build cpuminer just fine.

BTC: 15MRTcUweNVJbhTyH5rq9aeSdyigFrskqE · LTC: LTCPooLqTK1SANSNeTR63GbGwabTKEkuS7
linelec
Full Member
***
Offline Offline

Activity: 210


View Profile WWW
May 06, 2014, 05:51:40 PM
 #985


It looks like something is wrong with your environment. You say that you're on an x86 version of Slackware, and gcc seems to confirm that:
Code:
Target: i486-slackware-linux
But then why do arch and uname report "x86_64" as the architecture?
 

Because the AMD Sempron is a 64bits?

Code:
uname --help
....
-m, --machine            print the machine hardware name
...

Code:
$ uname -m

x86_64



Previously I've built the AVR tool chain without problem (GCC, binutils, AVRlibC, etc...) on this configuration.

http://www.nongnu.org/avr-libc/


The compilation of "cgminer" was also OK.





pooler
Hero Member
*****
Offline Offline

Activity: 675


View Profile
May 06, 2014, 06:53:33 PM
 #986


It looks like something is wrong with your environment. You say that you're on an x86 version of Slackware, and gcc seems to confirm that:
Code:
Target: i486-slackware-linux
But then why do arch and uname report "x86_64" as the architecture?

Because the AMD Sempron is a 64bits?

As far as I know, that's not how it works. arch should report the architecture in use, not what the hardware is or may be capable of. As a matter of fact, x86 and x86_64 are two distinct architectures; you cannot run a 64-bit binary if you're using a 32-bit kernel. Are you running a 64-bit kernel with a 32-bit userspace, by any chance?

Anyway, as you can see from config.log, the configure script detects "x86_64-unknown-linux-gnu" as the target, which conflicts with your compiler being for x86. Maybe try passing --target=i686-unknown-linux-gnu to configure.

Previously I've built the AVR tool chain without problem (GCC, binutils, AVRlibC, etc...) on this configuration.
http://www.nongnu.org/avr-libc/
The compilation of "cgminer" was also OK.
Unfortunately that's not very relevant here, as cgminer does not need to make fine distinctions between x86 and x86_64.

BTC: 15MRTcUweNVJbhTyH5rq9aeSdyigFrskqE · LTC: LTCPooLqTK1SANSNeTR63GbGwabTKEkuS7
linelec
Full Member
***
Offline Offline

Activity: 210


View Profile WWW
May 06, 2014, 09:39:55 PM
 #987


Anyway, as you can see from config.log, the configure script detects "x86_64-unknown-linux-gnu" as the target, which conflicts with your compiler being for x86. Maybe try passing --target=i686-unknown-linux-gnu to configure.

Thanks ! Now it work !  Grin

As soon as possible I'll install the Slackware 64 bits version on this PC


romeshomey
Hero Member
*****
Offline Offline

Activity: 538


View Profile
May 07, 2014, 02:04:45 AM
 #988

Any idea why I can't seem to get cpuminer to work solo mining?

It crashes right after minerd.exe executes.   I have no problems pool mining. 

Code:
minerd.exe --freq=850 --gc3355=COM3 --gc3355-chips=5 -o 192.168.0.100:35882 -u user.worker -p pass
captainproton
Jr. Member
*
Offline Offline

Activity: 38


View Profile WWW
May 11, 2014, 05:04:56 AM
 #989

For some reason I'm having trouble mining MemoryCoin. Keep getting json errors.

Version cpuminer 2.3.3
libcurl/7.35.0 zlib/1.2.8

I'm using mmcpool.com

Has anyone else had this problem?

This is a Virtual Stick Up - Give me all your BTC!
pooler
Hero Member
*****
Offline Offline

Activity: 675


View Profile
May 11, 2014, 07:22:19 AM
 #990

Any idea why I can't seem to get cpuminer to work solo mining?
It crashes right after minerd.exe executes.   I have no problems pool mining.  
Code:
minerd.exe --freq=850 --gc3355=COM3 --gc3355-chips=5 -o 192.168.0.100:35882 -u user.worker -p pass
Wrong thread. The cpuminer discussed in this thread is for CPU mining only.

For some reason I'm having trouble mining MemoryCoin. Keep getting json errors.
Version cpuminer 2.3.3
libcurl/7.35.0 zlib/1.2.8
I'm using mmcpool.com
Has anyone else had this problem?
MemoryCoin is not currently supported. If you are using a fork of this project, you should contact its author.

BTC: 15MRTcUweNVJbhTyH5rq9aeSdyigFrskqE · LTC: LTCPooLqTK1SANSNeTR63GbGwabTKEkuS7
Dark Leaf
Newbie
*
Offline Offline

Activity: 1


View Profile
May 15, 2014, 11:40:17 PM
 #991

I wanted to try out darkcoin-cpuminer-1.3-avx-aes and I fail to compile it on stock Ubuntu 14.04 64-bit server.

Here's what I do:
Code:
sudo apt-get install automake build-essential git libcurl4-gnutls-dev -y
git clone https://github.com/elmad/darkcoin-cpuminer-1.3-avx-aes.git
cd darkcoin-cpuminer-1.3-avx-aes
./autogen.sh
./configure CFLAGS="-O3"
make -j 8
And I get the following errors.

What can I do?
Massimo80
Full Member
***
Offline Offline

Activity: 168


View Profile
May 16, 2014, 06:45:21 AM
 #992

What can I do?

Avoid posting in the wrong thread.

It should help.
Oldminer
Legendary
*
Offline Offline

Activity: 1022



View Profile
May 16, 2014, 01:40:47 PM
 #993

Loving cpuminer  Grin


If you like my post please feel free to give me some positive rep https://bitcointalk.org/index.php?action=trust;u=18639
Tip me BTC: 1FBmoYijXVizfYk25CpiN8Eds9J6YiRDaX
iklajo
Jr. Member
*
Offline Offline

Activity: 46


View Profile
May 17, 2014, 02:24:21 AM
 #994

Loving cpuminer  Grin




2.7MH/s with 800Mhz ... What do you mine and with what do you mine?

Get a 3% discount on all new contracts @ Genesis Mining with promo code : 05PaSf
Netscout
Newbie
*
Offline Offline

Activity: 17


View Profile
May 17, 2014, 12:50:00 PM
 #995



2.7MH/s with 800Mhz ... What do you mine and with what do you mine?

stratum+tcp://us-east2.multipool.us:7777 = scrypt
iklajo
Jr. Member
*
Offline Offline

Activity: 46


View Profile
May 17, 2014, 06:29:15 PM
 #996

stratum+tcp://us-east2.multipool.us:7777 = scrypt

I figured that out, just don't know what device it is. Is it the Gridseed G-Blade?

Get a 3% discount on all new contracts @ Genesis Mining with promo code : 05PaSf
pooler
Hero Member
*****
Offline Offline

Activity: 675


View Profile
May 20, 2014, 12:38:44 PM
 #997

Version 2.4

  • Support for getblocktemplate (GBT, BIP 22). With getwork deprecated and soon to be removed from Bitcoin, it was important to get this implemented, especially for testing solo mining. The getblocktemplate method is now used by default for protocol HTTP, but the miner should automatically switch to getwork if the newer method is not available. To force the miner to use getwork, a --no-gbt option is provided.
  • It is now possible to tunnel Stratum through an HTTP proxy.
  • A --no-redirect option has been added, which makes the miner ignore redirection/reconnection requests coming from the server.
  • Startup error messages are now more descriptive.
  • The output of the --version option has been expanded to include additional build information.

The source code is, as always, available at GitHub. Source tarball and binaries are available at Sourceforge.

BTC: 15MRTcUweNVJbhTyH5rq9aeSdyigFrskqE · LTC: LTCPooLqTK1SANSNeTR63GbGwabTKEkuS7
PSL
Member
**
Offline Offline

Activity: 113


View Profile
May 21, 2014, 11:18:42 AM
 #998

Version 2.4

  • Support for getblocktemplate (GBT, BIP 22). With getwork deprecated and soon to be removed from Bitcoin, it was important to get this implemented, especially for testing solo mining. The getblocktemplate method is now used by default for protocol HTTP, but the miner should automatically switch to getwork if the newer method is not available. To force the miner to use getwork, a --no-gbt option is provided.

I found that for solo mining with cpuminer V1.4 I have to extend command line with parameter
--no-gbt or --coinbase-addr otherwise it will not connect to the "coin server":
Code:
[2014-05-21 13:05:06] No payout address provided
[2014-05-21 13:05:06] json_rpc_call failed, retry after 30 seconds

BTW, I think this is a cpuminer bug that it doesn't try to switch to getwork protocol and stays in never-ending loop waiting for a miracle...

I added --coinbase-addr because I think it can address a problem with wallet design, where it is not possible to export default key (at least I failed to find how to do it) and I have to keep backup of binary wallet that is far from perfect.

I test it at the moment, no block was found so far and that could be an indicator that something is wrong... Maybe I have only bad luck...

I found bfgminer notice, that when several clients are connected to the same "coin server" and are mining to the same address, than parameter --coinbase-sig has to be added

https://github.com/luke-jr/bfgminer, section SOLO MINING.

Is it true that --coinbase-sig with unique parameter has to be added when more clients are connected with the same address?? So far, I just configured all my clients with the same --coinbase-addr address but I am not sure if this is good idea because it is possible that they work on the same units and my computing power is reduces compared to configuration with --no-gbt (operation mode of older cpuminer)...
pooler
Hero Member
*****
Offline Offline

Activity: 675


View Profile
May 21, 2014, 11:38:10 AM
 #999

I found that for solo mining with cpuminer V2.4 I have to extend command line with parameter --no-gbt or --coinbase-addr otherwhise it will not connect to the "coin server".
That is correct. If you pass --no-gbt the miner will use the legacy getwork method, so all the block building is handled by the server. If on the other hand you want to use getblocktemplate for solo mining, then you have to provide a payout address.

Quote
I found bfgminer notice, that when several clients are connected to the same "coin server" and are mining to the same address, then parameter --coinbase-sig has to be added

https://github.com/luke-jr/bfgminer, section SOLO MINING.

Is it true that --coinbase-sig with unique parameter has to be added when more clients are connected with the same address?
Yes. If you intend to have multiple miners mining solo to the same address, each of them should specify a different signature. Alternatively, you can specify a different address for each miner.

BTC: 15MRTcUweNVJbhTyH5rq9aeSdyigFrskqE · LTC: LTCPooLqTK1SANSNeTR63GbGwabTKEkuS7
PSL
Member
**
Offline Offline

Activity: 113


View Profile
May 21, 2014, 12:25:03 PM
 #1000

Quote
I found bfgminer notice, that when several clients are connected to the same "coin server" and are mining to the same address, then parameter --coinbase-sig has to be added

https://github.com/luke-jr/bfgminer, section SOLO MINING.

Is it true that --coinbase-sig with unique parameter has to be added when more clients are connected with the same address?
Yes. If you intend to have multiple miners mining solo to the same address, each of them should specify a different signature. Alternatively, you can specify a different address for each miner.

Thank you for confirmation. That is bad news... I have a problem with a signature, it will be put to blockchain and everyone can see it. Is there other possibility to mine with the same address but without creating public message in the blockchain? Could be this addressed with new parameter that will work like signature but it will not be stored to blockchain? It will be just a local ID for mining client, I can use client hostname or IP address or something like that...
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 62 63 »
  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!