[138a:0005] [138a:0008] Fingerprint Validity reader devices VFS301 and VFS300 not recognized.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fingerprint GUI |
Invalid
|
Undecided
|
Unassigned | ||
libfprint |
Fix Released
|
Medium
|
|||
office |
New
|
Undecided
|
Unassigned | ||
libfprint (Ubuntu) |
Fix Released
|
Wishlist
|
Unassigned |
Bug Description
Hi,
this bugs is concerning the Validity fingerprint reader VFS301. With the command lsusb is listed as: Bus 001 Device 004: ID 138a:0005 DigitalPersona, Inc. This isn't a DigitalPersona fingerprint reader, its "Validity" but they use digitalpersona software.
It affects in my case the model HP Touchsmart tm2-2105. On the Bug #285089 there is a patch for the 138a:0001 VFS101 but unfortunately it didn't work on the VFS301. I am using Ubuntu 10.10 and libfprint-0.3.0.
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-image-
Regression: No
Reproducible: Yes
ProcVersionSign
Uname: Linux 2.6.35-28-generic x86_64
NonfreeKernelMo
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: amd64
ArecordDevices:
**** List of CAPTURE Hardware Devices ****
card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xc4500000 irq 47'
Mixer name : 'IDT 92HD81B1X5'
Components : 'HDA:111d7605,
Controls : 14
Simple ctrls : 9
Card1.Amixer.info:
Card hw:1 'Generic'/'HD-Audio Generic at 0xc4420000 irq 48'
Mixer name : 'ATI R6xx HDMI'
Components : 'HDA:1002aa01,
Controls : 4
Simple ctrls : 1
Card1.Amixer.
Simple mixer control 'IEC958',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
Date: Mon Mar 28 16:18:41 2011
EcryptfsInUse: Yes
HibernationDevice: RESUME=
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
MachineType: Hewlett-Packard HP TouchSmart tm2 Notebook PC
ProcCmdLine: BOOT_IMAGE=
ProcEnviron:
LANG=en_NZ.utf8
SHELL=/bin/bash
RelatedPackageV
SourcePackage: linux
dmi.bios.date: 10/28/2010
dmi.bios.vendor: Insyde
dmi.bios.version: F.23
dmi.board.
dmi.board.name: 1486
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 83.1F
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.
dmi.modalias: dmi:bvnInsyde:
dmi.product.name: HP TouchSmart tm2 Notebook PC
dmi.product.
dmi.sys.vendor: Hewlett-Packard
carlosv (cvedovatti) wrote : | #1 |
- AcpiTables.txt Edit (403.4 KiB, text/plain; charset="utf-8")
- AlsaDevices.txt Edit (586 bytes, text/plain; charset="utf-8")
- AplayDevices.txt Edit (274 bytes, text/plain; charset="utf-8")
- BootDmesg.txt Edit (59.3 KiB, text/plain; charset="utf-8")
- Card0.Amixer.values.txt Edit (1.8 KiB, text/plain; charset="utf-8")
- Card0.Codecs.codec.0.txt Edit (8.5 KiB, text/plain; charset="utf-8")
- Card1.Codecs.codec.0.txt Edit (235 bytes, text/plain; charset="utf-8")
- CurrentDmesg.txt Edit (16.1 KiB, text/plain; charset="utf-8")
- Dependencies.txt Edit (1.9 KiB, text/plain; charset="utf-8")
- IwConfig.txt Edit (280 bytes, text/plain; charset="utf-8")
- Lspci.txt Edit (13.0 KiB, text/plain; charset="utf-8")
- Lsusb.txt Edit (467 bytes, text/plain; charset="utf-8")
- PciMultimedia.txt Edit (815 bytes, text/plain; charset="utf-8")
- ProcCpuinfo.txt Edit (3.2 KiB, text/plain; charset="utf-8")
- ProcInterrupts.txt Edit (2.1 KiB, text/plain; charset="utf-8")
- ProcModules.txt Edit (4.5 KiB, text/plain; charset="utf-8")
- RfKill.txt Edit (115 bytes, text/plain; charset="utf-8")
- UdevDb.txt Edit (127.8 KiB, text/plain; charset="utf-8")
- UdevLog.txt Edit (289.6 KiB, text/plain; charset="utf-8")
- WifiSyslog.txt Edit (1.3 MiB, text/plain; charset="utf-8")
carlosv (cvedovatti) wrote : | #2 |
Paolo Melchiorre (paulox) wrote : | #3 |
Confirmed on Dell Vostro 3500, device ID 138a:0008 with Ubuntu 10.10 32bit
I tried Fingerprint 1.0 but it not recognize my device.
I attach log from command:
$ sudo lsusb -vs 001:004
Bus 001 Device 004: ID 138a:0008 Validity Sensors, Inc. VFS300 Fingeprint Reader
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 255 Vendor Specific Class
bDeviceSubClass 16
bDeviceProtocol 255
bMaxPacketSize0 8
idVendor 0x138a Validity Sensors, Inc.
idProduct 0x0008 VFS300 Fingeprint Reader
bcdDevice c.90
iManufacturer 0
iProduct 0
iSerial 1 0020e0492286
bNumConfigura
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 39
bNumInterfaces 1
bConfigurat
iConfiguration 0
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescript
bInterfac
bAlternat
bNumEndpoints 3
bInterfac
bInterfac
bInterfac
iInterface 0
Endpoint Descriptor:
bLength 7
Transfer Type Bulk
Synch Type None
Usage Type Data
bInterval 0
Endpoint Descriptor:
bLength 7
Transfer Type Bulk
Synch Type None
Usage Type Data
bInterval 0
Endpoint Descriptor:
bLength 7
Transfer Type Bulk
Synch Type None
Usage Type Data
bInterval 0
Device Status: 0x0000
(Bus Powered)
summary: |
- [138A:0001] fingerprint Validity VFS301 reader not recognized + [138A:0005] fingerprint Validity VFS301 reader not recognized |
summary: |
- [138A:0005] fingerprint Validity VFS301 reader not recognized + [138a:0005] fingerprint Validity VFS301 reader not recognized |
Oier Mees (oier) wrote : Re: [138a:0005] fingerprint Validity VFS301 reader not recognized | #4 |
Confirmed on dell vostro 3500, is Validity Sensors, Inc. VFS300 Fingeprint Reader
Is the VFS300 on the dell vostro and the VFS301 originally reported the same?
carlosv (cvedovatti) wrote : | #5 |
Hi there,
It is a bit confusing. It is not really clear if a solution or a patch for a Fingerprint reader from Validity would work in another one. The patch for VFS101, up to now it didn't work in another Validity fingerprint reader. So it is hard to say if there would be in future a driver for the VFS301, that it would work on the VFS300. But it seems that the Dell Vostro 3500 has the VFS300. On the other bug 138a:0001 somebody declared that the Vostro 3500 had a VFS301. I think it is were the confusion comes. Try the patch for the VFS101, if it doesn't work join the forum.
Changed in libfprint (Ubuntu): | |
status: | New → Confirmed |
Oier Mees (oier) wrote : Re: [Bug 744310] Re: [138a:0005] fingerprint Validity VFS301 reader not recognized | #6 |
The patch didn't work for me.
2011/4/6 carlosv <email address hidden>
> Hi there,
> It is a bit confusing. It is not really clear if a solution or a patch for
> a Fingerprint reader from Validity would work in another one. The patch for
> VFS101, up to now it didn't work in another Validity fingerprint reader. So
> it is hard to say if there would be in future a driver for the VFS301, that
> it would work on the VFS300. But it seems that the Dell Vostro 3500 has the
> VFS300. On the other bug 138a:0001 somebody declared that the Vostro 3500
> had a VFS301. I think it is were the confusion comes. Try the patch for the
> VFS101, if it doesn't work join the forum.
>
> ** Changed in: libfprint (Ubuntu)
> Status: New => Confirmed
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https:/
>
> Title:
> [138a:0005] fingerprint Validity VFS301 reader not recognized
>
> Status in “libfprint” package in Ubuntu:
> Confirmed
>
> Bug description:
> Hi,
> this bugs is concerning the Validity fingerprint reader VFS301. With the
> command lsusb is listed as: Bus 001 Device 004: ID 138a:0005 DigitalPersona,
> Inc. This isn't a DigitalPersona fingerprint reader, its "Validity" but they
> use digitalpersona software.
> It affects in my case the model HP Touchsmart tm2-2105. On the Bug #285089
> there is a patch for the 138a:0001 VFS101 but unfortunately it didn't work
> on the VFS301. I am using Ubuntu 10.10 and libfprint-0.3.0.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 10.10
> Package: linux-image-
> Regression: No
> Reproducible: Yes
> ProcVersionSign
> Uname: Linux 2.6.35-28-generic x86_64
> NonfreeKernelMo
> AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
> Architecture: amd64
> ArecordDevices:
> **** List of CAPTURE Hardware Devices ****
> card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
> Subdevices: 1/1
> Subdevice #0: subdevice #0
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: carlos 2175 F.... pulseaudio
> CRDA: Error: [Errno 2] No such file or directory
> Card0.Amixer.info:
> Card hw:0 'Intel'/'HDA Intel at 0xc4500000 irq 47'
> Mixer name : 'IDT 92HD81B1X5'
> Components : 'HDA:111d7605,
> Controls : 14
> Simple ctrls : 9
> Card1.Amixer.info:
> Card hw:1 'Generic'/'HD-Audio Generic at 0xc4420000 irq 48'
> Mixer name : 'ATI R6xx HDMI'
> Components : 'HDA:1002aa01,
> Controls : 4
> Simple ctrls : 1
> Card1.Amixer.
> Simple mixer control 'IEC958',0
> Capabilities: pswitch pswitch-joined penum
> Playback channels: Mono
> Mono: Playback [on]
> Date: Mon Mar 28 16:18:41 2011
> EcryptfsInUse: Yes
> HibernationDevice: RESUME=
> InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64
> (20101007)
> MachineType: Hewlett-Packard HP TouchSmart tm2 Notebook PC
> ProcCmdLine: BOOT_IMAGE=
> r...
JasonStokes (j32493) wrote : Re: [138a:0005] fingerprint Validity VFS301 reader not recognized | #7 |
same on HP Pavillion dv6-3025dx
Paolo Melchiorre (paulox) wrote : | #8 |
Someone have tried to use the patch submitted for Bug #285089 and replace the id 138a:0001 (VFS101) with the id 138a:0008 (VFS300) ?
I think it can work !
carlosv (cvedovatti) wrote : | #9 |
I tried to change the id 138a:0001 (VFS101) to 138a:0008 (VFS301). It just get recognised by the fprint_demo, but when you tried to enrol my fingerprints, it just doesn't read it at all. You should try if it works on the VFS300 and let us know.
I got an Email from the support of Validity Inc. regarding this bug (missing driver) told me that change the id in the patch may work. But with VFS301, it didn't
carlosv (cvedovatti) wrote : | #10 |
sorry I wanted to say: change the id 138a:0001 (VFS101) to 138a:0005 (VFS301)!!! not 138a:0008. Sorry my mistake
Nick Smith (ndaman) wrote : | #11 |
I just built with the patch, I only found one line where I modified 0001 to 0005, is there anything else I need to do? It didn't work, but I've heard people say that sudo make install put things in the wrong directories, how do I place them in the proper ones? Thanks!
carlosv (cvedovatti) wrote : | #12 |
Hi! The fprint dev are working on the driver it basically seems that the patch for the VFS101 (138a:001) just works on the VFS101 and VFS201. On the debug file when you try the driver on the VFS301 it gives errors that we don't know jet what could it be. The driver (or patch) for the VFS101 doesn't work, it was different protocol, register, or who know what else. Even though, I got two email from Validity Inc. insisting that it may work, but maybe it needs some modifications to make it work on the VFS301 that we don't know yet. Let's hope that fprint developers will create soon a driver or that maybe Validity Inc. decides to release a driver for its products.
carlosv (cvedovatti) wrote : | #13 |
Hi!. I just got another email from Validity Inc. Here is what I got:
>> SLED 11 SP1 is available this year for VFS451 & VFS471 on certain HP
notebooks.
>>
>> We're working on our own Linux driver for SLED, Ubuntu & Fedora and
we plan to make it available by April next year.
>>
>> It will support VFS301, 5011, 5111 and 5131 in addition to VFS451,
471 & 491.
>>
So let's see. It really seems that is a truthful Email. On the other
hand, Validity announced last year a driver for VFS101 on December 2010
that was never released.
In freedesktop.org Bugzilla #37574, carlosv (cvedovatti) wrote : | #75 |
Hi,
this bugs is concerning the Validity fingerprint reader VFS301. With the command lsusb is listed as: Bus 001 Device 004: ID 138a:0005 DigitalPersona, Inc. This isn't a DigitalPersona fingerprint reader, its "Validity" but they use digitalpersona software.
It affects in my case the model HP Touchsmart tm2.
The driver for the VFS101 [138a:0001] doesn't work on this device.
In freedesktop.org Bugzilla #37574, Bastien Nocera (hadess-deactivatedaccount) wrote : | #76 |
*** Bug 37578 has been marked as a duplicate of this bug. ***
carlosv (cvedovatti) wrote : | #14 |
Bug added to the libfprint traking
In freedesktop.org Bugzilla #37574, Lacombar-u (lacombar-u) wrote : | #77 |
As 37578 has been marked as a duplicate of this one, let's comment here.
The VFS300 [138a:0008] does not work either with the current VFS101 driver. This reader is shipped with the ASUSTEK laptops.
In freedesktop.org Bugzilla #37574, Andree (andree) wrote : | #78 |
I've started developing a driver at https:/
If someone test this and it works, let me know (through email/project site/this bugtracker).
Andrej Krutak (andree182) wrote : | #15 |
I've started developing a driver at https:/
carlosv (cvedovatti) wrote : | #16 |
Good news. Thanks Andrej! something that we could start working on and hopefully will become driver for the device.
Lopan (lopan-eti) wrote : Re: [Bug 744310] Re: [138a:0005] fingerprint Validity VFS301 reader not recognized | #17 |
Work very fine with VSF300! (Bus 001 Device 004: ID 138a:0008 Validity
Sensors, Inc. VFS300 Fingeprint Reader)
just change the proto.c line (135)
from:
dev->devh = libusb_
to:
dev->devh = libusb_
Congratulations!
2011/11/6 Andrej Krutak <email address hidden>
> I've started developing a driver at https:/
> . I am able to get some fingerprint from it - but the code still needs
> some love and integration to libfprint is yet to be done (after it works
> correctly from console).
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (787876).
> https:/
>
> Title:
> [138a:0005] fingerprint Validity VFS301 reader not recognized
>
> Status in Fingerprint GUI:
> New
> Status in “libfprint” package in Ubuntu:
> Confirmed
>
> Bug description:
> Hi,
> this bugs is concerning the Validity fingerprint reader VFS301. With the
> command lsusb is listed as: Bus 001 Device 004: ID 138a:0005
> DigitalPersona, Inc. This isn't a DigitalPersona fingerprint reader, its
> "Validity" but they use digitalpersona software.
> It affects in my case the model HP Touchsmart tm2-2105. On the Bug
> #285089 there is a patch for the 138a:0001 VFS101 but unfortunately it
> didn't work on the VFS301. I am using Ubuntu 10.10 and libfprint-0.3.0.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 10.10
> Package: linux-image-
> Regression: No
> Reproducible: Yes
> ProcVersionSign
> Uname: Linux 2.6.35-28-generic x86_64
> NonfreeKernelMo
> AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
> Architecture: amd64
> ArecordDevices:
> **** List of CAPTURE Hardware Devices ****
> card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
> Subdevices: 1/1
> Subdevice #0: subdevice #0
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: carlos 2175 F.... pulseaudio
> CRDA: Error: [Errno 2] No such file or directory
> Card0.Amixer.info:
> Card hw:0 'Intel'/'HDA Intel at 0xc4500000 irq 47'
> Mixer name : 'IDT 92HD81B1X5'
> Components : 'HDA:111d7605,
> Controls : 14
> Simple ctrls : 9
> Card1.Amixer.info:
> Card hw:1 'Generic'/'HD-Audio Generic at 0xc4420000 irq 48'
> Mixer name : 'ATI R6xx HDMI'
> Components : 'HDA:1002aa01,
> Controls : 4
> Simple ctrls : 1
> Card1.Amixer.
> Simple mixer control 'IEC958',0
> Capabilities: pswitch pswitch-joined penum
> Playback channels: Mono
> Mono: Playback [on]
> Date: Mon Mar 28 16:18:41 2011
> EcryptfsInUse: Yes
> HibernationDevice: RESUME=
> InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64
> (20101007)
> MachineType: Hewlett-Packard HP TouchSmart tm2 Notebook PC
> ProcCmdLine: BOOT_IMAGE=
> root=UUID=
...
Elizeu Soares (esosaja) wrote : Re: [138a:0005] fingerprint Validity VFS301 reader not recognized | #18 |
ID 138a:0005 Validity Sensors, Inc. VFS301 Fingerprint Reader
"No devices found!" (finguerprint GUI).
My notebook is HP Pavilion dm4-1075br.
Thanks.
carlosv (cvedovatti) wrote : | #19 |
@Lopan
Could please tell us the instructions how did installed and tried the driver? I would like to give it a try. Thanks
Lopan (arlindo) wrote : | #20 |
@carlosv
Just change the proto.c line (135)
from:
dev->devh = libusb_
to:
dev->devh = libusb_
Compile (command make) and run the proto (./proto). All steps like a root.
carlosv (cvedovatti) wrote : | #21 |
@Lopan,
thank you for your answer. I muss say that I cannot compile it. (just for the record I am not a programmer). So when I compile it i get:
collect2: ld returned 1 exit status
make: *** [cli] Error 1
I have installed the packages libusb1-0, make and g++. It supposed to compile it without problem. Do you have any suggestion about this?
Thanks
Lopan (lopan-eti) wrote : Re: [Bug 744310] Re: [138a:0005] fingerprint Validity VFS301 reader not recognized | #22 |
@carlosv,
Please, send the last 100 lines before the compile error.
2011/12/15 carlosv <email address hidden>
> @Lopan,
>
> thank you for your answer. I muss say that I cannot compile it. (just for
> the record I am not a programmer). So when I compile it i get:
> collect2: ld returned 1 exit status
> make: *** [cli] Error 1
> I have installed the packages libusb1-0, make and g++. It supposed to
> compile it without problem. Do you have any suggestion about this?
> Thanks
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (787876).
> https:/
>
> Title:
> [138a:0005] fingerprint Validity VFS301 reader not recognized
>
> Status in Fingerprint GUI:
> New
> Status in “libfprint” package in Ubuntu:
> Confirmed
>
> Bug description:
> Hi,
> this bugs is concerning the Validity fingerprint reader VFS301. With the
> command lsusb is listed as: Bus 001 Device 004: ID 138a:0005
> DigitalPersona, Inc. This isn't a DigitalPersona fingerprint reader, its
> "Validity" but they use digitalpersona software.
> It affects in my case the model HP Touchsmart tm2-2105. On the Bug
> #285089 there is a patch for the 138a:0001 VFS101 but unfortunately it
> didn't work on the VFS301. I am using Ubuntu 10.10 and libfprint-0.3.0.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 10.10
> Package: linux-image-
> Regression: No
> Reproducible: Yes
> ProcVersionSign
> Uname: Linux 2.6.35-28-generic x86_64
> NonfreeKernelMo
> AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
> Architecture: amd64
> ArecordDevices:
> **** List of CAPTURE Hardware Devices ****
> card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
> Subdevices: 1/1
> Subdevice #0: subdevice #0
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: carlos 2175 F.... pulseaudio
> CRDA: Error: [Errno 2] No such file or directory
> Card0.Amixer.info:
> Card hw:0 'Intel'/'HDA Intel at 0xc4500000 irq 47'
> Mixer name : 'IDT 92HD81B1X5'
> Components : 'HDA:111d7605,
> Controls : 14
> Simple ctrls : 9
> Card1.Amixer.info:
> Card hw:1 'Generic'/'HD-Audio Generic at 0xc4420000 irq 48'
> Mixer name : 'ATI R6xx HDMI'
> Components : 'HDA:1002aa01,
> Controls : 4
> Simple ctrls : 1
> Card1.Amixer.
> Simple mixer control 'IEC958',0
> Capabilities: pswitch pswitch-joined penum
> Playback channels: Mono
> Mono: Playback [on]
> Date: Mon Mar 28 16:18:41 2011
> EcryptfsInUse: Yes
> HibernationDevice: RESUME=
> InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64
> (20101007)
> MachineType: Hewlett-Packard HP TouchSmart tm2 Notebook PC
> ProcCmdLine: BOOT_IMAGE=
> root=UUID=
> ProcEnviron:
> LANG=en_NZ.utf8
> SHELL=/bin/bash
> RelatedPackageV
> SourcePackage: linux
> dmi.bios.da...
carlosv (cvedovatti) wrote : Re: [138a:0005] fingerprint Validity VFS301 reader not recognized | #23 |
@Lopan,
thank you again for your fast answer. So here it is:
carlos@
[sudo] password for carlos:
gcc -ggdb `pkg-config --cflags libusb-1.0` `pkg-config --libs libusb-1.0` -o cli proto.c cli.c
/tmp/cchqESW9.o: In function `usb_init':
/home/carlos/
/home/carlos/
/home/carlos/
/home/carlos/
/home/carlos/
/home/carlos/
/home/carlos/
/tmp/cchqESW9.o: In function `usb_deinit':
/home/carlos/
/home/carlos/
/home/carlos/
/home/carlos/
/tmp/cchqESW9.o: In function `usb_recv':
/home/carlos/
/tmp/cchqESW9.o: In function `usb_send':
/home/carlos/
collect2: ld returned 1 exit status
make: *** [cli] Error 1
Sérgio Faria (sergio91pt) wrote : Re: [Bug 744310] Re: [138a:0005] fingerprint Validity VFS301 reader not recognized | #24 |
carlosv, I still didn't have time to install this but you probably
also need libusb-1.0-0-dev
2011/12/15 carlosv <email address hidden>:
> @Lopan,
>
> thank you again for your fast answer. So here it is:
>
> carlos@
> [sudo] password for carlos:
> gcc -ggdb `pkg-config --cflags libusb-1.0` `pkg-config --libs libusb-1.0` -o cli proto.c cli.c
> /tmp/cchqESW9.o: In function `usb_init':
> /home/carlos/
> /home/carlos/
> /home/carlos/
> /home/carlos/
> /home/carlos/
> /home/carlos/
> /home/carlos/
> /tmp/cchqESW9.o: In function `usb_deinit':
> /home/carlos/
> /home/carlos/
> /home/carlos/
> /home/carlos/
> /tmp/cchqESW9.o: In function `usb_recv':
> /home/carlos/
> /tmp/cchqESW9.o: In function `usb_send':
> /home/carlos/
> collect2: ld returned 1 exit status
> make: *** [cli] Error 1
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> [138a:0005] fingerprint Validity VFS301 reader not recognized
>
> Status in Fingerprint GUI:
> New
> Status in “libfprint” package in Ubuntu:
> Confirmed
>
> Bug description:
> Hi,
> this bugs is concerning the Validity fingerprint reader VFS301. With the command lsusb is listed as: Bus 001 Device 004: ID 138a:0005 DigitalPersona, Inc. This isn't a DigitalPersona fingerprint reader, its "Validity" but they use digitalpersona software.
> It affects in my case the model HP Touchsmart tm2-2105. On the Bug #285089 there is a patch for the 138a:0001 VFS101 but unfortunately it didn't work on the VFS301. I am using Ubuntu 10.10 and libfprint-0.3.0.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 10.10
> Package: linux-image-
> Regression: No
> Reproducible: Yes
> ProcVersionSign
> Uname: Linux 2.6.35-28-generic x86_64
> NonfreeKernelMo
> AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
> Architecture: amd64
> ArecordDevices:
> **** List of CAPTURE Hardware Devices ****
> card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
> Subdevices: 1/1
> Subdevice #0: subdevice #0
> AudioDevicesInU
carlosv (cvedovatti) wrote : Re: [138a:0005] fingerprint Validity VFS301 reader not recognized | #25 |
@Sérgio
Thanks for the tip, but the libusb-1.0-0-dev I have it installed already. Cheers.
Paolo Melchiorre (paulox) wrote : | #26 |
I've the same problem of carlosv.
I've ubuntu 11.10 64bit.
The issue is related to 64bit infrastructure ?
carlosv (cvedovatti) wrote : | #27 |
I have the same Ubuntu 11.10 64bit. Maybe it needs to be developed for 64bit as well.
carlosv (cvedovatti) wrote : | #28 |
Hi there the problem has been just fixed. Andrej is working on it. Thanks.
The driver works! Lets hope soon will be full developed.
Paolo Melchiorre (paulox) wrote : | #29 |
Now, I compile correctly and get image of fingeprint.
I hope we'll have soon a libfprint driver for vfs300/1
Thanks!
Andrej Krutak (andree182) wrote : | #30 |
Good new everyone! :-) The libfprint driver can now be integrated into libfprint and seems to work (see the mentioned web for recent patches etc.) - I was able to compile and use the examples provided with libfprint (and the fingerprints matched when expected).
However it could take while until we clean up the code to a state acceptable by the mainline...
Changed in fingerprint-gui: | |
status: | New → In Progress |
Changed in libfprint (Ubuntu): | |
status: | Confirmed → In Progress |
carlosv (cvedovatti) wrote : | #31 |
Hi Andrej!
IT WORKS!!!! Amazing!
Great job! Thanks for the effort!
I compiled and installed. fprint_demo GUI.
So if anybody wants to give it a shot here is what I did:
I have Ubuntu 11.10 64bit
I have installed fprint_demo from repositories.
Now download fprint: http://
and download the driver: https:/
uncompressed them!
Now from the driver copy all the files:
libfprint/vfs301.c
and all the files on the other folder
cli/vfs301_photo.* (they are 3 files)
So copy all them on the libfprint uncompressed folder v_0_4_0/
Then in a Terminal apply the patch:
$ cd ~/v_0_4_0
$ patch -p1 < ~/Desktop/
$ ./autogen.sh
$ make
$ sudo make install
Restart the Computer
then test it try in a Termal
$ sudo fprint_demo (I assume that you installed from repositories)
Hope to see it in upstream soon!
summary: |
- [138a:0005] fingerprint Validity VFS301 reader not recognized + Fingerprint Validity reader devices [138a:0005] VFS301 and [138a:0008] + VFS300 not recognized. |
Lopan (lopan-eti) wrote : Re: [Bug 744310] Re: [138a:0005] fingerprint Validity VFS301 reader not recognized | #32 |
Yes! Congratulations!
I've implemented authentication with PAM(
http://
/ etc / pam.d / login
auth required pam_securetty.so
auth required pam_env.so
auth sufficient pam_fprint.so
auth sufficient pam_unix.so nullok try_first_pass likeauth
auth required pam_deny.so
See the test:
Login lopan: lopan
Scan right index finger on Validity VFS301
Último login:Qui Jan 5 10:46:26 BRST 2012em :0
lopan@lopan ~ $
Authentication on KDE works well.
/etc/pam.d/kde
auth required pam_env.so
auth sufficient pam_fprint.so
auth sufficient pam_unix.so try_first_pass likeauth nullok
auth required pam_deny.so
att.,
2012/1/5 carlosv <email address hidden>
> Hi Andrej!
>
> IT WORKS!!!! Amazing!
>
> Great job! Thanks for the effort!
>
> I compiled and installed. fprint_demo GUI.
>
> So if anybody wants to give it a shot here is what I did:
>
> I have Ubuntu 11.10 64bit
>
> I have installed fprint_demo from repositories.
>
> Now download fprint:
> http://
> and download the driver:
> https:/
> uncompressed them!
>
> Now from the driver copy all the files:
> libfprint/vfs301.c
> and all the files on the other folder
> cli/vfs301_photo.* (they are 3 files)
>
> So copy all them on the libfprint uncompressed folder
> v_0_4_0/
>
> Then in a Terminal apply the patch:
> $ cd ~/v_0_4_0
> $ patch -p1 < ~/Desktop/
> $ ./autogen.sh
> $ make
> $ sudo make install
>
> Restart the Computer
>
> then test it try in a Termal
> $ sudo fprint_demo (I assume that you installed from repositories)
>
> Hope to see it in upstream soon!
>
> ** Summary changed:
>
> - [138a:0005] fingerprint Validity VFS301 reader not recognized
> + Fingerprint Validity reader devices [138a:0005] VFS301 and [138a:0008]
> VFS300 not recognized.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (787876).
> https:/
>
> Title:
> Fingerprint Validity reader devices [138a:0005] VFS301 and [138a:0008]
> VFS300 not recognized.
>
> Status in Fingerprint GUI:
> In Progress
> Status in “libfprint” package in Ubuntu:
> In Progress
>
> Bug description:
> Hi,
> this bugs is concerning the Validity fingerprint reader VFS301. With the
> command lsusb is listed as: Bus 001 Device 004: ID 138a:0005
> DigitalPersona, Inc. This isn't a DigitalPersona fingerprint reader, its
> "Validity" but they use digitalpersona software.
> It affects in my case the model HP Touchsmart tm2-2105. On the Bug
> #285089 there is a patch for the 138a:0001 VFS101 but unfortunately it
> didn't work on the VFS301. I am using Ubuntu 10.10 and libfprint-0.3.0.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 10.10
> Package: linux-image-
> Regression: No
> Reproducible: Yes
> ProcVersionSign
> Uname: Linux 2.6.35-28-generic x86_64
> NonfreeKernelMo
> AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
> Architectu...
Paolo Melchiorre (paulox) wrote : Re: Fingerprint Validity reader devices [138a:0005] VFS301 and [138a:0008] VFS300 not recognized. | #33 |
- Shell script for patch libfprint with vfs301 Edit (1.4 KiB, text/x-sh)
Hi Andrej and thanks for your work.
I tried last code from vfs301 and libfprint with fprint-demo and it works well.
This is my configuration:
$ lsusb -s 001:004
Bus 001 Device 004: ID 138a:0008 Validity Sensors, Inc. VFS300 Fingerprint Reader
$ uname -a
Linux oz 3.0.0-14-generic #23-Ubuntu SMP Mon Nov 21 20:28:43 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
$ lsb_release -sd
Ubuntu 11.10
I attach a shell script to patch and compile libfprint with vfs301 and test it with fprint-demo and it works for me.
I hope to see soon this patch in the libfprint git master and fprint stable ppa.
triple (triplevic) wrote : | #34 |
Hi!!
I try to install it, but it don't works!
I have copied the files libfprint/vfs301.c cli/vfs301_*.* to
the libfprint directory libfprint/drivers
Then like carlosv, in a Terminal apply the patch:
$ cd ~/v_0_4_0
$ patch -p1 < ~/Desktop/
$ ./autogen.sh
$ make
$ sudo make install
Restart the Computer
and I use:
fingerprint-gui (v 1.02)
or
fprint-demo (v 0.04)
and it doesn't works.
I use Archlinux x86_64 and Bus 002 Device 003: ID 138a:0005 Validity Sensors, Inc. VFS301 Fingerprint Reader
What am I doing wrong?
My computer is HP dv6 3038ss
triple (triplevic) wrote : | #35 |
uname -a
Linux myhost 3.1.9-1-ARCH #1 SMP PREEMPT Fri Jan 13 12:43:42 CET 2012 x86_64 Intel(R) Core(TM) i7 CPU Q 720 @ 1.60GHz GenuineIntel GNU/Linux
carlosv (cvedovatti) wrote : | #36 |
@triple
Hi there!
I think you need to execute the fprint_demo as root user. So in a terminal $ sudo fprint_demo
If it doesnt work try to use the shell script from PaoloX.
If still doesnt work, just tell us a bit more if you get any error on the terminal.
triple (triplevic) wrote : | #37 |
It works!
My problem was that I had installed the fingerprint-gui package (from yaourt) that depends on libfprint, since, when I installed fingerprint-gui, linfprint be also installed.
I installed after fprint_demo from source code.
Then I installed the patch
$ patch -p1 < ~/Desktop/
$ ./autogen.sh
$ make
$ sudo make install
but this did not replace the other libfprint (the lib from yaourt), then, when I execute sudo fprint_demo, it doesn't works. Why make install doesn't replace the other lib?
THE SOLUTION IS:
First install libfprint without driver for ID 138a:0005. (It's to compile fprint_demo)
sudo pacman -S libfprint
Now download fprint_demo (v 0.04) from http://
Now compile fprint_demo
cd ~/fprint_demo-0.4
./configure
make
sudo make install
Now uninstall libfprint
sudo pacman -R libfprint
Now download fprint: http://
and download the driver https:/
uncompressed them.
Now copy the files libfprint/vfs301.c cli/vfs301_*.* to
the libfprint directory libfprint/drivers
Then, apply the patch:
$ cd ~/v_0_4_0
$ patch -p1 < ~/Desktop/
$ ./autogen.sh
$ make
$ sudo make install
Now copy /usr/local/
sudo mv /usr/local/
then execute fprint_demo
sudo fprint_demo
and, IT WORKS!
Is there another way to solve my problem easier? I mean changing the makefile or something.
carlosv (cvedovatti) wrote : | #38 |
Good to know that it worked out. I guess the only problem to solved easier is to wait until it's upstreamed. Andrej is solving a problem that seems to affect to certain device with a segmentation problem. So I guess when it will be solve. It will be upstreamed.
But good to know it works!
triple (triplevic) wrote : | #39 |
Is the problem with fingerprint-GUI? My question is because I installed fingerprint-GUI and doesn't works, it shows me "Segmentation fault" but pam_fprint and fprint_demo work.
fingerprint-GUI shows me this:
(process:7580): Gtk-WARNING **: Locale not supported by C library.
Using the fallback 'C' locale.
fp:debug [fp_init]
fp:debug [register_driver] registered driver upekts
fp:debug [register_driver] registered driver upeke2
fp:debug [register_driver] registered driver aes4000
fp:debug [register_driver] registered driver aes2501
fp:debug [register_driver] registered driver uru4000
fp:debug [register_driver] registered driver vcom5s
fp:debug [register_driver] registered driver upeksonly
fp:debug [register_driver] registered driver aes1610
fp:debug [register_driver] registered driver vfs101
fp:debug [register_driver] registered driver (null)
fp:debug [find_supportin
fp:debug [find_supportin
Segmentation fault
carlosv (cvedovatti) wrote : | #40 |
Ah! that may be the issue I was talking about before. Check: https:/
In freedesktop.org Bugzilla #37574, Bastien Nocera (hadess-deactivatedaccount) wrote : | #79 |
Andrej, any news on this branch and patches?
In freedesktop.org Bugzilla #37574, Bastien Nocera (hadess-deactivatedaccount) wrote : | #80 |
*** Bug 43252 has been marked as a duplicate of this bug. ***
Thoaha rashyd (r4shyd) wrote : | #41 |
i get this error
thoaha@
thoaha@
patching file configure.ac
patching file libfprint/
patching file libfprint/core.c
patching file libfprint/
thoaha@
./autogen.sh: 2: libtoolize: not found
ubuntu 11.10
Bus 001 Device 004: ID 138a:0005 Validity Sensors, Inc. VFS301 Fingerprint Reader
Sunil Mujumdar (radicall) wrote : | #42 |
Getting the same error ./autogen.sh: 2: libtoolize: not found
Ubuntu 11.10 32 bit
Sunil Mujumdar (radicall) wrote : | #43 |
I didn't have necessary packages
sudo apt-get install libtool
sudo apt-get install autotools-dev
sudo apt-get install automake
sudo apt-get install libusb-1.0
sudo apt-get libgtk2.0-dev
sudo apt-get install libnss3-1d-dev
sudo apt-get install libnss3-dev
sudo apt-get install libgtk2.0-dev
sudo apt-get install glib-2.0
did it - there might have been a couple more I missed ( i installed a few others that may have been uncecessary)
I wonder if I had run
sudo apt-get install build-essential
first i some of these might have been included
It does give an error after autogen
"configure: error: XV is required for X11 examples" which I am hoping can be ignored. Moving on with my testing now
Sunil Mujumdar (radicall) wrote : | #44 |
i did need xv to make
sudo apt-get libxv-dev
make
sudo make
sudo make install
rebooted .. no luck
go to cli folder.
make
cli
light blinked orange for a second on the reader
but no real luck
giving up for now
Paolo Melchiorre (paulox) wrote : | #45 |
Please, push this code on freedesktop git.
I want use my fingerprint out-of-the-box with Ubuntu 12.04.
carlosv (cvedovatti) wrote : | #46 |
I guess we have to wait until the bug of Segmentation Fault is solved, to be consider stable driver. Andrej has not give signals since two months. I just hope he won't abandon the project.
Keshwarsingh Nadan (keshwarsingh) wrote : | #47 |
just hope that validity will release their drivers in april 2012!!
Changed in fingerprint-gui: | |
status: | In Progress → Invalid |
Paolo Melchiorre (paulox) wrote : | #48 |
Please remove invalid status, it's wrong.
Changed in fingerprint-gui: | |
status: | Invalid → Confirmed |
carlosv (cvedovatti) wrote : | #49 |
Well, definitely the bug is there. And it fix is in progress. The open-source driver, still there. Unfortunately, Andrej, seems left the project, so I just hope somebody relieve it. On the other hand, Validity Inc. stated that will release a driver on April 2012. I hope they keep the word.
Changed in fingerprint-gui: | |
status: | Confirmed → In Progress |
carlosv (cvedovatti) wrote : | #50 |
I changed back in fingerpint-gui to invalid. I think Whoopie changed as the bug is not in the fingerprint-gui, but on the libfprint.
Changed in fingerprint-gui: | |
status: | In Progress → Invalid |
Ochir (oabushinov) wrote : | #51 |
- deb package for Precise Edit (125.3 KiB, application/x-debian-package)
Added a deb package with Validity for Precise I built myself at my laptop.
To install it, follow instrustions:
1. Add this PPA to your sources:
sudo add-apt-repository ppa:fingerprint
sudo apt-get update
sudo apt-get upgrade
2. Install the software:
sudo apt-get install libfprint0 fprint-demo libpam-fprintd gksu-polkit
And then:
sudo dpkg -i libfprint0_
Then run "Users and Accounts" and make fingeprint for login.
Walter Mourão (walter-mourao) wrote : | #52 |
Thank you very much Ochir!
Works with "138a:0008 Validity Sensors, Inc. VFS300 Fingerprint Reader" too.
carlosv (cvedovatti) wrote : | #53 |
Good news! Ochir thanks for your work.I haven't tried yet. I will give it a shot this weekend and report feedback.
Ochir, just one question: did you solved the problem described on the forum https:/
Thanks again!
Ochir (oabushinov) wrote : | #54 |
Unfortunately, no. However, driver works.
There is another issue still exists
if fingerprint cannot be recognized then message "Swipe your finger again" is shown but second swipe doesn't work and verification timeout occurs.
carlosv (cvedovatti) wrote : | #55 |
Hi! Thanks for the fast reply.
I wanted to ask you if you think the workaround on the last comment of the forum may solve the "Segmentation fault" problem?
Ochir (oabushinov) wrote : | #56 |
This comment
https:/
and last comment solves problem with segmentation fault after launch but after Ctrl-C it appears again.
carlosv (cvedovatti) wrote : | #57 |
Hi! good news! it works fine with VFS301! I tried with the fprint_demo several times. I just had one time crashed on the whole weekend that I have been testing. Maybe related to the segmentation fault. But otherwise it works. I tried to contact the Validity employee regarding the driver that suppose to release last month, no answer. I would assume that there won't be any driver. Anyway, great news. Thanks again Ochir
carlosv (cvedovatti) wrote : | #58 |
Hi there! I am having a problem with the login. I can register my fingerprint to login and works fine if do not log out from the session. Then I tried to lock the screen and unlock it with the fingerprint and works perfect. But then I log out and then I tried to login using the fingerprint and it recognizes my fingerprint but when it logs in the session seem to break and comes back to the lightdm login. I have to log in with the password. Am I the only one that happens or is a bug in Ubuntu 12.04?
Sayantan Das (sayantan13) wrote : | #59 |
hi,
is ithe update for comment #57 available in the fingerprint-gui ppa? or do i have to compile it ?
Ochir (oabushinov) wrote : | #60 |
No, instruction is in comment #51. At least one bug should be solved before merging patch with fingerprint. I hope Andrea (creator of driver) can read this thread.
Sayantan Das (sayantan13) wrote : | #61 |
Thanks ochir, I will try this
Sayantan Das (sayantan13) wrote : | #62 |
- Ubuntu_059.png Edit (44.9 KiB, image/png)
Hi,
This works on Vostro 3300 ( VFS300) fingerprint reader. However, there are two glaring issues
1. The underlying user wallet is not unlocked so, you have to put your password to unlock it after you login.
2. There is a system crash due to fprintd (Screenshot attached)
Sayantan Das (sayantan13) wrote : | #63 |
@carlos:
I have checked, I am able to swipe my fingerprints at lockscreen and also when I logout and login.
It does not break lightdm.
Only problem is I have enter my password to unlock the password keyring after login.
Ochir (oabushinov) wrote : | #64 |
the second bug is the issue of fprintd. The first is the feature of GNOME. Keyring is not locked during login due to security reasons
carlosv (cvedovatti) wrote : | #65 |
Hi guys. I found the reason why it crashes when I try to login using my fingerprints. It is because my home folder is encrypted. I created a user non encrypted and works fine. I encrypted the folder, crashes. Any ideas how to fix that? or do you think it should be consider as new bug?
Ochir (oabushinov) wrote : | #66 |
carlosv,
have you tried to do it without fingerprint?
carlosv (cvedovatti) wrote : | #67 |
yes! password always works encrypted or not encrypted home user folder. Just with fingerprint the login doesnt work. Seems is a new issue (or bug), other people inform about it: http://
Sayantan Das (sayantan13) wrote : | #68 |
@Ochir: is there any 32bit package available for the package you provided in #51?
Ochir (oabushinov) wrote : | #69 |
no, I built only for amd64
Paolo Melchiorre (paulox) wrote : | #70 |
@carlosv I've the same issue with encrypted home user folder.
carlosv (cvedovatti) wrote : | #71 |
Well here is the bug report: Bug #998367 of the encrypted home user.
Coming back to the issue I believe this driver works relatively fine. But Ochir is right, the segmentation fault bug in this driver should be solve before merging to libfprint. Now, I believe that Andrej has abandoned the project, so I guess if anybody has an idea how to solve it, just commented.
carlosv (cvedovatti) wrote : | #72 |
I tried the driver with Fingerprint GUI. The "segmentation fault" crashes the program. We really have to solve this issue.
Shailesh Paranjpe (shailesh-paranjpe) wrote : Re: [Bug 744310] Re: Fingerprint Validity reader devices [138a:0005] VFS301 and [138a:0008] VFS300 not recognized. | #73 |
I tried this on HP Pailion DV6 with 138a:0005 VFS301. It works great.
Thanks for the driver...
On 17 May 2012 21:14, carlosv <email address hidden> wrote:
> I tried the driver with Fingerprint GUI. The "segmentation fault"
> crashes the program. We really have to solve this issue.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> Fingerprint Validity reader devices [138a:0005] VFS301 and [138a:0008]
> VFS300 not recognized.
>
> Status in Fingerprint GUI:
> Invalid
> Status in “libfprint” package in Ubuntu:
> In Progress
>
> Bug description:
> Hi,
> this bugs is concerning the Validity fingerprint reader VFS301. With the
> command lsusb is listed as: Bus 001 Device 004: ID 138a:0005
> DigitalPersona, Inc. This isn't a DigitalPersona fingerprint reader, its
> "Validity" but they use digitalpersona software.
> It affects in my case the model HP Touchsmart tm2-2105. On the Bug
> #285089 there is a patch for the 138a:0001 VFS101 but unfortunately it
> didn't work on the VFS301. I am using Ubuntu 10.10 and libfprint-0.3.0.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 10.10
> Package: linux-image-
> Regression: No
> Reproducible: Yes
> ProcVersionSign
> Uname: Linux 2.6.35-28-generic x86_64
> NonfreeKernelMo
> AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
> Architecture: amd64
> ArecordDevices:
> **** List of CAPTURE Hardware Devices ****
> card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
> Subdevices: 1/1
> Subdevice #0: subdevice #0
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: carlos 2175 F.... pulseaudio
> CRDA: Error: [Errno 2] No such file or directory
> Card0.Amixer.info:
> Card hw:0 'Intel'/'HDA Intel at 0xc4500000 irq 47'
> Mixer name : 'IDT 92HD81B1X5'
> Components : 'HDA:111d7605,
> Controls : 14
> Simple ctrls : 9
> Card1.Amixer.info:
> Card hw:1 'Generic'/'HD-Audio Generic at 0xc4420000 irq 48'
> Mixer name : 'ATI R6xx HDMI'
> Components : 'HDA:1002aa01,
> Controls : 4
> Simple ctrls : 1
> Card1.Amixer.
> Simple mixer control 'IEC958',0
> Capabilities: pswitch pswitch-joined penum
> Playback channels: Mono
> Mono: Playback [on]
> Date: Mon Mar 28 16:18:41 2011
> EcryptfsInUse: Yes
> HibernationDevice: RESUME=
> InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64
> (20101007)
> MachineType: Hewlett-Packard HP TouchSmart tm2 Notebook PC
> ProcCmdLine: BOOT_IMAGE=
> root=UUID=
> ProcEnviron:
> LANG=en_NZ.utf8
> SHELL=/bin/bash
> RelatedPackageV
> SourcePackage: linux
> dmi.bios.date: 10/28/2010
> dmi.bios.vendor: Insyde
> dmi.bios.version: F.23
> dmi.board.
> dmi.board.name: 1486
> dmi.board.vendor: Hewlett-Packa...
Kostas Stam (stamfil) wrote : Re: Fingerprint Validity reader devices [138a:0005] VFS301 and [138a:0008] VFS300 not recognized. | #74 |
Hi all.
Thanks to your help here, I managed to have my HP Pailion DV7 with 138a:0005 VFS301 working on ubuntu 12.04.
Today I wanted to try on an extra partition ubuntu 12.10.
I used the "make.sh" script found above but had no luck untill now.
Did anayone manage to get the driver and fprint_demo work on ubuntu 12.10?
Thanks in advance.
Changed in libfprint (Ubuntu): | |
importance: | Undecided → Wishlist |
summary: |
- Fingerprint Validity reader devices [138a:0005] VFS301 and [138a:0008] + [138a:0005] [138a:0008] Fingerprint Validity reader devices VFS301 and VFS300 not recognized. |
In freedesktop.org Bugzilla #37574, Robert Ancell (robert-ancell) wrote : | #81 |
Created attachment 64254
Add support for Validity VFS301/VFS300
This is Andrej's patch taken from github and applied to libfprint. I can confirm that fprint_demo works with this patch on my laptop.
In freedesktop.org Bugzilla #37574, Gaurav Saxena (grvsaxena419) wrote : | #82 |
hi,
could you tell me which version of libfprint should I apply this patch ?
In freedesktop.org Bugzilla #37574, Robert Ancell (robert-ancell) wrote : | #83 |
(In reply to comment #7)
> hi,
> could you tell me which version of libfprint should I apply this patch ?
This patch should apply to git master.
In freedesktop.org Bugzilla #37574, Gaurav Saxena (grvsaxena419) wrote : | #84 |
Hi,
Thanks , fprint_demo is able to recognize the device but still gives error that it could not open the device.
In freedesktop.org Bugzilla #37574, Robert Ancell (robert-ancell) wrote : | #85 |
BTW I tested with a VFS300 (Dell Vostro). Guarav, do you have the 300 or the 301?
$ lsusb
Bus 001 Device 004: ID 138a:0008 Validity Sensors, Inc. VFS300 Fingerprint Reader
In freedesktop.org Bugzilla #37574, Gaurav Saxena (grvsaxena419) wrote : | #86 |
Hi,
Thanks for your reply. I am using HP Pavillion DM4 with a VFS 301 device. Is there anyway I could make it work on this device?
In freedesktop.org Bugzilla #37574, carlosv (cvedovatti) wrote : | #87 |
(In reply to comment #11)
> Hi,
> Thanks for your reply. I am using HP Pavillion DM4 with a VFS 301 device. Is
> there anyway I could make it work on this device?
Hi
on this forum: https:/
The comment #51 there is a deb package that works in Ubuntu and its more or less stable. Check if it works for your Laptop
In freedesktop.org Bugzilla #37574, Robert Ancell (robert-ancell) wrote : | #88 |
(In reply to comment #11)
> Hi,
> Thanks for your reply. I am using HP Pavillion DM4 with a VFS 301 device. Is
> there anyway I could make it work on this device?
Note I am not the author of this patch. So it may be working for the 300 but not the 301. I don't know what the author tested it with.
In freedesktop.org Bugzilla #37574, Gaurav Saxena (grvsaxena419) wrote : | #89 |
(In reply to comment #12)
> Hi
>
> on this forum: https:/
>
> The comment #51 there is a deb package that works in Ubuntu and its more or
> less stable. Check if it works for your Laptop
Hi, I tried the patch provided on that forum and it worked! Now I am able to get fingerprints. Any ideas on how to use it for authentication? I am using Ubuntu 12.04. I tried using fingerprint-gui but it crashes with segmentation fault. fprint_demo is working.
In freedesktop.org Bugzilla #37574, carlosv (cvedovatti) wrote : | #90 |
(In reply to comment #14)
> (In reply to comment #12)
> > Hi
> >
> > on this forum: https:/
> >
> > The comment #51 there is a deb package that works in Ubuntu and its more or
> > less stable. Check if it works for your Laptop
>
> Hi, I tried the patch provided on that forum and it worked! Now I am able to
> get fingerprints. Any ideas on how to use it for authentication? I am using
> Ubuntu 12.04. I tried using fingerprint-gui but it crashes with segmentation
> fault. fprint_demo is working.
Yes. The problem with fingerprint-gui is a segmentation fault not yet solved. In order to use it, you have to unistall fingerprint-gui.
Since Ubuntu 11.10 the system integrates the fingerprint authentification without using other fingerprint-gui. And that way it works with this driver.
So to login and authenticate you must have Ubuntu 11.10 or 12.04, uninstall fingerprint-gui. Then reboot the system. Then to access the "Ubuntu" fingerprint go to: System setting -> User accounts. In the users account window you will see the option "Fingerprint Login" on every account. Click the button and register your fingerprints. You will be able to login and use authenticate when root privileges are needed.
P.D. The fingerprint login unfortunately doesn't work if the home user folder is encrypted. But that is not a problem of the driver, is a Ubuntu (or linux) bug.
In freedesktop.org Bugzilla #37574, Gaurav Saxena (grvsaxena419) wrote : | #91 |
(In reply to comment #15)
>
> Yes. The problem with fingerprint-gui is a segmentation fault not yet solved.
> In order to use it, you have to unistall fingerprint-gui.
> Since Ubuntu 11.10 the system integrates the fingerprint authentification
> without using other fingerprint-gui. And that way it works with this driver.
>
> So to login and authenticate you must have Ubuntu 11.10 or 12.04, uninstall
> fingerprint-gui. Then reboot the system. Then to access the "Ubuntu"
> fingerprint go to: System setting -> User accounts. In the users account window
> you will see the option "Fingerprint Login" on every account. Click the button
> and register your fingerprints. You will be able to login and use authenticate
> when root privileges are needed.
>
> P.D. The fingerprint login unfortunately doesn't work if the home user folder
> is encrypted. But that is not a problem of the driver, is a Ubuntu (or linux)
> bug.
Hi,
OK. I tried that method ,but I couldn't find any fingerprint login option in that menu. I am using Gnome3 with Ubuntu 12.04. I tried modifying /etc/pam.d/login but its not working. Could you suggest me some method for doing the same.
In freedesktop.org Bugzilla #37574, carlosv (cvedovatti) wrote : | #92 |
Created attachment 64558
Screenshot fingerprint login Ubuntu
In freedesktop.org Bugzilla #37574, carlosv (cvedovatti) wrote : | #93 |
Hi
Unfortunately at the moment there is not other method. To use the fingerprint-gui we must wait until somebody solves the segmentation fault. Now, I really find strange that you do not have this option in the users menu. I tried in Unity and Gnome and both are there. I attached a screen-shot of how you supposed to find it. Make sure you installed the fprint .deb customized from the forum. Hope it helps.
In freedesktop.org Bugzilla #37574, Gaurav Saxena (grvsaxena419) wrote : | #94 |
(In reply to comment #18)
> Hi
> Unfortunately at the moment there is not other method. To use the
> fingerprint-gui we must wait until somebody solves the segmentation fault. Now,
> I really find strange that you do not have this option in the users menu. I
> tried in Unity and Gnome and both are there. I attached a screen-shot of how
> you supposed to find it. Make sure you installed the fprint .deb customized
> from the forum. Hope it helps.
Thank you very much its working now. I did all the steps again and now it works. Thanks a lot for your help. :)
In freedesktop.org Bugzilla #37574, carlosv (cvedovatti) wrote : | #95 |
(In reply to comment #19)
> (In reply to comment #18)
> > Hi
> > Unfortunately at the moment there is not other method. To use the
> > fingerprint-gui we must wait until somebody solves the segmentation fault. Now,
> > I really find strange that you do not have this option in the users menu. I
> > tried in Unity and Gnome and both are there. I attached a screen-shot of how
> > you supposed to find it. Make sure you installed the fprint .deb customized
> > from the forum. Hope it helps.
>
> Thank you very much its working now. I did all the steps again and now it
> works. Thanks a lot for your help. :)
Glad I could help!
In freedesktop.org Bugzilla #37574, Andree (andree) wrote : | #96 |
Created attachment 64946
vfs301 driver (1st public version)
Hi,
I have somewhat updated and improved the driver, should be a little more compatible with the coding style (in terms of internal functionality) of other libfprint drivers. I'm attaching the current version of the patch - please someone integrate it, so that I don't have to keep it on github sync'd .-)
Some notes:
The driver is for the devices 138a:0005 (primarily) and 138a:0008 (some users reported it as working too).
Unfortunately, we didn't decypher the protocol to much detail - so currently it mostly just repeats sequences the original binary driver does (that seems to work fine). That's why the driver doesn't look so pretty as other drivers. Maybe some users will be able to help with that :-)
The device on my notebook contains a LED next to the scanner, but I also didn't yet figure out how to control it - but anyhow, can libfprint use it to provide some feedback, even if we know how to control the LED?
Changed in libfprint: | |
importance: | Unknown → Medium |
status: | Unknown → In Progress |
Andrej Krutak (andree182) wrote : | #97 |
Hi guys. Sorry for not replying, had other priorities and forgot about this bugzilla. I mostly reply on the github page however. But anyhow, as stated above, I tried to make the patches merge-able into upstream, so they should be in in near future... If you guys still experience any driver-related issues, please let me know on github .-)
In freedesktop.org Bugzilla #37574, Kh3095 (kh3095) wrote : | #98 |
Hi, Andrej and Everyone!
I tried your updated patch with 138a:0018 Validity Sensors, Inc. on HP Pavilion dv6-6030er. I tried to change id 0008 to 0018 in sources. fprint-demo finds my device, but cannot open it. If I can help you to make your driver work for 0018, tell my what I should de. Unfortunately, I don't have Windows, so I cannot send you any reverse-engineered stuff.
In freedesktop.org Bugzilla #37574, carlosv (cvedovatti) wrote : | #99 |
(In reply to comment #22)
> Hi, Andrej and Everyone!
>
> I tried your updated patch with 138a:0018 Validity Sensors, Inc. on HP Pavilion
> dv6-6030er. I tried to change id 0008 to 0018 in sources. fprint-demo finds my
> device, but cannot open it. If I can help you to make your driver work for
> 0018, tell my what I should de. Unfortunately, I don't have Windows, so I
> cannot send you any reverse-engineered stuff.
Hi
I believe the Validity Sensors are very different from each other. If it doesn't work after modifying the usb id (as it happened to VFS300), I hardly believe this driver would work on this device. Check this bug https:/
In freedesktop.org Bugzilla #37574, Bastien Nocera (hadess-deactivatedaccount) wrote : | #100 |
Cleaned up a little more, and pushed. Thanks very much for the patch!
commit c3689665dbf3cd2
Author: Andrej Krutak <email address hidden>
Date: Sun Jul 22 21:44:34 2012 +0200
lib: Add VFS300/VFS301 driver
Changed in libfprint: | |
status: | In Progress → Fix Released |
Paolo Melchiorre (paulox) wrote : | #101 |
Can you upgrade ubuntu 12.10 package ? Latest commit on git repository contain VFS300/301 driver.
http://
Thanks
David Fraser (davidf) wrote : | #102 |
Testing this on my Dell Vostro 3700 with a VFS300, and installing the drivers from https:/
* fprint_demo lists the device as a VFS301
* Attempting to enroll fingers does nothing
* the program occasionally segfaults
What am I doing wrong? Versions below... dpkg -l "*fprint*" gksu-polkit
Desired=
| Status=
|/ Err?=(none)
||/ Name Version Architecture Description
+++-===
ii fprint-demo 1:0.4+git200803
ii fprintd 0.4.1-5-g73edad0-3 i386 D-Bus daemon for fingerprint reader access
ii gksu-polkit 0.0.2-2.1ubuntu2 i386 command line utility to run programs as root
ii libfprint0 1:0.5.0-
ii libpam-fprintd:i386 0.4.1-5-g73edad0-3 i386 PAM module for fingerprint authentication trough fprintd
ii xfprint4 4.6.1-3ubuntu1 i386 Printer GUI for Xfce4
Changed in libfprint (Ubuntu): | |
status: | In Progress → Fix Released |
It affects HP Pavillion dv7-4012eg and Dell Vostro 3500 too.