hmm, I guessed it might be some 32-bit ARMv6 v.s. 64-bit ARMv8.I've got two pi zero w 2, and one is showing the error and the other isn't. The one with the error is PI OS 64, and the other is the 64 lite with libcamera-apps installed. That's the only difference.
My Pi1B has the lite version of rpicam-apps installed and rpicam-still is used to take a picture about once per day and although the full-upgrade yesterday evening went fine (also new kernel 6.6.47 based), it doesn't work. So I rolled-back the whole action to a btrfs snapshot from just before the upgrade. It is remote outside, don't want to waste time now on it. I know Pi1 is a problem child because of not being normal Debian armhf 32-bit ARMv7, but replacing it simply 'costs a Pi' and then still dependent on rpicam software. A simple USB camera is also an option.
The Pi3B+ that I also did full-upgrade also failed w.r.t. camera, but it hasn't rpicam-apps installed. This failure is related to recent change in libcamera library names. The program MediaMTX was looking for the (orignal) name with only zero, and only 0.3 available. But fixed/hacked by symlinks and now by upgrade to 1.9.0 of MediaMTX.
I might have a check in other distros, first Debian Testing. That is to get some feet on the ground w.r.t. stable/testing/unstable/rolling/experimental, whatever label. Not the distro itself, but RPi additions and/or patches, needed to get the (special) HW to work.
Statistics: Posted by redvli — Sat Sep 07, 2024 5:37 am