"""
3) Installing grub-efi from an already installed Ubuntu32 creates
/efi/ubuntu/boot.efi , and /efi/ubuntu/grubia32.efi . Both EFI entries fail.
"""
And how exactly was that done? 32bit installer does not create UEFI partition
to correctly place efi bootloader image.
Thus to test this one has to do manual paritioning while installing 32bit
installer, leave a small partition (e.g. 200MB) at the front of the disk,
formatted as FAT (EFI) partition and only then install grub-efi and I would
then expect the UEFI boot in 32bits to work.
I have a MacBook early 2006 edition, which is 32bit EFI-only boot with
an option for bios emulation. And I have used grub-efi (grub2 that is)
successfully with it in the distant past. (~Hardy time)
It is true that we do not have 32bit UEFI bootable installation media.
And we have no plans on fixing that, as on the other end of the stick
older 32-bit BIOS-only computers may fail to boot when detecting
gpt/multiparition CD images with dual bios/uefi boot stack.
I highly daubt it's a bug in grub2-efi, and ubiquity has support for
efi. The bug here is against ubuntu-cdimage project that we don't
generate any 32-bit uefi capable installation media. But i'd like to see
a significant market share of 32bit-only-UEFI machines before we do
introduce such an image.
** Also affects: ubuntu-cdimage
Importance: Undecided
Status: New
** Summary changed:
- Ubuntu32bits is incompatible with recent (UEFI) computers
+ Ubuntu i386 images are not compatible with recent (UEFI) computers
** Changed in: grub2 (Ubuntu)
Status: Confirmed => Invalid
** Changed in: ubiquity (Ubuntu)
Status: Confirmed => Invalid
** Changed in: ubuntu-cdimage
Status: New => Confirmed
** Description changed:
64bits EFI computer (with GPT disk) with pre-installed 64bits Windows7.
AND 32bits EFI computer without legacy boot support
1) Installing Ubuntu 12.04 64bit creates a valid /efi/ubuntu/grubx64.efi
entry. At reboot, the GRUB menu appears and allows to boot Ubuntu.
2) Installing Ubuntu 12.04 32bits installs grub-pc, which creates no EFI
entry. Ubuntu can't be booted (except if it is possible to deactivate
EFI mode).
3) Installing grub-efi from an already installed Ubuntu32 creates
/efi/ubuntu/boot.efi , and /efi/ubuntu/grubia32.efi . Both EFI entries
fail.
4) Installing grub-efi in an already installed Ubuntu32 in chroot via an
Ubuntu64 live-CD ( so that grub-efi has access to EFI variables) also
creates two invalid EFI entries (/efi/ubuntu/boot.efi , and
/efi/ubuntu/grubia32.efi ).
CONCLUSION:
- grub-efi 32bits always creates invalid entries.
- Installing Ubuntu32 bits on an EFI system should be blocked by Ubiquity
(the Ubuntu installer). In this case, Ubiquity should ask the user to install
Ubuntu64 instead.
- the Download page should warn that the 32bits ISO is not compatible with
recent (EFI) computers
+
+ === Workarounds ==
+
+ If you have UEFI-only machine, please use amd64 (64-bit) images. That
+ image will most likely work for you as your machine is highly likely a
+ 64-bit one.
+
+ If you truly have 32-bit-only CPU and UEFI-only machines please post
+ exact Manufacturer, OEM, make, brand and model number as a comment on
+ this bug report.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1025555
Title:
Ubuntu i386 images are not compatible with recent (UEFI) computers
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1025555/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
