Dell Inspiron 5370 Fingerprint Reader not detected
Hi,
I am using the new dell inspiron 5370 with 8th gen i5 which has an inbuilt fingerprint reader working out of the box on windows 10. But on Bionic Beaver it is not even showing up.
avraw@alfred:~$ sudo lsusb
[sudo] password for avraw:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 27c6:5301
Bus 001 Device 003: ID 0cf3:e009 Atheros Communications, Inc.
Bus 001 Device 002: ID 0bda:576d Realtek Semiconductor Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Here is an lshw :
avraw@alfred:~$ sudo lshw
alfred
description: Notebook
product: Inspiron 5370 (082C)
vendor: Dell Inc.
serial: FWXY802
width: 64 bits
capabilities: smbios-3.0 dmi-3.0 smp vsyscall32
configuration: boot=normal chassis=notebook family=Inspiron sku=082C uuid=44454C4C-
*-core
description: Motherboard
product: 0PMMMX
vendor: Dell Inc.
physical id: 0
version: A00
serial: /FWXY802/
*-firmware
vendor: Dell Inc.
physical id: 0
version: 1.4.1
date: 01/25/2018
size: 64KiB
capacity: 15MiB
*-memory
physical id: 3a
slot: System board or motherboard
size: 8GiB
*-bank:0
slot: DIMM A
size: 8GiB
width: 64 bits
clock: 2400MHz (0.4ns)
*-bank:1
slot: ChannelB-DIMM0
*-cache:0
physical id: 3e
slot: L1 Cache
size: 256KiB
capacity: 256KiB
*-cache:1
physical id: 3f
slot: L2 Cache
size: 1MiB
capacity: 1MiB
*-cache:2
physical id: 40
slot: L3 Cache
size: 6MiB
capacity: 6MiB
*-cpu
product: Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz
vendor: Intel Corp.
physical id: 41
bus info: cpu@0
version: Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz
serial: To Be Filled By O.E.M.
slot: U3E1
size: 3397MHz
capacity: 3400MHz
width: 64 bits
clock: 100MHz
*-pci
product: Intel Corporation
vendor: Intel Corporation
physical id: 100
bus info: pci@0000:00:00.0
version: 08
width: 32 bits
clock: 33MHz
*-display
bus info: pci@0000:00:02.0
width: 64 bits
clock: 33MHz
*-generic:0
bus info: pci@0000:00:04.0
width: 64 bits
clock: 33MHz
*-usb
bus info: pci@0000:00:14.0
width: 64 bits
clock: 33MHz
bus info: usb@1
bus info: usb@2
*-generic:1
bus info: pci@0000:00:14.2
width: 64 bits
clock: 33MHz
*-generic:2
bus info: pci@0000:00:15.0
width: 64 bits
clock: 33MHz
bus info: pci@0000:00:16.0
width: 64 bits
clock: 33MHz
*-storage
bus info: pci@0000:00:17.0
width: 32 bits
clock: 66MHz
*-pci
bus info: pci@0000:00:1c.0
width: 32 bits
clock: 33MHz
bus info: pci@0000:01:00.0
*-generic:3
bus info: pci@0000:00:1e.0
width: 64 bits
clock: 33MHz
*-generic:4
bus info: pci@0000:00:1e.4
width: 64 bits
clock: 33MHz
*-isa
bus info: pci@0000:00:1f.0
width: 32 bits
clock: 33MHz
*-memory UNCLAIMED
bus info: pci@0000:00:1f.2
width: 32 bits
clock: 33MHz (30.3ns)
bus info: pci@0000:00:1f.3
width: 64 bits
clock: 33MHz
*-serial UNCLAIMED
bus info: pci@0000:00:1f.4
width: 64 bits
clock: 33MHz
*-scsi
physical id: 1
logical name: scsi2
*-disk
bus info: scsi@2:0.0.0
size: 238GiB (256GB)
bus info: scsi@2:0.0.0,1
bus info: scsi@2:0.0.0,2
*-battery
product: DELL 39DY56B
vendor: SMP
physical id: 1
version: 11/01/2017
serial: 05D1
slot: Sys. Battery Bay
capacity: 37990mWh
Tried using libfprint but without even the device not recognizing it wont work.
Any leads would be appreciated.
Thanks
Question information
- Language:
- English Edit question
- Status:
- Answered
- For:
- Ubuntu Edit question
- Assignee:
- No assignee Edit question
- Last query:
- 2018-05-01
- Last reply:
- 2018-05-01
Manfred Hampl (m-hampl) said : | #1 |
The fact that there is no text besides the USB-ID in the lsusb output is not relevant. This text is taken from a list of USB IDs which is incomplete - http://
The important output is from lshw, and it shows details about that device, including the name of the driver that is loaded for it:
This confirms that the device is detected.
What is the output of the diagnostic commands:
dmesg | grep -i usb
ls -l /dev/ttyAC*
Hi Manfred,
PFB
avraw@alfred:~$ sudo dmesg | grep -i usb
[sudo] password for avraw:
[ 0.000000] ACPI: SSDT 0x00000000AA8AB258 0007DF (v02 INTEL UsbCTabl 00001000 INTL 20160422)
[ 0.194420] ACPI: bus type USB registered
[ 0.194420] usbcore: registered new interface driver usbfs
[ 0.194420] usbcore: registered new interface driver hub
[ 0.194420] usbcore: registered new device driver usb
[ 1.255377] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 1.255400] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 1.255416] uhci_hcd: USB Universal Host Controller Interface driver
[ 1.255675] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 1
[ 1.257122] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 1.257125] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.257127] usb usb1: Product: xHCI Host Controller
[ 1.257129] usb usb1: Manufacturer: Linux 4.15.0-15-generic xhci-hcd
[ 1.257131] usb usb1: SerialNumber: 0000:00:14.0
[ 1.258145] hub 1-0:1.0: USB hub found
[ 1.268200] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 2
[ 1.268238] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003
[ 1.268240] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.268242] usb usb2: Product: xHCI Host Controller
[ 1.268244] usb usb2: Manufacturer: Linux 4.15.0-15-generic xhci-hcd
[ 1.268245] usb usb2: SerialNumber: 0000:00:14.0
[ 1.269140] hub 2-0:1.0: USB hub found
[ 1.272351] usb: port power management may be unreliable
[ 1.612295] usb 1-5: new high-speed USB device number 2 using xhci_hcd
[ 1.806135] usb 1-5: New USB device found, idVendor=0bda, idProduct=576d
[ 1.806137] usb 1-5: New USB device strings: Mfr=3, Product=1, SerialNumber=2
[ 1.806138] usb 1-5: Product: Integrated_
[ 1.806139] usb 1-5: Manufacturer: CN0WNTY0LOG0079
[ 1.806140] usb 1-5: SerialNumber: 200901010001
[ 1.936080] usb 1-7: new full-speed USB device number 3 using xhci_hcd
[ 2.086227] usb 1-7: New USB device found, idVendor=0cf3, idProduct=e009
[ 2.086247] usb 1-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 2.212269] usb 1-9: new full-speed USB device number 4 using xhci_hcd
[ 2.362729] usb 1-9: New USB device found, idVendor=27c6, idProduct=5301
[ 2.362731] usb 1-9: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2.362732] usb 1-9: Product: Goodix Fingerprint Device
[ 2.362733] usb 1-9: Manufacturer: HTMicroelectronics
[ 2.362734] usb 1-9: SerialNumber: HTK32
[ 2.891058] usbcore: registered new interface driver btusb
[ 2.916499] cdc_acm 1-9:1.0: ttyACM0: USB ACM device
[ 2.916631] usbcore: registered new interface driver cdc_acm
[ 2.916632] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[ 2.916936] Bluetooth: hci0: using rampatch file: qca/rampatch_
[ 2.934372] input: Integrated_
[ 2.934448] usbcore: registered new interface driver uvcvideo
[ 2.934449] USB Video Class driver (1.1.1)
[ 2.945032] Bluetooth: hci0: using NVM file: qca/nvm_
and
avraw@alfred:~$ ls -l /dev/ttyAC*
crw-rw---- 1 root dialout 166, 0 Apr 23 09:55 /dev/ttyACM0
Manfred Hampl (m-hampl) said : | #3 |
[ 2.212269] usb 1-9: new full-speed USB device number 4 using xhci_hcd
[ 2.362729] usb 1-9: New USB device found, idVendor=27c6, idProduct=5301
[ 2.362731] usb 1-9: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2.362732] usb 1-9: Product: Goodix Fingerprint Device
[ 2.362733] usb 1-9: Manufacturer: HTMicroelectronics
[ 2.362734] usb 1-9: SerialNumber: HTK32
The device is definitely detected.
The /dev/ttyACM0 device has been created by the driver, and I assume that you can use it to communicate with the fingerprint reader. You now need a program for this.
Hi Manfred,
That's a relief to know. Which program can I use to connect to the reader? Unfortunately I don't have any experience with making unix programs otherwise would have done it myself.
Manfred Hampl (m-hampl) said : | #5 |
For which purpose do you want to use the fingerprint reader?
You have to search for a program that does the task that you want.
There are some programs to use the fingerprint reader for authentication at https:/
Just need to use it for authentication.
Already tried installing the programs listed but none of them detects any fingerprint device.
What are my options ?
Can you help with this problem?
Provide an answer of your own, or ask Anubhav Rawat for more information if necessary.