munroesj52
(Steven Jay Munroe)
April 26, 2021, 11:18pm
1
Trying to upgrade a Thinkstation P500. Trying to make sure F2 is up to date before upgrade to F33.
Keep getting:
Error calling StartServiceByName for org.freedesktop.fwupd: Timeout was reached
Runing
journalctl -b -u fwupd
shows:
Apr 26 17:54:21 localhost.localdomain systemd[1]: Starting Firmware update daemon...
Apr 26 17:54:48 localhost.localdomain fwupd[17030]: ERROR:sys:src/tss2-sys/api/Tss2_Sys_Execute.c:114:Tss2_Sys_ExecuteFinish() Unsupported device. The device is a TPM 1.2
Apr 26 17:54:48 localhost.localdomain fwupd[17030]: ERROR:esys:src/tss2-esys/api/Esys_Startup.c:216:Esys_Startup_Finish() Received a non-TPM Error
Apr 26 17:54:48 localhost.localdomain fwupd[17030]: ERROR:esys:src/tss2-esys/api/Esys_Startup.c:78:Esys_Startup() Esys Finish ErrorCode (0x00080001)
Apr 26 17:54:48 localhost.localdomain fwupd[17030]: 22:54:48:0064 FuEngine failed to add device (null): failed to initialize TPM
Apr 26 17:54:48 localhost.localdomain fwupd[17030]: 22:54:48:0755 FuDeviceList ignoring device 79ace0a011036d0107e1629af76482edb39d6cf1 [ata:(null)] existing device af04bed0039ed01abf9b6b08d90cef9de4b17c08 [ata:(null)] already>
Apr 26 17:54:48 localhost.localdomain fwupd[17030]: 22:54:48:0765 FuDeviceList ignoring device b784a0abe923e607ca856f4317ce849f9d07b60e [ata:(null)] existing device af04bed0039ed01abf9b6b08d90cef9de4b17c08 [ata:(null)] already>
Apr 26 17:54:48 localhost.localdomain fwupd[17030]: 22:54:48:0775 FuDeviceList ignoring device 788f9ddb38891bb14bd733f9adca3f43466dd02f [ata:(null)] existing device af04bed0039ed01abf9b6b08d90cef9de4b17c08 [ata:(null)] already>
Apr 26 17:54:48 localhost.localdomain systemd[1]: Started Firmware update daemon.
Apr 26 17:54:55 localhost.localdomain fwupd[17030]: 22:54:55:0121 FuPluginPciMei ME family not supported for 0:9.1.2.1010
Can you please check this, if this helps for you?
opened 12:56AM - 04 Dec 19 UTC
closed 01:28PM - 10 Dec 19 UTC
bug
duplicate
To help us pinpoint your issue, please insert the output of the
following comma⦠nds when ran on the system with the issue:
```shell
$ fwupdmgr --version
[rlm@localhost ~]$ fwupdmgr --version
client version: 1.3.5
compile-time dependency versions
gusb: 0.3.1
efivar: 37
daemon version: 1.3.5
```
Note, the switch `--version` is only present since version 0.9.6. If you use an
earlier version, please use the package manager to find out the package
version. For example, `dpkg -l fwupd`.
```shell
$ fwupdmgr get-devices
Inspiron 3847
β
ββSystem Firmware:
β Device ID: 1d70a31dd3ff0941761550a38436fc990c6c3ff0
β Current version: 0.1.0.6
β Minimum Version: 0.1.0.6
β Vendor: Dell Inc.
β GUID: 7039436b-6acf-433b-86a1-368ec2ef7e1f
β Device Flags: β’ Internal device
β β’ Updatable
β β’ Requires AC power
β β’ Needs a reboot after installation
β β’ Cryptographic hash verification is available
β β’ Device is usable for the duration of the update
β
ββWDC WD10EZEX-75M2NA0:
Device ID: 602b0a6cc821d155208724f0e22f8d111542b74c
Summary: ATA Drive
Current version: 01.01A01
Vendor: Intel Corporation
GUIDs: d1dd99cb-6def-574e-a5d9-79d4f5111f62
fa5ea645-df36-5c29-8bc0-473b151320a5
ea47efd1-c30d-55fd-8e50-1d8d7a00e0cc
Device Flags: β’ Internal device
β’ Updatable
β’ Requires AC power
β’ Needs a reboot after installation
β’ Device is usable for the duration of the update
```
```shell
$ efibootmgr -v
BootCurrent: 0002
Timeout: 2 seconds
BootOrder: 0002,0008,0000,0001
Boot0000 P0: WDC WD10EZEX-75M2NA0 VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)
Boot0001 P4: PLDS DVD+/-RW DH-16AES VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)
Boot0002* Fedora HD(1,GPT,781f86bc-9c91-4b7e-83d4-34e43aa35e87,0x800,0x2800000)/File(\EFI\fedora\shim.efi)
Boot0008* UEFI OS HD(1,GPT,781f86bc-9c91-4b7e-83d4-34e43aa35e87,0x800,0x2800000)/File(\EFI\BOOT\BOOTX64.EFI)
**This is only required if you use the UEFI plugin**
```
```shell
$ efivar -l | grep fw
<no output>
**This is only required if you use the UEFI plugin**
```
```shell
$ tree /boot
/boot
βββ config-5.3.12-300.fc31.x86_64
βββ config-5.3.13-300.fc31.x86_64
βββ config-5.3.8-300.fc31.x86_64
βββ efi [error opening dir]
βββ elf-memtest86+-5.01
βββ extlinux
β βββ cat.c32
β βββ chain.c32
β βββ cmd.c32
β βββ cmenu.c32
β βββ config.c32
β βββ cptime.c32
β βββ cpu.c32
β βββ cpuid.c32
β βββ cpuidtest.c32
β βββ debug.c32
β βββ dhcp.c32
β βββ dir.c32
β βββ disk.c32
β βββ dmi.c32
β βββ dmitest.c32
β βββ elf.c32
β βββ ethersel.c32
β βββ gfxboot.c32
β βββ gpxecmd.c32
β βββ hdt.c32
β βββ hexdump.c32
β βββ host.c32
β βββ ifcpu64.c32
β βββ ifcpu.c32
β βββ ifmemdsk.c32
β βββ ifplop.c32
β βββ kbdmap.c32
β βββ kontron_wdt.c32
β βββ ldlinux.c32
β βββ lfs.c32
β βββ libcom32.c32
β βββ libgpl.c32
β βββ liblua.c32
β βββ libmenu.c32
β βββ libutil.c32
β βββ linux.c32
β βββ ls.c32
β βββ lua.c32
β βββ mboot.c32
β βββ memdisk
β βββ meminfo.c32
β βββ menu.c32
β βββ pci.c32
β βββ pcitest.c32
β βββ pmload.c32
β βββ poweroff.c32
β βββ prdhcp.c32
β βββ pwd.c32
β βββ pxechn.c32
β βββ reboot.c32
β βββ rosh.c32
β βββ sanboot.c32
β βββ sdi.c32
β βββ sysdump.c32
β βββ syslinux.c32
β βββ vesa.c32
β βββ vesainfo.c32
β βββ vesamenu.c32
β βββ vpdtest.c32
β βββ whichsys.c32
β βββ zzjson.c32
βββ f3603cfae66044dda9d024b8fa5aec6e
β βββ 4.11.8-300.fc26.x86_64
βββ grub2 [error opening dir]
βββ initramfs-0-rescue-2dde7c61ae444335b5ff6030b0eb959a.img
βββ initramfs-5.3.12-300.fc31.x86_64.img
βββ initramfs-5.3.13-300.fc31.x86_64.img
βββ initramfs-5.3.8-300.fc31.x86_64.img
βββ loader
β βββ entries [error opening dir]
βββ memtest86+-5.01
βββ System.map-5.3.12-300.fc31.x86_64
βββ System.map-5.3.13-300.fc31.x86_64
βββ System.map-5.3.8-300.fc31.x86_64
βββ vmlinuz-0-rescue-2dde7c61ae444335b5ff6030b0eb959a
βββ vmlinuz-5.3.12-300.fc31.x86_64
βββ vmlinuz-5.3.13-300.fc31.x86_64
βββ vmlinuz-5.3.8-300.fc31.x86_64
**This is only required if you use the UEFI plugin**
**We're looking for any `.cap` files and the location of `fwupx64.efi`**
```
Please answer the following questions:
- Operating system and version: Fedora 31
- How did you install fwupd (ex: `from source`, `pacman`, `apt-get`, etc): sudo dnf update
- Have you tried rebooting? Multiple times
- Are you using an NVMe disk? Not to my knowledge?
- Is secure boot enabled (only for the UEFI plugin)? UEFI not in use AFAIK
Thanks. I did look at one of the other cases with this error, but was unable to make any headway in terms of what the resolution was.
1 Like
firmware updates are not required before you system-upgrade
from F32 to F33
As for your fwupd problem, have you tried this: Fedora 31: Error calling StartServiceByName for org.freedesktop.fwupd: Timeout was reached Β· Issue #1549 Β· fwupd/fwupd Β· GitHub (βThe issue resolved itself after removing tpm2-abrmd. β)
1 Like
munroesj52
(Steven Jay Munroe)
April 27, 2021, 2:49pm
4
$ fwupdmgr --version
client version: 1.5.7
compile-time dependency versions
gusb: 0.3.5
daemon version: 1.5.7
munroesj52
(Steven Jay Munroe)
April 27, 2021, 2:58pm
5
$ rpm -qa | grep tpm2
tpm2-tools-4.1.3-1.fc32.x86_64
tpm2-tss-2.4.4-1.fc32.x86_64
and
$ rpm -qa | grep βtpm2-abrmdβ
finds nothing. So no tpm2-abrmdβ that i can find
The problem is the this is blocking akernel update.
whatβs the output of sudo dnf update kernel
?
munroesj52
(Steven Jay Munroe)
April 27, 2021, 3:05pm
7
The TPM on this box may be disabled or back-level/unsupported.
$ ./tpm2_selftest
bash: ./tpm2_selftest: No such file or directory
[sjmunroe@localhost ~]$ tpm2_selftest
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 0x7f9b55d5a0a0 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: Permission denied
WARNING:tcti:src/tss2-tcti/tctildr.c:79:tcti_from_init() TCTI init for function 0x7f9b55d5a0a0 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 0x7f9b55d5a500 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)β
That is what dnf complains about when attempting to update kernel*
?
munroesj52:
fwupd
Your device not appears on the LVFS page ?!
Lenovo (ThinkStation)
munroesj52
(Steven Jay Munroe)
April 27, 2021, 3:51pm
10
Fedora Modular 32 - x86_64 - Updates 32 kB/s | 12 kB 00:00
Fedora 32 - x86_64 - Updates 40 kB/s | 9.0 kB 00:00
Fedora 32 - x86_64 - Updates 1.8 MB/s | 3.8 MB 00:02
Ignoring repositories: advance-toolchain
Dependencies resolved.
================================================================================
Package Arch Version Repository Size
================================================================================
Installing:
kernel x86_64 5.11.16-100.fc32 updates 152 k
kernel-core x86_64 5.11.16-100.fc32 updates 34 M
kernel-modules x86_64 5.11.16-100.fc32 updates 31 M
Removing:
kernel x86_64 5.11.10-100.fc32 @updates 0
kernel-core x86_64 5.11.10-100.fc32 @updates 74 M
kernel-modules x86_64 5.11.10-100.fc32 @updates 30 M
Removing dependent packages:
kernel-modules-extra x86_64 5.11.10-100.fc32 @updates 1.9 M
Transaction Summary
================================================================================
Install 3 Packages
Remove 4 Packages
Total download size: 65 M
munroesj52
(Steven Jay Munroe)
April 27, 2021, 4:46pm
11
Yes it is bit old. P500 Haswell 8 Core
Intel(R) Xeon(R) CPU E5-2630 v3 @ 2.40GHz
munroesj52
(Steven Jay Munroe)
June 1, 2021, 8:53pm
12
Still have no solution for this. I keep getting
Detailed errors from the package manager follow:
Error calling StartServiceByName for org.freedesktop.fwupd: Timeout was reached
munroesj52
(Steven Jay Munroe)
June 2, 2021, 12:19am
13
Finally got F32 β F33 upgrade to work.
It seems that fedore is very fussy about install sources and some of the IBM POWER install sources have moved (and timed out) . So had to clean those up manually.
I think other distros disable these and give you a warning so you can reinstall what you need after the upgrade.
Fedora normally trows you a message when something is not good anymore. You were just about 2 weeks to late to update, so some repos might not be available anymore. Thatβs why you got 404 errors.
Next time you just have to save the repolist so that you can see if you find something like this for the newer version too (sudo dnf repolist >>F32reposlist.txt for example). Have a look in the log-files if you find the messages about the IBM stuff.
About your firmware you might have to check on the Lenovo page if you can get an update to make it manually.