OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
boot-kernel critical rare DISPUTE

Old CPU without AVX2: kernel update leaves the machine unbootable ('does not support all of the following CPU features')

omarchylimineukiold-hardwarelaptop
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

#11526 supports the error text, the reporter's jump from 1.29.0-1 to 1.38.0-1.1 and the x86-64-baseline rebuild. This machine has limine-mkinitcpio-hook 1.38.0-1.1, limine-snapper-sync 1.31.0-1.1 and kernel-modules-hook 0.1.7-3. /usr/share/libalpm/scripts/limine-mkinitcpio-install line 131 prints the quoted 'failed to get kernel cmdline' error, and 90-mkinitcpio-install.hook is PostTransaction, so the cause's reasoning about the fixing transaction holds. The cause's specifics are wrong in two places. The packaged CHANGELOG.md dates 1.29.0, the GraalVM native-image switch, to 2026-01-30 and not February. The corrected cause and the earlier audit note also assert that every build from 1.29 to 1.37 was affected. The reporter never ran those builds, and the upstream changelog for 1.29.1 (2026-02-05) already lists 'Adjust GraalVM native-image build flags for different x86_64 CPUs'. So only 1.29.0-1 is confirmed affected, and the cause is rewritten to say so. The fix and verify commands are correct and kept: readelf is in binutils 2.47-4, and pacman -S without -u is not blocked by the ALPM guard. Not exercised: no pre-AVX2 CPU was available.

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

Rebooting after an update that printed the CPU-features error starts the old UKI against a module tree that may no longer exist. Rebuild first. Omarchy also ships kernel-modules-hook, which restores the running kernel's modules after an upgrade. That may soften this case, but it was not exercised.

Symptom

On an older or low-end CPU (for example a Celeron N4000), a kernel update prints, among hundreds of lines:


The current machine does not support all of the following CPU features that are
required by the image: [CX8, CMOV, FXSR, MMX, SSE, SSE2, SSE3, SSSE3, SSE4_1,
SSE4_2, POPCNT, LZCNT, AVX, AVX2, BMI1, BMI2, FMA, F16C].
Please rebuild the executable with an appropriate setting of the -march option.
ERROR: failed to get kernel cmdline for 'linux'.

The update reports success. After a reboot the system breaks because the old kernel's modules are gone. snapper-cleanup.service may also fail daily.

Cause

From limine-mkinitcpio-hook 1.29.0, /usr/lib/limine/limine-entry-tool is a GraalVM native executable instead of a JVM program (upstream changelog, 1.29.0, 2026-01-30). The reporter's 1.29.0-1 build required AVX2 and refused to start on an x86-64-v2 CPU. 90-mkinitcpio-install.hook runs limine-mkinitcpio-install, which calls the tool to fetch the command line, fails with failed to get kernel cmdline, and leaves the UKI unrebuilt. A failing PostTransaction hook does not abort pacman, which had already replaced the kernel and removed the old modules. limine-mkinitcpio-hook 1.38.0-1.1 and limine-snapper-sync 1.31.0-1.1 are built at x86-64-baseline and run on such CPUs. Which builds between those two were affected is not established. The reporter went straight from 1.29.0-1 to 1.38.0-1.1, and the upstream changelog for 1.29.1 (2026-02-05) already lists "Adjust GraalVM native-image build flags for different x86_64 CPUs". The issue describes the fixing update as a trap. Because the hook runs after every package in the transaction is unpacked, a transaction that brings 1.38.0-1.1 should run the fixed binary, so the danger lies in kernel updates made while an affected build was installed. The report comes from Omarchy 3.8.5. Omarchy 4 ships kernel-modules-hook, which keeps the old kernel's modules.

Fix

## If you are still booted, do not reboot yet


pacman -Q limine-mkinitcpio-hook limine-snapper-sync
readelf -n /usr/lib/limine/limine-entry-tool | grep ISA     # want: x86-64-baseline
/usr/lib/limine/limine-entry-tool --version

If the fixed version is installed, rebuild the UKI before rebooting:


sudo limine-mkinitcpio

If it is not installed yet, run omarchy update -y to bring it in, then run sudo limine-mkinitcpio and check that it completes without the CPU-features error.

## If you already rebooted into a broken system

Boot the Omarchy ISO, unlock and mount the install as in chroot-recovery-btrfs-missing-subvol, then inside the chroot:


pacman -Q limine-mkinitcpio-hook        # 1.38.0-1.1 or later is fixed
# only if it is older:
pacman -S limine-mkinitcpio-hook limine-snapper-sync    # no -y: the database was synced by the update
limine-mkinitcpio

Verify

readelf -n /usr/lib/limine/limine-entry-tool | grep ISA prints x86-64-baseline. sudo limine-mkinitcpio finishes without the CPU-features error. After a reboot, uname -r matches pacman -Q linux (or linux-omarchy).

Sources

limine-entry-tool-avx2-old-cpu-unbootable