How to Install Liquorix Kernel on Debian 13, 12 and 11

Desktop latency is where Debian’s conservative kernel can feel least forgiving: games hitch, audio workstations drop buffers, and interactive workloads compete with background I/O. You can install Liquorix Kernel on Debian from the Liquorix APT repository when you need a low-latency kernel track with package-managed updates and a clean rollback path.

The current Liquorix Debian repository provides working meta packages for Debian 13 (Trixie) and Debian 12 (Bookworm) on amd64. Debian 11 (Bullseye) still has repository metadata online, but its Liquorix meta packages currently depend on missing package names, so Bullseye users should keep the default Debian kernel or upgrade before using Liquorix.

Liquorix kernels are unsigned for Secure Boot. Disable Secure Boot in UEFI/BIOS or keep using Debian’s signed kernel packages if Secure Boot must remain enabled.

Install Liquorix Kernel on Debian

This workflow uses the same Liquorix repository and signing key as the official Liquorix install script, but writes a DEB822 source file so the repository is easier to audit and remove later. Avoid configuring both this source and an older extrepo Liquorix source on the same system.

Confirm Debian Release and Architecture

Check the codename and architecture before adding the repository:

. /etc/os-release
printf '%s\n' "$VERSION_CODENAME"
dpkg --print-architecture

trixie
amd64

Continue on trixie or bookworm with amd64. Stop on bullseye, ARM, or i386 unless the Liquorix repository metadata changes and you revalidate the package path first.

Refresh APT and Install Prerequisites

Refresh package metadata, then install the tools used to download and inspect the repository key:

sudo apt update
sudo apt install curl ca-certificates gpg

These commands use sudo for root-owned package, keyring, and source-file changes. If your account cannot use sudo yet, add the account to sudoers with the Debian sudoers setup workflow before continuing.

If curl is new to you, the curl command reference explains the flags used in the download command.

Add the Liquorix APT Repository

Download the Liquorix signing key from the official Liquorix project site into a dedicated keyring file:

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

Inspect the key fingerprints before trusting the repository:

gpg --quiet --show-keys --with-fingerprint /usr/share/keyrings/liquorix-archive-keyring.gpg

pub   dsa1024 2009-05-11 [SC]
      70C4 F178 C4AC 36D2 9A3B  52F0 3EFF 4F27 2FB2 CD80
uid                      Steven Barrett <damentz@gmail.com>
sub   elg2048 2009-05-11 [E]

pub   rsa4096 2016-03-19 [SC]
      C5AD B4F3 FEBB CE27 A3E5  4D7D 9AE4 0780 33F8 024D
uid                      Steven Barrett <steven@liquorix.net>
sub   rsa4096 2016-03-19 [E]

Create the DEB822 source file only when the release and architecture are currently covered by this article:

. /etc/os-release
architecture=$(dpkg --print-architecture)

case "$VERSION_CODENAME:$architecture" in
  trixie:amd64|bookworm:amd64)
    printf '%s\n' \
    'Types: deb' \
    'URIs: https://liquorix.net/debian' \
    "Suites: $VERSION_CODENAME" \
    'Components: main' \
    'Architectures: amd64' \
    'Signed-By: /usr/share/keyrings/liquorix-archive-keyring.gpg' | sudo tee /etc/apt/sources.list.d/liquorix.sources > /dev/null
    ;;
  *)
    printf 'Liquorix meta packages are not currently covered for %s on %s.\n' "$VERSION_CODENAME" "$architecture" >&2
    false
    ;;
esac

Confirm the saved source file before refreshing APT:

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

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

Refresh APT, then confirm both Liquorix meta packages come from the new repository:

sudo apt update

apt-cache policy linux-image-liquorix-amd64 linux-headers-liquorix-amd64

linux-image-liquorix-amd64:
  Installed: (none)
  Candidate: 7.0-9.1~trixie
  Version table:
     7.0-9.1~trixie 500
        500 https://liquorix.net/debian trixie/main amd64 Packages
linux-headers-liquorix-amd64:
  Installed: (none)
  Candidate: 7.0-9.1~trixie
  Version table:
     7.0-9.1~trixie 500
        500 https://liquorix.net/debian trixie/main amd64 Packages

The exact Liquorix version changes over time. Debian 12 should show the same package names with a ~bookworm suffix, while Debian 13 shows ~trixie.

Install Liquorix Image and Headers

Install the Liquorix kernel image and matching headers:

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

