Search content
Sort by

Showing 16 of 16 results by Patches
Post
Topic
Board Pools
Re: [Testing] Eclipse Mining Consortium: The Be Everything 0 Fee Pool
by
Patches
on 15/06/2011, 10:28:15 UTC
Small glitch:

It seems your API is broken, at least for me. I get a similar JSON response no matter whether I use 'api.php?key=' or 'api.php?key=&poolstats=yes' etc. which seems to be a userstats report and the data returned does not appear to be for my account (the hash rate and number of workers are wrong).

Otherwise my workers seem to be mining just fine.

Edit:

Actually, I just checked and the API is reporting the same information as the webpage summary box which is incorrect. Even though I have only two workers registered, it is reporting 7 active miners and current speed 3X what is shown on the "My Workers" page. Still, I can't get the API to show anything different with '&poolstats=yes', '&userstats=yes' or '&blockstats=yes' they all just report something like this:

Code:
{"hashrate":"1.34 GH\/s","active_workers":"6","round_shares":"360252","round_duration":"1d 00:01:04","avg_shares_block":"0"}


Another edit:

Ah I see, that is actually the total poolstats. Where have all the miners gone? In that case, the problem is just that the API won't return the userstats or the blockstats for me.
Post
Topic
Board Pools
Re: [Testing] Eclipse Mining Consortium: The Be Everything 0 Fee Pool
by
Patches
on 14/06/2011, 19:57:04 UTC
Quick question - are you distributing the block transaction fees earned to the pool participants or are keeping them for yourself?

Regardless, I will definitely add some miners to the pool as soon as you have some anti-hopping measures put in place.
Post
Topic
Board Bitcoin Technical Support
Re: Help mining GPU
by
Patches
on 28/03/2011, 14:21:56 UTC
Does DiabloMiner miner actually work on a Mac? On my 2007 MacBook running OS X version 10.6.7, I get the following messages:

[3/27/11 10:05:16 PM] Started
[3/27/11 10:05:16 PM] Connecting to: http://bitcoinpool.com:8334/
[3/27/11 10:05:16 PM] ERROR: OpenCL platform Apple contains no devices


DiabloMiner works fine on my MacBook Pro with OS X (10.6.7) for about 7,000 khash/s. Likely the problem is your integrated Intel graphics in your MacBook does not support OpenCl.  
Post
Topic
Board Mining
Re: CPU Miner & problem with libcurl
by
Patches
on 23/03/2011, 11:47:29 UTC
Hello,

