Would then be released in the next DietPi version if too complex for a live patch?
how do you get this
change command ?
apt upgrade, I never had this command.
This happens only on RPi4 and if you run
dietpi-update which might trigger a package update for
I’m on RPI4 and tried both commands… and never had this message…
I did a
apt -y purge rpi-eeprom raspi-firmware and no more messages…
this is correct and part of the workaround to avoid this issue for now. However you can install previous version of rpi-eeprom and put it on hold.
Just installed the live patch however I’m still prompted to run
This information is collected once a night only or on reboot. However there could be other packages waiting as well.
apt update to verify availability if packages.
root@DietPi:~# apt update Hit:1 https://downloads.plex.tv/repo/deb public InRelease Hit:2 https://deb.debian.org/debian bookworm InRelease Hit:3 https://deb.debian.org/debian bookworm-updates InRelease Hit:4 https://deb.debian.org/debian-security bookworm-security InRelease Hit:5 https://deb.debian.org/debian bookworm-backports InRelease Hit:6 https://archive.raspberrypi.org/debian bookworm InRelease Hit:7 https://packagecloud.io/ookla/speedtest-cli/debian bookworm InRelease Reading package lists... Done Building dependency tree... Done Reading state information... Done 1 package can be upgraded. Run 'apt list --upgradable' to see it. root@DietPi:~# apt list --upgradable Listing... Done rpi-eeprom/stable 20.1-2 all [upgradable from: 20.1-1] N: There is 1 additional version. Please use the '-a' switch to see it
ok might be visual only. Running
apt upgrade should inform about the kept back package now.
root@DietPiProd:~# apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following packages have been kept back: rpi-eeprom 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. root@DietPiProd:~#
I confirm this
Would this be prompted on every reboot?
EDIT: Yes, I confirm the second too.
the current Live patch is just to avoid further issues for now. It is not the final solution. @MichaIng explained the way forward a little bit deeper on GitHub Image | Raspberry Pi 5 · Issue #6676 · MichaIng/DietPi · GitHub
The whole story around
rpi-eeprom is triggered by the new
raspi-firmware package. Gives us time to prepare the transition into new file system layout carefully.
Yes sure, wasn’t arguing about that my bad if so
I just wanted to give you updates!
As usual fantastic OS and even more fantastic support!
What does the
raspi-firmware package provide? I did the steps from github. They only tell us to install the previous
rpi-eeprom. Is the absence of the previous version of the other one not a problem?
No, we just stick to current kernel and bootloader version until we are able to safely migrate into the new file system structure that is required by the new RPi5 bootloader. Unfortunately, this impacts all RPi device.
Ty for your replies.
I have put the package on hold based on the initial Github’s instructions. Should i still apply the live patch or does it make no difference?
No, that makes no difference
BTW: RPI developer removed dependency between packages and workaround is not needed anymore. Package raspi-firmware is not configured yet · Issue #6747 · MichaIng/DietPi · GitHub