Remove the unused stock linux kernel that sits beside linux-omarchy (and whose entry can get booted by mistake)
Issue 13537 supports the fresh-install path. Its archinstall log line lists 'linux', it says omarchy-base.packages has no plain linux, and it says the report was filed by an agent (glm-5.3-flash via pi), so the record is right to call the Btrfs attribution unconfirmed. install/omarchy-other.packages on quattro names linux-omarchy and linux-omarchy-headers. The limine-snapper-sync README line 641 has the kernel-switching warning. Confirmed here: 00-omarchy-update-guard.hook triggers only on Operation = Upgrade, so pacman -R passes. The 60/90 remove hooks call limine-entry-tool --remove-all <kernel>, which removes the entry and its files. linux-omarchy provides KSMBD-MODULE, NTSYNC-MODULE, VIRTUALBOX-GUEST-MODULES and WIREGUARD-MODULE. Three defects in the fix. First, on a stock 4.0.4 machine pacman -Qi linux shows Required By: ntsync-autoload (it depends on NTSYNC-MODULE). The record tells the reader that this field shows prebuilt module packages that must be dealt with first, so a reader would stop or remove the wrong thing. linux-omarchy satisfies that dependency. Second, pacman -R linux linux-headers aborts with 'target not found' and removes nothing when linux-headers is absent. Third, it ignores Direct Boot. Issue 12145 shows the firmware entry pointing at \EFI\Linux\omarchy_linux.efi, the stock kernel's UKI, and the remove hook deletes that file. On such a machine the firmware entry then points at nothing, and the danger does not mention it. Not exercised: nothing was removed here, because this workstation still needs both kernels for other records.
Omarchy 4 has no fallback initramfs entry. After removal, the only bootable kernel is linux-omarchy plus older snapshot entries, so a future linux-omarchy regression on your hardware needs a snapshot or a live USB to recover. Keep an Omarchy or Arch USB stick. Never remove the kernel you are currently running. With Direct Boot enabled, removing linux deletes omarchy_linux.efi, so a firmware entry still pointing at it has nothing to boot. Repoint it before removing the kernel.
Symptom
The machine runs linux-omarchy, yet pacman -Q linux shows the stock kernel still installed and the Limine menu still lists a linux entry. Fresh 4.0.4 installs have it too. One reporter booted it by accident three weeks after installing, on a kernel version they had never run, and blamed it for a Btrfs failure. Others just see the ESP filling and kernel updates taking twice as long, since every update rebuilds two UKIs and two sets of DKMS modules.
Cause
Two paths leave stock linux in place. The upgrade migration 1789325478.sh keeps it on purpose as an escape hatch. Fresh installs get it from the archinstall base package set ('linux' appears in the installer's package list in /var/log/archinstall/install.log per issue 13537), even though Omarchy's own package lists name linux-omarchy. limine-entry-tool creates an entry for every installed kernel, so a never-updated-by-use kernel stays one keypress away. The Btrfs corruption attribution in issue 13537 was made by an agent-filed report and is not confirmed. limine-snapper-sync's own documentation does warn that switching often between kernel versions raises the risk of filesystem breakage.
Fix
**1. Check it is safe.** All of these must hold:
uname -r # must end in -omarchy
pacman -Qi linux | grep 'Required By' # see below
dkms status # DKMS modules built for the -omarchy kernel
pacman -Q linux-t2 2>/dev/null # T2 Macs use linux-t2: stop here if present
efibootmgr | grep -E 'Omarchy([[:space:]]|$)' # Direct Boot entry, see step 2
ntsync-autoload in Required By is expected on Omarchy 4. It depends on NTSYNC-MODULE, which linux-omarchy also provides, so it does not block removal. Any other package listed there, such as nvidia-open, is a prebuilt module package built for stock linux only: switch it to its DKMS variant first (see the prebuilt nvidia-open record). If this machine needed stock linux because of a linux-omarchy regression, keep it.
**2. If Direct Boot is enabled, point it away from the stock UKI first.** Removing linux deletes /boot/EFI/Linux/omarchy_linux.efi, and a Direct Boot entry may point at exactly that file. If the efibootmgr line above shows \EFI\Linux\omarchy_linux.efi (case may differ), replace the entry. XXXX is its number and the disk and partition come from findmnt:
findmnt -no SOURCE /boot # e.g. /dev/nvme0n1p1 is disk /dev/nvme0n1, partition 1
sudo efibootmgr --bootnum XXXX --delete-bootnum
sudo efibootmgr --create --disk /dev/nvme0n1 --part 1 --label Omarchy --loader '\EFI\Linux\omarchy_linux-omarchy.efi'
**3. Remove the stock kernel and, if installed, its headers.** pacman -R is not blocked by Omarchy's guard, which only fires on upgrade transactions. pacman -R aborts on a package that is not installed, so check the headers first:
pacman -Q linux-headers # if this says 'not found', drop it from the next line
sudo pacman -R linux linux-headers
The 60-limine-mkinitcpio-remove-pre and 90-limine-mkinitcpio-remove-post hooks remove its Limine entry and its UKI. If pacman refuses because another package requires linux, read the package it names before going further. linux-omarchy provides NTSYNC-MODULE, WIREGUARD-MODULE, KSMBD-MODULE and VIRTUALBOX-GUEST-MODULES, which satisfy packages depending on those.
**4. Check the result.**
sudo limine-entry-tool --tree
sudo ls /boot/EFI/Linux/
df -h /boot
efibootmgr | grep -E 'Omarchy([[:space:]]|$)' # must not name omarchy_linux.efi
Verify
pacman -Q linux reports it is not installed, the Limine menu lists only linux-omarchy (plus snapshots), and a reboot lands in uname -r ending in -omarchy.