The meta packages install the current versioned image and header packages. On clean Debian 13 and 12 systems, the transaction also pulled header build dependencies and packages such as irqbalance, firmware, or microcode from Debian’s own repositories where they were not already installed.

Verify the installed Liquorix package set before rebooting:

dpkg-query -W -f='${db:Status-Abbrev} ${binary:Package} ${Version}\n' 'linux-*liquorix*'

ii  linux-headers-7.0.9-1-liquorix-amd64 7.0-9.1~trixie
ii  linux-headers-liquorix-amd64 7.0-9.1~trixie
ii  linux-image-7.0.9-1-liquorix-amd64 7.0-9.1~trixie
ii  linux-image-liquorix-amd64 7.0-9.1~trixie

The versioned package names move with the Liquorix release cadence, so use the output pattern rather than the exact version as your success check.

Reboot Debian Into Liquorix Kernel

Reboot so GRUB can start the newly installed Liquorix kernel:

sudo reboot

If boot fails, open the GRUB menu with Shift or Esc, choose Advanced options for Debian GNU/Linux, and boot the previous non-Liquorix Debian kernel.

Verify Liquorix Kernel on Debian

Confirm the active kernel after reconnecting or logging back in:

uname -r

7.0.9-1-liquorix-amd64

Check that the matching header directory exists for DKMS-managed modules and other kernel-module builds:

test -d "/usr/src/linux-headers-$(uname -r)" && printf 'matching headers found\n'

matching headers found

Matching headers matter for DKMS workflows such as NVIDIA drivers, VirtualBox modules, and other out-of-tree kernel modules.

Manage Liquorix Kernel on Debian

Update Liquorix Kernel on Debian

Liquorix updates arrive through APT after the repository is configured. Upgrade the Liquorix meta packages when you want to pull the newest available Liquorix image and headers without upgrading the whole system:

sudo apt update
sudo apt install --only-upgrade linux-image-liquorix-amd64 linux-headers-liquorix-amd64

Reboot after a Liquorix kernel update, then rerun uname -r and the header-directory check to confirm the new kernel is active.

Remove Liquorix Kernel from Debian

Do not purge Liquorix while booted into a Liquorix kernel. Boot a stock Debian kernel first, then remove the Liquorix packages and repository.

Confirm Stock Debian Kernel Packages Are Installed

dpkg-query -W -f='${db:Status-Abbrev} ${binary:Package} ${Version}\n' linux-image-amd64 linux-headers-amd64

ii  linux-headers-amd64 6.12.88-1
ii  linux-image-amd64 6.12.88-1

If either stock metapackage is missing, install it before removing Liquorix:

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

Check the active kernel. If the output contains liquorix, reboot and choose a non-Liquorix Debian kernel from Advanced options for Debian GNU/Linux in GRUB.

uname -r

6.12.88+deb13-amd64

Purge Liquorix Packages

Build the package list from installed or residual Liquorix packages, then pass only those names to APT:

mapfile -t liquorix_packages < <(
  dpkg-query -W -f='${db:Status-Abbrev} ${binary:Package}\n' 'linux-*liquorix*' 2>/dev/null | awk '$1 ~ /^(ii|rc)/ {print $2}'
)

