search

dsd / fprintd

http://reactivated.net/fprint/wiki/Fprintd
GNU General Public License v2.0
19 stars 3 forks source link

0a5c:5834 Broadcom Corp. - Device Support #3

Open inventortechie opened 7 years ago

inventortechie commented 7 years ago

Would like to add support for this Fingerprint Scanner. Detected this on Latitude 7480 via Ubuntu 17.04.

*I've also noticed a typo in the man file. Will try and see if it's avail in repo to provide correction.

lfarkas commented 1 year ago

i only know it's works for me. but mine is 0a5c:5843

adi8900 commented 1 year ago

someone made it working on arch? I tried installing https://aur.archlinux.org/packages/libfprint-2-tod1-broadcom , but it didn't work, fp isn't detected in fprintd, I have latitude 7390 with 0a5c:5834

AlexanderS commented 1 year ago

someone made it working on arch? [...] I have latitude 7390 with 0a5c:5834

The 0a5c:5834 is working nowhere. I am not aware of any driver for this device.

airwinb commented 1 year ago

someone made it working on arch? [...] I have latitude 7390 with 0a5c:5834

The 0a5c:5834 is working nowhere. I am not aware of any driver for this device.

I have it working on Manjaro linux and on a Dell Precision 3571. Steps:

I needed to stop, start en check the fprintd.service a few times (sudio systemctl start/stop/status fprintd.service) but in the end it worked.

AlexanderS commented 1 year ago

I have it working on Manjaro linux and on a Dell Precision 3571.

Can you confirm whether your device have the device id 0a5c:5843 or 0a5c:5834? The first one is working, but I am not aware of any driver for the second device.

airwinb commented 1 year ago

I have it working on Manjaro linux and on a Dell Precision 3571.

Can you confirm whether your device have the device id 0a5c:5843 or 0a5c:5834? The first one is working, but I am not aware of any driver for the second device.

Damn. The devil is in the details. Indeed my device is 0a5c:5843. Sorry for the mistake.

javierlongoriaroche commented 1 year ago

Any idea on how to wake it up without cold boot?

I don't think it's possible, the device is probably in a bad state, and resetting the USB port isn't enough.

But I no longer have issues with suspend. I don't know if it comes from kernel changes, BIOS updates, or the newer firmware I extracted from the Windows drivers.

Here is how I updated the firmware :

Note that several firmware files will be updated, it's quite slow (the progress is visible in the system logs, ie journalctl). If there is a timeout in fprintd, restarting it again should continue and eventually finish.

Ideally, it would be better to have matching versions of the libraries and firmware (it's up to Dell and/or Broadcom...). For example, the 5.9.8.17 Windows package has 5.9.3.1/5.9.7.16 drivers with a 5.9.013.0 firmware. But the 5.9 firmware seems to work fine with the 5.8 Linux libraries.

Did it excactly like you said and it finally worked!!! I'm using my Dell Latitude 5530 with Ubuntu 22.04 Jammy

TwisX commented 1 year ago

Any idea on how to wake it up without cold boot?

I don't think it's possible, the device is probably in a bad state, and resetting the USB port isn't enough. But I no longer have issues with suspend. I don't know if it comes from kernel changes, BIOS updates, or the newer firmware I extracted from the Windows drivers. Here is how I updated the firmware :

Note that several firmware files will be updated, it's quite slow (the progress is visible in the system logs, ie journalctl). If there is a timeout in fprintd, restarting it again should continue and eventually finish. Ideally, it would be better to have matching versions of the libraries and firmware (it's up to Dell and/or Broadcom...). For example, the 5.9.8.17 Windows package has 5.9.3.1/5.9.7.16 drivers with a 5.9.013.0 firmware. But the 5.9 firmware seems to work fine with the 5.8 Linux libraries.

Did it excactly like you said and it finally worked!!! I'm using my Dell Latitude 5530 with Ubuntu 22.04 Jammy

Followed these steps and the reader works for maybe 30 seconds, but then fprintd restarts itself and goes through the update process again. Rebooted several times. It's like it's stuck in an update loop. If I switch back to the old firmware it's fine (except the reader goes offline after a day or so, which is what I'm trying to fix).

