GNU GRUB - Bugs: bug #58300, GRUB refuses to boot a 32-bit...
You are not allowed to post comments on this tracker with your current authentication level.
bug #58300: GRUB refuses to boot a 32-bit kernel when in EFI mode
Submitter: | Hamish McIntyre-Bhatty <hamishmb> | ||
Submitted: | Mon 04 May 2020 11:12:15 AM UTC | ||
Category: | Booting | Severity: | Major |
Priority: | 5 - Normal | Item Group: | Software Error |
Status: | None | Privacy: | Public |
Assigned to: | None | Originator Name: | Hamish McIntyre-Bhatty |
Open/Closed: | Open | Release: | 2.02 |
Release: | Reproducibility: | Every Time | |
Planned Release: | None |
Mon 04 May 2020 02:07:34 PM UTC, comment #2: |
Hamish McIntyre-Bhatty <hamishmb> |
Mon 04 May 2020 01:01:58 PM UTC, comment #1: NOTE: Doesn't seem to happen with grub 2.04 as found in Debian Bullseye, so this might be an Ubuntu problem. |
Hamish McIntyre-Bhatty <hamishmb> |
Mon 04 May 2020 11:12:15 AM UTC, original submission:
Note that this is with BIOS and UEFI images created from Ubuntu 18.04's current version of GRUB (*2.02-2ubuntu8.15*). If it would be more useful for me to submit for Ubuntu instead/as well then I'll do that.
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? |
Hamish McIntyre-Bhatty <hamishmb> |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Also reported at https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1876737