Closed perfect7gentleman closed 8 years ago
You've shown me /sys/firmware/efi/vars/ but the log has efivar using /sys/firmware/efi/efivars/ - is the file also there?
I'm suspecting there's a kernel bug here where they're not identical for some reason.
there is nothing in /sys/firmware/efi/efivars/
~ $ zcat /proc/config.gz | grep -i efi
CONFIG_EFI_PARTITION=y
CONFIG_EFI=y
CONFIG_EFI_STUB=y
# CONFIG_EFI_MIXED is not set
CONFIG_EFI_SECURE_BOOT_SIG_ENFORCE=y
# CONFIG_FB_EFI is not set
CONFIG_DMI_SCAN_MACHINE_NON_EFI_FALLBACK=y
# EFI (Extensible Firmware Interface) Support
CONFIG_EFI_VARS=y
CONFIG_EFI_ESRT=y
# CONFIG_EFI_FAKE_MEMMAP is not set
CONFIG_EFI_RUNTIME_WRAPPERS=y
# CONFIG_EFI_BOOTLOADER_CONTROL is not set
# CONFIG_EFI_CAPSULE_LOADER is not set
# CONFIG_EFIVAR_FS is not set
# CONFIG_EARLY_PRINTK_EFI is not set
# CONFIG_EFI_PGT_DUMP is not set
i think 'CONFIG_EFIVAR_FS is not set' causes the bug, amiright?
Give it a try with a libefivar built with that patch?
Saw the same issue here and this patch appears to fix the problem for me
(Also people should really be migrating to CONFIG_EFIVAR_FS)
I'm having the error message described in the title of this issue, and I've read all the comments here, but I yet didn't understand what I must do to fix, or workaround, this problem.
Have the same issue on Oracle Linux on Raspberry Pi 3b+ but no sure how to fix it. Anyone?
With new efibootmgr-13 there some bugs: