Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GRUB errors out on boot due to TPM module errors #353

Open
allaeddineomc opened this issue Sep 18, 2022 · 23 comments
Open

GRUB errors out on boot due to TPM module errors #353

allaeddineomc opened this issue Sep 18, 2022 · 23 comments
Labels
bug Something isn't working f39 Related to Fedora 39 f40 Related to Fedora 40

Comments

@allaeddineomc
Copy link

This issue tracker is intended only for Silverblue specific issues. We would like to ask you to try to reproduce the issue on a relevant Fedora Workstation release. If you will be able to reproduce there, then please report it in Red Hat Bugzilla (see How to file a bug) or in upstream (preferred for GNOME projects) and not in this issue tracker.

Describe the bug
grub errors out on boot with a tpm error after yesterday's update for f37 , the error was present for some time in f35

To Reproduce
rpm-ostree update
reboot

Expected behavior
boots with no errors

Screenshots
If applicable, add screenshots to help explain your problem.

OS version:

State: idle
BootedDeployment:
● fedora:fedora/37/x86_64/silverblue
                  Version: 37.20220917.n.0 (2022-09-17T08:40:50Z)
               BaseCommit: b8c2ee6d796392558966f93a665c46fc681bf0033660234d166556c8c7641170
             GPGSignature: Valid signature by ACB5EE4E831C74BB7C168D27F55AD3FB5323552A

Additional context
a quick workaround (not really a solution) :
on boot keep smashing up or down arrows for the grub menu to show
press "c"
type these commands
rmmode tpm
normal
the menu will show again but now it will boot properly

@allaeddineomc allaeddineomc added the bug Something isn't working label Sep 18, 2022
@allaeddineomc
Copy link
Author

today's update updated grub , the issue is still present

@travier travier added the f37 Related to Fedora 37 label Sep 19, 2022
@travier
Copy link
Member

travier commented Sep 19, 2022

This is likely an upstream GRUB bug or a firmware bug. Please file it in Bugzilla.

@travier travier added the upstream Issue reported, fixed or related to upstream projects label Sep 19, 2022
@travier travier changed the title grub TPM error GRUB errors out on boot due to TPM module errors Sep 19, 2022
@allaeddineomc
Copy link
Author

can't access my fedora account anymore , please someone else report it

@travier
Copy link
Member

travier commented Sep 19, 2022

It's likely specific to your hardware so I would recommend that you create a new account to report it.

@allaeddineomc
Copy link
Author

bug reported on bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2128485
i guess this issue can be closed here

@travier
Copy link
Member

travier commented Sep 21, 2022

Closing as the next steps will happen in Bugzilla.

@travier travier closed this as not planned Won't fix, can't repro, duplicate, stale Sep 21, 2022
@travier
Copy link
Member

travier commented Jan 4, 2023

Workaround until this is fixed in GRUB:

$ cat /etc/grub.d/02_notpm 
#!/usr/bin/sh -e
cat << EOF
rmmod tpm
EOF

Then update the system and the GRUB config will be regenerated.

@travier
Copy link
Member

travier commented Mar 27, 2023

Error message to help with searches:

../../grub-core/commands/efi/tpm.c:148:Unknown TPM error.

@rickatnight11
Copy link

The Bugzilla issue got closed incorrectly as a kernel fix, so not sure what the next steps here are for an actual fix.

@travier
Copy link
Member

travier commented Mar 28, 2023

The best path is to reply in the BZ that this is not fixed and I'll re-open it.

@travier
Copy link
Member

travier commented Mar 28, 2023

Note that this is marked "fixed" in F38.

@rickatnight11
Copy link

Thanks, @travier! I did comment on the BZ, which is still closed. Where do you see this marked as fixed in F38?

@travier
Copy link
Member

travier commented Mar 29, 2023

https://bugzilla.redhat.com/show_bug.cgi?id=2128485#c9 mentions F37. Did you try with Fedora 38? Note that the bootloader is also not updated yet in Silverblue. See: #120

@rickatnight11
Copy link

I've only been using and experiencing this issue on Fedora Silverblue 37. 38 isn't out yet, to my knowledge. I don't see any reference to where this issue is fixed in 38. I just have the above BZ reporting it for 37, then marking it closed as resolved as of a specific kernel version, which doesn't seem correct.

@jlaham
Copy link

jlaham commented May 13, 2023

FWIW, still seeing this with f38.

State: idle
Deployments:
● fedora:fedora/38/x86_64/silverblue
                  Version: 38.20230513.0 (2023-05-13T00:46:58Z)
               BaseCommit: 0cb2293657eaba7b89c1c62d74fd69f6c7c42fe31b0df16fbae8708202377ab0
             GPGSignature: Valid signature by 6A51BBABBA3D5467B6171221809A8D7CEB10B464

@travier
Copy link
Member

travier commented May 15, 2023

Note that this will likely not be fixed until we have #120.

Since that's on our end now, I'll re-open this issue.

@travier travier reopened this May 15, 2023
@travier travier added f38 Related to Fedora 38 need-info Further information is requested and removed upstream Issue reported, fixed or related to upstream projects labels May 15, 2023
@rickatnight11
Copy link

I'm not sure why this blocks on implementing bootupd and removing ostree-grub2. I believe this needs to be fixed in the tpm module in grub2 (I think it doesn't handle the older TPM on some Asus Zenbooks). Can we get the related bugzilla re-opened?

@travier
Copy link
Member

travier commented Jul 15, 2023

If the bug is fixed in a newer GRUB version then we need bootloader updates. Silverblue systems don't update the bootloader right now which is why we need bootupd.

@rickatnight11
Copy link

Ah, that makes sense for this issue tracker. I've learned how to update the bootloader, myself, and new installs would at least benefit before bootupd is implemented.

It's not clear to me that the core grub issue is being tracked, though, since the bugzilla was closed. Are you able to reopen it?

@travier
Copy link
Member

travier commented Jul 17, 2023

Can you verify that this is still an issue from a fresh Fedora 38 installation and comment in the Bugzilla?

@rickatnight11
Copy link

Yes, confirmed it's still an issue and commented on the bugzilla.

@travier travier removed the need-info Further information is requested label Jul 17, 2023
@travier travier removed the f37 Related to Fedora 37 label Nov 24, 2023
@travier
Copy link
Member

travier commented Nov 24, 2023

I think this is still an issue on F39 but if someone affected could confirm that would be great. Thanks

@rickatnight11
Copy link

Can confirm, still on f39.

@travier travier added the f39 Related to Fedora 39 label Nov 24, 2023
@travier travier added f40 Related to Fedora 40 and removed f38 Related to Fedora 38 labels Apr 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working f39 Related to Fedora 39 f40 Related to Fedora 40
Projects
None yet
Development

No branches or pull requests

4 participants