Hot answers tagged

15

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 ...


13

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 ...


10

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.


9

TO ADDRESS YOUR EDIT: I didn't notice the edit to your question until just now. As written now, the question is altogether different than when I first answered it. The mirror you describe is not in the spec, actually, as it is instead a rather dangerous and ugly hack known as a hybrid-MBR partition format. This question makes a lot more sense now - it's not ...


8

EDIT: When I wrote this answer very few distributions shipped with an EFI_STUB configured kernel so one had to build a custom one. Nowadays most distributions ship a suitably configured kernel and a custom build is not required any longer. In this case the sections “Set up your partitions” and “Setting things up” are the interesting ones, “Requirements” and ...


7

The problem was simply that the efivars kernel module was not loaded. This can be confirmed by: sh-4.2# efivar-tester UEFI variables are not supported on this machine. If you are chrooted in to your new install, exit out, and then enable efivars: exit modprobe efivars ...and then chroot back in. In my case, this means: chroot /mnt but you should ...


3

I don't know why you're using grub in the first place. UEFI acts as a boot loader and it allows to select different operating systems or individual kernels from a boot menu. Although there are some exceptions, it usually is not required to chain a second boot loader, grub in this case. You mention, you installed elementary OS instead of Fedora, which means ...


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 ...


3

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 ...


2

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 ...


2

You don't necessarily need to dual boot Windows and Linux on UEFI. Follow the guide to convert your UEFI to MBR-BIOS without loss of data. This guide has been made by me. Also, the referred blog will never be taken down. Although I have used it like 10 times without any loss of data, I would recommend you to backup your data before using my procedure.


2

I can heartily recommend the UEFI article series by Rod Smith. In particular, he mentions that "hybrid" GPT-MBR is a "dangerous hack" due to desynchronisation hazards.


2

I was able to boot Arch from UEFI by using an Archboot image, and then install it on the GPT drive. Then I had to install grub2, which I installed on the same partition as the Microsoft EFI partition, and chainloaded Windows 7 bootloader from it. Thanks!


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

So apparently there are several issues and several approaches to handle this. EFI should be able to handle RAID paritions, but only with metadata <= 1.0 Newer version of metadata are stored on the beginning of the partition (screwing up the filesystem detection). You can go without extra /boot partition if you integrate the /boot into /boot/efi after ...


2

I don't remember if EFI GRUB2 uses LoadImage() (most likely it does by now as the RestrictedBoot story has basically boiled down to "your last-mile bootloader has to or shim will blow it up") -- it will take EFI drivers (like those available with refind) if that's the case; GRUB-specific filesystem drivers are not available to EFI firmware. Your ...


2

I ended up fixing my computer by reinstalling OSX. Everything works fine now, I could go on to install anything I like from here. http://apple.stackexchange.com/questions/164975/going-back-to-mac-os-x-after-installing-ubuntu


2

When I reinstalled my ESP and grub I used rEFInd: http://sourceforge.net/projects/refind/files/?source=navbar (the flashdrive variant) to boot into my distribution. After booting mount your ESP into /boot/efi mount -t vfat /dev/yourESPdev /boot/efi Then you should be able to reinstall grub with this EFI directory. grub-install --efi-directory=/boot/efi ...


2

Forget grub entirely - it is nothing but a distraction. It isn't even a boot-loader anymore; on EFI systems the bootloader is built-in to the firmware. grub is just a boot-manager in that context - and almost definitely entirely redundant. What's more - it is probably the grub install that broke everything in the first place. These are the things you need: ...


2

Current util-linux versions of fdisk support GPT, the one I'm looking at here is fdisk from util-linux 2.24.2 (reported via fdisk -v). Run fdisk /dev/whatever. Have a look at the options with m. Note these change depending on the state of the partition table. First check what state the disk is currently in with p. Note the Disklabel type; if it is gpt ...


1

You seem to have spoiled your windows bootloader for now but that might still be fixable by installing openSUSE with UEFI bootloader and not CSM/Legacy one (so that there's actually an /EFI/opensuse/shim.efi on the EFI System Partition). There's nothing GRUB can do to load Windows if its own bootloader is misinstructed as per some careless tutorial. Don't ...


1

I've been working with a similar issue all day. I just installed lubuntu on a Quantum Byte QS-1043-QB. It uses the same processor and chipset you are working with. I got the to same point you are. Basically, you need to install a 32 bit EFI file for grub and 32 bit grub version. First, install 32-bit support for grub sudo apt-get install grub-efi-ia32 ...


1

You might be interested in Rod's EFI bootloaders introduction and my ALT Linux Rescue might come handy as it contains both Refind boot manager and all the tools needed to mess with partitions and filesystems (e.g., to create another ESP if debian installer didn't do that for you). Note that ESP -- a FAT32 partition with a special GPT UUID -- is both ...


1

If I understand you you're looking for a way to boot from USB using grub. According to this post, the way to do that is to start the machine with the USB stick connected and get to the grub prompt. There you can type root (hd (without pressing enter) and press tab to list hard drives. The USB device will probably be hd1 so the line would be root (hd1). From ...


1

You should install Linux in EFI too if you want using it with EFI. Simplest would be reinstall Linux in EFI mode (do not format EFI partition while installation). But you don't have to do it. You can just mount your EFI partition to '/boot/efi', add new line to fstab and install grub-efi. So you must do something like this: lsblk to find EFI partition. For ...


1

/boot/efi must be a FAT32 "efi system partition" (ESP), see also http://www.rodsbooks.com/efi-bootloaders/principles.html


1

jasonwryan pointed me in the right direction. I performed the following steps: 1) downloaded latest installation media and made a bootable USB 2) unencrypted my LUKS LVM volumes 3) mounted my volume to the live USB file system in /mnt/arch, a directory I created (including /mnt/arch/boot, and /mnt/arch/home) 4) connected to the internet with wifi-menu ...


1

To me, it seems that something went wrong with the installation of GRUB. I would try to create a new firmware boot entry first: efibootmgr -c -d /dev/disk/by-uuid/b790d826-8e17-4ec7-b89b-12d783ec520e -p 2 -l /EFI/debian/grubx64.efi -L "Debian" (for more information see e.g. ...


1

For EFI boot you need to form a specific structure of the image's filesystem, not just bootsector (since it's unused), so have a look at Ubuntu's live-helper scripts (my guess) or examine mki-copy-efiboot script (the part of mkimage which I wrote and use). In case you just need a custom rescue image, not neccessarily an Ubuntu-based one, you might like my ...


1

So, here's what the link says: Maintaining ELILO If your distribution includes scripts to maintain ELILO automatically, and if those scripts work, you shouldn't need to do much to maintain this boot loader. As noted earlier, though, in my experience these auto-maintenance scripts are often worse than useless. Thus, you may need to keep your ELILO ...



Only top voted, non community-wiki answers of a minimum length are eligible