OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
boot-kernel critical occasional DISPUTE

Boot/reboot loop when the TPM is present but unresponsive (systemd-pcrphase)

omarchyarchliminesystemd-boottpmlaptop
CORRECTED An auditor found the fix wrong or incomplete and rewrote it.
AUDIT NOTE

Issue 8190 is real and the record reproduces its journal excerpt faithfully (the issue also shows the 'Forcibly rebooting' line that explains the loop). The workaround is the one confirmed upstream. What is missing is a safety warning that makes the difference between a fix and a lockout: if the machine uses TPM-backed LUKS unlock (systemd-cryptenroll --tpm2-device), disabling the Security Chip in firmware removes the unlock path, and masking the pcrphase units changes PCR values so TPM-sealed secrets no longer unseal. On a laptop whose owner set up TPM auto-unlock and does not remember the recovery passphrase, this advice ends the session at an unopenable LUKS prompt.

The cause above was not rewritten and may still contain the error described. The fix below is the corrected version.
RISK

If you have enrolled a LUKS key against the TPM (systemd-cryptenroll --tpm2-device), disabling or clearing the TPM makes that key unusable and you must unlock with your passphrase. Never clear the Security Chip without first confirming you still know a working LUKS passphrase.

Symptom

Omarchy 4.0.0 installs cleanly on a ThinkPad T470, reaches the login screen, accepts the password, shows a loading state, and then reboots back to Limine. Loop repeats forever. The journal from the failed boot shows:


tpm tpm0: TPM0: Operation timed out
Failed to create TPM2 context: State not recoverable
systemd-pcrphase-sysinit.service: Main process exited, code=exited, status=1

Cause

systemd-pcrphase-sysinit.service tries to extend TPM PCRs during early boot. When the TPM chip is present in firmware but unresponsive (timeouts, I/O errors, invalid status), the unit fails hard and the failure cascades into a forced reboot rather than degrading gracefully. Tracked as basecamp/omarchy#8190.

Fix

**Before touching the TPM, check whether anything is sealed to it.** If a TPM2 keyslot is enrolled, disabling the chip removes your unlock path:


sudo cryptsetup luksDump /dev/nvme0n1p2 | grep -A3 -i 'tpm2\|Tokens'
sudo systemd-cryptenroll /dev/nvme0n1p2      # lists enrolled slots

If a TPM2 token is listed, make sure you have a working passphrase or recovery key **and have tested it** before continuing.

The confirmed workaround is to hide the TPM in firmware:

  • ThinkPad BIOS: **Security -> Security Chip -> Disabled**. Do **not** Clear the Security Chip. Clearing destroys sealed keys irreversibly. Disabling is reversible.

To break the loop before you can reach firmware, at the Limine menu press e and append to the cmdline: line for one boot:


systemd.mask=systemd-pcrphase-sysinit.service systemd.mask=systemd-pcrphase.service

Once booted, persist it:


sudo systemctl mask systemd-pcrphase-sysinit.service systemd-pcrphase.service systemd-pcrphase-initrd.service

Note this changes the PCR measurements, so any secret sealed to a PCR policy (TPM LUKS unlock, systemd-creds) will stop unsealing. Re-enroll with systemd-cryptenroll --wipe-slot=tpm2 --tpm2-device=auto after the TPM is working again, or leave TPM unlock off on this machine. Attach journalctl -b -1 to issue #8190.

Verify

systemctl --failed lists no systemd-pcrphase* units and the machine survives three consecutive cold boots to the desktop.

Sources

tpm-unresponsive-reboot-loop