New Kernel issue

Support & Help Requests
21

In order to remove installed packages that are no longer needed, including their configuration files, I just did:
sudo apt-get autoremove --purge

See what I get

Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade.
2 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up linux-image-unsigned-6.12.3-061203-generic (6.12.3-061203.202412060638) ...
Setting up linux-headers-6.12.3-061203-generic (6.12.3-061203.202412060638) ...
/etc/kernel/header_postinst.d/dkms:

  • dkms: running auto installation service for kernel 6.12.3-061203-generic
    Sign command: /usr/bin/kmodsign
    Signing key: /var/lib/shim-signed/mok/MOK.priv
    Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der

Building module:
Cleaning build area...
'make' -j8 KLIB=/lib/modules/6.12.3-061203-generic KLIB_BUILD=/lib/modules/6.12.3-061203-generic/build....(bad exit status: 2)
ERROR (dkms apport): kernel package linux-headers-6.12.3-061203-generic is not supported
Error! Bad return status for module build on kernel: 6.12.3-061203-generic (x86_64)
Consult /var/lib/dkms/backport-iwlwifi/0~89.12325-git36c5be1a/build/make.log for more information.
dkms autoinstall on 6.12.3-061203-generic/x86_64 failed for backport-iwlwifi(10)
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.

  • dkms: autoinstall for kernel 6.12.3-061203-generic
    ...fail!
    run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
    dpkg: error processing package linux-headers-6.12.3-061203-generic (--configure):
    installed linux-headers-6.12.3-061203-generic package post-installation script subprocess returned error exit status 11
    Processing triggers for linux-image-unsigned-6.12.3-061203-generic (6.12.3-061203.202412060638) ...
    /etc/kernel/postinst.d/dkms:
  • dkms: running auto installation service for kernel 6.12.3-061203-generic
    Sign command: /usr/bin/kmodsign
    Signing key: /var/lib/shim-signed/mok/MOK.priv
    Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der

Building module:
Cleaning build area...
'make' -j8 KLIB=/lib/modules/6.12.3-061203-generic KLIB_BUILD=/lib/modules/6.12.3-061203-generic/build....(bad exit status: 2)
ERROR (dkms apport): kernel package linux-headers-6.12.3-061203-generic is not supported
Error! Bad return status for module build on kernel: 6.12.3-061203-generic (x86_64)
Consult /var/lib/dkms/backport-iwlwifi/0~89.12325-git36c5be1a/build/make.log for more information.
dkms autoinstall on 6.12.3-061203-generic/x86_64 failed for backport-iwlwifi(10)
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.

  • dkms: autoinstall for kernel 6.12.3-061203-generic
    ...fail!
    run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
    dpkg: error processing package linux-image-unsigned-6.12.3-061203-generic (--configure):
    installed linux-image-unsigned-6.12.3-061203-generic package post-installation script subprocess returned error exit status 11
    Errors were encountered while processing:
    linux-headers-6.12.3-061203-generic
    linux-image-unsigned-6.12.3-061203-generic
    E: Sub-process /usr/bin/dpkg returned an error code (1)

So I'll get rid of this 6.12.3.... and see if it solves anything

W

1 Like
22

Seems like a good place to start. I would also, again, recommend getting rid of that problematic backport. It's not being actively supported: GitHub - intel/backport-iwlwifi

1 Like
23

Mind you, I have a feeling that other DKMS will fail to build, too.

1 Like
24

I also purged all packages with the "rc" status

So I am now with:

dpkg --list | grep linux-image
ii linux-image-6.11.0-13-generic 6.11.0-13.14 amd64 Signed kernel image generic
ii linux-image-6.11.0-9-generic 6.11.0-9.9 amd64 Signed kernel image generic

And updating grub

sudo update-grub
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.11.0-13-generic
Found initrd image: /boot/initrd.img-6.11.0-13-generic
Found linux image: /boot/vmlinuz-6.11.0-9-generic
Found initrd image: /boot/initrd.img-6.11.0-9-generic
Found memtest86+ 64bit EFI image: /memtest86+x64.efi
Warning: os-prober will not be executed to detect other bootable partitions.
Systems on them will not be added to the GRUB boot configuration.
Check GRUB_DISABLE_OS_PROBER documentation entry.
Adding boot menu entry for UEFI Firmware Settings ...
done

Lets see...

