cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
i2000s
HDMI
Posts: 307
Registered: ‎11-13-2010
Location: US
Views: 12,853
Message 51 of 197

Re: Validity Fingerprint Reader Linux

Can anyone suggest what we can do to accelerate this process? Calling, emailing someone, coding or just waiting? I have posted this thread on reddit once before...

-----------------------------------------------------------------------------
TPs own: X31 (2003), X61T, X200T, Tablet 2, P50 (2016); Win XP-10, Ubuntu8.04-16.04.
Aquabon
Ctrl-Alt-Del
Posts: 5
Registered: ‎01-20-2017
Location: FR
Views: 12,691
Message 52 of 197

Re: Validity Fingerprint Reader Linux


@grb19 wrote:

Many people have been trying to get the new fingerprint reader (by Validity / Synaptic) to run under Linux. However it seems, that there simply is no driver around.


..if it can help.

 

Just to say 'Hello Lenovo fan's or not' and also to says that i have no problem with my brand new Thinkpad E560 ev using the Validity Sensors, Inc. VFS5011 Fingerprint Reader ( usb ref : 138a:0011)  running a fresh Ubuntu 17.04 (zesty) . All devices are ok except  the usb 'sensivity'  - some mem storage doesn't lift up the usb device insertion trigger => no disk Smiley Sad

So  fprintd and fingerprint are running perfectly in a console (sudo,su) right now but i expect to manage it under X soon when calling others apps requiring authentication. Actually, i am really close to success except with GUI agents . The fingerprint dialog  box rise up but doen't care about swipes. (screenshot).


To conclude : i can't detect any module loader and as i didn't dig into my kernel config, i bet it's native in Zesty ... try it in live !

 

Good Luck and Happy new year.

 

Aquabon ( or AquaGood for you ^^)

 

edmundlaugasson
Core Memory
Posts: 22
Registered: ‎07-17-2016
Location: EE
Views: 12,550
Message 53 of 197

Re: Validity Fingerprint Reader Linux

No - Ubuntu 17.04 did not recognize nothing! Actually I have 138a:0090 and not 138a:0011.

Installed both fprint (from zesty repo) and fingerprint-gui (from yakkety repo as there is no zesty version yet).

 

Tested Lubuntu 17.04 and Ubuntu 17.04 as of 21th January 2017:

http://cdimage.ubuntu.com/daily-live/current/zesty-desktop-amd64.iso

http://cdimage.ubuntu.com/lubuntu/daily-live/current/zesty-desktop-amd64.iso

 

None of them did not recognize the 138a:0090 fingerprint sensor. Checked both - command line and GUI version. I noticed that zesty used 4.9.0 kernel.

 

If we check at https://launchpad.net/~fingerprint then the 138a:0011 is already listed there before even zesty repo is available. So, the 138a:0011 support is not related with Ubuntu 17.04 Zesty. But as you see, there is still no 138a:0090 support available. The fingerprint repo is here https://launchpad.net/~fingerprint/+archive/ubuntu/fingerprint-gui

 

The same goes for fprint - no 138a:0090 support - https://launchpad.net/~fingerprint/+archive/ubuntu/fprint

 

Another issue is that non-LTS version do not help me as I need more stable version as mission-critical work. Second and even more serious reason - Estonian ID-card software is made usually for LTS-version of Ubuntu. So even there will be working version I have to wait until next Ubuntu 18.04 LTS comes out and also ID-card software for that. There might be versions between available but as you know, non-LTS versions are not considered to use in mission-critical systems.

 

About accelerating the process. I actually called to Lenovo tech support as I described in quite beginning of this thread. I would mention that I have 7 hours time shift with that part of USA as I live in Estonia. It did not help - tech support said that they support only M$ Windows and that's it. Another issue - Validity is not Lenovo - tech support said that I should call or visit Validity.

 

Here is detailed output of my 138a:0090 sensor.

First: lsusb shows:

Bus 001 Device 005: ID 138a:0090 Validity Sensors, Inc.

Here I get that I have first bus (001) and fifth device (005), so for detailed information I need to run:

lsusb -s 001:005 -v

Then I get the following output:

Bus 001 Device 005: ID 138a:0090 Validity Sensors, Inc. 
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass          255 Vendor Specific Class
  bDeviceSubClass        16 
  bDeviceProtocol       255 
  bMaxPacketSize0         8
  idVendor           0x138a Validity Sensors, Inc.
  idProduct          0x0090 
  bcdDevice            1.64
  iManufacturer           0 
  iProduct                0 
  iSerial                 1 ca7aa2bf182c
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           53
    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           5
      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
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x84  EP 4 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0010  1x 16 bytes
        bInterval              10
Device Status:     0x0000
  (Bus Powered)
LONGMAN
Ctrl-Alt-Del
Posts: 11
Registered: ‎11-15-2016
Location: GE
Views: 12,490
Message 54 of 197

