Re: Permanently remove services

[Lennart Poettering <lennart@xxxxxxxxxxxxxx>]

On Do, 18.01.24 22:53, Morten Bo Johansen (mortenbo@xxxxxxxxxxx) wrote:

> ~/ % systemd-creds has-tpm2
> partial
> +firmware
> -driver
> +system
> +subsystem
> +libraries

OK, so this indicates that your system has TPM support on all levels
with a single exception: you lack an actual linux driver for your
specific hw. And that puzzles me. because to my knowledge at least
linux should support all relevant tpm2 interfaces just fine. THis
suggests that you haven#t got the right modules installed.

i don't know arch but is there possibly some extra package you have to
install to get more drivers?

tpm2 drivers are super basic stuff, it sound really weird to me to
split this out. It's a condition this stuff indeed is not prepared for
though: that everything is set up properly, from firmware to kernel to
userspace, but the driver is not actually available.

> The output from journalctl --unit systemd-tpm2-setup-early.service:
>
>    -- Boot b3fca98d73f6441590174a72ac0d27fa --
>    jan 18 18:13:02 gatsby systemd-tpm2-setup[329]: Failed to create TPM2 context: State not recoverable
>    jan 18 18:13:02 gatsby systemd-tpm2-setup[329]: ERROR:tcti:src/tss2-tcti/tcti-device.c:451:Tss2_Tcti_Device_Init() Failed to open specified TCTI device file /dev/tpmrm0: No such file or direc>
>    jan 18 18:13:03 gatsby systemd[1]: systemd-tpm2-setup-early.service: Main process exited, code=exited, status=1/FAILURE
>    jan 18 18:13:03 gatsby systemd[1]: systemd-tpm2-setup-early.service: Failed with result 'exit-code'.
>    jan 18 18:13:03 gatsby systemd[1]: Failed to start TPM2 SRK Setup (Early).
>
> There is a /dev/tpm0 file but not a /dev/tpmrm0 file

Oh, interesting. Is it possible that your system has only a TPM 1.2
device? (maybe your bios allows switching between TPM 2.0 and 1.2 modes)

It could be that we simply misdetect the tpm 1.2 case, i admittedly
never tested things on such a system. how old is that PC?

Lennart

--
Lennart Poettering, Berlin