Your message dated Sun, 12 Jul 2026 12:12:37 +0200
with message-id <[email protected]>
and subject line Re: replacing base package with -unsigned removes module files
has caused the Debian Bug report #851695,
regarding linux: switch from linux-image-5.5.0-1-amd64-unsigned to
linux-image-5.5.0-1-amd64 made modules being lost
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
851695: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851695
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: linux
Version: 5.5.17-1
Severity: important
Hi.
I've just switched from the linux-image-5.5.0-1-amd64-unsigned to
linux-image-5.5.0-1-amd64
(which wasn't available as soon as the -unsigned version) in on go via apt.
The consequence was, that many modules were missing.
Looking at the apt/term.log:
Removing linux-image-5.5.0-1-amd64-unsigned
[then debconf asks whether I want to remove the running image]
Removing the running kernel
/etc/kernel/prerm.d/dkms:
dkms: removing: openafs 1.8.6pre1 (5.5.0-1-amd64) (x86_64)
[...]
depmod...
DKMS: uninstall completed.
[...]
Selecting previously unselected package linux-image-5.5.0-1-amd64.
Preparing to unpack .../linux-image-5.5.0-1-amd64_5.5.13-2_amd64.deb ...
Unpacking linux-image-5.5.0-1-amd64 (5.5.13-2) ...
Preparing to unpack .../linux-image-amd64_5.5.13-2_amd64.deb ...
Unpacking linux-image-amd64 (5.5.13-2) over (5.4.19-1) ...
[...]
Removing linux-image-5.4.0-4-amd64 (5.4.19-1) ...
/etc/kernel/prerm.d/dkms:
dkms: removing: openafs 1.8.6pre1 (5.4.0-4-amd64) (x86_64)
[...]
depmod...
DKMS: uninstall completed.
[...]
Setting up linux-image-5.5.0-1-amd64 (5.5.13-2) ...
I: /vmlinuz.old is now a symlink to boot/vmlinuz-5.2.0-3-amd64
I: /initrd.img.old is now a symlink to boot/initrd.img-5.2.0-3-amd64
I: /vmlinuz is now a symlink to boot/vmlinuz-5.5.0-1-amd64
I: /initrd.img is now a symlink to boot/initrd.img-5.5.0-1-amd64
/etc/kernel/postinst.d/dkms:
dkms: running auto installation service for kernel 5.5.0-1-amd64:.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.5.0-1-amd64
W: Possible missing firmware /lib/firmware/i915/icl_dmc_ver1_09.bin for module
i915
W: Possible missing firmware /lib/firmware/i915/tgl_dmc_ver2_04.bin for module
i915
W: Possible missing firmware /lib/firmware/i915/skl_huc_2.0.0.bin for module
i915
W: Possible missing firmware /lib/firmware/i915/bxt_huc_2.0.0.bin for module
i915
W: Possible missing firmware /lib/firmware/i915/kbl_huc_4.0.0.bin for module
i915
W: Possible missing firmware /lib/firmware/i915/glk_huc_4.0.0.bin for module
i915
W: Possible missing firmware /lib/firmware/i915/kbl_huc_4.0.0.bin for module
i915
W: Possible missing firmware /lib/firmware/i915/cml_huc_4.0.0.bin for module
i915
W: Possible missing firmware /lib/firmware/i915/cml_guc_33.0.0.bin for module
i915
W: Possible missing firmware /lib/firmware/i915/icl_huc_9.0.0.bin for module
i915
W: Possible missing firmware /lib/firmware/i915/ehl_huc_9.0.0.bin for module
i915
W: Possible missing firmware /lib/firmware/i915/ehl_guc_33.0.4.bin for module
i915
W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.0.3.bin for module
i915
W: Possible missing firmware /lib/firmware/i915/tgl_guc_35.2.0.bin for module
i915
/etc/kernel/postinst.d/zz-update-grub:
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.5.0-1-amd64
Found initrd image: /boot/initrd.img-5.5.0-1-amd64
Found linux image: /boot/vmlinuz-5.2.0-3-amd64
Found initrd image: /boot/initrd.img-5.2.0-3-amd64
Configured General Secure System
Found memtest86+ image: /root/boot/memtest86+.bin
Found memtest86+ multiboot image: /root/boot/memtest86+_multiboot.bin
done
[...]
Setting up xtables-addons-dkms (3.9-1) ...
Loading new xtables-addons-3.9 DKMS files...
Building for 5.5.0-1-amd64
Building initial module for 5.5.0-1-amd64
Done.
[...]
depmod...
DKMS: install completed.
[...]
So far, so good...
Purging configuration files for linux-image-5.5.0-1-amd64-unsigned (5.5.13-2)
...
I: /vmlinuz is now a symlink to boot/vmlinuz-5.2.0-3-amd64
I: /initrd.img is now a symlink to boot/initrd.img-5.2.0-3-amd64
rmdir: failed to remove '/lib/modules/5.5.0-1-amd64': Directory not empty
Purging configuration files for linux-image-5.4.0-4-amd64 (5.4.19-1) ...
I: /vmlinuz.old is now a symlink to boot/vmlinuz-5.5.0-1-amd64
I: /initrd.img.old is now a symlink to boot/initrd.img-5.5.0-1-amd64
Processing triggers for tex-common (6.14) ...
[here apt ends after some further triggers]
Looking at the postrm:
if [ "$1" = purge ]; then
for extra_file in modules.dep modules.isapnpmap modules.pcimap \
modules.usbmap modules.parportmap \
modules.generic_string modules.ieee1394map \
modules.ieee1394map modules.pnpbiosmap \
modules.alias modules.ccwmap modules.inputmap \
modules.symbols modules.ofmap \
modules.seriomap modules.\*.bin \
modules.softdep modules.devname; do
eval rm -f /lib/modules/$version/$extra_file
done
rmdir /lib/modules/$version || true
fi
It deletes all modules... which are however already belonging to the
signed version of the package.
Interestingly, and I don't quite understand this, not all modules were deleted.
Cause I spotted the failed rmdir right away and looked briefly at the dir
and modules were still there.
However, after reboot, e.g. iwlwifi was gone.
Cheers,
Chris.
--- End Message ---
--- Begin Message ---
Version: 6.19~rc4-1~exp1
We no longer build linux-image-*-unsigned packages, which effectively
fixed this bug.
Ben.
--
Ben Hutchings
If the facts do not conform to your theory, they must be disposed of.
signature.asc
Description: This is a digitally signed message part
--- End Message ---
