efi images fail - Githubissues

NixOS / nixos

OBSOLETE (go to NixOS/nixpkgs) - NixOS, a Linux distribution based on the Nix package manager - OBSOLETE (go to NixOS/nixpkgs)

MIT License

175 stars 102 forks source link

efi images fail #248

Closed tebowy closed 9 years ago

tebowy commented 11 years ago

HW: Lenovo Y580

Description: All images avaiable at http://hydra.nixos.org/job/nixos/trunk/iso_efi.x86_64-linux doesn't have efi directory at the top level. I am not sure whether this is in accordance to UEFI spec, however, all efi images I've seen so far have this directory:

Arch Linux
Windows 8
systemrescuecd-x86-3.7.1.iso
ubuntu-gnome-13.04-desktop-amd64.iso

When I dd image on usb and try to select it from boot menu, system says there is nothing bootable on disk.

Replication:

Download nixos-efi-13.09pre5022_71365b7-af96f91-x86_64-linux.iso
dd it on USB drive
Reboot system
Press f12, select USB HDD
System Error: instert bootable disk and press any key

Expected result:

Nixos installer boot in efi mode

Workaround: None

Additional Info: My UEFi doesn't support Secure Boot, ergo this isn't factor here

edolstra commented 11 years ago

Maybe @shlevy knows about this?

tebowy commented 11 years ago

Am I suposed to mail him?

shlevy commented 11 years ago

No, I'll take a look some time this week

tebowy commented 11 years ago

Any news?

lovek323 commented 11 years ago

I'd be keen to get this working too.

Phreedom commented 11 years ago

You have this efi.img thing, which if loop-mounted has the needed files. To get usb drive bootable I had to use unetbootin, then copy stuff from efi.img to the drive and fix initrd params because it failed to find root partition.

shlevy commented 11 years ago

So as I note in the commit above, this now mostly works in nixpkgs master. The "mostly" is because by default the initrd can't find the rootfs, since unetbootin doesn't create the partition (where it could label it) and it doesn't know to modify gummiboot menu entries (it does copy grub entries and set root to use uuids for the syslinux boot though). The best solution for now is to press 'e' on the gummiboot command line and set the root= to the label or uuid or whatever of your thumb drive, which is not optimal but is probably the best we can do unless we either a) provide images to dd over the partition (which is what arch does) or b) modify unetbootin to know how to update gummiboot's entries. Neither of those seems super-appealing to me.