apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1416634/+attachment/4309238/+files/IwConfig.txt
-- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1416634 Title: installer failed to set boot flag on UEFI Status in linux package in Ubuntu: Confirmed Bug description: Hi, I installed Ubuntu 14.10 but it wouldn't boot, it took several hours to get a working system. I've managed, but I'd just like to document this because I couldn't find any relevant writeups online and the problem seems so simple that I'm surprised it just didn't work out of the box. I received a new Acer Aspire E1-572G, I took out the pre-installed Windows disk (after just checking that it booted OK) and replaced it with a blank SSD. I dd'd the 64-bit 14.10 to a USB key. I got the ISO last week from www.ubuntu.com, and most of the files on it are dated Oct 22. After booting (with some difficulties detailed at http://ubuntuforums.org/showthread.php?t=2263270) I installed Ubuntu, entire disk encrypted LVM (it's a laptop after all), rebooted... and nothing: "No bootable device -- insert boot disk and press any key". I tried with UEFI instead of Legacy, and I get a different error message (text graphics reminiscent of linux kernel make menuconfig) but same meaning, nothing bootable found. I booted the live USB to check that the disk looked OK (a half gig "Microsoft basic" partition, then a small 244MB linux partition, then the rest as a Linux partition. I followed the boot-repair doc on <https://help.ubuntu.com/community/Boot-Repair>, and I used default repair, no good. <http://paste.ubuntu.com/9959580> The installer needed to put the bootable flag on the "Microsoft Basic" partition, and maybe change the type to EFI also. Now that I've done that, my laptop boots OK with Legacy or UEFI without secure boot (and with secure boot it finds the bootable partition and says that the security policy blocks it, which is better than totally ignoring it like it did before). I don't understand why the installer didn't do that, maybe a problem with choosing encrypted LVM? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1416634/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
