Can't use apt upgrade anymore due dpkg: error processing package linux-image-6.1.0-10-amd64 (--configure)

[maria789]

I encounter an issue with Debian 12 and my PC. CPU info: AMD Ryzen 5 5600G with Radeon Graphics.
I cannot do apt upgrade, it fails due to - see log below.
I assume that the lines starting with W: Possible missing firmware I can ignore, these are just warnings.
I found some solutions online. I tried to do autoremove or purge and it failed with the same errors. These solutions don't look like correct.
Currently I can't install or update anything.
Could anyone give me a hint or help me?

Code: Select all

Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
2 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] Setting up linux-image-6.1.0-10-amd64 (6.1.37-1) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-6.1.0-10-amd64
W: Possible missing firmware /lib/firmware/amdgpu/ip_discovery.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega10_cap.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_cap.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navi12_cap.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/psp_13_0_11_ta.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/psp_13_0_11_toc.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/psp_13_0_10_ta.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/psp_13_0_10_sos.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/aldebaran_cap.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_imu.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_4_rlc.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_4_mec.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_4_me.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_4_pfp.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_rlc.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_mec.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_me.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_pfp.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_0_toc.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/sdma_6_0_3.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_mes1.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_mes.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_4_mes1.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_4_mes_2.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_4_mes.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_mes1.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_mes_2.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_mes.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_2_mes_2.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_1_mes_2.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_0_mes_2.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/smu_13_0_10.bin for module amdgpu
I: The initramfs will attempt to resume from /dev/nvme0n1p1
I: (UUID=1a4587c5-9b95-4db3-97a9-7af12e2e3c2a)
I: Set the RESUME variable to override this.
raspi-firmware: missing /boot/firmware, did you forget to mount it?
run-parts: /etc/initramfs/post-update.d//z50-raspi-firmware exited with return code 1
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
dpkg: error processing package linux-image-6.1.0-10-amd64 (--configure):
 installed linux-image-6.1.0-10-amd64 package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of linux-image-amd64:
 linux-image-amd64 depends on linux-image-6.1.0-10-amd64 (= 6.1.37-1); however:
  Package linux-image-6.1.0-10-amd64 is not configured yet.

