rpi-eeprom package "have been kept back"

[bede112]

Required Information

• DietPi version
  G_DIETPI_VERSION_CORE=9
  G_DIETPI_VERSION_SUB=7
  G_DIETPI_VERSION_RC=1
  G_GITBRANCH='master'
  G_GITOWNER='MichaIng'
• Distro version
  bookworm 0
• Kernel version
  Linux dietpi 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023 aarch64 GNU/Linux
• SBC model
  RPi 4 Model B (aarch64)
  Version:
  DietPi v9.7.1 ####

When i try to do an apt upgrade the rpi-eeprom package "have been kept back".
Usually it gets upgraded that why i am opening this issue.

Logs:

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.

apt list rpi-eeprom -a
Listing... Done
rpi-eeprom/stable 25.1-1 all [upgradable from: 24.0-1]
rpi-eeprom/now 24.0-1 all [installed,upgradable to: 25.1-1]

[MichaIng]

Hmm, what does it say when you do this?

apt install rpi-eeprom

Probably it depends on the raspi-utils package, which replaces the libraspberrypi-bin package, which is still used on the older kernel. Looks like another reason we need to push the kernel/firmware migration out to everyone.

[bede112]

@MichaIng

Hmm, what does it say when you do this?

apt install rpi-eeprom

apt install rpi-eeprom
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
  kms++-utils libdrm-common libdrm2 libfmt9 libkms++0 net-tools raspi-utils
  raspi-utils-core raspi-utils-dt raspi-utils-eeprom raspi-utils-otp raspinfo
Recommended packages:
  pastebinit flashrom
The following packages will be REMOVED:
  libraspberrypi-bin
The following NEW packages will be installed:
  kms++-utils libdrm-common libdrm2 libfmt9 libkms++0 net-tools raspi-utils
  raspi-utils-core raspi-utils-dt raspi-utils-eeprom raspi-utils-otp raspinfo
The following packages will be upgraded:
  rpi-eeprom
1 upgraded, 12 newly installed, 1 to remove and 0 not upgraded.
Need to get 38.1 MB of archives.
After this operation, 9862 kB of additional disk space will be used.
Do you want to continue? [Y/n]

Edit:
I aborted the command cause i don't know if it will break my setup.

[MichaIng]

Okay as I expected, dependencies have been updated. Do you use any camera device on that RPi, or special video software?

I guess the dependency could be lowered to raspi-utils-eeprom only. They split raspi-utils into dedicated packages, which is great, but not all dependants have been updated for this change. I'll have a look into the tools, and in case report it at the RPi repo.

[bede112]

Do you use any camera device on that RPi, or special video software?

No nothing special, terminal use only.
Only special that comes to my mind is the I2C software for the FAN i use to cool the RPi off.

[MichaIng]

Okay, so in this case it is safe to confirm the upgrade. However, it currently nastily pulls a bunch of additional packages you do not really need. The old EEPROM bootloader will work just fine as well. So no real recommendation here, especially if disk space is no topic for you and you do not use a cheap SD card. In case of cheap or small SD card, wait with the upgrade until I sorted it with RPi devs.

[bede112]

I ll wait mostly cause of i am always nervous when i upgrade the bootloader.
But if anytime you need me to upgrade for testing purposes, just let me know.

[master-kw]

+1 here

Identical hardware, software and logs.

Apps: (only) AdGuard Home, Unbound, MPD, ALSA

Execute apt install rpi-eeprom

Update went through cleanly, successful restart.

[peaceman1920]

+1 too
same hardware, SW: Dashboard and Portainer (2 or 3 container)

Execute
apt install rpi-eeprom

Update went through cleanly, successful restart.

[OpenLogicEFI]

Had the issue here too. I assumed it was being rolled out. On a Rpi4, I was in headless ssh and after doing a apt update/upgrade the eeprom got stuck on 78%. after about 30 min of 78% I lost connection. I waited another 20 min before trying to log back in but my device remained offline. Checking it physically I noticed it was very warm, much warmer than normal. I unplugged it and plugged it back in and after some diagnosis I can confirm it appears to be bricked. It will no longer power on or get warm. Unfortunately I don't have much info since it's dead. I'll try to pull some logs tomorrow off the SD card but I think it's just dead.

Very random on a pi only a few months old. I still have pi3's running 24/7. Given the time-frame it doesn't seems like hardware failure but instead an update error.

[Joulinar]

Booting without any device or SD card connected, does it have any LED activity?

[peaceman1920]

I've had the phenomenon of unnormal heat too, but appearently only because of my unintentionally started update additionally inside Webmin. There it hung and one core was busy 100%.
After reboot everything OK.
(my rpi is running as headless server in my homenet, accessed via ssh)

[Dynamic5912]

Same shit happened to me right now after 38 days uptime, didn't even upgrade eeprom, cpu 69C and stupid throttling.

apt list --upgradable

rpi-eeprom/stable 26.0-1 all [upgradable from: 24.0-1]

So.. not related to eeprom then?

[krollinsgh]

Do we have a solution or timeline for this yet? The eeprom update on my Pi 4 hasn't worked for ages. Backup of my flash card saved me from one crash during an update. Most times everything updates however, but never the eeprom.

[master-kw]

I had no problems with the last three or four automated eeprom updates.

[Joulinar]

Usually it should be possible to update the package apt install rpi-eeprom without any issue.

[krollinsgh]

Thanks for that. I forget what borked my card a few months ago. Could have been an auto update, could have been trying to do the eeprom individually.

I'm not totally fluid with this stuff, but if there are any specific instructions or things to look out for, with the individual eeprom update, I can try that again now under this new DietPi version. Just ran a new backup, so now would be the time to give it another shot.

Auto most definitely still didn't work as I just tried it twice.