Desktop workloads that need lower input latency, faster I/O behavior, or better frame pacing often outgrow the stock Mint kernel. To install XanMod kernel on Linux Mint, set up the official repository, choose the CPU-matched package, and keep a clean rollback path so you can test performance gains safely.
Use XanMod’s official APT repository only on Linux Mint 22.x x86_64 systems. On Linux Mint 21.x, leave the XanMod source unconfigured: upstream no longer serves a Mint 21.x or Ubuntu 22.04 jammy suite, so the repository guard stops before APT receives a broken source file.
Install XanMod Kernel on Linux Mint
Before adding the repository, compare the common Mint kernel choices so you can decide whether XanMod fits your workload and stability expectations.
| Kernel Option | Primary Focus | Best For | Trade-offs |
|---|---|---|---|
| Mint Generic or HWE Kernel | Stability and supported hardware enablement | Daily systems, production desktops, users prioritizing Mint’s normal update path | Less aggressive tuning than third-party desktop kernels |
| XanMod Kernel | CPU-targeted performance and low latency | Gaming, multimedia production, high-performance workstations on Mint 22.x | Third-party source, Secure Boot caveat, CPU-level package choice, and unsupported Mint 21.x repository path |
| Liquorix Kernel | Desktop responsiveness and multimedia | Content creators, audio production, desktop users wanting smooth UI performance | Similar third-party risk with a simpler branch matrix |
| Zabbly Mainline Kernel | Newest stable upstream kernel behavior | Hardware enablement, regression testing, and Incus-heavy systems | Mainline behavior is less Mint-integrated than generic or HWE kernels |
The default Mint kernel prioritizes broad hardware support and conservative updates. XanMod is a desktop-focused custom kernel that leans harder into low latency, scheduler tuning, BBRv3 enabled by default, and CPU-targeted builds. Liquorix targets the same general desktop space with a simpler branch matrix, while Zabbly is a better fit when you need mainline kernel behavior rather than XanMod’s patch set.
XanMod’s Mint packages target x86_64 architecture (APT’s
amd64package architecture) and are not signed for the normal Secure Boot trust chain. Disable Secure Boot in firmware before continuing unless you already manage your own kernel-signing workflow, then confirm architecture support withuname -m. If the output isx86_64, your CPU architecture is compatible.
Confirm CPU architecture before continuing:
uname -mx86_64
Verify Secure Boot Status for XanMod
XanMod kernels are not signed with Microsoft’s UEFI keys, so Secure Boot firmware blocks them from loading. Before installing XanMod, check whether Secure Boot is currently enabled on your system:
mokutil --sb-statePossible output includes:
SecureBoot enabled SecureBoot disabled EFI variables are not supported on this system
If the output shows SecureBoot enabled, disable Secure Boot in your BIOS/UEFI settings before proceeding. On many systems you can enter firmware setup during reboot with F2, F10, Del, or Esc, then switch Secure Boot to disabled and save changes.
If your system reports EFI variables are not supported on this system, the current Linux session cannot query firmware state directly. Change Secure Boot in firmware, then rerun mokutil --sb-state after booting Linux and continue only when it reports SecureBoot disabled.
Import XanMod APT Repository
Update Linux Mint Before XanMod Installation
Before proceeding, update your system to ensure all packages are current and minimize potential conflicts during installation. First, refresh the package index:
sudo apt updateThese commands use
sudofor tasks that need root privileges. If your account is not configured for sudo access, add users to sudoers on Linux Mint first.
Next, upgrade any outdated packages:
sudo apt upgrade -yInstall XanMod Prerequisites
Install the packages used in the next steps. curl downloads the signing key and CPU detection script, gpg converts the ASCII-armored key into a binary APT keyring, and dkms rebuilds third-party modules such as NVIDIA after each kernel change:
sudo apt install curl gpg ca-certificates dkms -yAdd XanMod GPG Key
Download the XanMod GPG key as an unprivileged user, convert it locally, then install the binary keyring where the repository file can reference it:
curl -fsSLo xanmod-archive.key https://dl.xanmod.org/archive.key
gpg --dearmor --yes -o xanmod-archive-keyring.gpg xanmod-archive.key
sudo install -m 0644 xanmod-archive-keyring.gpg /usr/share/keyrings/xanmod-archive-keyring.gpg
rm -f xanmod-archive.key xanmod-archive-keyring.gpgThe curl command fetches the ASCII-armored key, gpg --dearmor converts it to APT’s binary keyring format, and sudo install places the final file with readable permissions for APT.
Add XanMod APT Repository
Add the XanMod repository with a guarded DEB822 .sources file. XanMod does not publish a Launchpad PPA for Linux Mint, so use the official APT repository instead. This repository is a Mint-specific exception to the usual Ubuntu-base codename pattern because it serves Mint 22.x suite names directly: wilma, xia, zara, and zena.
Write the XanMod Repository File for Linux Mint 22.x
. /etc/lsb-release
mint_codename="${DISTRIB_CODENAME:-}"
arch="$(dpkg --print-architecture)"
case "${mint_codename}:${arch}" in
wilma:amd64|xia:amd64|zara:amd64|zena:amd64)
printf '%s\n' \
'Types: deb' \
'URIs: https://deb.xanmod.org' \
"Suites: ${mint_codename}" \
'Components: main' \
"Architectures: ${arch}" \
'Signed-By: /usr/share/keyrings/xanmod-archive-keyring.gpg' | sudo tee /etc/apt/sources.list.d/xanmod.sources > /dev/null
;;
*)
printf 'This XanMod repository setup supports Linux Mint 22.x amd64 only. No source file was written.\n' >&2
false
;;
esacThe guard checks both the Mint codename and APT architecture before it writes the source file. sudo tee handles the root-owned write step, because plain > redirection would still run in your unprivileged shell.
Use this support matrix before writing or repairing a XanMod source file:
| Linux Mint Series | Mint Codenames | XanMod Suite | Result |
|---|---|---|---|
| Linux Mint 22.x | Wilma, Xia, Zara, Zena | wilma, xia, zara, zena | Supported on amd64 |
| Linux Mint 21.x | Vanessa, Vera, Victoria, Virginia | No Mint 21.x or jammy suite | Unsupported by XanMod APT metadata |
Verify the repository file before refreshing APT:
cat /etc/apt/sources.list.d/xanmod.sourcesThe output displays the DEB822 repository configuration. On Linux Mint 22.3 Zena, it should look like this:
Types: deb URIs: https://deb.xanmod.org Suites: zena Components: main Architectures: amd64 Signed-By: /usr/share/keyrings/xanmod-archive-keyring.gpg
Refresh APT Cache After XanMod Import
Refresh the APT package index to include the XanMod repository:
sudo apt updateConfirm APT can see the XanMod metapackages from the Mint suite before installing a kernel:
apt-cache policy linux-xanmod-x64v2 linux-xanmod-lts-x64v1Continue when each package shows a real candidate from https://deb.xanmod.org and a source line such as zena/main amd64 Packages. If the candidate is (none) or APT reports a 404, use the repository troubleshooting section before trying to install a kernel.
Select and Install XanMod Kernel
Download XanMod CPU Detection Script
Download the XanMod CPU detection script to identify the correct kernel package for your processor:
curl -fsSLO https://dl.xanmod.org/check_x86-64_psabi.sh
chmod +x check_x86-64_psabi.shThe +x flag adds execute permission so the downloaded script can run. The chmod command in Linux with examples guide breaks down that permission change in more detail.
XanMod splits its Mint kernel packages by x86-64 psABI level instead of CPU brand name. The v1 package is the baseline fallback, v2 requires SSE4.2-era instruction support, and v3 adds AVX/AVX2-era support. The script checks the actual flags on your processor, so use the script result instead of guessing from model year or marketing name.
Run the script to determine the suitable x86-64 level:
./check_x86-64_psabi.shThe output indicates the supported x86-64 version:
CPU supports x86-64-v2
Your output may show x86-64-v1, x86-64-v2, x86-64-v3, or x86-64-v4 depending on supported instruction sets. If the script reports v1, use the LTS v1 package because the current MAIN, EDGE, and RT metapackages start at v2. If the script reports v4, install the v3 MAIN package or the v3 LTS package, because the performance-oriented metapackages stop at v3.
Once you have determined your CPU version, clean up the detection script:
rm check_x86-64_psabi.shInstall XanMod Kernel via APT
Install the package that matches the script output. Use the LTS v1 package when the script reports x86-64-v1:
sudo apt install -y linux-xanmod-lts-x64v1Use the v2 package when the script reports x86-64-v2:
sudo apt install -y linux-xanmod-x64v2Use the v3 package when the script reports x86-64-v3 or x86-64-v4:
sudo apt install -y linux-xanmod-x64v3On Linux Mint 22.x, MAIN and EDGE packages start at x86-64-v2, while LTS also carries x86-64-v1. If you want a longer support window, or your CPU only qualifies for x86-64-v1, install
linux-xanmod-lts-x64v1,linux-xanmod-lts-x64v2, orlinux-xanmod-lts-x64v3instead.
The official XanMod website explains the branch differences and CPU targets in more detail.
XanMod Branch Overview
XanMod offers multiple branch metapackages for different workloads. Treat the metapackage name as the durable choice and the exact kernel version as moving APT output. MAIN, EDGE, and RT provide v2 and v3 builds, while the LTS branch also carries a v1 package for older 64-bit CPUs.
XanMod enables Google’s BBRv3 TCP congestion control by default. In Linux, the active algorithm appears as bbr in sysctl output.
XanMod MAIN Branch
linux-xanmod-x64v2: Compatible with CPUs that pass the script’s x86-64-v2 check, including SSSE3, SSE4.1, SSE4.2, POPCNT, LAHF/SAHF, and CMPXCHG16B support. Use this package when the script reports v2 or when you want a conservative MAIN package on a newer v3 or v4 CPU.linux-xanmod-x64v3: Optimized for CPUs that pass the script’s x86-64-v3 check. This level adds AVX, AVX2, BMI1, BMI2, F16C, FMA, ABM, MOVBE, and XSAVE support for newer desktop and workstation processors.
XanMod EDGE Branch
linux-xanmod-edge-x64v2: EDGE branch for CPUs that pass x86-64-v2. Use it only when you specifically want newer upstream behavior before it settles in MAIN.linux-xanmod-edge-x64v3: EDGE branch for CPUs that pass x86-64-v3. It favors newer upstream behavior over the steadier MAIN or LTS branches.
XanMod LTS Branch
linux-xanmod-lts-x64v1: LTS branch for CPUs that only pass the baseline x86-64-v1 check. Use this package when the script reports v1 or when the CPU lacks SSE4.2 support.linux-xanmod-lts-x64v2: LTS branch for CPUs that pass x86-64-v2. Use it when you want the longer-support branch without requiring v3 instruction support.linux-xanmod-lts-x64v3: LTS branch for CPUs that pass x86-64-v3. Use it when you want the longer-support branch on newer processors.
XanMod RT Branch
linux-xanmod-rt-x64v2: Real-time branch for CPUs that pass x86-64-v2. Use it for PREEMPT_RT testing, audio workloads, or latency-sensitive systems where you can verify hardware and driver behavior.linux-xanmod-rt-x64v3: Real-time branch for CPUs that pass x86-64-v3. Use it when PREEMPT_RT behavior matters more than the steadier MAIN or LTS branches.
Selecting the correct version for your CPU architecture prevents illegal-instruction failures and avoids leaving performance on the table. On systems that support SSE4.2, the v2 package is the safer fallback when you are unsure. On older 64-bit systems without SSE4.2 support, use linux-xanmod-lts-x64v1 instead.
Reboot System After XanMod Installation
Reboot to activate the newly installed kernel:
sudo rebootDo not assume package installation alone proves the kernel is active. If Mint still comes up on the generic kernel after reboot, use the troubleshooting section before you assume the install failed.
Verify XanMod Kernel Installation
After reboot, confirm three things before you move on: the running kernel has the xanmod suffix, the matching headers are installed for that kernel, and the active congestion-control algorithm is bbr.
Check XanMod Kernel Version
Verify the active kernel version to confirm XanMod is running:
uname -rExample output includes the xanmod suffix and CPU architecture variant:
7.0.11-x64v2-xanmod1
The version string shows the upstream kernel series, the CPU optimization level, and the XanMod release suffix. If the output still ends in generic, Mint is still booting the stock kernel.
Confirm Matching XanMod Headers
DKMS rebuilds and out-of-tree driver installs depend on the header package for the kernel you are actually running. Verify the active header tree before you move on:
dpkg -l | grep "linux-headers-$(uname -r)"The grep filter limits the package list to the header package that matches the running kernel. The grep command in Linux with examples guide explains the text-filtering pattern used in checks like this one.
Relevant output includes:
ii linux-headers-7.0.11-x64v2-xanmod1 7.0.11-x64v2-xanmod1-0~20260602.gac9e28e amd64 Linux kernel headers for 7.0.11-x64v2-xanmod1 on amd64
If this command returns nothing, reboot may have left you on the generic kernel, or the header package did not install cleanly.
Check XanMod BBR Setting
XanMod enables BBR by default, and Linux reports the active algorithm as bbr in sysctl output:
sysctl net.ipv4.tcp_congestion_controlnet.ipv4.tcp_congestion_control = bbr
If the stock Mint kernel already meets your hardware needs and you only want the network-side tuning, enable BBR on Linux Mint instead of replacing the kernel.
Install Intel or AMD Microcode for XanMod
Microcode updates fix low-level CPU errata and security issues that the kernel depends on. XanMod uses the same Mint microcode packages as the generic kernel, so install the package that matches your CPU vendor if it is not already present.
Install Intel Microcode for XanMod
Intel processor users should install microcode updates from the Mint and Ubuntu base repositories:
sudo apt install -y intel-microcode iucode-toolIf APT reports the package is already the newest version, your Intel microcode is already in place. Reboot after any change so the updated firmware loads with the next kernel start.
Install AMD Microcode for XanMod
AMD processor users should install microcode updates from the Mint and Ubuntu base repositories:
sudo apt install -y amd64-microcodeIf APT reports the package is already the newest version, your AMD microcode is already installed. Reboot after any change so the updated firmware loads with the next kernel start.
Manage XanMod Kernel
APT updates the installed XanMod metapackage the same way it updates any other repository package. Reboot after each kernel upgrade, then confirm the running kernel and matching headers again.
Update XanMod Kernel
XanMod updates are delivered through APT. First, identify which XanMod metapackage is installed on your system:
dpkg --list | grep '^ii linux-xanmod'Example output:
ii linux-xanmod-x64v2 7.0.11-xanmod1-0 amd64 Complete XanMod Linux kernel and headers [7.0] [x86-64-v2]
Refresh package metadata, then upgrade only the installed XanMod metapackage (replace the package name if you use LTS, EDGE, RT, or v3):
sudo apt update
sudo apt install --only-upgrade -y linux-xanmod-x64v2After a kernel update, reboot to activate the new version. Then rerun uname -r and dpkg -l | grep "linux-headers-$(uname -r)" from the verification section so the running kernel and header tree stay aligned.
Troubleshoot XanMod Kernel Issues
These checks cover the most common Secure Boot, boot-order, repository, CPU-detection, and DKMS problems after a XanMod install on Linux Mint.
Secure Boot Prevents XanMod Kernel From Booting
If your system shows “Validation failed: Security Policy Violation” or fails to boot after installing XanMod, Secure Boot is still enabled. XanMod kernels are not signed with Microsoft’s UEFI keys, so Secure Boot firmware blocks them. Check your current Secure Boot status:
mokutil --sb-stateCommon output examples:
SecureBoot enabled SecureBoot disabled EFI variables are not supported on this system
If it reports SecureBoot enabled, disable Secure Boot in firmware and rerun the command. If it reports EFI variables are not supported on this system, the running Linux session cannot query firmware state directly.
Linux Mint Still Boots the Default Kernel After XanMod Installation
If uname -r still shows a generic Mint kernel after installation, the packages installed correctly but GRUB is still preferring another entry. For a menu-based way to inspect saved boot preferences, install GRUB Customizer on Linux Mint. List the installed kernels next:
dpkg --list | grep linux-imageYou should see both XanMod and generic kernels installed:
ii linux-image-7.0.11-x64v2-xanmod1 7.0.11-x64v2-xanmod1-0~20260602.gac9e28e amd64 Linux kernel, version 7.0.11-x64v2-xanmod1 ii linux-image-6.17.0-22-generic 6.17.0-22.22~24.04.1 amd64 Signed kernel image generic ii linux-image-6.17.0-19-generic 6.17.0-19.19~24.04.2 amd64 Signed kernel image generic
Then verify GRUB’s default boot entry:
grep '^GRUB_DEFAULT=' /etc/default/grubCommon output on systems using the first generated GRUB menu entry:
GRUB_DEFAULT=0
When this value is 0, Mint often boots the first generated menu entry after sudo update-grub, but boot order can still depend on the generated GRUB menu and saved-entry settings. If you changed it to saved or another manual value, Mint can keep returning to a remembered generic entry until you reset that preference.
sudo update-grubLook for output confirming XanMod entries were detected:
Found linux image: /boot/vmlinuz-7.0.11-x64v2-xanmod1 Found initrd image: /boot/initrd.img-7.0.11-x64v2-xanmod1 Found linux image: /boot/vmlinuz-6.17.0-22-generic done
Reboot after rebuilding GRUB and verify XanMod loads. If Mint still prefers the generic kernel, choose the XanMod entry once from “Advanced options for Linux Mint” or clear the remembered boot choice with GRUB Customizer.
XanMod Repository Returns 404 Error
If sudo apt update shows a 404 error for the XanMod repository, the source file may contain an unsupported suite. A supported Linux Mint 22.x source should use wilma, xia, zara, or zena. Mint 21.x suites and jammy do not resolve in the current XanMod repository.
Find any active XanMod source entries before deleting files:
grep -RIn "deb.xanmod.org" /etc/apt/sources.list /etc/apt/sources.list.d 2>/dev/nullAn unsupported Mint 21.x or old Ubuntu-base source can show a line like this:
/etc/apt/sources.list.d/xanmod.sources:3:Suites: jammy
On Linux Mint 22.x, remove the stale source and recreate it with the guarded command from the installation section. On Linux Mint 21.x, remove the source and stay on Mint’s generic or HWE kernel, or use another currently supported kernel source. If you intentionally use XanMod’s repository for another package, inspect the grep output and remove only the stale kernel source entry.
sudo rm -f /etc/apt/sources.list.d/xanmod.sources /etc/apt/sources.list.d/xanmod-release.list
sudo apt updateAfter cleanup on Mint 22.x, repeat the repository setup and confirm apt-cache policy linux-xanmod-x64v2 shows a candidate from your Mint 22.x suite.
XanMod CPU Detection Script Shows the Wrong Version
If the XanMod detection script reports a version that seems incorrect for your CPU, verify instruction set support manually. Check for AVX2 support (required for x64v3):
grep -o 'avx2' /proc/cpuinfo | head -n1Expected output when AVX2 is present:
avx2
If the output shows “avx2,” your CPU supports x64v3. If empty, your CPU only supports x64v2. You can also check SSE4.2 support (required for x64v2):
grep -o 'sse4_2' /proc/cpuinfo | head -n1Expected output when SSE4.2 is present:
sse4_2
When uncertain on an SSE4.2-capable system, install the x64v2 package as the safer fallback. Use x64v3 only when the detection script reports x86-64-v3 or x86-64-v4 and you specifically want the higher CPU baseline. If the CPU lacks SSE4.2 support, use linux-xanmod-lts-x64v1 instead; XanMod’s performance-oriented metapackages stop at v3 even when the script reports v4.
XanMod DKMS Module Build Failures
If DKMS errors appear during installation or after reboot, third-party modules such as NVIDIA or VirtualBox did not rebuild against the active XanMod kernel. Start by checking the current DKMS status:
sudo dkms statusIf no third-party modules are installed, this command may return nothing. When drivers are present, look for entries tied to the running XanMod kernel and make sure they say installed instead of error.
sudo dkms autoinstall -k $(uname -r)Relevant output includes:
* dkms: running auto installation service for kernel 7.0.11-x64v2-xanmod1 * dkms: autoinstall for kernel 7.0.11-x64v2-xanmod1 ...done.
If the rebuild still fails, locate the module build logs and inspect the matching make.log file:
sudo find /var/lib/dkms -path '*/build/make.log' -printFor NVIDIA-specific rebuild problems, install NVIDIA drivers on Linux Mint with driver packages that match Mint’s current kernels.
XanMod Repository GPG Key Errors
If apt update shows “GPG error: The following signatures couldn’t be verified,” the XanMod GPG key is missing or corrupted. Re-import the key:
curl -fsSLo xanmod-archive.key https://dl.xanmod.org/archive.key
gpg --dearmor --yes -o xanmod-archive-keyring.gpg xanmod-archive.key
sudo install -m 0644 xanmod-archive-keyring.gpg /usr/share/keyrings/xanmod-archive-keyring.gpg
rm -f xanmod-archive.key xanmod-archive-keyring.gpgNext, verify the keyring file exists and has correct permissions:
ls -l /usr/share/keyrings/xanmod-archive-keyring.gpgThe keyring file should be readable by all users. If permissions are wrong, fix them:
sudo chmod 644 /usr/share/keyrings/xanmod-archive-keyring.gpgRun sudo apt update again to verify the error resolves.
System Fails to Boot After XanMod Kernel Install
If your system fails to boot after installing XanMod, boot the previous working kernel from GRUB. When the system starts, hold Shift (BIOS) or Esc (UEFI) to show the GRUB menu. Select “Advanced options for Linux Mint,” then choose your previous generic Mint kernel. Once booted, remove the problematic XanMod kernel and investigate the issue before trying again.
Check system logs for boot failures:
sudo journalctl -xb -1This log shows the previous boot attempt. Look for kernel panics, driver failures, Secure Boot policy blocks, or early hardware initialization errors that prevented XanMod from finishing startup.
Remove XanMod Kernel
To remove XanMod and return to Mint’s stock kernel, purge the installed XanMod image, headers, and metapackage, then remove the repository files. The generic Mint kernel metapackage stays installed, so the next reboot falls back to the standard kernel.
Start by listing the installed XanMod packages so you can confirm exactly what APT is about to remove:
dpkg --list | grep -E '^ii linux-(image|headers)-.*xanmod|^ii linux-xanmod'The output lists XanMod kernel images and headers. For example:
ii linux-headers-7.0.11-x64v2-xanmod1 7.0.11-x64v2-xanmod1-0~20260602.gac9e28e amd64 Linux kernel headers for 7.0.11-x64v2-xanmod1 on amd64 ii linux-image-7.0.11-x64v2-xanmod1 7.0.11-x64v2-xanmod1-0~20260602.gac9e28e amd64 Linux kernel, version 7.0.11-x64v2-xanmod1 ii linux-xanmod-x64v2 7.0.11-xanmod1-0 amd64 Complete XanMod Linux kernel and headers [7.0] [x86-64-v2]
Now purge the installed XanMod packages:
mapfile -t xanmod_packages < <(dpkg-query -W -f='${binary:Package}\n' 'linux-*xanmod*' 2>/dev/null | grep -E '^linux-(headers|image)-.*xanmod|^linux-xanmod' || true)
if ((${#xanmod_packages[@]} == 0)); then
printf 'No installed XanMod kernel packages were found.\n' >&2
else
printf 'Purging these XanMod packages:\n'
printf '%s\n' "${xanmod_packages[@]}"
sudo apt purge "${xanmod_packages[@]}"
fiThis guarded purge prints the selected XanMod packages before APT asks for confirmation. It removes the XanMod image, matching headers, and metapackage without asking apt autoremove to decide which older fallback kernels to delete.
After the package purge, remove the repository definition and refresh APT. Remove the keyrings only when no remaining XanMod source entry needs them:
sudo rm -f /etc/apt/sources.list.d/xanmod.sources /etc/apt/sources.list.d/xanmod-release.list
sudo apt update
if grep -RIn "deb.xanmod.org" /etc/apt/sources.list /etc/apt/sources.list.d 2>/dev/null; then
printf 'Keep the XanMod keyring because another XanMod source is still configured.\n' >&2
else
sudo rm -f /usr/share/keyrings/xanmod-archive-keyring.gpg /etc/apt/keyrings/xanmod-archive-keyring.gpg
fiAfter removal, reboot to load the default Linux Mint kernel:
sudo rebootUpon restarting, verify that your system has reverted to the standard kernel:
uname -rThe output should show a default Linux Mint kernel version without the xanmod suffix:
6.17.0-22-generic
Conclusion
XanMod can now run on Linux Mint 22.x from the official repository while Mint’s generic kernel remains available as the rollback path. Keep the source file limited to supported Mint 22.x suites, recheck the running xanmod suffix after each reboot, and remove the repository cleanly if the kernel does not fit your hardware or stability needs.
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>