New demonstration CPU miner available

[Patches]

Ok... I added chromicant's 5 line patch for byteswap.h which seems to have worked (as far as I can tell), but I then ran into a libcurl problem shown here:

Code:

checking for curl-config... /sw2/bin/curl-config
checking for the version of libcurl... 7.21.2
checking for libcurl >= version 7.10.1... yes
checking whether libcurl is usable... no
configure: error: Missing required libcurl >= 7.10.1

As far as I can tell libcurl was install correctly, but I reinstalled it from fink (http://pdb.finkproject.org/pdb/package.php/libcurl4?rel_id=10.6-x86_64-current-stable) and when that didn't work, I rebuilt it from the latest source (7.21.4; http://curl.haxx.se/download.html). I am not sure if there is something strange or broken about this machine so I will try to compile on another, fresher Mac tomorrow. Curl -v gives:

Code:

curl 7.21.2 (i386-apple-darwin10.6.0) libcurl/7.21.2 OpenSSL/0.9.8l zlib/1.2.3 c-ares/1.7.3 libssh2/1.2.7 librtmp/2.3

[1714020031]

1714020031

[1714020031]

1714020031

[1714020031]

1714020031

[1714020031]

1714020031

[1714020031]

1714020031

[jgarzik]

- Suport --user/--pass options (and "user" and "pass" in config file), as an alternative to the current --userpass

--user/--pass is broken in version 0.8.  Either obtain the latest -git for a fix, or continue to use --userpass until the next release.

[Patches]

So I tried to compile on my newer MacBook Pro (Intel i7; OS 10.6.6) with Xcode (and YASM 1.1.0) installed using the tarball version 0.8 of cpuminer with chromicant's patch. Indeed, the previous issue I had with libcurl seems to be machine-specific thing, but I ran into another problem. The configure runs fine but I run into a "in x86_64/libx8664.a, file was built for unsupported file format which is not the architecture being linked (x86_64)" error while trying to make amd2_sse64 module.    
Here is the output after running make:

Code:

make  all-recursive
Making all in compat
Making all in jansson
gcc -DHAVE_CONFIG_H -I. -I../..     -O3 -Wall -msse2 -MT dump.o -MD -MP -MF .deps/dump.Tpo -c -o dump.o dump.c
mv -f .deps/dump.Tpo .deps/dump.Po
gcc -DHAVE_CONFIG_H -I. -I../..     -O3 -Wall -msse2 -MT hashtable.o -MD -MP -MF .deps/hashtable.Tpo -c -o hashtable.o hashtable.c
mv -f .deps/hashtable.Tpo .deps/hashtable.Po
gcc -DHAVE_CONFIG_H -I. -I../..     -O3 -Wall -msse2 -MT load.o -MD -MP -MF .deps/load.Tpo -c -o load.o load.c
mv -f .deps/load.Tpo .deps/load.Po
gcc -DHAVE_CONFIG_H -I. -I../..     -O3 -Wall -msse2 -MT strbuffer.o -MD -MP -MF .deps/strbuffer.Tpo -c -o strbuffer.o strbuffer.c
mv -f .deps/strbuffer.Tpo .deps/strbuffer.Po
gcc -DHAVE_CONFIG_H -I. -I../..     -O3 -Wall -msse2 -MT utf.o -MD -MP -MF .deps/utf.Tpo -c -o utf.o utf.c
mv -f .deps/utf.Tpo .deps/utf.Po
gcc -DHAVE_CONFIG_H -I. -I../..     -O3 -Wall -msse2 -MT value.o -MD -MP -MF .deps/value.Tpo -c -o value.o value.c
mv -f .deps/value.Tpo .deps/value.Po
rm -f libjansson.a
ar cru libjansson.a dump.o hashtable.o load.o strbuffer.o utf.o value.o 
ranlib libjansson.a
make[3]: Nothing to be done for `all-am'.
Making all in x86_64
/usr/local/bin/yasm -f elf64 sha256_xmm_amd64.asm
rm -f libx8664.a
ar cru libx8664.a sha256_xmm_amd64.o 
ranlib libx8664.a
ranlib: warning for library: libx8664.a the table of contents is empty (no object file members in the library define global symbols)
gcc -DHAVE_CONFIG_H -I. -pthread -fno-strict-aliasing -I./compat/jansson   -DHAS_YASM -O3 -Wall -msse2 -MT cpu-miner.o -MD -MP -MF .deps/cpu-miner.Tpo -c -o cpu-miner.o cpu-miner.c
mv -f .deps/cpu-miner.Tpo .deps/cpu-miner.Po
gcc -DHAVE_CONFIG_H -I. -pthread -fno-strict-aliasing -I./compat/jansson   -DHAS_YASM -O3 -Wall -msse2 -MT util.o -MD -MP -MF .deps/util.Tpo -c -o util.o util.c
mv -f .deps/util.Tpo .deps/util.Po
gcc -DHAVE_CONFIG_H -I. -pthread -fno-strict-aliasing -I./compat/jansson   -DHAS_YASM -O3 -Wall -msse2 -MT sha256_generic.o -MD -MP -MF .deps/sha256_generic.Tpo -c -o sha256_generic.o sha256_generic.c
mv -f .deps/sha256_generic.Tpo .deps/sha256_generic.Po
gcc -DHAVE_CONFIG_H -I. -pthread -fno-strict-aliasing -I./compat/jansson   -DHAS_YASM -O3 -Wall -msse2 -MT sha256_4way.o -MD -MP -MF .deps/sha256_4way.Tpo -c -o sha256_4way.o sha256_4way.c
mv -f .deps/sha256_4way.Tpo .deps/sha256_4way.Po
gcc -DHAVE_CONFIG_H -I. -pthread -fno-strict-aliasing -I./compat/jansson   -DHAS_YASM -O3 -Wall -msse2 -MT sha256_via.o -MD -MP -MF .deps/sha256_via.Tpo -c -o sha256_via.o sha256_via.c
mv -f .deps/sha256_via.Tpo .deps/sha256_via.Po
gcc -DHAVE_CONFIG_H -I. -pthread -fno-strict-aliasing -I./compat/jansson   -DHAS_YASM -O3 -Wall -msse2 -MT sha256_cryptopp.o -MD -MP -MF .deps/sha256_cryptopp.Tpo -c -o sha256_cryptopp.o sha256_cryptopp.c
mv -f .deps/sha256_cryptopp.Tpo .deps/sha256_cryptopp.Po
gcc -DHAVE_CONFIG_H -I. -pthread -fno-strict-aliasing -I./compat/jansson   -DHAS_YASM -O3 -Wall -msse2 -MT sha256_sse2_amd64.o -MD -MP -MF .deps/sha256_sse2_amd64.Tpo -c -o sha256_sse2_amd64.o sha256_sse2_amd64.c
mv -f .deps/sha256_sse2_amd64.Tpo .deps/sha256_sse2_amd64.Po
gcc -DHAS_YASM -O3 -Wall -msse2 -pthread  -o minerd cpu-miner.o util.o sha256_generic.o sha256_4way.o sha256_via.o sha256_cryptopp.o sha256_sse2_amd64.o -lcurl compat/jansson/libjansson.a -lpthread x86_64/libx8664.a 
ld: warning: in x86_64/libx8664.a, file was built for unsupported file format which is not the architecture being linked (x86_64)
Undefined symbols:
  "_CalcSha256_x64", referenced from:
      _scanhash_sse2_64 in sha256_sse2_amd64.o
      _scanhash_sse2_64 in sha256_sse2_amd64.o
ld: symbol(s) not found
collect2: ld returned 1 exit status
make[2]: *** [minerd] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2

Any ideas? If I make without the sse2_amd64 module it builds and runs fine using the original algorithms as you may have guessed.

[geebus]

BitcoinPool.com was updated to add support for jgarzik's CPU miner's long polling requests.

From the client side, Long Polling should be using GET method instead of POST method. That is, for it to be an actual "comet-style" long poll.

Either way though, we now support both GET and POST to long polling side channels.

...and to answer your question (jgarzik) in a completely late fashion, and in a different thread... our pool is "based on" your pool server in the sense that I used your pool as a reference when I wrote my own. However, we're running on a completely different framework, and not using sqlite3.

Great miner btw.

[chromicant]

So I tried to compile on my newer MacBook Pro (Intel i7; OS 10.6.6) with Xcode (and YASM 1.1.0) installed using the tarball version 0.8 of cpuminer with chromicant's patch. Indeed, the previous issue I had with libcurl seems to be machine-specific thing, but I ran into another problem. The configure runs fine but I run into a "in x86_64/libx8664.a, file was built for unsupported file format which is not the architecture being linked (x86_64)" error while trying to make amd2_sse64 module.    
Here is the output after running make:

Code:

Making all in x86_64
/usr/local/bin/yasm -f elf64 sha256_xmm_amd64.asm
rm -f libx8664.a
ar cru libx8664.a sha256_xmm_amd64.o 
ranlib libx8664.a
ranlib: warning for library: libx8664.a the table of contents is empty (no object file members in the library define global symbols)

Any ideas? If I make without the sse2_amd64 module it builds and runs fine using the original algorithms as you may have guessed.

Try replacing "-f elf64" with "-f macho64" in the x86_64/Makefile as a workaround. Also, you need to make sure you're producing a 64-bit binary while you're compiling. Can't remember how to do that with XCode, but if you don't, the SSE2 code as written will fail. The code uses the added registers that come with the x86_64 architecture to prevent reading/writing to memory.

[Patches]

Try replacing "-f elf64" with "-f macho64" in the x86_64/Makefile as a workaround. Also, you need to make sure you're producing a 64-bit binary while you're compiling. Can't remember how to do that with XCode, but if you don't, the SSE2 code as written will fail. The code uses the added registers that come with the x86_64 architecture to prevent reading/writing to memory.

No dice. I ran the configure with the arch x86_64 command like this:

Code:

CFLAGS="-O3 -Wall -msse2 -arch x86_64" ./configure

then edited the x86_64/Makefile as you suggested (elf -> macho). I still get the similar error shown here:

Code:

make  all-recursive
Making all in compat
Making all in jansson
make[3]: Nothing to be done for `all'.
make[3]: Nothing to be done for `all-am'.
Making all in x86_64
make[2]: Nothing to be done for `all'.
gcc -DHAS_YASM -O3 -Wall -msse2 -arch x86_64 -pthread  -o minerd cpu-miner.o util.o sha256_generic.o sha256_4way.o sha256_via.o sha256_cryptopp.o sha256_sse2_amd64.o -lcurl compat/jansson/libjansson.a -lpthread x86_64/libx8664.a 
ld: warning: in x86_64/libx8664.a, file was built for unsupported file format which is not the architecture being linked (x86_64)
Undefined symbols:
  "_CalcSha256_x64", referenced from:
      _scanhash_sse2_64 in sha256_sse2_amd64.o
      _scanhash_sse2_64 in sha256_sse2_amd64.o
ld: symbol(s) not found
collect2: ld returned 1 exit status
make[2]: *** [minerd] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2

Seems like something, perhaps gcc (Version: i686-apple-darwin10-gcc-4.2.1 (GCC) 4.2.1 (Apple Inc. build 5664)) , doesn't like the file x86_64/libx8664.a? That or I am not forcing a proper 64bit build for the confused Mac compiler.

For interest, I installed Debian on a virtual machine on my MacBook Pro and compiled cpuminer with SSE2_64 there with no problem. In fact, it runs quite well in the VM - over 3600 hashes/core/sec on the mobile i7, and over 3000 hashes/core/sec on the older Xeons in the MacPro.

[richy_rich]

I just compiled and ran this on OS X 10.6.6 by creating a byteswap.h and using no more than ./configure and make.  (No special options etc.)

Obviously you'll need the OS X developer tools installed but aside from that I did nothing funky.

Just create a file called byteswap.h with the following 4 lines in it in the same directory as everything else.

Code:

#include <libkern/OSByteOrder.h>
#define bswap_16(x) OSSwapInt16(x)
#define bswap_32(x) OSSwapInt32(x)
#define bswap_64(x) OSSwapInt64(x)

As far as I can see this is working fine, still testing though but no build probs after that.

Edit : Ah, just saw chromicants patch, that's probably a better way to bundle it into the build   Still, hope this helps someone.

[Patches]

I just compiled and ran this on OS X 10.6.6 by creating a byteswap.h and using no more than ./configure and make.  (No special options etc.)

Obviously you'll need the OS X developer tools installed but aside from that I did nothing funky.

Just create a file called byteswap.h with the following 4 lines in it in the same directory as everything else.

Code:

#include <libkern/OSByteOrder.h>
#define bswap_16(x) OSSwapInt16(x)
#define bswap_32(x) OSSwapInt32(x)
#define bswap_64(x) OSSwapInt64(x)

As far as I can see this is working fine, still testing though but no build probs after that.

Edit : Ah, just saw chromicants patch, that's probably a better way to bundle it into the build   Still, hope this helps someone.

Hi rich_rich. Does your compiled version have the sse2_64 algorithm as an option? If you don't install YASM, the compiler doesn't even try to make the sse2_64 so it works, albeit without sse2_64. If you have YASM however, you get the errors I described earlier in the thread. Still, using one of the other algorithm is a better option for mining than official client.

[richy_rich]

Hi, no it doesn't.  I've really only just started playing with it and looking at it tbh, if I get a chance I'll have a bash with yasm and report back

[jgarzik]

Version 0.8.1 released.  Some non-critical bugfixes, and one feature (User-Agent) that assists pool server operators in isolating problems to specific miner clients.

Changes:
- Make --user, --pass actually work

- Add User-Agent HTTP header to requests, so that server operators may
  more easily identify the miner client.

- Fix minor bug in example JSON config file

SHA1: 0e60652fb0d29c6d20ed40bfce721bcd7a231b51  cpuminer-installer-0.8.1.zip
MD5: cc42cf0ff88958325dfedbd199f71a9e  cpuminer-installer-0.8.1.zip

[cdnbcguy]

I am running Ubuntu 10.10 on an AMD Athlon X2 64 bit laptop

When I follow the instructions and do

   CFLAGS="-O3 -Wall -msse2" ./configure
   make

it runs fine and produces minerd as an executable.

But when I run it I get this

cdnbcguy@hiscomputer:~/cpuminer-0.8.1$ minerd
No command 'minerd' found, did you mean:
 Command 'mined' from package 'mined' (universe)
minerd: command not found

What the problem, please?

[TurdHurdur]

I am running Ubuntu 10.10 on an AMD Athlon X2 64 bit laptop

When I follow the instructions and do

   CFLAGS="-O3 -Wall -msse2" ./configure
   make

it runs fine and produces minerd as an executable.

But when I run it I get this

cdnbcguy@hiscomputer:~/cpuminer-0.8.1$ minerd
No command 'minerd' found, did you mean:
 Command 'mined' from package 'mined' (universe)
minerd: command not found

What the problem, please?

What'd "make install" output?

[chromicant]

cdnbcguy@hiscomputer:~/cpuminer-0.8.1$ minerd
No command 'minerd' found, did you mean:
 Command 'mined' from package 'mined' (universe)
minerd: command not found

What the problem, please?

Try ./minerd since . is traditionally not on your path.

[cdnbcguy]

Got it. What an embarrassing error. 

Thank you.

[Danzotron]

Ok guys,
Question with bitcoins as reward for good info.

I have a Sun Fire V880 with 8 UltraSPARC III Cpus @ 1200mhz at my disposal. This thing is a beast. Surely there is a way for me to get some decent hashing going on with it?

I've noticed there's not really much of a port, or anything that's been moved over doesn't get decent speeds.

Can someone give me the hot tip on how I can start really utilising this machine?

[dbitcoin]

v0.8.1 use full long polling url for posting.

Long polling url header for btcmine.com:

'X-Long-Polling', 'http://btcmine.com:8332/lp'

Request from poclbm:

POST /lp

Request from minerd:

POST /http://btcmine.com:8332/lp


In my configuration, such request processed anyway, but I not sure about other servers and configurations.

[Patches]

Ok guys,
Question with bitcoins as reward for good info.

I have a Sun Fire V880 with 8 UltraSPARC III Cpus @ 1200mhz at my disposal. This thing is a beast. Surely there is a way for me to get some decent hashing going on with it?

I've noticed there's not really much of a port, or anything that's been moved over doesn't get decent speeds.

Can someone give me the hot tip on how I can start really utilising this machine?

I think there are no reports because it probably isn't possible. Knowing nothing about the UltraSPARC III architecture, it would seem to me that without SSE2 or some built-in SHA256 hashing optimization in the CPUs you won't get more than a few hundred khashes/sec/CPU, perhaps a 1000 with the right algorithm. A single modern dual-core Intel chip using the sse2_64 algorithm would beat all 8 of the SPARC CPUs making mining with the V880 probably not worth the electricity.

If it's fully at your disposal sell it and by some ATI GPUs for some actually efficient mining. Otherwise, download and compile jgarzik's miner (http://yyz.us/bitcoin/) and test each of the included algorithms to see which runs best on your architecture but I wouldn't bet on eking out more than a couple thousand khashes/sec. Better than nothing I guess.

Good luck!

[chromicant]

Ok guys,
Question with bitcoins as reward for good info.

I have a Sun Fire V880 with 8 UltraSPARC III Cpus @ 1200mhz at my disposal. This thing is a beast. Surely there is a way for me to get some decent hashing going on with it?

I've noticed there's not really much of a port, or anything that's been moved over doesn't get decent speeds.

Can someone give me the hot tip on how I can start really utilising this machine?

Use a good compiler and the C code?

The UltraSPARC III is just a standard RISC 64-bit CPU. The UltraSPARC III does have "MMX Like" instructions (VIS), but the ISA doesn't even have a bit rotate if I recall, which makes it useless for trying SIMD tricks to speed up SHA-anything.

You may get something with some hand assembly, but I don't think it'll hold a candle to the tuned SSE2 code that's in some of the miners out there on modern hardware.

[adv]

Question with bitcoins as reward for good info.

Unfortunately, my info is not as good as we would like. :^)

I have a Sun Fire V880 with 8 UltraSPARC III Cpus @ 1200mhz at my disposal. This thing is a beast. Surely there is a way for me to get some decent hashing going on with it?

I've noticed there's not really much of a port, or anything that's been moved over doesn't get decent speeds.

Can someone give me the hot tip on how I can start really utilising this machine?

I build Jgarzik miner for spark, and I saw a few things:
1. Algorithms. Forget about VIA, or asm algorithms: they are for x86. Available only "c" and "cryptopp". It's not so bad, but no SSE2-fantastics.
2. It may be possible to optimize C and cryptopp. I'm going to study this possibility, when I have spare time.

P.S.
Thanx @ Mtve, who doing some interessed speed tests and found infos about this theme: http://bitcointalk.org/index.php?topic=1925.msg63526#msg63526

[Lardie]

I'm having trouble getting decent speeds out of Jgarzik's miner on Ubuntu 10.10 (Phenom II X4 920). I'm only getting 125 kh/s per thread (4 threads), which drops to 50 kh/s with 4way enabled.

The same computer does 10+ mh/s using ufasoft's Win SSE2 miner.
Can someone please enlighten me as to how I can get the same performance under Linux.