Hm. I currently have two Piz online. Each has a host name of pi41 and pi32. I am not seeing their names in the list of my computers. Also on both of these Piz when I do and update to E@H I get a 24 hour countdown followed by another one at the end of 1st 24 hour countdown. Am I missing some "special" software to make them run with E@H. I seem to recall many years ago that an E@H user provided such a package. Is it still necessary?
EDIT 11/26/19 I am also seeing in the contact log:
[CRITICAL] [HOST#12795278] platform 'aarch64-unknown-linux-gnu' not found ?????
Am I missing some "special" software to make them run with E@H. I seem to recall many years ago that an E@H user provided such a package. Is it still necessary?
EDIT 11/26/19 I am also seeing in the contact log:
[CRITICAL] [HOST#12795278] platform 'aarch64-unknown-linux-gnu' not found ?????
Am I missing some "special" software to make them run with E@H. I seem to recall many years ago that an E@H user provided such a package. Is it still necessary?
EDIT 11/26/19 I am also seeing in the contact log:
[CRITICAL] [HOST#12795278] platform 'aarch64-unknown-linux-gnu' not found ?????
I have a hdmi kvm switch to switch between towers. I have recently plugged in 2 Pis and they don't seem to play well with my kvm switch. Anyone??????
I came across an article about Piz not responding to hdmi interfaces. The advice given was to add the following line of code to the /boot/config.txt file. I tried adding this line to this file and now the Pi that would not "write" to the hdmi connected monitor on my kvm setup is just fine, i.e. seems to solve my problem with the kvm switch. It might also be worth adding this line to your config.txt file regardless.
Maybe use impatient mode to speed things up. The exhaustive mode usually doesn‘t make much difference in run time of most apps.
I've discoverd quite a big diffrence between a wisdom generated in exhaustive and in patient mode.
Let's say for example on my rock64, which is basically a PI3 with 4GB RAM (4x A53-[at]-1.2Ghz).
My patient wisdom useses about 600MB of RAM and has a runtime of roughly 1d 10h.
In comparison, my exhaustiv wisdom uses around 800MB and needs 1d 4h to finsh.
I'm using both wisdom's depending on the System Memory. I could explain why this happens but that would be a long post.
PorkyPies wrote:
Are you going to regenerate the BRP4 wisdom file for the Pi4?
At first I'm more focused on getting the FGRP out for the PI4. But jepp, when that is finished, I will make a new version of the BRP but only 64bit. And I propably won't include a wisdom directly in the binary as last time, I will provide it as a extra file.
I have a hdmi kvm switch to
)
I have a hdmi kvm switch to switch between towers. I have recently plugged in 2 Pis and they don't seem to play well with my kvm switch. Anyone??????
robl wrote:Bryant Stewart
)
I didn't get a chance to work on it this weekend. I will let you know how your guide goes when I get through it.
Bryant Stewart wrote:robl
)
Ok. Appreciate it.
Hm. I currently have two Pi
)
Hm. I currently have two Piz online. Each has a host name of pi41 and pi32. I am not seeing their names in the list of my computers. Also on both of these Piz when I do and update to E@H I get a 24 hour countdown followed by another one at the end of 1st 24 hour countdown. Am I missing some "special" software to make them run with E@H. I seem to recall many years ago that an E@H user provided such a package. Is it still necessary?
EDIT 11/26/19 I am also seeing in the contact log:
robl wrote:Am I missing some
)
The project doesn’t have any aarch64 apps. You’ll need to download and use the app from n30dg-arm. See https://einsteinathome.org/content/high-speed-linux-brp-app-odroid-c2I was hoping we could get Bernd to add it as a project supplied app but they are all too busy with the other searches.MarksRpiCluster
PorkyPies wrote:robl wrote:Am
)
PorkyPies thanks for:
1. a trip down memory lane (
the link you posted
)
and
2. for getting them up and running again.
One of these Piz is a Pi 4 running Ubuntu 19.10
robl wrote:I have a hdmi kvm
)
I came across an article about Piz not responding to hdmi interfaces. The advice given was to add the following line of code to the /boot/config.txt file. I tried adding this line to this file and now the Pi that would not "write" to the hdmi connected monitor on my kvm setup is just fine, i.e. seems to solve my problem with the kvm switch. It might also be worth adding this line to your config.txt file regardless.
I've got my PI4 up and
)
I've got my PI4 up and running, using the Ubuntu 64bit Server Image.
https://einsteinathome.org/host/12796061/
Results are looking very impressive. Avg. run time for a FGRP is around 12.36 h. This should lead to a RAC of close to 5000.
There is still some room for optimisation. I was using a Wisdom that was created on a Rockchip RK3399.
At the moment my PI generates a new wisdom-file for the FGRP, but this will take some time... Probably around a Month.
N30dG-ARM wrote:At the moment
)
Maybe use impatient mode to speed things up. The exhaustive mode usually doesn‘t make much difference in run time of most apps.
Are you going to regenerate the BRP4 wisdom file for the Pi4?
MarksRpiCluster
PorkyPies wrote:Maybe use
)
I've discoverd quite a big diffrence between a wisdom generated in exhaustive and in patient mode.
Let's say for example on my rock64, which is basically a PI3 with 4GB RAM (4x A53-[at]-1.2Ghz).
My patient wisdom useses about 600MB of RAM and has a runtime of roughly 1d 10h.
In comparison, my exhaustiv wisdom uses around 800MB and needs 1d 4h to finsh.
I'm using both wisdom's depending on the System Memory. I could explain why this happens but that would be a long post.
At first I'm more focused on getting the FGRP out for the PI4. But jepp, when that is finished, I will make a new version of the BRP but only 64bit. And I propably won't include a wisdom directly in the binary as last time, I will provide it as a extra file.