TPM2.0 still broken on Fedora 44?

Ask Fedora
,
1

Is tpm 2.0 still broken under Fedora44? If I swtch TPM 2.0 on booting takes forever

[Wed Aug 26 09:46:41 2026] systemd[1]: Expecting device dev-tpm0.device - /dev/tpm0…
[Wed Aug 26 09:46:41 2026] systemd[1]: Expecting device dev-tpmrm0.device - /dev/tpmrm0…
[Wed Aug 26 09:47:27 2026] systemd[1]: Expecting device dev-tpm0.device - /dev/tpm0…
[Wed Aug 26 09:47:27 2026] systemd[1]: Expecting device dev-tpmrm0.device - /dev/tpmrm0…

Or can I mask tpm service



systemctl mask dev-tpmrm0.device

EDIT : Masking has no effect on boot time. So this is wrong

2

On my systems with a TPM2 everything works.
But I did find this bug report - systemd-tpm2-setup delays boot by ~30 seconds · Issue #42615 · systemd/systemd · GitHub

If you have the TPM enabled what does this report?

journalctl -b 0 -g tpm

On my system I see this at the start of the output:

2026-08-26T11:21:15+01:00 kernel: efi: ACPI=0x7851e000 ACPI 2.0=0x7851e014 TPMFinalLog=0x7864c000 SMBIOS=0x79d2e000 SMB>
2026-08-26T11:21:15+01:00 kernel: ACPI: TPM2 0x0000000078352000 00004C (v04 ALASKA A M I    00000001 AMI  00000000)
2026-08-26T11:21:15+01:00 kernel: ACPI: Reserving TPM2 table memory at [mem 0x78352000-0x7835204b]
2026-08-26T11:21:15+01:00 systemd[1]: systemd 259.8-1.fc44 running in system mode (+PAM +AUDIT +SELINUX -APPARMOR +IMA >
2026-08-26T11:21:15+01:00 systemd[1]: systemd-pcrphase-initrd.service - TPM PCR Barrier (initrd) skipped, unmet conditi>
2026-08-26T11:21:16+01:00 systemd[1]: Condition check resulted in dev-tpmrm0.device - /dev/tpmrm0 being skipped.
2026-08-26T11:21:16+01:00 systemd[1]: Expecting device dev-tpm0.device - /dev/tpm0...
2026-08-26T11:21:16+01:00 systemd[1]: Found device dev-tpm0.device - /dev/tpm0.
2026-08-26T11:21:16+01:00 systemd[1]: Reached target tpm2.target - Trusted Platform Module.
2026-08-26T11:21:26+01:00 systemd[1]: Stopped target tpm2.target - Trusted Platform Module.
3

In the end they might “work” but boot time increases by a full minute when switched on.

I will test this on my GA-170z Gaming 7

4

Did you read through that bug report about the 30s delay?
Maybe add your experience to the bug report?