dpkg: error processing package linux-image-amd64 (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 linux-image-6.1.0-10-amd64
 linux-image-amd64

[4D696B65]

You are not alone
viewtopic.php?t=155192
viewtopic.php?t=154857

[maria789]

Thanks

[Dude Guyman]

I have the exact same error(s) with a Ryzen 5 5600, Radeon RX 6600. Could not tell you how to fix it. I can't even figure out what "dependency problems" it has.

[Random_Troll]

Could not tell you how to fix it

The links posted by 4D696B65 explain exactly how to fix this problem.

[Dude Guyman]

Could not tell you how to fix it

The links posted by 4D696B65 explain exactly how to fix this problem.

Links to links to more links to descriptions of removing some random thing and when I do that errors out too. No thanks! I'll just move along elsewhere. I installed Debian 12 three days ago and all I have done since then is try to fix one thing after another...starting on step one with the friggin' installer!

[pwzhangzz]

The problem is not with Debian 12 itself but was caused because the QC people allowed the kernel to be upgraded to 6.1.0-10, which caused a raspi-firmware-related "malware" (can't think of a better term) to be re-introduced into the system. So much for the "stable" designation.

This bug has been reported during the "bkworm stage of unstable" (whatever that means). Very annoying but has been dragging on for quite some time. There is no excuse for this bug to continue and be re-introduced during a Debian "Stable" upgrade. Conspiracists may suggest that there is a mole in the debian development team, but I don't think so.

As per @Random_Troll and others, we need to remove three files:

1. /etc/kernel/postinst.d/z50-raspi-firmware
2. /etc/kernel/postrm.d/z50-raspi-firmware
3. /etc/initramfs/post-update.d/z50-raspi-firmware

Then do a sudo apt purge raspi-firmware

viewtopic.php?p=776929#p776929

[sunrat]

raspi-firmware-related "malware" (can't think of a better term)

"malware" The word is "bug".

[pwzhangzz]

raspi-firmware-related "malware" (can't think of a better term)

"malware" The word is "bug".

The word "bug" implies this is "unintentional". For something so prevalent--and which has been reported so long ago and for so many times--to be "penetrated" into the "Stable" distro --the "trademark" of Debian--, I can't but think otherwise.

[TheRaven]

As per @Random_Troll and others, we need to remove three files:

1. /etc/kernel/postinst.d/z50-raspi-firmware
2. /etc/kernel/postrm.d/z50-raspi-firmware
3. /etc/initramfs/post-update.d/z50-raspi-firmware

Then do a sudo apt purge raspi-firmware

viewtopic.php?p=776929#p776929

Absolute life saver; I was starting to get mad especially when I saw raspi-firmware. Kind of started using language.
Anyway, all is good now.

[rufus_deb]

1. /etc/kernel/postinst.d/z50-raspi-firmware
2. /etc/kernel/postrm.d/z50-raspi-firmware
3. /etc/initramfs/post-update.d/z50-raspi-firmware

Then do a sudo apt purge raspi-firmware

viewtopic.php?p=776929#p776929

Thanks! The above steps worked after a failed NVIDIA driver installation too (which invokes update-initramfs at the end). Once the above steps were done and rebooted, NVIDIA driver which was otherwise installed correctly worked fine.

Lest anybody relates it to AMD, my system is Intel Alder Lake 12700KF and a RTX 3070. So it is independent of any specific hardware.

I would request Debian admins involved in approving these type of changes to be more vigilant on matters that affect stability. We can always have an unstable version for experiments, but OS installed from official ISO should not end up having these basic issues.

[Abinash]

I'm new to Linux, having installed Debian only today. While trying to install flatpak, I encountered the following error;


sudo apt install flatpak gnome-software-plugin-flatpak
[sudo] password for abinash:
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
flatpak is already the newest version (1.14.4-1).
gnome-software-plugin-flatpak is already the newest version (43.4-1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
2 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up linux-image-6.1.0-10-amd64 (6.1.37-1) ...
/etc/kernel/postinst.d/dkms:
dkms: running auto installation service for kernel 6.1.0-10-amd64.
dkms: autoinstall for kernel: 6.1.0-10-amd64.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-6.1.0-10-amd64
raspi-firmware: missing /boot/firmware, did you forget to mount it?
run-parts: /etc/initramfs/post-update.d//z50-raspi-firmware exited with return code 1
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
dpkg: error processing package linux-image-6.1.0-10-amd64 (--configure):
installed linux-image-6.1.0-10-amd64 package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of linux-image-amd64:
linux-image-amd64 depends on linux-image-6.1.0-10-amd64 (= 6.1.37-1); however:
Package linux-image-6.1.0-10-amd64 is not configured yet.

dpkg: error processing package linux-image-amd64 (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
linux-image-6.1.0-10-amd64
linux-image-amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)

Kindly guide how can I overcome this issue as I am not well versed with command line

[Aki]

I'm new to Linux, having installed Debian only today. While trying to install flatpak, I encountered the following error;
[..]
Kindly guide how can I overcome this issue as I am not well versed with command line

It is in a previous post: see viewtopic.php?p=777027#p777027

[sunrat]

I'm new to Linux, having installed Debian only today. While trying to install flatpak, I encountered the following error;


sudo apt install flatpak gnome-software-plugin-flatpak
[sudo] password for abinash:
...
linux-image-amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)

Kindly guide how can I overcome this issue as I am not well versed with command line

Also in the announcements section of every subforum - viewtopic.php?t=155245

Please use code tags for terminal text output.

[alex819964]

The problem is not with Debian 12 itself but was caused because the QC people allowed the kernel to be upgraded to 6.1.0-10, which caused a raspi-firmware-related "malware" (can't think of a better term) to be re-introduced into the system. So much for the "stable" designation.

This bug has been reported during the "bkworm stage of unstable" (whatever that means). Very annoying but has been dragging on for quite some time. There is no excuse for this bug to continue and be re-introduced during a Debian "Stable" upgrade. Conspiracists may suggest that there is a mole in the debian development team, but I don't think so.

As per @Random_Troll and others, we need to remove three files:

1. /etc/kernel/postinst.d/z50-raspi-firmware
2. /etc/kernel/postrm.d/z50-raspi-firmware
3. /etc/initramfs/post-update.d/z50-raspi-firmware

Then do a sudo apt purge raspi-firmware

viewtopic.php?p=776929#p776929

This finally got my upgrade going, thanks a lot!