Kernel Panic After Update Fix Guide

[ryanrhughes]

In the latest update of Limine, the lookup order of the limine.conf was changed to prioritize the one in the same directory as the EFI file. https://github.com/limine-bootloader/limine/blob/v10.3.0/ChangeLog

Because of this, a number of installs fail to boot after updating since our conf is located in /boot/limine.conf which was previously highest priority.

We can't change our location at the moment due to have limine-entry-tool sources the conf file so the best bet for now is to ensure no alternatives exist.

If you were unfortunate enough to hit this error, the following should be the fastest method to get you back up and running with a permanent fix.

1. Press a key to return to the Limine bootloader

   

2. With the entry highlighted, press the e key

3. Remove the two highlighted lines

   

4. Change protocol to efi_chainload

   

5. Add the line image_path: boot():/EFI/Linux/omarchy_linux.efi

   

6. Press f10 to boot normally.

7. IMPORTANT After booting, run Omarchy Menu > Update > Omarchy and ensure the migration to fix this permanently runs properly before rebooting.

To manually verify, you can also run lt --level 3 /boot and ensure you only have one limine.conf file in the main /boot folder.

Alternative Method

If for some reason this doesn't work, it's likely that you're using a different kernel so the efi path is slightly different. In that instance, the easiest restoration method is the folowing.

• Boot to the Omarchy ISO and hit ctrl + c, then select exit at the error screen until you get to a terminal OR use the Arch Live ISO.
• Run lsblk and identify your drive.
• Run mount /dev/{boot_partition} /mnt/boot
• Locate the rogue .conf file in /mnt/boot and remove it. It will likely be at /mnt/boot/EFI/limine/limine.conf

[ryanrhughes]

☝️

[sarniva]

After trying to update to 3.1.6 from
3.1.5, the terminal showed some warning to not boot but I didn't care much , Now it's in panic mode.
Help plz.

[sarniva]

I follwed the guide and changed limine entry but still shows error.
Help Please !!
@ryanrhughes

[illangpasandre-prog]

Check this #3239

[Christophe-ldb]

After modifying the lines as proposed, I get this error message :
'PANIC: Unsupported protocol specified.'
Before modification I had: `protocol: linux'

[depmots]

thanks! this fixed it for me, but even after running omarchy-update once in omarchy, when i reboot i still get the default limine bootloader and not the omarchy one, and i have to redo the fix again (editing with efi_chainload etc...)

[acramatte]

Thanks @ryanrhughes 🤝

To make it work on my Intel MBP (2019) I adapted the image_path to the T2 chip:
image_path: boot():/EFI/Linux/omarchy_linux-t2.efi

If that helps others.

[ryanrhughes]

Good callout! If you've changed your kernel, that extension will be different.

I think we have a couple running Cachy kernels so that'll be important for them if they hit this.

[illangpasandre-prog]

I have tried both of the methods above but it failed

[illangpasandre-prog]

[knothhe]

edit this file like this
#3239 (comment)

[illangpasandre-prog]

Thanks

[sarniva]

Did you able to fix it?

[sarniva]

Is my /boot directory good? can i reboot?

[CaffeinatedTech]

This is an upstream issue where they've made breaking changes, and unfortunately it makes Omarchy look bad; I see people losing trust over on reddit, and switching out. Maybe they were just looky-loos anyway, but it has had a negative impact. I don't really have a point, other than to bring up what I've noticed. Maybe we could push the community support a bit more, as I keep directing people to the discord who don't seem to know it exists despite being linked right next to the download button.

**Special notes:**
    Despite there being breaking changes in this release, no major version
    bump is done; this is because the changes are minor enough, there are
    no big new features, and version 10.x was not released long enough ago.
    This is technically in violation of Semantic Versioning, but considered
    to be an acceptable exception.

Breaking changes:
    - Change default paths and default path ordering for configuration file
      search. Mainly, search first for a configuration file in the same
      directory as the EFI application file of Limine, on EFI ports.
    - Change default path ordering for stage 3 file search on BIOS ports.
    - No longer install the limine.h header file on the host.
    - No longer install PROTOCOL.md (Limine Boot Protocol specification) on
      the host.

[ryanrhughes]

@CaffeinatedTech I'm with you. It's an unfortunate byproduct of a rolling release, and unfortunately we had 2 in one weekend kind of slap us. There was this one where an upstream decision to reverse a load order for seemingly no reason wrecked our boots, followed almost immediately by a Hyprland parsing issue.

However; with both of these, it has pushed the agenda a bit further for hardening the whole thing and testing some unique ways to achieve the benefits of Arch Linux and rolling release while also having a more stable go at it for your average person.

[erlestor]

Is rolling release that important? I would much rather prefer stable releases

[dbo-keeganpatton]

I have followed the solution, but the efi file is not found either. Pretty much bricked.

Even when I place Omarchy higher in the boot order in bios, Limine boot loader is what starts

[AppleKid7]

FWIW I performed a system update/upgrade yesterday directly with pacman and today ran into this issue booting up first thing in the morning.

What worked for me was switching the the boot order to give Omarchy priority over Limine (make sure when you exit the BIOS menu you save changes), which allowed me to boot into Omarchy. Once in Omarchy, I did a system update from the menu, and when it was done, everything went back to normal. I switched the order back to Limine having boot order priority over Omarchy and it's exactly the same as it was last week.