Nvidia will no longer be supporting older Nvidia GPU's on and there after Kernels 6.11, so I decided to apt-hold Kernel 6.8 and use it till it dies. I would normally do a web search for the answer, but am having a hard time forming the words in the engine to get a direct answer. I am dual booting and will be changing one of the systems shortly and was wondering if the hold on the kernel would interfere or break when the new install creates a new grub boot menu on the efi partition?
Announcement
Collapse
No announcement yet.
Will a apt-hold on Kernel 6.8.0-79-lowlatency, interfere with update-grub?
Collapse
X
-
AI Overview
Using apt-mark hold on your current kernel packages prevents those specific kernel packages from being upgraded or removed during subsequent apt upgrade or apt dist-upgradeoperations.
Specifically, this means:- No new kernel versions will be installed for the held packages:
If a newer version of the exact kernel package you held becomes available, apt will not install it. - Security updates for the held kernel will not be applied:
If the held kernel version receives security patches, these patches are typically delivered as updates to that specific kernel package. Holding the package prevents these security updates from being installed. - Other system updates may still occur:
Holding the kernel packages does not prevent other non-kernel packages from being updated. - Potential for new kernel installations via metapackages:
If you are using a kernel metapackage (e.g., linux-image-generic, linux-generic-hwe), and you only hold the specific real kernel package (e.g., linux-image-4.15.0-1007-aws), the metapackage itself might still be updated. This update could then pull in a new, unheld kernel package, effectively installing a newer kernel despite your hold on the older one. To fully prevent kernel upgrades, you typically need to hold both the specific real kernel packages and the relevant metapackages.
Consequences of holding your kernel:- System vulnerability:
You will not receive security updates for your kernel, potentially leaving your system vulnerable to known exploits. - Lack of new features and hardware support:
Newer kernels often include support for new hardware and performance improvements, which you will miss out on. - Potential for system instability (less common):
While less frequent, some software or hardware might eventually require features or bug fixes present in newer kernel versions, leading to potential compatibility issues.
To hold your kernel, you would typically use commands like:
Code
sudo apt-mark hold linux-image-$(uname -r) linux-headers-$(uname -r)And if using a metapackage, you might also need to hold it:
Code
sudo apt-mark hold linux-image-generic linux-headers-genericTo unhold the packages and allow updates:
Code
sudo apt-mark unhold linux-image-$(uname -r) linux-headers-$(uname -r)sudo apt-mark unhold linux-image-generic linux-headers-generic zz0.p4imsngrjp7zzWindows no longer obstruct my view.
Using Kubuntu Linux since March 23, 2007.
"It is a capital mistake to theorize before one has data." - Sherlock Holmes
- Top
- Bottom
- No new kernel versions will be installed for the held packages:
-
No, holding a kernel package won't affect updating grub. that should still keep three kernel versions around.
Actually, instead of holding a specific kernel package, you might consider simply removing the HWE kernel upgrade track altogether, and just keep to the stock (GA) kernel track with the 6.8. This keeps you with all the kernel security updates patches for the full life of the LTS, and will stay at 6.8.0.
Now, I am not sure if I recommend the lowlatency unless you are doing something with music production or something and have tested it against the normal kernel.
I have heard that recent kernels seem to have mostly negated the need to use a lowlatency version, though of course ymmv.
So:
Install the GA kernel metapackage:
Code:sudo apt install --install-recommendsy linux-image-generic
If necessary, Reboot, and select the 6.8 kernel in grub and make sure things are working fine there (as they seem to be)
Next, remove the HWE kernels and related packages:
Code:sudo apt purge linux-generic-hwe-24.04 linux-headers-generic-hwe-24.04 linux-modules-6.1* linux-headers-6.1* sudo apt autoremove
Code:sudo apt install linux-image-lowlatency
Pinning (aka holding) a specific kernel package can still be a useful tool if there is an issue with a specific build down the road and you want to keep one around. But this seems less likely for you here.
Last edited by claydoh; Yesterday, 07:03 PM.
- Top
- Bottom
Comment
-
Removing the HWE kernel upgrade track will be my go to solution. Now I will run MXLinux alongside Kubuntu 24.04 until I have to remove this card and switch to AMD. Note: Ubuntu Studio KDE comes with a low latency kernel, I use this for desktop publishing for a company and have been afraid to change it. It handles graphics, fonts, and video better than all the distros I have tried. Thank you both for your help.Last edited by TinyTim; Yesterday, 08:30 PM.
- Top
- Bottom
Comment
Users Viewing This Topic
Collapse
There are 0 users viewing this topic.
Comment