Rpi-eeprom update fails

Trying a regular apt upgrade and two packages fail to be upgraded or installed: raspi-firmware, rpi-eeprom


The following NEW packages will be installed:
The following packages will be upgraded:
1 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 7873 kB of archives.
After this operation, 22.3 MB of additional disk space will be used.
Get:1 https://archive.raspberrypi.org/debian bookworm/main arm64 raspi-firmwareall 1:1.20231024+ds-1+rpt1 [4550 kB]
Get:2 https://archive.raspberrypi.org/debian bookworm/main arm64 rpi-eeprom all20.1-2 [3322 kB]
debconf: delaying package configuration, since apt-utils is not installed
Fetched 7873 kB in 1s (5964 kB/s)
                                 Selecting previously unselected package raspi-firmware.
(Reading database ... 24642 files and directories currently installed.)
Preparing to unpack .../raspi-firmware_1%3a1.20231024+ds-1+rpt1_all.deb ...
Unpacking raspi-firmware (1:1.20231024+ds-1+rpt1) ...
Preparing to unpack .../rpi-eeprom_20.1-2_all.deb ...
Unpacking rpi-eeprom (20.1-2) over (20.1-1) ...
Setting up raspi-firmware (1:1.20231024+ds-1+rpt1) ...
Error: missing /boot/firmware, did you forget to mount it?
dpkg: error processing package raspi-firmware (--configure):
 installed raspi-firmware package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of rpi-eeprom:
 rpi-eeprom depends on raspi-firmware; however:
  Package raspi-firmware is not configured yet.

dpkg: error processing package rpi-eeprom (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
E: Sub-process /usr/bin/dpkg returned an error code (1)

Required Information

  • DietPi version

  • Distro version
    bookworm 0

  • Kernel version
    Linux 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023 aarch64 GNU/Linux

  • Architecture

  • SBC model
    RPi 4 Model B (aarch64)

1 Like

already known, see Package raspi-firmware is not configured yet · Issue #6747 · MichaIng/DietPi · GitHub


Is it safe to reboot after having this update fail?

yes, you can follow the advice on GitHub

Just got this but reading this only now :smiling_face_with_tear:
Run apt upgrade and failed with errors above then rebooted. Anything I should be worried off?
I’ve a dietpi-backup from a couple of hours ago, should I restore?

Follow the instructions on GitHub for now

Please select from the error-handle "Change command" and replace everything with true

Can you explain this please?
Would restoring a diepi-backup be the same?

Execute dietpi-update and when the error shows, chose change command and enter true.


there is no need to perform a restore.

1 Like

I just did this but wasn’t ask to chose change command.

Got it!

Did you run dietpi-update after executing the workaround from GitHub? I guess so.

No just the opposite as reading the workarount I tought you first chose change command when update fails and then you do the workaround :sweat_smile:

the workaround need to be applied on any case. Using change command option is just a way to continue with dietpi-update if hit by the error.

I’ve run apt upgrade as prompted by DietPi, got error and rebooted.
I tried running dietpi-update to get error again and do the workaround but I didn’t get any error.
Btw I’ve restored tonight’s backup :+1:

that was not needed at all

I know but now I’m just like before applying the update and can wait for a live patch.

DietPi update is not the issue. It’s the apt package update from rpi-eeprom (20.1-1) to (20.1-2). This requires a new file system layout structure due to the raspi-firmware package.

Will a live patch be released? I remember seeing something on the GitHub’s issue.

Depends on complexity. Usually Live patches are simple fixes. Not sure how complex this one will be.