Boinc in Rapsberry?


111 posts   Page 4 of 5   1, 2, 3, 4, 5
by Ray_GTI-R » Tue Jan 22, 2013 2:23 am
Yep - both work perfectly.

Thanks to :ugeek: dcarrion87 BOINC is now available under Raspbian for many BOINC projects.

NativeBOINC? Not on the RPi Android "releases" and not, I fear, soon given the existing history :(

HELP:- BOINC in Raspberry? Someone please fix the forum Topic typo :roll:
User avatar
Posts: 96
Joined: Fri Mar 09, 2012 1:21 am
by dcarrion87 » Tue Jan 22, 2013 2:47 am
Thanks to dcarrion87 BOINC is now available under Raspbian for many BOINC projects.


Cheers Ray and thanks for your support in testing out these project binaries I've been putting out.
User avatar
Posts: 36
Joined: Fri Nov 23, 2012 9:51 am
Location: Australia
by Ray_GTI-R » Wed Jan 23, 2013 2:22 am
Forgot to say ... all the BOINC results returned to date are for my RPi 1st-gen 256mb Model B board @ 900mhz.

FWIW1:- WLAN works fine under Raspbian with a generic wifi adapter (a -ve for Android, hint!) And proper UK keyboard mapping (another -ve for Android)

Hint, hint Android developers!

FWIW2:- my RPi is now shown on BOINCstats as " " or more easily http://boincstats.com/en/stats/-1/host/detail/68237129 ... BoincSTATS is not 100% reliable, I know, but it's the first time my RPi shows up there.
User avatar
Posts: 96
Joined: Fri Mar 09, 2012 1:21 am
by Ray_GTI-R » Wed Jan 23, 2013 10:33 pm
Update: after the first non-stop run of approx 44 hours the RPi processed over 150 BOINC tasks for OProject@home see:-

http://oproject.info/show_host_detail.php?hostid=9618
and
http://oproject.info/results.php?hostid=9618

Plus 15 tasks for WUprop@home.
All whilst simultaneously crunching a Milkyway@home task that is 58% complete.

Yep, 3 BOINC tasks running concurrently :D

Image
User avatar
Posts: 96
Joined: Fri Mar 09, 2012 1:21 am
by Bikeman » Mon Jan 28, 2013 1:42 pm
Update:

The beta-test-project of Einstein@Home, Albert@Home ( http://albert.phys.uwm.edu ) is now hosting an experimental Raspi app. We are also testing a workunit pool that has tasks that are much shorter than usual and should be better suited for the Raspi (completion (CPU) time about one or two days, instead of almost 10 days before).

The app requires < 100 MB RAM while running.

Feel free to give it a try. Note that this is a beta project using test data only (so no real scientific discoveries (and the fame that comes with it)). But you can help test the app so that it is certified to go on the Einstein@Home project soon, if all goes well.

Cheers
HB
Posts: 46
Joined: Sun Nov 04, 2012 9:03 pm
Location: near Hannover, Germany
by Ray_GTI-R » Mon Jan 28, 2013 11:22 pm
The app requires < 100 MB RAM while running.

Error BRP Search requires 247.96mb RAM but you only have 166.20mb :?

I have the 256mb RPi Model B. Tried to file an error report on the beta forum but failed as I don't have enough credit ...
User avatar
Posts: 96
Joined: Fri Mar 09, 2012 1:21 am
by Bikeman » Wed Jan 30, 2013 8:15 pm
Hi!

Oh, thanks for spotting this. I'll try to get this one fixed tomorrow.

Cheers
HBE
Posts: 46
Joined: Sun Nov 04, 2012 9:03 pm
Location: near Hannover, Germany
by Bikeman » Thu Jan 31, 2013 12:02 pm
Hi!

Ok, fixed, you can try again. To allow some headroom, the setting now is that work will be distributed if the client reports 128 MB of available RAM.

Cheers
HB
Posts: 46
Joined: Sun Nov 04, 2012 9:03 pm
Location: near Hannover, Germany
by Ray_GTI-R » Fri Feb 08, 2013 1:02 am
Update .. in the past few days/weeks I have sucessfully run and completed Albert (1 task), Milkyway (2 tasks), WUProp (133 tasks) & Oproject (1,931 tasks) on my 256MB Model B RPi using Raspbian & BOINC 7.0.27.
Thanks, all, for your genius :mrgreen:
User avatar
Posts: 96
Joined: Fri Mar 09, 2012 1:21 am
by enginerd » Sat Feb 23, 2013 11:55 pm
any chance that we can get qcn support?
there is an existing "7.1.0" from the project site:
http://qcn.stanford.edu/sensor/download/boinc-armv6.zip
but i'm having a terrible time getting wifi to work on this older system image.
the vanilla raspbian easily runs the wifi dongle, but then has the issue of boinc configuration by total linux noobs.
either way, a daunting challenge! i'd rather be working with a current system image and install boinc in the "right" place and manner, but most guides read for the linux scholar, not someone of my limited skills.
thanks
Posts: 3
Joined: Sat Feb 23, 2013 11:46 pm
by dcarrion87 » Sun Feb 24, 2013 12:14 am
@enginerd

My understanding is that QCN is natively supported on Raspberry Pi armv6l. If you install the BOINC client using "apt-get install boinc" you should just be able to add http://qcn.stanford.edu/sensor/ as an individual project. Is this not the case for you?

I tried this on one of my Raspberry Pis and it attached and downloaded project files. It had no tasks available for me though.
Last edited by dcarrion87 on Sun Feb 24, 2013 12:20 am, edited 1 time in total.
User avatar
Posts: 36
Joined: Fri Nov 23, 2012 9:51 am
Location: Australia
by dcarrion87 » Sun Feb 24, 2013 12:17 am
BOINC application for Raspberry Pi news:

I've made a Raspberry Pi version of SubsetSum@Home available over on my project page for anyone that is interested. I've posted on their forums to try and get them to natively support it.

http://burdeview.blogspot.com.au/p/raspberry-pi-boinc-project-ive-created.html
User avatar
Posts: 36
Joined: Fri Nov 23, 2012 9:51 am
Location: Australia
by enginerd » Sun Feb 24, 2013 8:39 pm
not the case for me.
with the vanilla install, i can't get the sensor connected.
with the qcn built image, i can't get wifi to work.
out of luck either way!
wish i didn't need a phd in computer science to get this up and running...
Posts: 3
Joined: Sat Feb 23, 2013 11:46 pm
by jackokring » Sun Feb 24, 2013 9:00 pm
Un4Seen wrote:"Set the boinc binary and boincmgr binary to pass in your firewall on TCP port 31416. The boinc binary needs separate access to the internet on TCP ports 80 and 443."
Port 80 is in use by Apache, so I cannot use that one.
Ports 31416 and 443 are not configured in my router to be forwarded to my RPI (and I'm not at home so I cannot try it now).

It's a minor point, but incoming and outgoing can be different port numbers. So for examplemy browser could pick 4532 at random to connect 80 of the web server I'm looking at. It does not have to be 80 at both ends, and so apache is no problem. I think 31416 is maybe incoming for the background daemon, and outgoing for the GUI manager.
Pi=B256R0USB CL4SD8GB Raspbian Stock. https://sites.google.com/site/rubikcompression/strictly-long https://dl.dropboxusercontent.com/u/1615413/Own%20Work/Leptronics.pdf https://groups.google.com/forum/#!topic/comp.compression/t22ct_BKi9w
User avatar
Posts: 784
Joined: Tue Jul 31, 2012 8:27 am
Location: London, UK
by waltd » Mon Feb 25, 2013 11:22 am
Yes, I have BOINC and a BOINC project running on my Raspberry PI.
It wasn't easy and it took days of Google searches and emailing. But I have success and a BOINC project called Albert@home is running on my Raspberry PI. More BOINC projects are coming soon such as Einstein@home. But they are not ready yet.

Here's how I did it:
1. I installed BOINC client and BOINC manager as instructed on this web page http://wiki.debian.org/BOINC. The steps to install are under the section "Installation of binary packages". You'll install two packages, the client package and the manager package.
2. I went to the Albert@home web site at http://albert.phys.uwm.edu/ and created an account.
3. I started BOINC from the Unity GUI and went through the steps to add a project. I put in Albert@home's URL address which is http://albert.phys.uwm.edu/ to add this project.

All went well. The project was added and work was downloaded. The Pi is now processing the work. I'm very happy to be using my Raspberry Pi for a useful science project. Hope this helps.
Posts: 27
Joined: Mon Feb 18, 2013 12:58 pm
by dcarrion87 » Mon Feb 25, 2013 12:32 pm
enginerd wrote:not the case for me.
with the vanilla install, i can't get the sensor connected.
with the qcn built image, i can't get wifi to work.
out of luck either way!
wish i didn't need a phd in computer science to get this up and running...


Hmmm, sorry to hear it's such a headache. I'd like to help but I suspect that the QCN forum is the best bet for this since you're working with their sensor hardware. I actually asked them for a trial kit to do some testing on multiple ARM devices but they never got back to me.

Maybe you should try get the BOINC project working using the wired connection and then try to solve the wireless adapter problem afterwards? Depends on your priorities I guess, i.e. wireless or crunching first.

I'd probably prod the QCN support forums about getting the sensor working on the newer Raspbian image. Maybe it's just a driver/module that needs to be loaded? I really don't know that sensor hardware to be honest. I'm guessing you're already hitting up their forums anyway. :)
User avatar
Posts: 36
Joined: Fri Nov 23, 2012 9:51 am
Location: Australia
by waltd » Mon Feb 25, 2013 3:28 pm
waltd wrote:Yes, I have BOINC and a BOINC project running on my Raspberry PI.
It wasn't easy and it took days of Google searches and emailing. But I have success and a BOINC project called Albert@home is running on my Raspberry PI. More BOINC projects are coming soon such as Einstein@home. But they are not ready yet.

Here's how I did it:
1. I installed BOINC client and BOINC manager as instructed on this web page http://wiki.debian.org/BOINC. The steps to install are under the section "Installation of binary packages". You'll install two packages, the client package and the manager package.
2. I went to the Albert@home web site at http://albert.phys.uwm.edu/ and created an account.
3. I started BOINC from the Unity GUI and went through the steps to add a project. I put in Albert@home's URL address which is http://albert.phys.uwm.edu/ to add this project.

All went well. The project was added and work was downloaded. The Pi is now processing the work. I'm very happy to be using my Raspberry Pi for a useful science project. Hope this helps.


Error Correction: In step 3, I said that I opened BOINC in Unity GUI. That's incorrect. I opened BOINC in LXDE GUI.
Posts: 27
Joined: Mon Feb 18, 2013 12:58 pm
by enginerd » Mon Feb 25, 2013 7:08 pm
dcarrion87 wrote:
enginerd wrote:not the case for me.
with the vanilla install, i can't get the sensor connected.
with the qcn built image, i can't get wifi to work.
out of luck either way!
wish i didn't need a phd in computer science to get this up and running...


Hmmm, sorry to hear it's such a headache. I'd like to help but I suspect that the QCN forum is the best bet for this since you're working with their sensor hardware. I actually asked them for a trial kit to do some testing on multiple ARM devices but they never got back to me.

Maybe you should try get the BOINC project working using the wired connection and then try to solve the wireless adapter problem afterwards? Depends on your priorities I guess, i.e. wireless or crunching first.

I'd probably prod the QCN support forums about getting the sensor working on the newer Raspbian image. Maybe it's just a driver/module that needs to be loaded? I really don't know that sensor hardware to be honest. I'm guessing you're already hitting up their forums anyway. :)


yup - someone out there knows how to get this running, but that person isn't me yet...

i can see the sensor using "lsusb" and even read the output but it doesn't register with qcn. a permissions problem?

at least the pi is achieving its' intended goal of getting people into programming, i know i'd have never touched linux command line if it weren't for qcn/pi :^)

unfortunately i can only get a wired connection by bridging my work laptop's wireless to ethernet. so this is not a good solution. hopefully someone can explain how to install qcn 7.1.0 onto the regular raspbian image including permission changes and other tricky stuff.

thanks for your response!
Posts: 3
Joined: Sat Feb 23, 2013 11:46 pm
by waltd » Wed Feb 27, 2013 10:57 am
I'm using my RPi as a full time client to run BOINC Albert@home 24/7/365. I still need to go into LXDE GUI sometimes to check on the status of how BOINC is running and that everything is running ok. But mostly the Pi is only running BOINC. Since it's only running BOINC 24/7/365 on the Pi, can someone suggest what is the optimal CPU/GPU memory allocation for this type of processing.
Posts: 27
Joined: Mon Feb 18, 2013 12:58 pm
by Bikeman » Thu Feb 28, 2013 5:14 pm
waltd wrote:I'm using my RPi as a full time client to run BOINC Albert@home 24/7/365. I still need to go into LXDE GUI sometimes to check on the status of how BOINC is running and that everything is running ok. But mostly the Pi is only running BOINC. Since it's only running BOINC 24/7/365 on the Pi, can someone suggest what is the optimal CPU/GPU memory allocation for this type of processing.


Hi!
I'm running BOINC / Albert@Home on a 512 MB Raspi together with the Raspbmc media server. I tested this with as much as 192 MB allocated to the GPU and had no problems.

Cheers
HB
Posts: 46
Joined: Sun Nov 04, 2012 9:03 pm
Location: near Hannover, Germany
by Ray_GTI-R » Thu Mar 07, 2013 1:56 am
Experience running various BOINC projects on my RPi suggests more CPU memory over CPU overclock.

Maybe there is a memory threshhold vs marginal return/swapfile issue? I don't know as I'm only running 256mb - pretty sucessfully :lol:

See:- http://boincstats.com/en/stats/-1/host/ ... 905/charts
User avatar
Posts: 96
Joined: Fri Mar 09, 2012 1:21 am
by Ray_GTI-R » Mon Mar 18, 2013 1:10 am
Update to earlier posts:-

OProject
The subproject ALX appears to be discontinued for some weeks now so no OProject work for the RPi.
Also, IIRC, all OProject subprojects won't work on "old" BOINC versions e.g., (RPi) v7.0.27 and the much older, much beloved version provided by NativeBOINC. BOINC devs have released newer versions of BOINC that include ARM and should work with the RPi when force-installed but as I'm no :ugeek: I'll wait for a sudo update/upgrade(d) version of BOINC to become available.

Asteroids
Works on the RPi v7.0.27 "out of the box" and is vailable via "Add Project" (simple clicks to do this).
Estimate to complete +/- 6 days.
Also available for Android devices "out of the box" via NativeBOINC that uses the much older, much beloved version provided by NativeBOINC.
Estimate to complete +/- 6 days.

Um ... does anyone see patterns here?

HTH, Ray
User avatar
Posts: 96
Joined: Fri Mar 09, 2012 1:21 am
by yv1hx » Sun Apr 21, 2013 1:19 am
Hi fellas, some updates form this (very convulsed) corner of our world:

I was very interested in continue my cooperation with the Seti@home project using my RPi, but aware the very frequent and prolonged power cuts that we are suffering in my country several days a week, I was reluctant to spend time preparing the setup until I was capable to maintain my RPi operating with some kind of battery backup.

After several tries (using some discarded laptop battery packs) and parts from my scratch box, I find the proper way purchasing a external battery backup for recharging/powering portable devices (like cell phones), this device is powered from mains by any cell phone charger and has been capable to support my RPi powered at least 3 hours while computing the Seti task.

The battery backup device was purchased on Amazon http://www.amazon.com/gp/product/B006VZ3CIA/ref=oh_details_o00_s00_i00?ie=UTF8&psc=1
I'm not related in any way with this seller or any other.

After making myself sure about the reliability of the backup device, I followed the install instructions kindly provided by dcarrion87 in his site: http://burdeview.blogspot.com.au/p/raspberry-pi-boinc-project-ive-created.html and after roughly 323110 seconds, I go my first task completed. :D

Another of my concerns was the internal temperature while computing tasks, but this is subject-matter of other thread.
Marco-Luis
Telecom Specialist (Available for Hire!)

Please support our Voluntary Firefighters:
http://www.gofundme.com/dj8kf0

http://www.meteoven.org - http://twitter.com/meteoven
http://yv1hx.no-ip.org
http://twitter.com/yv1hx
User avatar
Posts: 238
Joined: Sat Jul 21, 2012 10:09 pm
Location: Zulia, Venezuela
by Bikeman » Tue May 07, 2013 10:17 pm
Hi all,

On the project Albert@Home (the beta test project for the Einstein@Home project), we have just released a new Raspberry Pi application version (for Raspis running under Raspian and similar Linuxes). It should be quite a bit faster than the previous version.

At the same time we are also beta-testing Einstein@Home on the Android platform, and it's quite interesting to see how the Android phones and tablets perform compared to the Raspberry Pi.

Almost all Android phones sold these days have multi-core ARMv7 CPUs with > 1GHz clock rates, one generation more advanced than the Raspi's single core ARMv6 CPU. But some low-end phones like the Samsung "Galaxy y" still have a CPU that is very similar to the Raspi's. The ARMv7 CPUs almost all have support for the NEON floating point single-instruction-multiple-data (SIMD) instructions which help a lot to boost performance in applications that are designed to make use of them.

Still, the Raspi performs surprisingly well at Einstein@Home. First, it can easily be overclocked to 0.9 ...1.0 GHz, and then it can easily beat low end Android phones, even some with newer ARMv7, NEON enabled CPUs. I suspect this has to do with the "hardfloat" ABI that Raspian and similar Linux versions for the Raspberry Pi are using. Android (on ARM) doesn't use this ABI and comes with quite a bit more overhead in handling floating point numbers.

So if you want to give us a hand in testing, please join the project at http://albert.phys.uwm.edu .

If all goes well we will launch the Raspi and Android versions on the "production" project Einstein@Home in a matter of a couple of weeks (latest July I'd say).

Heinz-Bernd Eggenstein
Albert-Einstein-Institute/Max-Planck-Institute for Gravitational Physics
Posts: 46
Joined: Sun Nov 04, 2012 9:03 pm
Location: near Hannover, Germany
by dcarrion87 » Wed Jun 12, 2013 4:17 am
Just a quick one to say I've compiled SETI v7 client for those that are running the v6 client at the moment.

http://burdeview.blogspot.com.au/2013/06/new-setihome-v7-client-for-raspberry-pi.html

Note that I've yet to have a task complete so some might want to hold off on updating until one does. I'm not sure what the status of the v6 client is and when they're going to discontinue it for use. I believe it's still being used for Astropulse?

I managed to pull a task that's going to take just under 2 weeks to finish :D. Might have to look at tweaking once I confirm the first task completes as there's been a few changes.
User avatar
Posts: 36
Joined: Fri Nov 23, 2012 9:51 am
Location: Australia