Page 1 of 1

Identifying the Board to BOINC

PostPosted: Thu Mar 13, 2014 10:42 am
by Janos
For Parallella to work on BOINC it will need to broadcast it's name.

All it says just now is:

Code: Select all
CPU type                      ARM
Number of processors            2
Coprocessors                  ---
Operating System   Linux 3.12.0-g0bc9c3a-dirty


My board is here: http://www.enigmaathome.net/show_host_detail.php?hostid=122657

Re: Identifying the Board to BOINC

PostPosted: Thu Mar 13, 2014 11:11 am
by Claggy
Can you post the Boinc startup from the Event log please, the first 30 lines should do.

Claggy

Re: Identifying the Board to BOINC

PostPosted: Thu Mar 13, 2014 11:39 am
by Janos
Here you go:

Code: Select all
01/01/1970 00:00:50 |  | Starting BOINC client version 7.2.7 for arm-unknown-linux-gnueabihf
01/01/1970 00:00:50 |  | log flags: file_xfer, sched_ops, task
01/01/1970 00:00:50 |  | Libraries: libcurl/7.32.0 OpenSSL/1.0.1e zlib/1.2.8 libidn/1.28 librtmp/2.3
01/01/1970 00:00:50 |  | Data directory: /var/lib/boinc-client
01/01/1970 00:00:50 |  | Processor: 2 ARM
01/01/1970 00:00:50 |  | Processor features: swp half thumb fastmult vfp edsp neon vfpv3 tls vfpd32
01/01/1970 00:00:50 |  | OS: Linux: 3.12.0-g0bc9c3a-dirty
01/01/1970 00:00:50 |  | Memory: 969.19 MB physical, 0 bytes virtual
01/01/1970 00:00:50 |  | Disk: 28.50 GB total, 24.46 GB free
01/01/1970 00:00:50 |  | Local time is UTC +0 hours
01/01/1970 00:00:50 |  | No usable GPUs found
01/01/1970 00:00:50 |  | [error] bad value 1394643279.527320 of time stats last update; ignoring
01/01/1970 00:00:50 |  | Config: GUI RPCs allowed from:
01/01/1970 00:00:50 |  | 192.168.1.12

Re: Identifying the Board to BOINC

PostPosted: Thu Mar 13, 2014 12:23 pm
by Claggy
I assume that was from the Repository, I was hoping Boinc 7.2.42 would be in it, looking at the packages Saucy Salamander gets 7.2.7+dfsg-1,
while Trusty Tahr gets 7.2.42+dfsg-1, I was going to suggest a PPA you could add, but armhf failed to build on it, i'll email LocutusOfBorg later.

I'm thinking that we need (for now) a parallella primary platform, with arm-unknown-linux-gnueabihf (or armv7-unknown-linux-gnueabihf) as alternate,
i'll email the devs later and suggest it.

Claggy

Re: Identifying the Board to BOINC

PostPosted: Thu Mar 13, 2014 12:39 pm
by 9600
Janos wrote:For Parallella to work on BOINC it will need to broadcast it's name.

All it says just now is:

Code: Select all
CPU type                      ARM
Number of processors            2
Coprocessors                  ---
Operating System   Linux 3.12.0-g0bc9c3a-dirty


I raised the issue of identifying Parallella boards to BOINC projects last year, and it appears that the options are to treat it as an ARM host + Epiphany co-processor, or a new platform called Parallella. The former has the advantage that it may make it easier to support future systems other than Parallella, which have an Epiphany co-processor. Whereas the 2nd option would seem the easier route and simply requires building with a custom configure switch.

For details of the discussion see the list archive.

Once we have decided upon a platform there then is the matter of adding Epiphany offload support to BOINC projects, and if anyone is interested in working on this I believe that David Richie (dar) has taken a look at porting a couple of projects to using COPRTHR, and can probably share some useful insights.

Cheers,

Andrew

Re: Identifying the Board to BOINC

PostPosted: Thu Mar 13, 2014 12:45 pm
by Janos
Claggy wrote:I assume that was from the Repository...


Yes, just a standard apt-get.

Re: Identifying the Board to BOINC

PostPosted: Mon Jun 02, 2014 9:05 am
by MarkjBOINC
I have Trusty installed and BOINC 7.2.42. I tried defining the epiphany as coprocessor via cc_config which didn't seem to work. I emailed the alpha mailing list and DA has said he has checked in a fix. He didn't say what so I presume it's in the core client. Unfortunately it might take a while to get it through the repo unless somebody wants to compile their own client on the Parallella.

While it may pass through to project servers we'll still need project apps to add Epiphany support but it's a first step.

Re: Identifying the Board to BOINC

PostPosted: Wed Sep 17, 2014 11:50 am
by MarkjBOINC
There is a 7.4.13 BOINC client available from LocutusofBorg's ppa. It now has the ability if you define your own coprocessor to request work for it, so I discovered by accident. I managed to ask Einstein@home for work for an Epiphany16, of course there wasn't any. So it looks like it's telling the project it has a coprocessor now.

The backend plumbing needs to be put in place for it to work and of course we'll need some apps that can use the Epiphany.

As Claggy mentioned they have also been working on OpenCL detection for devices so if Linux can find the OpenCL.so then BOINC should also be able to report that. You'll have to install the OpenCL stuff from Brown Deer to get it though.

MarkJ