2. The boinc-client package (7.16.16) in the Debian repo, the service is disabled by default so you have to manually start it or enable the service if you want it to start automatically. Use "sudo systemctl enable boinc-client" to enable it.
2. The boinc-client package (7.16.16) in the Debian repo, the service is disabled by default so you have to manually start it or enable the service if you want it to start automatically. Use "sudo systemctl enable boinc-client" to enable it.
Thanks! That one was a head scratcher
And because of this I will wait until at least next week to bring mine up to the new version, I use a tv as a monitor and have an HDMI switch to switch between the different Pi's.
Another quirk I found was they are now using the systemd-timesyncd service. Its a rather basic SNTP service with not much in the way of configuration options. If you install ntp or ntpsec its smart enough to remove systemd-timesyncd. One of my support Pi's gets the time from a GPS and provides it to the other Pi's in my cluster.
As Keith mentioned a couple of messages before this, the project now have an FGRP5 arm64 app for Linux which I tried on a Pi4. Peak working set was 995MB but most of the time they use around 748MB, so recommend you use an 8GB Pi4. You might be able to get away with a 4GB model. They took 27 hours to run. Waiting for them to validate at the moment.
As far as I know this isn't the optimized app that N30dg wrote but one the project compiled for arm64. Hopefully the project can speed it up. I haven't seen N30dg on here in the last two years.
Still waiting on getting some of that work as I work through other projects cpu work. The Nano is only an ARM57 core so it will run much slower than on a Pi4.
The main purpose of the Nano is to run my BRP4 CUDA gpu application on anonymous platform.
Have a real 4GB Pi4 showing up today so itching to get it working on the ARM64 app for comparison.
As Keith mentioned a couple of messages before this, the project now have an FGRP5 arm64 app for Linux which I tried on a Pi4. Peak working set was 995MB but most of the time they use around 748MB, so recommend you use an 8GB Pi4. You might be able to get away with a 4GB model. They took 27 hours to run. Waiting for them to validate at the moment.
As far as I know this isn't the optimized app that N30dg wrote but one the project compiled for arm64. Hopefully the project can speed it up. I haven't seen N30dg on here in the last two years.
How do you get to run those tasks? Mine are saying app_info.xml does not have a version for it
Not sure if you are replying to me regarding my Nano or my Pi 4? For the Nano I had to add to my app_info.xml file to add the FGRP5 application to my custom BRP gpu app. That is the only reason to write an app_info.
For the Pi 4 you shouldn't need to write an app_info as the project has a stock aarch64 application version 1.16 for FGRP5. Just select the application in project preferences and you should get the app and some work.
In case you too need to run an app_info for some reason because you are not using stock applications here is my FGRP5 snippet for my app_info.xml for my Jetson Nano.
The Raspberry Pi foundation have now decided to officially embrace the 64 bit world. I've been running the "beta test" 64 bit builds since June 2020. Its now out of beta test and has an official build. The raspberrypi.com download page now has links to the 64 bit build. You can get it with a desktop or without (the lite version).
I don't know if the official image differs from the beta image although Jeff Geerling mentions on his Youtube channel that its closer to the Debian images instead of having hacks to allow the Pi to support > 4GB memory.
The Pi3, Pi4, Pi400 and the Pi Zero 2 W can all run it, although you might have issues on the Pi3 and Pi Zero 2 W due to the limited memory.
PorkyPies wrote: 2. The
)
Thanks! That one was a head scratcher
bowguy wrote: PorkyPies
)
And because of this I will wait until at least next week to bring mine up to the new version, I use a tv as a monitor and have an HDMI switch to switch between the different Pi's.
Anybody in this thread
)
Anybody in this thread running the FGRP5 cpu tasks on a ARM v8 64bit device?
Looking for your anonymous platform application section.
Another quirk I found was
)
Another quirk I found was they are now using the systemd-timesyncd service. Its a rather basic SNTP service with not much in the way of configuration options. If you install ntp or ntpsec its smart enough to remove systemd-timesyncd. One of my support Pi's gets the time from a GPS and provides it to the other Pi's in my cluster.
MarksRpiCluster
The project have an FGRP5
)
As Keith mentioned a couple of messages before this, the project now have an FGRP5 arm64 app for Linux which I tried on a Pi4. Peak working set was 995MB but most of the time they use around 748MB, so recommend you use an 8GB Pi4. You might be able to get away with a 4GB model. They took 27 hours to run. Waiting for them to validate at the moment.
As far as I know this isn't the optimized app that N30dg wrote but one the project compiled for arm64. Hopefully the project can speed it up. I haven't seen N30dg on here in the last two years.
MarksRpiCluster
Still waiting on getting some
)
Still waiting on getting some of that work as I work through other projects cpu work. The Nano is only an ARM57 core so it will run much slower than on a Pi4.
The main purpose of the Nano is to run my BRP4 CUDA gpu application on anonymous platform.
Have a real 4GB Pi4 showing up today so itching to get it working on the ARM64 app for comparison.
I've received FGRP5 tasks now
)
I've received FGRP5 tasks now and am crunching with the app. Progress has me finishing them in a little over 24 hours.
PorkyPies wrote: As Keith
)
How do you get to run those tasks? Mine are saying app_info.xml does not have a version for it
Not sure if you are replying
)
Not sure if you are replying to me regarding my Nano or my Pi 4? For the Nano I had to add to my app_info.xml file to add the FGRP5 application to my custom BRP gpu app. That is the only reason to write an app_info.
For the Pi 4 you shouldn't need to write an app_info as the project has a stock aarch64 application version 1.16 for FGRP5. Just select the application in project preferences and you should get the app and some work.
In case you too need to run an app_info for some reason because you are not using stock applications here is my FGRP5 snippet for my app_info.xml for my Jetson Nano.
<app>
<name>hsgamma_FGRP5</name>
<user_friendly_name>Gamma-ray pulsar search #5</user_friendly_name>
</app>
<file_info>
<name>hsgamma_FGRP5_1.16_aarch64-unknown-linux-gnu</name>
<executable/>
</file_info>
<app_version>
<app_name>hsgamma_FGRP5</app_name>
<platform>amd64-unknown-linux-gnu</platform>
<version_num>116</version_num>
<api_version>7.2.2</api_version>
<file_ref>
<file_name>hsgamma_FGRP5_1.16_aarch64-unknown-linux-gnu</file_name>
<main_program/>
</file_ref>
</app_version>
The Raspberry Pi foundation
)
The Raspberry Pi foundation have now decided to officially embrace the 64 bit world. I've been running the "beta test" 64 bit builds since June 2020. Its now out of beta test and has an official build. The raspberrypi.com download page now has links to the 64 bit build. You can get it with a desktop or without (the lite version).
I don't know if the official image differs from the beta image although Jeff Geerling mentions on his Youtube channel that its closer to the Debian images instead of having hacks to allow the Pi to support > 4GB memory.
The Pi3, Pi4, Pi400 and the Pi Zero 2 W can all run it, although you might have issues on the Pi3 and Pi Zero 2 W due to the limited memory.
MarksRpiCluster