Related issue, https://www.dell.com/community/Latitude/Fingerprint-driver-for-GNU-Linux/m-p/7563679#M21440

With a fresh install of Ubuntu 20.04.3 on a Latitude 7420 the 0a5c:5843 Broadcom fingerprint reader is working! I had to go into Software & Updates -> Additional Drivers and move the radio button to "Using Broadcom fingerprint TOD driver from libfprint-2-tod1-broadcom (open source)". Then I was able to add fingerprints in Settings -> Users, open a terminal, run sudo pam-auth-update, and enable Fingerprint authentication. I also just got it working on my Latitude 9410 with the same reader, running 21.04. They both have the libfprint-2-tod1 package installed. The trick is to enable the Canonical Partners repo for somerville and somerville-melissa (on 9410 and somerville-squirtle on 7420), then go back into Additional drivers and switch the radio button to use the newly found driver.

fprintd does not work with this dell driver:

Oct 31 21:49:22 host systemd[1]: Starting Fingerprint Authentication Daemon...
Oct 31 21:49:22 host fprintd[6647]: Failed to open /sys/bus/usb/devices/1-10/power/persist
Oct 31 21:49:22 host fprintd[6647]: In cvif_IsUshThere(), cv_get_ush_ver() status: (0x0)
Oct 31 21:49:22 host fprintd[6647]: Control Vault getting chip type
Oct 31 21:49:22 host fprintd[6647]: Citadel A0 CID7 Chip Found....
Oct 31 21:49:22 host fprintd[6647]: Current AAI Version = 5.8.12.0
Oct 31 21:49:22 host fprintd[6647]: Current SBI Version = 122
Oct 31 21:49:22 host fprintd[6647]: AAI version available for upgrade = 5.8.12.0
Oct 31 21:49:22 host fprintd[6647]: SBI version available for upgrade = 122
Oct 31 21:49:22 host fprintd[6647]: AAI version matches - it is up do date
Oct 31 21:49:22 host fprintd[6647]: SBI version matches - it is up do date
Oct 31 21:49:22 host fprintd[6647]: Citadel A0 CID7 Chip Found....
Oct 31 21:49:22 host fprintd[6647]: Sensor type  : 12 Sensor firmware version on device: 3088084-109-0-3473 length: 18
Oct 31 21:49:22 host fprintd[6647]: Sensor-firmware file signature verification is valid
Oct 31 21:49:22 host fprintd[6647]: Sensor Version length: 16
Oct 31 21:49:22 host fprintd[6647]: Sensor Version: 3031663-2-0-3545
Oct 31 21:49:22 host fprintd[6647]: cv_check_sensor_firmware_upgradable: FALSE
Oct 31 21:49:22 host fprintd[6647]: cv_check_sensor_firmware_upgradable: Skipping
Oct 31 21:49:22 host fprintd[6647]: Sensor Version length: 18
Oct 31 21:49:22 host fprintd[6647]: Sensor Version: 3088084-109-0-3473
Oct 31 21:49:22 host fprintd[6647]: cv_check_sensor_firmware_upgradable: FALSE
Oct 31 21:49:22 host fprintd[6647]: cv_check_sensor_firmware_upgradable: Skipping
Oct 31 21:49:22 host fprintd[6647]: cv_check_sensor_firmware_upgradable: Skipping
Oct 31 21:49:22 host fprintd[6647]: Sensor Version length: 16
Oct 31 21:49:22 host fprintd[6647]: Sensor Version: 3031663-2-0-3528
Oct 31 21:49:22 host fprintd[6647]: cv_check_sensor_firmware_upgradable: FALSE
Oct 31 21:49:22 host fprintd[6647]: Couldn't find UPDATABLE sensor-firmware for this sensor
Oct 31 21:49:22 host fprintd[6647]: Couldn't get UPDATABLE firmware image data for sensor
Oct 31 21:49:22 host fprintd[6647]: fpi_device_probe_complete: assertion 'priv->current_action == FPI_DEVICE_ACTION_PROBE' failed
Oct 31 21:49:47 host dbus-daemon[903]: [system] Failed to activate service 'net.reactivated.Fprint': timed out (service_start_timeout=25000ms)
Oct 31 21:50:52 host systemd[1]: fprintd.service: start operation timed out. Terminating.
Oct 31 21:51:02 host systemd[1]: fprintd.service: State 'stop-sigterm' timed out. Killing.
Oct 31 21:51:02 host systemd[1]: fprintd.service: Killing process 6647 (fprintd) with signal SIGKILL.
Oct 31 21:51:02 host systemd[1]: fprintd.service: Main process exited, code=killed, status=9/KILL
Oct 31 21:51:02 host systemd[1]: fprintd.service: Failed with result 'timeout'.
Oct 31 21:51:02 host systemd[1]: Failed to start Fingerprint Authentication Daemon.

