NVRAM changes not persistent with efibootmgr

Gareth Williams gareth at garethwilliams.me.uk
Fri Jul 11 20:09:51 UTC 2014


> There's an argument for totally ignoring NVRAM. rEFInd, an EFI boot 
> manager, produces its boot entries dynamically from fstab, a static 
> configuration file, and the contents of /boot. It ignores NVRAM, 
> there's no constantly modified grub.cfg on the EFI system partition 
> when kernels are updated. 

That sound worth investigating.  How can it ignore NVRAM?  Isn't NVRAM 
used by the firmware to decide which EFI executable to run? Or does 
rEFIind simply takes the place of the default EFI/BOOT/BOOTX64.EFI and 
hence there won't be any reason to have entries in NVRAM?  Maybe I 
should RTFM instead of asking!

Thank you again for your help - it's most appreciated.

Gareth


More information about the users mailing list