How to Install Liquorix Kernel on Debian

The Liquorix Kernel replaces Debian’s default kernel with one optimized for desktop responsiveness, gaming, multimedia production, and real-time workloads. If you experience input lag during gaming, audio glitches in DAW software, or sluggish desktop performance under heavy multitasking, Liquorix addresses these issues through aggressive latency tuning. By the end of this guide, you will have Liquorix installed and verified as your active kernel on Debian.

Key optimizations include Zen Interactive Tuning, the PDS process scheduler, 1000Hz tick rate, hard kernel preemption, Budget Fair Queue disk scheduling, and TCP BBR2 congestion control. Additionally, Liquorix enables compressed swap with LZ4 and the multigenerational LRU algorithm for better performance under memory pressure.

Liquorix provides packages for amd64 (64-bit x86) only. The project does not support ARM, i386, or other architectures. Additionally, Liquorix kernels lack Secure Boot signatures, so if your system uses Secure Boot, you must disable it in your UEFI/BIOS settings before the Liquorix kernel will boot.

Compare Debian Kernel Options

Debian offers several kernel options depending on your performance and stability requirements:

Kernel Option	Primary Focus	Best For	Trade-offs
Default Debian Kernel	Stability and broad hardware support	Servers and users who prioritize reliability	Conservative features, older drivers
Liquorix Kernel	Desktop responsiveness and low latency	Gaming, audio production, real-time workloads	Higher power usage, less testing than default
XanMod Kernel	Balanced performance with multiple scheduler options	Desktop users wanting newer features with choices	Requires selecting appropriate variant
Mainline Kernel	Bleeding-edge features and newest drivers	Testing new hardware, kernel development	Less stable, no Debian-specific patches

For gaming and multimedia workloads, choose Liquorix because its Zen Interactive Tuning prioritizes the responsiveness that desktop users notice most. In contrast, the default kernel remains the safest choice for servers or systems where stability outweighs interactivity.

Choose Your Liquorix Installation Method

You can install Liquorix through Debian’s extrepo tool or by manually configuring the repository. The following table compares both approaches:

Method	GPG Key Management	Debian Support	Steps Required	Best For
extrepo (Recommended)	Automatic	11, 12, 13	4 commands	Most users; quick setup with minimal configuration
Manual Repository	Manual download	11, 12, 13	6 commands	Scripted deployments, custom configurations, or learning APT internals

For most users, the extrepo method is recommended because it handles GPG key management automatically and detects your Debian version. Only use the manual method if you need explicit control over repository configuration or are scripting automated deployments.

Debian 11 users: The Liquorix repository provides kernel version 6.5.x for Bullseye, which is significantly older than the current kernels (6.17.x) available for Debian 12 and 13. While functional, you will not receive the latest upstream features or security patches available in newer kernel branches.

Update Debian Before Liquorix Installation

First, update your existing packages to prevent conflicts during installation:

sudo apt update && sudo apt upgrade

Option 1: Install Liquorix via extrepo (Recommended)

The extrepo tool is Debian’s official method for managing external repositories. It handles GPG key downloads automatically and configures the correct repository URL based on your Debian version.

Install extrepo

Install the extrepo package if it is not already present on your system:

sudo apt install extrepo

Enable the Liquorix Repository

Next, enable the Liquorix repository using extrepo. This command downloads the GPG key and creates the repository configuration automatically:

sudo extrepo enable liquorix

Then, verify the repository was added correctly:

cat /etc/apt/sources.list.d/extrepo_liquorix.sources

Components: main
Uris: https://liquorix.net/debian
Suites: trixie
Types: deb deb-src
Signed-By: /var/lib/extrepo/keys/liquorix.asc

The Suites field above shows trixie as an example. Your output will display your actual Debian codename (trixie, bookworm, or bullseye) based on your installed version.

Update Package Index and Verify Repository

Refresh APT to recognize the new repository, then verify the Liquorix packages are available:

sudo apt update

apt-cache policy linux-image-liquorix-amd64

linux-image-liquorix-amd64:
  Installed: (none)
  Candidate: 6.x.x~your-release
  Version table:
     6.x.x~your-release 500
        500 https://liquorix.net/debian your-release/main amd64 Packages

The output confirms APT can locate the Liquorix kernel packages. Now proceed to the Install Liquorix Kernel section below.

Option 2: Install Liquorix via Manual Repository

If you prefer manual control over the repository configuration, follow these steps to add the Liquorix repository directly. This method gives you explicit visibility into the GPG key and DEB822 configuration.

