Selecting linux-omarchy resets the machine back to Limine while the stock linux entry boots
#12087 read in full. It is open. The original Lenovo P1 Gen5 report is unresolved, the maintainer posted a 7.2.7rc1 kernel for testing, and the Beelink SER9 commenter traced the early hard reset to BIOS SER9T407 and fixed it by flashing SER9T409. The intermittency, the empty journal and pstore, the intact UKI hash and identical cmdlines, the three config differences and the BOOT_ORDER plus limine-update stopgap are all in that comment. On this workstation /etc/default/limine holds the BOOT_ORDER line migration 1789325478.sh writes, limine-common-functions loads that file last, limine-update runs limine-install then limine-mkinitcpio, and the migration's marker at /var/lib/omarchy/migrations/1789325478 stops it rewriting BOOT_ORDER later. /usr/share/omarchy/bin/omarchy-update-firmware installs fwupd if missing and calls sudo itself, so running it without sudo is right. The symptom is written as a quote but paraphrases the SER9 comment faithfully. The IOMMU suggestion is labelled as a try, which fits since the P1 Gen5 is Intel and unresolved. Not exercised: no boot, no firmware update.
A BIOS flash that is interrupted can brick the board. Use AC power and the vendor's procedure.
Symptom
"Since the 4.0.4 update made linux-omarchy the default, picking it in Limine reboots the machine within a couple of seconds. The Limine menu comes back every time and I never see the LUKS prompt. The regular linux entry boots fine." Sometimes it is intermittent: several reset cycles, then one attempt gets through and runs for days. journalctl --list-boots shows only the successful boots on the old kernel, and there is no pstore record.
Cause
There is no single root cause yet. On a Beelink SER9 (Ryzen AI 9 HX PRO 370) the reporter traced it to the platform firmware: BIOS SER9T407 reset the machine in very early boot on linux-omarchy 7.2.5-3, and flashing SER9T409 fixed it with nothing changed on the Linux side. The UKI hash, limine.conf and the module tree were all verified intact. The original Lenovo P1 Gen5 report is unresolved, and the maintainer asked affected users to test a 7.2.7rc1 kernel. The reporter noted config differences from Arch's kernel (CONFIG_RESET_ATTACK_MITIGATION=y, CONFIG_SECURITY_LOCKDOWN_LSM_EARLY=y) but could not tie them to the failure. On Intel machines, rule out the IOMMU default first (see linux-omarchy-intel-iommu-default-on-boot-failures).
Fix
## Boot the stock kernel and make it the default for now
The migration keeps linux installed so it stays available if the new kernel cannot boot. /etc/default/limine overrides every drop-in:
sudo sed -i 's/^BOOT_ORDER=.*/BOOT_ORDER="linux, linux-omarchy, linux-omarchy-*, *, *fallback, Snapshots"/' /etc/default/limine
sudo limine-update
This is reversible, and linux-omarchy stays installed and listed.
## Look for a firmware update
omarchy-update-firmware # wraps fwupd. Run it without sudo, it calls sudo itself
Many small-PC vendors are not on LVFS. If fwupd offers nothing, check the vendor's support page for a newer BIOS and flash it by the vendor's method.
## On Intel, try the IOMMU workaround once
At the Limine menu highlight linux-omarchy, press e, append intel_iommu=off, and boot with F10. If that boots, follow linux-omarchy-intel-iommu-default-on-boot-failures.
## Report with logs
If a failed attempt left anything behind, it is here (boot the stock kernel first):
journalctl --list-boots
journalctl -b -1 -k
uname -a
cat /proc/cmdline
Verify
uname -r shows the kernel you intended (-arch for stock, -omarchy for linux-omarchy). After a firmware update, select linux-omarchy across several cold boots and confirm none of them resets.