It works on both of mine and several of my co-workers. I've had an issue of it crashing and I have to wait for a timeout before it asks for my password. A reboot fixes that. You can see from my log that it had crashed at around 19:45 and I rebooted at 20:42 and it loaded properly again:

Nov  2 19:04:12 C77D7G3 fprintd[174832]: Sensor-firmware file signature verification is valid
Nov  2 19:04:12 C77D7G3 fprintd[174832]: Sensor firmware version in file(sensor 16): GF5288_GM188WNC_APP_10009 length: 25
Nov  2 19:04:12 C77D7G3 fprintd[174832]: Sensor firmware versions in file and on device match
Nov  2 19:04:30 C77D7G3 fprintd[174832]: Client :1.603 not authorized to call method 'Claim' for device Broadcom Sensors: Device was already claimed
Nov  2 19:05:12 C77D7G3 fprintd[174832]: Capture Initiated, Please place your finger now on the sensor now
Nov  2 19:05:12 C77D7G3 fprintd[174832]: cv_open() return status: 0xb
Nov  2 19:05:55 C77D7G3 systemd[1]: fprintd.service: Succeeded.
Nov  2 19:45:26 C77D7G3 dbus-daemon[958]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' requested by ':1.92' (uid=1000 pid=2580 comm="/usr/bin/gnome-shell " label="unconfined")
Nov  2 19:45:29 C77D7G3 fprintd[184530]: Error: 0xb from cv_get_ush_ver()
Nov  2 19:45:32 C77D7G3 fprintd[184530]: In cvif_IsUshThere(), cv_get_ush_ver() status: (0xb)
Nov  2 19:45:36 C77D7G3 fprintd[184530]: In cvif_IsUshThere(), cv_get_ush_ver() status: (0xb)
Nov  2 19:45:48 C77D7G3 fprintd[184530]: message repeated 3 times: [ In cvif_IsUshThere(), cv_get_ush_ver() status: (0xb)]
Nov  2 19:45:49 C77D7G3 fprintd[184530]: Could NOT detect USH.
Nov  2 19:45:49 C77D7G3 fprintd[184530]: #011#011FwUpgradeError. Check Firmware Files or CID used or Hardware etc. Error: 0x1c
Nov  2 19:45:49 C77D7G3 fprintd[184530]: Ignoring device due to initialization error: An unspecified error occurred!
Nov  2 19:46:19 C77D7G3 systemd[1]: fprintd.service: Succeeded.
Nov  2 19:47:21 C77D7G3 dbus-daemon[958]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' requested by ':1.664' (uid=0 pid=185368 comm="sudo systemctl restart fprintd " label="unconfined")
Nov  2 19:47:24 C77D7G3 fprintd[185369]: Error: 0xb from cv_get_ush_ver()
Nov  2 19:47:27 C77D7G3 fprintd[185369]: In cvif_IsUshThere(), cv_get_ush_ver() status: (0xb)
Nov  2 19:47:43 C77D7G3 fprintd[185369]: message repeated 4 times: [ In cvif_IsUshThere(), cv_get_ush_ver() status: (0xb)]
Nov  2 19:47:44 C77D7G3 fprintd[185369]: Could NOT detect USH.
Nov  2 19:47:44 C77D7G3 fprintd[185369]: #011#011FwUpgradeError. Check Firmware Files or CID used or Hardware etc. Error: 0x1c
Nov  2 19:47:44 C77D7G3 fprintd[185369]: Ignoring device due to initialization error: An unspecified error occurred!
Nov  2 19:47:50 C77D7G3 systemd[1]: fprintd.service: Succeeded.
Nov  2 19:47:53 C77D7G3 fprintd[185407]: Error: 0xb from cv_get_ush_ver()
Nov  2 19:47:56 C77D7G3 fprintd[185407]: In cvif_IsUshThere(), cv_get_ush_ver() status: (0xb)
Nov  2 19:48:12 C77D7G3 fprintd[185407]: message repeated 4 times: [ In cvif_IsUshThere(), cv_get_ush_ver() status: (0xb)]
Nov  2 19:48:13 C77D7G3 fprintd[185407]: Could NOT detect USH.
Nov  2 19:48:13 C77D7G3 fprintd[185407]: #011#011FwUpgradeError. Check Firmware Files or CID used or Hardware etc. Error: 0x1c
Nov  2 19:48:13 C77D7G3 fprintd[185407]: Ignoring device due to initialization error: An unspecified error occurred!
Nov  2 19:48:43 C77D7G3 systemd[1]: fprintd.service: Succeeded.
Nov  2 19:48:50 C77D7G3 dbus-daemon[958]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' requested by ':1.668' (uid=0 pid=185573 comm="sudo tail -n 50 /var/log/syslog " label="unconfined")
Nov  2 19:48:53 C77D7G3 fprintd[185575]: Error: 0xb from cv_get_ush_ver()
Nov  2 19:48:56 C77D7G3 fprintd[185575]: In cvif_IsUshThere(), cv_get_ush_ver() status: (0xb)
Nov  2 19:49:12 C77D7G3 fprintd[185575]: message repeated 4 times: [ In cvif_IsUshThere(), cv_get_ush_ver() status: (0xb)]
Nov  2 19:49:13 C77D7G3 fprintd[185575]: Could NOT detect USH.
Nov  2 19:49:13 C77D7G3 fprintd[185575]: #011#011FwUpgradeError. Check Firmware Files or CID used or Hardware etc. Error: 0x1c
Nov  2 19:49:13 C77D7G3 fprintd[185575]: Ignoring device due to initialization error: An unspecified error occurred!
Nov  2 19:49:43 C77D7G3 systemd[1]: fprintd.service: Succeeded.
Nov  2 20:33:25 C77D7G3 dbus-daemon[958]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' requested by ':1.92' (uid=1000 pid=2580 comm="/usr/bin/gnome-shell " label="unconfined")
Nov  2 20:33:28 C77D7G3 fprintd[187245]: Error: 0xb from cv_get_ush_ver()
Nov  2 20:33:31 C77D7G3 fprintd[187245]: In cvif_IsUshThere(), cv_get_ush_ver() status: (0xb)
Nov  2 20:33:35 C77D7G3 fprintd[187245]: In cvif_IsUshThere(), cv_get_ush_ver() status: (0xb)
Nov  2 20:33:39 C77D7G3 fprintd[187245]: In cvif_IsUshThere(), cv_get_ush_ver() status: (0xb)
Nov  2 20:33:43 C77D7G3 fprintd[187245]: In cvif_IsUshThere(), cv_get_ush_ver() status: (0xb)
Nov  2 20:33:47 C77D7G3 fprintd[187245]: In cvif_IsUshThere(), cv_get_ush_ver() status: (0xb)
Nov  2 20:33:48 C77D7G3 fprintd[187245]: Could NOT detect USH.
Nov  2 20:33:48 C77D7G3 fprintd[187245]: #011#011FwUpgradeError. Check Firmware Files or CID used or Hardware etc. Error: 0x1c
Nov  2 20:33:48 C77D7G3 fprintd[187245]: Ignoring device due to initialization error: An unspecified error occurred!
Nov  2 20:34:19 C77D7G3 systemd[1]: fprintd.service: Succeeded.
Nov  2 20:42:49 C77D7G3 dbus-daemon[980]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' requested by ':1.38' (uid=125 pid=1624 comm="/usr/bin/gnome-shell " label="unconfined")
Nov  2 20:42:49 C77D7G3 fprintd[1909]: In cvif_IsUshThere(), cv_get_ush_ver() status: (0x0)
Nov  2 20:42:49 C77D7G3 fprintd[1909]: Control Vault getting chip type
Nov  2 20:42:49 C77D7G3 fprintd[1909]: Citadel A0 CID7 Chip Found....
Nov  2 20:42:49 C77D7G3 fprintd[1909]: Current AAI Version = 5.8.12.0
Nov  2 20:42:49 C77D7G3 fprintd[1909]: Current SBI Version = 122
Nov  2 20:42:49 C77D7G3 fprintd[1909]: AAI version available for upgrade = 5.8.12.0
Nov  2 20:42:49 C77D7G3 fprintd[1909]: SBI version available for upgrade = 122
Nov  2 20:42:49 C77D7G3 fprintd[1909]: AAI version matches - it is up do date
Nov  2 20:42:49 C77D7G3 fprintd[1909]: SBI version matches - it is up do date
Nov  2 20:42:49 C77D7G3 fprintd[1909]: Citadel A0 CID7 Chip Found....
Nov  2 20:42:49 C77D7G3 fprintd[1909]: Sensor type  : 16 Sensor firmware version on device: GF5288_GM188WNC_APP_10009 length: 25
Nov  2 20:42:49 C77D7G3 fprintd[1909]: Sensor-firmware file signature verification is valid
Nov  2 20:42:49 C77D7G3 fprintd[1909]: Sensor firmware version in file(sensor 16): GF5288_GM188WNC_APP_10009 length: 25
Nov  2 20:42:49 C77D7G3 fprintd[1909]: Sensor firmware versions in file and on device match

