You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
UEFI loads /boot/efi/EFI/Boot/BOOTX64.EFI. This needs to be signed by Microsoft.
In Ubuntu, this is the same as the /usr/lib/shim/shimx64.efi.signed file that is shipped by the shim-signed package.
Shim-signed contains Canonical's grub keys and is able to load their own signed grub, /boot/efi/EFI/ubuntu/grubx64.efi. This is the same as the /usr/lib/grub/x86_64-efi-signed/grubx64.efi.signed file that is shipped by the grub-efi-amd64-signed package.
AFAIK, shimx64.efi.signed doesn't contain the keys of other distributions and isn't able to directly boot Debian or Fedora kernels. Liveusb requires that secure boot is disabled in this case.
Up to grub2 version 2.04-1ubuntu21, grub was able to load a 32 bit kernel under UEFI, although not under secure boot. After that version loading for example lubuntu-18.04-desktop-i386.iso under UEFI won't work, with the following error message:
"error: kernel doesn't support 64-bit CPUs"
So, a new liveusb version will be released that will be based on Ubuntu's grub 2.04-1ubuntu21 packages, and it will keep using that version until booting 32bit kernels under UEFI isn't needed anymore.
The text was updated successfully, but these errors were encountered:
Secure boot in Ubuntu works like this:
Up to grub2 version 2.04-1ubuntu21, grub was able to load a 32 bit kernel under UEFI, although not under secure boot. After that version loading for example lubuntu-18.04-desktop-i386.iso under UEFI won't work, with the following error message:
So, a new liveusb version will be released that will be based on Ubuntu's grub 2.04-1ubuntu21 packages, and it will keep using that version until booting 32bit kernels under UEFI isn't needed anymore.
The text was updated successfully, but these errors were encountered: