** Description changed: Currently, Ubiquity sometimes fails creating a correct Windows dualboot when: - - either it installs Ubuntu in EFI mode when Windows is installed in Legacy mode ( examples: Bug #908109 , Bug #959446 , + - either it installs Ubuntu in EFI mode when Windows is installed in Legacy mode ( examples: Bug #908109 , Bug #959446 , Bug #956412 http://ubuntuforums.org/showthread.php?p=12238420#post12238420 ) - or it installs Ubuntu in Legacy (not-EFI) mode when Windows is installed in EFI mode. ( example: http://ubuntuforums.org/showpost.php?p=12246811&postcount=6 ) In order to create a correct dualboot, Ubiquity should always install Ubuntu in the same mode as Windows. I think the deep problem is that Ubiquity only looks at dmesg | grep EFI to determine if it is going to install in EFI mode or not. AFAIK, dmesg only indicates the mode in which the BIOS boots the live media, NOT the mode in which the BIOS boots the HDD. Remark: currently Ubuntu32bit is not EFI compatible (see Bug #1025555 ), so Ubiquity32bit will always install in Legacy mode (which allowed the OP of Bug #908109 to workaround the current bug). (this problem is more and more frequent as new computers generally come with EFI firmware) *************** WORKAROUND: using Boot-Repair to convert Ubuntu in the same mode as Windows. See https://help.ubuntu.com/community/UEFI
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1050940 Title: Ubiquity fails creating a correct Windows dualboot on EFI computers (grub-pc <-> grub-efi) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1050940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
