http://bugzilla.opensuse.org/show_bug.cgi?id=1173574
Bug ID: 1173574 Summary: fwupd Initialize default tcti. ErrorCode (0x000a000a) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs@suse.de Reporter: emiliano.langella@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: ---
Hi,
I noticed the following fwupd errors:
# journalctl -u fwupd.service -b -- Logs begin at Thu 2020-04-23 11:28:04 CEST, end at Wed 2020-07-01 09:54:57 CEST. -- Jul 01 09:52:40 kitt systemd[1]: Starting Firmware update daemon... Jul 01 09:52:42 kitt fwupd[2846]: ERROR:esys:src/tss2-esys/esys_context.c:69:Esys_Initialize() Initialize default tcti. ErrorCode (0x000a000a) Jul 01 09:52:42 kitt fwupd[2846]: ERROR:esys:src/tss2-esys/esys_context.c:69:Esys_Initialize() Initialize default tcti. ErrorCode (0x000a000a) Jul 01 09:52:43 kitt fwupd[2846]: ERROR:esys:src/tss2-esys/esys_context.c:69:Esys_Initialize() Initialize default tcti. ErrorCode (0x000a000a) Jul 01 09:52:43 kitt fwupd[2846]: 07:52:43:0646 FuEngine failed to add udev device /sys/devices/platform/MSFT0101:00/tpm/tpm0: failed to initialize> Jul 01 09:52:43 kitt systemd[1]: Started Firmware update daemon.
# fwupdate -i failed: Error opening file /sys/firmware/efi/efivars/fwupd-34578c72-11dc-4378-bc7f-b643866f598c-0-0abba7dc-e516-4167-bbf5-4d9d1c739416: No such file or directory
Laptop: Dell Precision 5520 Tumbleweed: 20200628
# fwupdmgr --version client version: 1.4.2 compile-time dependency versions gusb: 0.3.0 efivar: 37 daemon version: 1.4.2
Let me know if you need any additional info.
Thanks.
http://bugzilla.opensuse.org/show_bug.cgi?id=1173574
Emiliano Langella emiliano.langella@suse.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |emiliano.langella@suse.com
http://bugzilla.opensuse.org/show_bug.cgi?id=1173574 http://bugzilla.opensuse.org/show_bug.cgi?id=1173574#c1
--- Comment #1 from Emiliano Langella emiliano.langella@suse.com --- Created attachment 839261 --> http://bugzilla.opensuse.org/attachment.cgi?id=839261&action=edit fwupdmgr get-devices output
http://bugzilla.opensuse.org/show_bug.cgi?id=1173574
Dominique Leuenberger dimstar@opensuse.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |rhughes@redhat.com
http://bugzilla.opensuse.org/show_bug.cgi?id=1173574 http://bugzilla.opensuse.org/show_bug.cgi?id=1173574#c4
--- Comment #4 from Emiliano Langella emiliano.langella@suse.com --- Just an update with version 1.5.3:
# journalctl -u fwupd.service -b -- Logs begin at Fri 2020-11-13 09:44:09 CET, end at Tue 2020-12-29 15:48:09 CET. -- Dec 29 15:47:38 rodan systemd[1]: Starting Firmware update daemon... Dec 29 15:47:39 rodan fwupd[2411]: ERROR:esys:src/tss2-esys/esys_context.c:69:Esys_Initialize() Initialize default tcti. ErrorCode (0x000a000a) Dec 29 15:47:39 rodan fwupd[2411]: ERROR:esys:src/tss2-esys/esys_context.c:69:Esys_Initialize() Initialize default tcti. ErrorCode (0x000a000a) Dec 29 15:47:40 rodan fwupd[2411]: ERROR:esys:src/tss2-esys/esys_context.c:69:Esys_Initialize() Initialize default tcti. ErrorCode (0x000a000a) Dec 29 15:47:40 rodan fwupd[2411]: 14:47:40:0233 FuEngine failed to add udev device /sys/devices/platform/MSFT0101:00/tpm/tpm0: failed to initializ> Dec 29 15:47:40 rodan systemd[1]: Started Firmware update daemon.
# fwupdate -i Information for the update status entry 0: Firmware GUID: {34578c72-11dc-4378-bc7f-b643866f598c} Update Status: No update info found
# fwupdmgr --version client version: 1.5.3 compile-time dependency versions gusb: 0.3.5
daemon version: 1.5.3
http://bugzilla.opensuse.org/show_bug.cgi?id=1173574 http://bugzilla.opensuse.org/show_bug.cgi?id=1173574#c5
Frank Kr�ger fkrueger@mailbox.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |fkrueger@mailbox.org
--- Comment #5 from Frank Kr�ger fkrueger@mailbox.org --- (In reply to Emiliano Langella from comment #4)
Just an update with version 1.5.3:
# journalctl -u fwupd.service -b -- Logs begin at Fri 2020-11-13 09:44:09 CET, end at Tue 2020-12-29 15:48:09 CET. -- Dec 29 15:47:38 rodan systemd[1]: Starting Firmware update daemon... Dec 29 15:47:39 rodan fwupd[2411]: ERROR:esys:src/tss2-esys/esys_context.c:69:Esys_Initialize() Initialize default tcti. ErrorCode (0x000a000a) Dec 29 15:47:39 rodan fwupd[2411]: ERROR:esys:src/tss2-esys/esys_context.c:69:Esys_Initialize() Initialize default tcti. ErrorCode (0x000a000a) Dec 29 15:47:40 rodan fwupd[2411]: ERROR:esys:src/tss2-esys/esys_context.c:69:Esys_Initialize() Initialize default tcti. ErrorCode (0x000a000a) Dec 29 15:47:40 rodan fwupd[2411]: 14:47:40:0233 FuEngine failed to add udev device /sys/devices/platform/MSFT0101:00/tpm/tpm0: failed to initializ> Dec 29 15:47:40 rodan systemd[1]: Started Firmware update daemon.
I can confirm your observation with TW20201228, although I am not sure whether these error messages are really harmful. Anyway, they disappear after installing the packages tpm2-0-tss and tpm2.0-abrmd, which are neither required nor recommended by zypper.
http://bugzilla.opensuse.org/show_bug.cgi?id=1173574 http://bugzilla.opensuse.org/show_bug.cgi?id=1173574#c6
Dominique Leuenberger dimstar@opensuse.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED
--- Comment #6 from Dominique Leuenberger dimstar@opensuse.org --- Dear Reporter,
Thank you for taking the time to report this bug and helping to make openSUSE better.
We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in openSUSE since the time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a current, supported openSUSE version. The TPM chip is, in many cases, present, but not enabled (or the TPM chip does not support all capabilities, which can lead to those errors)
When you test it and it is still an issue, kindly reopen this bug and move it to the tested version of openSUSE.
Truly yours.