I install CPU Miner ( https://github.com/j16sdiz/cpuminer ).
But when I execute configure, I have a problem with the libcurl :

Code:
./configure: line 4830: syntax error near unexpected token `,'
./configure: line 4830: `LIBCURL_CHECK_CONFIG(, 7.10.1, ,

I have Fedora 14.

So, I look if I have a libcurl on the system :

Code:
Le paquet libcurl-7.21.0-6.fc14.x86_64 est déjà installé dans sa dernière version

I try install a libcurl-7.21 devel and I have always this problem.

Would you have a solution?



Thanks


PS : Sorry for my bad english

Download and compile from the tarball (http://yyz.us/bitcoin/cpuminer-0.8.1.tar.gz) rather than from github. At least that worked for me on OS X which was having trouble finding libcurl.

Bon chance!

Post
Topic
Board Mining software (miners)
Re: New demonstration CPU miner available
by
Patches
on 23/03/2011, 11:42:54 UTC
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!
Post
Topic
Board Mining software (miners)
Re: New demonstration CPU miner available
by
Patches
on 22/03/2011, 15:58:49 UTC
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
#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 Smiley  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.
Post
Topic
Board Mining software (miners)
Re: New demonstration CPU miner available
by
Patches
on 22/03/2011, 14:49:09 UTC
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.


Post
Topic
Board Mining software (miners)
Re: New demonstration CPU miner available
by
Patches
on 22/03/2011, 08:54:01 UTC
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.


Post
Topic
Board Mining software (miners)
Re: New demonstration CPU miner available
by
Patches
on 21/03/2011, 21:53:32 UTC
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
Post
Topic
Board Mining software (miners)
Re: New demonstration CPU miner available
by
Patches
on 21/03/2011, 19:57:46 UTC
As far as I know no one has been able to easily compile and get this to run on OS X natively. However, you can run the miner (unfortunately without ufasoft's sse2 optimizations) using the following steps:

Urm. Have you tried to compile it natively using XCode on OSX 10.6 on a machine that can handle SSE2? I'd like to see some bug reports as to why it won't compile. I don't think there's anything super specific that would prevent a build from happening. I've seen nothing on what sort of compile errors one gets on OSX. Also remember, I crafted the SSE2 code in jgarzik's miner to require the 64-bit mode of Intel/AMD chips. So if you're running a 32-bit kernel/userspace, you won't be able to use it.

(I'd try myself, but my Mac is in little bits...and it's just a CoreDuo, so I couldn't test the SSE2 code if I wanted to)

I do know my SSE2 WILL NOT WORK in win64, since the calling ABI is different.

The one place where there probably is a problem is I used ELF64 as the output for yasm. That should be Mach-O for OSX...but it may also just work.

I have only spent a couple minutes playing with it but I got stuck at the same byteswap.h problem described previously in this thread (see: http://bitcointalk.org/index.php?topic=1925.msg48679#msg48679). I am sure it is possible so I'll give it another go when I have some time.
Post
Topic
Board Mining software (miners)
Re: New demonstration CPU miner available
by
Patches
on 21/03/2011, 19:44:38 UTC
for a complete newb how do i go around to make this work on mac OSx 10.6?
As far as I know no one has been able to easily compile and get this to run on OS X natively. However, you can run the miner (unfortunately without ufasoft's sse2 optimizations) using the following steps:

1) Install MacPorts (here:http://www.macports.org/install.php). This software will allow you to easily install various linux packages on your Mac.
2) Open up the terminal, and run 'sudo port -v selfupdate' to get the latest package info and then 'sudo port install wine'. This will install wine, an application that will let you run windows programs.
3) Download the windows installer of the miner (from here: http://bitcointalk.org/index.php?topic=1925.msg24217#msg24217) and unzip it. Run it in the terminal with 'wine cpuminer-installer.exe' and make sure to choose a directory you will remember (I just made one on the desktop). If you aren't sure the full path to cpuminer-installer.exe, just drag the file from the finder window to the terminal window and terminal will add it.
4) Run the miner in the terminal with 'wine /yourdirectory/minerd.exe --help' or with whatever command line options you decide. I found the cryptopp_asm32 algorithm to give my MacPro the highest hashing rates.

Happy mining.

Post
Topic
Board Mining
Re: Is it working?
by
Patches
on 02/03/2011, 09:41:27 UTC
I setup BC on my MacMini with the bitcoin.conf as follows:
Code:
server=1
rpcallowip=10.1.0.*
gen=1
4way=1
rpcuser=username
rpcpassword=password
rpctimeout=30

I setup Diablo on a couple of clients to point to it and it appears to be working but how do I know? When I run bitcoin getinfo the hashespersc value doesn't change to reflect the miners work.
Am I missing something?

Thanks!!

I don't think the combined hash rate is displayed on the Bitcoin client when it is working in server mode although I have never run it like this and I could be wrong. However, if you are getting hash rates displayed with Diablo, that suggests that everything is working fine as it should report an error if it can't find the server. If you want some peace of mind turn off the Bitcoin client once everything is running, and your Diablo instances should start complaining with connection errors giving you the proof that the two are talking.
Post
Topic
Board Mining
Re: Mac n00b needs help!
by
Patches
on 02/03/2011, 09:27:33 UTC

Patches-
OK, now I'm getting about 7000k like you and figured out why it was low before. If I run the BC CPU app then start Diablo I only get about 2000k. Even if I kill BC Diablo never climbs. I have to reboot and start Diablo and never start the BC client and then it gets 7000k.
Did you find the same thing?
Odd thing is that this isn't a problem on the MB with the 320.

Strange.

Thanks for the info!



No, I don't seem to have the same problem. I upgraded to the latest DiabloMiner (as per slush's request) and had it humming along at about 7000k. I stopped it, and then started generating bitcoins on the official client (v0.3.19). I then restarted the DiabloMiner and was getting about the same khash/sec with the DiabloMiner as before.

I didn't run the test for very long, but my quick attempt wasn't able to reproduce what you are seeing.
 
Post
Topic
Board Mining
Re: Mac n00b needs help!
by
Patches
on 01/03/2011, 19:04:08 UTC
Thanks guys!
The Diablo miner works pretty well. Strange that my MBP's 330M gets about 1800khps and my MB's 320M gets 5200khps. Any idea what the cheaper one is doing so much better?

Does the rpcminer author provice binaries?

Can the bitcoin.org client act as a miner? I see that the conf file can have username/password added to it.

Thanks again for the help!!

That is strange. I get 7500-7800 khash/sec with the 330M in my MBP. I am running a version I downloaded in early February, but I don't recall using any strange options or having to install anything. I use "DiabloMiner-OSX.sh -u user -p password -o mining.bitcoin.cz -r 8332" with slush's pool.

Yes, you can use the default client as a CPU miner and also add the hashes from the Diablo's miner using the server mode and the conf file as you saw. Just point the "-o" to localhost or to your ip address.

Happy mining.


Post
Topic
Board Mining
Re: Mac n00b needs help!
by
Patches
on 28/02/2011, 04:05:44 UTC
For OS X I am running jgarzik's CPU miner under wine and Diablo's GPU miner works well out of the box. I ran into various errors trying to compile the other miners with OS X.
Post
Topic
Board Mining software (miners)
Re: New demonstration CPU miner available
by
Patches
on 18/02/2011, 13:42:35 UTC
Just to share, the miner seems to work quite well under wine on OS X on a Mac Pro. Just install wine as per these instructions: http://wiki.winehq.org/MacOSX/Installing (I used Mac Ports) and you are good to go.