# TPM delaying boot sequence

**URL:** <https://forum.endeavouros.com/t/tpm-delaying-boot-sequence/57050>\
**Category:** Kernel, boot, graphics & hardware\
**Created:** [June 22, 2024, 7:50am UTC](https://forum.endeavouros.com/t/tpm-delaying-boot-sequence/57050 "2024-06-22T07:50:11Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![LDC](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/l/ecae2f/32.png) [@LDC](https://forum.endeavouros.com/u/LDC)\
**Post date:** [June 22, 2024, 7:50am UTC](https://forum.endeavouros.com/t/tpm-delaying-boot-sequence/57050/1 "2024-06-22T07:50:11Z")

</div>

The latest update messed with TPM, as it now hangs during boot. After a quick research, it looks like my options are to either blacklist or disable it entirely. Before doing so, I’d like to know if it has any practical use in the daily life of on Arch-based distro. Any idea?

---

<div class="post-metadata">

**Author:** ![mihalycsaba](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/mihalycsaba/32/70916_2.png) [@mihalycsaba](https://forum.endeavouros.com/u/mihalycsaba)\
**Post date:** [June 22, 2024, 9:39am UTC](https://forum.endeavouros.com/t/tpm-delaying-boot-sequence/57050/2 "2024-06-22T09:39:36Z")

</div>

Just disable it, unless you encrypted your drive

---

<div class="post-metadata">

**Author:** ![LDC](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/l/ecae2f/32.png) [@LDC](https://forum.endeavouros.com/u/LDC)\
**Post date:** [June 22, 2024, 10:14am UTC](https://forum.endeavouros.com/t/tpm-delaying-boot-sequence/57050/3 "2024-06-22T10:14:30Z")

</div>

fine, thought that was Windows-only “feature” (never bothered investigating TPM tbh). Thanks

---

<div class="post-metadata">

**Author:** ![pebcak](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/pebcak/32/100472_2.png) [@pebcak](https://forum.endeavouros.com/u/pebcak)\
**Post date:** [June 22, 2024, 10:54am UTC](https://forum.endeavouros.com/t/tpm-delaying-boot-sequence/57050/4 "2024-06-22T10:54:09Z")

</div>

A similar issue was reported here as well:

> [@A start job is running for /dev/tpmrm0 times out](https://forum.endeavouros.com/t/a-start-job-is-running-for-dev-tpmrm0-times-out/56898):
>
> I now have to wait for the start job to timeout after updating my system, disabling TPM fixes the issue but I would rather still have it on, going on fallback has the same issue.

---

<div class="post-metadata">

**Author:** ![mihalycsaba](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/mihalycsaba/32/70916_2.png) [@mihalycsaba](https://forum.endeavouros.com/u/mihalycsaba)\
**Post date:** [June 22, 2024, 11:15am UTC](https://forum.endeavouros.com/t/tpm-delaying-boot-sequence/57050/5 "2024-06-22T11:15:13Z")

</div>

It’s kinda useless on a regular desktop setup in my opinion. I’m not sure but I think it’s only useful if you encrypt your drives. But I don’t like relying on these hardware features, they are buggy. Secure boot is even worse and more useless. Just try to disable it from the firmware.

---

<div class="post-metadata">

**Author:** ![LDC](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/l/ecae2f/32.png) [@LDC](https://forum.endeavouros.com/u/LDC)\
**Post date:** [June 22, 2024, 11:37am UTC](https://forum.endeavouros.com/t/tpm-delaying-boot-sequence/57050/6 "2024-06-22T11:37:28Z")

</div>

ofc never used that, I was in fact surprised to find it active at all on this system (it’s not my main PC, which also has EOS). Anyway, just disabled and everything runs smoothly as always.