| 2012-09-14 14:22:05 |
YannUbuntu |
bug |
|
|
added bug |
| 2012-09-14 14:23:04 |
YannUbuntu |
summary |
Ubiquity fails creating a correct Windows dualboot on EFI systems |
Ubiquity fails creating a correct Windows dualboot on EFI computers |
|
| 2012-09-14 14:24:39 |
Launchpad Janitor |
ubiquity (Ubuntu): status |
New |
Confirmed |
|
| 2012-09-14 14:28:44 |
YannUbuntu |
description |
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 ,
http://ubuntuforums.org/showthread.php?p=12238420#post12238420 )
- or it installs Ubuntu in Legacy (not-EFI) mode when Windows is installed in EFI mode.
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.
(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 |
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 ,
http://ubuntuforums.org/showthread.php?p=12238420#post12238420 )
- or it installs Ubuntu in Legacy (not-EFI) mode when Windows is installed in EFI mode.
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 the 32bit ISO is not EFI compatible 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 |
|
| 2012-09-14 14:32:47 |
YannUbuntu |
description |
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 ,
http://ubuntuforums.org/showthread.php?p=12238420#post12238420 )
- or it installs Ubuntu in Legacy (not-EFI) mode when Windows is installed in EFI mode.
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 the 32bit ISO is not EFI compatible 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 |
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 ,
http://ubuntuforums.org/showthread.php?p=12238420#post12238420 )
- or it installs Ubuntu in Legacy (not-EFI) mode when Windows is installed in EFI mode.
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 |
|
| 2012-09-14 14:44:30 |
YannUbuntu |
summary |
Ubiquity fails creating a correct Windows dualboot on EFI computers |
Ubiquity fails creating a correct Windows dualboot on EFI computers (wrong Ubuntu mode) |
|
| 2012-09-14 15:28:47 |
YannUbuntu |
summary |
Ubiquity fails creating a correct Windows dualboot on EFI computers (wrong Ubuntu mode) |
Ubiquity fails creating a correct Windows dualboot on EFI computers (grub-pc <-> grub-efi) |
|
| 2012-09-17 01:19:38 |
odror |
bug |
|
|
added subscriber odror |
| 2012-09-18 12:17:31 |
Jim Kyle |
bug |
|
|
added subscriber Jim Kyle |
| 2012-09-18 21:46:57 |
YannUbuntu |
description |
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 ,
http://ubuntuforums.org/showthread.php?p=12238420#post12238420 )
- or it installs Ubuntu in Legacy (not-EFI) mode when Windows is installed in EFI mode.
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 |
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 ,
http://ubuntuforums.org/showthread.php?p=12238420#post12238420 )
- or it installs Ubuntu in Legacy (not-EFI) mode when Windows is installed in EFI mode. ( 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 |
|
| 2012-09-18 21:49:03 |
YannUbuntu |
description |
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 ,
http://ubuntuforums.org/showthread.php?p=12238420#post12238420 )
- or it installs Ubuntu in Legacy (not-EFI) mode when Windows is installed in EFI mode. ( 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 |
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 ,
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 where Windows was installed in both EFI and Legacy modes: 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 |
|
| 2012-09-18 21:58:47 |
YannUbuntu |
description |
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 ,
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 where Windows was installed in both EFI and Legacy modes: 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 |
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 ,
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 |
|
| 2012-09-21 10:47:28 |
YannUbuntu |
description |
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 ,
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 |
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 , 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 |
|
| 2012-10-15 23:20:22 |
YannUbuntu |
description |
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 , 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 |
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 , 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 /sys/firmware/efi (or 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 |
|
| 2012-10-16 00:03:34 |
Steve Langasek |
bug |
|
|
added subscriber Steve Langasek |
| 2013-04-14 11:24:10 |
isden |
bug |
|
|
added subscriber isden |
| 2014-01-03 15:54:24 |
Phillip Susi |
ubiquity (Ubuntu): status |
Confirmed |
Invalid |
|
| 2014-01-03 17:03:20 |
Phillip Susi |
ubiquity (Ubuntu): importance |
Undecided |
Medium |
|
| 2014-01-03 17:03:20 |
Phillip Susi |
ubiquity (Ubuntu): status |
Invalid |
Triaged |
|
| 2014-01-03 17:05:41 |
Phillip Susi |
description |
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 , 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 /sys/firmware/efi (or 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 |
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 , 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.
This could be done by choosing between grub-efi and grub-pc based on the presence of an existing ESP when performing a side-by-side install, instead of whether the cd is booted in efi mode or not.
*************** WORKAROUND: using Boot-Repair to convert Ubuntu in the same mode as Windows.
See https://help.ubuntu.com/community/UEFI |
|
| 2014-01-09 19:56:21 |
Magnus Melin |
bug |
|
|
added subscriber Magnus Melin |
| 2014-07-30 07:19:52 |
JackT |
bug |
|
|
added subscriber JackT |
| 2015-02-05 22:29:17 |
Erick Brunzell |
bug |
|
|
added subscriber Erick Brunzell |
| 2015-02-05 23:14:35 |
Ubuntu QA Website |
tags |
|
iso-testing |
|
| 2015-02-06 15:50:57 |
Phillip Susi |
marked as duplicate |
|
1302418 |
|
