rpi-eeprom package "have been kept back" #7222
Comments
|
Hmm, what does it say when you do this? apt install rpi-eepromProbably it depends on the |
Edit: |
|
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 |
No nothing special, terminal use only. |
|
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. |
|
I ll wait mostly cause of i am always nervous when i upgrade the bootloader. |
|
+1 here Identical hardware, software and logs. Apps: (only) AdGuard Home, Unbound, MPD, ALSA Execute Update went through cleanly, successful restart. |
|
+1 too Execute Update went through cleanly, successful restart. |
|
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. |
|
Booting without any device or SD card connected, does it have any LED activity? |
|
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%. |
So.. not related to eeprom then? |
|
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. |
|
I had no problems with the last three or four automated eeprom updates. |
|
Usually it should be possible to update the package |
|
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. |
|
Is there a particular reason one wants to upgrade this package? It pulls in parts of the new firmware stack, which might cause issues with the old kernel. So I would just ignore it, let it on hold. The EEPROM bootloader is not updated often anyway, and usually to support new boards or revisions only. Solution will be the migration to the new kernel stack, which I plan to offer more officially with next DietPi release: #6676 |
|
Oh nobody likes those nagging little notifications, especially when they go on for a year or more :) apt install rpi-eeprom worked this time so thanks folks for the reminder to try again. I'm sure I had tried it in the past to no avail. Perhaps the latest 9.9.0 made a difference. |
DietPi release or code has nothing to do with it |
|
That some may be annoyed by such warning is indeed true. As said, upcoming update will offer the firmware migration more prominently via DietPi update. It has been applied/tested by so many in the meantime, should be considered very safe to do. In the same turn, images with the new kernel/firmware will be available from our download page as well. |
|
Upgrading to the latest rpi-eeprom also got me some dpkg-warnings |
Same. But it still upgraded OK |
|
Content of package is out of our control, it's unrelated to our code https://forums.raspberrypi.com/viewtopic.php?t=382649 |
No one said it was. We were merely advising of the error message in case others experience the same... |
Required Information
G_DIETPI_VERSION_CORE=9
G_DIETPI_VERSION_SUB=7
G_DIETPI_VERSION_RC=1
G_GITBRANCH='master'
G_GITOWNER='MichaIng'
bookworm 0
Linux dietpi 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023 aarch64 GNU/LinuxRPi 4 Model B (aarch64)
Version:
DietPi v9.7.1 ####
When i try to do an
apt upgradethe rpi-eeprom package "have been kept back".Usually it gets upgraded that why i am opening this issue.
Logs:
The text was updated successfully, but these errors were encountered: