Bug 894300 - Grub won't boot older kernels without support of EFI handover
Summary: Grub won't boot older kernels without support of EFI handover
Alias: None
Product: Fedora
Classification: Fedora
Component: grub2
Version: 18
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Peter Jones
QA Contact: Fedora Extras Quality Assurance
Depends On: 860909
TreeView+ depends on / blocked
Reported: 2013-01-11 11:18 UTC by Lingzhu Xiang
Modified: 2020-09-10 09:16 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 860909
Last Closed: 2014-02-05 14:43:39 UTC
Type: Bug

Attachments (Terms of Use)

Description Lingzhu Xiang 2013-01-11 11:18:28 UTC
Description of problem:

GRUB2 forces a kernel version check for the EFI handover protocol added in 3.6. This makes older EFI kernels unable to boot in EFI environment.

Introduced here http://pkgs.fedoraproject.org/cgit/grub2.git/tree/grub2-linuxefi.patch

+  if (lh.version < grub_cpu_to_le16 (0x020b))
+    {
+      grub_error (GRUB_ERR_BAD_OS, N_("kernel too old"));
+      goto fail;
+    }

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Install a older kernel.
2. Reboot.

Actual results:
Loading Fedora (3.5.6-1.fc17.x86_64)
Secure boot not enabled
error: kernel too old.
Loading initial ramdisk ...
error: you need to load the kernel first.

Press any key to continue...

Expected results:
The kernel is booted.

Comment 1 Prarit Bhargava 2013-01-22 02:23:12 UTC
I feel like this should have a higher priority.  If you're like me ;) and you keep a "backup"/safe/known-good kernel on a system this results in the known-good kernel not booting.

In my case, I upgraded to F18 and the base F18 kernel would not boot.  I then went back to the old known-good F17 kernel and it wouldn't boot.

... which now means I have a brick for a laptop.  It's a good thing that I don't keep irreplaceable data on my laptop otherwise I'd be screaming at someone right now ;)


Comment 2 Prarit Bhargava 2013-01-22 02:27:39 UTC
... I wonder if the "fix" here is to update the F17 kernel to latest, verify it boots, and then update the rest of the system?

Either way, I can't possibly be the only one in this mess...


Comment 3 Peter Jones 2013-04-03 18:03:42 UTC
The fix here is probably to use "linux" and "initrd" instead of "linuxefi" and "initrdefi" on those old kernels, but right now there's not an easy way to detect that from grub2-mkconfig.

Comment 4 Peter Jones 2013-04-03 18:10:36 UTC
Even once that's done, you're going to hit EFI bugs where the answer is "you need to use a newer kernel and 'linuxefi'".

Comment 6 Fedora End Of Life 2013-12-21 10:19:37 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 7 Fedora End Of Life 2014-02-05 14:43:45 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.