Hot answers tagged efi
6
I don't know how Windows handles UEFI, but from the Debian side it's pretty
straightforward.
Set up your partitions
Use the GPT partition scheme, not MBR.
To boot from a GPT partition with UEFI a dedicated boot partition is mandated,
called the EFI SYSTEM PARTITION (ESP). It is not mandatory, but the most
compatible way is to use a FAT32 partition. A size ...
4
After a day of research, I can now answer my own Question: yes it is possible, and you can even use that partition as /boot and store your kernels/initramfs/etc. there.
Requirements:
Grub >= 2.00 (1.98 and 1.99 do not work)
Grub must be installed from a Linux kernel, that has support for EFI variables (CONFIG_EFI_VARS compiled in or as module efivars)
For ...
4
QEMU's -kernel, -boot, and -initrd are BIOS only. They are completely incompatible with EFI (currently).
Update: OVMF supports -boot since r13683, and supports -kernel -append -initrd since r13923.
Download OVMF-0.1+r14071-1.1.x86_64.rpm or newer version.
Extract bios.bin from the rpm: rpm2cpio OVMF-0.1+r14071-1.1.x86_64.rpm | cpio -idmv
Specify firmware ...
3
A system can have a UEFI firmware and still boot OS in legacy BIOS mode. In that situation there is no way for the booted OS to determine if the hardware is actually capable of UEFI, because BIOS isn't forward compatible with UEFI.
You can still look at firmware interface if anything is related to UEFI, but that is vendor specific and inconsistent. So there ...
2
When you go into the "BIOS" (EFI actually) one of the items in the list of bootable items should be the EFI boot prompt, if it's a UEFI system. This is sometimes called the EFI shell. It's much like an emaciated version of a Unix command prompt. Normally you won't want it in the boot list but it can be useful during initial setup and during troubleshooting.
...
2
Just drop this binary into that flash drive FAT's root directory under the name of shellx64.efi, or get yourself a copy of refind usbflash image which would also serve as a decent boot manager.
1
I am not that familiar with SUSE but i think that the boot partition always has to be outside lvm.
the kernel loads the lvm module and then can access the lvm-disks but not before.
so you need a 500MB /boot partition outside lvm that can hold the kernel image.
As far as i read you need a special bootmanager to be able to boot form EFI:
I am not sure if ...
1
I think I've found the answer: I believe it is Windows boot code. Based on the readable ASCII in the hexdump ("Invalid partition table.Error loading operating system.Missing operating system.") I was able to do a Google search and found a site which discussed windows bootloaders. The hexdump of mine matches the Windows 7 bootloader detailed at ...
1
Not a direct answer but as there are none you might be interested in this xorriso bugreport -- I'm going to comment there too but in short, xorriso-1.2.4 with the upstream revision 1044 works fine for me and my hardware stand with exactly this script (it's a Russian spoken wiki but the script part should be legible enough; pay attention to efiboot.img).
...
1
Apparently it was a bug with the UEFI firmware, as described in the release notes for intels 0053 firmware update. However DO NOT install it. It will brick your motherboard! Well done intel. Yet another reason not to have UEFI.
1
Do you have Windows installed on a GPT partition?
If I understand you correctly, you are trying something like what I did yesterday
I had the same error, it comes up, because with EFI you do not give chainloader a number of sectors to read but the path to the Windows boot file.
chainloader /efi/Microsoft/Boot/bootmgfw.efi
Your root should be set to the ...
1
Make sure that UEFI is not going to lock Linux out of your machine; there is probably a setting to that effect in the BIOS. Check and verify for sure. I would double-check this point with the manual and with the manufacturer if you must.
There was some extended discussion about it; ZDNet had several articles. Here is an article from 21 September 2011 and ...
1
Try adding noefi to the end of the GRUB_CMDLINE_LINUX_DEFAULT line in /etc/default/grub, then run grub-mkconfig -o /boot/grub/grub.cfg (assuming that's where you grub configuration file is).
I used to get the exact same error. This fixed it. Although I still can't get the keyboard to work...
Only top voted, non community-wiki answers of a minimum length are eligible