I'm assuming you didn't encounter any such issue? I'm on a Dell Latitude 5430 with Pop!_OS 22.04 (Ubuntu-based).

javierlongoriaroche commented 1 year ago

Any idea on how to wake it up without cold boot?

I don't think it's possible, the device is probably in a bad state, and resetting the USB port isn't enough. But I no longer have issues with suspend. I don't know if it comes from kernel changes, BIOS updates, or the newer firmware I extracted from the Windows drivers. Here is how I updated the firmware :

Note that several firmware files will be updated, it's quite slow (the progress is visible in the system logs, ie journalctl). If there is a timeout in fprintd, restarting it again should continue and eventually finish. Ideally, it would be better to have matching versions of the libraries and firmware (it's up to Dell and/or Broadcom...). For example, the 5.9.8.17 Windows package has 5.9.3.1/5.9.7.16 drivers with a 5.9.013.0 firmware. But the 5.9 firmware seems to work fine with the 5.8 Linux libraries.

Did it excactly like you said and it finally worked!!! I'm using my Dell Latitude 5530 with Ubuntu 22.04 Jammy

Followed these steps and the reader works for maybe 30 seconds, but then fprintd restarts itself and goes through the update process again. Rebooted several times. It's like it's stuck in an update loop. If I switch back to the old firmware it's fine (except the reader goes offline after a day or so, which is what I'm trying to fix).

I'm assuming you didn't encounter any such issue? I'm on a Dell Latitude 5430 with Pop!_OS 22.04 (Ubuntu-based).

No, I had no issues after upgarding

hwti commented 1 year ago

Followed these steps and the reader works for maybe 30 seconds, but then fprintd restarts itself and goes through the update process again. Rebooted several times. It's like it's stuck in an update loop. If I switch back to the old firmware it's fine (except the reader goes offline after a day or so, which is what I'm trying to fix).

I'm assuming you didn't encounter any such issue? I'm on a Dell Latitude 5430 with Pop!_OS 22.04 (Ubuntu-based).

What do you have in the logs ? Maybe the update has an issue. Which libfprint-2-tod1-broadcom package do you have ?

As you can see on https://git.launchpad.net/~oem-solutions-engineers/libfprint-2-tod1-broadcom/+git/libfprint-2-tod1-broadcom/log/?h=jammy, there are several versions which haven't been pushed to the repositories :

So there shouldn't be any need to extract the Windows firmware now, the newer 5.12.018 library and firmwares should be better (but you would have to either build the deb yourself, or update the files yourself).

iconoclasthero commented 1 year ago

Followed these steps and the reader works for maybe 30 seconds, but then fprintd restarts itself and goes through the update process again. Rebooted several times. It's like it's stuck in an update loop. If I switch back to the old firmware it's fine (except the reader goes offline after a day or so, which is what I'm trying to fix). I'm assuming you didn't encounter any such issue? I'm on a Dell Latitude 5430 with Pop!_OS 22.04 (Ubuntu-based).

What do you have in the logs ? Maybe the update has an issue. Which libfprint-2-tod1-broadcom package do you have ?

As you can see on https://git.launchpad.net/~oem-solutions-engineers/libfprint-2-tod1-broadcom/+git/libfprint-2-tod1-broadcom/log/?h=jammy, there are several versions which haven't been pushed to the repositories :

  • 5.8.012.0-0ubuntu1~22.04.01~oem1, with maybe firmware 5.11.002.0 for CID1 (pre-production) chips, but firmware 5.9.013.0 for CID7 (production), so probably a firmware update loop with the provided bcm_cv_current_version.txt (due to the version mismatch)
  • 5.12.303-0ubuntu1~22.04.01~oem2, with 5.12.004.0 CID1 firmware, but still 5.9.013.0 for CID7 (firmware update loop)
  • 5.12.018-0ubuntu1~22.04.01, with 5.12.018.0 for all chips