You might have a firmware issue. I see these differences in our logs:

Yours shows this:

Oct 31 21:49:22 host fprintd[6647]: Citadel A0 CID7 Chip Found....
Oct 31 21:49:22 host fprintd[6647]: Sensor type  : 12 Sensor firmware version on device: 3088084-109-0-3473 length: 18
Oct 31 21:49:22 host fprintd[6647]: Sensor-firmware file signature verification is valid
Oct 31 21:49:22 host fprintd[6647]: Sensor Version length: 16
Oct 31 21:49:22 host fprintd[6647]: Sensor Version: 3031663-2-0-3545
Oct 31 21:49:22 host fprintd[6647]: cv_check_sensor_firmware_upgradable: FALSE
Oct 31 21:49:22 host fprintd[6647]: cv_check_sensor_firmware_upgradable: Skipping
Oct 31 21:49:22 host fprintd[6647]: Sensor Version length: 18

Mine shows this with the same sensor:

Nov  2 20:42:49 C77D7G3 fprintd[1909]: Citadel A0 CID7 Chip Found....
Nov  2 20:42:49 C77D7G3 fprintd[1909]: Sensor type  : 16 Sensor firmware version on device: GF5288_GM188WNC_APP_10009 length: 25
Nov  2 20:42:49 C77D7G3 fprintd[1909]: Sensor-firmware file signature verification is valid
Nov  2 20:42:49 C77D7G3 fprintd[1909]: Sensor firmware version in file(sensor 16): GF5288_GM188WNC_APP_10009 length: 25
Nov  2 20:42:49 C77D7G3 fprintd[1909]: Sensor firmware versions in file and on device match

