On Jul 11, 2014, at 2:09 PM, Gareth Williams
wrote:
>
>> 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
>> mo
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
On Jul 10, 2014, at 11:39 PM, Gareth Williams
wrote:
> On 11/07/14 06:24, Chris Murphy wrote:
>> On Jul 10, 2014, at 4:56 AM, "Williams, Gareth"
>> wrote:
>>
>>> My question therefore is: Does anaconda do something else after running
>>> 'efibootmgr' to make it permanent? Or: Why can anacon
On 11/07/14 06:24, Chris Murphy wrote:
On Jul 10, 2014, at 4:56 AM, "Williams, Gareth"
wrote:
My question therefore is: Does anaconda do something else after running
'efibootmgr' to make it permanent? Or: Why can anaconda update NVRAM using
efibootmgr, while I can't?
'no bootable device' s
On Jul 10, 2014, at 4:56 AM, "Williams, Gareth"
wrote:
> My question therefore is: Does anaconda do something else after running
> 'efibootmgr' to make it permanent? Or: Why can anaconda update NVRAM using
> efibootmgr, while I can't?
'no bootable device' sounds suspiciously like a BIOS mess
After a frozen install while trying to make a dual-boot system I had
to hard-reboot my laptop using the power button.
On restarting, I was greeted with a UEFI message telling me that there
was no bootable device installed! I quickly inserted a boot CD and
managed to boot into my inst
