Oh, good point. I was operating under the false assumption that we did ship two separate copies of the kernel as on the installed system.
Still, there is no reason for the system to ever try to run efibootmgr / install grub-efi-amd64 unless it detects being booted in EFI mode, and where /sys/firmware/efi being available. What we're getting here is that it may be that just checking if /sys/firmware/efi exists isn't sufficient to tell whether we're really on an EFI system. Benjamin, if you boot the CD normally to get on the live system, could you then check if there are files under /sys/firmware/efi? If there are files populated by the kernel, but efivar reports that EFI variable support is absent (ie. some variable handling operations are unavailable), then we'll know what piece of the installer to look at. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1582320 Title: Problem detected upon boot/login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1582320/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
