I reproduced the issue on some Apple hardware I had access to yesterday. What is interesting so far is that while the command `efibootmgr` fails:
# efibootmgr EFI variables are not supported on this system.
It succeeds when specifying efivarfs for the LIBEFIVAR_OPS environment variable:
# LIBEFIVAR_OPS=efivarfs efibootmgr BootCurrent: 0000 BootOrder: 0000,0080 Boot0000* ubuntu Boot0080* Mac OS X Boot0082* BootFFFF*
This seems to indicate a failure in the efivarfs_probe function.
I reproduced the issue on some Apple hardware I had access to yesterday. What is interesting so far is that while the command `efibootmgr` fails:
# efibootmgr
EFI variables are not supported on this system.
It succeeds when specifying efivarfs for the LIBEFIVAR_OPS environment variable:
# LIBEFIVAR_ OPS=efivarfs efibootmgr
BootCurrent: 0000
BootOrder: 0000,0080
Boot0000* ubuntu
Boot0080* Mac OS X
Boot0082*
BootFFFF*
This seems to indicate a failure in the efivarfs_probe function.