Parallella, Raspberry Pi, FPGA & All That Stuff

Anonymous

N30dG wrote:Quote:Quote:4.

23 May 2017 1:37:10 UTC

Message 158183 in response to message 158172

(moderation:

)

N30dG wrote:

Quote:
Quote:

4. install the app:

cd ..

sudo dpkg -i boinc-app-eah-brp_0.20170426+dfsg-3_arm64.deb

generated the following deb: boinc-app-eah-brp_0.20170426+dfsg-3_armhf.deb

Sorry, my mistake, the armhf is the right package for your device :) So you should install that.

sudo dpkg -i boinc-app-eah-brp_0.20170426+dfsg-3_armhf.deb

Now you should restart boinc-client and try it. At this moment you run without a wisdom-file, so don't expect that it run too fast at this point.

did the above two steps but put on a 23 hour delay. reset the project but no work

Quote:

The script is currently under development. The output is maybe a little bit confusing ;).

Quote:

finished in seconds with the following issues:

./boinc-app-eah-brp/debian/extra/create_wisdomf_eah_brp.sh I: Computing wisdom file for BRP4 and FGRP projects. This will take several hours if not days.

I: Generating wisdom for (2^22)*3 sample projects (BRP) W: Not recognising platform 'armv7l' as sufficiently capable for 2^26 bit projects fftw-wisdom:

This is normal behavior. The script generates a wisdom for the FGRP (2^26) too. But there is no need for that wisdom on arm-devices. So the script skips the generation of that.

Quote:

system-wisdom import failed PLANNING PROBLEM: rof12582912

That is okay, there is no system-wisdom at that point.

The problem with the short runtime of the wisdom-generation is caused by a bug in the current libfftw3 debian/ubuntu-package on ARM-devices. fftw can not access the performance-timer on ARM-devices. So it can't make the necessary measurements to generate a wisdom. Instead it only guesses the right settings and put that into the wisdomfile. Thats why it only takes seconds to compute.

We fixed that. But the fixed version(3.3.6p2-1) is only available under debian sid/unstable or ubuntu artful/devel at the moment.

I guess you are running ubuntu xenial on your odroid?

yes

Quote:

There are several ways to get the new Version of the fftw3-package. This is only one way and not the best way to do it.

will look into doing this tomorrow

Quote:

edit your sources.list and add the following lines to it:

sudo nano /etc/apt/sources.list

deb http://ports.ubuntu.com/ubuntu-ports/ devel main restricted deb-src http://ports.ubuntu.com/ubuntu-ports/ devel main restricted

do a update, NO UPGRADE!!!

sudo apt-get update

check the installation-candidate

apt-cache policy libfftw3-dev

You should find this in the output: Candidate: 3.3.6p2-1

Install it:

sudo apt-get install libfftw3

Remove both lines from soures.list

do apt-get update again

steffen_moeller

Joined: 9 Feb 05

Posts: 78

Credit: 1773655132

RAC: 0

Hello, Ubuntu already has

23 May 2017 8:20:40 UTC

Message 158191

(moderation:

)

