ID 138a:003d Validity Sensors, Inc.

Bug #1101647 reported by Mario F. Rodríguez R.
314
This bug affects 61 people
Affects Status Importance Assigned to Milestone
libfprint (Ubuntu)
Undecided
Unassigned

Bug Description

The libfprint package does not seem to recognize the VFS491 Validity Sensor

OS: Ubuntu 12.04 LTS 64 bits
Kernel: 3.7.1-030701-generic
Hardware: HP Probook 4540s
lsusb output:
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 003 Device 002: ID 04f3:0103 Elan Microelectronics Corp.
Bus 003 Device 003: ID 04d9:0499 Holtek Semiconductor, Inc. Optical Mouse
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 138a:003d Validity Sensors, Inc.
Bus 001 Device 004: ID 0461:4dfe Primax Electronics, Ltd
Bus 002 Device 003: ID 0cf3:311d Atheros Communications, Inc.

When running both the Fingerprint GUI and the fprint project demo, the device is not recognized.

Will the VFS491 be included as a supported device anywhere in the future?

Thank you.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in libfprint (Ubuntu):
status: New → Confirmed
Revision history for this message
Gert van Dijk (gertvdijk) wrote :
Download full text (3.1 KiB)

I have the same "138a:003d Validity Sensors, Inc." on my HP Elitebook 8570w. Running Linux 3.7.4 still does not support this device it seems. Here's some more hardware information.

'usb-devices' output:

T: Bus=01 Lev=02 Prnt=02 Port=00 Cnt=01 Dev#= 3 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=ff(vend.) Sub=11 Prot=ff MxPS= 8 #Cfgs= 1
P: Vendor=138a ProdID=003d Rev=01.04
S: SerialNumber=(censored)
C: #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=100mA
I: If#= 0 Alt= 0 #EPs= 4 Cls=ff(vend.) Sub=00 Prot=00 Driver=(none)

relevant 'lsusb -v' output:

Bus 001 Device 003: ID 138a:003d Validity Sensors, Inc.
Device Descriptor:
  bLength 18
  bDescriptorType 1
  bcdUSB 1.10
  bDeviceClass 255 Vendor Specific Class
  bDeviceSubClass 17
  bDeviceProtocol 255
  bMaxPacketSize0 8
  idVendor 0x138a Validity Sensors, Inc.
  idProduct 0x003d
  bcdDevice 1.04
  iManufacturer 0
  iProduct 0
  iSerial 1
  bNumConfigurations 1
  Configuration Descriptor:
    bLength 9
    bDescriptorType 2
    wTotalLength 46
    bNumInterfaces 1
    bConfigurationValue 1
    iConfiguration 0
    bmAttributes 0xa0
      (Bus Powered)
      Remote Wakeup
    MaxPower 100mA
    Interface Descriptor:
      bLength 9
      bDescriptorType 4
      bInterfaceNumber 0
      bAlternateSetting 0
      bNumEndpoints 4
      bInterfaceClass 255 Vendor Specific Class
      bInterfaceSubClass 0
      bInterfaceProtocol 0
      iInterface 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x01 EP 1 OUT
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0040 1x 64 bytes
        bInterval 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x81 EP 1 IN
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0040 1x 64 bytes
        bInterval 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x82 EP 2 IN
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0040 1x 64 bytes
        bInterval 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x83 EP 3 IN
        bmAttributes 3
          Transfer Type Interrupt
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0008 1x 8 bytes
        bInterval ...

Read more...

Revision history for this message
Pål F. Kristiansen (paalfe) wrote :

I have the same problem!
I have added the FPrint and Fingerprint GUI repositories and installed as described on https://launchpad.net/~fingerprint.

 OS: Ubuntu 13.04 beta x86_64
 Kernel: 3.8.0-15-generic
 Hardware: HP EliteBook 8470w

 lsusb output:
 Bus 001 Device 003: ID 138a:003d Validity Sensors, Inc.

