Ubuntu Version:
22.04 LTS
Problem Description:
A good practice is not to install Ubuntu kernel updates the moment they are released. However, did you ever install several updates and then restarted on the last one. For example, you have installed 5.15.0-179 through 5.15.0-186 then restarted on 186. Or you directly restart after every install
Ubuntu 22.04 LTS started off with Linux kernel 5.15 but by now Ubuntu 22.04 LTS should be using Linux kernel 6.8.
When did you install Ubuntu 22.04 LTS. Why do you not want to keep the operating system up-to-date.
Actually, I do not agree with this statement:
I always install updates and accept kernel updates at the same time. I have no concerns or worries about re-starting on the new installed Linux kernel. If upgrading using Software Updater I sometimes accept the offer to reboot. Sometimes I choose the “not now” option. I am usually doing work and do not want to be interrupted.
In the past there have been times when the new kernel was, in my opinion, “broken.” I am very familiar with Recovery Mode. I use it to boot into the older, but working, kernels and I keep doing that until an update/upgrade brings in an update to the broken kernel.
In fact if I ever get into a broken kernel situation I stop using Software Updater and update using the terminal. Then I avoid the situation of having the first two kernels in the list of kernels as broken kernels.
Regards
Thank you for your prompt reply. The practice was done because it is a remote online server that we cannot afford to experience downtime with. As you have said in the past some broken kernels caused issues… The concern is when restarting after several kernel installs. It is usually better to restart after each kernel install/update and not after a compilation of installs/updates.
I use Livepatch, which means that kernels are updated “live” without needing a reboot. So, that would be “immediate”.
I reboot daily anyway, and if it fails, it’s easy enough to fall back to the previous kernel version. By default, Ubuntu always keeps the previous version. You can also manually mark a version to be kept, so that it won’t be auto-removed.
No, never. It seems a strange thing to do.
I agree with @graymech. Given that Ubuntu’s kernel updates nearly always include fixes to important security vulnerabilities, you should update promptly. Where did you come across this advice?
I am on Ubuntu 22.04.5 LTS and my system works well with kernel 5.15.0.171.
When it was updated to kernel 6.8, I experienced display problems (elongated Ubuntu logos on startup for example) and general slow page loading. Therefore I continue to boot into kernel 5.15.
I am completely happy with my setup, but am I missing out by not addressing my 6.8 problem?
I cannot use Livepatch as I removed snapd from my system, only a) to see if there were any improvements, and b) to see if I could do it!
I don’t know if this has any bearing on the kernel issue.
On restart the latest kernel will boot unless you config grub to do otherwise
Sure, grub is set to boot into 5.15.
Certain 6.8 kernels had regression problems (I was one of the many affected people).
The regressions were fixed in 6.11. Are you able to test kernel 6.11 or later?
Thank you for your reply, I’ll check that out asap.
sudo apt install linux-generic-hwe-22.04 results in the latest kernel version 6.8.0-136. This appears to be the latest version for Ubuntu 22.04.
That seems to be true whether or not you have Pro enabled.
The only thing that I can suggest is to experiment with GRUB settings. When you boot the machine with kernel 6.8, get to the GRUB prompt. If it’s not shown automatically, press Esc when you see the computer’s logo; it should show GRUB.
At that point, press the letter e, which brings you to the GRUB editor to make temporary changes. Find the line that begins with linux vmlinuz. At the end of that line, add a space and then one of the following strings:
intel_iommu=igfx_offi915.enable_psr=0acpi_backlight=nativeYou’ll need to try each one, one at a time. You can even try two of them at once (both on the same line). I hope that one of the tries solves the problem!
If one of them solves the problem, you’ll need to make it permanent (let me know if you don’t know how).
If none of them solves the problem, unfortunately you’ll have to stick with kernel 5.15.
In addition to all of the above, it would be useful to boot from a Live USB with 26.04 to see if kernel 7 still causes the problem. If kernel 7 still causes the problem, you’ll need to raise a bug report in the hope that it will be solved before you are forced to upgrade (May 2032 if using Pro, May 2027 if not).
Thank you for the detailed response and despite the effort you have gone to, and as all works well for me as is, I don’t wish to experiment to that extent at the moment.
Part of my original post was:
I stuck with 22.04 after trying 24.04 in a VM, but couldn’t see much differenc e for my setup, but perhaps an upgrade may be in order. I do have Pro enabled.
I’ll keep your post and if we ever get a rainy day again (!), I’ll experiment and post the result.