> - the disk is Ms-Dos (not GPT) This is not relevant. UEFI does not require a GPT to boot; there is a specification for a declaration of EFI System Partitions on an MBR-only disk.
> - and Windows was installed in Legacy mode ( there is no EFI partition) Also not relevant. To grub-installer, this just looks like a system that has an unbootable copy of Windows sitting on the disk. Fundamentally, the problem here seems to be that the CD *is* booted in UEFI mode, but the firmware won't use UEFI when booting the OS from disk. That sounds like a firmware bug, and one I have no idea how to work around. It should be obvious that if the firmware booted the CD under UEFI, the firmware is UEFI and we should install grub-efi to the install disk too. It would be absolutely incorrect to blindly install grub-pc on systems that have clearly booted using EFI. Likewise, installing grub-pc instead of grub-efi based on the detection of non-EFI OS installs would trade one set of bugs for another. The only reliable fix here would be to know that this buggy firmware is in such an EFI-only-on-CD mode and install grub-pc in that case. (Alternatively, we could rearchitect the grub packages so that we are always installing both grub-efi and grub-pc on all installs, something that I increasingly believe we need to be doing in order to support users across the BIOS->EFI threshold. But eventually we would want to drop grub-pc from EFI systems anyway, so this bug could still be a problem.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1015211 Title: Ubiquity installed grub-efi when it should have installed grub-pc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1015211/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
