and when it doesn't like HD(5,MBR...) entry and has no other entries it
tries to "autogenerate" the entry and injects it into bootorder and
then boot loops and then the entries pile up
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
So i don't think efibootmgr generates "right" entries for ESP on
extended mbr partition.
or maybe it should learn to generate HD(2,MBR)/HD(1,MBR)
And/or maybe we shouldn't put ESP on the extended partition if we can /
have primary partitions available.
** Also affects: efibootmgr
So we have zeroed these out. And we have now done bios-mbr install, and
then side-by-side install in uefi mode with mok util.
1) mok util did not register a `correct` esp boot path, it pointed at
\efi\boot\mmx64.efi but that is a wrong path, as it should be at
\efi\ubuntu\mmx64.efi.
2) the
Jean-Baptiste, your efibootmgr -v output shows no fewer than 18 boot
entries for Ubuntu. That didn't happen as a result of a single install
of Ubuntu ( I hope). I think Dimitri's suggestion is that you zero
these out, either with efibootmgr or from the firmware UI, to see if the
system is
@Dimitri, what do you mean by "Clearing all the boot entries" ? I didn't
do anything but installing this machine with ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796260
Title:
UEFI
with persistent uefi vars, it rebooted into uefi system fine.
I'd recommend clearing all of your boot entries
** Changed in: grub2 (Ubuntu)
Status: Incomplete => Invalid
** Changed in: ubiquity (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you
@jibel
you really should clear all the boot entries, you may be overflowing.
@steve
it is quite easy to give an nvram to the VM, but i think we have a spare
laptop here that can do legacy & uefi, we'll retest this there.
--
You received this bug notification because you are a member of Ubuntu
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1796260
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
output of efibootmgr -v:
BootCurrent: 0017
Timeout: 0 seconds
BootOrder: 0002,0003,0004,0005,0006,0017,0018
Boot* ubuntu
HD(5,MBR,0x39a7181f,0x0,0x0)/File(\EFI\ubuntu\shimx64.efi)
Boot0001* ubuntu
