BIOS updates and GRUB

Hello again friends!

A few days ago I updated my BIOS, to possibly fix an issue I was having, and I’ve noticed some strange behavior when it comes to my boot entries. This might’ve been caused by my BIOS reverting to default settings after the update, but I’m not sure. Anyway, bellow I’ve attached the output of efibootmgr.

Summary
$ efibootmgr 
BootCurrent: 0001
Timeout: 1 seconds
BootOrder: 0001,0000,0004,0005
Boot0000* Windows Boot Manager	HD(1,GPT,2b63a0c5-ef16-4372-8a17-8bc823bc3d75,0x800,0x32000)/File(\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI)57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d0000004d000100000010000000040000007fff0400
Boot0001* UEFI OS	HD(1,GPT,1c5854c5-d649-474f-b109-2751ff8cd83d,0x22,0x967de)/File(\EFI\BOOT\BOOTX64.EFI)0000424f
Boot0004* CD/DVD Drive	BBS(CDROM,,0x0)0000474f00004e4f9d0000000100000075004400520057002d0032003400440035004d00540000000501090003000000007fff040002010c00d041030a0000000001010600030101010600010003120a000500ffff00007fff040001043e00ef47642dc93ba041ac194d51d01b4ce632004b00470034004200410031004a0030003800200030002000200020002000200020002000200000007fff04000000424f
Boot0005* Hard Drive	BBS(HD,,0x0)0000474f00004e4fb50000000100000075004b0049004e004700530054004f004e002000530055005600340030003000530033003700320034003000470000000501090002000000007fff040002010c00d041030a0000000001010600030101010600010003120a000000ffff00007fff040001043e00ef47642dc93ba041ac194d51d01b4ce63000350032003000420036003700370033003700320030003900420031003000200020002000200000007fff04000000424f00004e4fad00000001000000750053005400310030003000300044004d003000310030002d0032004500500031003000320000000501090002000000007fff040002010c00d041030a0000000001010600030101010600010003120a000100ffff00007fff040001043e00ef47642dc93ba041ac194d51d01b4ce620002000200020002000200020002000200020002000200039005a00430041004b0045005600340000007fff04000000424f00004e4fb3000000010000007100530061006d00730075006e006700200053005300440020003900380030002000500052004f00200031005400420000000501090002000000007fff040002010c00d041030a000000000101060001010101060000000317100001000000002538b321b4dc027fff040001043400ef47642dc93ba041ac194d51d01b4ce653003500470058004e00580031005400330030003600340031003400560000007fff04000000424f

What you’re seeing is pretty much identical to what I got after the update in the BIOS itself, except for the boot order. It was originally set to boot into Windows by default, so I wanted to change it to GRUB. Problem was that I was missing one of the entries that I used to have before the update, called endeavouros.

Seeing as the UEFI OS entry was on the same drive as my Endeavour install, I tried booting that one and it booted into GRUB successfully. Set it as primary option and left it at that.

Additionally, this is what I have in the /boot/efi/EFI directory:

ls /boot/efi/EFI/
boot  endeavouros  endeavouros-9494

Now, this might just be paranoia, but I’m worried that this isn’t the way to go about it and something might end up breaking in the future.

Question is, would it be fine to use it as it is right now? Should I run grub-install and grub-mkconfig or maybe something else entirely?

Thanks in advance! Take care everyone :slight_smile:

1 Like

this is always required on update Bios , reset to default settings , reboot then reapply your settings
there is no entry for endevourOS in your UEFI table motherboard

check date inside /boot/efi/EFI/endevouros and /boot/efi/EFI/endevourosendeavouros-9494 , and remove old one

you will have to : chroot from USB live endevouros
and apply command grub-install and grub-mkconfig

then recheck efibootmgr
and change order with option -o

1 Like

If I am not mistaken, this is the fallback boot path that UEFI firmware will use. The boot entries for EnOS seems to have been deleted in the NVRAM.

Since you are able to boot into your system, you could try reinstalling the bootloader from the running system:

sudo grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=enos-grub

and then regenerate your grub.cfg using:

sudo grub-mkconfig -o /boot/grub/grub.cfg

Check with efibootmgr if the new boot entry has been created.

Reboot using the new boot entry and remove the old directories

endeavouros  endeavouros-9494

from /boot/efi/EFI.

1 Like

endeavouros seems to be the most recent one. Should I just delete the endeavouros-9494 directory entirely?

Any reason why I shouldn’t run those straight from Endeavour, since I have access to it?

Out of curiosity, would running it with --bootloader-id=endeavouros instead of --bootloader-id=enos-grub be a bad idea. Since it’s the most recent entry I was thinking I could just overwrite it.

I guess you could do that as well.
The important thing is to check if the EFI boot entry is correctly created and “registered” in UEFI.

1 Like
$ efibootmgr 
BootCurrent: 0001
Timeout: 1 seconds
BootOrder: 0002,0001,0000,0004,0005
Boot0000* Windows Boot Manager	HD(1,GPT,2b63a0c5-ef16-4372-8a17-8bc823bc3d75,0x800,0x32000)/File(\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI)57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d0000004d000100000010000000040000007fff0400
Boot0001* UEFI OS	HD(1,GPT,1c5854c5-d649-474f-b109-2751ff8cd83d,0x22,0x967de)/File(\EFI\BOOT\BOOTX64.EFI)0000424f
Boot0002* endeavouros	HD(1,GPT,1c5854c5-d649-474f-b109-2751ff8cd83d,0x22,0x967de)/File(\EFI\endeavouros\grubx64.efi)
Boot0004* CD/DVD Drive	BBS(CDROM,,0x0)0000474f00004e4f9d0000000100000075004400520057002d0032003400440035004d00540000000501090003000000007fff040002010c00d041030a0000000001010600030101010600010003120a000500ffff00007fff040001043e00ef47642dc93ba041ac194d51d01b4ce632004b00470034004200410031004a0030003800200030002000200020002000200020002000200000007fff04000000424f
Boot0005* Hard Drive	BBS(HD,,0x0)0000474f00004e4fb50000000100000075004b0049004e004700530054004f004e002000530055005600340030003000530033003700320034003000470000000501090002000000007fff040002010c00d041030a0000000001010600030101010600010003120a000000ffff00007fff040001043e00ef47642dc93ba041ac194d51d01b4ce63000350032003000420036003700370033003700320030003900420031003000200020002000200000007fff04000000424f00004e4fad00000001000000750053005400310030003000300044004d003000310030002d0032004500500031003000320000000501090002000000007fff040002010c00d041030a0000000001010600030101010600010003120a000100ffff00007fff040001043e00ef47642dc93ba041ac194d51d01b4ce620002000200020002000200020002000200020002000200039005a00430041004b0045005600340000007fff04000000424f00004e4fb3000000010000007100530061006d00730075006e006700200053005300440020003900380030002000500052004f00200031005400420000000501090002000000007fff040002010c00d041030a000000000101060001010101060000000317100001000000002538b321b4dc027fff040001043400ef47642dc93ba041ac194d51d01b4ce653003500470058004e00580031005400330030003600340031003400560000007fff04000000424f

Looks like it’s there. Safe to reboot now and remove endeavouros-9494?

1 Like

Looks good!
Reboot and once in the system you could remove endeavouros-9494.

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.