http://bugzilla.opensuse.org/show_bug.cgi?id=939453 http://bugzilla.opensuse.org/show_bug.cgi?id=939453#c1 Chris Murphy changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bugzilla@colorremedies.com --- Comment #1 from Chris Murphy --- https://bugzilla.opensuse.org/show_bug.cgi?id=848609#c3 I'm confused by this. Why is gptmbr.bin being used, unless extlinux is the bootloader? If GRUB is the bootloader, grub2-install should write boot.img to LBA 0, not gptmbr. And boot.img contains the jump code to find core.img in BIOSBoot, so there is no need for legacy_boot attribute. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=939453 http://bugzilla.opensuse.org/show_bug.cgi?id=939453#c9 --- Comment #9 from Chris Murphy --- (In reply to Michael Chang from comment #2)

The problem is that not all users like the idea to write grub/grub2 to LBA0.

Then they should opt out and use extlinux instead of GRUB 2. The current openSUSE behavior and recommendation is incongruent with GRUB upstream. http://lists.gnu.org/archive/html/grub-devel/2015-08/msg00093.html Basically what you have in openSUSE now is something that's a.) inconsistent with GRUB upstream b.) inconsistent with all other distros c.) not documented anywhere a user could find it d.) not a self-describing or easily followed boot process, e.) installing GRUB core.img into the Btrfs 64KiB bootloader pad while supported is considered suboptimal by GRUB upstream they prefer it going either in the MBR gap or BIOS Boot where there's more room for a larger core.img. This makes it difficult to troubleshoot, the user has to get this esoteric information from not just the openSUSE community since no one else does it this way, but a narrow slice within the openSUSE community because it's such esoteric (and unexpected) behavior. If GRUB by default, then only support their recommended methods. Optionally provide UI for the user to opt out of overwriting LBA 0, which then uses extlinux, which is explicitly meant for this use case. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=939453 http://bugzilla.opensuse.org/show_bug.cgi?id=939453#c11 --- Comment #11 from Michael Chang --- (In reply to Chris Murphy from comment #9)

(In reply to Michael Chang from comment #2)

...

The problem is that not all users like the idea to write grub/grub2 to LBA0.

If GRUB by default, then only support their recommended methods. Optionally provide UI for the user to opt out of overwriting LBA 0, which then uses extlinux, which is explicitly meant for this use case.

The UI is already there, we just have to change default proposal to mbr. We don't want to bring yet another loader (extlinux) to mess up maintenance work and we can't simply disable or remove that option from yast installer also because any feature change should go through FATE process to evaluate impact and I believe some people or running setup would still stay to prefer it. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.