Hi, I can set the efivars correctly with th efibootmgr. Thereafter I can read them correct and set the bootorder. After a reboot looking in uefi (bios)everything is correct. But after the reboot efibootmgr reads nothing !!! Is this a bug in efibootmgr or uefi or normal behaviour of a non standard uefi ??? -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 27. 07. 20, 16:51, JJM de Faber wrote:
Hi,
I can set the efivars correctly with th efibootmgr.
Thereafter I can read them correct and set the bootorder.
After a reboot looking in uefi (bios)everything is correct.
But after the reboot efibootmgr reads nothing !!!
Is this a bug in efibootmgr or uefi or normal behaviour of a non standard uefi ???
Hi, usually crazy bioses remove entries which occur invalid to them. Just when enumerating what to boot (i.e. just before loading shim/grub). For example all non-Windows entries might vanish. regards, -- js suse labs -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 28. 07. 20, 9:05, Jiri Slaby wrote:
On 27. 07. 20, 16:51, JJM de Faber wrote:
Hi,
I can set the efivars correctly with th efibootmgr.
Thereafter I can read them correct and set the bootorder.
After a reboot looking in uefi (bios)everything is correct.
But after the reboot efibootmgr reads nothing !!!
Is this a bug in efibootmgr or uefi or normal behaviour of a non standard uefi ???
Hi,
usually crazy bioses remove entries which occur invalid to them. Just when enumerating what to boot (i.e. just before loading shim/grub). For example all non-Windows entries might vanish.
One more note: make sure you pass correct partition and disk to efibootmgr. Sometimes efibootmgr stores an invalid disk and/or partition to the variables and BIOS rightfully removes that entry as such partition is not FAT for example (but is your / or /boot, not /boot/efi). What's the output when you pass -v to efibootmgr when adding the entry? regards, -- js suse labs -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 2020-07-28 09:05, Jiri Slaby wrote:
On 27. 07. 20, 16:51, JJM de Faber wrote:
Hi,
I can set the efivars correctly with th efibootmgr.
Thereafter I can read them correct and set the bootorder.
After a reboot looking in uefi (bios)everything is correct.
But after the reboot efibootmgr reads nothing !!!
Is this a bug in efibootmgr or uefi or normal behaviour of a non standard uefi ??? Hi,
usually crazy bioses remove entries which occur invalid to them. Just when enumerating what to boot (i.e. just before loading shim/grub). For example all non-Windows entries might vanish.
regards,
Imediately after setting I read a correct setting and it works also as expected. Reading it in uefi(bios) everything is always correct. But after a reboot only efibootmgr reads nothing, maybe the data is replaced or efibootmgr or the kernel looks at the wrong place (address). I guess it is a "American megatrends" or a "asus motherboard uefi problem". jjm1:/home/hans/scripts # efibootmgr -v BootOrder: 0001,0002,0003,0000 Boot0000* refind HD(1,GPT,df31d808-5611-48d3-8344-7162f2b5cb77,0x800,0xfa000)/File(\EFI\refind\refind_x64.efi) Boot0001* leap152 HD(1,GPT,df31d808-5611-48d3-8344-7162f2b5cb77,0x800,0xfa000)/File(\EFI\leap152\grubx64.efi) Boot0002* leap151 HD(1,GPT,df31d808-5611-48d3-8344-7162f2b5cb77,0x800,0xfa000)/File(\EFI\leap151\grubx64.efi) Boot0003* tumbleweed HD(1,GPT,df31d808-5611-48d3-8344-7162f2b5cb77,0x800,0xfa000)/File(\EFI\tumbleweed\grubx64.efi) regards,Hans -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 28. 07. 20, 10:56, JJM de Faber wrote:
jjm1:/home/hans/scripts # efibootmgr -v
Which of those entries were added by you and dismiss?
BootOrder: 0001,0002,0003,0000 Boot0000* refind HD(1,GPT,df31d808-5611-48d3-8344-7162f2b5cb77,0x800,0xfa000)/File(\EFI\refind\refind_x64.efi)
Boot0001* leap152 HD(1,GPT,df31d808-5611-48d3-8344-7162f2b5cb77,0x800,0xfa000)/File(\EFI\leap152\grubx64.efi)
Boot0002* leap151 HD(1,GPT,df31d808-5611-48d3-8344-7162f2b5cb77,0x800,0xfa000)/File(\EFI\leap151\grubx64.efi)
Boot0003* tumbleweed HD(1,GPT,df31d808-5611-48d3-8344-7162f2b5cb77,0x800,0xfa000)/File(\EFI\tumbleweed\grubx64.efi)
-- js suse labs -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 2020-07-29 07:50, Jiri Slaby wrote:
On 28. 07. 20, 10:56, JJM de Faber wrote:
jjm1:/home/hans/scripts # efibootmgr -v Which of those entries were added by you and dismiss?
BootOrder: 0001,0002,0003,0000 Boot0000* refind HD(1,GPT,df31d808-5611-48d3-8344-7162f2b5cb77,0x800,0xfa000)/File(\EFI\refind\refind_x64.efi)
Boot0001* leap152 HD(1,GPT,df31d808-5611-48d3-8344-7162f2b5cb77,0x800,0xfa000)/File(\EFI\leap152\grubx64.efi)
Boot0002* leap151 HD(1,GPT,df31d808-5611-48d3-8344-7162f2b5cb77,0x800,0xfa000)/File(\EFI\leap151\grubx64.efi)
Boot0003* tumbleweed HD(1,GPT,df31d808-5611-48d3-8344-7162f2b5cb77,0x800,0xfa000)/File(\EFI\tumbleweed\grubx64.efi)
Entry 0 is done by myself (script). Entry 1,2,3 are done by yast. After a reboot all entries still exist (read in uefi (bios)) But efibootmgr does not see them. ----- jjm1:/home/hans # efibootmgr -v No BootOrder is set; firmware will attempt recovery ---- I think the problem is in the asus uefi implementation the data is moved to a different address (safe and immutable). -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
participants (2)
-
Jiri Slaby -
JJM de Faber