Vfs495 fingerprint reader linux

Balint Banyasz

I’ve modified the libfprint-validity patch file to add support for the VFS 495 (138a:003f) device and put all the required packages into a single archive.

Download vfs495.tar containing all the required files.

Install proprietary Validity driver

Compile and install libfprint

Compile and install fprint_demo

Enroll a finger

Enroll your right index finger.

If you prefer console, use this command:

Compile and install pam_fprint

Enable fingerprint authentication

Change the first auth line to auth sufficient.

Add a new auth line with the following content:

Overwrite init script

Configure service to run at startup

Test fingerprint authentication

• Restart your computer
• At the greeting screen press enter
• Scan your right index finger
• You should see a Scan right index finger on Validity Sensors message appear
• Press enter

If you’ve screwed something up in common-auth you won’t be able to log in. In that case, follow these steps:

Make corrections to the file, save and reboot.

Links to the used packages/sources:

Share this:

Like this:

56 thoughts on “ Get Validity VFS 495 FingerPrint Reader working on Ubuntu 16.04 ”

$ sudo /etc/init.d/vcsFPServiceDaemon start

/etc/init.d/vcsFPServiceDaemon: 36: /etc/init.d/vcsFPServiceDaemon: rc_reset: not found
Starting vcsFPService Daemonnohup: ignoring input and redirecting stderr to stdout
nohup: failed to run command ‘/sbin/startproc’: No such file or directory
/etc/init.d/vcsFPServiceDaemon: 49: /etc/init.d/vcsFPServiceDaemon: rc_status: not found
/etc/init.d/vcsFPServiceDaemon: 113: /etc/init.d/vcsFPServiceDaemon: rc_exit: not found

and i googled this:
: It’s specific to whatever distribution you’re running. Debian and Ubuntu have /lib/lsb/init-functions; SuSE has /etc/rc.status; none of them are compatible with the others.

can You give any advise?

Have you tried using the original vcsFPServiceDaemon from the rpm package (i.e. skipping the overwrite init script step)? According to HP the package is for SuSE Linux SLED 11.

I’m new to linux. I’m using it for just 2weeks so right now I don’t understand what You are saying about. could You give me the instructions what to do?

Can you show us how to do it on 18.04 Lts. Getting this to work on 18.04 is a common issue to most users. And your post seems to be the only solution to this problem as of now.

Hello! @taras in the beginning of the post there is a link to http://blog.pasqualefiorillo.it/post/hp-probook-4540s-validity-sensors-driver-su-linux-mintdebian/ – use script for /etc/init.d/vcsFPServiceDaemon and you’ll be able to start the service.

I have another problem – when I run fprint_demo and click Enroll, I scan my finger and nothing happens. After a while in the console appears:
fp:error [capture] VFS module failed to initialize
fp:error [fpi_imgdev_capture] capture failed with error -1
and a window appears to rescan my finger again. Any ideas?

Hello ! Unfortunately, to this day the link is dead. Any idea to where I could find that script ?

Thank you, sir!
Works like a charm in Debian Jessie x64 on HP Elitebook 840 G2 🙂

When I start fprint_demo i get an error

fp:error [dev_init] VFS module failed to wait for service
fp:error [fp_dev_open] device initialisation failed, driver=Validity

I had the same problem because I received an error after running the “sudo /etc/init.d/vcsFPServiceDaemon start” command and I didn’t notice. If you’re getting an error there too, try copying the vcsFPServiceDaemon file from vfs495.tar to /etc/init.d/ (deleting or replacing the file that already exists in that directory) and then running the start daemon command again. You should get:

[ ok ] Starting vcsFPServiceDaemon (via systemctl): vcsFPServiceDaemon.service.

Then try starting fprint_demo again.

thank you this solved also for me

Thanks, I will update the post to include links to the used packages/sources.

fiddling between them I ended up setting it right.
linking libssl didn’t work so I installed instead libssl from there:
http://security.ubuntu.com/ubuntu/pool/universe/o/openssl098/libssl0.9.8_0.9.8o-7ubuntu3.2_amd64.deb

Thank you very much for this step-by-step guide. It works on my HP ZBook 15 G2 which uses this fingerprint reader (Kubuntu 15.10 64-bits).

