Error time out waiting for device /dev/tpmrm0

Axios

whats your hardware?

Korfou

Here

`Ordinateur
Processeur AMD A8-7410 with AMD 1 processeur physique; 4 coeurs; 4 threads
Mémoire 7045MB (2997MB utilisées)
Type de machine Notebook
Systeme d'exploitation Solus 4.8

Date/Heure	mer. 19 nov. 2025 10:32:05

Affichage
Résolution 1600x900 pixels
Display Adapter AMD/ATI Mullins + AMD/ATI Topaz XT
OpenGL Rendu AMD Radeon R5 Graphics (radeonsi, kabini, ACO, DRM 3.64, 6.17.8-324.current)
Serveur d'affichage de session The X.Org Foundation 21.1.20
Matériels Audio
Adapteur Audio HDA-Intel - HDA ATI HDMI
Adapteur Audio HDA-Intel - HD-Audio Generic`

TraceyC

This is a system error, at a lower level than XFCE. After a brief internet search I found this thread on the Arch Linux forums that might help.

Korfou

TraceyC

I followed the instructions in the link.
The command removes what is in the second image, but not what is in the first image.

To clarify, when you see the first image, it takes 20 seconds to complete this step, and only then does the start-up process begin.

cornbean

sudo systemctl mask dev-tpmrm0.device or sudo systemctl mask tpm2.target for timeout to be fixed. Unfortunately the timeout came back for me after I updated yesterday and booted today 😢 So your mileage may vary but it will definitely fix it for a short while until system update or next update of systemd me thinks.

michael_s

@Korfou, @cornbean, @TraceyC
I'm having the same problem (the 2nd one) on Budgie. I also followed @cornbean's advice, but here it didn't fix it.

In general I'm not happy with the outcome of week 45s update. My system is heavily slowed down, programs or media files always take the extra moment to start or stop, if I write a program's name in the search field of the menu it looks like the software is kinda drunk, 'cause the letters a.. l.. w.. a.. y.. s.. show up with some delay.

I don't want to call the update enshittification, but ...

cornbean

michael_s Damn bro yeah it was a rocky update for Budgie users unfortunately 😢 I see your point about enshitification, but it was mostly due to GNOME 49 update i think which doesn't have to do with the Solus team.

Axios

Yes bumpy but well taken care of!!
With good input from forum users and others
Truck on!

pomon

To requires digging into the logs and looking for errors. I suggest:

ls -la /dev/tpm*
systemctl --failed
dmesg | grep -i tpm
journalctl -b -0 | grep -i tpm
journalctl -b -0 | grep -A 5 -B 5 tpm
lsmod | grep tpm

Check if TPM is enabled in the BIOS. On my system it’s under Security → TPM 2.0 Security. It’s possible that TPM is disabled in the BIOS, but the system is still trying to load it.

Korfou

So what is the right option, should TPM be enabled or disabled in the BIOS?

ChaoticChrono

Korfou just disable it . your chip seems to be faulty is it possibly an amd cpu

Korfou

I placed the orders:

m@Ordizor ~ $ ls -la /dev/tpm*
ls: Unable to access '/dev/tpm*': No file or folder with that name

marie@Ordizor ~ $ systemctl --failed
  UNIT LOAD ACTIVE SUB DESCRIPTION

0 loaded units listed.

