maxcorrads
Newbie
Offline
Activity: 42
Merit: 0
|
|
May 09, 2011, 03:28:27 PM |
|
Hi, i'm trying to compile it but i alway got this error the first time i compile: ps3@ps3:~/Downloads/verement-cellminer-68aa80c$ make cd ext && ruby1.9.1 extconf.rb checking for spe_context_run() in -lspe2... yes creating Makefile /usr/lib/ruby/1.9.1/mkmf.rb:1589:in `gsub!': invalid byte sequence in US-ASCII (ArgumentError) from /usr/lib/ruby/1.9.1/mkmf.rb:1589:in `block in depend_rules' from /usr/lib/ruby/1.9.1/mkmf.rb:1588:in `each_line' from /usr/lib/ruby/1.9.1/mkmf.rb:1588:in `depend_rules' from /usr/lib/ruby/1.9.1/mkmf.rb:1906:in `create_makefile' from extconf.rb:29:in `<main>' make: *** [ext/Makefile] Error 1 And this the second time: make make -C ext make[1]: Entering directory `/home/ps3/Downloads/verement-cellminer-68aa80c/ext' gcc -I. -I/usr/include/ruby-1.9.1/powerpc-linux -I/usr/include/ruby-1.9.1/ruby/backward -I/usr/include/ruby-1.9.1 -I. -D_FILE_OFFSET_BITS=64 -fPIC -fno-strict-aliasing -g -g -O2 -fPIC -Wall -o cellminer.o -c cellminer.c gcc -I. -I/usr/include/ruby-1.9.1/powerpc-linux -I/usr/include/ruby-1.9.1/ruby/backward -I/usr/include/ruby-1.9.1 -I. -D_FILE_OFFSET_BITS=64 -fPIC -fno-strict-aliasing -g -g -O2 -fPIC -Wall -o spu_miner.o -c spu_miner.c make[1]: *** No rule to make target `spu_worker.o', needed by `cellminer.so'. Stop. make[1]: Leaving directory `/home/ps3/Downloads/verement-cellminer-68aa80c/ext' make: *** [ext/cellminer.so] Error 2
Have you ever seen this error? Thank you
|
|
|
|
FnuGk
Newbie
Offline
Activity: 55
Merit: 0
|
|
May 09, 2011, 05:05:20 PM |
|
|
|
|
|
verement
Newbie
Offline
Activity: 16
Merit: 0
|
|
May 09, 2011, 09:28:29 PM |
|
Hi, i'm trying to compile it but i alway got this error the first time i compile: ps3@ps3:~/Downloads/verement-cellminer-68aa80c$ make cd ext && ruby1.9.1 extconf.rb checking for spe_context_run() in -lspe2... yes creating Makefile /usr/lib/ruby/1.9.1/mkmf.rb:1589:in `gsub!': invalid byte sequence in US-ASCII (ArgumentError) from /usr/lib/ruby/1.9.1/mkmf.rb:1589:in `block in depend_rules' from /usr/lib/ruby/1.9.1/mkmf.rb:1588:in `each_line' from /usr/lib/ruby/1.9.1/mkmf.rb:1588:in `depend_rules' from /usr/lib/ruby/1.9.1/mkmf.rb:1906:in `create_makefile' from extconf.rb:29:in `<main>' make: *** [ext/Makefile] Error 1 Try the latest version I just pushed to github. Apparently the $LANG setting in your environment can have an effect on the interpretation of source files; I corrected this by setting an explicit encoding which should solve the problem. Make sure you clean your source tree with "git clean -x -f" before you try again. Thanks for the report.
|
|
|
|
maxcorrads
Newbie
Offline
Activity: 42
Merit: 0
|
|
May 10, 2011, 04:15:23 PM |
|
Hi, i'm trying to compile it but i alway got this error the first time i compile: ps3@ps3:~/Downloads/verement-cellminer-68aa80c$ make cd ext && ruby1.9.1 extconf.rb checking for spe_context_run() in -lspe2... yes creating Makefile /usr/lib/ruby/1.9.1/mkmf.rb:1589:in `gsub!': invalid byte sequence in US-ASCII (ArgumentError) from /usr/lib/ruby/1.9.1/mkmf.rb:1589:in `block in depend_rules' from /usr/lib/ruby/1.9.1/mkmf.rb:1588:in `each_line' from /usr/lib/ruby/1.9.1/mkmf.rb:1588:in `depend_rules' from /usr/lib/ruby/1.9.1/mkmf.rb:1906:in `create_makefile' from extconf.rb:29:in `<main>' make: *** [ext/Makefile] Error 1 Try the latest version I just pushed to github. Apparently the $LANG setting in your environment can have an effect on the interpretation of source files; I corrected this by setting an explicit encoding which should solve the problem. Make sure you clean your source tree with "git clean -x -f" before you try again. Thanks for the report. Now i've got this error when i run the make command: cd ext && ruby1.9.1 -E ascii-8bit extconf.rb checking for spe_context_run() in -lspe2... yes creating Makefile make -C ext make[1]: Entering directory `/home/ps3/Downloads/verement-cellminer-f313a7a/ext' Makefile:230: depend.auto: No such file or directory make[1]: Leaving directory `/home/ps3/Downloads/verement-cellminer-f313a7a/ext' make[1]: Entering directory `/home/ps3/Downloads/verement-cellminer-f313a7a/ext' gcc -I. -I/usr/include/ruby-1.9.1/powerpc-linux -I/usr/include/ruby-1.9.1/ruby/backward -I/usr/include/ruby-1.9.1 -I. -D_FILE_OFFSET_BITS=64 -fPIC -fno-strict-aliasing -g -g -O2 -fPIC -Wall -o cellminer.o -c cellminer.c gcc -I. -I/usr/include/ruby-1.9.1/powerpc-linux -I/usr/include/ruby-1.9.1/ruby/backward -I/usr/include/ruby-1.9.1 -I. -D_FILE_OFFSET_BITS=64 -fPIC -fno-strict-aliasing -g -g -O2 -fPIC -Wall -o spu_miner.o -c spu_miner.c make -C spu make[2]: Entering directory `/home/ps3/Downloads/verement-cellminer-f313a7a/ext/spu' Makefile:55: depend.auto: No such file or directory make[2]: Leaving directory `/home/ps3/Downloads/verement-cellminer-f313a7a/ext/spu' make[2]: Entering directory `/home/ps3/Downloads/verement-cellminer-f313a7a/ext/spu' spu-gcc -DUNROLL_SHA256 -Dinline="inline __attribute__((always_inline))" -O3 -fno-strict-aliasing -funroll-loops -mno-safe-hints -Wall -Werror -c -o main.o main.c spu-gcc -DUNROLL_SHA256 -Dinline="inline __attribute__((always_inline))" -O3 -fno-strict-aliasing -funroll-loops -mno-safe-hints -Wall -Werror -c -o worker.o worker.c spu-gcc -DUNROLL_SHA256 -Dinline="inline __attribute__((always_inline))" -O3 -fno-strict-aliasing -funroll-loops -mno-safe-hints -Wall -Werror -c -o sha256.o sha256.c spu-gcc -DUNROLL_SHA256 -Dinline="inline __attribute__((always_inline))" -O3 -fno-strict-aliasing -funroll-loops -mno-safe-hints -Wall -Werror -c -o util.o util.c spu-gcc -DUNROLL_SHA256 -Dinline="inline __attribute__((always_inline))" -O3 -fno-strict-aliasing -funroll-loops -mno-safe-hints -Wall -Werror -c -o spu_slih.o spu_slih.c spu-as -o spu_flih.o spu_flih.s spu-gcc -o worker.elf main.o worker.o sha256.o util.o spu_slih.o spu_flih.o make[2]: Leaving directory `/home/ps3/Downloads/verement-cellminer-f313a7a/ext/spu' embedspu spu_worker spu/worker.elf spu_worker.o gcc -I. -I/usr/include/ruby-1.9.1/powerpc-linux -I/usr/include/ruby-1.9.1/ruby/backward -I/usr/include/ruby-1.9.1 -I. -D_FILE_OFFSET_BITS=64 -fPIC -fno-strict-aliasing -g -g -O2 -fPIC -Wall -o ppu_miner.o -c ppu_miner.c make -C ppu make[2]: Entering directory `/home/ps3/Downloads/verement-cellminer-f313a7a/ext/ppu' Makefile:51: depend.auto: No such file or directory make[2]: Leaving directory `/home/ps3/Downloads/verement-cellminer-f313a7a/ext/ppu' make[2]: Entering directory `/home/ps3/Downloads/verement-cellminer-f313a7a/ext/ppu' gcc -DUNROLL_SHA256 -Dinline="inline __attribute__((always_inline))" -O3 -fno-strict-aliasing -funroll-loops -mcpu=cell -Wall -Werror -c -o worker.o worker.c gcc -DUNROLL_SHA256 -Dinline="inline __attribute__((always_inline))" -O3 -fno-strict-aliasing -funroll-loops -mcpu=cell -Wall -Werror -c -o sha256.o sha256.c sha256.c: In function 'sha256_search': sha256.c:664:1: internal compiler error: in trunc_int_for_mode, at explow.c:56 Please submit a full bug report, with preprocessed source if appropriate. See <file:///usr/share/doc/gcc-4.5/README.Bugs> for instructions. make[2]: *** [sha256.o] Error 1 make[2]: Leaving directory `/home/ps3/Downloads/verement-cellminer-f313a7a/ext/ppu' make[1]: *** [ppu/worker.a] Error 2 make[1]: Leaving directory `/home/ps3/Downloads/verement-cellminer-f313a7a/ext' make: *** [ext/cellminer.so] Error 2
if you can help me thanks!
|
|
|
|
niooron
|
|
May 10, 2011, 04:39:24 PM |
|
Why not just upload the binary? All PS3 are the same anyway, no need to always compile from source.
|
|
|
|
Nicksasa
|
|
May 10, 2011, 05:28:03 PM |
|
Why not just upload the binary? All PS3 are the same anyway, no need to always compile from source.
But the linux that they run isn't
|
|
|
|
verement
Newbie
Offline
Activity: 16
Merit: 0
|
|
May 10, 2011, 05:37:28 PM |
|
Now i've got this error when i run the make command: cd ext && ruby1.9.1 -E ascii-8bit extconf.rb checking for spe_context_run() in -lspe2... yes creating Makefile make -C ext make[1]: Entering directory `/home/ps3/Downloads/verement-cellminer-f313a7a/ext' Makefile:230: depend.auto: No such file or directory make[1]: Leaving directory `/home/ps3/Downloads/verement-cellminer-f313a7a/ext' make[1]: Entering directory `/home/ps3/Downloads/verement-cellminer-f313a7a/ext' gcc -I. -I/usr/include/ruby-1.9.1/powerpc-linux -I/usr/include/ruby-1.9.1/ruby/backward -I/usr/include/ruby-1.9.1 -I. -D_FILE_OFFSET_BITS=64 -fPIC -fno-strict-aliasing -g -g -O2 -fPIC -Wall -o cellminer.o -c cellminer.c gcc -I. -I/usr/include/ruby-1.9.1/powerpc-linux -I/usr/include/ruby-1.9.1/ruby/backward -I/usr/include/ruby-1.9.1 -I. -D_FILE_OFFSET_BITS=64 -fPIC -fno-strict-aliasing -g -g -O2 -fPIC -Wall -o spu_miner.o -c spu_miner.c make -C spu make[2]: Entering directory `/home/ps3/Downloads/verement-cellminer-f313a7a/ext/spu' Makefile:55: depend.auto: No such file or directory make[2]: Leaving directory `/home/ps3/Downloads/verement-cellminer-f313a7a/ext/spu' make[2]: Entering directory `/home/ps3/Downloads/verement-cellminer-f313a7a/ext/spu' spu-gcc -DUNROLL_SHA256 -Dinline="inline __attribute__((always_inline))" -O3 -fno-strict-aliasing -funroll-loops -mno-safe-hints -Wall -Werror -c -o main.o main.c spu-gcc -DUNROLL_SHA256 -Dinline="inline __attribute__((always_inline))" -O3 -fno-strict-aliasing -funroll-loops -mno-safe-hints -Wall -Werror -c -o worker.o worker.c spu-gcc -DUNROLL_SHA256 -Dinline="inline __attribute__((always_inline))" -O3 -fno-strict-aliasing -funroll-loops -mno-safe-hints -Wall -Werror -c -o sha256.o sha256.c spu-gcc -DUNROLL_SHA256 -Dinline="inline __attribute__((always_inline))" -O3 -fno-strict-aliasing -funroll-loops -mno-safe-hints -Wall -Werror -c -o util.o util.c spu-gcc -DUNROLL_SHA256 -Dinline="inline __attribute__((always_inline))" -O3 -fno-strict-aliasing -funroll-loops -mno-safe-hints -Wall -Werror -c -o spu_slih.o spu_slih.c spu-as -o spu_flih.o spu_flih.s spu-gcc -o worker.elf main.o worker.o sha256.o util.o spu_slih.o spu_flih.o make[2]: Leaving directory `/home/ps3/Downloads/verement-cellminer-f313a7a/ext/spu' embedspu spu_worker spu/worker.elf spu_worker.o gcc -I. -I/usr/include/ruby-1.9.1/powerpc-linux -I/usr/include/ruby-1.9.1/ruby/backward -I/usr/include/ruby-1.9.1 -I. -D_FILE_OFFSET_BITS=64 -fPIC -fno-strict-aliasing -g -g -O2 -fPIC -Wall -o ppu_miner.o -c ppu_miner.c make -C ppu make[2]: Entering directory `/home/ps3/Downloads/verement-cellminer-f313a7a/ext/ppu' Makefile:51: depend.auto: No such file or directory make[2]: Leaving directory `/home/ps3/Downloads/verement-cellminer-f313a7a/ext/ppu' make[2]: Entering directory `/home/ps3/Downloads/verement-cellminer-f313a7a/ext/ppu' gcc -DUNROLL_SHA256 -Dinline="inline __attribute__((always_inline))" -O3 -fno-strict-aliasing -funroll-loops -mcpu=cell -Wall -Werror -c -o worker.o worker.c gcc -DUNROLL_SHA256 -Dinline="inline __attribute__((always_inline))" -O3 -fno-strict-aliasing -funroll-loops -mcpu=cell -Wall -Werror -c -o sha256.o sha256.c sha256.c: In function 'sha256_search': sha256.c:664:1: internal compiler error: in trunc_int_for_mode, at explow.c:56 Please submit a full bug report, with preprocessed source if appropriate. See <file:///usr/share/doc/gcc-4.5/README.Bugs> for instructions. make[2]: *** [sha256.o] Error 1 make[2]: Leaving directory `/home/ps3/Downloads/verement-cellminer-f313a7a/ext/ppu' make[1]: *** [ppu/worker.a] Error 2 make[1]: Leaving directory `/home/ps3/Downloads/verement-cellminer-f313a7a/ext' make: *** [ext/cellminer.so] Error 2
if you can help me thanks! Looks like you might want to use a different version of gcc. I'm using version 4.4.5 (from the Debian gcc-4.4 package).
|
|
|
|
maxcorrads
Newbie
Offline
Activity: 42
Merit: 0
|
|
May 10, 2011, 07:25:44 PM |
|
Looks like you might want to use a different version of gcc. I'm using version 4.4.5 (from the Debian gcc-4.4 package).
Ok, thank you! i've used gcc-4.4 now it compile correctly. 22.073 Mhash/s with 6 SPE and 2 PPE Miner. Nice work verement! Only one question, what is Backlogged work items? When the program is running i've got message like this [2011-05-10 19:20:19] Cell Miner starting [2011-05-10 19:20:19] Creating 6 SPU miner(s) [2011-05-10 19:20:19] Creating 2 PPU miner(s) [2011-05-10 19:20:22] Starting long poll [2011-05-10 19:20:22] Got work... 0.000 Mhash/s, 0 backlogged work items target = 00000000ffffffffffffffffffffffffffffffffffffffffffffffffffffffff prev = 000000000000568a844beb51c0fea9f8e5806772ec12a8dbdb1703e9b34c24ee [2011-05-10 19:21:23] Got work... 21.355 Mhash/s, 84 backlogged work items [2011-05-10 19:22:23] Got work... 22.073 Mhash/s, 174 backlogged work items [2011-05-10 19:23:24] Got work... 22.073 Mhash/s, 261 backlogged work items [2011-05-10 19:24:24] Got work... 22.073 Mhash/s, 345 backlogged work items [2011-05-10 19:25:25] Got work... 22.073 Mhash/s, 341 backlogged work items
|
|
|
|
maxcorrads
Newbie
Offline
Activity: 42
Merit: 0
|
|
May 10, 2011, 07:55:38 PM |
|
./cellminer --spe 7 --ppe 2 [2011-05-10 19:52:31] Cell Miner starting [2011-05-10 19:52:31] Creating 7 SPU miner(s) [2011-05-10 19:52:31] Creating 2 PPU miner(s) [2011-05-10 19:52:32] Starting long poll [2011-05-10 19:52:32] Got work... 0.000 Mhash/s, 0 backlogged work items target = 00000000ffffffffffffffffffffffffffffffffffffffffffffffffffffffff prev = 00000000000050f51a6a09a695f114c0799d4a843a1f737da36d95ce6b4d1d23 [2011-05-10 19:53:32] Got work... 24.933 Mhash/s, 77 backlogged work items [2011-05-10 19:54:32] Got work... 25.647 Mhash/s, 161 backlogged work items
25.647 Mhash with 7 SPE and 2 PPE Thread
|
|
|
|
verement
Newbie
Offline
Activity: 16
Merit: 0
|
|
May 10, 2011, 08:16:26 PM Last edit: May 10, 2011, 08:27:25 PM by verement |
|
Ok, thank you! i've used gcc-4.4 now it compile correctly.
22.073 Mhash/s with 6 SPE and 2 PPE Miner.
Nice work verement!
Only one question, what is Backlogged work items?
It's the number of work items that are still unfinished since the last time work was obtained. If this number reaches zero, the SPU/PPU miners will be starved for work. On the other hand, there is little point in keeping a huge backlog, so the work items are trimmed automatically to keep the number reasonable. The number is essentially just informational. The number will drop each time a new block is being worked on, since the backlog is then essentially useless and has to be cleared. The only time to be concerned (in terms of overall efficiency) is if you have a long period of RPC errors during which the entire backlog is depleted.
|
|
|
|
datguywhowanders
Member
Offline
Activity: 112
Merit: 10
|
|
May 17, 2011, 04:23:15 AM |
|
This whole thing sounds awesome. I don't really have any powerful graphics cards in my house, and I've had to rely on all cpu miners from laptops and old desktops for the time being. I think I'm running maybe a total of 20 Mhash with 5 machines right now. While I don't have the money to run out and buy a whole new desktop, I can afford a few extra dollars on my electricity bill to run the PS3 along with the rest of them and effectively double my total.
Here's the trouble... I'm running PS3 firmware 3.60, and I'm unsure of how to go about getting the otherOS set up. I messed around with it back in the day when it was still actually integrated with the official PS3 firmware, but that's obviously a thing of the past. I have no qualms about jailbreaking the PS3 and voiding warranty and what not, as I own an original 60GB fat model, so there is no longer a warranty, and the thing is likely to die at some point soon anyway. I just don't know how to best go about the whole process. Do I need to jailbreak? install a custom firmware? at what point do I install the firmware from gitbrew.org? how would I install the firmware from gitbrew.org? (the instructions are anything but helpful)
If someone could walk me through this, I'd really appreciate it.
|
Donations Welcome: 163id7T8KZ6MevqT86DjrBF2kfCPrQsfZE
|
|
|
portpho
Newbie
Offline
Activity: 9
Merit: 0
|
|
May 17, 2011, 04:29:33 AM |
|
THIS is what bitcoin needs to be a viable currency.
It needs a powerful GPU in every living room calculating while idle. This kind of strategy is the only way the public will ever gain substancial confidence in bitcoin.
We need many democratically distributed non-purpose built GPUs to make bitcoin a viable alternative currency.
|
|
|
|
mikey5287
Newbie
Offline
Activity: 51
Merit: 0
|
|
May 18, 2011, 05:49:42 PM |
|
Getting this error during make. [root@debian:~/verement-cellminer-ded41f8# make make -C ext make[1]: Entering directory `/root/verement-cellminer-ded41f8/ext' make -C spu make[2]: Entering directory `/root/verement-cellminer-ded41f8/ext/spu' spu-gcc -DUNROLL_SHA256 -Dinline="inline __attribute__((always_inline))" -O3 -fno-strict-aliasing -funroll-loops -mno-safe-hints -Wall -Werror -c -o main.o main.c /bin/sh: spu-gcc: not found make[2]: *** [main.o] Error 127 make[2]: Leaving directory `/root/verement-cellminer-ded41f8/ext/spu' make[1]: *** [spu/worker.elf] Error 2 make[1]: Leaving directory `/root/verement-cellminer-ded41f8/ext' make: *** [ext/cellminer.so] Error 2 /code]
I think it might be cause the packages aren't working properly.
Any helping getting the packages installed?
So the make will build.
|
|
|
|
anisoptera
Member
Offline
Activity: 308
Merit: 10
|
|
May 18, 2011, 06:07:46 PM |
|
THIS is what bitcoin needs to be a viable currency.
It needs a powerful GPU in every living room calculating while idle. This kind of strategy is the only way the public will ever gain substancial confidence in bitcoin.
Yes, I'm sure that's the one thing keeping the public from having confidence in bitcoin. I know when I think about a currency, I'm like "Man, but that doesn't eat up a bunch of power in my house for no reason. That's not very secure."
|
|
|
|
maxcorrads
Newbie
Offline
Activity: 42
Merit: 0
|
|
May 18, 2011, 06:38:54 PM |
|
Getting this error during make. [root@debian:~/verement-cellminer-ded41f8# make make -C ext make[1]: Entering directory `/root/verement-cellminer-ded41f8/ext' make -C spu make[2]: Entering directory `/root/verement-cellminer-ded41f8/ext/spu' spu-gcc -DUNROLL_SHA256 -Dinline="inline __attribute__((always_inline))" -O3 -fno-strict-aliasing -funroll-loops -mno-safe-hints -Wall -Werror -c -o main.o main.c /bin/sh: spu-gcc: not found make[2]: *** [main.o] Error 127 make[2]: Leaving directory `/root/verement-cellminer-ded41f8/ext/spu' make[1]: *** [spu/worker.elf] Error 2 make[1]: Leaving directory `/root/verement-cellminer-ded41f8/ext' make: *** [ext/cellminer.so] Error 2 /code]
I think it might be cause the packages aren't working properly.
Any helping getting the packages installed?
So the make will build.
try sudo apt-get install spu-gcc
|
|
|
|
verement
Newbie
Offline
Activity: 16
Merit: 0
|
|
May 19, 2011, 04:08:37 AM |
|
Getting this error during make. [root@debian:~/verement-cellminer-ded41f8# make make -C ext make[1]: Entering directory `/root/verement-cellminer-ded41f8/ext' make -C spu make[2]: Entering directory `/root/verement-cellminer-ded41f8/ext/spu' spu-gcc -DUNROLL_SHA256 -Dinline="inline __attribute__((always_inline))" -O3 -fno-strict-aliasing -funroll-loops -mno-safe-hints -Wall -Werror -c -o main.o main.c /bin/sh: spu-gcc: not found make[2]: *** [main.o] Error 127 make[2]: Leaving directory `/root/verement-cellminer-ded41f8/ext/spu' make[1]: *** [spu/worker.elf] Error 2 make[1]: Leaving directory `/root/verement-cellminer-ded41f8/ext' make: *** [ext/cellminer.so] Error 2
I think it might be cause the packages aren't working properly. Any helping getting the packages installed? So the make will build. You are probably missing the 'gcc-spu' package. Make sure all the packages listed in the README are installed.
|
|
|
|
verement
Newbie
Offline
Activity: 16
Merit: 0
|
|
May 19, 2011, 04:22:13 AM |
|
I've put up a new version of Cell Miner, now supporting HTTP keep-alive connections to reduce communication overhead. Thanks to lgeek on GitHub for the idea and initial implementation. This version requires a different Ruby Gem — be sure to: # gem1.9.1 install net-http-persistent https://github.com/verement/cellminer
|
|
|
|
hollajandro
Member
Offline
Activity: 83
Merit: 10
|
|
May 19, 2011, 08:44:24 AM |
|
alex@ps3:~/cellminer$ ./cellminer -u ????? -p ????? bitcoinpool.com [2011-05-19 01:41:16] Cell Miner starting [2011-05-19 01:41:16] Creating 6 SPU miner(s) spu_create(): Function not implemented spu_create(): Function not implemented /home/alex/cellminer/cellminer.rb:132: [BUG] Segmentation fault ruby 1.9.2p0 (2010-08-18 revision 29036) [powerpc-linux]
-- control frame ---------- c:0005 p:---- s:0014 b:0014 l:000013 d:000013 CFUNC :(null) c:0004 p:---- s:0012 b:0012 l:000011 d:000011 CFUNC :new c:0003 p:0022 s:0008 b:0008 l:001fec d:000007 LAMBDA /home/alex/cellminer/cellminer.rb:132 c:0002 p:---- s:0004 b:0004 l:000003 d:000003 FINISH c:0001 p:---- s:0002 b:0002 l:000001 d:000001 TOP --------------------------- -- Ruby level backtrace information ---------------------------------------- /home/alex/cellminer/cellminer.rb:132:in `block in main' /home/alex/cellminer/cellminer.rb:132:in `new' Segmentation fault alex@ps3:~/cellminer$ Any ideas?
|
|
|
|
lgeek
Newbie
Offline
Activity: 3
Merit: 0
|
|
May 19, 2011, 05:26:57 PM |
|
alex@ps3:~/cellminer$ ./cellminer -u ????? -p ????? bitcoinpool.com [2011-05-19 01:41:16] Cell Miner starting [2011-05-19 01:41:16] Creating 6 SPU miner(s) spu_create(): Function not implemented spu_create(): Function not implemented /home/alex/cellminer/cellminer.rb:132: [BUG] Segmentation fault ruby 1.9.2p0 (2010-08-18 revision 29036) [powerpc-linux]
-- control frame ---------- c:0005 p:---- s:0014 b:0014 l:000013 d:000013 CFUNC :(null) c:0004 p:---- s:0012 b:0012 l:000011 d:000011 CFUNC :new c:0003 p:0022 s:0008 b:0008 l:001fec d:000007 LAMBDA /home/alex/cellminer/cellminer.rb:132 c:0002 p:---- s:0004 b:0004 l:000003 d:000003 FINISH c:0001 p:---- s:0002 b:0002 l:000001 d:000001 TOP --------------------------- -- Ruby level backtrace information ---------------------------------------- /home/alex/cellminer/cellminer.rb:132:in `block in main' /home/alex/cellminer/cellminer.rb:132:in `new' Segmentation fault alex@ps3:~/cellminer$ Any ideas? Have you mounted spufs? none /spu spufs defaults 0 0 inside /etc/fstab or manually
|
|
|
|
hollajandro
Member
Offline
Activity: 83
Merit: 10
|
|
May 19, 2011, 09:54:28 PM |
|
Have you mounted spufs? none /spu spufs defaults 0 0 inside /etc/fstab or manually Ahhh. Alright it's working now, thanks!
|
|
|
|
|