So there shouldn't be any need to extract the Windows firmware now, the newer 5.12.018 library and firmwares should be better (but you would have to either build the deb yourself, or update the files yourself).

Any hope that any of the updates will work with 22.10? I am fairly sure that I will only be installing LTS after this, lol.

hwti commented 1 year ago

Any hope that any of the updates will work with 22.10? I am fairly sure that I will only be installing LTS after this, lol.

The packages on http://dell.archive.canonical.com are for 20.04, so built with OpenSSL 1.1 (libcrypto.so.1.1). Ubuntu doesn't provide OpenSSL 1.1.1 packages for 22.04 or later.

Instead of trying to install older OpenSSL packages, it's better to try newer libfprint-2-tod-1-broadcom.so, which are built on 22.04 (so with OpenSSL 3.0, libcrypto.so.3).

You can build your own package :

$ git clone -b jammy https://git.launchpad.net/libfprint-2-tod1-broadcom
$ cd libfprint-2-tod1-broadcom
$ dpkg-buildpackage

dpkg-buildpackage might ask for dependencies to be installed. After if has completed, you should have a libfprint-2-tod1-broadcom_5.12.018-0ubuntu1~22.04.01_amd64.deb in the parent directory.

vadimpiven commented 1 year ago

fedora users can use my repo: https://lfarkas.org/linux/packages/fedora/lfarkas.repo

rpm -e --nodeps libfprint
dnf install libfprint-tod libfprint-tod-broadcom

and reboot (sometimes the first reboot not working and needs 2 reboot:-)

our packages directly from: https://lfarkas.org/linux/packages/fedora/37/x86_64/

This worked for me on Dell Latitude 5431 with 0a5c:5843. Thanks for providing the package!

prafulla-git commented 1 year ago

Broadcom doesn't support Linux FP driver for chip: 0a5c:5834, it supports for 0a5c:584x.

prafulla-git commented 1 year ago

Got it working on Fedora 35, hardware is Lattitude 7400 (0a5c:5843) I recompiled fprintd from source (tag v1.94.1) and reinstalled it (sudo meson install) same with libfprintd using branch tod (sudo meson install) Cloned git://git.launchpad.net/~oem-solutions-engineers/libfprint-2-tod1-broadcom/+git/libfprint-2-tod1-broadcom and ran the install script.

In the end this is what I have:

lrwxrwxrwx. 1 root root      20 Sep 24 16:44 /usr/lib64/libfprint-2.so.2 -> libfprint-2.so.2.0.0
-rwxr-xr-x. 1 root root 2440288 Nov 11 11:59 /usr/lib64/libfprint-2.so.2.0.0
-rwxr-xr-x. 1 root root 1060656 Nov 11 11:31 /usr/lib64/libfprint-2/tod-1/libfprint-2-tod-1-broadcom.so
-rwxr-xr-x. 1 root root  605384 Nov 11 12:00 /usr/lib64/libfprint-2-tod.so
-rwxr-xr-x. 1 root root  605384 Nov 11 11:59 /usr/lib64/libfprint-2-tod.so.1
lrwxrwxrwx. 1 root root      23 Nov 11 12:06 /usr/lib/x86_64-linux-gnu/libfprint-2.so.2 -> /lib64/libfprint-2.so.2
-rwxr-xr-x. 1 root root 1060656 Nov 11 11:56 /usr/lib/x86_64-linux-gnu/libfprint-2/tod-1/libfprint-2-tod-1-broadcom.so
lrwxrwxrwx. 1 root root      16 Nov 11 11:59 /usr/local/lib64/libfprint-2.so -> libfprint-2.so.2
lrwxrwxrwx. 1 root root      20 Nov 11 11:59 /usr/local/lib64/libfprint-2.so.2 -> libfprint-2.so.2.0.0
-rwxr-xr-x. 1 root root 2440288 Nov 11 11:59 /usr/local/lib64/libfprint-2.so.2.0.0
-rwxr-xr-x. 1 root root 1060656 Nov 11 11:31 /usr/local/lib64/libfprint-2/tod-1/libfprint-2-tod-1-broadcom.so
lrwxrwxrwx. 1 root root      20 Nov 11 11:59 /usr/local/lib64/libfprint-2-tod.so -> libfprint-2-tod.so.1
-rwxr-xr-x. 1 root root  605384 Nov 11 11:58 /usr/local/lib64/libfprint-2-tod.so.1

