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

Boot stalls 90 seconds on 'Timed out waiting for device /dev/tpmrm0'

archomarchyendeavouroscachyosmanjarosystemdtpmlaptopdesktop
CORRECTED An auditor found the fix wrong or incomplete and rewrote it. · checked against Omarchy omarchy 4.0.4-1 on 2026-10-05
AUDIT NOTE

bbs 296699 carries the exact journal lines, the tpm_crb ACPI region error -16, systemd 256-1-arch, and both mask fixes (tpm2.target and dev-tpmrm0.device). bbs 297009 adds the tpm_tis error -1 case and a 30 to 40 second wait. systemd 261's NEWS lists systemd-tpm2-generator and tpm2.target under 'CHANGES WITH 256', and systemd-tpm2-generator(8) on this machine documents systemd.tpm2_wait= with false meaning the target is not inserted even if the firmware reported a device. omarchy-pkgs#677 supports the linux-omarchy 7.2.5-3 Broadwell PTT cross-reference. It is still open, the reporter confirmed 7.2.7rc1 fixes it, and the local omarchy sync database (dated 2026-09-18) still offers 7.2.5-3. The Omarchy branch writes a KERNEL_CMDLINE[default]+= drop-in into /etc/limine-entry-tool.d, which matches the shape of /etc/limine-entry-tool.d/omarchy-defaults.conf. The one defect is that the symptom puts a paraphrase in quotation marks as if it were a user's words. No source contains that sentence, so the symptom is rewritten without the quote. Not exercised: no parameter was applied and no unit was masked.

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

Masking tpm2.target or passing systemd.tpm2_wait=0 on a machine that unlocks LUKS through the TPM can make the unlock run before the TPM is ready, so you fall back to the passphrase or the boot fails. Only apply it where the TPM is unused or absent.

Symptom

After an update, boot sits on a black screen with a blinking cursor for 30 to 90 seconds before the login screen. The journal shows:


systemd[1]: Expecting device /dev/tpmrm0...
systemd[1]: dev-tpmrm0.device: Job dev-tpmrm0.device/start timed out.
systemd[1]: Timed out waiting for device /dev/tpmrm0.
systemd-tpm2-setup[784]: No complete TPM2 support detected, exiting gracefully.

usually after a kernel line such as:


tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer.
tpm_crb MSFT0101:00: probe with driver tpm_crb failed with error -16

Cause

systemd-tpm2-generator makes sysinit.target wait on tpm2.target when the firmware reports a TPM2 but the kernel has not exposed one yet. This arrived with systemd 256 in June 2024. When the kernel driver fails to probe (a firmware ACPI region bug, tpm_tis error -1, or a TPM disabled in a way the firmware still advertises), the device never appears, and systemd waits for the full device timeout before giving up. On Omarchy's linux-omarchy 7.2.5-3, a separate cause gives the same symptom on Broadwell machines with Intel PTT: see linux-omarchy-intel-iommu-default-on-boot-failures.

Fix

First decide whether you use the TPM at all, for example for LUKS auto-unlock with systemd-cryptenroll. If you do, fix the firmware side instead (BIOS update, or TPM enabled properly under Security > TPM 2.0).

## Tell the generator not to wait (preferred)

The kernel parameter systemd.tpm2_wait=0 is documented in systemd-tpm2-generator(8) for exactly this case.

Omarchy 4:


echo 'KERNEL_CMDLINE[default]+=" systemd.tpm2_wait=0"' | sudo tee /etc/limine-entry-tool.d/tpm2-nowait.conf
sudo limine-mkinitcpio

Plain Arch with GRUB: add systemd.tpm2_wait=0 to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub, then sudo grub-mkconfig -o /boot/grub/grub.cfg. With systemd-boot, append it to the options line in /boot/loader/entries/*.conf.

## Or mask the wait (the forum fix)


sudo systemctl mask tpm2.target
# one reporter masked the device unit instead:
# sudo systemctl mask dev-tpmrm0.device

If you have no TPM and the firmware still advertises one, disabling the TPM in firmware setup also removes the wait.

Verify

journalctl -b | grep -i tpmrm0 shows no timeout, and systemd-analyze reports userspace time down by roughly the old wait. systemd-analyze critical-chain no longer lists dev-tpmrm0.device.

Sources

tpmrm0-timeout-slow-boot