tpm2-abrmd
tpm2-abrmd copied to clipboard
tpm2-software
Problems with tpm2 in fedora 32
As seen in this link, I report to be having the issue below mentioned
Evrytime the OS boots, I get an error message on gnome notification:
Failed to Update: Detailed errors from the package manager follow: Error calling StartServiceByName for org.freedesktop.fwupd: Timeout was reached
@luchonat there were a couple of issues that caused this in the past but these should had been solved in tpm2-abrmd 2.3.1 and I see that's the latest packaged version in F32: tpm2-abrmd-2.3.1-2.fc32.x86_64
Can you please provide the following information to figure out what's going on:
1- What's the version of your tpm2-tools and tpm2-abrmd packages? Could you please make sure that are using the latest version.
2- Do you have SELinux in Enforcing or Permissive mode? i.e: what's the output of getenforce
3- Do you have the tpm2-abrmd-selinux package installed?
4- Do you have a /dev/tpm* character device?
5- Is this something that only happens with fwupd? That is, are the tpm2 tools able to talk with the tpm2-abrmd daemon? What happens if you execute for example the tpm2_pcrread command?
1: Name : tpm2-tools Version : 4.1.3 Release : 1.fc32 Architecture : x86_64 Size : 5.1 M Source : tpm2-tools-4.1.3-1.fc32.src.rpm
Name : tpm2-abrmd Version : 2.3.1 Release : 2.fc32 Architecture : x86_64 Size : 328 k Source : tpm2-abrmd-2.3.1-2.fc32.src.rpm
2: Enforcing 3: Yes 4: No 5: I don't know how to determine that. I think it's related to fwupdate but not sure. [root@localhost]# tpm2_pcrread
** (process:26788): CRITICAL **: 19:40:15.721: failed to allocate dbus proxy object: Error calling StartServiceByName for com.intel.tss2.Tabrmd: Timeout was reached WARNING:tcti:src/tss2-tcti/tctildr.c:79:tcti_from_init() TCTI init for function 0x7fef1c6b1d00 failed with a0008 WARNING:tcti:src/tss2-tcti/tctildr.c:109:tcti_from_info() Could not initialize TCTI named: tcti-abrmd ERROR:tcti:src/tss2-tcti/tctildr-dl.c:150:tcti_from_file() Could not initialize TCTI file: libtss2-tcti-tabrmd.so.0 ERROR:tcti:src/tss2-tcti/tcti-device.c:477:Tss2_Tcti_Device_Init() Failed to open specified TCTI device file /dev/tpmrm0: No such file or directory WARNING:tcti:src/tss2-tcti/tctildr.c:79:tcti_from_init() TCTI init for function 0x7fef1cd130a0 failed with a000a WARNING:tcti:src/tss2-tcti/tctildr.c:109:tcti_from_info() Could not initialize TCTI named: tcti-device ERROR:tcti:src/tss2-tcti/tctildr-dl.c:150:tcti_from_file() Could not initialize TCTI file: libtss2-tcti-device.so.0 ERROR:tcti:src/tss2-tcti/tcti-device.c:477:Tss2_Tcti_Device_Init() Failed to open specified TCTI device file /dev/tpm0: No such file or directory WARNING:tcti:src/tss2-tcti/tctildr.c:79:tcti_from_init() TCTI init for function 0x7fef1cd130a0 failed with a000a WARNING:tcti:src/tss2-tcti/tctildr.c:109:tcti_from_info() Could not initialize TCTI named: tcti-device ERROR:tcti:src/tss2-tcti/tctildr-dl.c:150:tcti_from_file() Could not initialize TCTI file: libtss2-tcti-device.so.0 WARNING:tcti:src/util/io.c:252:socket_connect() Failed to connect to host 127.0.0.1, port 2321: errno 111: Connection refused WARNING:tcti:src/tss2-tcti/tctildr.c:79:tcti_from_init() TCTI init for function 0x7fef1cd13500 failed with a000a WARNING:tcti:src/tss2-tcti/tctildr.c:109:tcti_from_info() Could not initialize TCTI named: tcti-socket ERROR:tcti:src/tss2-tcti/tctildr-dl.c:150:tcti_from_file() Could not initialize TCTI file: libtss2-tcti-mssim.so.0 ERROR:tcti:src/tss2-tcti/tctildr-dl.c:250:tctildr_get_default() No standard TCTI could be loaded ERROR:tcti:src/tss2-tcti/tctildr.c:416:Tss2_TctiLdr_Initialize_Ex() Failed to instantiate TCTI ERROR: Could not load tcti, got: "(null)"
On Wed, Jul 8, 2020 at 6:22 AM Javier Martinez Canillas < [email protected]> wrote:
@luchonat https://github.com/luchonat there were a couple of issues that caused this in the past but these should had been solved in tpm2-abrmd 2.3.1 and I see that's the latest packaged version in F32: tpm2-abrmd-2.3.1-2.fc32.x86_64
Can you please provide the following information to figure out what's going on:
1- What's the version of your tpm2-tools and tpm2-abrmd packages? Could you please make sure that are using the latest version. 2- Do you have SELinux in Enforcing or Permissive mode? i.e: what's the output of getenforce 3- Do you have the tpm2-abrmd-selinux package installed? 4- Do you have a /dev/tpm* character device? 5- Is this something that only happens with fwupd? That is, are the tpm2 tools able to talk with the tpm2-abrmd daemon? What happens if you execute for example the tpm2_pcrread command?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/tpm2-software/tpm2-abrmd/issues/724#issuecomment-655401207, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABRMBEE2NHHYGSEBBT3257LR2Q3F5ANCNFSM4OPCGDAQ .
-- Luciano César Natale
Having exactly the same issue in Fedora 32. The following logs might be helpful.
01:40:21:0780 FIXME failed to allocate dbus proxy object: Error calling StartServiceByName for com.intel.tss2.Tabrmd: Timeout was reached
ERROR:esys:src/tss2-esys/esys_context.c:69:Esys_Initialize() Initialize default tcti. ErrorCode (0x000a000a)
01:40:22:0112 FuPluginUefi failed to initialize TPM library
