On Sun, Jul 26, 2015 at 10:15 PM, Andrei Borzenkov <arvidjaar@gmail.com> wrote:
В Sun, 26 Jul 2015 22:08:37 -0600 Chris Murphy <lists@colorremedies.com> пишет:
On Sun, Jul 26, 2015 at 9:41 PM, Andrei Borzenkov <arvidjaar@gmail.com> wrote:
В Sun, 26 Jul 2015 19:23:03 -0600 Chris Murphy <lists@colorremedies.com> пишет:
On Sun, Jul 26, 2015 at 6:20 PM, Larry Finger <Larry.Finger@lwfinger.net> wrote:
Strictly speaking the firmware is completely unaware of the legacy_boot attribute, it's only something the gptmbr.bin initial bootloader code is looking for to know where to continue loading bootloader code.
Which is why I'm confused. gptmbr.bin is part of the syslinux package.
GPT_MBR = "/usr/share/syslinux/gptmbr.bin" DOS_MBR = "/usr/share/syslinux/mbr.bin" def generic_mbr_file @generic_mbr_file ||= mbr_is_gpt? ? GPT_MBR : DOS_MBR end
YaST writes it if you check "install generic MBR".
Oh, you know what? I spaced out that openSUSE doesn't put core.img in either the MBR gap or BIOSBoot.
That depends on boot device selected in bootloader configuration.
They're sticking it into the 64KB bootloader pad on Btrfs. Since core.img starts right at the first sector of the Btrfs partition, gptmbr.bin and mbr.bin will find it when the Btrfs partition is marked bootable.
Even when installed in partition grub consists of two parts - boot sector that is installed in partition boot record and core.img that is installed elsewhere. Do not confuse them. [gpt]mbr.bin finds only the former; where the latter is located is encoded as absolute position in boot sector as usual.
Got it. Thanks. -- Chris Murphy -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org