m@Ordizor ~ $ dmesg | grep -i tpm
[    0.000000] efi: ESRT=0x7f099c18 ACPI=0x7fbfe000 ACPI 2.0=0x7fbfe014 SMBIOS=0x7f97df98 INITRD=0x7437e498 RNG=0x7fbe4e18 TPMEventLog=0x7fbb9018 
[    0.000000] TPM Final Events table not present
[    0.009632] ACPI: TPM2 0x000000007FBCB000 000044 (v03 HPQOEM INSYDE   20505350 HP   00040000)
[    0.009704] ACPI: Reserving TPM2 table memory at [mem 0x7fbcb000-0x7fbcb043]
[    0.940556] tpm_crb MSFT0101:00: error -EBUSY: can't request region for resource [mem 0x7fb6f000-0x7fc6efff]
[    0.940574] tpm_crb MSFT0101:00: probe with driver tpm_crb failed with error -16
[    2.850414] systemd[1]: systemd 257.10 running in system mode (+PAM -AUDIT -SELINUX -APPARMOR +IMA +IPE +SMACK +SECCOMP +GCRYPT +GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN -IPTC +KMOD +LIBCRYPTSETUP +LIBCRYPTSETUP_PLUGINS +LIBFDISK +PCRE2 +PWQUALITY +P11KIT +QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD +BPF_FRAMEWORK +BTF +XKBCOMMON +UTMP -SYSVINIT +LIBARCHIVE)
[    2.992496] systemd[1]: Expecting device dev-tpmrm0.device - /dev/tpmrm0...
[   35.190784] systemd[1]: systemd 257.10 running in system mode (+PAM -AUDIT -SELINUX -APPARMOR +IMA +IPE +SMACK +SECCOMP +GCRYPT +GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN -IPTC +KMOD +LIBCRYPTSETUP +LIBCRYPTSETUP_PLUGINS +LIBFDISK +PCRE2 +PWQUALITY +P11KIT +QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD +BPF_FRAMEWORK +BTF +XKBCOMMON +UTMP -SYSVINIT +LIBARCHIVE)
[   39.599463] systemd[1]: Expecting device dev-tpmrm0.device - /dev/tpmrm0...

m@Ordizor ~ $ journalctl -b -0 | grep -i tpm
Hint: You are currently not seeing messages from other users and the system.
      Users in groups 'adm', 'avahi-autoipd', 'systemd-journal', 'wheel' can see all messages.
      Pass -q to turn off this notice.

m@Ordizor ~ $ journalctl -b -0 | grep -A 5 -B 5 tpm
Hint: You are currently not seeing messages from other users and the system.
      Users in groups 'adm', 'avahi-autoipd', 'systemd-journal', 'wheel' can see all messages.
      Pass -q to turn off this notice.

m@Ordizor ~ $ lsmod | grep tpm
m@Ordizor ~ $

Korfou

After placing all the orders, when I start up, I see what is shown in the two images above again.

michael_s

@cornbean, @Axios
I keep my fingers crossed. Wouldn't like it to choose yet another distro just one year after I came to Solus ...

pomon

You’re not in any of the required groups, so you must use: sudo journalctl
You should first check which TPM-related service is actually running:
systemctl status *tpm*
Then mask the exact service that appears there:
sudo systemctl mask <service-name>
If TPM is disabled in BIOS, try enabling it once to compare the boot logs.

Korfou

Hello pomon

I had already disabled TPM in the BIOS and the message in the second image is not visible.
The first command returns nothing.

I then enabled TPM in the BIOS, and the message in the second image is visible. Now, the first command gives me a result. I copied the result after the second command and restarted the PC. The message in the second image is still visible.

I have to return the laptop this afternoon.
I leave TPM disabled and not visible in the BIOS entries. :
No matter what I do, the first image remains visible all the time.
And I have to wait 20 seconds before the start-up continues.

Thank you all very much for your help.

Axios

The irq issue seems pronounced over the net and from what I can tell may be more of an Amd
issue /Eufi with all variety of answers on how to handle it.
In my opinion prob is not a Solus issue.
Most computers with it still boot but alot slower.

And as always with that kind of issue start with bios update if their is one.

Korfou

To my knowledge, and unless I am mistaken, I am not aware of any manufacturer that offers BIOS updates with Linux systems.
And since with Windows we don't know how it will boot up, it's complicated.

Korfou

I just returned the laptop to its owner.

I showed him the update and restarted it as requested.
And then, surprise, the updates were done in the same window as the image at the top.
This is the first time I've seen this.
Is this now a normal process on Solus or is there another reason?