Kernel updated to 6.11.x

[Beerislife]

A bit of a surprise this morning. I woke up to an update to the 6.8.x series,rebooted and went happily on my way
and auto-removed the old kernel.

Then about ten minutes or so ago I got an update to the 6.11.x series! I'm not complaining, just surprised to have
two kernel updates within hours of each other!

Nothing to report so far good or bad.

[Beerislife]

My Mint Cinnamon machine also had it available but I had to choose to install it from
Mint's kernel manager!

[claydoh]

Normal Ubuntu HWE stuff for LTS.
In 6 months we should see Ubuntu 25.10's kernel

Mint doesn't install the HWE kernel track (the meta-package) by default.

[marco07]

My fully updated KDE neon 6.2 (User Edition) was also upgraded to the KDE Plasma version 6.3.0 with a new 6.11.0-17-generic Kernel today. However at the boot-up I get a blank screen with no further response. I can get back to the system by reverting back to Kernel 6.8.0-53-generic, the latest prior one. Any comment or guidance on this issue? Thanks!
My system is a Lenovo Thinkpad T540P.

[oshunluvr]

My fully updated KDE neon 6.2 (User Edition) was also upgraded to the KDE Plasma version 6.3.0 with a new 6.11.0-17-generic Kernel today. However at the boot-up I get a blank screen with no further response. I can get back to the system by reverting back to Kernel 6.8.0-53-generic, the latest prior one. Any comment or guidance on this issue? Thanks!
My system is a Lenovo Thinkpad T540P.

Not having any trouble here, but I did initially because I had an out-of-date PPA enabled. I suggest you try and fix this using the console and command line.

First, I would boot 6.11 and let it fail and sit for a minute or so. Then reboot to the GRUB menu and boot to 6.8 and take note of the time you hit enter. Once you're booted to 6.8 and running normally, open Konsole and run "sudo dmesg" and see what was reported just before you rebooted to 6.8. If anything seems relevant, post it here.

Then, when you're done with that, check to be sure all the necessary packages were installed. I've run into this issue once or twice in the past that one package did't get installed.

To check what packages are installed relating to the new 6.11 kernel in Neon;

dpkg -l | grep 6.11.0-17

Then compare the lists and be sure all the packages

linux-generic-hwe-24.04 
linux-headers-6.11.0-17-generic
linux-headers-generic-hwe-24.04
linux-hwe-6.11-headers-6.11.0-17
linux-hwe-6.11-tools-6.11.0-17
linux-image-6.11.0-17-generic
linux-image-generic-hwe-24.04
linux-modules-6.11.0-17-generic
linux-modules-extra-6.11.0-17-generic
linux-tools-6.11.0-17-generic

[claydoh]

The main culprits with kernel upgrades I find and see are falied DKMS rebuilds of kernel modules for various drivers -- Nvidia being the most common one that uses tis system. Third party wifi drivers found on Git, and any driver package installed that has 'dkms' in its name.

Sometimes there is an incompatibility between the code and the kernel. Often dkms simpply barfs, but successfully completes the compile on its next go (reinstalling the package, for example)

This is something that can happen on any distro, really, and at least with KDE neon, you just need to look for other Ubuntu users facing the same issue, and hopefully an easy fix.

I think Discover and Gnome Software may mask or hide these dkms failures. Updating with apt will always show them.

[marco07]

OK, I followed your instruction. After failing to boot with kernel 6.11, while booting 6.8 it took 2.25 minutes to get to the desk top. The "sudo dmesg" command came up with a very looong list. Going through the list I found the following unusual messages:

0.199884] pnp: PnP ACPI init
[ 0.200310] pnp 00:00: disabling [mem 0x000c0000-0x000c3fff] because it overlaps 0000:00:02.0 BAR 6 [mem 0x000c0000-0x000dffff]
[ 0.200315] pnp 00:00: disabling [mem 0x000c4000-0x000c7fff] because it overlaps 0000:00:02.0 BAR 6 [mem 0x000c0000-0x000dffff]
[ 0.200317] pnp 00:00: disabling [mem 0x000c8000-0x000cbfff] because it overlaps 0000:00:02.0 BAR 6 [mem 0x000c0000-0x000dffff]
[ 0.200319] pnp 00:00: disabling [mem 0x000cc000-0x000cffff] because it overlaps 0000:00:02.0 BAR 6 [mem 0x000c0000-0x000dffff]
[ 0.200320] pnp 00:00: disabling [mem 0x000d0000-0x000d3fff] because it overlaps 0000:00:02.0 BAR 6 [mem 0x000c0000-0x000dffff]
[ 0.200322] pnp 00:00: disabling [mem 0x000d4000-0x000d7fff] because it overlaps 0000:00:02.0 BAR 6 [mem 0x000c0000-0x000dffff]
[ 0.200324] pnp 00:00: disabling [mem 0x000d8000-0x000dbfff] because it overlaps 0000:00:02.0 BAR 6 [mem 0x000c0000-0x000dffff]
[ 0.200326] pnp 00:00: disabling [mem 0x000dc000-0x000dffff] because it overlaps 0000:00:02.0 BAR 6 [mem 0x000c0000-0x000dffff]
[ 0.200359] system 00:00: [mem 0x00000000-0x0009ffff] could not be reserved
[ 0.
.......
.........
[ 0.353602] platform eisa.0: Probing EISA bus 0
[ 0.353604] platform eisa.0: EISA: Cannot allocate resource for mainboard
[ 0.353606] platform eisa.0: Cannot allocate resource for EISA slot 1
[ 0.353608] platform eisa.0: Cannot allocate resource for EISA slot 2
[ 0.353609] platform eisa.0: Cannot allocate resource for EISA slot 3
[ 0.353610] platform eisa.0: Cannot allocate resource for EISA slot 4
[ 0.353612] platform eisa.0: Cannot allocate resource for EISA slot 5
[ 0.353613] platform eisa.0: Cannot allocate resource for EISA slot 6
[ 0.353614] platform eisa.0: Cannot allocate resource for EISA slot 7
[ 0.353615] platform eisa.0: Cannot allocate resource for EISA slot 8
[ 0.353616] platform eisa.0: EISA: Detected 0 cards
[ 0.353621] intel_pstate: Intel P-state driver initializing
[ 0.3
...
...
...
[ 35.213164] Bluetooth: MGMT ver 1.22
[ 35.309345] NET: Registered PF_ALG protocol family
[ 40.730285] NET: Registered PF_QIPCRTR protocol family
[ 40.925585] loop29: detected capacity change from 0 to 8
[ 48.095208] ACPI: \: failed to evaluate _DSM bf0212f2-788f-c64d-a5b3-1f738e285ade (0x1001)
[ 48.095219] ACPI: \: failed to evaluate _DSM bf0212f2-788f-c64d-a5b3-1f738e285ade (0x1001)
[ 48.095221] ACPI: \: failed to evaluate _DSM bf0212f2-788f-c64d-a5b3-1f738e285ade (0x1001)
[ 48.095222] ACPI: \: failed to evaluate _DSM bf0212f2-788f-c64d-a5b3-1f738e285ade (0x1001)
[ 48.095224] ACPI: \: failed to evaluate _DSM bf0212f2-788f-c64d-a5b3-1f738e285ade (0x1001)
[ 48.095225] ACPI: \: failed to evaluate _DSM bf0212f2-788f-c64d-a5b3-1f738e285ade (0x1001)
[ 48.095227] ACPI: \: failed to evaluate _DSM bf0212f2-788f-c64d-a5b3-1f738e285ade (0x1001)
[ 48.095973] iwlwifi 0000:04:00.0: Registered PHC clock: iwlwifi-PTP, with index: 1
[ 48.921894] kauditd_printk_skb: 173 callbacks suppressed
[ 48.921897] audit: type=1400 audit(1739632427.068:185): apparmor="DENIED" operation="capable" class="cap" profile="/snap/snapd/23545/usr/lib/snapd/snap-confine" pid=1749 comm="snap-confine" capability=12 capname="net_admin"
[ 4
......
......
[ 122.455701] warning: `kdeconnectd' uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl80211

marco@t540p:~$ dpkg -l | grep 6.11.0-17
iU linux-generic-hwe-24.04 6.11.0-17.17~24.04.2+2 amd64 Complete Generic Linux kernel and headers
iF linux-headers-6.11.0-17-generic 6.11.0-17.17~24.04.2 amd64 Linux kernel headers for version 6.11.0 on 64 bit x86 SMP
iU linux-headers-generic-hwe-24.04 6.11.0-17.17~24.04.2+2 amd64 Generic Linux kernel headers
ii linux-hwe-6.11-headers-6.11.0-17 6.11.0-17.17~24.04.2 all Header files related to Linux kernel version 6.11.0
ii linux-hwe-6.11-tools-6.11.0-17 6.11.0-17.17~24.04.2 amd64 Linux kernel version specific tools for version 6.11.0-17
iF linux-image-6.11.0-17-generic 6.11.0-17.17~24.04.2 amd64 Signed kernel image generic
ii linux-image-generic-hwe-24.04 6.11.0-17.17~24.04.2+2 amd64 Generic Linux kernel image
ii linux-modules-6.11.0-17-generic 6.11.0-17.17~24.04.2 amd64 Linux kernel extra modules for version 6.11.0 on 64 bit x86 SMP
ii linux-modules-extra-6.11.0-17-generic 6.11.0-17.17~24.04.2 amd64 Linux kernel extra modules for version 6.11.0 on 64 bit x86 SMP
ii linux-tools-6.11.0-17-generic 6.11.0-17.17~24.04.2 amd64 Linux kernel version specific tools for version 6.11.0-17
marco@t540p:~$

[oshunluvr]

CODE tags work better then CONSOLE, IMO. I changed the dpkg output so you could see the difference

[marco07]

Sorry! I meant to box the konsol listings, but it seems it did not work out well.

[marco07]

Thank you!
So, I keep on using 6.8 until perhaps the future updates will take care of whatever the issue might be. My fingers are crossed.

[oshunluvr]

6.11 did not install correctly/fully as I suspected. When dpks says "iF" that means "failed to configure". "iU" means "unpacked" which I believe is like it unpacked the downlooad but didn't try to install it fro some reason. So these are your problem packages:

iU linux-generic-hwe-24.04
iF linux-headers-6.11.0-17-generic
iU linux-headers-generic-hwe-24.04
iF linux-image-6.11.0-17-generic

I think I would start by attempting to re-install these, starting with the kernel image itself. Then look at the error output and see if it offers any clues:

sudo apt install linux-image-6.11.0-17-generic

If you get a response like "already installed" or "...is latest version" then try:

sudo apt reinstall linux-image-6.11.0-17-generic

Paste the output here and maybe we can find answers...

[marco07]

Thanks!
Here is the outcome:

marco@t540p:~$ sudo apt install linux-image-6.11.0-17-generic
[sudo] password for marco:[
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
linux-image-6.11.0-17-generic is already the newest version (6.11.0-17.17~24.04.2).
linux-image-6.11.0-17-generic set to manually installed.
Starting pkgProblemResolver with broken count: 0
Starting 2 pkgProblemResolver with broken count: 0
Done
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
4 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-headers-6.11.0-17-generic (6.11.0-17.17~24.04.2) ...
/etc/kernel/header_postinst.d/dkms:
* dkms: running auto installation service for kernel 6.11.0-17-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' -j4 KLIB=/lib/modules/6.11.0-17-generic KLIB_BUILD=/lib/modules/6.11.0-17-generic/build...........................(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.11.0-17-generic (x86_64)
Consult /var/lib/dkms/backport-iwlwifi/11510/build/make.log for more information.
dkms autoinstall on 6.11.0-17-generic/x86_64 succeeded for nvidia-srv
dkms autoinstall on 6.11.0-17-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.11.0-17-generic
...fail!
run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
dpkg: error processing package linux-headers-6.11.0-17-generic (--configure):
installed linux-headers-6.11.0-17-generic package post-installation script subprocess returned error exit status 11
Setting up linux-image-6.11.0-17-generic (6.11.0-17.17~24.04.2) ...
dpkg: dependency problems prevent configuration of linux-headers-generic-hwe-24.04:
linux-headers-generic-hwe-24.04 depends on linux-headers-6.11.0-17-generic; however:
Package linux-headers-6.11.0-17-generic is not configured yet.

dpkg: error processing package linux-headers-generic-hwe-24.04 (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of linux-generic-hwe-24.04:
linux-generic-hwe-24.04 depends on linux-headers-generic-hwe-24.04 (= 6.11.0-17.17~24.04.2+2); however:
Package linux-headers-generic-hwe-24.04 is not configured yet.

dpkg: error processing package linux-generic-hwe-24.04 (--configure):
dependency problems - leaving unconfigured
Processing triggers for linux-image-6.11.0-17-generic (6.11.0-17.17~24.04.2) ...
/etc/kernel/postinst.d/dkms:
* dkms: running auto installation service for kernel 6.11.0-17-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' -j4 KLIB=/lib/modules/6.11.0-17-generic KLIB_BUILD=/lib/modules/6.11.0-17-generic/build..........................(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.11.0-17-generic (x86_64)
Consult /var/lib/dkms/backport-iwlwifi/11510/build/make.log for more information.
dkms autoinstall on 6.11.0-17-generic/x86_64 succeeded for nvidia-srv
dkms autoinstall on 6.11.0-17-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.11.0-17-generic
...fail!
run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
dpkg: error processing package linux-image-6.11.0-17-generic (--configure):
installed linux-image-6.11.0-17-generic package post-installation script subprocess returned error exit status 11
Errors were encountered while processing:
linux-headers-6.11.0-17-generic
linux-headers-generic-hwe-24.04
linux-generic-hwe-24.04
linux-image-6.11.0-17-generic
E: Sub-process /usr/bin/dpkg returned an error code (1)
marco@t540p:~$

[claydoh]

dkms autoinstall on 6.11.0-17-generic/x86_64 failed for backport-iwlwifi(10)

So, is this wifi driver necessary? backport-iwlwifi-dkms seems to fail for the few that are using it.
I think that the upgraded kernel doesn't need it/has this already built-in.

backport-iwlwifi-dkms IS a package released in November 2023, fwiw.

This is the current reported bug
https://bugs.launchpad.net/ubuntu/+s...s/+bug/2097945


Uninstall the driver package, which will allow dkms to not fail (or not even be needed) and allow the new kernel to be installed.

[marco07]

Yes! that was the culprit! I purged "backport-iwlwifi-dkms" and had to re-update the Grub. All is OK now.
Thanks to you and oushunluvr as well!

[oshunluvr]

Yes, that was my stumbling block also! I didn't think to mention it specifically because what are the odds we had the same PPA enabled? Apparently very high, lol.