arm64 version of pfclient

jbuzar

New Member
Is there a native arm64 version of pfclient?
I run the armhf version on an arm64 hardware and it looks to be working but it fills the kernel log with such messages:

[ 985.935295] cp15barrier_handler: 10374 callbacks suppressed
[ 985.935322] "pfclient" (1262) uses deprecated CP15 Barrier instruction at 0x417cc
[ 985.935336] "pfclient" (1262) uses deprecated CP15 Barrier instruction at 0x417d4
[ 985.954546] "pfclient" (1256) uses deprecated CP15 Barrier instruction at 0x40fc8
[ 985.954582] "pfclient" (1256) uses deprecated CP15 Barrier instruction at 0x40fd0
[ 985.957682] "pfclient" (1256) uses deprecated CP15 Barrier instruction at 0x39458
[ 985.957716] "pfclient" (1256) uses deprecated CP15 Barrier instruction at 0x39460
 
1680139152909.png




1680139620129.png







.
 
Last edited:
Is there a native arm64 version of pfclient?
I run the armhf version on an arm64 hardware and it looks to be working but it fills the kernel log with such messages:

[ 985.935295] cp15barrier_handler: 10374 callbacks suppressed
[ 985.935322] "pfclient" (1262) uses deprecated CP15 Barrier instruction at 0x417cc
[ 985.935336] "pfclient" (1262) uses deprecated CP15 Barrier instruction at 0x417d4
[ 985.954546] "pfclient" (1256) uses deprecated CP15 Barrier instruction at 0x40fc8
[ 985.954582] "pfclient" (1256) uses deprecated CP15 Barrier instruction at 0x40fd0
[ 985.957682] "pfclient" (1256) uses deprecated CP15 Barrier instruction at 0x39458
[ 985.957716] "pfclient" (1256) uses deprecated CP15 Barrier instruction at 0x39460


There is nothing wrong with pfclient's 32-bit version runnig on 64-bit OS. It is done by adding architecture armhf.

As shown in my post above, my logs show nothing like your system shows.
Check architectures by following commands.
Code:
dpkg --print-architecture 

dpkg --print-foreign-architectures




1680156203080.png
 
armhf is added as architecture.
The differece to above is
$lsb_release -sc
jammy

And that I run it on a orangepi-zero2, not RPI4.
 
armhf is added as architecture.
The differece to above is
$lsb_release -sc
jammy

And that I run it on a orangepi-zero2, not RPI4.

orangepi-zero2 is OK
jammy, Oops!
Ubuntu based OS.
Ubuntu latest versions are pain in neck when it comes to ADS-B
Bullseye is smooth sailing.

Armbian_22.08.2_Orangepizero2_bullseye_current_5.15.69.img.xz (24-Sep-2022)



.
 
The armbian image has some other issues that make it not usable for me. Apart from Planefinder all other feeder tools (5 more I have running) work without problems on jammy. If it is really a jammy issue.
 
The armbian image has some other issues that make it not usable for me. Apart from Planefinder all other feeder tools (5 more I have running) work without problems on jammy. If it is really a jammy issue.


It is not only Planefinder feeder which has issues with Ubuntu.
Try to install performance graphs on Ubuntu / Jammy. Most users get stuck

Code:
sudo bash -c "$(wget -q -O - https://github.com/wiedehopf/graphs1090/raw/master/install.sh)"


1680183385877.png
 
I too run the armhf version on an arm64 host, but it's 2024 and it would be nice to have a native arm64 client.
After all, there is nothing wrong running an i386 client on an amd64 machine, right?

just ranting a bit, but I do enjoy planefinder a lot :-D
 
Back
Top