failed to add device

[ooonea]

Describe the question I would like to know what that failed to add device value in the fwupd.service status means and why one called (null) appears in the device list:

❯ ~ systemctl status fwupd           
● fwupd.service - Firmware update daemon
     Loaded: loaded (/usr/lib/systemd/system/fwupd.service; static)
     Active: active (running) since Tue 2024-10-15 18:24:51 CEST; 1min 22s ago
 Invocation: 5921aa748226449f81636de466432f16
       Docs: https://fwupd.org/
   Main PID: 530908 (fwupd)
      Tasks: 4 (limit: 38187)
     Memory: 9.7M (peak: 10.7M)
        CPU: 621ms
     CGroup: /system.slice/fwupd.service
             └─530908 /usr/lib/fwupd/fwupd

Oct 15 18:24:49 unicorn systemd[1]: Starting Firmware update daemon...
Oct 15 18:24:50 unicorn fwupd[530908]: 16:24:50.686 FuEngine             failed to add device /sys/devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3:1.0/host>
Oct 15 18:24:51 unicorn fwupd[530908]: 16:24:51.346 FuMain               Daemon ready for requests (locale it_IT.UTF-8)
Oct 15 18:24:51 unicorn systemd[1]: Started Firmware update daemon.

❯ ~ fwupdmgr get-updates    
Devices with no available firmware updates: 
 • (null)
 • Thunderbolt host controller
 • UEFI Device Firmware
 • UEFI Device Firmware
 • UEFI Device Firmware
Devices with the latest available firmware version:
 • Embedded Controller
 • Intel Management Engine
 • MZVLB256HAHQ-000L7
 • System Firmware
 • UEFI dbx
No updates available

fwupd version information fwupd 2.0.1-1 on Arch Linux

fwupdmgr --version

compile   info.libusb                   1.0.27
compile   org.freedesktop.fwupd         2.0.1
compile   org.freedesktop.Passim        0.1.8
compile   com.hughsie.libxmlb           0.3.21
compile   com.hughsie.libjcat           0.2.1
runtime   org.freedesktop.fwupd-efi     1.7
runtime   org.freedesktop.Passim        0.1.8
runtime   com.hughsie.libxmlb           0.3.21
runtime   com.hughsie.libjcat           0.2.1
runtime   org.kernel                    6.6.56-1-lts
runtime   org.freedesktop.fwupd         2.0.1

[superm1]

Can you please run fwupdtool get-devices -vv and share?

[ooonea]

https://clbin.com/bg3KA Here is the complete output. It is too long to publish.

[superm1]

To me it looks like it's your GPU at 0000:00:02.0

[ooonea]

But systemd says other: fwupd[171369]: 21:13:05.907 FuEngine failed to add device /sys/devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3:1.0/host1/target1:0:0/1:0:0:0/block/sdb: failed to setup: failed to read version: command fail with status 2, senseKey 0x05, asc 0x24, ascq 0x00

To me it looks like it's your GPU at 0000:00:02.0

Are you referring to the device that appears as (null)? Previously, the devices were all shown to me.

[superm1]

Yeah that's the device that looks like NULL title to me . It's this device:

 FuOptionromDevice:
  DeviceId:             5792b48846ce271fab11c4a545f7a3df0d36e00a
  Guid:                 8b72a10c-1279-5f8e-a28a-34fb11a58240 <- PCI\VEN_8086&DEV_5917
  Plugin:               optionrom
  Flags:                internal|can-verify|can-verify-image|can-emulation-tag
  Vendor:               Intel Corporation
  VendorId:             PCI:0x8086
  Version:              07
  VersionFormat:        plain
  Created:              2024-10-15

@hughsie I guess this is a case of missing data in PCI IDs. Maybe we should have an automagic created title based on the PCI class.

[ooonea]

What could I do?

[superm1]

So at lease the "Null Device" will be fixed in the next release (2.0.2) by this https://github.com/fwupd/fwupd/pull/7915

[superm1]

Regarding the other message about failing to add device, did this populate as a device before? Or just didn't make noise before?

[ooonea]

To be honest, I have no idea what that message means. I never noticed it before.

[superm1]

It looks like it's from your SD card reader. Did you have an SD card inserted?

FuScsiDevice:
  DeviceId:             62922422e5238f9258d3370aac34a7b79eb621cb
  Name:                 SD/MMC
  Guid:                 7da4b3f1-d79e-5d4d-bc60-7ea08e13aecc <- BLOCK\VEN_0BDA&DEV_0316
  Guid:                 e8f42b03-8404-51a6-8614-95c9aff5bd4e <- SCSI\VEN_Generic-&DEV_SD/MMC  
  Guid:                 de0bff0b-c5b5-5b41-b4e1-e553baac7135 <- SCSI\VEN_Generic-&DEV_SD/MMC  &REV_1.00
  Summary:              SCSI device
  Plugin:               scsi
  Flags:                can-emulation-tag
  Vendor:               Generic-
  VendorId:             USB:0x0BDA
  VendorId:             SCSI:Generic-
  Version:              1.00
  VersionFormat:        plain
  Icon:                 drive-harddisk
  Created:              2024-10-15
  Guid[quirk]:          0b18d9bf-3b6a-5a32-832a-d7b0bc4d34b0 <- BLOCK\TYPE_DISK
  Guid[quirk]:          5f9e78eb-9e1d-5830-8934-ebba7d6d8aea <- BLOCK\VEN_0BDA
  Guid[quirk]:          20ccb7f9-ac5a-536d-9553-83c40055348a <- SCSI\VEN_Generic-
  PhysicalId:           DEVPATH=/devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3:1.0/host1/target1:0:0
  BackendId:            /sys/devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3:1.0/host1/target1:0:0/1:0:0:0/block/sdb
  Vid:                  0xbda
  Pid:                  0x316
  AcquiesceDelay:       2500
  PossiblePlugin:       algoltek_usbcr
  PossiblePlugin:       android_boot
  PossiblePlugin:       ata
  PossiblePlugin:       emmc
  PossiblePlugin:       scsi
  PossiblePlugin:       uf2
  PrivateFlags:         add-instance-id-rev,is-open,registered
  Subsystem:            block
  DeviceFile:           /dev/sdb
  OpenFlags:            read,sync

[ooonea]

I understood that it was my SD Card reader, but I have no SD Card inserted, just the empty reader.