Hello, Ubuntu already has boinc-app-eah-brp in the upcoming "artful" distribution
(https://packages.ubuntu.com/search?keywords=boinc-app-eah-brp)
and so is the fftw3 3.3.6p2 version (https://packages.ubuntu.com/source/artful/fftw3).

I am too swamped to address the backporting to earlier Ubuntu releases myself. Any volunteers out there? Ubuntu has the fantastic well-established concepts of PPA (Personal Package Archives) that would do the job to auto-build the package upon submitting a so called source package. Everyone could do that, really, also computer-enthusiastic non-programmers, ... I am too swamped to promise any long term commitment myself on this, so I better reject any active involvement on Ubuntu backports upfront. The backports for Debian I'll help out with.

Here is a PPA for the regular BOINC packages, which also includes SETI@Home for the time your distribution is not directly supported for BRP: https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/boinc

N30dG

Joined: 29 Feb 16

Posts: 89

Credit: 4805610

RAC: 0

did the above two steps but

23 May 2017 17:34:41 UTC

Message 158212

(moderation:

)

did the above two steps but put on a 23 hour delay. reset the project but no work

I need some more infos to help. Could provide the output of boinc's eventlog?

In Boinc-Manager go to Tools -> Event Log; (Use the copy all Button)

Anonymous

N30dG wrote: did the above

23 May 2017 18:41:04 UTC

Message 158214 in response to message 158212

(moderation:

)

N30dG wrote:

did the above two steps but put on a 23 hour delay. reset the project but no work

I need some more infos to help. Could provide the output of boinc's eventlog?

In Boinc-Manager go to Tools -> Event Log; (Use the copy all Button)

I did a reset on the project and what follows is the content of "Event Log". There are no WUs/tasks showing up in Boinc_Manager.

N30dG

Joined: 29 Feb 16

Posts: 89

Credit: 4805610

RAC: 0

Ahh, okay. It doesn't seems

23 May 2017 18:54:27 UTC

Message 158216

(moderation:

)

Ahh, okay. It doesn't seems to found a app_info.xml. It seems that the installation using dpkg -i havn't worked *strange*.

Could you prove that? Go to your boinc-project-folder: /var/lib/boinc-client/projects/einstein.phys.uwm.edu in my case.

There should be a link to a app_info.xml and a einsteinbinary_BRP4. Both should have boinc as owner.

If that's not the case, you have to manually copy the einsteinbinary_BRP4 to this folder change the owner to boinc and create a app_info.xml. If you need help with that write me a PM ;)

Anonymous

N30dG wrote:Ahh, okay. It

23 May 2017 20:25:47 UTC

Message 158219 in response to message 158216

(moderation:

)

N30dG wrote:

Ahh, okay. It doesn't seems to found a app_info.xml. It seems that the installation using dpkg -i havn't worked *strange*.

Could you prove that? Go to your boinc-project-folder: /var/lib/boinc-client/projects/einstein.phys.uwm.edu in my case.

There should be a link to a app_info.xml and a einsteinbinary_BRP4. Both should have boinc as owner.

If that's not the case, you have to manually copy the einsteinbinary_BRP4 to this folder change the owner to boinc and create a app_info.xml. If you need help with that write me a PM ;)

The directory: /var/lib/boinc-client/projects/einstein.phys.uwm.edu contains the following:

-rw-r--r-- 1 boinc boinc 489 Jul 18 2016 app_info.xml <--- not a link and note date probably wrong/incorrect file

and

lrwxrwxrwx 1 boinc boinc 46 May 22 20:42 einsteinbinary_BRP4 -> /usr/lib/boinc-app-eah-brp/einsteinbinary_BRP4

ls -l /usr/lib/boinc-app-eah-brp/einsteinbinary_BRP4
-rwxr-xr-x 1 root root 68396 May 21 19:08 /usr/lib/boinc-app-eah-brp/einsteinbinary_BRP4 - note ownership

contents of app_info.xml :

<app_info>
<app>
<name>einsteinbinary_BRP4</name>
</app>
<file_info>
<name>einsteinbinary_BRP4_0.13_AARCH64-unknown-linux-gnu</name>
<executable/>
</file_info>
<app_version>
<app_name>einsteinbinary_BRP4</app_name>
<version_num>013</version_num>
<file_ref>
<file_name>einsteinbinary_BRP4_0.13_AARCH64-unknown-linux-gnu</file_name>
<main_program/>
</file_ref>
</app_version>
</app_info>

Anonymous

First let me say that I have

24 May 2017 15:57:03 UTC

Message 158245 in response to message 158122

(moderation:

)

First let me say that I have a single WU processing on the Odroid XU4. How this happened though I am not sure. For this reason I am replying to N30DG's original procedure and where I believe an problem may have occurred.

N30dG wrote:

You could build the BRP-App from our github-repositroy at your own. It's not that hard.

1. install git-buildpackage & build-dependencies

sudo apt-get update

sudo apt-get install git-buildpackage debhelper libboinc-app-dev libxml2-dev libiberty-dev libgsl-dev binutils-dev libfftw3-dev pkg-config

2. clone from our repositroy:

gbp clone https://github.com/VolunteerComputingHelp/boinc-app-eah-brp.git --pristine-tar

3. build the app:

cd boinc-app-eah-brp/

gbp buildpackage -uc -us

4. install the app:

cd ..

sudo dpkg -i boinc-app-eah-brp_0.20170426+dfsg-3_arm64.deb

It was noted in an earlier post that the above command might have failed to generate the app_info.xml file. I noted that there was an app_info.xml file in /var/lib/boinc-client/projects/einstein.phys.uwm.edu and that it had a 2016 date. I removed it and reran the above dpkg command and this time a new app_info.xml link was generated in the project directory. There was also a new link for einsteinbinary_BRP4 -> /usr/lib/boinc-app-eah-brp/einsteinbinary_BRP4

I restarted boinc-client and reset it. Still no work until I made a change to my preference set (generic in my case for the XU4) - USE CPU -> NO, and Run CPU versions of apps for which GPU versions are available -> Yes

I then did a project update and received one WU which is estimating at 3 hours 47 minutes.

Not sure if any of this makes sense. The short version might be that I just "fat fingered" N30DG's procedure

Quote:

5. generate a wisdom

./boinc-app-eah-brp/debian/extra/create_wisdomf_eah_brp.sh

(wait until finished, some hours)

sudo mkdir /etc/fftw

sudo mv /tmp/wisdomf /etc/fftw/

6. restart boinc-client:

sudo systemctl restart boinc-client

7. Be happy with your new fast cruncher

8. Tell me if that worked for you, and I tell you how to get it even faster .

N30dG

Joined: 29 Feb 16

Posts: 89

Credit: 4805610

RAC: 0

Zitat:It was noted in an

24 May 2017 17:07:40 UTC

Message 158250

(moderation:

)

Quote:

It was noted in an earlier post that the above command might have failed to generate the app_info.xml file. I noted that there was an app_info.xml file in /var/lib/boinc-client/projects/einstein.phys.uwm.edu and that it had a 2016 date. I removed it and reran the above dpkg command and this time a new app_info.xml link was generated in the project directory. There was also a new link for einsteinbinary_BRP4 -> /usr/lib/boinc-app-eah-brp/einsteinbinary_BRP4

You tryed to use my optimized AArch64-App before, that can not work. This app only works with cortex-A53 in 64bit-mode! Thats why the installation of your self-build package fails. It couldn't link the app-info, because there was already a file with that name.

Quote:

I restarted boinc-client and reset it. Still no work until I made a change to my preference set (generic in my case for the XU4) - USE CPU -> NO, and Run CPU versions of apps for which GPU versions are available -> Yes

I then did a project update and received one WU which is estimating at 3 hours 47 minutes.

Pretty fast, considering that you don't have a proper wisdom at the moment.

Quote:

Not sure if any of this makes sense. The short version might be that I just "fat fingered" N30DG's procedure

Zitat:

5. generate a wisdom

./boinc-app-eah-brp/debian/extra/create_wisdomf_eah_brp.sh

(wait until finished, some hours)

sudo mkdir /etc/fftw

sudo mv /tmp/wisdomf /etc/fftw/

6. restart boinc-client:

sudo systemctl restart boinc-client

7. Be happy with your new fast cruncher

8. Tell me if that worked for you, and I tell you how to get it even faster .

Try to upgrade your fftw-version to 3.3.6p2-1 before. Then run the create_wisdomf_eah_brp.sh again and copy the new wisdom to /etc/fftw/wisdomf
It should take some hours to compete.

I'm excited to hear about your run-times after that. I guess it will much blow 3h. Maybe below 2h.

Anonymous

Quote:Try to upgrade

24 May 2017 22:58:58 UTC

Message 158252 in response to message 158250

(moderation:

)

Quote:

Try to upgrade your fftw-version to 3.3.6p2-1 before. Then run the create_wisdomf_eah_brp.sh again and copy the new wisdom to /etc/fftw/wisdomf

It should take some hours to compete.

I'm excited to hear about your run-times after that. I guess it will much blow 3h. Maybe below 2h.

did the following:

1. downloaded 3.3.6 version from site
2. gunziped the file
3. tar -xvf fftw-3.3.6-pl2.tar
4. cd fftw-3.3.6-pl2
5. ./configure
6. make
7. make install

the above seemed to run fine.

ran

./boinc-app-eah-brp/debian/extra/create_wisdomf_eah_brp.sh this took maybe 2 minutes

sudo mkdir /etc/fftw

sudo mv /tmp/wisdomf /etc/fftw/

restarted boinc-cllient

also had to change account/preferences/project/usecpu to yes from no.

an update now is running 4 consecutive tasks with duration of ~4 hours.

Again not sure if the wisdom file was correctly generated. What follows is the content of the generate file:

(fftw-3.3.4 fftwf_wisdom #x4a633eef #xb5a95564 #x91014bdd #x9c85ce5f (fftwf_dft_vrank_geq1_register 0 #x11048 #x11048 #x0 #x3ccfdb1a #xf8b7fb16 #xb777192b #xa86989c1) (fftwf_codelet_t1fv_32_neon 0 #x11048 #x11048 #x0 #x13a350ff #xccbd0d68 #x1df44d80 #x16ee0d41) (fftwf_codelet_hc2cfdftv_16_neon 0 #x11048 #x11048 #x0 #xead3fd9e #xffec487c #x5b618d5e #x8f8f3b12) (fftwf_codelet_r2cfII_16 2 #x11048 #x11048 #x0 #xf4d971ab #x381e69c1 #xc4398fe0 #x3f2135b1) (fftwf_codelet_t2fv_16_neon 0 #x11048 #x11048 #x0 #x3d0b62a7 #x15d0e0a0 #xd8a2423f #xa9a6da1c) (fftwf_dft_vrank_geq1_register 0 #x11048 #x11048 #x0 #xbddeb44e #xfd7343e7 #x3c8fc850 #x6888d042) (fftwf_codelet_t1fv_12_neon 0 #x11048 #x11048 #x0 #x821ed100 #xa1017c4b #x40993259 #x7860b2a1) (fftwf_codelet_r2cf_16 2 #x11048 #x11048 #x0 #x8f3ef9f7 #xe67e11ab #xe25a4700 #x8eed687a) (fftwf_dft_vrank_geq1_register 0 #x11048 #x11048 #x0 #xa65ca367 #xee5c44cb #x0578eeed #x986cea5e) (fftwf_dft_vrank_geq1_register 1 #x11048 #x11048 #x0 #xd97dcac9 #xd6110c1d #x25bf8814 #xe9a1ed91) (fftwf_codelet_n1fv_128_neon 0 #x11048 #x11048 #x0 #xdcd9ab89 #x9279272f #x45725e3d #xb22380a2)

[EDIT] the temp on the xu4 is averaging 92C

N30dG

Joined: 29 Feb 16

Posts: 89

Credit: 4805610

RAC: 0

Zitat: did the following: 1.

25 May 2017 14:38:15 UTC

Message 158281

(moderation:

)

Quote:

did the following:

1. downloaded 3.3.6 version from site
2. gunziped the file
3. tar -xvf fftw-3.3.6-pl2.tar
4. cd fftw-3.3.6-pl2
5. ./configure
6. make
7. make install

the above seemed to run fine.

You configured fftw wrong. You need to apply --enable-float --with-slow-timer --enable-neon to the ./configure.

And I'm not shure what make install does. I would suggest you to install the libfftw3-dev package from artful or devel instead.

Parallella, Raspberry Pi, FPGA & All That Stuff

Forums › Cruncher's Corner

Comment viewing options

Forums › Cruncher's Corner