Switching kernels is a common troubleshooting step in Linux and can often resolve hardware compatibility issues. If the new kernel resolves your issues without introducing new problems, you can continue using it. If you’ve tried multiple kernels and are still experiencing issues, the problem might lie elsewhere, such as with system settings, driver configurations, or hardware compatibility.
List the current running version of the kernel with uname -a or uname -r.
List current installed kernels,
apt list --installed | grep linux-image
sudo apt search linux-image
Usually, the most suitable choice among the listed kernel versions would be one of the generic kernels. These are standard, generic kernels that are typically well-suited for a wide range of desktop and server hardware, including workstations.
There are also other kernels, e.g., low latency kernels are optimized for scenarios where low latency is crucial, such as audio recording or live performance. Unless you have specific needs for low-latency operations, these might not offer significant benefits for general use.
The kernels with specific cloud provider names (e.g., aws, azure, gcp) are optimized for running on virtual machines in those respective cloud environments and are not suitable for physical workstation.
I installed the latest generic version,
sudo apt install linux-image-6.2.0-36-generic
If you have GRUB_TIMEOUT=0 set in your GRUB configuration, it means the GRUB menu is not displayed during boot, and your system boots directly into the default kernel. To access the GRUB menu and select the new kernel you’ve installed, you’ll need to modify this setting.
sudo vim /etc/default/grub
GRUB_TIMEOUT=5
You might also need to change GRUB_TIMEOUT_STYLE=hidden to GRUB_TIMEOUT_STYLE=menu. This change
will ensure that the GRUB menu is displayed rather than hidden during boot.
After saving the changes, update GRUB to apply them:
sudo update-grub
Now, when the system boots you will see the GRUB menu and you will be able to choose an advanced option and the kernel that you want to boot with.
To monitor the system’s behavior you can use your system as you normally would, paying attention to any changes in performance, stability, or the occurrence of the issues you’ve been experiencing.