Grub 2:2.06.r322.gd9b4638c5-1 won't boot and goes straight to the BIOS after update

Open a new thread, it’s unrelated to the issues being discussed in this one.

1 Like

it says:
Loading kernel linux-zen …
452: out of range pointer: 0x89253020

Aborted. Press any key to exit.

It is UEFI .

You need to change in the BIOS the boot order, from UEFI OS to endeavouros-a_number
It happened here too and I fixed doing that.

Okay is your root /dev/nvme0n1p6? Is /dev/nvme0n1p4 the efi partition?

Edit: Boot on the live ISO

sudo mount /dev/nvme0n1p6 /mnt
sudo mount /dev/nvme0n1p4 /mnt/boot/efi
sudo arch-chroot /mnt

Downgrade grub.

1 Like

I had the same issue.

For me the solution was to go into my BIOS and select the EndeavourOS-grub as first Boot Entry again.
The instructions on here name --bootloader-id=EndeavourOS-grub but for me the name was just EndeavourOS previously.

That’s why I needed to update the enrty in the BIOS again.

p6 is the root partition and p4 is the boot partition. As I got fro fdisk command.

Okay should work then with my instructions.

@android @mcury
thank you!
in my case it was the newly created eos-grub entry that did it ! :smiling_face_with_tear:

1 Like

I gave up for this nonsense and converted my grub to systemd boot using @dalto quide :exploding_head:


It is definitely caused by running grub-mkconfig after updating grub.

If you don’t generate a new config, it works fine. So in theory, we could diff those files and see that the difference is. I will do that now.


Its not os-prober I reproduced the issue with os-prober turned off

1 Like

That user has a familiar name… @bitterhalt

My os-prober is also off.

1 Like

That’s a different issue, that user was still able to boot into the Arch installation.


I think I found it.

It looks like fwsetup --is-supported was added to 30_uefi-firmware

That line seems to cause the issue.

EDIT: However, that doesn’t really answer anything, does it? Does that imply that we should be running grub-install after grub updates?



All hail to @dalto. Yet, what off now?



I do not and I never did. Is there anything that makes you (and @sradjoker , @Stagger_Lee and @ivanhoe ) think I did?

You are right, sorry, will delete my post

Nobody said so.
It’s strictly “to the issue” here, afaict.