Floyd2000

Hello Igor, thanks for your reply and the advice about the armbian-bsp* package. It worked! 👍 I tried it out and finally managed to update all previously withheld packages and get rid of the error messages, but it was still kind of bumpy... I had to take these steps: 1. dpkg -r the armbian-bsp-cli-rpi4b-current because apt remove would not work and produce errors 2. apt --fix-broken install 3. dpkg -i --force-all /var/cache/apt/archives/armbian-bsp-cli-rpi4b-current_25.2.3_arm64.deb as apt install would not work without errors and dpkg would not work without forcing it. The error message was something about armbian-bsp* trying to overwrite a file that had been created by raspi-firmware (or something like that. Unfortunately, I did not copy the exact message) Now, everything seems up to date, including the RPi firmware (which had been quite old in the pre-built image, now it's up to date). BTW: in my previous post I wrote that OMV is running on an RPi4B, in fact that was a typo, it is an RPI3B+ really, so the firmware is not in an EEPROM, but only in a couple files in the /boot/firmware folder. Thanks again. I'm curious if it will stay stable or if future updates will cause trouble again at some point. 🙂 🙃

Hi all, I installed the pre-built OMV Image for my RPi4 the other week (Image from section "Dedicated applications images with Armbian Linux v6.12 Build Date: Mar 6, 2025") and everything is working fine so far. However, today I noticed that the unattended-upgrades would not upgrade libraspberrypi0 and libraspberrypi-run. Upon attempting a manual upgrade I got the message that libc6 should be at least 2.38 while the installed version is 2.36. Before I trigger a dependency avalanche and possibly break things, I was just going to ask whether these 2 upgrades could simply be ignored or if there is a safe way to solve this. Thanks for any feedback.