Ubuntu’s stock kernel favors broad hardware coverage and conservative defaults, but gaming, audio work, and other latency-sensitive desktop workloads often feel better on a kernel tuned for responsiveness. You can install XanMod kernel on Ubuntu 26.04 and 24.04 from the official project repository when you want CPU-specific builds, scheduler tweaks, and newer desktop-focused patches.
XanMod is a custom Linux kernel for Debian-based systems, not a Launchpad PPA or a separate package manager. The same repository gives you MAIN, EDGE, LTS, and RT branches, plus the CPU-level package selection, reboot checks, and rollback steps you need if Ubuntu keeps booting the stock kernel first.
Install XanMod Kernel on Ubuntu
Ubuntu already offers multiple kernel paths, so it helps to decide whether you want a low-risk hardware refresh or a more aggressive performance kernel before you change anything.
| Kernel Option | Primary Focus | Best For | Trade-offs |
|---|---|---|---|
| Install HWE kernel on Ubuntu | Hardware enablement and long-term support | Desktop systems that need newer drivers without leaving Ubuntu’s supported kernel track | Still conservative compared with performance kernels, and updates follow Ubuntu’s cadence |
| XanMod Kernel | Performance optimization and low latency | Gaming, multimedia production, and workstations that value responsiveness over exhaustive certification | More aggressive patching, tighter hardware focus, and extra bootloader work on some systems |
| Install Liquorix kernel on Ubuntu | Desktop responsiveness and multimedia | General-purpose desktops, creative work, and low-latency interactive use | Less CPU-specific than XanMod and still outside Ubuntu’s stock kernel track |
| Install Zabbly kernel on Ubuntu | Mainline kernel tracking | Developers and early adopters who want upstream kernels with fewer downstream changes | Less desktop-focused tuning and faster-moving upstream churn |
Use XanMod when lower latency, frame pacing, or desktop responsiveness matter more than staying on Ubuntu’s default kernel cadence. If you mainly need newer hardware support with fewer surprises, install HWE kernel on Ubuntu instead.
These instructions are scoped to Ubuntu 26.04 LTS and 24.04 LTS. XanMod’s current supported-codename list no longer includes jammy, so Ubuntu 22.04 is not documented here even though the repository still exposes legacy jammy packages.
XanMod supports only
x86_64systems and does not ship Microsoft-signed kernels for Secure Boot. Check your architecture withuname -m; if it returnsx86_64, you can continue. If Secure Boot must stay enabled, keep Ubuntu’s stock or HWE kernel instead.
Update Ubuntu Before XanMod Installation
Start with a standard package index refresh so Ubuntu pulls the newest dependency metadata before you add another kernel repository.
sudo apt updateThese commands use
sudofor system-wide changes. If your account does not have sudo access yet, follow the guide on how to add a new user to sudoers on Ubuntu or run the commands from a root shell.
Upgrade any pending packages next so the new kernel lands on a current userland and DKMS base.
sudo apt upgradeInstall XanMod Prerequisites on Ubuntu
XanMod needs the usual APT transport and key-management tools, plus dkms if you expect external modules such as NVIDIA, VirtualBox, or VMware to rebuild against the new kernel.
sudo apt install ca-certificates curl dkms gnupg lsb-releaseAdd the XanMod GPG Key and Repository on Ubuntu
The curl command streams XanMod’s ASCII-armored signing key directly into gpg --dearmor, and the --yes flag makes reruns replace the existing keyring without stopping for an interactive prompt.
sudo install -m 0755 -d /etc/apt/keyrings
curl -fsSL https://dl.xanmod.org/archive.key | sudo gpg --dearmor --yes -o /etc/apt/keyrings/xanmod-archive-keyring.gpgThis short DEB822 file uses $(lsb_release -sc) to insert your Ubuntu codename automatically. The sudo tee portion writes the file with root privileges because a plain shell redirection would still run as your unprivileged user.
printf '%s\n' \
"Types: deb" \
"URIs: http://deb.xanmod.org" \
"Suites: $(lsb_release -sc)" \
"Components: main" \
"Signed-By: /etc/apt/keyrings/xanmod-archive-keyring.gpg" | sudo tee /etc/apt/sources.list.d/xanmod.sources > /dev/nullRefresh APT and Confirm XanMod Packages on Ubuntu
Refresh APT again so Ubuntu reads the new repository metadata, then confirm the MAIN package is visible before you choose a branch.
sudo apt updateapt-cache policy linux-xanmod-x64v3Relevant output includes:
linux-xanmod-x64v3:
Installed: (none)
Candidate: 6.19.10-xanmod1-0
Version table:
6.19.10-xanmod1-0 500
500 http://deb.xanmod.org resolute/main amd64 Packages
On Ubuntu 24.04, the final repository line ends in noble/main instead of resolute/main.
Detect Your CPU Level for XanMod on Ubuntu
Download XanMod’s psABI helper and make it executable in your current directory. The script checks whether your CPU matches the x86-64-v2 or x86-64-v3 package line.
curl -fsSLO https://dl.xanmod.org/check_x86-64_psabi.sh
chmod +x check_x86-64_psabi.shThe chmod +x step adds execute permission so you can run the downloaded script directly. After that, start the check:
./check_x86-64_psabi.shCPU supports x86-64-v3
If the output says x86-64-v3, use the v3 package. If it falls back to x86-64-v2, use the v2 package instead. XanMod’s current repository does not publish a linux-xanmod-x64v4 package, so even newer CPUs still use the x64v3 build.
Choose the XanMod Branch and Package on Ubuntu
MAIN is the default choice for most desktops. EDGE, LTS, and RT use the same repository but target different stability and latency trade-offs.
| Branch | Packages | Best For | Current line |
|---|---|---|---|
| MAIN | linux-xanmod-x64v2, linux-xanmod-x64v3 | Default desktop, gaming, and low-latency workstation use | 6.19.x stable mainline |
| EDGE | linux-xanmod-edge-x64v2, linux-xanmod-edge-x64v3 | Testing newer XanMod patches before they land in MAIN | 6.19.x fast-moving preview |
| LTS | linux-xanmod-lts-x64v1, linux-xanmod-lts-x64v2, linux-xanmod-lts-x64v3 | Longer-lived workstation installs, plus very old CPUs that still need x64v1 | 6.18.x long-term support |
| RT | linux-xanmod-rt-x64v2, linux-xanmod-rt-x64v3 | Audio, control, and other deterministic latency workloads | 6.18.x PREEMPT_RT |
Install the XanMod Package on Ubuntu
MAIN is the right starting point for most readers. If you want EDGE, LTS, or RT instead, replace only the package name with the matching entry from the table above.
sudo apt install linux-xanmod-x64v3If the psABI script reported x86-64-v2, install the v2 package instead:
sudo apt install linux-xanmod-x64v2Relevant output includes:
Installing: linux-xanmod-x64v3 Installing dependencies: linux-headers-6.19.10-x64v3-xanmod1 linux-image-6.19.10-x64v3-xanmod1 Summary: Upgrading: 0, Installing: 3, Removing: 0, Not Upgrading: 21
XanMod installs the versioned image and headers beside Ubuntu’s stock kernel. The project home page lists the current supported codenames, branch status, and release links if you want to inspect upstream changelogs or source trees directly on the XanMod website.
Reboot Ubuntu After XanMod Installation
Reboot once the package install finishes. On Ubuntu 26.04, the first reboot may still land on the stock 7.0 generic kernel because that branch currently sorts ahead of XanMod’s 6.19 packages in GRUB.
sudo rebootIf you no longer need the psABI helper afterward, remove it from your working directory:
rm check_x86-64_psabi.shVerify XanMod Kernel on Ubuntu
Verify the Running XanMod Kernel on Ubuntu
Check the active kernel first instead of assuming the reboot picked the new entry automatically.
uname -r6.19.10-x64v3-xanmod1
A XanMod boot shows the upstream kernel version, the CPU-level suffix, and the xanmod tag. If you still see a *-generic kernel on Ubuntu 26.04, use the GRUB fix in the troubleshooting section before you keep tuning the system.
Verify Matching XanMod Headers on Ubuntu
Kernel headers need to match the running XanMod image, especially when DKMS modules compile against the active kernel.
dpkg -l | grep linux-headers-$(uname -r)ii linux-headers-6.19.10-x64v3-xanmod1 6.19.10-x64v3-xanmod1-0~20260325.gef8a086 amd64 Linux kernel headers for 6.19.10-x64v3-xanmod1 on amd64
Install CPU Microcode for XanMod on Ubuntu
Install only the vendor package that matches your processor. Microcode updates load before the kernel and fix CPU errata that can affect stability, scheduling, and security.
Install Intel Microcode on Ubuntu
Use Intel’s microcode package if your system runs on Intel hardware:
sudo apt install intel-microcode iucode-toolInstall AMD Microcode on Ubuntu
Use AMD’s package instead on Ryzen, Threadripper, EPYC, or older AMD platforms:
sudo apt install amd64-microcodeReboot after a microcode update so the firmware change loads before XanMod starts.
Update or Remove XanMod Kernel on Ubuntu
Update XanMod Kernel on Ubuntu
XanMod updates through normal APT maintenance. The branch meta package pulls the newer versioned image and headers when upstream publishes a new build.
sudo apt update
sudo apt upgradeRemove XanMod Kernel on Ubuntu
Removal is safest when you split it into three parts: restore the generic GRUB default if you changed it, remove the installed XanMod packages, then remove the repository files.
If you switched Ubuntu 26.04 to a saved XanMod boot entry earlier, put GRUB back on the default first slot before you remove the kernel:
sudo sed -i 's/^GRUB_DEFAULT=.*/GRUB_DEFAULT=0/' /etc/default/grub
sudo update-grubList the installed XanMod packages so you can see the exact branch meta package and versioned image/header names on your system:
dpkg -l | grep xanmodii linux-headers-6.19.10-x64v3-xanmod1 6.19.10-x64v3-xanmod1-0~20260325.gef8a086 amd64 Linux kernel headers for 6.19.10-x64v3-xanmod1 on amd64 ii linux-image-6.19.10-x64v3-xanmod1 6.19.10-x64v3-xanmod1-0~20260325.gef8a086 amd64 Linux kernel, version 6.19.10-x64v3-xanmod1 ii linux-xanmod-x64v3 6.19.10-xanmod1-0 amd64 Complete XanMod Linux kernel and headers [6.19] [x86-64-v3]
If the running kernel is XanMod, linux-image-$(uname -r) and linux-headers-$(uname -r) match the versioned packages above. Remove those alongside the branch meta package you actually installed:
sudo apt remove --purge linux-xanmod-x64v3 linux-image-$(uname -r) linux-headers-$(uname -r)If Ubuntu is still running a generic kernel, do not rely on $(uname -r) there. Copy the exact XanMod image and header package names from the previous dpkg -l | grep xanmod output instead. If you installed EDGE, LTS, or RT, replace linux-xanmod-x64v3 with that branch’s meta package as well.
Avoid using apt autoremove as the primary XanMod removal command. During validation it cleaned unrelated old Ubuntu kernels before it removed the current XanMod image.
Remove the repository file and keyring only after the package cleanup, then refresh APT:
sudo rm /etc/apt/sources.list.d/xanmod.sources
sudo rm /etc/apt/keyrings/xanmod-archive-keyring.gpg
sudo apt updateReboot back into Ubuntu’s stock kernel after the XanMod packages are gone:
sudo rebootAfter the reboot, confirm the stock kernel is active. Ubuntu 24.04 will show its own *-generic version string, while the example below comes from Ubuntu 26.04.
uname -r7.0.0-10-generic
These two checks should return no output once the installed XanMod packages and repository metadata are gone:
dpkg -l | grep xanmod
apt-cache search ^linux-xanmodNo output
Troubleshoot XanMod Kernel on Ubuntu
Most XanMod issues on Ubuntu come down to Secure Boot, GRUB choosing the wrong entry, or DKMS modules rebuilding against the wrong kernel. Work through the checks below in that order before you start swapping branches.
Fix Secure Boot Problems with XanMod on Ubuntu
Secure Boot blocks XanMod on UEFI systems because the project does not ship Microsoft-signed kernels. Check the current firmware state first:
mokutil --sb-statePossible outputs include:
SecureBoot enabled SecureBoot disabled EFI variables are not supported on this system
If you see SecureBoot enabled, disable Secure Boot in your firmware settings before you try to boot XanMod again. If you see EFI variables are not supported on this system, the machine booted in legacy BIOS mode and Secure Boot is not the blocker.
Fix the Wrong Default Boot Entry for XanMod on Ubuntu
Ubuntu 26.04 currently ships a stock 7.0 generic kernel that sorts ahead of XanMod’s 6.19 MAIN branch, so GRUB_DEFAULT=0 can keep booting the generic entry even after XanMod installs cleanly.
grep '^GRUB_DEFAULT' /etc/default/grub
sudo grep menuentry /boot/grub/grub.cfg | grep xanmodIf GRUB_DEFAULT is still 0, switch GRUB to saved-entry mode and set the XanMod menu title as the default. Replace the kernel title in the example below with the XanMod title from your own grub.cfg output if it differs:
sudo sed -i 's/^GRUB_DEFAULT=.*/GRUB_DEFAULT=saved/' /etc/default/grub
sudo update-grub
sudo grub-set-default "Advanced options for Ubuntu>Ubuntu, with Linux 6.19.10-x64v3-xanmod1"
sudo rebootOn Ubuntu 26.04, that change is what moves the system from 7.0.0-10-generic to 6.19.10-x64v3-xanmod1 when the stock kernel keeps winning the default slot.
Fix XanMod CPU Detection Mismatches on Ubuntu
If the psABI helper picks a package line that looks wrong for your hardware, check the instruction-set flags directly.
grep -o 'avx2' /proc/cpuinfo | head -n1avx2
An avx2 hit means the CPU supports the x64v3 build. If that command returns no output, check for the x64v2 baseline instead:
grep -o 'sse4_2' /proc/cpuinfo | head -n1sse4_2
If sse4_2 appears, install the x64v2 package. If both checks return no output, the current MAIN, EDGE, and RT packages are not a fit and you should stay on Ubuntu’s stock kernel or test the LTS x64v1 branch on hardware old enough to need it.
Fix XanMod DKMS Module Build Failures on Ubuntu
DKMS errors mean an out-of-tree module did not rebuild against the new XanMod headers. Start with the registered module list, then rerun the autoinstall against the active kernel.
sudo dkms status
sudo dkms autoinstall -k $(uname -r)If the rebuild still fails, install the current driver branch again and inspect the DKMS build log. NVIDIA users should start with install NVIDIA drivers on Ubuntu so the driver stack matches the new kernel headers.
sudo cat /var/lib/dkms/*/build/make.logFix XanMod Repository GPG Errors on Ubuntu
If apt update reports a missing or invalid XanMod signature, reimport the keyring in place and then confirm the file is readable by APT.
curl -fsSL https://dl.xanmod.org/archive.key | sudo gpg --dearmor --yes -o /etc/apt/keyrings/xanmod-archive-keyring.gpg
ls -lh /etc/apt/keyrings/xanmod-archive-keyring.gpg
sudo apt updateRelevant output includes a readable keyring such as -rw-r--r-- on /etc/apt/keyrings/xanmod-archive-keyring.gpg. If the permissions look tighter than that, run sudo chmod 644 /etc/apt/keyrings/xanmod-archive-keyring.gpg and refresh APT again.
Recover from a Failed XanMod Boot on Ubuntu
If Ubuntu stops booting after a XanMod install, go back through GRUB’s Advanced options for Ubuntu menu and choose the previous generic kernel first. Once the system is stable again, remove the XanMod packages and read the previous boot log before you try another branch.
sudo journalctl -xb -1Look for kernel panics, storage-driver failures, GPU module errors, or other hardware initialization problems that stopped the XanMod boot early.
XanMod Kernel on Ubuntu FAQ
No. XanMod uses its own APT repository at deb.xanmod.org, not a Launchpad PPA. That means you add a normal repo file and keyring instead of using add-apt-repository.
XanMod’s current supported-codename list no longer includes jammy, so the documented Ubuntu path is limited to 26.04 and 24.04. The repository still exposes legacy jammy packages, but they are no longer part of XanMod’s official support list.
Ubuntu 26.04 currently ships a newer stock 7.0 generic kernel, while XanMod’s MAIN branch is on 6.19.x. With GRUB_DEFAULT=0, GRUB keeps the first generic entry. Switch GRUB to saved mode and set the XanMod menu entry as the default if you want XanMod to boot automatically.
Not by default. XanMod does not ship Microsoft-signed kernels, so Secure Boot blocks them on UEFI systems. If mokutil --sb-state reports SecureBoot enabled, disable Secure Boot or stay on Ubuntu’s stock or HWE kernel.
No. The current repository publishes x64v2 and x64v3 packages for MAIN, EDGE, and RT, plus x64v1 only on the LTS branch. Even if your CPU supports newer instructions, XanMod’s published desktop packages still top out at x64v3.
Conclusion
XanMod kernel is running on Ubuntu with the branch and CPU level that match your hardware, and the official repository now handles future updates through normal APT maintenance. If you would rather stay on Ubuntu’s supported kernel track, install HWE kernel on Ubuntu instead. If DKMS drivers still need attention, install NVIDIA drivers on Ubuntu next.
The repository does not contain linux-xanmod-x64v4.
Thanks for reporting this, kto. You’re absolutely right: the XanMod repository does not provide any
linux-xanmod-x64v4packages, and that reference was added by mistake.XanMod only ships v2 and v3 builds for the MAIN and EDGE branches, and v1, v2, and v3 for the LTS branch. The x86-64-v4 level is listed only as a CPU reference for AVX-512 systems and is noted upstream as offering no practical kernel benefit, so there is no v4 package.
The guide has been corrected to match the official XanMod packages. Thanks again for catching this.