When running both the Fingerprint GUI and the fprint project demo, the device is not recognized.

I found a driver for RHEL6.2-x86_64 and SLED11-SP2-GM-x86_64 on the HP Driver Disks, they can be downloaded from HP.com.

I found newer versions of the driver (including i586) for sle11sp2 on http://www.validityinc.com/uploads/hp/bnb/2012/sle11sp2/

They are rpm packages, I used alien on them to convert them do deb, but the did not work.

Revision history for this message
Cristiano Casella (cristiano-casella) wrote :

HP EliteBook Folio 9470m
Same Sensor, same problem:

user@host:~$ lsusb
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 138a:003d Validity Sensors, Inc.
Bus 001 Device 004: ID 05c8:034b Cheng Uei Precision Industry Co., Ltd (Foxlink)
Bus 001 Device 005: ID 03f0:3d1d Hewlett-Packard

Revision history for this message
Haggan (hagberg-jonas) wrote :

I have HP 2570p Same sensor and same problem.

Bus 001 Device 003: ID 138a:003d Validity Sensors, Inc.

Revision history for this message
Jerry Bezencon (valtam) wrote :

Not working here either, would love for this to be updated.

OS: Ubuntu 12.04 LTS 32 bit
Kernel: 3.2.0-40-generic-pae
Hardware: HP Probook 4540s

No devices found with either fprint or Fingerprint GUI.

lsusb output:

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 003 Device 002: ID 046d:c051 Logitech, Inc. G3 (MX518) Optical Mouse
Bus 001 Device 003: ID 138a:003d Validity Sensors, Inc.
Bus 001 Device 004: ID 046d:0a1f Logitech, Inc.
Bus 001 Device 005: ID 1bcf:2c2a Sunplus Innovation Technology Inc.
Bus 002 Device 003: ID 8087:07da Intel Corp.

Revision history for this message
Mario F. Rodríguez R. (mferrodriguez) wrote :

Anyone from the development or maintenance teams know if the issue will be addressed?

Thank you.

Revision history for this message
SoftExpert (marian.popescu) wrote :

Hello,

On my EliteBook 8770w I have the 138a:003d Validity Sensors.
It is not recognized either - tested with fprintd 0.4.1 and with libfprint0 0.5.0.
How many of us need to say "me too" so that this issue gets enough attention?

Thank you for your help!

Revision history for this message
Pali (pali) wrote :

@SoftExpert: I think that ubuntu devs ignoring all these bugs. All reports going to /dev/null. And if by mistake some ubuntu dev read this he would write only "do not care" or "WONTFIX"... For example took at bug #951736. There is patch for it, fixed in upstream but ubuntu devs do not care about it... So really do not expect that somebody will look at this fprint bug and try to fix it.

Revision history for this message
Jerry Bezencon (valtam) wrote :

@Pali, I don't think it helps to speak about the devs like that. I for one am grateful for the time and effort they put into Ubuntu. You can't make them notice something or work harder. Just be patient and I'm sure we'll get driver support for this chip when its ready.

Revision history for this message
windfix (paul-mckimmy) wrote :

