I have not tried this but thought it might be of interest to the community. It is not the "/boot" partition on SD card and "/root" partition on usb approach but a self contained "all on usb device" approach. Anyway have a look.
Doing lots of maintenance of power applies and cases. Dug up stuff from my pi junk drawer and rebuilt everything I had. I now have the following models generating credit on Einstein@Home:
Zero
ZeroW
PiB
Pi3B
Pi3B+
I also have pi4's with credit but they are on Rosetta@Home. Fun little toys.
Added a Pi 4 8GB to the E@H effort. It is running Ubuntu 20.04 64bit. The computer ID ends in 7344. OS installation on Pi 4s seem to have difficulty with the HDMI interface unless you make adjustments to the /boot/firmware/usercfg.txt file (Ubuntu). Adding the line: hdmi_safe=1 helps with painting your monitor screen. Otherwise you just have a black screen. The usercfg.txt file gets picked up in the boot logic with ubuntu. Many solutions say to modify /boot/config.txt but the Header to this file on Ubuntu states the user should use the usercfg.txt file to make necessary adjustments. In Raspberrypi OS I don't believe there is a usercfg.txt file so one would have to use the config.txt file to make changes if you are experiencing problems with nothing written to screen.
HDMI recognition seems to be a bit of an issue with the Pi 4s, i.e. the Pi boots but nothing is being written to the screen/monitor without tweeking one of the files above depending on which OS you use. When done with Ubuntu 20 install you will have a 592x448 screen resolution which is quite useless but easily corrected my additional changes to the usercfg.txt file above.
I use Ubuntu because I know where everything is. Raspberrpi OS is a great OS too. I am just not that familiar with it so: "better the devil you know".
What app do you use on the Pi zeroes and Pi model B? I thought the 1.47 app didn’t work on them and the 1.06 stopped working with Stretch.
A year or so go I compiled it from source. It took a few minor bug tweaks but not bad. Now it is harder because it was built against some depreciated libraries.
I could post my binary if interested. A Zero only gets about 40 RAC but the memory is fine since there is only 1 CPU
I'm giving away my Pi2's and and a fair few Pi3's so that I can concentrate on the Pi4's. The bad news is you'll need to be in Australia. See my blog for details if interested.
I have an RP4 2gb running Raspberry Pi OS 32bit (armv7l). It seems to run the BRP4 app fine (first task is 26% complete.
I have four RP4 8gb running Raspberry Pi OS 64bit (aarch64). Natively, when asking for BRP4 tasks, it gets back "platform 'aarch64-unknown-linux-gnu' not found". Fair enough. Most projects that support RPs don't (yet). So I add the following to my cc_config.xml:
This works for other projects that only support 32bit, such as WCG. I am then able to get work (yay!). But the tasks all error out with the following:
Stderr output
<core_client_version>7.14.2</core_client_version>
<![CDATA[
<message>
process exited with code 127 (0x7f, -129)</message>
<stderr_txt>
../../projects/einstein.phys.uwm.edu/einsteinbinary_BRP4_1.06_arm-unknown-linux-gnueabihf: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory
Thanks for the suggestion. I tried that, but still getting errors. Any other suggestions? Is anyone successfully crunching this app with RP4 + Raspberry Pi OS 64 bit?
Stderr output
<core_client_version>7.14.2</core_client_version>
<![CDATA[
<message>
process exited with code 127 (0x7f, -129)</message>
<stderr_txt>
../../projects/einstein.phys.uwm.edu/einsteinbinary_BRP4_1.06_arm-unknown-linux-gnueabihf: relocation error: ../../projects/einstein.phys.uwm.edu/einsteinbinary_BRP4_1.06_arm-unknown-linux-gnueabihf: symbol h_errno version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference
Thanks for the suggestion. I tried that, but still getting errors. Any other suggestions? Is anyone successfully crunching this app with RP4 + Raspberry Pi OS 64 bit?
Stderr output
<core_client_version>7.14.2</core_client_version>
<![CDATA[
<message>
process exited with code 127 (0x7f, -129)</message>
<stderr_txt>
../../projects/einstein.phys.uwm.edu/einsteinbinary_BRP4_1.06_arm-unknown-linux-gnueabihf: relocation error: ../../projects/einstein.phys.uwm.edu/einsteinbinary_BRP4_1.06_arm-unknown-linux-gnueabihf: symbol h_errno version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference
</stderr_txt>
]]>
look at my list of computers. then look at: this link.
How To Boot From USB On
)
How To Boot From USB On Raspberry Pi 4
I have not tried this but thought it might be of interest to the community. It is not the "/boot" partition on SD card and "/root" partition on usb approach but a self contained "all on usb device" approach. Anyway have a look.
Doing lots of maintenance of
)
Doing lots of maintenance of power applies and cases. Dug up stuff from my pi junk drawer and rebuilt everything I had. I now have the following models generating credit on Einstein@Home:
Zero
ZeroW
PiB
Pi3B
Pi3B+
I also have pi4's with credit but they are on Rosetta@Home. Fun little toys.
Added a Pi 4 8GB to the E@H
)
Added a Pi 4 8GB to the E@H effort. It is running Ubuntu 20.04 64bit. The computer ID ends in 7344. OS installation on Pi 4s seem to have difficulty with the HDMI interface unless you make adjustments to the /boot/firmware/usercfg.txt file (Ubuntu). Adding the line: hdmi_safe=1 helps with painting your monitor screen. Otherwise you just have a black screen. The usercfg.txt file gets picked up in the boot logic with ubuntu. Many solutions say to modify /boot/config.txt but the Header to this file on Ubuntu states the user should use the usercfg.txt file to make necessary adjustments. In Raspberrypi OS I don't believe there is a usercfg.txt file so one would have to use the config.txt file to make changes if you are experiencing problems with nothing written to screen.
HDMI recognition seems to be a bit of an issue with the Pi 4s, i.e. the Pi boots but nothing is being written to the screen/monitor without tweeking one of the files above depending on which OS you use. When done with Ubuntu 20 install you will have a 592x448 screen resolution which is quite useless but easily corrected my additional changes to the usercfg.txt file above.
I use Ubuntu because I know where everything is. Raspberrpi OS is a great OS too. I am just not that familiar with it so: "better the devil you know".
EDIT: The following link provides a procedure on How to install Ubuntu 20.04 on a Pi 4
bowguy wrote: I now have the
)
What app do you use on the Pi zeroes and Pi model B? I thought the 1.47 app didn’t work on them and the 1.06 stopped working with Stretch.
MarksRpiCluster
PorkyPies wrote: What app do
)
A year or so go I compiled it from source. It took a few minor bug tweaks but not bad. Now it is harder because it was built against some depreciated libraries.
I could post my binary if interested. A Zero only gets about 40 RAC but the memory is fine since there is only 1 CPU
I'm giving away my Pi2's and
)
I'm giving away my Pi2's and and a fair few Pi3's so that I can concentrate on the Pi4's. The bad news is you'll need to be in Australia. See my blog for details if interested.
MarksRpiCluster
I have an RP4 2gb running
)
I have an RP4 2gb running Raspberry Pi OS 32bit (armv7l). It seems to run the BRP4 app fine (first task is 26% complete.
I have four RP4 8gb running Raspberry Pi OS 64bit (aarch64). Natively, when asking for BRP4 tasks, it gets back "platform 'aarch64-unknown-linux-gnu' not found". Fair enough. Most projects that support RPs don't (yet). So I add the following to my cc_config.xml:
<alt_platform>arm-unknown-linux-gnueabihf</alt_platform>
This works for other projects that only support 32bit, such as WCG. I am then able to get work (yay!). But the tasks all error out with the following:
Stderr output
<core_client_version>7.14.2</core_client_version>
<![CDATA[
<message>
process exited with code 127 (0x7f, -129)</message>
<stderr_txt>
../../projects/einstein.phys.uwm.edu/einsteinbinary_BRP4_1.06_arm-unknown-linux-gnueabihf: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory
</stderr_txt>
]]>
Any ideas how to resolve?
Reno, NV Team: SETI.USA
You need to install the 32
)
You need to install the 32 bit libraries for libstdc++. And then do the cc_config.xml alt_platform deal.
https://boinc.berkeley.edu/forum_thread.php?id=11411#75341
Keith Myers wrote: You need
)
Thanks for the suggestion. I tried that, but still getting errors. Any other suggestions? Is anyone successfully crunching this app with RP4 + Raspberry Pi OS 64 bit?
Stderr output
</stderr_txt>
]]>
Reno, NV Team: SETI.USA
zombie67 [MM wrote:]Keith
)
look at my list of computers. then look at: this link.