I would like to know whether it is possible to have both password and fingerprint authentication as an option. Editing /etc/pam.d/common-auth as you suggested, I can no longer log in with my regular UNIX password. The problem I have is that every time I lock my screen I can no longer log back in (somehow the fingerprint authentication doesn’t seem to work at that point). I would appreciate any suggestion. Thanks!

You should add pam_fprint as the second option (see the picture). That way the primary authentication method would be the default pam_unix and pam_fprint would only be activated as a fallback mode. That’s why I’ve written that you have to press enter in the password box first – that’s the standard unix authentication.

Thank you very much for this step-by-step guide. It works on my HP 8560w which uses this fingerprint reader (ubuntu 14.04 64-bits).

Thank you very much for this step-by-step guide. It works on my HP 8560w which uses this fingerprint reader (Kubuntu 14.04 LTS 64-bits).

Hi. Thanks for this tutorial. I got it half-working and I can’t find what’s wrong.

Everything built fine, but fprint_demo couldn’t find my sensor. I then used –enable-example-build on libfprint, and the example worked perfectly, so the lib is working for sure. Yet even with a completely clean build, fprint_demo won’t find my sensor. Any idea ?

First, remove any previous installation of libfprint:
sudo apt-get remove –purge libfprint libfprint0 libfprint-dev

Then recompile libfprint and install it again.

This worked for me when I had the same issue.

This should prevent Ubuntu (apt) from updating the custom built packages:
sudo apt-mark hold libfprint
sudo apt-mark hold fprint-demo

Hello!
Thanks for this excellent tutorial. I’m having a bit of trouble running this command:
sudo dpkg -i libfprint_0.0.6-1_amd64.deb

Which results in this error:
dpkg: error processing archive libfprint_0.0.6-1_amd64.deb (–install):
trying to overwrite ‘/usr/lib/libfprint.so.0.0.0’, which is also in package libfprint0 1:0.6.0-git20151216-1-0ppa1

wily2
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)

What am I doing wrong?

I think you have a conflicting package already installed? Try

sudo apt-get remove libfprint0

sudo dpkg -i libfprint_0.0.6-1_amd64.deb

That worked, thanks!

Hi, I tried to install the reader following your instructions, but I get an error right from the start after executing the alien command:
Can you help? Thanks!

Is this only for first login or will this work with sudo commands on consoles as well .

Yes, it works in console as well.

Thanks for this. It worked for me on an HP ProBook 430 G3, with Ubuntu 16.04 beta 2

Thanks for the info about 16.04. I’m using a ProBook 430 G2, these are really nice notebooks 🙂

bro i am also using g2 but it doesn’t works for me.
please reply me your email, facebook id bro so that i can contact you .

Can you write a new post for fedora ? I am having problem with libusb while ./configure
I have already libusb installed on my system.

Thank you! It works great.
However, DO NOT RUN fprint_demo with sudo as instructed.
Also, little detail, you can run alien with fakeroot instead of sudo.

On Ubuntu 16.04 (HP Zbook 15u), despite carefully following your procedure,
sudo ln /usr/lib/x86_64-linux-gnu/libssl.so /usr/lib/libssl.so.0.9.8
resulted in:
ln: failed to access ‘/usr/lib/x86_64-linux-gnu/libssl.so’: No such file or directory
I guess I missed something?
Thanks for that anyway!

Try this:
sudo apt-get install libssl1.0.0 libssl-dev

It is not working when i lock the screen and try to login again.It works fine when doing a reboot

Hi , thanks for the tutorial, i tried following it but got stuck with the initializing the driver, now terminal doesn’t work gives the following when i try to remove previously installed packages.

sh: 1: cannot create /tmp/vcsSemKey_ServiceId: Permission denied
sh: 1: cannot create /tmp/vcsSemKey_ServiceId: Permission denied
sh: 1: cannot create /tmp/vcsSemKey_ServiceId: Permission denied
sh: 1: cannot create /tmp/vcsSemKey_ServiceId: Permission denied
sh: 1: cannot create /tmp/vcsSemKey_ServiceId: Permission denied
sh: 1: cannot create /tmp/vcsSemKey_ServiceId: Permission denied
sh: 1: cannot create /tmp/vcsSemKey_ServiceId: Permission denied
sh: 1: cannot create /tmp/vcsSemKey_ServiceId: Permission denied

fp:error [dev_init] VFS module failed to wait for service
fp:error [fp_dev_open] device initialisation failed, driver=Validity

any help woul be apreciated.

