http://bugzilla.opensuse.org/show_bug.cgi?id=1142229
http://bugzilla.opensuse.org/show_bug.cgi?id=1142229#c19
--- Comment #19 from Neil Rickert
Dell machines, for example.
Interesting. I have had some Dell machines, but never noticed. Perhaps I never tested that, or perhaps it isn't all Dell machines. I current have a Dell Inspiron N5010 (purchased in 2009 or 2010). Currently, it is using the "altmbr.bin" boot code, configure to always boot "/dev/sda5". But it has "/boot/sda3" set as active (to keep Windows happy). As a test, I changed so that only partition 5 is active. And it still boots. I suspect the following would work to boot partition 5 with "btrfs": (1) mark the extended partition as active; (2) install "altmbr.bin" into the extended partition, set to always boot partition 5 (or whatever partition is using "btrfs"). (3) install grub to boot from partition 5 (or whatever is using "btrfs") However, I'm not sure that it is worth changing the installer for these situations. Most newer computers won't be affected. Even that Dell N5010 has a large enough MBR gap that there wouldn't be a problem. There are so few computers where there would be a problem, that it makes more sense to just have a Wiki page on how to handle these unusual boot situations. It is better for the owner of such a computer to be aware of the problems and of how he has worked around them. -- You are receiving this mail because: You are on the CC list for the bug.