After re-booting I faced a initramfs. Blocked and exited under 6.11.0-13. 6.11.0-9 asked me to input the encrypted password and I am now back.

W

2 Likes
25

To confirm:

  • 6.11.0-13 you get cryptsetup: Wait for encrypted source device UUID ... and cannot proceed.
  • with 6.11.0-9, you are able to boot, and can decrypt the system when required.

So; something has gone wrong with the cryptsetup with the 6.11.0-13 image? Does your /etc/fstab/ have "crypt" entries with that UUID?

1 Like
26

/etc/fstab: static file system information.

Use 'blkid' to print the universally unique identifier for a
device; this may be used with UUID= as a more robust way to name devices
that works even if disks are added and removed. See fstab(5).


/ was on /dev/ubuntu-vg/ubuntu-lv during curtin installation
/dev/disk/by-id/dm-uuid-LVM-P0lyypdgN7DNAXgO8TX28wPvOz6VzQz4kx5SWVHizF2E9GwoxIZ2WLM95VeFviSM / ext4 defaults 0 1
/boot was on /dev/nvme1n1p2 during curtin installation
/dev/disk/by-uuid/64930a0d-33e0-489a-a4f1-6323c9787c27 /boot ext4 defaults 0 1
/boot/efi was on /dev/nvme1n1p1 during curtin installation
/dev/disk/by-uuid/6E38-3B35 /boot/efi vfat defaults 0 1
/swap.img none swap sw 0 0

27

Presumably, there is some output from (i.e. cryptsetup is trying a valid UUID):

sudo blkid | grep 3f73916b
1 Like
28

sudo blkid | grep 3f73916b

/dev/nvme0n1p3: UUID="3f73916b-21cf-4143-9e87-c0fb327aa55b" TYPE="crypto_LUKS" PARTUUID="50a96f1c-ae3f-4d33-9a7f-51f374f06e4c"

W

1 Like
29

Hi Stephen

At boot I have to keep the arrow down to get to the choice of kernel. Even by choosing 6.11.0-9 it then leads to initramfs where I can unlock with my password. It then leads me to splash where I can input my user pw - a bit cumbersome but at least I can work (and put on suspend between working sessions)

If I choose 6.11.0-13 it waits for premount… and stalls

I tried all the options offered by safe mode (e.g. grub upgrade, packages update, etc)

I really don;t know how to solve that one. Except another full re-install.

I case you have an idea where I should dig...

Thanks

W

30

I'd say something has gone wrong with your etc/crypttab file or similar. I'm not game to offer any suggestions as I wouldn't want you to lose anything important (like the keys for the encryption) based on my bad advice - I haven't used any boot encryption!

1 Like
31

etc/crypttab reads:

dm_crypt-0 UUID=3f73916b-21cf-4143-9e87-c0fb327aa55b none luks

So. Nothing special there

W

32

I am 'playing around' to help find a solution

If I do
sudo lsblk -o NAME,FSTYPE

Why do I get all these loops ?

sudo lsblk -o NAME,FSTYPE
NAME FSTYPE
loop0 squashfs
loop1 squashfs
loop2 squashfs
loop3 squashfs
loop4 squashfs
loop5 squashfs
loop6 squashfs
loop7 squashfs
loop8
loop9
loop10
loop11
loop12
loop13
loop14
loop15
loop16
loop17
loop18
loop19
loop20
loop21
loop22
loop23
loop24
loop25
loop26
loop27
loop28
loop29
loop30
loop31
loop32
loop33
loop34
loop35
loop36
loop37
loop38
nvme0n1
├─nvme0n1p1 vfat
├─nvme0n1p2 ext4
└─nvme0n1p3 crypto_LUKS
└─dm_crypt-0 LVM2_member
└─ubuntu--vg-ubuntu--lv ext4
nvme1n1

1 Like
33

They are likely snaps:

user@home:~$ sudo lsblk -o NAME,FSTYPE,MOUNTPOINTS
NAME        FSTYPE   MOUNTPOINTS
loop0       squashfs /snap/bare/5
loop1       squashfs /snap/core20/2434
loop2       squashfs /snap/core22/1663
...
loop22      squashfs /snap/snapd-desktop-integration/253
nvme0n1              
├─nvme0n1p1 vfat     /boot/efi
├─nvme0n1p2          
...
2 Likes