I’m trying to get the Validity Swipe Fingerprint Sensor (USB ID 138a:0050) on my wife’s Fujitsu Lifebook T935 working on Fedora 24. I’m subscribed to Bug ID 1191926 (https://bugzilla.redhat.com/show_bug.cgi?id=1191926).
With your procedure I no longer get error “list_devices failed: No devices available” with fprintd-enroll. (I did have to add my USB ID to libfprint-validity.patch.) However I can now no longer start fprintd:
Aug 24 00:23:50 ivanka_fujitsu_wireless.wasielewski systemd[1]: Starting Fingerprint Authentication Daemon…
Aug 24 00:23:50 ivanka_fujitsu_wireless.wasielewski fprintd[9179]: /usr/libexec/fprintd: symbol lookup error: /usr/libexec/fprintd: undefined symbol: fp_async_dev_close
Aug 24 00:23:50 ivanka_fujitsu_wireless.wasielewski systemd[1]: fprintd.service: Main process exited, code=exited, status=127/n/a
Aug 24 00:23:50 ivanka_fujitsu_wireless.wasielewski systemd[1]: Failed to start Fingerprint Authentication Daemon.
Aug 24 00:23:50 ivanka_fujitsu_wireless.wasielewski systemd[1]: fprintd.service: Unit entered failed state.

If I remove the libfprint RPM it also takes fprintd as well, and if I then reinstall fprintd from RPM it reinstalls libfprint and so overwrites the custom build package. Any ideas how I can fix the apparent issue with “undefined symbol: fp_async_dev_close”? Hopefully this will get fixed in mainline Fedora packages soon…

Источник

Linux Mint Forums

Welcome to the Linux Mint forums!

[SOLVED] Driver support for Validity Fingerprint sensor device (138a:003f) VFS495

[SOLVED] Driver support for Validity Fingerprint sensor device (138a:003f) VFS495

Post by sobuj53 » Fri Oct 04, 2019 1:10 am

line as linnux mint doesn’t use makepkg. I would really appreciate if anyone could make this guide mint compatible or give any light on how to make .rpm or .deb package after build has been completed.

I should also mention that, finger print gui didn’t work. This method also didn’t work

Re: Driver support for Validity Fingerprint sensor device (138a:003f) VFS495

Post by secureIT » Mon Oct 07, 2019 3:00 pm

look at this thread and translate from a german forum outside of LM-forums, may be youll try a solution suggested, which the thread-owner had not tried in past :

Re: Driver support for Validity Fingerprint sensor device (138a:003f) VFS495

Post by HAWR » Mon Oct 07, 2019 3:31 pm

I’m sorry, but have a look at the following website und you can see the following hopeless message:

Kernel Drivers
A driver for the device is not found in any Linux kernel versions according to the LKDDb.

Third-party Drivers
A driver for the device is not found in known additional packages.

And look at the long list of «failed», too. Only for the last three probes (page 3) it is detected with the usbfs driver.

Re: Driver support for Validity Fingerprint sensor device (138a:003f) VFS495

Post by thx-1138 » Mon Oct 07, 2019 7:29 pm

ninja -v install will place the files on said destdir. from there,
you can then first examine said files, and manually cp the files to the appropriate locations in the system.
ninja install will blindly install the files on the system no questions asked, not really recommended.
Reason i would insist on examining what’s built / where it’s gonna get installed,
is because i see various arch-isms / slackware-isms, eg. /usr/lib64/ instead of /usr/lib/x86_64-linux-gnu/,
the build system also assumes /opt/validity-sensor/usr/lib64. ie. locations that quite likely need to adjusted here or there.
As the whole thing appears to be quite a bit of a hack, I’d strongly suggest experimenting in a VM thereby.
Building a .deb file out of the files in DESTDIR goes quite a lot further.

Re: Driver support for Validity Fingerprint sensor device (138a:003f) VFS495

Post by sobuj53 » Tue Oct 08, 2019 1:19 am

make a restart and voala! it works just the way I wanted

It also has fallback so, on unsuccessful attempts, it will ask for password as well.

Re: Driver support for Validity Fingerprint sensor device (138a:003f) VFS495

Post by kuehhe1 » Wed Oct 09, 2019 2:42 pm

Hello @secureIT,
Thanks for the info via LMU-PN to this thread.

I have never lost sight of the problem and still open in the browser tab. Somehow we were already very close, I wrote the time the HP-Softpaq-Manager u.a. Linux / Ubuntu / Redhat as BS systems but unfortunately did not list packages under win10 (softpacks).
Anyway, here are the basic requirements with LM19.2 and the FP-Reader (138a: 003f) VFS495 the same. With a lot of rest, I’ll do it again with the @ sobuj53 driverlink to attempt.

I can not write PN yet, i guess I have too few posts.

Ist hier Englisch Pflicht?

Re: Driver support for Validity Fingerprint sensor device (138a:003f) VFS495

Post by Moem » Wed Oct 09, 2019 3:11 pm

If your issue is solved, kindly indicate that by editing the first post in the topic, and adding [SOLVED] to the title. Thanks!

Re: [SOLVED] Driver support for Validity Fingerprint sensor device (138a:003f) VFS495

Post by kuehhe1 » Mon Oct 14, 2019 1:43 am

Re: [SOLVED] Driver support for Validity Fingerprint sensor device (138a:003f) VFS495

Post by kuehhe1 » Thu Oct 17, 2019 1:52 am

Hello @ sobuj53,
I use LM19.2Cin. on an «HP ProBook 470 G5 with the FP-Reader VFS495 (138a: 003f)» and had some time ago unsuccessful attempts, you can read this in my german thread: https://www.linuxmintusers.de/index.php?topic=52186.msg in witch i following these two instructions:
1. https://github.com/PetreBoboc/vfs495/bl . u_18.04.md
2. https://askubuntu.com/questions/385372/ . 475#924475
Afterwards the FP-Reader was either not recognized or I was able to create FingerPrints but the FP-Reader did not login activated.

Since they would like to link in their «Tutorial» viewtopic.php?p=1697707#p1697707 on the same instructions would like to start a new attempt around the FP-Reader for the purpose Login in lightdm to use. But unfortunately, they do not exactly describe what step they followed the «PetreBoboc» guide and from where they came in the guide: https://askubuntu.com/questions/385372/ . 475#924475 continue.

Two more questions:

• Instructions 1. requires in step 5. the command: sudo apt-mark hold fprint-demo, did you do this step as well?

• You write that you must push the button «Change User» before to log in, have you set up multiple users?

Best Regards
kuehhe1

Re: [SOLVED] Driver support for Validity Fingerprint sensor device (138a:003f) VFS495

Post by sobuj53 » Thu Oct 17, 2019 2:56 am

in your terminal does it match with the below image?

If so then congrats, you have a working Finger print driver now! And for the finger print login, you have to set up your /etc/pam.d/common-auth properly, so that finger print takes the first lead. To do that run

in terminal and edit that file like this.. Once again Take caution before doing so. Setting up your SU password is very important and useful as well. Rather than deleting any line from common-auth file just place a «#» before that line so that if anything goes wrong you’ll know what amendments to make.

Coming to your questions,

Not exactly. It just transfers me to a window where I can swipe my finger.

My recommendation is to start fresh means if you’ve tried other method earlier please remove all of those settings and installed file from your PC this will ensure proper functioning of your driver, also don’t forget to take Timeshift backup before your try anything.

Re: [SOLVED] Driver support for Validity Fingerprint sensor device (138a:003f) VFS495

Post by kuehhe1 » Thu Oct 17, 2019 12:35 pm

Hello and thank you for your feedback.

Yes, the picture was displayed to me exactly, Device Status: Ready for use

But I could only read four (4) fingers, with the little finger the program went on strike.

With the four fingers I finished fprint-demo and restarted the System, but I could not log in to the lightdm login-window because after a return or input of ani character, the FP-Reader did not open.

Thank you for pointing out the risk, but the risk of changing the /etc/pam.d/common-auth is known to me as well (looks here) as commenting out a line with a rhombus «#».

One more question regarding the /etc/pam.d/common-auth, in their linked common-auth file the last three parts look different than in my not yet edited (original LM19.2) common-auth. Did you remove rows in the section of the «Additional» block?
This is what my original /etc/pam.d/common-auth looks like, my system is not encrypted:

Excuse me, I have read your 5th post in this thread several times, but unfortunately I still am not quite clear from where they switch in the instructions 1 to 2 guide. Or just use PetreBobic’s Guide 1, using her linked HP driver.

My questions may to appear strange, but I would like to try again on a properly installed LM19.2 Cin. Since previous attempts under LM19 Cin. ended up negatively.

Best regards and thank you for your patience
kuehhe1

Источник