Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use last signed grub for 32bit kernels #3

Closed
alkisg opened this issue Oct 27, 2020 · 2 comments
Closed

Use last signed grub for 32bit kernels #3

alkisg opened this issue Oct 27, 2020 · 2 comments

Comments

@alkisg
Copy link
Owner

alkisg commented Oct 27, 2020

Secure boot in Ubuntu works like this:

  • 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.

@alkisg
Copy link
Owner Author

alkisg commented Oct 27, 2020

@alkisg
Copy link
Owner Author

alkisg commented Dec 14, 2020

Fixed in the 20.10 liveusb release.

@alkisg alkisg closed this as completed Dec 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant