Tranz

PiHoboNickels

46 posts in this topic

Since I used up all my coin age on the PI, I took the time to compile 1.4.0.1, and resync. Backup and running!  Start up time went from 45 mins to about 3. :-)  CPU usage is low, and memory is about 67%. I think memory will be the biggest issue in the future.  Should be able to use the disk for more swap, if needed.

 

 

KiB Mem:    448180 total,   429904 used,    18276 free,    23412 buffers
KiB Swap:   511996 total,        0 used,   511996 free,    75760 cached

  PID USER      PR  NI  VIRT  RES  SHR S  %CPU %MEM    TIME+  COMMAND
 2710      20   0  4664 1360 1028 R   1.0  0.3   0:00.29 top
 2241      20   0  430m 297m 4440 S   0.7 67.9 146:12.23 hobonickelsd

 

presstab likes this

Share this post


Link to post
Share on other sites

67.9% memory isn't all that bad for a pi - I am guessing it is the 512 model though right?

Share this post


Link to post
Share on other sites

Yes it is.  Would be cool to the gui working over X window. Not sure how that would work right off hand though..

presstab likes this

Share this post


Link to post
Share on other sites

I am pretty sure db_cxx is in Berkeley database item. I would double check to make sure it is there.  Look in the build_unix folder in the Berkeley directory for a file called db_cxx.h

Share this post


Link to post
Share on other sites

Yes, correct, my instructions were incomplete. You only need to remove "#include <xmmintrin.h>" from scrypt_mine.cpp

 

I'll fix my instructions, and I will also put IFDEFs in place to do this automatically for the next major release.

c0da likes this

Share this post


Link to post
Share on other sites

Hi there again,

 

so I've been trying to compile the HoboNickels QT Wallet on my Raspberry Pi

for a few days now but I'm stuck.

 

If anyone has the courage to look into it, compile logs are over here.

 

Cheers.

Share this post


Link to post
Share on other sites

I have not tried to get the GUI on the PI. Will be really cool if you can pull it off. I wonder how it will respond.

 

Regarding your error. Did you edit the scrypt_mine.cpp or the make?

Share this post


Link to post
Share on other sites

Hi,

 

I indeed edited the makefile generated by 

qmake "USE_UPNP=-"

to remove the -msse2 flag.

 

Neither of those should have caused that.

 

Looks like it is geting caught up in this section of scrypt_mine.cpp

 

#if defined(__x86_64__)

#define SCRYPT_3WAY #define SCRYPT_BUFFER_SIZE (3 * 131072 + 63)

extern "C" int scrypt_best_throughput(); extern "C" void scrypt_core(uint32_t *X, uint32_t *V); extern "C" void scrypt_core_2way(uint32_t *X, uint32_t *Y, uint32_t *V); extern "C" void scrypt_core_3way(uint32_t *X, uint32_t *Y, uint32_t *Z, uint32_t *V);

#elif defined(__i386__) || defined(__arm__)

#define SCRYPT_BUFFER_SIZE (131072 + 63)

 

 

Might need to define __arm__ similar to how the makefile.unix does it. I'll have a closer look later.

 

edit: you could try to use the scrypt_mine.o compiled from the daemon compilation. Just put it with the other .o(s) for this build.

presstab likes this

Share this post


Link to post
Share on other sites

uptime
 03:54:41 up 76 days, 14:32,  1 user,  load average: 1.37, 0.98, 0.82

 

  PID USER      PR  NI  VIRT  RES  SHR S  %CPU %MEM    TIME+  COMMAND
31888 gawd      20   0  641m 401m 1320 S   3.3 91.8   4393:36 hobonickelsd

 

./hobonickelsd getbalance
2353.37275400

 

still going!
 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.