OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
omarchy-core high occasional DISPUTE

Stop booting the stock Arch kernel that sits beside linux-omarchy

omarchyomarchy-4limineukidirect-boot
CORRECTED An auditor found the fix wrong or incomplete and rewrote it. · checked against Omarchy omarchy 4.0.4-1 on 2026-10-05
AUDIT NOTE

Confirmed on this workstation: linux 7.2.3.arch1-3 and linux-omarchy 7.2.5-3 both installed, migration 1789325478.sh keeps linux and only rewrites BOOT_ORDER in /etc/default/limine, CUSTOM_UKI_NAME="omarchy" in /etc/limine-entry-tool.d/omarchy-defaults.conf, UKI path built as ${UKI_PREFIX}_${KERNEL_NAME}.efi in limine-mkinitcpio-install, omarchy-setup-direct-boot still uses find | head -1 on quattro, and the template still has default_entry: 2. The ALPM guard hook triggers only on Operation = Upgrade, so pacman -R linux is not blocked, and ntsync-autoload depends on NTSYNC-MODULE, which linux-omarchy also provides. #12145 (with a second-machine confirmation) and #13537 support the Direct Boot and accidental-boot paths. The default_entry part of the cause does not hold up: Limine's common/menu.c print_tree counts the expanded /+Omarchy directory as entry 1, so default_entry: 2 is the first kernel under it, which is linux-omarchy when BOOT_ORDER is applied. #12664 numbers only the kernel leaves and has no maintainer reply. This workstation, with both kernels and the same template, booted Omarchy.linux-omarchy per LoaderEntrySelected, though whether by default or by hand is not recorded. Cause rewritten to stop asserting that mechanism. Frequency lowered to occasional, because the two-kernel state is common but booting the stock kernel needs Direct Boot or a manual pick. The hardware regressions in the danger are real (#12097, #12550, #13795, #13849, #13959). The danger now also says to check DKMS modules before removing linux. Fix steps unchanged. Not exercised: no kernel was removed and no EFI entry was changed.

The cause above was rewritten on 2026-10-05 to match this note; the fix was corrected by the audit itself.
RISK

Removing linux removes your fallback kernel. Many linux-omarchy 7.2.5 regressions are reported on specific hardware where the stock kernel works, among them older MacBooks, some Wi-Fi chips (ath9k, mt7925e) and PoE devices. Boot linux-omarchy successfully on your machine and use it for a while before removing the stock one, and keep the Limine snapshot menu available. On NVIDIA or other DKMS systems, check that dkms status shows the module built for the -omarchy kernel before removing linux. Never remove the kernel you are currently running.

Symptom

uname -r shows a stock kernel such as 7.2.3-arch1-3 instead of 7.2.5-3-omarchy, days or weeks after the update that installed linux-omarchy and asked for a reboot. Nothing looks wrong: the migration is marked done and the Limine menu lists linux-omarchy first. With Direct Boot enabled, efibootmgr shows the Omarchy entry pointing at \EFI\LINUX\OMARCHY_LINUX.EFI. Fixes that shipped only in linux-omarchy never take effect, and one report traced btrfs corruption to an accidental boot of the stale stock kernel.

Cause

Two kernels are installed on most Omarchy 4 systems. Fresh 4.0.4 ISO installs get stock linux from archinstall's base package set (#13537). Migration 1789325478 installs linux-omarchy but deliberately leaves linux installed as a fallback, and only sets BOOT_ORDER="linux-omarchy, linux-omarchy-*, *, *fallback, Snapshots" in /etc/default/limine. limine-mkinitcpio builds one UKI per kernel package, named omarchy_<pkgname>.efi because /etc/limine-entry-tool.d/omarchy-defaults.conf sets CUSTOM_UKI_NAME="omarchy". So omarchy_linux.efi is the stock kernel and omarchy_linux-omarchy.efi is the Omarchy one.

The confirmed way to keep booting the stock kernel is Direct Boot. An EFI entry created before the migration still points at omarchy_linux.efi, because Direct Boot bypasses Limine and its BOOT_ORDER (#12145, reproduced on a second machine in its comments). omarchy-setup-direct-boot also picks the UKI with find ... -name "omarchy*.efi" | head -1, which is unpredictable once two files exist. Through Limine, the stock entry stays in the menu one selection away, and #13537 reports a machine that landed on it three weeks after install.

#12664 blames the template's default_entry: 2. Limine's menu.c counts the expanded /+Omarchy directory as entry 1, so entry 2 is the first kernel listed under it, which is linux-omarchy when BOOT_ORDER is applied. That index points somewhere else only if the menu is ordered differently, which this audit could not check on the reporter's machine. Confirmed on this workstation: both kernels installed, the template carries default_entry: 2, and the machine booted Omarchy.linux-omarchy.

Fix

Check what you are running and what is installed:


uname -r
pacman -Q linux linux-omarchy
sudo efibootmgr | grep -i omarchy

If you are on the stock kernel, reboot and pick linux-omarchy by hand in the Omarchy Bootloader menu (Direct Boot users: choose Limine from the firmware boot menu). Use it for a while. Once you are satisfied it works on your hardware, remove the stock kernel while running linux-omarchy. The package's ALPM hooks remove its Limine entry and UKI:


uname -r | grep -q -- '-omarchy$' && sudo pacman -R linux

If pacman refuses because something depends on linux (for example a prebuilt nvidia-open module package), stop and switch that package to its DKMS or linux-omarchy equivalent first.

With Direct Boot, re-point the EFI entry at the remaining UKI. The script removes the entry on the first run and creates a new one on the second:


omarchy-setup-direct-boot   # answer yes to: Disable direct boot
omarchy-setup-direct-boot   # answer yes to: Setup direct boot
sudo efibootmgr | grep -i omarchy   # expect ...OMARCHY_LINUX-OMARCHY.EFI

Plain Arch with no Omarchy kernel is not affected. Apple T2 Macs keep linux-t2 and are skipped by the migration on purpose.

Verify

After a reboot without touching the menu, uname -r ends in -omarchy, pacman -Q linux reports it is not installed, and on Direct Boot systems sudo efibootmgr -v | grep -i omarchy names OMARCHY_LINUX-OMARCHY.EFI.

Sources

still-booting-stock-linux-kernel-after-linux-omarchy