This affects precise,quantal , and raring. Have not tried saucy yet. Is there a way to confirm the first stage installer are capable of running on an EFI system that is not secure boot capable? Is shim required on non SecureBoot system?
I suspect if shim/ first stage installer are not able to run using .efi image and are only looking for signed.efi criteria not finding either so should drop to legacy/bios installer automatically but fall back installer is not running either. is only speculation because do not know the intended meaning of first and second stage installer- ref:http://web.dodds.net/~vorlon/wiki/blog/SecureBoot_in_Ubuntu_12.10/ ga a75 ud4h mobo being used. When booting precise,quantal or raring with EFI on get to situation as described http://askubuntu.com/q/208405/102029 and several other related questions. Searching ask ubuntu http://askubuntu.com/search?q=need+to+load+kernel+first+ confirms a recnt increase in these queries on differing hardware so this is almost a certain bug. Doing ls -l after dropping to command prompt when getting UEFI grub screen ref https://help.ubuntu.com/community/UEFI#Identifying_if_the_computer_boots_the_HDD_in_EFI_mode confirms cd0,apple1 and cd0apple2 images are detected and might go some way to explaining why they are not usable on an amd 64 platform. running lsefisystab here also indicates EFI ver 1.1. rev 2 rEFInd sees this firmware as UEFI 2.1 which goes to completely confirm this is not Secure Boot capable system. Confirm Christopher M. Penalver's workaround does work but i do not see this as afull solution due to the lack of being to use efibootmgr when booting live session- which has to be with EFI off due to installer bug. No efi = no efibootmgr. If dual booting with windows using this workaround will mean having to simply create grub_bios partition, install grub-efi and possibly rename windows bootfmgr to trick firmware to booting grub-efi. Using boot-repair seems to be the accepted and easiest way of doing this but has hugely varying success rates. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1072378 Title: [Asus Eee PC 1015BXO] Ubuntu 12.10 EFI support is not ready To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1072378/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
