[Bug 1876737] Re: GRUB refuses to boot a 32-bit kernel when in EFI mode

pemartins 1876737 at bugs.launchpad.net
Wed Aug 19 10:36:02 UTC 2020


I really thought, because I've read and heard so many times about it,
that the Linux world was about freedom. Well, can't really say that
someone imposing that other people were from now on prohibited from
running 32 bits operating systems in an updated 64 bits
grub/uefi/whatever suits that...

I've been running on my laptop, for the last many years, 32 bits Android-x86 based operating systems because the 64 bits ones won't work due to my cpu lacking sse 4.1 and 4.2. But thanks to the awesome Linux freedom, I can now choose not to do it anymore... you know, because I can't do it anymore.
No worries, at least this is great for having a laugh!

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to grub2 in Ubuntu.
https://bugs.launchpad.net/bugs/1876737

Title:
  GRUB refuses to boot a 32-bit kernel when in EFI mode

Status in grub2 package in Ubuntu:
  Won't Fix

Bug description:
  Also reported at https://savannah.gnu.org/bugs/index.php?58300, but
  doesn't occur in Debian's v2.04 from Bulleye, and only occurred in the
  last few months, so it might be an Ubuntu bug.

  This is grub version 2.02-2ubuntu8.15 as reported by "apt show grub-
  efi"

  GRUB2 fails to boot a 32-bit kernel when started in EFI mode (64-bit
  EFI) on a 64-bit x86 CPU, and gives the message:

  "error: kernel doesn't support 64-bit CPUs"

  However, when a bios grub image made by the same version of grub is
  used, with the same kernel, on the same CPU, everything is normal and
  the kernel boots as expected.

  Hence, I know this kernel will boot on a 64-bit CPU, and with a
  previous version of GRUB 2 (unfortunately I don't know which version),
  it also booted fine in 64-bit mode using GRUB-EFI.

  Running with debug=all doesn't seem to provide any extra useful
  information, as far as I can tell - it just lists sectors being read
  and then freed.

  Any ideas as to what's going on?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1876737/+subscriptions



More information about the foundations-bugs mailing list