I understand that HWE kernels arrive few months after non-LTS release comes out. Is there a chance to make it instantly available for LTS users with HWE-edge branch?
Not really, no. Thereās no such thing as an optional kernel. Itās either in the archive (and thus fully supported) or itās not. The bar to get a kernel into the archive sits fairly high, so we canāt and donāt want to do that for short-lived kernels. All DKMS packages from the archive need to compile, all autopkgtests need to pass, the AppArmor patchset needs to be updated and functional, ā¦ and probably other things that Iām not aware of.
What youāre looking for is a rolling kernel which is not feasible at the moment.
But nothing prevents you from using mainline builds [1] or packages from any of our build [2], bootstrap [3] or unstable [3] PPAs. Just be aware that none of this is supported nor fully tested nor patched for security or other issues on an on-going basis.
[1] Ubuntu Mainline Build Status
[2] https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa
[3] https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/bootstrap
[4] https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/unstable
1 Like
Iām afraid not. For the same reasons mentioned in my previous comment.
1 Like
So, if a regular user experiences an issue because his hardware is very new, what would be the solution thatād be supported by Canonical (all unsupported solutions are out of the window)?
You would have to wait for the next interim release which would have the latest upstream kernel, and if you are on an LTS you would then need to wait a bit longer for it to roll as an HWE.
Hello Kernel Team, please enable āSamsung Galaxy Book driverā in the next kernel.
Thank you
Hi @sandra0815. A notebook device like the Samsung Galaxy Book requires several kernel device drivers in order for it to work properly with Linux. The Ubuntu kernel inherits most of those drivers from the upstream Linux kernel and usually the availability of those drivers depend on contributions from the manufacturer of those components to the open source community. We from the Kernel Team commit ourselves to enable the support for as many devices as we can, therefore as soon as a device driver is available in the upstream Linux kernel it will usually be enabled in the following Ubuntu releases. If you are using the latest LTS release, when enabled in a later release, drivers will become available via the HWE kernel.
1 Like
Did the AppArmor stuff land on 6.15?
1 Like
unfortunately it did not Snapd STILL requires out-of-tree apparmor patches for strict confinement - #60 by A333 - snapd - snapcraft.io
there seem to be something holding it back still, it is unclear to me what is holding it back atm
Hi, (previously posted here which came up as the closest match search result.)
Today I ran my ālots of security patches, update nowā cycle. Apparently, the lowlatency kernel disappears.
apt search linux-lowlatency stops at 6.8.0-60 but -generic has a -62 and apt wants to replace my kernel.
Is there a walk through of how to ensure - before I reboot and pick up the generic kernel - Iām not going to lose the lowlatency tuning?
(I installed 22.04 LTS with the lowlatency kernel and updated to 24.04 LTS with the lowlatency kernel - Iāve not been really aware of any concrete developments that indicated it was being removed.)
Thanks,
ā Peter
Post-script: I remembered that the boot menu would have the previous kernel still, so I stopped panicking. However, I did find the system booted automatically to -generic rather than -lowlatency and I had to select -lowlatency by hand from the boot menu, so the question still stands.
Reading up in the post you linked, the Low Latency kernel is eventually going to be deprecated as the -generic kernel acts as a low latency kernel with preempt=full and threadirqs added to the boot parameters, so thereās no real reason to carry the -lowlatency flavor of the kernel anymore.
I remember a note that said that the latest kernel available would be used for the new release. is it still true? So 25.10 will have the 17.x kernel?
Thanks - the generic already has threadirqs enabled, so Iād just add preempt=full?
OK, thanks ā the addition settings, of course, are needed regardless of which kernel is installed. Itās good to see them set out clearly, though.