How to install app version 147 on Raspberry Pi 4B?

Einsteinpi
Einsteinpi
Joined: 10 Dec 14
Posts: 32
Credit: 819000
RAC: 204
Topic 229368

I'm trying to run Einstein@Home on a Raspberry Pi 4B. The downloads immediately fail with a "computer error." The app version is 106.

App version 147 is running successfully on a Pi 2B. How can I get version 147 installed on the Pi 4B? The "run beta" setting is set to "YES" in my account preferences and I've updated, but still get downloads showing app 106.

Thank you for your help.

Keith Myers
Keith Myers
Joined: 11 Feb 11
Posts: 4964
Credit: 18718450766
RAC: 6371539

Try detaching the Pi4 and

Try detaching the Pi4 and reattaching a few times to see if if you get the scheduler to send you the correct app.

The other solution is to run an anonymous app for the 1.47 version.  You can get the executable from your Pi2B.

 

Einsteinpi
Einsteinpi
Joined: 10 Dec 14
Posts: 32
Credit: 819000
RAC: 204

Many thanks for your prompt

Many thanks for your prompt reply. I've removed and added Einstein several times, but the downloads still show app version 106 with the subsequent computer errors.

Sorry, I don't know what needs to be done to try your other suggestion of running the anonymous app for the 1.47 version by getting the executable from the Pi 2B. Detail of specific steps would be much appreciated.

Keith Myers
Keith Myers
Joined: 11 Feb 11
Posts: 4964
Credit: 18718450766
RAC: 6371539

Right now you are in the

Right now you are in the penalty box for returning too many errors.  So 24 hour timeout.

I looked at my Pi4 and I am running the 1.61 app for BRP4.  That is a 64 bit app but I looked at your host OS details and I think you are running a 64 bit OS too so I think you should be getting the 1.61 app instead of the 1.47 app.

This is the app I am using. einsteinbinary_BRP4_1.61_aarch64-unknown-linux-gnu

The 1.47 app is geared toward 32 bit hosts.

You would have to craft a app_info.xml file for the BRP4 gpu tasks.

BOINC Application configuration

Anonymous platform

You would copy the 1.47 binary over from the Pi2B host to use in the app_info.xml file. But I think you really should use the 64 bit app if you really are using a 64 bit OS. 

You could try downloading it from these two Einstein servers.

</file_signature>
    <download_url>http://einstein-dl.phys.uwm.edu/download/einsteinbinary_BRP4_1.61_aarch64-unknown-linux-gnu</download_url>
    <download_url>http://einstein-dl.syr.edu/download/einsteinbinary_BRP4_1.61_aarch64-unknown-linux-gnu</download_url>
 

 

Einsteinpi
Einsteinpi
Joined: 10 Dec 14
Posts: 32
Credit: 819000
RAC: 204

I think the Raspberry Pi OS I

I think the Raspberry Pi OS I installed is the 32-bit version. This is the output from cat /etc/os-release:

PRETTY_NAME="Raspbian GNU/Linux 11 (bullseye)"

NAME="Raspbian GNU/Linux"

VERSION_ID="11"

VERSION="11 (bullseye)"

VERSION_CODENAME=bullseye ID=raspbian

ID_LIKE=debian

HOME_URL="http://www.raspbian.org/"

SUPPORT_URL="http://www.raspbian.org/RaspbianForums" BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"

Writing an app_info.xml file to get this to run on the Pi 4B is probably way beyond my capability. But, it seems to me that I shouldn't have to do that in any case. The Einstein installer should recognize the Pi's architecture and install the appropriate app for that machine.

Once the time-out penalty is lifted tomorrow, I'll again try removing and adding the project and hope for the best. Einstein@home was working on this computer some months ago. It installed and ran with no glitches at that time. (It ran headlessly, with the GPU memory set at 16MB.)

Again, thank you for your suggestions and comments. I appreciate you taking the time to offer your help.

Keith Myers
Keith Myers
Joined: 11 Feb 11
Posts: 4964
Credit: 18718450766
RAC: 6371539

The easiest and simplest way

