Michael J. Kidd

Hi @brianboru82 -- Can you attach the `/var/log/allsky.log` file file to this issue. Note: Attach can be done by dragging the file into the compose window for your next comment,...

This line ``` /usr/bin/ld: lib/armv8/libASICamera2.a: error adding symbols: file format not recognized ``` Indicates it's failing to link the binary libraries from ZWO ( libASICamera2.a ). It's possible this file...

> @linuxkidd I thought on my Pi 4 it used "armv7". What does yours use? If it's also armv7, could that be the problem? Very good point! Mine too is...

That is super odd.. maybe the chip is different rev due to chip shortages? My test pi is also the BCM2711. On the problem Pi, can you provide: ``` grep...

scratch that request.. I found a [full cpuinfo](https://forums.raspberrypi.com/viewtopic.php?t=245384) from a Pi with this chip. It still reports the CPU is v7l... so, I'm not sure why the make `platform` variable...

Interesting... I found the issue that spawned the PR ( Issue #509 ) .. but it was Sept 24th. So, It's easy to workaround... but we need a proper fix...

Oohhh... @Jonk2 .. can you provide: ``` uname -a ``` There seems to be some discussion that this only occurs with the 64bit kernel, and it actually IS a reporting...

There we go... this is the 64bit raspbian, not 32bit. Thus, aarch64 is 'correct' for platform, but including the armv8 libs is not since the CPU arch is not v8....

Your 'live' allsky Pi is running 32bit version of Raspbian. This is actually the recommended version from RPi maintainers of Raspberry Pi -- actually, they don't even link the 64...

From the [official blog announcing the 8gb Pi availability](https://www.raspberrypi.com/news/8gb-raspberry-pi-4-on-sale-now-at-75/): > Our default operating system image uses a 32-bit LPAE kernel and a 32-bit userland. This allows multiple processes to share...