On Thu, 28.06.12 09:29, Peter Jones (pjones@xxxxxxxxxx) wrote: > Having sent that mail it became obvious that what's happened is that your > new x220 board doesn't have the efi boot variable set. Some machines allow > you to boot from a file, in which case it'll be /efi/fedora/grubx64.efi . > If your firmware doesn't have that, you'll need to boot some install/rescue > media to get to a shell. In either case you'll need to use efibootmgr to > add /efi/fedora/grubx64.efi to the boot order. > > That's all assuming it's F17; if it's earlier, it'll be /efi/redhat/grub.efi . Hmm, so if grub would also install itself into /efi/boot/bootx64.efi then this problem would just go away as that is the default file that the EFI bios will execute. This would enable disk images that just boot without any need to register them in the bios... Is there any reason why Fedora doesn't create that file? (it's a pity FAT can't do symlinks, hence it should just be a copcy of grubx64.efi) Lennart -- Lennart Poettering - Red Hat, Inc. -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
