EEPROM still held back...

[Dynamic5912]

Is this still an issue?

I thought the "hold" was removed in a previous dietpi update?

I still get this when upgrading:

dietpi@dietpi:~$ sudo apt upgrade -y
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.
dietpi@dietpi:~$ 

[Joulinar]

Simply do

apt install --reinstall rpi-eeprom

[MichaIng]

The package is not on hold and there was no change regarding. APT holds it back by default because it requires a replacement of old with new RPi tools package, and APT never removed a package without confirmation.

A reinstall should allow you to confirm, but it might break some legacy hardware features, as the new tools are designed for the new kernel/firmware packages. Same with the new EEPROM bootloader. Hence I'd either ignore this (keep rpi-eeprom on old version) or migrate the RPi to new kernel/firmware as well: #6676

[Dynamic5912]

The package is not on hold and there was no change regarding. APT holds it back by default because it requires a replacement of old with new RPi tools package, and APT never removed a package without confirmation.

A reinstall should allow you to confirm, but it might break some legacy hardware features, as the new tools are designed for the new kernel/firmware packages. Same with the new EEPROM bootloader. Hence I'd either ignore this (keep rpi-eeprom on old version) or migrate the RPi to new kernel/firmware as well: #6676

Thanks. I'm running a Pi4 not a Pi5 - so does this make any difference?

[MichaIng]

No, the migration is needed to all RPi models.

[Dynamic5912]

No, the migration is needed to all RPi models.

OK thanks.

So what do I run to do the migration?

Any errors/warnings to look out for during the process?

[MichaIng]

So what do I run to do the migration?

The command in the first comment of that issue. No errors expected. When being asked, as you do not plan to run it on RPi 5, no additional kernel needs to be installed.

[Dynamic5912]

So what do I run to do the migration?

The command in the first comment of that issue. No errors expected. When being asked, as you do not plan to run it on RPi 5, no additional kernel needs to be installed.

bash <(curl -sSf 'https://raw.githubusercontent.com/MichaIng/DietPi/dev/.meta/dietpi-rpi-firmware-migration')

?

[Dynamic5912]

This doesn't work for me:

dietpi@dietpi:$ sudo bash <(curl -sSf 'https://raw.githubusercontent.com/MichaIng/DietPi/dev/.meta/dietpi-rpi-firmware-migration')
bash: /dev/fd/63: No such file or directory
dietpi@dietpi:$ curl: (23) Failed writing body

[MichaIng]

As of the context change sudo does, you cannot pass through a script like that. Either you need to switch to an interactive root shell, or do like that:

sudo bash -c "$(curl -sSf 'https://raw.githubusercontent.com/MichaIng/DietPi/dev/.meta/dietpi-rpi-firmware-migration')"

[Dynamic5912]

Thanks. All done - rebooted and everything seems fine.

It asked me whether I was installing on a Pi5 so I chose "NO" as I'm using a Pi4 and not planning (yet) on jumping to a Pi5.

If however I do plan to move to a Pi5 - is there a process to follow - I.e should I install a new DietPi image and start from scratch again?

I'm only really using my Pi4 for AdGuard Home, Unbound and some HomeAssistant tinkering.

[MichaIng]

Check out dietpi-config advanced options. There is "RPi kernel choice" which allows to install or uninstall optional kernel packages for other RPi models. It will always keep the one needed for the current RPi model you run it on, so once you boot the image on an RPi 5, you can also uninstall the RPi 4 kernel, to reduce disk usage and upgrade downloads/processing a little.

[Dynamic5912]

So in theory I can just take the SD Card out of my Pi4 and put it into a Pi5 (if/when purchased) and it will work with little to no additional configuration?

[MichaIng]

Yes, it will work even without installing the RPi5-only kernel. That that one has 16k page size vs 4k, which theoretically can mean a performance benefit. And regarding kernel build config etc, if at all, that one is optimised for the RPi 5, since it does not work on any other RPi model.

[Dynamic5912]

Great thanks.

Glad I don't have to reinstall or restore everything if I were to upgrade :)