Audio dropouts, frame-time spikes, and sluggish input usually mean Ubuntu’s stock kernel is tuned for broad stability instead of desktop latency. The Launchpad PPA lets you install Liquorix kernel on Ubuntu 26.04, 24.04, and 22.04 with package-managed updates for gaming, multimedia work, and other interactive desktop loads.
Liquorix is a desktop-focused kernel build with aggressive preemption, Project-C scheduler tuning, a 1000 Hz timer, and desktop-oriented I/O defaults. The packages install from any shell, but the kernel itself is for x86_64 systems, does not ship with Secure Boot signing, and makes more sense on workstations than on production servers. For upstream details, see the Liquorix website and the Liquorix Launchpad PPA.
Install Liquorix Kernel on Ubuntu
The Liquorix packages install with the same package names on all supported Ubuntu LTS releases, so the workflow stays simple once the PPA is in place.
These steps work on Ubuntu 26.04, 24.04, and 22.04. Liquorix publishes
amd64packages only, and Secure Boot must be disabled unless you plan to sign the Liquorix kernel and related modules yourself.
Update Ubuntu and Confirm x86_64 Support for Liquorix
Refresh package metadata first so the PPA and kernel dependencies resolve cleanly.
sudo apt update
sudo apt upgrade
These commands use
sudobecause they change system packages. If your account does not have sudo access yet, follow the guide on how to add a new user to sudoers on Ubuntu.
Liquorix supports 64-bit x86 hardware only, so check the architecture before you add the PPA.
uname -m
x86_64
Continue only when the output is x86_64. ARM and other architectures are outside the Liquorix Ubuntu package scope.
Add the Liquorix PPA on Ubuntu
Most Ubuntu desktop installs already include add-apt-repository, but minimal or server images may need the software-properties-common package first.
sudo apt install software-properties-common
sudo add-apt-repository ppa:damentz/liquorix -y
The -y flag accepts the repository prompt automatically. Ubuntu imports the Launchpad signing key and refreshes package metadata as part of the same step.
Run one explicit refresh after that step so you can see APT pull metadata from the Liquorix source, then confirm the metapackage candidate.
sudo apt update
Hit:26 https://ppa.launchpadcontent.net/damentz/liquorix/ubuntu resolute InRelease
Ubuntu 24.04 shows the same line with noble, and Ubuntu 22.04 shows jammy. Once that source appears in the refresh output, check the metapackage candidate before installing the kernel.
apt-cache policy linux-image-liquorix-amd64
linux-image-liquorix-amd64:
Installed: (none)
Candidate: 6.19-4ubuntu1~resolute
Version table:
6.19-4ubuntu1~resolute 500
500 https://ppa.launchpadcontent.net/damentz/liquorix/ubuntu resolute/main amd64 Packages
Ubuntu 24.04 shows the same package with a ~noble suffix, and Ubuntu 22.04 shows ~jammy. The important part is that Candidate is populated and the source points at the Liquorix Launchpad PPA.
Install Liquorix Kernel Packages on Ubuntu
Install the Liquorix image and header metapackages together so future updates keep the running kernel and DKMS rebuilds aligned.
sudo apt install linux-image-liquorix-amd64 linux-headers-liquorix-amd64
Before you reboot, confirm that Ubuntu installed both the versioned Liquorix packages and the metapackages that track future releases.
dpkg -l | grep liquorix
ii linux-headers-6.19.9-1-liquorix-amd64 6.19-4ubuntu1~resolute amd64 Header files for Linux 6.19.9-1-liquorix-amd64 ii linux-headers-liquorix-amd64 6.19-4ubuntu1~resolute amd64 Linux headers for liquorix on 64-bit PCs ii linux-image-6.19.9-1-liquorix-amd64 6.19-4ubuntu1~resolute amd64 Linux 6.19 for 64-bit PCs ii linux-image-liquorix-amd64 6.19-4ubuntu1~resolute amd64 Linux image for liquorix on 64-bit PCs
The header tree should also exist under /usr/src, which matters for NVIDIA, VirtualBox, and other DKMS-managed modules.
ls -d /usr/src/linux-headers-*liquorix*
/usr/src/linux-headers-6.19.9-1-liquorix-amd64
Reboot and Verify Liquorix on Ubuntu
Reboot so GRUB can load the new kernel, then check the running kernel version from the next session.
Ubuntu 26.04 may keep booting its newer generic 7.0 kernel even after Liquorix installs cleanly. If
uname -rstill ends withgeneric, choose the Liquorix entry from GRUB once, or set that entry as your default boot target before you expect Liquorix to stay active.
sudo reboot
uname -r
6.19.9-1-liquorix-amd64
If the output ends with liquorix-amd64, the Liquorix kernel is active. If it still ends with generic, use the troubleshooting section to check the GRUB entries before changing boot defaults.
Compare Liquorix With Other Ubuntu Kernel Choices
Liquorix is not the only way to move off Ubuntu’s stock kernel, so it helps to match the kernel track to the kind of system you actually run.
| Kernel Option | Primary Focus | Best For | Trade-offs |
|---|---|---|---|
| Install HWE Kernel on Ubuntu | Newer hardware support on Ubuntu’s supported stack | Desktops that need newer drivers without leaving Ubuntu defaults | More conservative tuning than Liquorix |
| Install Zabbly Kernel on Ubuntu | Mainline-style kernel tracking | Testing newer upstream kernels and hardware support quickly | Faster update cadence and less Ubuntu-style conservatism |
| Install XanMod Kernel on Ubuntu | Performance tuning for gaming and desktop workloads | Users who want another custom desktop kernel track | Different patch choices, same Secure Boot caveat class |
| Liquorix Kernel | Low-latency desktop responsiveness | Audio work, gaming, and interactive desktop systems | Unsigned for Secure Boot and limited to amd64 |
- Choose Liquorix when input latency and desktop responsiveness matter more than staying close to Ubuntu’s stock kernel behavior.
- Choose HWE when you mainly want newer drivers and hardware support with Ubuntu-managed defaults.
- Choose Zabbly when you want a mainline-style tracking kernel for newer upstream code paths.
- Choose XanMod when you want another desktop performance kernel and prefer its patch mix over Liquorix.
Update or Remove Liquorix Kernel on Ubuntu
Update Liquorix Kernel on Ubuntu
Liquorix updates through APT, so refresh package metadata and upgrade the Liquorix metapackages when new builds land in the PPA.
sudo apt update
sudo apt install --only-upgrade linux-image-liquorix-amd64 linux-headers-liquorix-amd64
After an update run, the metapackage should show the same installed and candidate version unless a newer kernel is waiting for the next upgrade.
apt-cache policy linux-image-liquorix-amd64
linux-image-liquorix-amd64:
Installed: 6.19-4ubuntu1~resolute
Candidate: 6.19-4ubuntu1~resolute
Version table:
*** 6.19-4ubuntu1~resolute 500
500 https://ppa.launchpadcontent.net/damentz/liquorix/ubuntu resolute/main amd64 Packages
100 /var/lib/dpkg/status
Install an Ubuntu Fallback Kernel Before Removing Liquorix
Make sure an Ubuntu kernel track is available before you remove Liquorix, otherwise the next reboot can leave you without the kernel you expect.
sudo apt install linux-image-generic linux-headers-generic
That command restores Ubuntu’s GA kernel track. If you prefer the Hardware Enablement stack instead, use Install HWE Kernel on Ubuntu and keep that kernel family in place before removing Liquorix. Systems that already use HWE can continue booting the HWE generic kernel after Liquorix is removed.
Remove Liquorix Kernel Packages on Ubuntu
List the installed Liquorix packages first so you can see exactly what the removal step is about to purge.
dpkg -l | grep liquorix
ii linux-headers-6.19.9-1-liquorix-amd64 6.19-4ubuntu1~jammy amd64 Header files for Linux 6.19.9-1-liquorix-amd64 ii linux-headers-liquorix-amd64 6.19-4ubuntu1~jammy amd64 Linux headers for liquorix on 64-bit PCs ii linux-image-6.19.9-1-liquorix-amd64 6.19-4ubuntu1~jammy amd64 Linux 6.19 for 64-bit PCs ii linux-image-liquorix-amd64 6.19-4ubuntu1~jammy amd64 Linux image for liquorix on 64-bit PCs
Remove the Liquorix packages first, then review any leftover automatic dependencies in a separate cleanup step.
sudo apt remove --purge 'linux-*liquorix*'
The following packages will be REMOVED: linux-headers-6.19.9-1-liquorix-amd64* linux-headers-liquorix-amd64* linux-image-6.19.9-1-liquorix-amd64* linux-image-liquorix-amd64* W: Removing the running kernel
Ubuntu warns when Liquorix is still the running kernel, which is why the fallback-kernel step comes first. Ubuntu 26.04 shows the same four packages under an APT 3 REMOVING: summary, while Ubuntu 24.04 and 22.04 keep the older The following packages will be REMOVED: wording. Use a separate cleanup pass for orphaned dependencies so you can review what else APT wants to remove.
sudo apt autoremove
Remove the Liquorix PPA on Ubuntu
Remove the PPA after the package purge so future APT refreshes stop pulling Liquorix metadata.
sudo add-apt-repository --remove ppa:damentz/liquorix -y
Ubuntu 24.04 and 26.04 currently write this PPA as a .sources file, while Ubuntu 22.04 typically uses a .list file. The extension matters less than confirming that no damentz source file remains after removal.
ls /etc/apt/sources.list.d | grep damentz || echo "No Liquorix source files remain"
No Liquorix source files remain
Reboot and Verify the Restored Ubuntu Kernel After Removing Liquorix
Reboot one more time so Ubuntu comes back on the restored kernel track instead of the removed Liquorix image.
sudo reboot
uname -r
6.8.0-106-generic
A restored Ubuntu kernel usually ends with generic, although the exact version depends on whether you kept the GA or HWE track.
Troubleshoot Liquorix on Ubuntu
Most Liquorix problems on Ubuntu come down to boot selection, Secure Boot, or third-party modules that need to rebuild against the new headers.
Ubuntu Still Boots the Generic Kernel After Liquorix Installation
If Ubuntu comes back on a generic kernel after installation, confirm that GRUB actually has a Liquorix entry before you change anything else.
sudo grep -n liquorix /boot/grub/grub.cfg
219: menuentry 'Ubuntu, with Linux 6.19.9-1-liquorix-amd64' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-6.19.9-1-liquorix-amd64-advanced-ba3bd1ba-5e3a-4cf8-b426-5803f0a6cfca' {
233: echo 'Loading Linux 6.19.9-1-liquorix-amd64 ...'
234: linux /boot/vmlinuz-6.19.9-1-liquorix-amd64 root=UUID=ba3bd1ba-5e3a-4cf8-b426-5803f0a6cfca ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
If the entry exists, choose it once from GRUB on the next boot. For a persistent GUI workflow, Install GRUB Customizer on Ubuntu and set the Liquorix entry as the default only after you confirm it boots cleanly.
Secure Boot Blocks Liquorix on Ubuntu
Liquorix packages from the Launchpad PPA are not signed for Secure Boot, so a Secure Boot-enabled system can refuse to load them. Disable Secure Boot in UEFI firmware, or keep Ubuntu’s signed kernel track if you do not want to manage your own signing workflow.
NVIDIA or VirtualBox Modules Fail After a Liquorix Boot on Ubuntu
DKMS-managed modules need the Liquorix headers to rebuild cleanly after the new kernel installs. If a driver breaks after the switch, boot an Ubuntu kernel that still works, reinstall or rebuild the affected DKMS package, and then retry the Liquorix boot. For the NVIDIA path, use Install NVIDIA Drivers on Ubuntu to rebuild the driver stack against the active headers.
Liquorix Kernel on Ubuntu FAQ
Liquorix replaces Ubuntu’s stock desktop tuning with a lower-latency kernel aimed at gaming, audio work, and other interactive loads. It uses Project-C scheduler tuning, aggressive preemption, a 1000 Hz timer, and desktop-focused I/O defaults such as BFQ or Kyber depending on the device queue model.
Not by default. Liquorix packages from the PPA are unsigned for Secure Boot, so Ubuntu systems with Secure Boot enabled usually need it disabled in firmware before the Liquorix kernel will boot unless you sign the kernel and related modules yourself.
Ubuntu can keep its existing default GRUB entry even after the Liquorix packages install. On newer releases such as Ubuntu 26.04, the stock generic kernel may also sort ahead of the current Liquorix build, so check uname -r after reboot and choose the Liquorix entry from GRUB if the system stays on generic.
Install the Ubuntu kernel track you want first, remove the Liquorix packages, remove the PPA, and reboot. After the restart, uname -r should end with generic or another Ubuntu kernel name instead of liquorix-amd64.
Conclusion
Liquorix is running on Ubuntu with a lower-latency kernel once uname -r reports the Liquorix build instead of generic. If Ubuntu’s own kernel track is a better fit later, Install HWE Kernel on Ubuntu for newer hardware support. If boot-order changes are the real problem, Install GRUB Customizer on Ubuntu to manage the default entry from the desktop.
Formatting tips for your comment
You can use basic HTML to format your comment. Useful tags currently allowed in published comments:
<code>command</code>command<strong>bold</strong><em>italic</em><blockquote>quote</blockquote>