Bug 1626817 - 2.02-54 still broken here with EFI/Lenovo x250
Summary: 2.02-54 still broken here with EFI/Lenovo x250
Keywords:
Status: CLOSED DUPLICATE of bug 1626844
Alias: None
Product: Fedora
Classification: Fedora
Component: grub2
Version: rawhide
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Peter Jones
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-09-09 07:49 UTC by dac.override
Modified: 2018-09-11 07:08 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-09-11 07:08:57 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1626844 0 unspecified CLOSED grub2-2.02-54.fc29 fails to boot, drops to grub shell 2021-02-22 00:41:40 UTC

Internal Links: 1626844

Description dac.override 2018-09-09 07:49:59 UTC
Description of problem:
Boots straight to "grub>", `ls` shows no partitions

Issue started with 2.02-53 and https://src.fedoraproject.org/rpms/grub2/c/1b51084aaa0ecb77a43979d8cb1d5956bd32da95?branch=master did not fix it for me

Downgrading to 2.02-51 fixes the issue

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

How reproducible:
update grub2 and reboot

Steps to Reproduce:
1. update grub2
2. reboot
3.

Actual results:
grub>

Expected results:
! grub>

Additional info:

Comment 1 Branko Grubić 2018-09-09 09:37:44 UTC
I know this is rawhide bug, but the same grub2 package is in f29 I guess (different build, but same patches ...). This again breaks the boot on my x220, same issue as in original report ^^, I only get the grub shell/commandline. My system i set to EFI mode only (no secure boot, not supported). Downgrading to -51, makes it work again.

Comment 2 Adam Williamson 2018-09-11 07:08:57 UTC
We don't really need two bugs for this.

*** This bug has been marked as a duplicate of bug 1626844 ***


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