Frame-time spikes, audio dropouts, and sluggish input can happen when Linux Mint’s stock kernel is not tuned for low-latency desktop work. You can install the Liquorix kernel on Linux Mint 22.x and 21.x from the Launchpad PPA when gaming, audio production, or other interactive workloads matter more than staying on Mint’s conservative generic kernel track.
Liquorix is a desktop-focused kernel build with aggressive preemption, PDS scheduler tuning, a 1000 Hz timer, and I/O defaults aimed at responsiveness. The upstream Liquorix website also publishes an install script, but explicit Liquorix Launchpad PPA commands are easier for newer Mint users to audit because they show the package source, verification point, and cleanup path.
Install Liquorix Kernel on Linux Mint
The PPA publishes packages for the Ubuntu bases used by current Linux Mint releases: Mint 22.x uses Ubuntu 24.04 noble, while Mint 21.x uses Ubuntu 22.04 jammy. The package names are the same on both Mint series.
Use Liquorix only on 64-bit x86 systems. If Secure Boot is enabled and you do not want to manage your own kernel signing, keep Linux Mint’s generic kernel instead of switching to a third-party kernel.
Install Liquorix from the Launchpad PPA
Run these phases in order so APT uses the correct Ubuntu-base suite, installs both the image and headers, and proves the new kernel is active after reboot.
Update Linux Mint and Check Your CPU Architecture
Refresh package metadata before adding the PPA. If the upgrade installs a new generic kernel, reboot before continuing so Mint starts from a clean package state.
sudo apt update
sudo apt upgradeThese commands use
sudobecause they change system packages. If your account cannot run administrative commands yet, set up sudo access with the Linux Mint sudoers instructions before continuing.
Liquorix publishes Ubuntu PPA packages for amd64, which Mint reports as x86_64 from the kernel architecture command.
uname -mx86_64
Continue only when the output is x86_64. ARM systems and other CPU architectures are outside this Liquorix PPA package path.
Add the Liquorix PPA on Linux Mint
Standard Mint desktop installs may not include the PPA helper until you install software-properties-common. Add that package first, then add the Liquorix PPA.
sudo apt install software-properties-commonsudo add-apt-repository ppa:damentz/liquorix -yThe -y flag accepts the PPA prompt. On supported Mint releases, the helper maps Mint 22.x to noble and Mint 21.x to jammy, so you do not need to write a manual source file with a Mint codename such as zena or virginia.
Refresh APT again, then check that the Liquorix image metapackage has a candidate from the PPA.
sudo apt updateapt-cache policy linux-image-liquorix-amd64Example output from Linux Mint 22.x shows the noble package. Mint 21.x shows the same package with a ~jammy suffix instead.
linux-image-liquorix-amd64:
Installed: (none)
Candidate: 7.0-8ubuntu1~noble
Version table:
7.0-8ubuntu1~noble 500
500 https://ppa.launchpadcontent.net/damentz/liquorix/ubuntu noble/main amd64 Packages
If Candidate is (none), stop before installing. The PPA was not added correctly, the package metadata did not refresh, or your Mint release does not match a supported Ubuntu base.
Install Liquorix Image and Headers on Linux Mint
Install the Liquorix image and header metapackages together. The headers matter for DKMS-managed drivers and virtualization modules, including NVIDIA and VirtualBox.
sudo apt install linux-image-liquorix-amd64 linux-headers-liquorix-amd64APT may install extra development libraries with the header package. That is normal; review the transaction and continue when the main packages are the Liquorix image, Liquorix headers, and their required dependencies.
Confirm that the installed package list includes both the versioned Liquorix packages and the tracking metapackages.
dpkg-query -W -f='${db:Status-Abbrev} ${binary:Package} ${Version}\n' 'linux-*liquorix*' 2>/dev/null | sortii linux-headers-7.0.8-1-liquorix-amd64 7.0-8ubuntu1~noble ii linux-headers-liquorix-amd64 7.0-8ubuntu1~noble ii linux-image-7.0.8-1-liquorix-amd64 7.0-8ubuntu1~noble ii linux-image-liquorix-amd64 7.0-8ubuntu1~noble
Check that the Liquorix header tree exists under /usr/src.
ls -d /usr/src/linux-headers-*liquorix*/usr/src/linux-headers-7.0.8-1-liquorix-amd64
Reboot and Verify Liquorix on Linux Mint
Reboot so GRUB can start the new kernel, then check the running kernel from the next session.
Keep at least one Linux Mint generic kernel installed and make sure you can reach the GRUB menu before rebooting. If Liquorix does not boot correctly, choose a generic kernel from GRUB’s advanced options and remove Liquorix after the generic kernel starts.
sudo rebootuname -r7.0.8-1-liquorix-amd64
The exact version changes as Liquorix publishes new kernels. The important part is that the output ends with liquorix-amd64.
Compare Liquorix With Other Linux Mint Kernel Choices
Liquorix is useful for latency-sensitive desktops, but it is not the safest default for every Mint system. Match the kernel source to the problem you are trying to solve.
| Kernel Option | Update Source | Best For | Trade-offs |
|---|---|---|---|
| Linux Mint generic kernel | Linux Mint and Ubuntu base repositories | Most desktops, laptops, and systems where stability matters most | Conservative tuning compared with custom desktop kernels |
| Mint Update Manager kernel branches | Linux Mint Update Manager | Users who want a Mint-supported kernel switch from the graphical tools | Less aggressive latency tuning than Liquorix or XanMod |
| XanMod Kernel on Linux Mint | XanMod repository | Users comparing custom desktop kernel patch sets | Different package source and CPU-level choices to manage |
| Liquorix Kernel | Launchpad PPA | Gaming, audio work, and responsive desktop workloads on x86_64 systems | Third-party kernel source, Secure Boot caveat, and more frequent kernel churn |
- Stay on Mint’s generic kernel when the system is a work machine, a shared family computer, or a laptop where predictable updates matter more than latency tuning.
- Try Liquorix when you can recover from GRUB, need lower desktop latency, and are comfortable testing a third-party kernel after each major update.
- Compare XanMod when you want another custom desktop kernel path before deciding which patch set behaves better on your hardware.
Update or Remove Liquorix Kernel on Linux Mint
Update Liquorix Kernel on Linux Mint
Liquorix updates through APT after the PPA is enabled. Run the install command again after refreshing metadata; APT upgrades the tracking metapackages and pulls in the newer versioned image and header packages when available.
sudo apt update
sudo apt install linux-image-liquorix-amd64 linux-headers-liquorix-amd64Check the package candidate if you want to confirm whether APT already installed the newest Liquorix build for your Mint base.
apt-cache policy linux-image-liquorix-amd64When the installed version changes, reboot and confirm that uname -r reports the new liquorix-amd64 kernel.
Boot a Generic Kernel Before Removing Liquorix
Do not remove Liquorix while the system is still running a Liquorix kernel. Debian-family systems can stop the removal with a running-kernel warning, and continuing from that prompt is risky for newer users.
First, make sure the generic Mint kernel track is installed.
sudo apt install linux-image-generic linux-headers-genericCheck the running kernel before you remove anything.
uname -rIf the output still ends with liquorix-amd64, reboot and choose a generic kernel from GRUB’s advanced options menu. The menu title can include the Mint version and desktop edition, so use the kernel name rather than the menu label as your checkpoint. After the generic kernel boots, run uname -r again and continue only when the output ends with generic.
If Mint keeps booting Liquorix and you want a graphical boot-menu editor after you have confirmed the generic entry works, use GRUB Customizer on Linux Mint to set the preferred default entry.
Remove Liquorix Kernel Packages on Linux Mint
List the installed Liquorix packages so you know what APT should remove.
dpkg-query -W -f='${db:Status-Abbrev} ${binary:Package} ${Version}\n' 'linux-*liquorix*' 2>/dev/null | sortThen remove the Liquorix image and header packages. The APT pattern selects installed packages whose names start with linux- and include liquorix. Review the transaction before accepting it; the package list should be limited to Liquorix packages.
sudo apt remove --purge '?and(?installed,?name(^linux-.*liquorix.*))'Confirm that no Liquorix packages remain installed.
dpkg -l | grep liquorix || echo "No Liquorix packages remain installed"No Liquorix packages remain installed
Remove the Liquorix PPA on Linux Mint
Remove the PPA after the packages are gone so future APT refreshes stop reading the Liquorix source.
sudo add-apt-repository --remove ppa:damentz/liquorix -y
sudo apt updateCheck that the generated source file is gone.
sudo find /etc/apt/sources.list.d -maxdepth 1 \( -iname '*damentz*' -o -iname '*liquorix*' \) -print | sortNo output means the Liquorix source file is no longer active. Current Mint 22.x and 21.x cleanup normally removes the generated PPA key, which uses version-specific names such as damentz-liquorix-noble.gpg or damentz-liquorix-jammy.gpg, but check for leftovers if this system has been upgraded or used older instructions before.
sudo find /etc/apt/keyrings /etc/apt/trusted.gpg.d -maxdepth 1 \( -iname '*damentz*' -o -iname '*liquorix*' -o -iname 'A7654D8BAB1824F4D8F4E9D19352A0B69B72E6DF*' \) -print 2>/dev/null | sortIf the command prints a Liquorix key file and no Liquorix source file remains, remove only those Liquorix-related key files.
sudo rm -f /etc/apt/keyrings/damentz-liquorix-noble.gpg /etc/apt/keyrings/damentz-liquorix-jammy.gpg /etc/apt/keyrings/A7654D8BAB1824F4D8F4E9D19352A0B69B72E6DF.keyring /etc/apt/trusted.gpg.d/damentz-ubuntu-liquorix.gpg /etc/apt/trusted.gpg.d/damentz-ubuntu-liquorix.gpg~Preview automatic cleanup before removing orphaned dependencies. Mint may list development libraries that the Liquorix header package pulled in, but your system may have other packages marked automatic from earlier work.
sudo apt autoremove --dry-runRun the real cleanup only when the preview contains packages you are comfortable removing.
sudo apt autoremoveReboot one more time and confirm that Linux Mint starts from a generic kernel.
sudo rebootuname -rA restored Mint kernel normally ends with generic, although the exact version depends on the kernel branch installed on your system.
Troubleshoot Liquorix on Linux Mint
Most Liquorix problems on Linux Mint come from PPA metadata, GRUB boot selection, Secure Boot, or DKMS modules that need matching headers.
APT Cannot Find the Liquorix Package
Check the package candidate first. This tells you whether APT can see the Liquorix PPA for your Mint base.
apt-cache policy linux-image-liquorix-amd64If Candidate is (none), run sudo apt update again and check whether the PPA add step completed without errors. Mint 22.x should consume the PPA’s noble metadata, while Mint 21.x should consume jammy metadata.
Linux Mint Still Boots the Generic Kernel After Liquorix Installation
First confirm that GRUB has a Liquorix entry.
sudo grep -E "menuentry '.*liquorix-amd64" /boot/grub/grub.cfgIf an entry exists, choose the Liquorix option once from GRUB’s advanced menu. Do not make it the permanent default until it has booted successfully at least once.
Removing Liquorix Prompts About the Running Kernel
If APT warns that you are trying to remove the same kernel version that is currently running, abort the removal. Reboot, select a generic kernel from GRUB’s advanced options, confirm with uname -r, and then rerun the removal command.
NVIDIA, VirtualBox, or Other DKMS Modules Fail After Liquorix Boots
DKMS modules must rebuild against the active Liquorix headers. Check that the header directory exists for the running kernel.
ls -d /usr/src/linux-headers-$(uname -r)If the directory is missing, confirm the Liquorix PPA is still enabled, then refresh APT and install the Liquorix header metapackage again.
sudo apt update
sudo apt install linux-headers-liquorix-amd64If the module still fails, boot a generic kernel that works, repair the affected driver package, and retry Liquorix. For proprietary GPU issues, use NVIDIA drivers on Linux Mint to rebuild the driver stack from a known working kernel. For VirtualBox module issues, review the VirtualBox on Linux Mint package path before rebuilding against Liquorix.
Secure Boot Blocks the Liquorix Kernel
Secure Boot can block third-party kernels that are not signed for the normal Mint boot chain. Check the current state first.
mokutil --sb-stateIf Secure Boot is enabled, disable it in UEFI firmware, manage your own signing workflow, or stay on Mint’s generic kernel if Secure Boot is required on that machine. Systems booted without UEFI support may report that EFI variables are unavailable instead.
Conclusion
Liquorix is active on Linux Mint once uname -r ends with liquorix-amd64, and APT owns future kernel updates through the PPA. Keep a generic kernel available for rollback, review each kernel transaction before accepting it, and change GRUB defaults only after the new kernel boots cleanly.
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>