No, I didn't run that but I did install firmware updates using these:

sudo fwupdmgr refresh
sudo fwupdmgr get-updates
sudo fwupdmgr update

Do you need to run the `/usr/bin/update-fw.py` before using this driver?

I tried running it but it would not show any output.. 

What does "lsusb -v -d 0a5c:5843" give you? Mine shows the info below. I'd be surprised if Dell used a different device with the same vendor:product code

lsusb -v -d 0a5c:5843

Bus 003 Device 003: ID 0a5c:5843 Broadcom Corp. 58200
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x0a5c Broadcom Corp.
  idProduct          0x5843 
  bcdDevice            1.02
  iManufacturer           1 Broadcom Corp
  iProduct                2 58200
  iSerial                 3 0123456789ABCD
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength       0x0037
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0xe0
      Self Powered
      Remote Wakeup
    MaxPower              100mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           3
      bInterfaceClass       254 Application Specific Interface
      bInterfaceSubClass      0 
      bInterfaceProtocol      0 
      iInterface              4 Broadcom ControlVault 3 w/FingerPrint
      ** UNRECOGNIZED:  10 25 00 00 00 00 00 00 00 00 00 00 00 00 00 00
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x01  EP 1 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x85  EP 5 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0400  1x 1024 bytes
        bInterval               1
Device Qualifier (for other device speed):
  bLength                10
  bDescriptorType         6
  bcdUSB               2.00
  bDeviceClass            0 
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  bNumConfigurations      1
Device Status:     0x0000
  (Bus Powered)

This is another thread on this forum where a couple have confirmed that it worked for them, even in Arch Linux: https://www.dell.com/community/Latitude/Fingerprint-driver-for-GNU-Linux/td-p/7563679/page/3

My device seems to have another sensor type: 12

While your has sensor type: 16

And that must be the reason why it's not working.... 

Device ID matches 0a5c:5843, but my bcdDevice=1.01 comparing to yours bcdDevice=1.02 (this is device release number).

