Re: [fprint] Digital Persona 138a:0005
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. ___ fprint mailing list fprint@reactivated.net http://lists.reactivated.net/mailman/listinfo/fprint
Re: [fprint] Digital Persona 138a:0005
Well, I downloaded version 0.4.0 and the latest fprint-demo. fprint-demo
doesn't see the fingerprint scanner.
However, running the example codes I get this when trying to enroll or
verify-live.
$sudo ./enroll
Found device claimed by Validity VFS101 driver
Opened device. It's now time to enroll your finger.
You will need to successfully scan your finger 3 times to complete the
process.
Scan your finger now.
vfs101:error [async_recv_cb] transfer not completed, status = 6
async:error [fpi_drvcb_enroll_stage_completed] BUG at async.c:161
sync:error [fp_enroll_finger_img] unrecognised return code -5
Enroll failed with error -22
Now it says VFS101, but I left the code alone and added the VFS301 to the
list of supported devices for the driver.
$ diff vfs101.c vfs101.c.new
1542a1543
{ .vendor = 0x138a, .product = 0x0005 },
--
The other examples gave other messages.
$sudo ./img_capture
Found device claimed by Validity VFS101 driver
Opened device. It's now time to scan your finger.
image capture failed, code -95
Verify failed because the was no file to verify.
cpp-test seems to do nothing, but no error.
That's all for tonight (morning). I'll have to dig into the code to see
what the messages mean.
Brian
___
fprint mailing list
fprint@reactivated.net
http://lists.reactivated.net/mailman/listinfo/fprint
Re: [fprint] Digital Persona 138a:0005
Most likely, the protocol is different than vfs101/201. Maybe, it has different registers? maybe takes different values for dev init? who knows? So, just adding the dev ids in vfs101.c won't help. Even though Validity is saying it should work. We'll need to understand the protocol from usb-sniff logs. That's a Windows/DOS application. Sadly, I have wiped Windows from the machine, save for the disaster recovery partition. Has anyone ever run these from WINE? It's a daunting task, to be honest. VFS101 was made possible due to Ray Lehtiniemi's efforts to reverse-engineer the protocol from sniff logs. Do those sniff logs still exist? I can try running usb sniffers in WINE and with that info try to figure out the differences. That is because you _explicitly_ added the devid in the driver - so, while scanning the devices, libfprint sees that vfs101 driver *claims* to support the device that it found using usb ids. So, the statement that it has opened the device without error is completely bogus? I would have thought there was at least some wake up code happening there. I expected the first message that it found a supported device. I did not expect the I have successfully opened the device. message. At least not without a handshake. It's a pointless message then. cpp-test is a simple C++ program that just tries to link to the fprint library - to make sure that we can still call the libfprint functions from C++ code. I suspected as much, just a stub program of a few lines. But, it needs a lot of patience - which, I hope, we'll have ;) Patience is sometimes called a virtue, but I've never waited long enough to find out if it's true. However, I've found stubbornness and unrelenting determination are generally much more effective over mere patience. However, I have a company to run, and after our holiday in Europe, I discover our funds are lower than normal so I have to actually work for a while. The good news is, I own (most of) the company so have no issues concerning any software I might write, and am free to code to any OSS license. I own all the code I write. Brian ___ fprint mailing list fprint@reactivated.net http://lists.reactivated.net/mailman/listinfo/fprint
Re: [fprint] Digital Persona 138a:0005
Well it seems Mepis' default kernel is broken. So I'm going to have to
rebuild the kernel with some features they shut off. I have a Phenom core
(running 32 bit, for a single application required for business, grrr).
Would it be best for me to build to a 686 (the default) processor family?
In case I produce anything useful.
Brian
On Fri, April 29, 2011 5:32 am, Kunal Gangakhedkar wrote:
On Friday 29 Apr 2011 2:33:42 pm br...@amason.net wrote:
Well, I downloaded version 0.4.0 and the latest fprint-demo. fprint-demo
doesn't see the fingerprint scanner.
However, running the example codes I get this when trying to enroll or
verify-live.
$sudo ./enroll
Found device claimed by Validity VFS101 driver
Opened device. It's now time to enroll your finger.
You will need to successfully scan your finger 3 times to complete the
process.
Scan your finger now.
vfs101:error [async_recv_cb] transfer not completed, status = 6
async:error [fpi_drvcb_enroll_stage_completed] BUG at async.c:161
sync:error [fp_enroll_finger_img] unrecognised return code -5
Enroll failed with error -22
Most likely, the protocol is different than vfs101/201.
Maybe, it has different registers? maybe takes different values for dev
init?
who knows?
So, just adding the dev ids in vfs101.c won't help.
We'll need to understand the protocol from usb-sniff logs.
It's a daunting task, to be honest. VFS101 was made possible due to
Ray Lehtiniemi's efforts to reverse-engineer the protocol from sniff logs.
Kudos to him. And of course, vfs101.c primary author - Sergio Cerlesi. :)
Even the current vfs101.c doesn't cover up all the states for my VFS201
sensor
- but, at least it can get the image out.
Now it says VFS101, but I left the code alone and added the VFS301 to
the
list of supported devices for the driver.
$ diff vfs101.c vfs101.c.new
1542a1543
{ .vendor = 0x138a, .product = 0x0005 },
That is because you _explicitly_ added the devid in the driver - so, while
scanning the devices, libfprint sees that vfs101 driver *claims* to
support
the device that it found using usb ids.
--
The other examples gave other messages.
$sudo ./img_capture
Found device claimed by Validity VFS101 driver
Opened device. It's now time to scan your finger.
image capture failed, code -95
Verify failed because the was no file to verify.
cpp-test seems to do nothing, but no error.
cpp-test is a simple C++ program that just tries to link to the
fprint library - to make sure that we can still call the libfprint
functions from C++ code.
It doesn't serve any other purpose.
That's all for tonight (morning). I'll have to dig into the code to see
what the messages mean.
Brian
IOW, there is a lot more work to be done for Validity sensors.
We're just starting off with some usable code.
But, it needs a lot of patience - which, I hope, we'll have ;)
I'd rather prefer to have an open source driver than anything
closed-source from Validity Inc. ;)
Kunal
___
fprint mailing list
fprint@reactivated.net
http://lists.reactivated.net/mailman/listinfo/fprint
Re: [fprint] Digital Persona 138a:0005
Hi there, So here is what we know: 1) The id 138a:0005 is the VFS301 Validity Inc. sensor encrypted. The Digital Persona is the software. I submitted a bug to indicate that is wrong detected by linux kernel to the kernel.org team and I got this answer: That string either comes from the lsusb usb.ids database, which isn't in te kernel, or from the device itself. Either way, there's nothing that the kernel can do about it, sorry. Also, odds are the device is manufactured by a different vendor, so the old device id is being used, but as the device works fine, I wouldn't worry about it. And I can confirm that is a Validity hardware because the driver for device in windows 7 from the hp official website is named VFS301 and I got an email from validity inc. that confirms the id 138a:0005 as a VFS301. 2) As Lukáš point out Validity supposed to release a driver for the VFS101. Well it has not been release and the fprint dev already released a working driver for VFS101. Beside, several people tried (including me) the VFS101 driver (changing the id on the patch) on other Validity hardware and it has not worked in other device that is not the VFS101. We know that the VFS101 driver for linux adapted (changing the id) doesn't work for the VFS301 (and neither VFS451 and VFS471) 3) As Lukáš said they supposed to be working with HP to develop a driver. But they are really taking long, I really doubt that they are working on a driver for linux. I asked for support to the Validty Inc. and is they are working on a driver and got a reply the on the 01.04.2011 (just one month ago) that the VFS101 driver may work. But it doesnt. I asked for more info about the device but no reply. So as I got no answer regarding their work on the development for a linux driver, I assume that they are not doing it. So basically we are at this point, I will send another email to Validity asking for the specs and capabilities of the chip(s)or other info that could help for a linux-driver for the VFS301 and see what we can get from them. ___ fprint mailing list fprint@reactivated.net http://lists.reactivated.net/mailman/listinfo/fprint
Re: [fprint] Digital Persona 138a:0005
Ok, thanks. So I updated my usbids and it now reports the device properly as a Validity VFS301 fingerprint reader. The general consensus seems to be to try hacking on the VFS101 driver. So, I guess I'll go build the code from the latest, and see what happens. At the worst I'll get some debug info. Thanks, guys. Brian On Tue, April 26, 2011 3:15 pm, Lukáš Karas wrote: Hi Brian. Usb id 138a isn't Digital Persona, but Validity Inc. I got mail from HP that they work with Validity on proprietary driver some months ago... [1] And today, I found message from Validity that they will release Ubuntu package by the end of year 2010... [2]. But now is year 2011 and driver (proprietary or opensource) nowhere... (I mean driver for newer devices than VS101) Lukas 1. http://www.mail-archive.com/fprint@reactivated.net/msg01589.html 2. http://www.omgubuntu.co.uk/2010/09/vfs101-fingerprint-reader-driver-coming- for-ubuntu/ Dne Pá 22. dubna 2011 23:38:47 br...@amason.net napsal(a): I have a Digital persona 138a:0005 in my HP dv7 laptop. Willing to help with development of support for this device. I have a full development environ set up, but not all the pieces for fprint dev. Let me know if there is anything I can do to help. I can code, debug, test, whatever. Brian ___ fprint mailing list fprint@reactivated.net http://lists.reactivated.net/mailman/listinfo/fprint ___ fprint mailing list fprint@reactivated.net http://lists.reactivated.net/mailman/listinfo/fprint
