Hardware broke after 4.0.4 moved you to linux-omarchy: make the stock linux kernel the default again
Read migrations/1789325478.sh at v4.0.4 (identical to /usr/share/omarchy/migrations/1789325478.sh here): it skips only T2 (linux-t2 package or -t2 in uname -r), deletes and re-appends BOOT_ORDER in /etc/default/limine, keeps stock linux on purpose, and exits early once /var/lib/omarchy/migrations/1789325478 exists. Confirmed in /usr/lib/limine/limine-common-functions load_config() that /etc/default/limine is loaded after /etc/limine-entry-tool.d/*.conf, so editing omarchy-defaults.conf (which also sets BOOT_ORDER) cannot win. /usr/bin/limine-update runs limine-install --no-efi-register then limine-mkinitcpio, and limine-entry-tool --tree exists per its --help. Issue 12087 has a reporter (Beelink SER9) whose reset loop was fixed by a BIOS update and who gives exactly this BOOT_ORDER plus sudo limine-update stopgap. Issue 12281 confirms T1 Macs were switched, with a root-caused CS4208 speaker regression in a comment. The tracker lists many 7.2.5-3 regressions that stock 7.2.3 does not show (touchpad 12181, backlight 12188, HDMI audio 12131 and 12628, suspend 12190 and 13196, freezes 12926 and 12371, Wi-Fi 13795 and 13849), so the symptom and cause hold. Defects: the fix calls 12087 a "beta report", which it is not (it is a 4.0.4 user comment), and step 3 points at another record without the commands. Issue 12145 shows the direct-boot entry keeps pointing at omarchy_linux.efi and that omarchy-setup-direct-boot picks a UKI with find | head -1, so its choice is unpredictable with two UKIs. The corrected fix gives the efibootmgr commands that script itself uses. Issue 12664 claims default_entry: 2 selects the stock kernel. Limine CONFIG.md says an index can name a directory, so the /+Omarchy directory is entry 1 and the first kernel is entry 2, and this workstation boots 7.2.5-3-omarchy under that template. That issue does not invalidate the fix. Not exercised: I did not edit /etc/default/limine, run limine-update or reboot. /boot is dmask=0077 and I did not use root, so /boot/limine.conf was not read.
Stock linux must stay installed and its DKMS modules built (dkms status) for this to work. A mistyped BOOT_ORDER only reorders entries, but deleting the KERNEL_CMDLINE line from /etc/default/limine removes root= from every UKI on the next rebuild and nothing boots.
Symptom
Since the Omarchy 4.0.4 update (which installed linux-omarchy 7.2.5-3 and made it the first Limine entry), something works only on the stock kernel: the machine resets before the LUKS prompt, freezes, loses Wi-Fi, touchpad, backlight, HDMI audio or suspend. Picking linux in the Limine menu at every boot fixes it until you forget.
Cause
Migration 1789325478.sh installs linux-omarchy and writes BOOT_ORDER="linux-omarchy, linux-omarchy-*, *, *fallback, Snapshots" to /etc/default/limine, which limine-entry-tool reads last and which overrides every drop-in. It deliberately keeps stock linux installed "so it remains available if the new one cannot boot". The upstream tracker has many hardware-specific regressions reported against linux-omarchy 7.2.5-3 that stock linux 7.2.3 does not show. Its exemption covers T2 Macs only (linux-t2 or a -t2 kernel), so T1 and older Macs were switched too (issue 12281). The migration exits early once /var/lib/omarchy/migrations/1789325478 exists, so it never rewrites BOOT_ORDER again.
Fix
**1. Put linux first in /etc/default/limine.** Editing /etc/limine-entry-tool.d/omarchy-defaults.conf does nothing here, because /etc/default/limine is read after every drop-in and overrides it.
sudoedit /etc/default/limine
Replace the BOOT_ORDER= line with:
BOOT_ORDER="linux, linux-omarchy, linux-omarchy-*, *, *fallback, Snapshots"
Leave the ESP_PATH and KERNEL_CMDLINE lines alone.
**2. Regenerate the Limine entries.**
sudo limine-update
sudo limine-entry-tool --tree # linux should now be listed first
**3. If Direct Boot is enabled, the firmware entry decides, not Limine.** Check for it:
efibootmgr | grep -E 'Omarchy([[:space:]]|$)'
If it is there and its path is not \EFI\Linux\omarchy_linux.efi, replace it. Do not rely on omarchy-setup-direct-boot for this, because with two kernels it picks whichever omarchy*.efi file find lists first. These are the same commands that script runs. Replace XXXX with the number from the line above:
sudo ls /boot/EFI/Linux/ # omarchy_linux.efi must be listed
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.efi'
**4. Keep linux-omarchy installed** so you can retest a later release from the menu. One reporter in issue 12087 (Beelink SER9) had the same reset loop fixed by a BIOS update alone, so check for a firmware update and retest. An Intel machine whose failure shows DMAR: faults may only need intel_iommu=off (see that record) rather than the stock kernel.
To return to the Omarchy kernel later, put linux-omarchy first again, rerun sudo limine-update, and point a Direct Boot entry at \EFI\Linux\omarchy_linux-omarchy.efi.
Verify
Reboot without touching the menu. uname -r prints the -arch version and the broken device works.
Sources
- https://github.com/omacom/omarchy/blob/v4.0.4/migrations/1789325478.sh
- https://github.com/omacom/omarchy/issues/12281
- https://github.com/omacom/omarchy/issues/12087
- https://gitlab.com/Zesko/limine-entry-tool
- https://github.com/omacom/omarchy/issues/12145
- https://github.com/omacom/omarchy/issues/12181
- https://github.com/omacom/omarchy/issues/12664
- https://github.com/limine-bootloader/limine/blob/trunk/CONFIG.md