Now journalctl -u fprintd shows that it has found the device with version 12. But it fails with a dbus error:

failed to claim device: GDBus.Error:net.reactivated.Fprint.Error.PermissionDenied: Not Authorized: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Action net.reactivated.fprint.device.enroll is not registered

Just reboot and voilà fprintd-enroll now work.

If you use the stock fprintd package from Fedora, then you get another type of error (that's why it's important te rebuild and install it from sources)

Error: 0xb from cv_get_ush_ver()
In cvif_IsUshThere(), cv_get_ush_ver() status: (0xb)
...
Could NOT detect USH.
UpgradeError. Check Firmware Files or CID used or Hardware etc. Error: 0x1c
Ignoring device due to initialization error: An unspecified error occurred!

Thanks all for your help.

EDIT: I can register a fingerprint but fprintd-verify seem to hang:

$ fprintd-verify 
Using device /net/reactivated/Fprint/Device/0
Listing enrolled fingers:
 - #0: right-index-finger
Verify started!
Verifying: right-index-finger

At that stage the daemon has output this:

Nov 11 12:53:00 dell systemd[1]: Starting Fingerprint Authentication Daemon...
Nov 11 12:53:00 dell fprintd[2145]: In cvif_IsUshThere(), cv_get_ush_ver() status: (0x0)
Nov 11 12:53:00 dell fprintd[2145]: Control Vault getting chip type
Nov 11 12:53:00 dell fprintd[2145]: Citadel A0 CID7 Chip Found....
Nov 11 12:53:00 dell fprintd[2145]: Current AAI Version = 5.8.12.0
Nov 11 12:53:00 dell fprintd[2145]: Current SBI Version = 122
Nov 11 12:53:00 dell fprintd[2145]: AAI version available for upgrade = 5.8.12.0
Nov 11 12:53:00 dell fprintd[2145]: SBI version available for upgrade = 122
Nov 11 12:53:00 dell fprintd[2145]: AAI version matches - it is up do date
Nov 11 12:53:00 dell fprintd[2145]: SBI version matches - it is up do date
Nov 11 12:53:00 dell fprintd[2145]: Citadel A0 CID7 Chip Found....
Nov 11 12:53:00 dell fprintd[2145]: Sensor type  : 12 Sensor firmware version on device: 3088084-109-0-3473 length: 18
Nov 11 12:53:00 dell fprintd[2145]: Sensor-firmware file signature verification is valid
Nov 11 12:53:00 dell fprintd[2145]: Sensor Version length: 16
Nov 11 12:53:00 dell fprintd[2145]: Sensor Version: 3031663-2-0-3545
Nov 11 12:53:00 dell fprintd[2145]: cv_check_sensor_firmware_upgradable: FALSE
Nov 11 12:53:00 dell fprintd[2145]: cv_check_sensor_firmware_upgradable: Skipping
Nov 11 12:53:00 dell fprintd[2145]: Sensor Version length: 18
Nov 11 12:53:00 dell fprintd[2145]: Sensor Version: 3088084-109-0-3473
Nov 11 12:53:00 dell fprintd[2145]: cv_check_sensor_firmware_upgradable: FALSE
Nov 11 12:53:00 dell fprintd[2145]: cv_check_sensor_firmware_upgradable: Skipping
Nov 11 12:53:00 dell fprintd[2145]: cv_check_sensor_firmware_upgradable: Skipping
Nov 11 12:53:00 dell fprintd[2145]: Sensor Version length: 16
Nov 11 12:53:00 dell fprintd[2145]: Sensor Version: 3031663-2-0-3528
Nov 11 12:53:00 dell fprintd[2145]: cv_check_sensor_firmware_upgradable: FALSE
Nov 11 12:53:00 dell fprintd[2145]: Couldn't find UPDATABLE sensor-firmware for this sensor
Nov 11 12:53:00 dell fprintd[2145]: Couldn't get UPDATABLE firmware image data for sensor
Nov 11 12:53:00 dell systemd[1]: Started Fingerprint Authentication Daemon.

