Bug 1172114

u-boot does not expose EFI vars, so only removable installations are possible. This conflicts with:

"# run grub2-install also non-removable if efi is there"

Sounds like fallout from bug #1167015 for Fujitsu A64FX.

Created attachment 838197 [details]
y2logs

I could reproduce this on Build 202.5 (jeos 14.49) on a RPi3B+ by installing yast2-bootloader, running "yast2 bootloader" and pressing Save/Finish.

Created attachment 838198 [details]
framebuffer screenshot of error msg

Yes, it is result of change done for bug #1167015

Adding needinfo for mchang, as he requested that change and also adding Gary, who has some insight.

It seems that grub2-install was run twice unconditionally. I'd expect something like this:

if (efivarfs exists) {
  grub2-install
}
grub2-install --no-nvram --removable

(In reply to Gary Ching-Pang Lin from comment #6)
> It seems that grub2-install was run twice unconditionally. I'd expect
> something like this:
> 
> if (efivarfs exists) {
>   grub2-install
> }
> grub2-install --no-nvram --removable

well, I use previously existing test for efivars which looks like

Yast::Arch.aarch64 && File.directory?("/sys/firmware/efi")

so if /sys/firmware/efi is directory, it will run it without params. We use it to decide if we need to add `--no-nvram --removable` or not.

So Dominik, can you please check if this directory exists in your case?

Yes, /sys/firmware/efi is a directory with some files and subfolders in it on my Raspberry Pi 3B+.

(In reply to Dominik Heidler from comment #8)
> Yes, /sys/firmware/efi is a directory with some files and subfolders in it
> on my Raspberry Pi 3B+.

Is there any like Boot0000-8be4df61-93ca-11d2-aa0d-00e098032b8c in /sys/firmware/efi/efivars/ or /sys/firmware/efi/vars/? If u-boot did emulate some UEFI variables, then we need to find another way to detect the emulated UEFI environment...

If so, this is not a regression by new update, but brand new issue as uboot emulated uefi couldn't be reliably detected by the logic we know of (and using).

Or is there any good explanation why previous version would work ?

(In reply to Josef Reidinger from comment #7)
> (In reply to Gary Ching-Pang Lin from comment #6)
> > It seems that grub2-install was run twice unconditionally. I'd expect
> > something like this:
> > 
> > if (efivarfs exists) {
> >   grub2-install
> > }
> > grub2-install --no-nvram --removable
> 
> well, I use previously existing test for efivars which looks like
> 
> Yast::Arch.aarch64 && File.directory?("/sys/firmware/efi")


Hi Josef,

It seems like !Dir.glob("/sys/firmware/efi/efivars/*").empty? should be used instead of File.directory?("/sys/firmware/efi") ? It was used by removable_efi? in previous version and also aligned with the logic in perl bootloader.

Yes, I can change it, it is not problem. Just Dominik can you please check if there is anything at `/sys/firmware/efi/efivars/*` ? So we are sure before changing it?

# find /sys/firmware/efi
/sys/firmware/efi/
/sys/firmware/efi/fw_platform_size
/sys/firmware/efi/efivars
/sys/firmware/efi/systab
/sys/firmware/efi/config_table
/sys/firmware/efi/vars
/sys/firmware/efi/vars/del_var
/sys/firmware/efi/vars/new_var

OK, fix is in review https://github.com/yast/yast-bootloader/pull/605

*** Bug 1172133 has been marked as a duplicate of this bug. ***

fix merged. It is sr#219190 yast2-bootloader version 4.2.25

Works fine on build 209.2