Re: Validity Fingerprint Reader Linux

What is a web site of Validity Sensors Inc.? I think we should contact with validity support, after if they wont help, create petition, invite more people, blame Lenovo etc. We should to do something

Treviño
Fanfold Paper
Posts: 18
Registered: ‎08-25-2015
Location: IT
Views: 12,482
Message 55 of 197

Re: Validity Fingerprint Reader Linux

It's just Synaptics now... They've been bought by them. 

edmundlaugasson
Core Memory
Posts: 22
Registered: ‎07-17-2016
Location: EE
Views: 12,468
Message 56 of 197

Re: Validity Fingerprint Reader Linux

All Synaptics contacts are here - http://www.synaptics.com/contact

I have to admit that I even called to EMEA office in Switzerland (no one did not pick up the phone), then to Shanghai office in China - there they told me (after short search who can speak English) that fingerprint production is in U.S.

Then I tried to call U.S. main office in San Jose but only answering machine talked with me. This was ca half year ago, when this thread started. Probably the situation is changed for now. Anyone who is in U.S. could probably more easily reach right people. I guess visiting them and talking physically eye-to-eye would probably good idea whenever possible.

 

I found http://www.linkedin.com/company/validity-sensors-inc. - looks like former Validity Sensors, Inc. is also located at the same place:  2001 Gateway Place Suite 455E San Jose, CA 95110 - probably after acquisition the production is still in same place. The Synaptics main office is at 1251 McKay Dr. San Jose, CA 95131. Looks like there is less than 3 miles distance between these two addresses.

Aquabon
Ctrl-Alt-Del
Posts: 5
Registered: ‎01-20-2017
Location: FR
Views: 12,333
Message 57 of 197

Re: Validity Fingerprint Reader Linux

Thank's for this clear "report".

 

but please; don't be so vincdictive, i must admit that didn't notice that the 0090 device was the main/real topic of this feed. Ggl fool me !

 

Anyway, i still hope that my post will help someone else until topic change.

ps : I wonder if someone try Ndiswrapper solution ?

edmundlaugasson
Core Memory
Posts: 22
Registered: ‎07-17-2016
Location: EE
Views: 12,175
Message 58 of 197

Re: Validity Fingerprint Reader Linux

Somehow I could not post reply - it disappears. My reply is written here - http://pastebin.com/YdEdCiWN

Aquabon
Ctrl-Alt-Del
Posts: 5
Registered: ‎01-20-2017
Location: FR
Views: 12,141
Message 59 of 197

Re: Validity Fingerprint Reader Linux

It's ok sir.

 

Your progress is very interesting.

 

Obvioulsy, wine can't help (same dll missing) but VirtualBox does !

 

Perhaps a tip to retreive drivers stuff' out of exec, did you have a look into temp dir or somewere ? . I'am going to check it out .

 

Done later :

 

I have extracted the msi installer file from lenovo driver (your link). The next step was to unpack the file and isolate the driver files to  feed ndiswrapper. The resulting ZIP is here : https://file.io/EJIMZs

 

The  WudfBioUsbLenovoTPinf7p_x64.D82AE54F_FA41_40F6_9F4C_413BFDA44E5E contains some info check it out!

--------------------

extract

--------------------

 

[Synaptics.NTamd64.6.1]
; TODO: Change the VendorID (VID) and ProductID (PID) to match your device
%WBDIUsbDeviceName%=Biometric_Install_7, USB\VID_138A&PID_0090

[Synaptics.NTamd64.6.2]
; TODO: Change the VendorID (VID) and ProductID (PID) to match your device
%WBDIUsbDeviceName%=Biometric_Install, USB\VID_138A&PID_0090

 

The extracted msi is here : https://file.io/LyiRcs

 

Good luck !

edmundlaugasson
Core Memory
Posts: 22
Registered: ‎07-17-2016
Location: EE
Views: 12,097
Message 60 of 197

Re: Validity Fingerprint Reader Linux

From where that driver were downloaded? In other words - how to find all laptops that use this (138a:0090) fingerprint sensor. Yes - that is great but still do not know what to do with these files in Linux. There are bunch of .dll files and garbage (Zone.Identifier) generated by buggy VirtualBox but it's OK - these can be removed. I guess these zone files can be avoided when to pack inside virtual Windows and then copy already packed file to Linux. Now some kind of wrapper would be appreciated in order to use these .dll files in Linux. Does anybody know such wrapper? It would be also appreciated when such wrapper can be used via PAM, e.g. to use fingerprint sensor to log into system. In addition when such wrapper exist - it would be interesting whether it will survive laptop sleep.

 

Tested: the only one .exe included in that file, did not open using Wine 2.0 RC6 Smiley Sad

Check out current deals!


Shop current deals

Top Kudoed Authors