second, you've installed 32-bit BOINC, so it will only get 32-bit apps despite you having a 64-bit OS.
64-bit arm BOINC starts up like this: Mon 29 Jul 2024 10:12:30 AM EDT | | Starting BOINC client version 7.20.5 for aarch64-unknown-linux-gnu
OK I put the <options> tags in and it now does not error when loading the cc_config. I downloaded some new work and got 32 bit tasks for my 32 bit Boinc install but I still have the error.
</p>
<p>c1</p>
<p>1 30/07/2024 11:48:13 AM Starting BOINC client version 7.14.2 for arm-unknown-linux-gnueabihf <br />
2 30/07/2024 11:48:13 AM log flags: file_xfer, sched_ops, task <br />
3 30/07/2024 11:48:13 AM Libraries: libcurl/7.64.0 OpenSSL/1.1.1n zlib/1.2.11 libidn2/2.0.5 libpsl/0.20.2 (+libidn2/2.0.5) libssh2/1.8.0 nghttp2/1.36.0 librtmp/2.3 <br />
4 30/07/2024 11:48:13 AM Running as a daemon <br />
5 30/07/2024 11:48:13 AM Data directory: /usr/bin <br />
6 30/07/2024 11:48:14 AM No usable GPUs found <br />
7 30/07/2024 11:48:14 AM [libc detection] gathered: 2.28, Debian GLIBC 2.28-10+rpt2+rpi1+deb10u2 <br />
8 30/07/2024 11:48:14 AM Host name: c1 <br />
9 30/07/2024 11:48:14 AM Processor: 4 ARM [Impl 0x41 Arch 8 Variant 0x0 Part 0xd08 Rev 3] <br />
10 30/07/2024 11:48:14 AM Processor features: fp asimd evtstrm crc32 cpuid <br />
11 30/07/2024 11:48:14 AM OS: Linux Raspbian: Raspbian GNU/Linux 10 (buster) [6.6.39-v8+|libc 2.28 (Debian GLIBC 2.28-10+rpt2+rpi1+deb10u2)] <br />
12 30/07/2024 11:48:14 AM Memory: 3.71 GB physical, 100.00 MB virtual <br />
13 30/07/2024 11:48:14 AM Disk: 28.14 GB total, 22.99 GB free <br />
14 30/07/2024 11:48:14 AM Local time is UTC +10 hours <br />
</p>
<p>
</p>
<h3>Stderr output</h3>
<pre>
<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>
]]></pre>
<p>
If I have 32 bit boinc and get a 32 bit job I shouldn't get the error ??
@Keith Myers I think I might have to do a re install but with eight RPI's all headless it is a pain and I do not have a cable at the moment to hook up to a monitor.
You get the error probably because you lack the 32-bit libraries for the 32-bit apps. You can add these, and it would stop the error, but your production would be a lot less than what it could be. I would recommend getting the 64-bit BOINC installed so you can get the 64-bit apps and make the most of the hardware.
sudo apt-get install libc6:armhf libstdc++6:armhf
Reading package lists... Done
Building dependency tree
Reading state information... Done
libstdc++6 is already the newest version (8.3.0-6+rpi1).
libc6 is already the newest version (2.28-10+rpt2+rpi1+deb10u2).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
I will have to install the newest version of Raspberry Pi for 64 bit and Install BOINC again etc. Just a pain when all the pi's are headless.
I wouldn't deal with the hardware directly for the installs. I'd just gather up all eight SDHC cards and sit down in front of a machine with a keyboard and monitor and clone the 64 bit install of the distro along with the 64 bit BOINC installations with my favorite imaging/cloning software for Pi's.
I use Balena Etcher to write my Pi boot cards. Balene Etcher
I have installed Raspberry 64 bit which includes setting the hostname, the wifi and password, and opening port 22 for ssh on my 16 RPI 4's. I used the Raspberry Pi Imager to write the cards.
I do not have a hdmi to micro hdmi cable, I installed the current software in 2022, so could not see if any of them worked but they should as they all verified OK. Can't find a way to find the ip addresses of them as the hostname is not recognised. I thought that I would be able to see them on my router but nothing there.
Going to the shops tomorrow to get a cable and configure them all for static ip so I can use putty to communicate with them.
Why do you have the armhf architecture installed on the Pi's? Is it for some other project that only has 32 bit apps?
I think that because of it being installed, the scheduler is sending you the lowest common denominator app which is 32 bit and not supported by your silicon.
If you don't want to remove the armhf architecture, then I believe your only other option is to go with an app_info installation and call the proper 64 bit 1.61 app directly.
I've been through a similar odyssey the last few days with a brand new RPi5, which proved to be a misunderstanding on my part. I purchased it from PiHut along with a pre installed sd card , power supply and heatsink case.
Booted it up fine, installed boinc, attached to my usual projects. Asteroids@home worked fine, but Einstein at home gave me compute errors.
I was scratching my head as other people seem to have no issues.
I tried many of the points here, and eventually realised the SD card came preinstalled with the 32-bit Raspian, not 64 bit. DOH !
So I imaged a 64 bit SD, booted and einstein@home has been working fine , barring a couple of inconclusive results.
uname -m was correctly reporting the machine as aarch64, but it was when I ran the file command on any standard OS binary i.e. file /usr/bin/top
It was confirmed it was a 32-bit binary
My fault, I assumed that the sdcard would be the 64-bit version with any Pi4 or 5 ?
Another thing I notice is it runs a lot cooler. Running 32bit on the Pi5 with 4 cores of a@home it was hitting 85 degrees with a wraparound heatsink. With 64 bit running 4 cores of E@h its steady around 60 degrees. I might even have room to overclock :)
This may be a red herring, but with the latest 64bit OS, its working fine
@Jonathon I think you are completely correct. I could not find a HDMI to Micro HDMI cable in Canberra so I ordered one and it will be here next week I hope. I can then confirm that was what was wrong with my 16 RPI 4's as well.
OK just to wrap this up I have them working now. After installing Raspberry Pi 64 bit and installing BOINC I got Einstein work and have had one at this stage finish so all seems well.
Ian&Steve C. wrote:first,
)
OK I put the <options> tags in and it now does not error when loading the cc_config. I downloaded some new work and got 32 bit tasks for my 32 bit Boinc install but I still have the error.
If I have 32 bit boinc and get a 32 bit job I shouldn't get the error ??
@Keith Myers I think I might have to do a re install but with eight RPI's all headless it is a pain and I do not have a cable at the moment to hook up to a monitor.
Proud Founder of
Have a look at my WebCam<
You get the error probably
)
You get the error probably because you lack the 32-bit libraries for the 32-bit apps. You can add these, and it would stop the error, but your production would be a lot less than what it could be. I would recommend getting the 64-bit BOINC installed so you can get the 64-bit apps and make the most of the hardware.
_________________________________________________________________________
Looks like I already have the
)
Looks like I already have the 32 bit libraries.
sudo apt-get install libc6:armhf libstdc++6:armhf
Reading package lists... Done
Building dependency tree
Reading state information... Done
libstdc++6 is already the newest version (8.3.0-6+rpi1).
libc6 is already the newest version (2.28-10+rpt2+rpi1+deb10u2).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
I will have to install the newest version of Raspberry Pi for 64 bit and Install BOINC again etc. Just a pain when all the pi's are headless.
Proud Founder of
Have a look at my WebCam<
I wouldn't deal with the
)
I wouldn't deal with the hardware directly for the installs. I'd just gather up all eight SDHC cards and sit down in front of a machine with a keyboard and monitor and clone the 64 bit install of the distro along with the 64 bit BOINC installations with my favorite imaging/cloning software for Pi's.
I use Balena Etcher to write my Pi boot cards. Balene Etcher
I have installed Raspberry 64
)
I have installed Raspberry 64 bit which includes setting the hostname, the wifi and password, and opening port 22 for ssh on my 16 RPI 4's. I used the Raspberry Pi Imager to write the cards.
I do not have a hdmi to micro hdmi cable, I installed the current software in 2022, so could not see if any of them worked but they should as they all verified OK. Can't find a way to find the ip addresses of them as the hostname is not recognised. I thought that I would be able to see them on my router but nothing there.
Going to the shops tomorrow to get a cable and configure them all for static ip so I can use putty to communicate with them.
Proud Founder of
Have a look at my WebCam<
Why do you have the armhf
)
Why do you have the armhf architecture installed on the Pi's? Is it for some other project that only has 32 bit apps?
I think that because of it being installed, the scheduler is sending you the lowest common denominator app which is 32 bit and not supported by your silicon.
If you don't want to remove the armhf architecture, then I believe your only other option is to go with an app_info installation and call the proper 64 bit 1.61 app directly.
I've been through a similar
)
I've been through a similar odyssey the last few days with a brand new RPi5, which proved to be a misunderstanding on my part. I purchased it from PiHut along with a pre installed sd card , power supply and heatsink case.
Booted it up fine, installed boinc, attached to my usual projects. Asteroids@home worked fine, but Einstein at home gave me compute errors.
I was scratching my head as other people seem to have no issues.
I tried many of the points here, and eventually realised the SD card came preinstalled with the 32-bit Raspian, not 64 bit. DOH !
So I imaged a 64 bit SD, booted and einstein@home has been working fine , barring a couple of inconclusive results.
uname -m was correctly reporting the machine as aarch64, but it was when I ran the file command on any standard OS binary i.e. file /usr/bin/top
It was confirmed it was a 32-bit binary
My fault, I assumed that the sdcard would be the 64-bit version with any Pi4 or 5 ?
Another thing I notice is it runs a lot cooler. Running 32bit on the Pi5 with 4 cores of a@home it was hitting 85 degrees with a wraparound heatsink. With 64 bit running 4 cores of E@h its steady around 60 degrees. I might even have room to overclock :)
This may be a red herring, but with the latest 64bit OS, its working fine
@Jonathon I think you are
)
@Jonathon I think you are completely correct. I could not find a HDMI to Micro HDMI cable in Canberra so I ordered one and it will be here next week I hope. I can then confirm that was what was wrong with my 16 RPI 4's as well.
Proud Founder of
Have a look at my WebCam<
OK just to wrap this up I
)
OK just to wrap this up I have them working now. After installing Raspberry Pi 64 bit and installing BOINC I got Einstein work and have had one at this stage finish so all seems well.
I would like to thank all those that gave advise.
Proud Founder of
Have a look at my WebCam<