efi stub record is going out after reboot

[st834]

Hi,

i am try to install kernel as uefi stub. i have read this guide: https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Bootloader#Alternative_2:_EFI_Stub. But my settings and new boot record are going out after rebboting my Hewlett Packard Pavilion laptop. I read the article about efibootmgr too. An Internet search indicates errors, but I am booming that this is not so, because the GRUB installation (now I would like to do it without GRUB) works without problems.

I would appreciate advice on how I can get the efi stub right.

Thanks!

[charles17]

for minimalistic setup based on gentoo-sources see https://wiki.gentoo.org/wiki/User:Vaukai/EFI_stub
there replace /boot with /efi

further options in https://wiki.gentoo.org/wiki/EFI_stub

[st834]

Thank you very much for your response. I replaced /boot with /efi, read these articles and checked the kernel settings.

If I try to UEFI file (select the *.efi file) at boot, the kernel behaves as expected.

When adding a boot entry:

[charles17]

can't you use onboard tool to access the bios / efi instead of bothering with efibootmgr?
i don't even have efibootmgr installed.

[st834]

I didn't use it before, but today I'll try it, thanks for the idea. I also found this: https://wiki.archlinux.org/title/Unified_Extensible_Firmware_Interface#Windows_changes_boot_order, section 9.8 "Boot entries created with efibootmgr fail to show up in UEFI".

Thanks!

[pietinger]

st834,

I boot my kernel also directly from UEFI and wrote this article:

https://wiki.gentoo.org/wiki/User:Pietinger/Tutorials/Boot_kernel_via_UEFI

If your created UEFI boot entry disappears after system start there exist two reasons:

1. Your UEFI is faulty ... we had in our forum some systems where it was not possible to create a new entry (this is a definite violation of the uefi specification), OR

2. There exist no (valid) bin-file where the entry points to. Most (all?) UEFI systems check at system start EVERY entry it has and if that bin-file EXIST at the defined location; AND IF NOT, UEFI simply deletes this entry (so, yes, you can create every entry you want and you will even see it in "efibootmgr" immdediately after creating ... but if it is not correct it will be deleted after enxt system startup). =>

So, please check again if --loader "\EFI\Gentoo\kernel-6.6.30-gentoo.efi" really point to your EXISTING kernel (maybe a typo somewhere ?).


P.S.: Maybe give us the output of "efibootmgr" and a "ls -lR /efi"
_________________
https://wiki.gentoo.org/wiki/User:Pietinger

[st834]

Thank you very much for your response. I will check all paths today and will read your article again carefully. I will write the results here. Thanks!

[charles17]

[st834]

Hi,

continued to explore the topic.

I installed GRUB earlier with the --removable key. Without this key the bootloader was not visible in UEFI. Here I read https://superuser.com/questions/1756758/what-does-grub-installs-removable-flag-do about with what path and with what name is the *.efi file of the bootloader with the -- removable key installed. Renamed the kernel from /efi/EFI/Gentoo/kernel-6.6.30-gentoo.efi to /efi/EFI/BOOT/bootx64.efi and the process went.

But doesn't Hewlett Packard firmware understand the other way? I bought this computer without pre-installed Windows and there is a version of non-Windows UEFI.

Thanks!

[AndrewAmmerlaan]

[pietinger]

[AndrewAmmerlaan]

[pietinger]

[AndrewAmmerlaan]

[pietinger]

[st834]

Thakns a lot for all answers!

[logrusx]

The boot entry may disappear if the files it points to disappear as well.

Also search the internet for similar problems with your particular hardware.

Best Regards,
Georgi