If you ping me an email, I’ll send you my latest build where I still need some help with the SELinux policy generation so if you’re happy to work through that with me then you’ll be a good test candidate.
Hi Graham,
I’m on a Latitude 5500 with the 5843 fingerprint reader and can confirm, that I’m also unable to register fingerprints with your current package.
I used the same workaround with the much older version on Ubuntu and was unable to get the current version to work there.
Updating the FW worked fine, but afterwards when enrolling (terminal or GUI) I get no reaction.
Thanks for your contributions
Stefan
That’s really strange… I have the 5843 and to double check I have just successfully registered a different fingerprint to those that I already had registered, I can lock my screen and unlock with the newly registered print. I wonder whether you guys can see anything problematic in the journal logs???
This is all I get, when enrolling with fprintd-enroll, touching the fingerprint reader I don’t get any reaction at all.
Mar 24 10:40:46 latitude audit: BPF prog-id=122 op=LOAD
Mar 24 10:40:46 latitude systemd[1]: Starting fprintd.service - Fingerprint Authentication Daemon…
Mar 24 10:40:46 latitude fprintd[14974]: In cvif_IsUshThere(), cv_get_ush_ver() status: (0x0)
Mar 24 10:40:46 latitude fprintd[14974]: Control Vault getting chip type
Mar 24 10:40:46 latitude fprintd[14974]: Citadel A0 CID7 Chip Found…
Mar 24 10:40:46 latitude fprintd[14974]: Current AAI Version = 5.15.10.0
Mar 24 10:40:46 latitude fprintd[14974]: Current SBI Version = 229
Mar 24 10:40:46 latitude fprintd[14974]: AAI version available for upgrade = 5.15.10.0
Mar 24 10:40:46 latitude fprintd[14974]: SBI version available for upgrade = 229
Mar 24 10:40:46 latitude fprintd[14974]: AAI version matches - it is up do date
Mar 24 10:40:46 latitude fprintd[14974]: SBI version matches - it is up do date
Mar 24 10:40:46 latitude fprintd[14974]: Citadel A0 CID7 Chip Found…
Mar 24 10:40:46 latitude fprintd[14974]: Sensor type : 12 Sensor firmware version on device: 3088084-109-0-3473 length: 18
Mar 24 10:40:46 latitude fprintd[14974]: Sensor-firmware file signature verification is valid
Mar 24 10:40:46 latitude fprintd[14974]: Sensor Version length: 16
Mar 24 10:40:46 latitude fprintd[14974]: Sensor Version: 3031663-2-0-3545
Mar 24 10:40:46 latitude fprintd[14974]: cv_check_sensor_firmware_upgradable: FALSE
Mar 24 10:40:46 latitude fprintd[14974]: cv_check_sensor_firmware_upgradable: Skipping
Mar 24 10:40:46 latitude fprintd[14974]: Sensor Version length: 18
Mar 24 10:40:46 latitude fprintd[14974]: Sensor Version: 3088084-109-0-3473
Mar 24 10:40:46 latitude fprintd[14974]: cv_check_sensor_firmware_upgradable: FALSE
Mar 24 10:40:46 latitude fprintd[14974]: cv_check_sensor_firmware_upgradable: Skipping
Mar 24 10:40:46 latitude fprintd[14974]: cv_check_sensor_firmware_upgradable: Skipping
Mar 24 10:40:46 latitude fprintd[14974]: Sensor Version length: 16
Mar 24 10:40:46 latitude fprintd[14974]: Sensor Version: 3031663-2-0-3528
Mar 24 10:40:46 latitude fprintd[14974]: cv_check_sensor_firmware_upgradable: FALSE
Mar 24 10:40:46 latitude fprintd[14974]: Couldn’t find UPDATABLE sensor-firmware for this sensor
Mar 24 10:40:46 latitude fprintd[14974]: Couldn’t get UPDATABLE firmware image data for sensor
Mar 24 10:40:46 latitude systemd[1]: Started fprintd.service - Fingerprint Authentication Daemon.
Mar 24 10:40:46 latitude audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg=‘unit=fprintd comm=“systemd” exe=“/usr/lib/systemd/systemd” hostname=? addr=? terminal=? res=success’
Mar 24 10:40:50 latitude audit[14988]: AUDIT1100 pid=14988 uid=1000 auid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg=‘op=PAM:authentication grantors=pam_unix acct=“sayuuk” exe=“/usr/lib/polkit-1/polkit-agent-helper-1” hostname=? addr=? terminal=? res=success’
Mar 24 10:40:50 latitude audit[14988]: AUDIT1101 pid=14988 uid=1000 auid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg=‘op=PAM:accounting grantors=pam_unix acct=“sayuuk” exe=“/usr/lib/polkit-1/polkit-agent-helper-1” hostname=? addr=? terminal=? res=success’
There’s nothing obvious going on there. There’s always the sledgehammer approach to debugging this by stracing the fprintd binary when it’s running. If you’re happy with a bit of terminal-based debugging then you could try something like this:
sudo dnf install strace
mkdir ~/tmp && cd ~/tmp
sudo systemctl stop fprintd
sudo setenforce 0
sudo strace -o fprintd -ff /usr/libexec/fprintd
When you have fprintd running via the above, try to use your fingerprint reader and/or register a new fingerprint. What you’ll end up with is a ton of files written to your ~/tmp directory that will show a trace of the fprintd daemon. This might yield a hint as to what’s going wrong.
When you’re done just ctrl+c the fprintd you started on the command line, set SELinux back to Enforcing mode (with setenforce 1) and restart fprintd via systemd.
I’ve sent an email to both your listed adresses - hope one makes it through.
1 Like
When I try to enroll, fprintd goes into Capture Mode, but then hangs for a bit.
Sensor firmware versions in file and on device match
Capture Initiated, Please place your finger now on the sensor now
cv_fingerprint_identify failed b :
Capture Initiated, Please place your finger now on the sensor now
Update enrollment is successful
More fingers needed
...
It then registers the 10 enrollment stages and then fails with enroll-unknown-error. fprintd reports:
Update enrollment failed : cancel capture
(fprintd:6275): fprintd-WARNING **: 11:37:58.392: Device reported an error during enroll: Enrollment failed : Device status = (11)
I’ll give strace a try and see if anything comes up.
I’ve sent you the strace output via Matrix, I hope this reaches you
1 Like
Hi grahamwhiteuk,
I have a Dell notebook with the same Broadcom 58200 ControlVault 3 Plus fingerprint reader:
Bus 003 Device 003: ID 0a5c:5865 Broadcom Corp. 58200
Running Fedora 43. I’d be happy to test your experimental CV3+ build and provide feedback, including SELinux debugging if needed. I’m comfortable reading journal logs and troubleshooting.
Thanks for your contributions
Niko
I have run up a build with experimental support for the newer CV3+ device IDs. This has been reported to work but I don’t have one of these chips to test with so I’m unable to test directly. Your mileage may vary but feel free to give it a go. I’m still working with some others on here that have kindly been testing things out so I may post an updated version in the future.
1 Like
Hi Graham,
I installed the packages from your COPR repo on Fedora 43 and the CV3+ firmware update ran successfully. Happy to report that enrollment and authentication are working with my device:
Bus 003 Device 003: ID 0a5c:5865 Broadcom Corp. 58200
One thing to note for other testers: the sensor tends to overheat during enrollment. After about 5-6 scans, the capture rate slows down noticeably. If you keep going too fast at that point, the device will disconnect with Device disabled to prevent overheating. The trick is to wait a few seconds between scans once it starts slowing down, and if it does disconnect, let the sensor cool down completely before retrying. It took me a couple of attempts but enrollment completed successfully.
SELinux enabled, libfprint-tod-selinux installed, no AVC denials observed.
Thanks for your work on this!
That’s great, thanks for the feedback and other useful tips. I don’t see overheating issues but my device ID is for the older chip.
There’s a newer version of the CV3+ firmware that I’ve deliberately not made available yet as it could potentially be less stable. I’m currently considering whether I should release an update as it could potentially help with the overheating issues (purely a guess on my part).
Thank you for your work on this!
I wanted to let you know that on my Dell laptop (with a fingerprint reader 0a5c:5865 Broadcom Corp. 58200 as well) this has been working fine on Fedora 43. The initial set-up took some slight debugging, but no more than five minutes of fiddling with the installation and it was up and running via Gnome’s user settings just like it should!
I’ve also had this fingerprint sensor working on Fedora 44 Beta for a week or so now with, but YMMV. I’d be glad to debug this 58200 chip for you as well if you need more people trying out devel builds.
I couldn’t re-produce the overheating effect on my end that was mentioned earlier during enrolment. No slowing downs either, but might depend on the exact workstation / chip / kernel / alignment of the stars combination too. Overall very, very stable: SELinux enabled + libfprint+tod+selinux installed, no AVC denials that I’ve noticed.
Whenever I try fprintd-enroll, it always errors out:
$ date && fprintd-enroll
Fri May 22 10:03:50 PM +08 2026
Using device /net/reactivated/Fprint/Device/0
Enrolling right-index-finger finger.
Enroll result: enroll-stage-passed
Enroll result: enroll-stage-passed
Enroll result: enroll-stage-passed
Enroll result: enroll-stage-passed
Enroll result: enroll-stage-passed
Enroll result: enroll-disconnected
journalctl:
May 22 22:03:50 furnace.yshmail.com systemd[1]: Starting fprintd.service - Fingerprint Authentication Daemon...
May 22 22:03:51 furnace.yshmail.com fprintd[23527]: In cvif_IsUshThere(), cv_get_ush_ver() status: (0x0)
May 22 22:03:51 furnace.yshmail.com fprintd[23527]: Control Vault getting chip type
May 22 22:03:51 furnace.yshmail.com fprintd[23527]: Citadel A0 CID7 Chip Found....
May 22 22:03:51 furnace.yshmail.com fprintd[23527]: Current AAI Version = 5.15.10.0
May 22 22:03:51 furnace.yshmail.com fprintd[23527]: Current SBI Version = 229
May 22 22:03:51 furnace.yshmail.com fprintd[23527]: AAI version available for upgrade = 5.15.10.0
May 22 22:03:51 furnace.yshmail.com fprintd[23527]: SBI version available for upgrade = 229
May 22 22:03:51 furnace.yshmail.com fprintd[23527]: AAI version matches - it is up do date
May 22 22:03:51 furnace.yshmail.com fprintd[23527]: SBI version matches - it is up do date
May 22 22:03:51 furnace.yshmail.com fprintd[23527]: Citadel A0 CID7 Chip Found....
May 22 22:03:51 furnace.yshmail.com fprintd[23527]: Sensor type : 16 Sensor firmware version on device: GF5288_GM188WNC_APP_10009 length: 25
May 22 22:03:51 furnace.yshmail.com fprintd[23527]: Sensor-firmware file signature verification is valid
May 22 22:03:51 furnace.yshmail.com fprintd[23527]: Sensor firmware version in file(sensor 16): GF5288_GM188WNC_APP_10009 length: 25
May 22 22:03:51 furnace.yshmail.com fprintd[23527]: Sensor firmware versions in file and on device match
May 22 22:03:51 furnace.yshmail.com systemd[1]: Started fprintd.service - Fingerprint Authentication Daemon.
May 22 22:03:51 furnace.yshmail.com audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=fprintd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
May 22 22:04:01 furnace.yshmail.com audit[23541]: AUDIT1100 pid=23541 uid=1000 auid=1000 ses=2 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=PAM:authentication grantors=pam_unix acct="rabbit" exe="/usr/lib/polkit-1/polkit-agent-helper-1" hostname=? addr=? terminal=? res=success'
May 22 22:04:01 furnace.yshmail.com audit[23541]: AUDIT1101 pid=23541 uid=1000 auid=1000 ses=2 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=PAM:accounting grantors=pam_unix acct="rabbit" exe="/usr/lib/polkit-1/polkit-agent-helper-1" hostname=? addr=? terminal=? res=success'
May 22 22:04:25 furnace.yshmail.com sway[2141]: 05:08:34.166 [ERROR] [wlr] [backend/drm/atomic.c:81] connector eDP-1: Atomic commit failed: Device or resource busy
May 22 22:04:25 furnace.yshmail.com sway[2141]: 05:08:34.166 [ERROR] [sway/desktop/output.c:300] Page-flip failed on output eDP-1
May 22 22:04:25 furnace.yshmail.com sway[2141]: 05:08:34.251 [ERROR] [wlr] [backend/drm/atomic.c:81] connector eDP-1: Atomic commit failed: Device or resource busy
May 22 22:04:25 furnace.yshmail.com sway[2141]: 05:08:34.251 [ERROR] [sway/desktop/output.c:300] Page-flip failed on output eDP-1
May 22 22:04:41 furnace.yshmail.com sway[2141]: 05:08:50.803 [ERROR] [wlr] [backend/drm/atomic.c:81] connector eDP-1: Atomic commit failed: Device or resource busy
May 22 22:04:41 furnace.yshmail.com sway[2141]: 05:08:50.803 [ERROR] [sway/desktop/output.c:300] Page-flip failed on output eDP-1
May 22 22:04:53 furnace.yshmail.com systemd[2097]: Starting blueman-manager.service - Bluetooth Manager...
May 22 22:04:54 furnace.yshmail.com systemd[2097]: Started blueman-manager.service - Bluetooth Manager.
May 22 22:04:54 furnace.yshmail.com pipewire-pulse[2361]: mod.protocol-pulse: setsockopt(SO_PRIORITY) failed: Bad file descriptor
May 22 22:04:54 furnace.yshmail.com pipewire-pulse[2361]: mod.protocol-pulse: client 0x55643c274b30: no peercred: Bad file descriptor
May 22 22:04:56 furnace.yshmail.com systemd[2097]: blueman-manager.service: Consumed 563ms CPU time over 2.261s wall clock time, 65.5M memory peak.
May 22 22:05:13 furnace.yshmail.com cat[2525]: [2526:2526:0522/220513.320571:ERROR:ui/compositor/compositor_animation_observer.cc:65] CompositorAnimationObserver is active for too long (110.35s) location=GlowHoverController@chrome/browser/ui/views/tabs/tab/glow_hover_controller.cc:17
May 22 22:05:27 furnace.yshmail.com pipewire-pulse[2361]: mod.protocol-pulse: setsockopt(SO_PRIORITY) failed: Bad file descriptor
May 22 22:05:27 furnace.yshmail.com pipewire-pulse[2361]: mod.protocol-pulse: client 0x55643c28b9a0: no peercred: Bad file descriptor
May 22 22:05:27 furnace.yshmail.com chronyd[1681]: Selected source 15.235.146.185 (2.fedora.pool.ntp.org)
May 22 22:05:42 furnace.yshmail.com pipewire-pulse[2361]: mod.protocol-pulse: setsockopt(SO_PRIORITY) failed: Bad file descriptor
May 22 22:05:42 furnace.yshmail.com pipewire-pulse[2361]: mod.protocol-pulse: client 0x55643c1632e0: no peercred: Bad file descriptor
May 22 22:05:43 furnace.yshmail.com sway[2141]: 05:09:52.719 [ERROR] [wlr] [backend/drm/atomic.c:81] connector eDP-1: Atomic commit failed: Device or resource busy
May 22 22:05:43 furnace.yshmail.com sway[2141]: 05:09:52.719 [ERROR] [sway/desktop/output.c:300] Page-flip failed on output eDP-1
May 22 22:05:43 furnace.yshmail.com sway[2141]: 05:09:52.769 [ERROR] [wlr] [backend/drm/atomic.c:81] connector eDP-1: Atomic commit failed: Device or resource busy
May 22 22:05:43 furnace.yshmail.com sway[2141]: 05:09:52.769 [ERROR] [sway/desktop/output.c:300] Page-flip failed on output eDP-1
May 22 22:05:43 furnace.yshmail.com sway[2141]: 05:09:52.803 [ERROR] [wlr] [backend/drm/atomic.c:81] connector eDP-1: Atomic commit failed: Device or resource busy
May 22 22:05:43 furnace.yshmail.com sway[2141]: 05:09:52.803 [ERROR] [sway/desktop/output.c:300] Page-flip failed on output eDP-1
May 22 22:05:55 furnace.yshmail.com sway[2141]: 05:10:04.336 [ERROR] [wlr] [backend/drm/atomic.c:81] connector eDP-1: Atomic commit failed: Device or resource busy
May 22 22:05:55 furnace.yshmail.com sway[2141]: 05:10:04.336 [ERROR] [sway/desktop/output.c:300] Page-flip failed on output eDP-1
May 22 22:05:55 furnace.yshmail.com sway[2141]: 05:10:04.703 [ERROR] [wlr] [backend/drm/atomic.c:81] connector eDP-1: Atomic commit failed: Device or resource busy
May 22 22:05:55 furnace.yshmail.com sway[2141]: 05:10:04.703 [ERROR] [sway/desktop/output.c:300] Page-flip failed on output eDP-1
May 22 22:06:07 furnace.yshmail.com sway[2141]: 05:10:16.204 [ERROR] [wlr] [backend/drm/atomic.c:81] connector eDP-1: Atomic commit failed: Device or resource busy
May 22 22:06:07 furnace.yshmail.com sway[2141]: 05:10:16.204 [ERROR] [sway/desktop/output.c:300] Page-flip failed on output eDP-1
May 22 22:06:08 furnace.yshmail.com sway[2141]: 05:10:17.520 [ERROR] [wlr] [backend/drm/atomic.c:81] connector eDP-1: Atomic commit failed: Device or resource busy
May 22 22:06:08 furnace.yshmail.com sway[2141]: 05:10:17.520 [ERROR] [sway/desktop/output.c:300] Page-flip failed on output eDP-1
May 22 22:06:12 furnace.yshmail.com sway[2141]: 05:10:21.103 [ERROR] [wlr] [backend/drm/atomic.c:81] connector eDP-1: Atomic commit failed: Device or resource busy
May 22 22:06:12 furnace.yshmail.com sway[2141]: 05:10:21.103 [ERROR] [sway/desktop/output.c:300] Page-flip failed on output eDP-1
May 22 22:06:21 furnace.yshmail.com sway[2141]: 05:10:30.820 [ERROR] [wlr] [backend/drm/atomic.c:81] connector eDP-1: Atomic commit failed: Device or resource busy
May 22 22:06:21 furnace.yshmail.com sway[2141]: 05:10:30.820 [ERROR] [sway/desktop/output.c:300] Page-flip failed on output eDP-1
May 22 22:06:22 furnace.yshmail.com sway[2141]: 05:10:31.720 [ERROR] [wlr] [backend/drm/atomic.c:81] connector eDP-1: Atomic commit failed: Device or resource busy
May 22 22:06:22 furnace.yshmail.com sway[2141]: 05:10:31.720 [ERROR] [sway/desktop/output.c:300] Page-flip failed on output eDP-1
May 22 22:07:04 furnace.yshmail.com fprintd[23527]: Device reported an error during enroll: Device disabled to prevent overheating.
Can I get some advice on how to fix this?
I’m using a Dell Latitude 7410 (Fedora 44 Sway Spin) with
Bus 001 Device 004: ID 0a5c:5843 Broadcom Corp. BCM58200 ControlVault 3 (FingerPrint sensor + Contacted SmartCard)
which should be supported.
I’m not sure what’s going on here. Would need some digging into the source code to figure out.
This works perfectly on Dell Latitude 7440 (0a5c:5843 Broadcom Corp. BCM58200 ControlVault 3 (FingerPrint sensor + Contacted SmartCard) with Fedora 44.
Thanks 
1 Like
Hello,
Thanks so much for all the effort on this.
I am using a Dell 7450 with 5860 Fingerprint reader, on Fedora 44 KDE Plasma Edition
lsusb
Bus 003 Device 006: ID 0a5c:5860 Broadcom Corp. 58200
I have tested with the following, but it seems device is not supported yet:
sudo dnf swap libfprint libfprint-tod
sudo dnf install libfprint-2-tod1-broadcom-cv3plus libfprint-tod-selinux
The output of:
sudo /usr/libexec/fprintd
gives:
/usr/libexec/fprintd
In cvif_IsUshThere(), cv_get_ush_ver() status: (0x0)
Control Vault getting chip type
Citadel B0 CID7 Chip Found....
Current AAI Version = 6.4.54.0
Current SBI Version = 240
AAI version available for upgrade = 6.0.55.0
SBI version available for upgrade = 48
Updating ControlVault firmware from 6.4.54.0 to 6.0.55.0
Event: FwUpgradeStarted
Upgrade the SBI from 240 to 48, first clear SCD
Writing /var/lib/fprint/.broadcomCv3plusFW/bcm_cv_clearscd.bin to flash
cv_flash_update() successful
Reset to SBI to update the SBI....
In cvif_IsUshThere(), cv_get_ush_ver() status: (0x13)
In cvif_IsUshThere(), cv_get_ush_ver() status: (0x0)
Found ControlVault Chip Type: Citadel B0 CID7
Event: FwUpgradeInProgress 1
Going to update SBI (bcmsbiCitadelB0_7.otp)
Writing /var/lib/fprint/.broadcomCv3plusFW/bcmsbiCitadelB0_7.otp to flash
Error: 0x47 from cv_flash_update()
ERROR: Failed to update SBI, status: 0x47
FwUpgradeError. Check Firmware Files or CID used or Hardware etc. Error: 0x7
libfprint-context-Message: 13:02:08.186: Ignoring device due to initialization error: An unspecified error occurred!
In cvif_IsUshThere(), cv_get_ush_ver() status: (0x0)
Control Vault getting chip type
Citadel B0 CID7 Chip Found....
Current AAI Version = ???
Current SBI Version = 240
AAI version available for upgrade = 6.0.55.0
SBI version available for upgrade = 48
Updating ControlVault firmware from ??? to 6.0.55.0
Event: FwUpgradeStarted
Upgrade the SBI from 240 to 48, first clear SCD
Writing /var/lib/fprint/.broadcomCv3plusFW/bcm_cv_clearscd.bin to flash
cv_flash_update() successful
Reset to SBI to update the SBI....
In cvif_IsUshThere(), cv_get_ush_ver() status: (0x13)
In cvif_IsUshThere(), cv_get_ush_ver() status: (0xb)
In cvif_IsUshThere(), cv_get_ush_ver() status: (0x0)
Found ControlVault Chip Type: Citadel B0 CID7
Event: FwUpgradeInProgress 1
Going to update SBI (bcmsbiCitadelB0_7.otp)
Writing /var/lib/fprint/.broadcomCv3plusFW/bcmsbiCitadelB0_7.otp to flash
Error: 0xb from cv_flash_update()
ERROR: Failed to update SBI, status: 0xb
FwUpgradeError. Check Firmware Files or CID used or Hardware etc. Error: 0x7
libfprint-context-Message: 13:02:15.934: Ignoring device due to initialization error: An unspecified error occurred!
Error: 0xb from cv_get_ush_ver()
In cvif_IsUshThere(), cv_get_ush_ver() status: (0xb)
In cvif_IsUshThere(), cv_get_ush_ver() status: (0xb)
In cvif_IsUshThere(), cv_get_ush_ver() status: (0xb)
In cvif_IsUshThere(), cv_get_ush_ver() status: (0xb)
In cvif_IsUshThere(), cv_get_ush_ver() status: (0xb)
Could NOT detect USH.
FwUpgradeError. Check Firmware Files or CID used or Hardware etc. Error: 0x1c
libfprint-context-Message: 13:02:38.977: Ignoring device due to initialization error: An unspecified error occurred!
root@Dell-7450:/home/alex#
The output of journalctl status is:
root@Dell-7450:/home/alex# systemctl status fprintd
● fprintd.service - Fingerprint Authentication Daemon
Loaded: loaded (/usr/lib/systemd/system/fprintd.service; static)
Drop-In: /usr/lib/systemd/system/service.d
└─10-timeout-abort.conf
Active: active (running) since Fri 2026-06-05 13:12:13 CEST; 11s ago
Invocation: b763f65e6a5148c5be3bb4323c6af209
Docs: man:fprintd(1)
Main PID: 10753 (fprintd)
Tasks: 6 (limit: 37759)
Memory: 2.2M (peak: 4.9M)
CPU: 140ms
CGroup: /system.slice/fprintd.service
└─10753 /usr/libexec/fprintd
Jun 05 13:11:53 Dell-7450 fprintd[10753]: Error: 0xb from cv_get_ush_ver()
Jun 05 13:11:56 Dell-7450 fprintd[10753]: In cvif_IsUshThere(), cv_get_ush_ver() status: (0xb)
Jun 05 13:12:00 Dell-7450 fprintd[10753]: In cvif_IsUshThere(), cv_get_ush_ver() status: (0xb)
Jun 05 13:12:04 Dell-7450 fprintd[10753]: In cvif_IsUshThere(), cv_get_ush_ver() status: (0xb)
Jun 05 13:12:08 Dell-7450 fprintd[10753]: In cvif_IsUshThere(), cv_get_ush_ver() status: (0xb)
Jun 05 13:12:12 Dell-7450 fprintd[10753]: In cvif_IsUshThere(), cv_get_ush_ver() status: (0xb)
Jun 05 13:12:13 Dell-7450 fprintd[10753]: Could NOT detect USH.
Jun 05 13:12:13 Dell-7450 fprintd[10753]: FwUpgradeError. Check Firmware Files or CID used or Hardware>
Jun 05 13:12:13 Dell-7450 fprintd[10753]: Ignoring device due to initialization error: An unspecified error occurred!
Jun 05 13:12:13 Dell-7450 systemd[1]: Started fprintd.service - Fingerprint Authentication Daemon.
I guess that indicates that this fp reader is not supported. Am a willing guinea pig to test, or have I missed something in the process?
Many thanks,
Alex
This isn’t a device ID I’m aware of being supported by either of the two firmware versions available or the older goodix drive that I’m not packaging.
Hi Graham,
Many thanks for the reply, and oh well. I will poke around and see what I can find, and maybe support will come up in the future.
All the best,
Alex