if ((${#liquorix_packages[@]})); then
  sudo apt purge "${liquorix_packages[@]}"
fi

Review the APT transaction before confirming. It should remove Liquorix image and header packages, not the stock Debian kernel you just booted.

After the Liquorix packages are gone, remove automatically installed dependencies only if the transaction keeps at least one stock fallback kernel:

sudo apt autoremove --purge

Remove Liquorix Repository and Key

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

If an older extrepo-based setup exists, remove that source and key material as well:

if command -v extrepo >/dev/null 2>&1; then
  sudo extrepo disable liquorix
fi

sudo rm -f /etc/apt/sources.list.d/extrepo_liquorix.sources
sudo rm -f /var/lib/extrepo/keys/liquorix.asc
sudo apt update

Confirm no Liquorix source file, key file, or active APT source remains:

find /etc/apt/sources.list.d /usr/share/keyrings /var/lib/extrepo/keys -maxdepth 1 -iname '*liquorix*' -print 2>/dev/null

if apt-cache policy | grep -qF 'liquorix.net'; then
  printf 'Liquorix repository is still active\n'
else
  printf 'Liquorix repository is no longer active\n'
fi

Liquorix repository is no longer active

Regenerate GRUB and Verify Stock Kernel

sudo update-grub

uname -r

6.12.88+deb13-amd64

No Liquorix package should remain installed:

dpkg-query -W -f='${db:Status-Abbrev} ${binary:Package}\n' 'linux-*liquorix*' 2>/dev/null

No output means the Liquorix image, header, and meta packages are no longer installed or left in residual-config state.

Compare Liquorix and Debian Kernel Options

Liquorix is a tuned desktop kernel, not a generic “latest kernel” replacement for every Debian system. Use the kernel track that matches the problem you are trying to solve:

Kernel Option	Source	Best For	Trade-offs
Default Debian kernel	Debian repositories	Servers, conservative desktops, Secure Boot systems	Older feature set but strongest Debian integration
Liquorix kernel	Liquorix APT repository	Gaming, audio production, and latency-sensitive desktops	Unsigned for Secure Boot and faster-moving than Debian’s stock kernel
XanMod kernel on Debian	XanMod APT repository	Users who want tuned-kernel variants and profile choices	Requires choosing the correct variant for the system
Mainline kernel on Debian	Mainline-focused workflow	Testing newer upstream hardware support or regressions	Less conservative than Debian’s packaged kernel path

Liquorix vs Zen Kernel on Debian

Debian does not ship an official linux-zen package like Arch Linux. Liquorix is the practical Debian package path for Zen-style low-latency tuning, while XanMod is the closest same-distro alternative when you want a different tuned-kernel profile.

Liquorix also includes BBR2 support; for stock-kernel network tuning context, use the separate BBR on Debian workflow instead of treating Liquorix as the only way to tune congestion control.

Troubleshoot Liquorix Kernel Issues on Debian

Debian 11 Bullseye Liquorix Dependencies Are Missing

On May 20, 2026, the Bullseye Liquorix repository still advertised linux-image-liquorix-amd64 and linux-headers-liquorix-amd64, but those meta packages depended on missing 6.5.3-2 package names. A simulated Bullseye install returned this error:

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

The following packages have unmet dependencies:
 linux-headers-liquorix-amd64 : Depends: linux-headers-6.5.3-2-liquorix-amd64 (= 6.5-2.1~bullseye) but it is not installable
 linux-image-liquorix-amd64 : Depends: linux-image-6.5.3-2-liquorix-amd64 (= 6.5-2.1~bullseye) but it is not installable
E: Unable to correct problems, you have held broken packages.

Do not work around this by installing stale kernel packages unless you have a specific recovery reason and have validated the exact package set yourself. For normal desktop use, keep Debian 11 on its default kernel or move the system to Debian 12 or 13 before installing Liquorix.

System Fails to Boot After Installing Liquorix

Use GRUB’s Advanced options for Debian GNU/Linux menu to boot the previous stock Debian kernel. After the system is back online, follow the removal workflow and keep the stock kernel selected until Liquorix is fully removed.

Secure Boot Blocks Liquorix

If Liquorix appears in GRUB but does not boot, check Secure Boot from a working Debian kernel. Install mokutil first if the command is missing:

sudo apt install mokutil
mokutil --sb-state

Disable Secure Boot in firmware settings, or stay on Debian’s signed kernel packages if Secure Boot is required on the machine.

DKMS Modules Do Not Load on Liquorix

Check DKMS status for the active Liquorix kernel:

dkms status

Look for a line that matches the active Liquorix kernel from uname -r. If the Liquorix line shows built but not installed, rebuild modules for the active kernel:

sudo dkms autoinstall
dkms status

For a complete driver setup path, use the dedicated NVIDIA drivers on Debian guide.

APT Reports Liquorix Signature or Repository Errors

Refresh the Liquorix key, inspect the source file, and rerun APT update:

sudo curl -fsSLo /usr/share/keyrings/liquorix-archive-keyring.gpg https://liquorix.net/liquorix-keyring.gpg
cat /etc/apt/sources.list.d/liquorix.sources
sudo apt update

If the error mentions Bullseye dependencies instead of a signature failure, use the Debian 11 troubleshooting section; refreshing the key cannot repair missing packages in repository metadata.

Conclusion

Debian is running the Liquorix kernel with matching headers, APT-managed updates, and a stock-kernel fallback ready for recovery. Keep Secure Boot, DKMS modules, and old fallback kernels in mind after each kernel update, especially on desktops that also depend on proprietary graphics drivers or other out-of-tree modules.