On Wed, 2013-03-20 at 00:25 +0000, Mike wrote:
[...]
> In order to document this failure mode, I made this installation attempt on a
> system that I "cleaned" after a successful installation. So it isn't quite
> the same as a brand-new machine.
>
> At the HP startup screen, hit "ESC" for the "Startup Menu", "F10" for "BIOS
> Setup", in "System Configuration" tab, "Boot Options", change "Boot Mode" from
> "Legacy" to "UEFI Hybrid (With CSM)". (I made other, irrelevant, settings
> changes, too.)
>
> Reboot to the "Startup Menu", "F9" for "Boot Device Options", choose "USB Hard
> Drive 1",
At a guess, this option might result in booting the installer in legacy
mode. The installer cannot set EFI boot variables unless it is booted
in EFI mode.
On the system I've installed using EFI, the BIOS shows two boot options
for removable media, for the two possible boot modes.
> "Advanced options", "Expert install".
>
> The Installer seemed to think that GRUB succeeded: "grub-installer: info:
> grub-install ran successfully". But rebooting fails to find boot code, gives
> HP screen:
>
> ----------------------------------------
> BootDevice Not Found
>
> Please install an operating system on your hard disk.
> ----------------------------------------
>
> etc. Rebooting the USB stick to rescue mode, I umount the /boot and /boot/efi
> partitions--because mount thinks they're mounted--before I truly mount them.
> Then I install grub-efi-amd64, and:
>
> ----------------------------------------
> # grub-install /dev/sda
> Fatal: Couldn't open either sysfs or procfs directories for accessing EFI variables.
> Try 'modprobe efivars' as root.
> Fatal: Couldn't open either sysfs or procfs directories for accessing EFI variables.
> Try 'modprobe efivars' as root.
> Installation finished. No error reported.
> # modprobe efivars
> ERROR: could not insert 'efivars': Unknown symbol in module, or unknown parameter (see dmesg)
> # dmesg | tail -1
> [...] efivars: Unknown symbol efi_enabled_facility (err 0)
[...]
The rescue system should load efivars from the installation kernel,
since the installed system which might not have a compatible kernel
version (as happened here). This is bug #703363 and should be fixed in
rc2.
Still, efivars will fail to initialise if you didn't boot in EFI mode.
Ben.
--
Ben Hutchings
The generation of random numbers is too important to be left to chance.
- Robert Coveyou
Attachment:
signature.asc
Description: This is a digitally signed message part