It disappears from the connected USB devices list after the first suspend/resume, so I'd need to power-off and boot again to give you the full output of lsusb for it (cannot do it right now, I can do it later).

So, the device ID matches but the device release number is different here. 

Thanks, this works for Dell Precision 7550 laptop also!

Confirm - this method works fine with Latitude 5310. The first problem was that Ubuntu 20.04.3 couldn't find additional drivers even if Canonical Partners source was marked. The solution is to install oem-somerville-melisa package (hardware support for XPS 13 9300) from Synaptic Package Manager for example. Then the drivers was found just as Jermaine151 described. Sensor now works fine

Hi, I have a Latitude 5411 laptop with a Broadcom 58200 module. I want to run the fingerprint reader. Despite many attempts, the reader did not work.

lsusb -v -d 0a5c:5843
Bus 001 Device 002: ID 0a5c:5843 Broadcom Corp. 58200
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 
bDeviceSubClass 0 
bDeviceProtocol 0 
bMaxPacketSize0 64
idVendor 0x0a5c Broadcom Corp.
idProduct 0x5843 
bcdDevice 1.01
iManufacturer 1 Broadcom Corp
iProduct 2 58200
iSerial 3 0123456789ABCD
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x008b
bNumInterfaces 2
bConfigurationValue 1
iConfiguration 0 
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 254 Application Specific Interface
bInterfaceSubClass 0 
bInterfaceProtocol 0 
iInterface 4 Broadcom ControlVault 3 w/FingerPrint
** UNRECOGNIZED: 10 25 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x85 EP 5 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0400 1x 1024 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 11 Chip/SmartCard
bInterfaceSubClass 0 
bInterfaceProtocol 0 
iInterface 5 Contacted SmartCard
ChipCard Interface Descriptor:
bLength 54
bDescriptorType 33
bcdCCID 1.00
nMaxSlotIndex 0
bVoltageSupport 7 5.0V 3.0V 1.8V 
dwProtocols 3 T=0 T=1
dwDefaultClock 4000
dwMaxiumumClock 4000
bNumClockSupported 0
dwDataRate 9600 bps
dwMaxDataRate 250000 bps
bNumDataRatesSupp. 0
dwMaxIFSD 247
dwSyncProtocols 00000000 
dwMechanical 00000000 
dwFeatures 000102BA
Auto configuration based on ATR
Auto voltage selection
Auto clock change
Auto baud rate change
Auto PPS made by CCID
NAD value other than 0x00 accepted
TPDU level exchange
dwMaxCCIDMsgLen 271
bClassGetResponse 00
bClassEnvelope 00
wlcdLayout none
bPINSupport 0 
bMaxCCIDBusySlots 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x86 EP 6 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0400 1x 1024 bytes
bInterval 1
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 0 
bDeviceSubClass 0 
bDeviceProtocol 0 
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0000
(Bus Powered)


fprintd-enroll
Impossible to enroll: GDBus.Error:net.reactivated.Fprint.Error.NoSuchDevice: No devices available

uname -r
5.17.4-051704-generic

cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=22.04
DISTRIB_CODENAME=jammy
DISTRIB_DESCRIPTION="Ubuntu 22.04 LTS"

I'd like to summarize all the steps I did to get my Finger Print reader Broadcom Corp. 58200, USB ID 0a5c:5842 working in my Dell Latitude 5500. 

First, I update the firmware (thanks to jermaine151):

sudo fwupdmgr refresh
sudo fwupdmgr get-updates
sudo fwupdmgr update

Be advised after the first reboot, the BIOS firmware update will start, and this process cannot be canceled, and it is very long. Make sure to not turn off your computer. Keep it plugged in power. 

After that, I add the  `oem-somerville-melisa-meta` package (thanks ironic_):

sudo apt install oem-somerville-melisa-meta
sudo apt update
sudo apt upgrade

Another trick process. After installing the package, it adds the Canonical Partners Somerville apt repository, but it doesn't refresh the packages. You need to do it manually, then restart your computer. 

And the last step, open "Software & Updates" app, select the "Additional Drivers" tab, and voilá, you'll see your Broadcom driver:

Check the Broadcom driver, and restart your computer again. 

Once it is done, you'll be able to enable the fingerprint login in "Settings" -> "Users".

Thank you all for helping me with that. I hated Broadcom for over a decade because they only do drivers for Windows. Unfortunately, Dell insists to ship your computer with this brand, but now, I am more joyful with that solution (but still hate Broadcom).