Pressing the sensor doesn't do much at this point.

After a few minutes I Ctrl+C to terminate fprint-verify and then the daemon outputs this:

Nov 11 12:59:51 dell fprintd[2145]: Capture Initiated, Please place your finger now on the sensor now
Nov 11 12:59:51 dell fprintd[2145]: The interrupt processed data 3
Nov 11 12:59:51 dell systemd[1]: fprintd.service: Deactivated successfully.

libfprint-2-tod1-broadcom_5.12.x version fixed above issue.

prafulla-git commented 1 year ago

Followed these steps and the reader works for maybe 30 seconds, but then fprintd restarts itself and goes through the update process again. Rebooted several times. It's like it's stuck in an update loop. If I switch back to the old firmware it's fine (except the reader goes offline after a day or so, which is what I'm trying to fix). I'm assuming you didn't encounter any such issue? I'm on a Dell Latitude 5430 with Pop!_OS 22.04 (Ubuntu-based).

What do you have in the logs ? Maybe the update has an issue. Which libfprint-2-tod1-broadcom package do you have ? As you can see on https://git.launchpad.net/~oem-solutions-engineers/libfprint-2-tod1-broadcom/+git/libfprint-2-tod1-broadcom/log/?h=jammy, there are several versions which haven't been pushed to the repositories :

  • 5.8.012.0-0ubuntu1~22.04.01~oem1, with maybe firmware 5.11.002.0 for CID1 (pre-production) chips, but firmware 5.9.013.0 for CID7 (production), so probably a firmware update loop with the provided bcm_cv_current_version.txt (due to the version mismatch)
  • 5.12.303-0ubuntu1~22.04.01~oem2, with 5.12.004.0 CID1 firmware, but still 5.9.013.0 for CID7 (firmware update loop)
  • 5.12.018-0ubuntu1~22.04.01, with 5.12.018.0 for all chips

So there shouldn't be any need to extract the Windows firmware now, the newer 5.12.018 library and firmwares should be better (but you would have to either build the deb yourself, or update the files yourself).

Any hope that any of the updates will work with 22.10? I am fairly sure that I will only be installing LTS after this, lol.

5.12 release: http://dell.archive.canonical.com/updates/pool/public/libf/libfprint-2-tod1-broadcom/

prafulla-git commented 8 months ago

Hi,

5834 Linux support is not available, Linux support is added only from 584x.

-Prafulla Kota.

On Mon, Oct 30, 2023 at 6:36 PM Alan Barros de Oliveira < @.***> wrote:

arch

I know this is old, and you may already have solved you problem. Anyways, here what I've found so far: https://github.com/hummusbird/arch-fingerprint

— Reply to this email directly, view it on GitHub https://github.com/dsd/fprintd/issues/3#issuecomment-1785154664, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKHXRSIZJE7NB2YJBAN65DTYB6Q3VAVCNFSM4DRM2M3KU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCNZYGUYTKNBWGY2A . You are receiving this because you commented.Message ID: @.***>

-- Thanks, Prafulla Kota 9866544810

bentech4u commented 8 months ago

HI

i am on fedora 39 and installed packages through dnf,(from the above repos)

after restart fingerprint enroll is showing under user management and when i try to enroll, nothing is happening,

even i tried from command like and found below:

# fprintd-enroll ben Using device /net/reactivated/Fprint/Device/0 Enrolling right-index-finger finger. Enroll result: enroll-stage-passed Enroll result: enroll-unknown-error

device: Bus 003 Device 004: ID 0a5c:5843 Broadcom Corp. [unknown]

can anyone help me to achieve fingerprint login?

hwti commented 8 months ago

Enroll result: enroll-unknown-error

