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

Migrate to the mkinitcpio `microcode` hook (mkinitcpio 38 / March 2024)

archomarchyendeavouroscachyosmanjarointelamdsystemd-bootgrublimine
CORRECTED An auditor found the fix wrong or incomplete and rewrote it.
AUDIT NOTE

Version claims checked against the mkinitcpio CHANGELOG and the gitlab tags: v38 was tagged 2024-02-28 with '--microcode has been deprecated and replaced by the new microcode hook', v38.1 on 2024-03-12 noted the hook prefers /usr/lib/firmware/*-ucode/ and uses /boot/*-ucode.img only as a fallback, and the Arch news post is dated 2024-03-04 and lists mkinitcpio 38-3, systemd 255.4-2, lvm2 2.03.23-3, mdadm 4.3-2 and cryptsetup 2.7.0-3. So 'mkinitcpio 38 / systemd 255.4 / March 2024' holds. On this machine mkinitcpio 41.1 still accepts --microcode with the warning 'The --microcode option has deprecated' (/usr/bin/mkinitcpio line 982) and warns on a preset's *_microcode or ALL_microcode option (lines 727 to 731), so the symptom is still reachable on an Arch install carrying a pre-2024 preset. The wiki Microcode page confirms the hook, the autodetect-before-microcode narrowing, the lsinitcpio --early check, and the separate-file layouts for GRUB, systemd-boot and Limine that the record describes. Omarchy 4 is not affected and the fix as written misdirects there: /etc/mkinitcpio.conf.d/omarchy_hooks.conf (owned by omarchy-settings 4.0.2-1) assigns HOOKS wholesale with microcode directly after autodetect, so the record's edit to HOOKS in /etc/mkinitcpio.conf is silently replaced when the drop-in is sourced afterwards. journalctl -k on this machine shows 'microcode: Updated early from: 0x000000ae' to revision 0x000000f8 with intel-ucode 20260812-1, confirming early loading works stock. sudo pacman -Syu mkinitcpio systemd lvm2 mdadm cryptsetup is refused on Omarchy 4 by /etc/pacman.d/hooks/00-omarchy-update-guard.hook, whose script aborts any pacman invocation carrying both S and u (omarchy-update-pacman-guard lines 23 to 47), while pacman -S amd-ucode passes because it has no u. sudo mkinitcpio -P exits with 'No presets found in /etc/mkinitcpio.d' because that directory is empty here (limine-mkinitcpio-hook shadows mkinitcpio's pacman hook and never generates presets), so the rebuild on Omarchy is limine-mkinitcpio, and the record's advice to grep /etc/mkinitcpio.d/*.preset has nothing to grep. The verify field also names mkinitcpio -P, which does not apply on Omarchy 4. Not exercised: lsinitcpio --early on the UKI (needs root to read /boot), a rebuild, and the systemd-boot and GRUB branches, which were checked against the wiki only.

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

Removing the initrd /*-ucode.img line from a systemd-boot entry *before* the microcode hook is in place and the image rebuilt leaves you booting without microcode updates. Do the HOOKS edit and mkinitcpio -P first, then edit the loader entry.

Symptom

After the mkinitcpio 38 / systemd 255.4 upgrade, boot entries that hand-list microcode still work but mkinitcpio warns about the deprecated --microcode flag, or CPU microcode silently stops being loaded (dmesg | grep -i microcode shows no early update). Users on manual systemd-boot entries also report the boot failing to find /intel-ucode.img after cleaning /boot.

Cause

Arch moved the systemd, udev, encrypt, sd-encrypt, lvm2 and mdadm_udev hooks from distro packages into upstream mkinitcpio, and deprecated the --microcode flag and the microcode preset option in favour of a new microcode **hook** that embeds the CPU microcode into the initramfs itself. Configs written before March 2024 still use the old two-initrd approach. mkinitcpio 41 still accepts the old flag and preset option, with a deprecation warning, so a preset or boot entry that was never migrated keeps working and keeps warning.

Omarchy 4 is not affected. It was packaged after this change, and its hooks are assigned wholesale by /etc/mkinitcpio.conf.d/omarchy_hooks.conf (owned by omarchy-settings), which already carries microcode right after autodetect. The microcode is inside the UKI at /boot/EFI/Linux/omarchy_linux.efi, so no separate intel-ucode.img or amd-ucode.img line exists in the Limine entry.

Fix

**Omarchy 4**

Nothing to migrate. Confirm the hook is present and the microcode loads:


grep -h microcode /etc/mkinitcpio.conf.d/*.conf
journalctl -k --grep='microcode:'

Expect a HOOKS=(... autodetect microcode ...) line from omarchy_hooks.conf and microcode: Updated early from: ... in the journal. Do not edit HOOKS in /etc/mkinitcpio.conf: the drop-in assigns HOOKS=(...) after that file is read and replaces whatever you set there.

If the journal shows no early update, the microcode package is missing. Install the one for your CPU, then rebuild the UKI:


sudo pacman -S amd-ucode      # AMD
sudo pacman -S intel-ucode    # Intel
sudo limine-mkinitcpio

pacman -S <pkg> passes the ALPM guard, which only refuses -Syu. Use limine-mkinitcpio, not mkinitcpio -P: /etc/mkinitcpio.d is empty on Omarchy 4 and -P exits with No presets found. Do not add initrd=/intel-ucode.img to a /etc/limine-entry-tool.d file or a module_path line to /boot/limine.conf. Keep the packages current with omarchy update, since a direct pacman -Syu is refused.

**Plain Arch**

Bring the system fully current. The March 2024 announcement required mkinitcpio 38-3, systemd 255.4-2, lvm2 2.03.23-3, mdadm 4.3-2 and cryptsetup 2.7.0-3 to move as a set, and a full upgrade does that:


sudo pacman -Syu

Install the microcode package for your CPU if it is not already there:


sudo pacman -S amd-ucode      # AMD
sudo pacman -S intel-ucode    # Intel

Add the microcode hook right after autodetect in /etc/mkinitcpio.conf:


HOOKS=(base udev autodetect microcode modconf kms keyboard keymap consolefont block filesystems fsck)

Rebuild:


sudo mkinitcpio -P

If you use **systemd-boot with hand-written entries**, the separate microcode initrd line is now redundant. /boot/loader/entries/arch.conf becomes:


title   Arch Linux
linux   /vmlinuz-linux
initrd  /initramfs-linux.img
options root=UUID=xxxx-xxxx rw

(delete any initrd /amd-ucode.img or initrd /intel-ucode.img line). GRUB users need do nothing extra beyond sudo grub-mkconfig -o /boot/grub/grub.cfg. Limine users with a hand-written limine.conf can drop the module_path: boot():/<cpu>-ucode.img line once the hook is in place.

Also check /etc/mkinitcpio.d/*.preset for a leftover --microcode in default_options or fallback_options and remove it. Then confirm:


journalctl -k --grep='microcode:'
sudo lsinitcpio --early /boot/initramfs-linux.img | grep microcode

Verify

dmesg | grep -i 'microcode' shows microcode: Current revision: ... / updated early, and mkinitcpio -P runs without deprecation warnings.

Sources

microcode-hook-migration-mkinitcpio-38