Bug 1582811

Summary: F28 Workstation, GRUB loader bug : After booting in Windows, then Linux, there is a "TPM Error 2"
Product: [Fedora] Fedora Reporter: Andre Gompel <agompel>
Component: grub2Assignee: Peter Jones <pjones>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 28CC: hdegoede, lkundrak, pjones
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-06-14 21:27:27 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Andre Gompel 2018-05-27 00:47:59 UTC
Description of problem:
------------------------

In Fedora 28 Workstation, the GRUB loader is buggy.
After booting in Windows, there is a "TPM Error 2" when booting Fedora,
    and then system hangs. 


Version-Release number of selected component (if applicable):
 Fedora 28 Workstation X86_64

How reproducible:
    SOLID

Steps to Reproduce:
1.  Install Fedora 28 x86_64, with a Windows 10 Partition
2.  Boot Fedora : it works, boots normally
3.  Boot Windows 10: it works, boots normally, but modify TPM register
4.  Boot Fedora : it fails with "TPM Error 2"... and hangs!

Actual results:
Need to reset the BIOS, clear the TPM to be able to boot again !

Expected results:


Additional info:
-----------------

  1) Matt Garrett documented this issue one year ago, as :

https://bugzilla.redhat.com/attachment.cgi?id=1160008&action=diff

  2) A nice workaround may be to use an older, Fedora 27 set of packages for Grub, but dependencies problems are complex...

  3) Grub-customizer does not work, but the grub-customizer package from Fedora 27, seems to work juts fine : a simple workaround...

Comment 1 Hans de Goede 2018-06-14 21:27:27 UTC

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