I was so hopeful that everything on my HP Elitebook would work... only this fingerprint reader :(

Revision history for this message
Muhammad Sajid (sajidctn) wrote :

I have the same "138a:003d Validity Sensors, Inc." on my HP Elitebook 8570p. Running Linux

Revision history for this message
Holger (holger-jakobs) wrote :

Still same problem on HP Probook 4540s. What a pity!

Revision history for this message
Lev Lamberov (l-lamberov) wrote :

Also have the same problem on HP Pavilion dv6-6030er.

I've created petition on change.org, requesting opensource drivers for Validity Sensors fingerprint scanners: http://www.change.org/de/Petitionen/validity-sensors-inc-opensource-drivers-for-validity-sensors-fingerprint-scanner

Please, consider to sign it.

Revision history for this message
Leonid Malashev (lm1024) wrote :

Still same problem on HP Probook 6570b.

$ lsusb
Bus 001 Device 003: ID 138a:003d Validity Sensors, Inc.

Revision history for this message
Brendan Abolivier (jomtelt) wrote :

Exactly the same with my Probook 4540s.

Revision history for this message
C Filorux (breakfast) wrote :

I attempted to get a USB trace by installing the Digital Persona / HP fingerprint software on a windows installation in a virtual machine -- that didn't go well. The installer says it can only be installed on certain types of hardware, which the virtual machine is not. Anybody thinking of this approach, don't - nothing but bare metal will do for this fine hardware and software.

Revision history for this message
hassan musadaq (hassan-musadaq-91) wrote :

Hi
I bought HP folio 9470m ultrabook laptop and unfortunately it has the same sensor of fingerprint.

ID 138a:003d Validity Sensors, Inc.

when it will be fixed :(

summary: - VFS491 Validity Sensor on HP Probook 4540s
+ ID 138a:003d Validity Sensors, Inc.
Revision history for this message
Stratos (stratism) wrote :

Hi,

I have the ProBook 6570b with the same Sensor: ID 138a:003d Validity Sensors, Inc. and running on Ubuntu 13.10 but the problem is still there.

Any updates?

Thanks.

Revision history for this message
Denys (frasinich) wrote :
Download full text (3.5 KiB)

So, there is way to set it up with propriethal drive... only for 64bit systems.

We need driver:
h20565.www2.hp.com/portal/site/hpsc/template.PAGE/public/psi/swdHome?javax.portlet.begCacheTok=com.vignette.cachetoken&javax.portlet.endCacheTok=com.vignette.cachetoken&javax.portlet.prp_bd9b6997fbc7fc515f4cf4626f5c8d01=wsrp-navigationalState%3DswEnvOID%253D2020%257CswLang%253D%257Caction%253DlistDriver&javax.portlet.tpst=bd9b6997fbc7fc515f4cf4626f5c8d01&sp4ts.oid=5229459&ac.admitted=1397379248506.876444892.492883150#Driver%20-%20Scanner

SLED libfprint source:
http://suse.mes.edu.cu/SLES_11_SP2/CD2/suse/src/libfprint-0.0.6-18.20.1.src.rpm

fprint_demo:
http://sourceforge.net/projects/fprint/files/fprint_demo/v0.4/

pam module:
http://sourceforge.net/projects/fprint/files/pam_fprint/v0.2/

First, we need to convert with alien rpm driver package to deb and install it.
After that we need to make some symlinks to start vcsFPServiceDaemon.
Here is my (i`m debian sid user):

sudo ln /usr/lib/x86_64-linux-gnu/libssl.so.1.0.0 /usr/lib/libssl.so.0.9.8
sudo ln /usr/lib/libcryptopp.so.9 /usr/lib/libcrypto.so.0.9.8

Also we need to edit init script. Somthing like that:

#!/bin/sh
### BEGIN INIT INFO
# Provides: Validity Fingerprint Service Daemon
# Required-Start: $remote_fs $syslog
# Required-Stop: $remote_fs $syslog
# Default-Start: 2 3 5
# Default-Stop: 0 6
# Short-Description: Validity Fingerprint Service Daemon
# Description: Start vcsFPService to provide Validity FP Service
### END INIT INFO
#
# Note on runlevels:
# 0 - halt/poweroff 6 - reboot
# 1 - single user 2 - multiuser without network exported
# 3 - multiuser w/ network (text mode) 5 - multiuser w/ network and X11 (xdm)
#

. /lib/lsb/init-functions

vcsFPService_BIN=/usr/bin/vcsFPService
test -x $vcsFPService_BIN || { echo "$vcsFPServiceDaemon is not installed";
 if [ "$1" = "stop" ]; then exit 0;
 else exit 5; fi; }

case "$1" in
    start)
 echo -n "Starting vcsFPService Daemon \n"
 start-stop-daemon --start --background --quiet --exec "$vcsFPService_BIN" > /dev/null 2 >&1

 ;;
    stop)
 echo -n "Stopping vcsFPService Daemon \n"

 #/sbin/killall -TERM $vcsFPService_BIN
 start-stop-daemon --stop --quiet --quiet --oknodo --retry=0/1/KILL/5 --exec "$vcsFPService_BIN" > /dev/null 2 >&1

 ;;
    status)
 echo "Checking for vcsFPService Daemon \n"

 if pidof -o %PPID $vcsFPService_BIN> /dev/null; then
  echo "client is running. \n"
  exit 0
 else
  echo "client is not running. \n"
  exit 1
 fi
 ;;
    *)
 echo "Usage: $0 {start|stop|status}"
 exit 1
 ;;
esac

exit 0

So, we had vcsFPServiceDaemon working and starting, when system booting.
lets do other packages. First of all, delete yuor system packages

And unpack sles sources and appaly validity patch
patch -p1 < <libfprint-validity.patch location>

after that you nid
./configure --prefix=/usr
make
sudo checkinstall -install=no make install

instal your package if evrything go fine. Also, you can make examples, witch comes with libfprint sources
 and try yor sensor (WARNING! vcsFPServiceDaemon must be started)

After that yuo need to compile fprint_demo and pam module, make packages and inst...

Read more...

Revision history for this message
Mauro (mauromol) wrote :

I own a HP ProBook 450 G1 and I have some similar Validity sensor which is not recognized by libfprint:

Bus 003 Device 002: ID 138a:003f Validity Sensors, Inc.

T: Bus=03 Lev=01 Prnt=01 Port=04 Cnt=02 Dev#= 2 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=ff(vend.) Sub=12 Prot=ff MxPS= 8 #Cfgs= 1
P: Vendor=138a ProdID=003f Rev=01.04
S: SerialNumber=00b0c0ebbd92
C: #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=100mA
I: If#= 0 Alt= 0 #EPs= 4 Cls=ff(vend.) Sub=00 Prot=00 Driver=(none)

Bus 003 Device 002: ID 138a:003f Validity Sensors, Inc.
Device Descriptor:
  bLength 18
  bDescriptorType 1
  bcdUSB 1.10
  bDeviceClass 255 Vendor Specific Class
  bDeviceSubClass 18
  bDeviceProtocol 255
  bMaxPacketSize0 8
  idVendor 0x138a Validity Sensors, Inc.
  idProduct 0x003f
  bcdDevice 1.04
  iManufacturer 0
  iProduct 0
  iSerial 1 00b0c0ebbd92
  bNumConfigurations 1
  Configuration Descriptor:
    bLength 9
    bDescriptorType 2
    wTotalLength 46
    bNumInterfaces 1
    bConfigurationValue 1
    iConfiguration 0
    bmAttributes 0xa0
      (Bus Powered)
      Remote Wakeup
    MaxPower 100mA
    Interface Descriptor:
      bLength 9
      bDescriptorType 4
      bInterfaceNumber 0
      bAlternateSetting 0
      bNumEndpoints 4
      bInterfaceClass 255 Vendor Specific Class
      bInterfaceSubClass 0
      bInterfaceProtocol 0
      iInterface 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x01 EP 1 OUT
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0040 1x 64 bytes
        bInterval 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x81 EP 1 IN
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0040 1x 64 bytes
        bInterval 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x82 EP 2 IN
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0040 1x 64 bytes
        bInterval 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x83 EP 3 IN
        bmAttributes 3
          Transfer Type Interrupt
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0008 1x 8 bytes
        bInterval 4
Device Status: 0x0000
  (Bus Powered)

Revision history for this message
Paweł Wojdyga (trzyowce) wrote :

i follow Denys (frasinich) wrote on 2014-04-13 procedure with some modification ( i do not have to link
sudo ln /usr/lib/x86_64-linux-gnu/libssl.so.1.0.0 /usr/lib/libssl.so.0.9.8
sudo ln /usr/lib/libcryptopp.so.9 /usr/lib/libcrypto.so.0.9.8

just install dev libary
)

and now it work fine with
ubuntu 14.04
HP 6470b and sensor 138a:003d

Revision history for this message
LE BIDEAU (elbc) wrote :

Not sure to understand, I'm running Ubuntu 14.04 on a HP 450 G1 laptop with 138a:003f validity sensors, is it possible to have clear steps on how to install the correct driver ? thank you

Revision history for this message
LE BIDEAU (elbc) wrote :

Nobody anoyed by this issue anymore ?

Revision history for this message
jurgen (jurgen-hofmann) wrote :

Yes, I still have this issue. Well still... I just bought a new Lenovo W540 with this fingerprintreader.
I thought that It should have been a piece of cake.

138a:0017 Validity Sensors, Inc.

I have no idea how to continue because the symlinks suggested by Denys (frasinich) (wrote on 2014-04-13) do not excist on my system.
Also the init file, where can I find this file?

I there really no easier way to do this?

Jurgen

Revision history for this message
Jerry Bezencon (valtam) wrote :

People who don't have the 138a:003d sensor need to stop posting in this thread.

Revision history for this message
gregory bahde (nystal-deactivatedaccount) wrote :

Hello there, I have one but thought I tried posting about it in the dev, It doesn't seem like someone is working on it, so I will.

frasinich, can you send me the proprietary drivers you got please so thzt i can work on it as they were remvoed it seems.

regards,

greg bahde

Revision history for this message
Nathaniel "Gnate" Sigrist (sigrist-nathaniel) wrote :

gregory bahde,

I can build off of what Denys (frasinich) has done with my own updates and source code. You can find everything on my GitHub `libfprint` page here, https://github.com/Gnate/libfprint/tree/master/libfprint/drivers/validity .

The problem is that it requires the install of a library, `libvfsFprintWrapper.so`, so it is NOT a complete solution.

Revision history for this message
Ahmad Amr (aamr) wrote :

Almost 3 years now!!

Revision history for this message
littlelion (the-littlelion) wrote :

Still an issue ... on a HP EliteBook 2760p (Convertilbe)

The links provided in #20 are partially gone, so the workaround isn't available any more.

... and Yes, it is the VFS491 (138a:003d).

Revision history for this message
Nick (kodz) wrote :

Yes I have the same issue! Would appreciate any updates!

Revision history for this message
Eugene (solofeed) wrote :

I have the same problem. Please help us.

Revision history for this message
Alexander Notae (mrzer0) wrote :

Still a Problem...
Ive done search after search and finally found this one dedicated to the sensor i have

HP EliteBook 8570w
Bus 001 Device 003: ID 138a:003d Validity Sensors, Inc. VFS491

=-=-=-=-=-=-=-=
I tried a couple things so far... but i didnt keep the web-links

-1 add fprint repository
sudo add-apt-repository ppa:fingerprint/fprint
sudo apt-get install libpam-fprintd
##Err## fprintd-enroll [user] : No device found

-2 add fingerprint gui
sudo add-apt-repository ppa:fingerprint/fingerprint-gui
apt-get update
sudo apt-get install libbsapi policykit-1-fingerprint-gui fingerprint-gui
##Err## No Device

-3 compile it myself
[download]
tar -xzf rayl-vfs101driver-f00e93a.tar.gz
cd rayl-vfs101driver-f00e93a
make
sudo make install
##Err## no rule to make target 'install'. stop.

=-=-=-=-=-=-=-=

Any new info would be great.

I would prefer if it worked, but not essential

My last output
$ lsusb -s 001:003 -v

Bus 001 Device 003: ID 138a:003d Validity Sensors, Inc. VFS491
Couldn't open device, some information will be missing
info
info
info

Revision history for this message
Koczka David (dkoczka) wrote :

Still having the problem on Ubuntu 16.04 LTS

Bus 001 Device 003: ID 138a:003d Validity Sensors, Inc. VFS491

Would be nice if someone can help.

Revision history for this message
Kelvin Kyalo (voke) wrote :

I also have the same problem. Ubuntu please do something. Make us digital for the respect we give you.
I never new Ubuntu to lack solutions for this long. We can contribute for the project if that hastens.

Revision history for this message
Kelvin Kyalo (voke) wrote :

I have validity sensor 138a:003d, not working, any solution?

Revision history for this message
Jishnu (ezioauditore97) wrote :

Its 2017 and still no solution to this?

Has someone found a way to install Validity Sensors VFS491....?

Revision history for this message
tothsoft@gmail.com (tothsoft) wrote :

I found only this internet, but maybe nobody dont know, what doing with this: https://www.onlinedisassembler.com/odaweb/iUA9cq9s

Revision history for this message
Joseph Tyler Schuster (six6six) wrote :

Hate to reiterate what has already been said... a hundred times.... but, I have this same issue also.

Revision history for this message
Paul (mondbaer) wrote :

The bug also affects me. I found a solution featuring an automatic install script, but libpam-fprintd is quite buggy, at least for me.

https://github.com/PetreBoboc/vfs495_ubuntu

It does also work with my VFS 471 and possibly with the VFS 491.

Would it be possible to link/integrate fprint to/into fingerprint-gui? The authentication itself seems to work quite reliably, it's the PAM-module that is causing problems.

Revision history for this message
Dmitry (drud) wrote :

2018 and it's still an issue.

Bus 001 Device 003: ID 138a:003d Validity Sensors, Inc. VFS491

It doesn't work on my Ubuntu 16.04. fingerprint-gui doesn't help either.

Revision history for this message
Ma'mur Rezeki (erzqy) wrote :

I'm HP 8470p user with Validity vfs491 fp. Until now, it's still won't work.

Revision history for this message
Jakub Štajner (kubik256) wrote :

2019 Ubuntu 18.04 x64 still an issue :(

Revision history for this message
Fasis Assam (fsas) wrote :

mid 2019, HP 6475b, LinuxMint 18.3
138a:003d Validity Sensors, Inc. is still not operational.

Revision history for this message
Dmitriy Rabotyagov (noonedeadpunk) wrote :

Agree, nothing changed untill now

Revision history for this message
Michal Plichta (mplichta) wrote :

Probably never will, get over it...

Revision history for this message
ergouyeg mouad (kaboohd) wrote :

2020 a new decade.
Cannot get over it as long as VFS491 is still being manufactured finding a fix will still be relevant.

Revision history for this message
Gwyn Dh'oine (mikson-kaczmarek) wrote :

Still didn't have good news, did you?
There is some archaic driver for Suse form HP, maybe it can help?
https://ftp.hp.com/pub/softpaq/sp53501-54000/sp53655.tar

Revision history for this message
Michal Plichta (mplichta) wrote :

Doubt it, it ancient history 2.6.32.12 Kernel
ftp://ftp.hp.com/pub/softpaq/sp53501-54000/sp53655.html

Revision history for this message
ahmed kay (ahmedkay059) wrote :

same i have an hp laptop with the same problem ,checked it's 138a:003d device:VFS491

Revision history for this message
Marco Trevisan (Treviño) (3v1n0) wrote :

Drivers requests are upstream issues and as such should be redirected to the official wiki:

 - https://gitlab.freedesktop.org/libfprint/wiki/-/wikis/Unsupported-Devices

As per this, I'm closing all the requests, I please you to update that wiki page if needed.

Changed in libfprint (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers