3

Based on this answer for detecting the boot loader I ran sudo dd if=/dev/sda bs=512 count=1 2>&1 | grep GRUB and it matched. However, I'm pretty sure I'm running Gummiboot since modifying /boot/loader/entries/arch.conf affected my boot. Does an EFI boot loader like Gummiboot not modify the MBR, or am I misunderstanding something? Is it a problem if I have "enabled" both?

Related to enabling Intel microcode updates.

l0b0
  • 51,350
  • 2
    The EFI boot loader is in its own partition, type EF00, formatted vfat. The EFI loader resides on the filesystem, but isn't necessarily in the first N blocks. What is it you want to do? – bsd Oct 23 '14 at 08:20
  • 1
    ^this. and, in fact, it is extremely rare that you would even have an MBR if you are booting with EFI as you are almost definitely working with a GPT-formatted disk per spec - though I have recently been made aware that MBR+EFI is possible. maybe look here for a short-discussion on EFI boot process, and definitely look at rodsbooks.com – mikeserv Oct 23 '14 at 09:25
  • Were you referring to a specific book or article at rodsbooks.com? – l0b0 Oct 23 '14 at 11:53
  • There are several series which you'll find under My Web Pages but Managing EFI BootLoaders for Linux is as good a place as any to start. The other link I provided before is really just a primer for rodsbooks, anyway, and also contains a few relevant links to various pages there. – mikeserv Oct 23 '14 at 12:36

0 Answers0