Arch Linux

ane

Member

Registered: 2025-11-08

Posts: 4

Broadcom Device 58200: Drivers not working [libfprint-2-tod1-broadcom]

I have a Dell Latitude 5400 Laptop, which apparently comes with the Broadcom 58200 Fingerprint reader (device 0a5c:5842). This package on the AUR is meant to be correct to install the device, and yet it's not being seen by fprintd-enroll. I tried installing it with the main package from the Ubuntu Repos of which the Arch package is a port, but no luck there either. Can anyone more familiar with drivers and/or Broadcom devices help?

nyx@artemis(~) $ systemctl status fprintd
○ fprintd.service - Fingerprint Authentication Daemon
     Loaded: loaded (/usr/lib/systemd/system/fprintd.service; static)
     Active: inactive (dead)
       Docs: man:fprintd(1)

Nov 07 22:42:39 artemis fprintd[1248]: In cvif_IsUshThere(), cv_get_ush_ver() status: (0xb)
Nov 07 22:42:40 artemis fprintd[1248]: In cvif_IsUshThere(), cv_get_ush_ver() status: (0xb)
Nov 07 22:42:41 artemis fprintd[1248]: In cvif_IsUshThere(), cv_get_ush_ver() status: (0xb)
Nov 07 22:42:42 artemis fprintd[1248]: In cvif_IsUshThere(), cv_get_ush_ver() status: (0xb)
Nov 07 22:42:43 artemis fprintd[1248]: In cvif_IsUshThere(), cv_get_ush_ver() status: (0xb)
Nov 07 22:42:44 artemis fprintd[1248]: Could NOT detect USH.
Nov 07 22:42:44 artemis fprintd[1248]:                 FwUpgradeError. Check Firmware Files or CID used or Hardware etc. Error: 0x1c
Nov 07 22:42:44 artemis fprintd[1248]: Ignoring device due to initialization error: An unspecified error occurred!
Nov 07 22:42:44 artemis systemd[1]: Started Fingerprint Authentication Daemon.
Nov 07 22:43:14 artemis systemd[1]: fprintd.service: Deactivated successfully.
nyx@artemis(~) $ 

Last edited by ane (2025-11-08 04:26:41)

ane

Member

Registered: 2025-11-08

Posts: 4

Re: Broadcom Device 58200: Drivers not working [libfprint-2-tod1-broadcom]

forgot to mention, but the error i'm receiving is

nyx@artemis(~) $ fprintd-enroll
Impossible to enroll: GDBus.Error:net.reactivated.Fprint.Error.NoSuchDevice: No devices available
nyx@artemis(~) $ 

which seems to imply that the driver isn't managing the device properly to make it valid. the systemctl logs seem to be most of note tho-- mostly the firmware update error and the "unspecified error"

Last edited by ane (2025-11-08 18:19:24)

ane

Member

Registered: 2025-11-08

Posts: 4

Re: Broadcom Device 58200: Drivers not working [libfprint-2-tod1-broadcom]

Still unresolved.

ane

Member

Registered: 2025-11-08

Posts: 4

Re: Broadcom Device 58200: Drivers not working [libfprint-2-tod1-broadcom]

still need help