[Bug 1025555] Re: Ubuntu i386 images are not compatible with recent (UEFI) computers

[sean]

I have a legitimate issue with this as well.
I just bought a Dell Latitude 10 with the intended purpose of trying out ubuntu's more touch friendly features on my new atom 32bit processor.

As all dells now come with EFI instead of BIOS i'm suck until the 32bit
Grub is adapted to support EFI.

I can get the 64bit ISO on a thumbdrive to be recognized by the Dell Latitude 10 inch tablet.
But when I select it to boot, it just goes to windows.

I can also get the 32bit ISO  on a thumbdrive to be recognized by the Dell Latitude 10 inch tablet.
But when I select it to boot, it just goes to windows.

I believe this is an issue with Ubuntu's lack of EFI support on their
32bit ISO, and Also intels lack of Legacy support on their new Tablet.

Is there a beta version we can begin testing?

Does anyone know if you can turn off EFI on the Dell Latitude 10?

The Latitude 10 is the cheapest tablet with an intel atom processor. It
seems an ideal candidate for pushing this bug up to the front.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubiquity in Ubuntu.
https://bugs.launchpad.net/bugs/1025555

Title:
  Ubuntu i386 images are not compatible with recent (UEFI) computers

Status in Ubuntu CD image build software:
  Confirmed
Status in “grub2” package in Ubuntu:
  Opinion
Status in “ubiquity” package in Ubuntu:
  Invalid

Bug description:
  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.

  Currently known machines that are affected are Intel Atom 32-bit System-on-a-chip based machines, such as phones & tablets as listed on:
  https://en.wikipedia.org/wiki/Atom_(system_on_chip)

  Please note explicit Intel Atom (CPU) architecture has not been
  supported in Ubuntu for a while know. The Atom system-on-chip is a new
  & upcoming type of processors that are not supported by Ubuntu at the
  moment and further work is required to bring up an Ubuntu port to such
  machines. At the moment those machines have limited stock, high
  pricetag and no Ubuntu ports known to be in progress.

  (potential work-around disable secure boot, prepare usb-stick with
  32bit grub-efi image installed, boot of that and perform manual  -
  "debootstrap" based installation: manually partition, manually install
  grub-efi, debootstrap packages, attempt to boot.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1025555/+subscriptions