Install Prerequisites

First, install the required packages for repository management. The lsb-release package is essential because the repository configuration uses the lsb_release command to detect your Debian version:

sudo apt install lsb-release curl ca-certificates

Import the Liquorix GPG Key

Next, download the Liquorix signing key to verify package authenticity. Place it in /usr/share/keyrings/ so APT can reference it with scoped trust:

sudo curl -fsSL https://liquorix.net/liquorix-keyring.gpg -o /usr/share/keyrings/liquorix-archive-keyring.gpg

Then, verify the key downloaded successfully:

ls -l /usr/share/keyrings/liquorix-archive-keyring.gpg

-rw-r--r-- 1 root root 3441 Dec  1 10:39 /usr/share/keyrings/liquorix-archive-keyring.gpg

Add the Liquorix Repository

Create a DEB822 format .sources file that references your Debian version automatically. This modern format provides clearer syntax and scoped GPG key trust:

cat <<EOF | sudo tee /etc/apt/sources.list.d/liquorix.sources
Types: deb deb-src
URIs: https://liquorix.net/debian
Suites: $(lsb_release -cs)
Components: main
Architectures: amd64
Signed-By: /usr/share/keyrings/liquorix-archive-keyring.gpg
EOF

The $(lsb_release -cs) command automatically inserts your Debian codename (trixie, bookworm, or bullseye). Afterward, verify the command created the file correctly:

cat /etc/apt/sources.list.d/liquorix.sources

Types: deb deb-src
URIs: https://liquorix.net/debian
Suites: trixie
Components: main
Architectures: amd64
Signed-By: /usr/share/keyrings/liquorix-archive-keyring.gpg

Debian 13 (trixie), 12 (bookworm), and 11 (bullseye) all support the DEB822 .sources format. This guide uses the modern format for all versions because it works identically across releases and provides better security through scoped key trust.

Update Package Index and Verify Repository

Refresh APT to recognize the new repository, then verify the Liquorix packages are available:

sudo apt update

apt-cache policy linux-image-liquorix-amd64

linux-image-liquorix-amd64:
  Installed: (none)
  Candidate: 6.x.x~your-release
  Version table:
     6.x.x~your-release 500
        500 https://liquorix.net/debian your-release/main amd64 Packages

The output confirms APT can locate the Liquorix kernel packages from the repository you configured.

Install Liquorix Kernel

With the repository configured (via either method above), install the Liquorix kernel packages:

sudo apt install linux-image-liquorix-amd64 linux-headers-liquorix-amd64

This command installs both the kernel image and headers. You need the headers for building kernel modules such as NVIDIA drivers through DKMS (Dynamic Kernel Module Support), which automatically rebuilds third-party drivers when you install new kernels.

Afterward, verify APT installed the packages correctly:

dpkg -l | grep liquorix

ii  linux-headers-6.x.x-liquorix-amd64   6.x.x~your-release amd64  Header files for Linux 6.x.x-liquorix-amd64
ii  linux-headers-liquorix-amd64         6.x.x~your-release amd64  Linux headers for liquorix on 64-bit PCs
ii  linux-image-6.x.x-liquorix-amd64     6.x.x~your-release amd64  Linux 6.x for 64-bit PCs
ii  linux-image-liquorix-amd64           6.x.x~your-release amd64  Linux image for liquorix on 64-bit PCs

The version numbers above serve as examples. Your installation will reflect the current Liquorix release available for your Debian version.

Reboot to Activate Liquorix

Now, reboot your system to load the new kernel:

sudo reboot

If you encounter boot issues, hold Shift during startup to access the GRUB menu. Select Advanced options for Debian and choose your original Debian kernel to boot safely.

Verify Liquorix Kernel Is Active

After rebooting, confirm the Liquorix kernel is running:

uname -r

The output should include “liquorix” in the kernel version string:

6.x.x-liquorix-amd64

For more detailed system information including the kernel:

hostnamectl

 Static hostname: debian
       Icon name: computer-vm
         Chassis: vm
      Machine ID: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
         Boot ID: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
  Virtualization: kvm
Operating System: Debian GNU/Linux 13 (trixie)
          Kernel: Linux 6.x.x-liquorix-amd64
    Architecture: x86-64

Manage Liquorix Kernel

Update Liquorix Kernel

Liquorix updates arrive through APT alongside your regular system updates:

sudo apt update && sudo apt upgrade

After kernel updates, reboot to activate the new version. Your previous kernel remains available in the GRUB menu as a fallback option.

