Okay, this is crazy but I ACCIDENTALLY fixed this issue today by fixing another issue that my system was having, and given how on a surface level the two issues shouldn’t be related I am starting to wonder if I have found a bug possibly…
Anyway, here is my solution to THIS problem mentioned in THIS Forum Post, run the following command;
systemctl mask dev-tpmrm0.device
You can find info on how I came to discover this command by reading my other issue post here:
Now here is some context in case that post above ever gets deleted or goes missing (I will try to back them up using the Wayback Machine just so that it can benefit others hopefully in the future!).
The issue seem to be indirectly (or maybe directly, I don’t know for sure) linked to the TPM 2.0 Module of the Linux Kernel, or at least some part of it, and strangely this issue has been a thorn in my side for years but didn’t actually provide any context in the Kernel Boot-Up Output until I purchased & installed a dedicated TPM 2.0 Hardware Module onto my motherboard.
By installing the TPM 2.0 Physical Hardware Module (NOT the Linux Kernel Module) I managed to get the kernel to start outputting information which has then lead to me ultimately working out what is broken and how to at the very least work around the issue until it can be properly fixed.
I say this as I don’t think that this is meant to happen when you install but don’t actually use a TPM 2.0 Hardware Module, it should just be ignored but clearly it isn’t, or at least it isn’t ignored fully.
Hopefully this helps someone out!