Hi,
I'm trying to set up boinc on a Raspberry Pi model B running Arch Linux in order to participate to this project.

By following the wiki page on https://wiki.archlinux.org/index.php/BOINC I have installed boinc, then added my user to the 'boinc' group, and finally started 'boinc.service'.

I found this step-by-step guide to configure boinc: http://setiathome.ssl.berkeley.edu/forum_thread.php?id=68318, and since I'm posting to this forum, I suppose I already have an account. Therefore I'm trying to run

boinccmd --lookup_account http://setiathome.berkeley.edu my_email my_password

Unfortunately I always get an error as output to that command, and I cannot understand why:

$ boinccmd --lookup_account http://setiathome.berkeley.edu my_email my_password
status: authentication error
Operation failed: authentication error

Note that I also tried to run this command as root, but the result is the same.

Since the command above produces error code 101 (as 'echo $?' states), by googling a around I found this page http://boincfaq.mundayweb.com/index.php?viewCat=3 that says error code 101 is related to lack of memory:

ERR_MALLOC -101

There is a problem with the memory allocation. If insufficient memory is found to store BOINC and the project's science application plus work unit in, you'll get an error -101.

Solution: Free up memory or add more memory to your computer.
See RAM Requirements for how much RAM you need free.

However, according to http://boincfaq.mundayweb.com/index.php?view=67 my memory requirements for this project shall be ok, as you can see below.

$ free -m
              total        used        free      shared  buff/cache   available
Mem:            432          43         287           9         101         365

I tried also 'boinccmd --create_account' but the result is exactly the same. error 101.

What am I doing wrong?

Are you running the boinc client when you run boinccmd?
Are you sure you typed the email address and password correctly (case sensitive)?

---

Checking through the source code, this can also be attributed when the RPC authorization fails. Try to run boinccmd from the same directory as the boinc client, or make sure you allow all parts of BOINC to communicate with each other through TCP port 31416 (in the firewall).

If running the command from elsewhere, make sure there's a password in the gui_rpc_auth.cfg file on the device, or run the BOINC client with the --allow_remote_gui_rpc attribut (boinc --allow_remote_gui_rpc).

---

Ok, got some improvements, thanks!

From /var/lib/boinc (boinc's home defined by --dir into boinc.service file) I had to run boinccmd as root.
In this way I was able to lookup the account, add the project, and update it...but...
... unfortunately log files are pretty clear about a thing:

16-Dec-2015 21:52:50 [SETI@home] This project doesn't support computers of type armv6l-unknown-linux-gnueabihf

It seems the Raspberry Pi is not supported by SETI@home. Darn.

Thanks anyway

It seems the Raspberry Pi is not supported by SETI@home. Darn.

Not by default, no. But you can build the science application(s) for it, or ask one of the people who done so already.

See http://burdeview.blogspot.nl/p/raspberry-pi-boinc-project-ive-created.html for the Setiathome v7 Multibeam application and anonymous platform app_info.xml file.

It also shows how to build applications and BOINC, if necessary.

---

It seems the Raspberry Pi is not supported by SETI@home. Darn.

Not by default, no. But you can build the science application(s) for it, or ask one of the people who done so already.

See http://burdeview.blogspot.nl/p/raspberry-pi-boinc-project-ive-created.html for the Setiathome v7 Multibeam application and anonymous platform app_info.xml file.

It also shows how to build applications and BOINC, if necessary.

I was just about to publish that link here. It works now. Thanks alot!