Do you get the error when touching the sensor for the second time ? There should be 10 stages, so at least 10 different captures of the same fingerprint.

What do you have in fprind logs (journalctl /usr/libexec/fprintd) ?

bentech4u commented 8 months ago

HI,

Thanks for the update, i was not aware that it needs to take 10 scans, after i did that, it is enrolled,

$ fprintd-list ben found 1 devices Device at /net/reactivated/Fprint/Device/0 Using device /net/reactivated/Fprint/Device/0 Fingerprints for user ben on Broadcom Sensors (press): - #0: right-index-finger

prafulla-git commented 8 months ago

Hi,

There is no linux support for 5834.

Prafulla

On Thu, 9 Nov, 2023, 02:39 Ben, @.***> wrote:

HI,

Thanks for the update, i was not aware that it needs to take 10 scans, after i did that, it is enrolled,

$ fprintd-list ben found 1 devices Device at /net/reactivated/Fprint/Device/0 Using device /net/reactivated/Fprint/Device/0 Fingerprints for user ben on Broadcom Sensors (press):

  • 0: right-index-finger

— Reply to this email directly, view it on GitHub https://github.com/dsd/fprintd/issues/3#issuecomment-1802685027, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKHXRSMD42XEMS7GM6Z4D5TYDPYKBAVCNFSM4DRM2M3KU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOBQGI3DQNJQGI3Q . You are receiving this because you commented.Message ID: @.***>

bagnaram commented 8 months ago

Hi @bentech4u I tried the same procedure on F39 with the above repo but I see: What did you do for 5843 to get the correct firmware files? Do I need to extract from the windows installer?

Nov 09 10:23:05 fedora systemd[1]: fprintd.service: Deactivated successfully.
Nov 09 10:22:35 fedora systemd[1]: Started fprintd.service - Fingerprint Authentication Daemon.
Nov 09 10:22:35 fedora fprintd[101116]: Ignoring device due to initialization error: An unspecified error occurred!
Nov 09 10:22:35 fedora fprintd[101116]:                 FwUpgradeError. Check Firmware Files or CID used or Hardware etc. Error: 0x1c
Nov 09 10:22:35 fedora fprintd[101116]: Could NOT detect USH.
Nov 09 10:22:34 fedora fprintd[101116]: In cvif_IsUshThere(), cv_get_ush_ver() status: (0x100002)
Nov 09 10:22:33 fedora fprintd[101116]: In cvif_IsUshThere(), cv_get_ush_ver() status: (0x100002)
Nov 09 10:22:32 fedora fprintd[101116]: In cvif_IsUshThere(), cv_get_ush_ver() status: (0x100002)
Nov 09 10:22:31 fedora fprintd[101116]: In cvif_IsUshThere(), cv_get_ush_ver() status: (0x100002)
Nov 09 10:22:30 fedora fprintd[101116]: In cvif_IsUshThere(), cv_get_ush_ver() status: (0x100002)
Nov 09 10:22:30 fedora fprintd[101116]: Error: 0x100002 from cv_get_ush_ver()
Nov 09 10:22:30 fedora systemd[1]: Starting fprintd.service - Fingerprint Authentication Daemon...

[fedora@fedora]~% rpm -qa | grep fprint
fprintd-1.94.2-8.fc39.x86_64
libfprint-tod-1.94.5+git20221202+tod1-1.fc37.x86_64
libfprint-tod-broadcom-5.12.018-1.fc37.x86_64
prafulla-git commented 8 months ago

Hi, I work for broadcom and we support 5843 on linux and we dont have any plans to support 5834 on linux.

Prafulla kota

On Thu, 9 Nov, 2023, 21:58 bagnaram, @.***> wrote:

Hi @bentech4u https://github.com/bentech4u I tried the same procedure on F39 with the above repo but I see: What did you do for 5843 to get the correct firmware files. Do I need to extract from the windows installer?

