Kernel panic after update

[RodriMora]

System details

AMD Ryzen, Nvidia 4060, Omarchy 3.1.5

What's wrong?

After a regular Omarchy update today at 2:00pm UTC, rebooting results in a kernel panic. I've seen reports in reddit too:
https://www.reddit.com/r/omarchy/comments/1oqwwd6/kernel_panic_after_fresh_install_and_update/

[ljrobins]

Prior discussion in #3154

I and others are having the same issue! Dell Latitude E7470.

[whargrove]

I was able to workaround this by booting from Omarchy directly, instead of booting Limine first. I had changed the boot order so that Limine was first, but since it is now borked I can still boot directly to Omarchy. Confirms it is likely an issue with the limine conf.

[bashln]

I was able to workaround this by booting from Omarchy directly, instead of booting Limine first. I had changed the boot order so that Limine was first, but since it is now borked I can still boot directly to Omarchy. Confirms it is likely an issue with the limine conf.

I can confirm that this actually works.

Had the same kernel panic a few minutes ago and tried this. Everything works great

[cazador11]

Got the same issue

[bashln]

Got the same issue

Try what @whargrove mentioned and let us know if it worked or not, please.

[clouraLabs]

I can confirm this issue as well. After today's update, I'm experiencing the same kernel panic on boot when using Limine bootloader.

The workaround mentioned by @whargrove works for me - bypassing Limine and booting directly to Omarchy resolves the panic. This strongly suggests the recent update introduced a compatibility issue with the Limine bootloader configuration.

Would it be possible to get more details on what changed in the update that might affect bootloader compatibility? This seems to be affecting multiple users across different hardware configurations.

[SirenGlitch]

Would it be possible to get more details on what changed in the update that might affect bootloader compatibility? This seems to be affecting multiple users across different hardware configurations.

Limine-Bootloader/Limine@e06cc37 Changes the order Limine looks for configs using

[jubiloso]

I guess .local/share/omarchy/migrations/1761241493.sh should have used the new path for limine.conf

echo "Cleanup extra UKI if needed to prevent errors"
if [[ -f /boot/EFI/linux/omarchy_linux.efi ]] && [[ -f /boot/EFI/linux/$(cat /etc/machine-id)_linux.efi ]]; then
  sudo rm -f /boot/EFI/Linux/$(cat /etc/machine-id)_linux.efi

  if grep -q "/boot/EFI/Linux/$(cat /etc/machine-id)_linux.efi" /boot/limine.conf; then
    echo -e "Resetting limine config\n(you may need to re-add other entries via sudo limine-update)"

    sudo mv /boot/limine.conf /boot/limine.conf.bak
  sudo tee /boot/limine.conf <<EOF >/dev/null                    ###### <------------------------------------------------- HERE ???
### Read more at config document: https://github.com/limine-bootloader/limine/blob/trunk/CONFIG.md
#timeout: 3
default_entry: 2
interface_branding: Omarchy Bootloader
interface_branding_color: 2
hash_mismatch_panic: no

term_background: 1a1b26
backdrop: 1a1b26

# Terminal colors (Tokyo Night palette)
term_palette: 15161e;f7768e;9ece6a;e0af68;7aa2f7;bb9af7;7dcfff;a9b1d6
term_palette_bright: 414868;f7768e;9ece6a;e0af68;7aa2f7;bb9af7;7dcfff;c0caf5

# Text colors
term_foreground: c0caf5
term_foreground_bright: c0caf5
term_background_bright: 24283b

EOF
    sudo limine-update
    sudo limine-snapper-sync
  fi
fi

[allandt-numan]

Installed Omarchy for the first time on an old Asus Centrino N58, did the update while I poked around at all the new toys, rebooted, same issue.

Can I ask how to boot into omarchy directly? I've only used grub before (ubuntu user) so I'm not used to the limine bootloader

[SirenGlitch]

Can I ask how to boot into omarchy directly? I've only used grub before (ubuntu user) so I'm not used to the limine bootloader

From this reddit comment: "Quick fix is to manually edit the boot entry and change the protocol to efi_chainload and the path to /EFI/Linux/omarchy_linux.efi"

Then from there either delete /boot/EFI/limine/limine.conf or copy /boot/limine.conf into its place (per @jubiloso's workaround

[allandt-numan]

does the module_path also need to be updated (currently it matches path but with the addition of .img on the end)

[SirenGlitch]

does the module_path also need to be updated (currently it matches path but with the addition of .img on the end)

Shouldn't do, should just work

[MrHPotter]

Thanks. Had the same issue on ryzen 5800x. Copyong the limine config seems to have done the trick