On Mon, May 16, 2016 at 08:15:29PM -0000, Mathieu Trudel-Lapierre wrote: > I'm not convinced that this isn't an EFI system.
> The CD used here looks like it was booted in EFI mode: > [ 0.000000] Command line: BOOT_IMAGE=/casper/vmlinuz.efi > file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash --- This is not evidence of an EFI boot. There is only a single vmlinuz image on the CD, used by both BIOS and EFI boot. There is no reason to have two separate vmlinuz images, and it doesn't matter that it's called 'vmlinuz.efi'. > And that there was some EFI data available to the system as ESRT: > [ 0.000000] efi: EFI v2.31 by American Megatrends > [ 0.000000] efi: ESRT=0xbbf56898 ACPI=0xba7df000 ACPI 2.0=0xba7df000 > SMBIOS=0xf04c0 MPS=0xfd4d0 > [ 0.000000] esrt: Reserving ESRT space from 0x00000000bbf56898 to > 0x00000000bbf568d0. I don't know how the kernel decides whether to initialize these drivers. It's possible that this does point to the system having been booted under EFI mode. But maybe it's also possible that the system was booted in CSM mode. -- 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