Remove Liquorix Kernel

Before removing Liquorix, ensure you have the default Debian kernel installed and bootable. Removing your only kernel will leave the system unbootable. Therefore, complete all steps below before rebooting.

Verify Default Kernel Is Installed

First, confirm your system has the default Debian kernel:

dpkg -l | grep linux-image | grep -v liquorix

If no default kernel appears in the output, install one before proceeding:

sudo apt install linux-image-amd64

Remove Liquorix Packages

Next, remove all Liquorix kernel packages and clean up orphaned dependencies:

sudo apt purge linux-*liquorix* && sudo apt autoremove

When prompted, confirm the removal. Do not reboot yet.

Remove Repository and GPG Key

Clean up the Liquorix repository configuration. The commands differ slightly depending on which installation method you used:

If you used extrepo:

sudo extrepo disable liquorix
sudo rm -f /etc/apt/sources.list.d/extrepo_liquorix.sources

If you used the manual method:

sudo rm /etc/apt/sources.list.d/liquorix.sources
sudo rm /usr/share/keyrings/liquorix-archive-keyring.gpg

Then, refresh the package cache and verify the repository was removed:

sudo apt update
apt-cache policy linux-image-liquorix-amd64

linux-image-liquorix-amd64:
  Installed: (none)
  Candidate: (none)
  Version table:

The output confirms the Liquorix repository is no longer available.

Update GRUB and Reboot

Regenerate the boot configuration and restart:

sudo update-initramfs -u && sudo update-grub

sudo reboot

Verify Default Kernel Is Active

After rebooting, confirm the system is running the default Debian kernel:

uname -r

The output should show the standard Debian kernel without “liquorix”:

6.x.x-amd64

Troubleshoot Liquorix Issues

System Fails to Boot After Installation

If your system fails to boot after installing Liquorix, access the GRUB menu by holding Shift during startup. Select Advanced options for Debian, then choose your original kernel (without “liquorix” in the name) to boot into a working system. From there, you can remove Liquorix using the steps in the removal section above.

Secure Boot Blocking Liquorix

Liquorix kernels lack Secure Boot signatures. If your system boots to the GRUB menu but fails to load Liquorix with a security or signature error, then Secure Boot is likely blocking it. First, boot into your original Debian kernel from GRUB, then check Secure Boot status:

mokutil --sb-state

SecureBoot enabled

To use Liquorix, reboot and enter your UEFI/BIOS settings (typically by pressing F2, F12, Del, or Esc during startup). Then, navigate to the Security or Boot section and disable Secure Boot. Save changes and exit. Once you disable Secure Boot, the Liquorix kernel will boot normally.

NVIDIA or Other Kernel Modules Not Working

New kernels require rebuilding kernel modules like NVIDIA drivers. DKMS (Dynamic Kernel Module Support) handles this automatically when you install kernel updates. However, if your graphics driver stops working after switching to Liquorix, check whether DKMS built the modules for the new kernel:

dkms status

Example output showing modules not installed for the Liquorix kernel:

nvidia/560.35.03, 6.x.x-amd64, x86_64: installed
nvidia/560.35.03, 6.x.x-liquorix-amd64, x86_64: built

If modules show “built” but not “installed” for the Liquorix kernel version, rebuild and install them:

sudo dkms autoinstall

Finally, verify DKMS installed the modules for the Liquorix kernel:

dkms status

nvidia/560.35.03, 6.x.x-amd64, x86_64: installed
nvidia/560.35.03, 6.x.x-liquorix-amd64, x86_64: installed

For detailed NVIDIA driver installation, see our guide on installing NVIDIA drivers on Debian.

Repository Update Errors

If apt update reports GPG errors for the Liquorix repository, then the signing key may be missing or corrupted. The fix depends on which installation method you used:

If you used extrepo:

sudo extrepo disable liquorix
sudo extrepo enable liquorix
sudo apt update

If you used the manual method:

sudo curl -fsSL https://liquorix.net/liquorix-keyring.gpg -o /usr/share/keyrings/liquorix-archive-keyring.gpg
sudo apt update

Conclusion

You now have the Liquorix kernel installed on Debian, either through extrepo for simplified management or via manual repository configuration. As a result, the kernel’s Zen Interactive Tuning and PDS scheduler provide noticeable responsiveness improvements for gaming, audio production, and other desktop workloads. Additionally, keep the default Debian kernel installed as a fallback, accessible through the GRUB menu if you encounter hardware compatibility issues.