On 07/26/2015 01:30 PM, Chris Murphy wrote:
On Sun, Jul 26, 2015 at 9:51 AM, Larry Finger
wrote: As long as a particular installation needs to set the "legacy_boot" flag, it absolutely must clear that flag on all other partitions.
I thought that flag was only used by syslinux gptmbr.bin use case, which suggests BIOS firmware and a GPT partition scheme. That itself is an odd combination because there are a sufficient number of BIOS firmware systems that face plant on GPT that it's not a good default combination.
GRUB doesn't make use of legacy_boot, whether on BIOS or UEFI firmware. And it's next to pointless on UEFI firmware systems because the UEFI spec says any code in LBA 0 is to be ignored (except by CSM).
I'm under the impression these are all sufficiently edge cases they shouldn't happen on installations, and just be used for things like installation media.
This may be an edge case, but I'm not sure how rare it is. The bug report referenced in my first E-mail was not posted by me - there are at least two of us. The other one was in 13.1, I first hit the case with 13.2, and now it is present in 42.1. My BIOS has two options for boot - UEFI and CSM. The text says that the later option is for an OS that expects traditional BIOS booting capability. That is the setting that I am using. The legacy_boot flag is not used by GRUB as it is used by the BIOS to find the correct GPT partition to boot in the same manner that the active partition is selected for the boot code in a traditional DOS-type partition scheme. We all know what happens if you have more than one active partition. That is what is happening here. Larry -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org