Arch Linux

ane

Member

Registered: 2025-11-08

Posts: 5

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: 5

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: 5

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

Still unresolved.

ane

Member

Registered: 2025-11-08

Posts: 5

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

still need help

nspsck

Member

Registered: 2026-01-24

Posts: 1

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

Hi, you need to install a proprietary driver in order for the device to run. libfprint-2-tod1-broadcom from AUR. Tho no guarantee for you to be able to register you fingerprint, I couldn't at least ...

ane

Member

Registered: 2025-11-08

Posts: 5

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

libfprint-2-tod1-broadcom from AUR.

I already installed this package, as was in the title of the post. The error was with the driver installed from the AUR. I haven't done any extra setup with it, but the package is installed and present.

nimrodium

Member

Registered: 2026-07-05

Posts: 1

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

I have the same issue but on NixOS. did you ever figure this out?

Umbrawing

Member

Registered: 2026-08-24

Posts: 1

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

I'm running on a Latitude 5520 with Hyprland, and I found that mine started working after the following steps:
Installing the following packages:
- fprintd
- libfprint-2-tod1-broadcom (AUR)
- libfprint-tod (AUR)

I also needed to go into my BIOS and re-enable my fingerprint sensor. After a quick reboot, fprintd got through detection of the sensor, and I could add fingers and get it to verify. I still need to figure out how to get it to authenticate with PAM, but that's what I got so far. I don't know if this is going to be helpful to anyone else, but I hope it is

alex092lap

Member

Registered: Yesterday

Posts: 2

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

Your 0a5c:5842 case is adjacent to the 0a5c:5843 issue I reproduced, but the log points to an earlier initialization/firmware identity failure rather than the final enrollment timeout: repeated USH status 0xb, then FwUpgradeError 0x1c, followed by the device being ignored and NoSuchDevice.

Before attempting any firmware change, verify that the fingerprint sensor is enabled in BIOS, identify the exact ControlVault/CID and sensor PID, and ensure the matching libfprint-tod plus libfprint-2-tod1-broadcom files are installed. A recent reply in this thread reports a Latitude 5520 working after installing fprintd, both AUR TOD packages, re-enabling the sensor in BIOS, and rebooting.

The safe inspection tooling and reproducible notes are here: https://github.com/GrecAndrei/controlva … ey-toolkit. The controller deliberately does not flash firmware; mismatched CV3 firmware can make initialization worse.