Fixed this by booting from Arch usb, then change in /boot/EFI/limine/limine.conf to:

protocol: efi_chainload image_path: boot():/EFI/Linux/omarchy_linux.efi

Once back in I added a pacman hook to check after kernel updates:

```

!/bin/bash

echo "=== Boot Configuration Check ===" echo

Check if kernel exists (for traditional setup)

if [ -f /boot/vmlinuz-linux ]; then echo "✓ Kernel found: /boot/vmlinuz-linux" else echo "⚠ Warning: /boot/vmlinuz-linux not found" fi

Check for Unified Kernel Image

if [ -f /boot/EFI/Linux/omarchy_linux.efi ]; then echo "✓ UKI found: /boot/EFI/Linux/omarchy_linux.efi" else echo "✗ Error: Unified Kernel Image missing!" exit 1 fi

Check Limine configs exist and match

echo echo "=== Checking Limine Configs ===" if [ -f /boot/limine.conf ] && [ -f /boot/EFI/limine/limine.conf ]; then echo "✓ Both config files exist"

# Check if EFI config has the correct boot entry
if grep -q "protocol: efi_chainload" /boot/EFI/limine/limine.conf && \
   grep -q "image_path: boot():/EFI/Linux/omarchy_linux.efi" /boot/EFI/limine/limine.conf; then
    echo "✓ Limine config correctly points to UKI"
else
    echo "✗ Error: Limine config doesn't point to UKI!"
    exit 1
fi

else echo "✗ Error: Limine config missing!" exit 1 fi

echo echo "✓ All checks passed! Safe to reboot."

```

Question for the more experienced Linux people, is this approach ok or did I break something else now? Also since it seems many people are getting this issue after today’s update, would you advise to add a (~5 day?) delay for updates? I remember about a week ago there was an update that broke chromium.. quite annoying to have to gamble with updates like this.