Nov 09 10:23:05 fedora systemd[1]: fprintd.service: Deactivated successfully. Nov 09 10:22:35 fedora systemd[1]: Started fprintd.service - Fingerprint Authentication Daemon. Nov 09 10:22:35 fedora fprintd[101116]: Ignoring device due to initialization error: An unspecified error occurred! Nov 09 10:22:35 fedora fprintd[101116]: FwUpgradeError. Check Firmware Files or CID used or Hardware etc. Error: 0x1c Nov 09 10:22:35 fedora fprintd[101116]: Could NOT detect USH. Nov 09 10:22:34 fedora fprintd[101116]: In cvif_IsUshThere(), cv_get_ush_ver() status: (0x100002) Nov 09 10:22:33 fedora fprintd[101116]: In cvif_IsUshThere(), cv_get_ush_ver() status: (0x100002) Nov 09 10:22:32 fedora fprintd[101116]: In cvif_IsUshThere(), cv_get_ush_ver() status: (0x100002) Nov 09 10:22:31 fedora fprintd[101116]: In cvif_IsUshThere(), cv_get_ush_ver() status: (0x100002) Nov 09 10:22:30 fedora fprintd[101116]: In cvif_IsUshThere(), cv_get_ush_ver() status: (0x100002) Nov 09 10:22:30 fedora fprintd[101116]: Error: 0x100002 from cv_get_ush_ver() Nov 09 10:22:30 fedora systemd[1]: Starting fprintd.service - Fingerprint Authentication Daemon... Nov 09 10:22:30 fedora systemd[1]: Stopped fprintd.service - Fingerprint Authentication Daemon. Nov 09 10:22:30 fedora systemd[1]: fprintd.service: Deactivated successfully. Nov 09 10:22:30 fedora systemd[1]: Stopping fprintd.service - Fingerprint Authentication Daemon... Nov 09 10:22:17 fedora systemd[1]: Started fprintd.service - Fingerprint Authentication Daemon.

— Reply to this email directly, view it on GitHub https://github.com/dsd/fprintd/issues/3#issuecomment-1804156391, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKHXRSJ4YVMMV6YUBYVHPDTYDUAEBAVCNFSM4DRM2M3KU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOBQGQYTKNRTHEYQ . You are receiving this because you commented.Message ID: @.***>

hackerb9 commented 8 months ago

Hi, I work for broadcom and we support 5843 on linux and we dont have any plans to support 5834 on linux. Prafulla kota

Thank you for letting us know. Would Broadcom be willing to release its internal documentation for the 5834 so the Linux community has a chance to write its own driver? Or does the 5834 rely on such information being kept secret to remain secure?

prafulla-git commented 8 months ago

Hi,

Broadcom company decided to keep information secret about secure fingerprint FIPS complaint chip, if you need support for this legacy chip, DELL can be asked and they will prioritise based on their business needs.

Thanks, Prafulla

On Mon, 13 Nov, 2023, 01:13 hackerb9, @.***> wrote:

Hi, I work for broadcom and we support 5843 on linux and we dont have any plans to support 5834 on linux. Prafulla kota

Thank you for letting us know. Would Broadcom be willing to release its internal documentation for the 5834 so the Linux community has a chance to write its own driver? Or does the 5834 rely on such information being kept secret to remain secure?

— Reply to this email directly, view it on GitHub https://github.com/dsd/fprintd/issues/3#issuecomment-1807220483, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKHXRSIU5K25GHB66Y44BETYEERGTAVCNFSM4DRM2M3KU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOBQG4ZDEMBUHAZQ . You are receiving this because you commented.Message ID: @.***>

hackerb9 commented 8 months ago

Hi, Broadcom company decided to keep information secret about secure fingerprint FIPS compliant chip, if you need support for this legacy chip, DELL can be asked and they will prioritise based on their business needs. Thanks, Prafulla

Thank you, that is again very informative!

My business is not looking for further support with this legacy device. Linux drivers never came, so we wrote it off as a loss long ago. It was yet another reminder to avoid relying on any manufacturer for drivers.

I hope Broadcom executives will someday see that treating the programming information for their chips as proprietary trade secrets dramatically reduces Broadcom's value to businesses.

Thank you again for doing all you can and keeping us informed, Prafulla.