The easiest and simplest way to check for the OS bitness is from the terminal with this command:

uname -m

For my Pi4 this is the output:

keith@Pi4:~ $ uname -m
aarch64

It is not that hard to craft a app_info.xml.   I provided the links to the examples for anonymous platform.

This for example is my anonymous platform app_info.xml for my Jetson Nano so I can run custom BRP4 applications. Yours wouldn't be as involved with just the stock application.

keith@Nano:~/BOINC/projects/einstein.phys.uwm.edu$ cat app_info.xml
<app_info>

  <app>
    <name>einsteinbinary_BRP4</name>
  </app>
  <file_info>
    <name>einsteinbinary_cuda64</name>
    <executable/>
  </file_info>
  <file_info>
    <name>einsteinbinary_cuda-db.dev</name>
  </file_info>
  <file_info>
    <name>einsteinbinary_cuda-dbhs.dev</name>
  </file_info>
  <file_info>
    <name>libcufft.so.8.0</name>
  </file_info>
  <file_info>
   <name>libcudart.so.8.0</name>
  </file_info>
  <app_version>
    <app_name>einsteinbinary_BRP4</app_name>
    <version_num>999</version_num>
    <api_version>7.2.2</api_version>
    <coproc>
      <type>CUDA</type>
      <count>1.0</count>
    </coproc>
    <file_ref>
      <file_name>einsteinbinary_cuda64</file_name>
      <main_program/>
    </file_ref>
    <file_ref>
      <file_name>einsteinbinary_cuda-db.dev</file_name>
      <open_name>db.dev</open_name>
      <copy_file/>
    </file_ref>
    <file_ref>
      <file_name>einsteinbinary_cuda-dbhs.dev</file_name>
      <open_name>dbhs.dev</open_name>
      <copy_file/>
    </file_ref>
    <file_ref>
    <file_name>libcufft.so.8.0</file_name>
    </file_ref>
    <file_ref>
      <file_name>libcudart.so.8.0</file_name>
    </file_ref>
  </app_version>

 <app>
    <name>einsteinbinary_BRP4G</name>
 </app>
  <file_info>
    <name>einsteinbinary_cuda64</name>
    <executable/>
  </file_info>
  <file_info>
    <name>einsteinbinary_cuda-db.dev</name>
  </file_info>
  <file_info>
    <name>einsteinbinary_cuda-dbhs.dev</name>
  </file_info>
  <file_info>
    <name>libcufft.so.8.0</name>
  </file_info>
  <file_info>
   <name>libcudart.so.8.0</name>
  </file_info>
  <app_version>
    <app_name>einsteinbinary_BRP4G</app_name>
    <version_num>999</version_num>
    <api_version>7.2.2</api_version>
    <coproc>
      <type>CUDA</type>
      <count>1.0</count>
    </coproc>
    <file_ref>
      <file_name>einsteinbinary_cuda64</file_name>
      <main_program/>
    </file_ref>
    <file_ref>
      <file_name>einsteinbinary_cuda-db.dev</file_name>
      <open_name>db.dev</open_name>
      <copy_file/>
    </file_ref>
    <file_ref>
      <file_name>einsteinbinary_cuda-dbhs.dev</file_name>
      <open_name>dbhs.dev</open_name>
      <copy_file/>
    </file_ref>
    <file_ref>
    <file_name>libcufft.so.8.0</file_name>
    </file_ref>
    <file_ref>
      <file_name>libcudart.so.8.0</file_name>
    </file_ref>
  </app_version>

</app_info>

Your app_info.xml would be just something like this:

<app_info>

  <app>
    <name>einsteinbinary_BRP4</name>
  </app>
  <file_info>
    <name>einsteinbinary_BRP4_1.61_aarch64-unknown-linux-gnu</name>
    <executable/>
  </file_info>

  <app_version>
    <app_name>einsteinbinary_BRP4</app_name>
    <version_num>161</version_num>
    <file_ref>
      <file_name>einsteinbinary_BRP4_1.61_aarch64-unknown-linux-gnu</file_name>
      <main_program/>
    </file_ref>
  </app_version>

</app_info>

 

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.