From sergio.cerlesi at gmail.com Mon Apr 4 11:23:36 2011 From: sergio.cerlesi at gmail.com (Sergio Cerlesi) Date: Mon, 04 Apr 2011 12:23:36 +0200 Subject: [fprint] New driver for Validity VFS101 Message-ID: <1301912616.5794.5.camel@cerlyLp> Hi Daniel, Bastien, the attached patch add support for Validity VFS101 (USB ID 138a:0001). Bye Sergio -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-Added-support-for-Validity-VFS101-USB-ID-138a-0001.patch Type: text/x-patch Size: 41763 bytes Desc: not available Url : http://lists.reactivated.net/pipermail/fprint/attachments/20110404/e64d0121/0001-Added-support-for-Validity-VFS101-USB-ID-138a-0001-0001.bin From rafaeldtoledo at gmail.com Wed Apr 6 21:43:30 2011 From: rafaeldtoledo at gmail.com (Rafael Toledo) Date: Wed, 06 Apr 2011 17:43:30 -0300 Subject: [fprint] AES3500 Device Message-ID: <4D9CD072.8030602@gmail.com> Hi! I'm developing a Linux system with a fingerprint reader. I have a APC Fingerprint reader, with AES3500. I checked that this driver isn't avaliable in fprint, then, I contacted Tobias Wolf that is in the Wiki's page as the developer of the driver. Here's the email reply: "I don?t know why my name is listed there. I never announced that I plan to work on that device. I merely posted to the mailing list and when someone asked me to provide a USB log I posted it. If you have access to that page, can you remove my name? I don?t have this device anymore, I?m using a Lenovo X301 now whose fingerprint driver is not supported either. I have simply giving up on fingerprint stuff." Well, I don't know how to build a driver, but I can help with logs or another helpful info. Best Regards Rafael Toledo From machese at gmail.com Thu Apr 7 01:58:47 2011 From: machese at gmail.com (Juvenn Woo) Date: Thu, 7 Apr 2011 08:58:47 +0800 Subject: [fprint] AES3500 Device In-Reply-To: <4D9CD072.8030602@gmail.com> References: <4D9CD072.8030602@gmail.com> Message-ID: Hi Rafael, I have this device too. What Tobias Wolf did, AFAIK, was to reassemble the AES 4000 driver, change the image dimension, and compile it as a AES 3500 driver. Which hadn't gone so far as a working driver. I don't think there were anyone working on the devices thereafter. I'm looking to work on this, though with my shallow experience in driver development, you should not expect too much from me. Anyway, if you could help, maybe we can sort this out? I'm trying to get a Windows driver, XP specifically, so we could sniff the USB in Windows first. Do you have a Windows driver? Thanks. Best, -- Juvenn Woo ? On Thu, Apr 7, 2011 at 4:43 AM, Rafael Toledo wrote: > Hi! > > I'm developing a Linux system with a fingerprint reader. I have a APC > Fingerprint reader, with AES3500. I checked that this driver isn't > avaliable in fprint, then, I contacted Tobias Wolf that is in the Wiki's > page as the developer of the driver. Here's the email reply: > > "I don?t know why my name is listed there. I never announced that I plan > to work on that device. I merely posted to the mailing list and when > someone asked me to provide a USB log I posted it. If you have access to > that page, can you remove my name? I don?t have this device anymore, I?m > using a Lenovo X301 now whose fingerprint driver is not supported > either. I have simply giving up on fingerprint stuff." > > Well, I don't know how to build a driver, but I can help with logs or > another helpful info. > > Best Regards > Rafael Toledo > _______________________________________________ > fprint mailing list > fprint at reactivated.net > http://lists.reactivated.net/mailman/listinfo/fprint > From hadess at hadess.net Fri Apr 8 15:40:30 2011 From: hadess at hadess.net (Bastien Nocera) Date: Fri, 08 Apr 2011 15:40:30 +0100 Subject: [fprint] New driver for Validity VFS101 In-Reply-To: <1301912616.5794.5.camel@cerlyLp> References: <1301912616.5794.5.camel@cerlyLp> Message-ID: <1302273632.5271.1.camel@novo.hadess.net> On Mon, 2011-04-04 at 12:23 +0200, Sergio Cerlesi wrote: > Hi Daniel, Bastien, > > the attached patch add support for Validity VFS101 (USB ID 138a:0001). Pushed (after removing the trailing spaces). I'll do a release in a couple of days. Thanks! From lopan.eti at gmail.com Wed Apr 13 23:30:08 2011 From: lopan.eti at gmail.com (Arlindo F. Neto) Date: Wed, 13 Apr 2011 22:30:08 +0000 Subject: [fprint] 138a:0008 - VFS300 Fingeprint Reader Message-ID: Hi, Is there anyone working in this device? Can I help? Has a lot of messagens on web looking for a VFS300 driver, and, me too! lol regards, -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.reactivated.net/pipermail/fprint/attachments/20110413/e7ce8cbf/attachment.html From methaniya.mukesh at gmail.com Thu Apr 14 14:17:46 2011 From: methaniya.mukesh at gmail.com (methaniya mukesh) Date: Thu, 14 Apr 2011 18:47:46 +0530 Subject: [fprint] not detect finger print reader in libfprint Message-ID: dev :no dev device found whe i type dmesg this error exist apture_finger1[27917]: segfault at 0 ip b7efff58 sp bff22074 error 4 in libdpfp.so.0.0.0[b7efe000+6000] this error exist *Mukesh G Methaniya **Ahmedabad, India **Mobile: **+919998186874 Email:methaniya.mukesh at gmail.com ***** -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.reactivated.net/pipermail/fprint/attachments/20110414/4145af6a/attachment.html From hadess at hadess.net Thu Apr 14 17:18:34 2011 From: hadess at hadess.net (Bastien Nocera) Date: Thu, 14 Apr 2011 17:18:34 +0100 Subject: [fprint] not detect finger print reader in libfprint In-Reply-To: References: Message-ID: <1302797915.28592.39.camel@novo.hadess.net> On Thu, 2011-04-14 at 18:47 +0530, methaniya mukesh wrote: > dev :no dev device found > > whe i type dmesg this error exist > apture_finger1[27917]: segfault at 0 ip b7efff58 sp bff22074 error 4 > in libdpfp.so.0.0.0[b7efe000+6000] You're using some outdated code which doesn't have anything to do with libfprint. libdpfp is from http://dpfp.berlios.de/wikka.php?wakka=HomePage Cheers From rafaeldtoledo at gmail.com Thu Apr 14 18:43:59 2011 From: rafaeldtoledo at gmail.com (Rafael Toledo) Date: Thu, 14 Apr 2011 14:43:59 -0300 Subject: [fprint] Cross-compile fprint Message-ID: <4DA7325F.9090307@gmail.com> Did someone make it? I can do this (using arm-linux-gcc)? How? From vishnu.kumar at mahiti.org Mon Apr 18 14:38:19 2011 From: vishnu.kumar at mahiti.org (Vishnu Kumar D R) Date: Mon, 18 Apr 2011 19:08:19 +0530 Subject: [fprint] fprint 0.3.0, dp4500 and Ubuntu 10.04 Message-ID: Hi, I am trying to use fprint from http://cgit.freedesktop.org/libfprint/ and setup PAM authentication based on it in my Ubuntu Desktop 10.04. But, when i launch the 'fprint_demo' ( an GUI for fingerprint enrollment) It fails after searching for the encryption bit. It seems to work on uru4000B driver, then why does it fail? Any idea? P.S. Have attached the fprint_demo log. Regards, Vishnu Kumar Mahiti Support Mahiti Infotech Pvt. Ltd. http://www.mahiti.org 583 Vyalikaval HBCS Layout Nagawara, Veerannapalya Bangalore 560 045 Karnataka, India (map details) -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.reactivated.net/pipermail/fprint/attachments/20110418/dd9b3681/attachment-0001.html -------------- next part -------------- mahiti at mahiti-admin:~$ fprint_demo 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 [find_supporting_driver] driver uru4000 supports USB device 05ba:000a fp:debug [find_supporting_driver] selected driver uru4000 supports USB device 05ba:000a sync:debug [fp_dev_open] async:debug [fp_async_dev_open] async:debug [fpi_drvcb_open_complete] status 0 sync:debug [sync_open_cb] status 0 sync:debug [fp_enroll_finger_img] async:debug [fp_async_enroll_start] starting enrollment fp:debug [generic_acquire_start] action 1 drv:debug [__ssm_call_handler] 0x8598b70 entering state 0 uru4000:debug [sm_read_reg] read reg 7 sync:debug [fp_enroll_finger_img] uru4000 will handle enroll stage 0/0 uru4000:debug [sm_read_reg_cb] reg value 81 drv:debug [__ssm_call_handler] 0x8598b70 entering state 1 drv:debug [__ssm_call_handler] 0x8598b70 entering state 3 drv:debug [__ssm_call_handler] 0x8598b70 entering state 4 drv:debug [__ssm_call_handler] 0x8599f50 entering state 0 drv:debug [__ssm_call_handler] 0x8599f50 entering state 1 uru4000:debug [fwfixer_run_state] looking for encryption byte at 510 uru4000:debug [fwfixer_read_cb] data: 58 06 15 drv:debug [__ssm_call_handler] 0x8599f50 entering state 1 uru4000:debug [fwfixer_run_state] looking for encryption byte at 62d uru4000:debug [fwfixer_read_cb] data: 33 72 05 drv:debug [__ssm_call_handler] 0x8599f50 entering state 1 uru4000:debug [fwfixer_run_state] looking for encryption byte at 792 uru4000:debug [fwfixer_read_cb] data: 0f 10 0c drv:debug [__ssm_call_handler] 0x8599f50 entering state 1 uru4000:debug [fwfixer_run_state] looking for encryption byte at 7f4 uru4000:debug [fwfixer_read_cb] data: 0c 40 14 drv:debug [__ssm_call_handler] 0x8599f50 entering state 1 uru4000:error [fwfixer_run_state] could not find encryption byte drv:debug [fpi_ssm_mark_aborted] error -19 from state 1 drv:debug [fpi_ssm_mark_completed] 0x8599f50 completed with status -19 drv:debug [fpi_ssm_mark_aborted] error -19 from state 4 drv:debug [fpi_ssm_mark_completed] 0x8598b70 completed with status -19 fp:debug [fpi_imgdev_activate_complete] status -19 async:debug [fpi_drvcb_enroll_started] status -19 sync:debug [sync_enroll_cb] result -19 sync:error [fp_enroll_finger_img] unrecognised return code -19 sync:debug [fp_enroll_finger_img] ending enrollment async:debug [fp_async_enroll_stop] drv:debug [__ssm_call_handler] 0x8599f50 entering state 0 uru4000:debug [sm_set_mode] mode 00 drv:debug [__ssm_call_handler] 0x8599f50 entering state 1 uru4000:debug [sm_set_hwstat] set 80 drv:debug [fpi_ssm_mark_completed] 0x8599f50 completed with status 0 uru4000:debug [irq_handler] cancelled fp:debug [fpi_imgdev_deactivate_complete] async:debug [fpi_drvcb_enroll_stopped] sync:debug [enroll_stop_cb] From hadess at hadess.net Mon Apr 18 18:11:09 2011 From: hadess at hadess.net (Bastien Nocera) Date: Mon, 18 Apr 2011 18:11:09 +0100 Subject: [fprint] libfprint 0.4.0 and fprintd 0.4.0 Message-ID: <1303146670.25922.2.camel@novo.hadess.net> Heya, New versions of libfprint and fprintd available. Many thanks to Sergio Cerlesi for his Validity VFS101 driver, and the associated bug fixes. libfprint: 2011-04-18: v0.4.0 release * Add support for Validity VFS101 (USB ID 138a:0001) * Fix crasher when resizing a fingerprint image * Fix wrong timeout being returned when either of libusb or libfprint doesn't have a timeout http://people.freedesktop.org/~hadess/libfprint-0.4.0.tar.bz2 fprintd: version 0.4.0: - Loads of new translations - Fix crasher when PAM module gets unloaded - Use GIO to monitor D-Bus clients instead of custom code http://people.freedesktop.org/~hadess/fprintd-0.4.0.tar.bz2 Cheers From hadess at hadess.net Tue Apr 19 00:31:23 2011 From: hadess at hadess.net (Bastien Nocera) Date: Tue, 19 Apr 2011 00:31:23 +0100 Subject: [fprint] fprintd 0.4.1 (was Re: libfprint 0.4.0 and fprintd 0.4.0) In-Reply-To: <1303146670.25922.2.camel@novo.hadess.net> References: <1303146670.25922.2.camel@novo.hadess.net> Message-ID: <1303169486.25922.4.camel@novo.hadess.net> On Mon, 2011-04-18 at 18:11 +0100, Bastien Nocera wrote: > fprintd: > version 0.4.0: And version 0.4.1 to fix building with documentation enabled. http://people.freedesktop.org/~hadess/fprintd-0.4.1.tar.bz2 Cheers From vishnu.kumar at mahiti.org Tue Apr 19 05:28:39 2011 From: vishnu.kumar at mahiti.org (Vishnu Kumar D R) Date: Tue, 19 Apr 2011 09:58:39 +0530 Subject: [fprint] fprint 0.3.0, dp4500 and Ubuntu 10.04 In-Reply-To: <4DAC5852.7070706@pktsolutions.com> References: <4DAC5852.7070706@pktsolutions.com> Message-ID: Hi Ben, Thanks for replying. But i didnt get what you tried to tell me. Does your statements mean that its not possible, or a workaround needs to be implemented?? Regards, Vishnu Kumar Mahiti Support Mahiti Infotech Pvt. Ltd. http://www.mahiti.org 583 Vyalikaval HBCS Layout Nagawara, Veerannapalya Bangalore 560 045 Karnataka, India (map details) On Mon, Apr 18, 2011 at 8:57 PM, Ben Green wrote: > Hi Vishnu, > > I have a Digital Persona URU 4500 fingerprint reader myself, they work in a > similar way to the 4000B but the data is always encrypted from what I can > tell. I have spent some time trying to decrypt the data stream that is > returned over the USB bus but so far have had no success. The key is in > dpD00701.dll provided with the SDK, I have located where the data goes in to > the DPHostW service and where it comes back out but in the middle plenty of > funny stuff happens with the data being passed from one thread to another > and it is very difficult to track. > > Benjamin. > > > On 18/04/2011 14:38, Vishnu Kumar D R wrote: > >> Hi, >> >> I am trying to use fprint from http://cgit.freedesktop.org/libfprint/ and >> setup PAM authentication based on it in my Ubuntu Desktop 10.04. >> But, when i launch the 'fprint_demo' ( an GUI for fingerprint enrollment) >> It fails after searching for the encryption bit. >> >> It seems to work on uru4000B driver, then why does it fail? >> >> Any idea? >> >> P.S. Have attached the fprint_demo log. >> >> Regards, >> Vishnu Kumar >> Mahiti Support >> >> Mahiti Infotech Pvt. Ltd. >> http://www.mahiti.org >> >> _______________________________________________ >> fprint mailing list >> fprint at reactivated.net >> http://lists.reactivated.net/mailman/listinfo/fprint >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.reactivated.net/pipermail/fprint/attachments/20110419/92aa0236/attachment.html From oegoen at gmail.com Tue Apr 19 17:16:01 2011 From: oegoen at gmail.com (=?ISO-8859-1?B?TulP?=) Date: Tue, 19 Apr 2011 18:16:01 +0200 Subject: [fprint] Device request Message-ID: Hi, Once fingerprint-gui correctly installed, i found my fingerprint reader in the attached usb devices list. But it wasn't possible to find it in the combo box : "No devices found !" lsusb command gives : Bus 001 Device 004: ID 138a:0007 DigitalPersona, Inc My laptop is a HP EliteBook 8740w Thanks a lot for your work. I hope I could use it soon ! Regards. Alain -- Things should be as simple as possible. But no simpler (A. Einstein). -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.reactivated.net/pipermail/fprint/attachments/20110419/b81115aa/attachment.html From rajendra.racha at gmail.com Wed Apr 20 07:31:40 2011 From: rajendra.racha at gmail.com (Rajendra prasad) Date: Wed, 20 Apr 2011 12:01:40 +0530 Subject: [fprint] Cross compiling libfprint for ARM Linux Message-ID: Hi. This is Rajendra. I am trying to cross compile the libfprint libraries for arm architecture. But while configuring the library im getting configure error as glib-2.0 not found. So i downloaded the glib source from net. But while cross compiling glib command im getting error as follows. That error as follows. -->make gatomic.c:607: Error: no such instruction: swp %eax,%eax,[%edx]. So ple suggest me, what could be the problem for getting above errror. And is it possible to compile libfprint witout glib-2.0. Thanking you. -- Sent from my mobile device _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Best Regards R.R.Prasad +91-7893535148 From machese at gmail.com Wed Apr 20 10:09:40 2011 From: machese at gmail.com (Juvenn Woo) Date: Wed, 20 Apr 2011 17:09:40 +0800 Subject: [fprint] Progress on AES3500 Message-ID: Hi all, With Rafael Toledo's help, we've been able to make good progress on device AES3500 (aka BioPod). Attached is an enrolled sample, with the driver code to make it. As you can see it's able to make a complete scan, the strips are well connected, but the scanned quality is not that good. The image is a little fussy, and no more than 10 minutiaes detected, which is not quite good, as NBIS needs more than 10 minutiaes to work. There are quite a lot of initial_reqs to initialize the device, which are used to set up the environment or so, I think. The next step, I think, is to tweak the initial_reqs, to improve the quality of scanned image. A sniffed log of windows driver is attached, if anyone can help figure out the bits, that would be great! P.S.: AES3500 is a relatively low-end device, there're plenty of supply in China, with very cheap price, which is about $5USD - $10USD. Best, -- Juvenn Woo ? From hadess at hadess.net Wed Apr 20 12:02:57 2011 From: hadess at hadess.net (Bastien Nocera) Date: Wed, 20 Apr 2011 12:02:57 +0100 Subject: [fprint] Cross compiling libfprint for ARM Linux In-Reply-To: References: Message-ID: <1303297379.25922.29.camel@novo.hadess.net> On Wed, 2011-04-20 at 12:01 +0530, Rajendra prasad wrote: > Hi. > > This is Rajendra. I am trying to cross compile the libfprint libraries > for arm architecture. > > But while configuring the library im getting configure error as > glib-2.0 not found. > > So i downloaded the glib source from net. But while cross compiling > glib command im getting error as follows. > That error as follows. > -->make > gatomic.c:607: Error: no such instruction: swp %eax,%eax,[%edx]. This is a problem in your cross-compiling setup, or in glib. Not a problem in libfprint anyway. > So ple suggest me, what could be the problem for getting above errror. > And is it possible to compile libfprint witout glib-2.0. Afraid not. Cheers From rafaeldtoledo at gmail.com Wed Apr 20 12:14:13 2011 From: rafaeldtoledo at gmail.com (Rafael Toledo) Date: Wed, 20 Apr 2011 08:14:13 -0300 Subject: [fprint] Cross compiling libfprint for ARM Linux In-Reply-To: <1303297379.25922.29.camel@novo.hadess.net> References: <1303297379.25922.29.camel@novo.hadess.net> Message-ID: Hi! I'm trying to cross-compile libfprint for an ARM device too. In my journey, I stopped because I can't cross-compile the libnss3 (requierement for libfprint). Let's maintain some communication, maybe we can help each order! 2011/4/20 Bastien Nocera > On Wed, 2011-04-20 at 12:01 +0530, Rajendra prasad wrote: > > Hi. > > > > This is Rajendra. I am trying to cross compile the libfprint libraries > > for arm architecture. > > > > But while configuring the library im getting configure error as > > glib-2.0 not found. > > > > So i downloaded the glib source from net. But while cross compiling > > glib command im getting error as follows. > > That error as follows. > > -->make > > gatomic.c:607: Error: no such instruction: swp %eax,%eax,[%edx]. > > This is a problem in your cross-compiling setup, or in glib. Not a > problem in libfprint anyway. > > > So ple suggest me, what could be the problem for getting above errror. > > And is it possible to compile libfprint witout glib-2.0. > > Afraid not. > > Cheers > > _______________________________________________ > fprint mailing list > fprint at reactivated.net > http://lists.reactivated.net/mailman/listinfo/fprint > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.reactivated.net/pipermail/fprint/attachments/20110420/de9f2f5f/attachment-0001.html From vishnu.kumar at mahiti.org Wed Apr 20 12:30:27 2011 From: vishnu.kumar at mahiti.org (Vishnu Kumar D R) Date: Wed, 20 Apr 2011 17:00:27 +0530 Subject: [fprint] Error while compiling latest fprintd-0.4.1 on Ubuntu 10.04 Message-ID: Hi, Heres the error: checking for FPRINT... yes checking for GLIB... yes checking for DAEMON... no configure: error: Package requirements (glib-2.0 dbus-glib-1 gmodule-2.0 polkit-gobject-1 >= 0.91 gio-2.0 >= 2.26) were not met: Requested 'gio-2.0 >= 2.26' but version of GIO is 2.24.1 Do i need to reinstall anything? Regards, Vishnu Kumar Mahiti Support Mahiti Infotech Pvt. Ltd. http://www.mahiti.org 583 Vyalikaval HBCS Layout Nagawara, Veerannapalya Bangalore 560 045 Karnataka, India (map details) -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.reactivated.net/pipermail/fprint/attachments/20110420/c1553bf2/attachment.html From rajendra.racha at gmail.com Wed Apr 20 12:59:09 2011 From: rajendra.racha at gmail.com (Rajendra prasad) Date: Wed, 20 Apr 2011 17:29:09 +0530 Subject: [fprint] Cross compiling libfprint for ARM Linux In-Reply-To: <1303297379.25922.29.camel@novo.hadess.net> References: <1303297379.25922.29.camel@novo.hadess.net> Message-ID: Hi. Thanks for your responce. Ok i agree with you. Now i compiled glib and installed as well. Now im trying to compile fprint library. While make command im getting error as follows. gdate.h:179: Error: expected declation specifiers or '...' before 'GTime' like this im getting for all files in glib include directory. Pls help me, why im getting the above errors On 4/20/11, Bastien Nocera wrote: > On Wed, 2011-04-20 at 12:01 +0530, Rajendra prasad wrote: >> Hi. >> >> This is Rajendra. I am trying to cross compile the libfprint libraries >> for arm architecture. >> >> But while configuring the library im getting configure error as >> glib-2.0 not found. >> >> So i downloaded the glib source from net. But while cross compiling >> glib command im getting error as follows. >> That error as follows. >> -->make >> gatomic.c:607: Error: no such instruction: swp %eax,%eax,[%edx]. > > This is a problem in your cross-compiling setup, or in glib. Not a > problem in libfprint anyway. > >> So ple suggest me, what could be the problem for getting above errror. >> And is it possible to compile libfprint witout glib-2.0. > > Afraid not. > > Cheers > > -- Sent from my mobile device _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Best Regards R.R.Prasad +91-7893535148 From acassis at gmail.com Wed Apr 20 15:22:43 2011 From: acassis at gmail.com (Alan Carvalho de Assis) Date: Wed, 20 Apr 2011 12:22:43 -0200 Subject: [fprint] Progress on AES3500 In-Reply-To: References: Message-ID: On 4/20/11, Juvenn Woo wrote: > Hi all, > > With Rafael Toledo's help, we've been able to make good progress on > device AES3500 (aka BioPod). Attached is an enrolled sample, with the > driver code to make it. Hi Juvem, I think you forgot to attach it. BR, Alan From machese at gmail.com Fri Apr 22 04:28:39 2011 From: machese at gmail.com (Juvenn Woo) Date: Fri, 22 Apr 2011 11:28:39 +0800 Subject: [fprint] Progress on AES3500 In-Reply-To: References: Message-ID: I'm sorry, but my updated email (with attachments) has been hold for moderator approval. Hi Bastien, can you check the moderation queue, and approve my email with the attachments? Or should I repost the files here, it seems exceed the max size allowed. Thanks! Best, -- Juvenn Woo ? On Thu, Apr 21, 2011 at 9:21 AM, Juvenn Woo wrote: > Oh, sorry, re-attached :-) > > Thank you, Alan! > > Best, > -- > Juvenn Woo ? > > > > > On Wed, Apr 20, 2011 at 10:22 PM, Alan Carvalho de Assis > wrote: >> On 4/20/11, Juvenn Woo wrote: >>> Hi all, >>> >>> With Rafael Toledo's help, we've been able to make good progress on >>> device AES3500 (aka BioPod). Attached is an enrolled sample, with the >>> driver code to make it. >> >> Hi Juvem, >> >> I think you forgot to attach it. >> >> BR, >> >> Alan >> > From hadess at hadess.net Fri Apr 22 11:33:54 2011 From: hadess at hadess.net (Bastien Nocera) Date: Fri, 22 Apr 2011 11:33:54 +0100 Subject: [fprint] Progress on AES3500 In-Reply-To: References: Message-ID: <1303468436.10712.16.camel@novo.hadess.net> On Fri, 2011-04-22 at 11:28 +0800, Juvenn Woo wrote: > I'm sorry, but my updated email (with attachments) has been hold for > moderator approval. > > Hi Bastien, can you check the moderation queue, and approve my email > with the attachments? Or should I repost the files here, it seems > exceed the max size allowed. I don't have moderator access to the list. Send it again without the attachment, or put the attachment somewhere else. Cheers From brian at amason.net Fri Apr 22 22:38:47 2011 From: brian at amason.net (brian@amason.net) Date: Fri, 22 Apr 2011 16:38:47 -0500 Subject: [fprint] Digital Persona 138a:0005 Message-ID: <266531701a9dfb4e3fd226500c109bd4.squirrel@www.amason.net> 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 From carlos.vedovatti at googlemail.com Sat Apr 23 14:01:40 2011 From: carlos.vedovatti at googlemail.com (Carlos Vedovatti) Date: Sat, 23 Apr 2011 15:01:40 +0200 Subject: [fprint] help for VFS301 the VID/PID 138a:0005 Message-ID: <1303563700.2722.1.camel@Linux> Hi there, I would like to ask for support for this device. 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" VFS301 but they use digitalpersona software. I opened a bug in launchpad.net #744310 to see if something comes out. I tried the patch that was build for the VFS301, changing the id parameter but didn't work. A pity. I got an email from Validity Inc. support that the patch may work. But no... So.. does anybody has idea of what documentation would be necessary to build a driver? or if modifying the driver for the VFS101 would work on the VFS301? Its a pity is the only hardware that doesn't work on my computer under Linux. Thanks -- Carlos Before printing, think about the environment. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.reactivated.net/pipermail/fprint/attachments/20110423/f9025e39/attachment.html From machese at gmail.com Sun Apr 24 06:23:12 2011 From: machese at gmail.com (Juvenn Woo) Date: Sun, 24 Apr 2011 13:23:12 +0800 Subject: [fprint] Progress on AES3500 with code listing Message-ID: Sorry friends, my attached code and log files have been holding for moderation. And I've posted somewhere else as Bastien suggested, sorry if I've flooded your inbox. Code and log listings: https://gist.github.com/939298 Enrolled sample is attached. Best, -- Juvenn Woo ? On Fri, Apr 22, 2011 at 6:33 PM, Bastien Nocera wrote: > On Fri, 2011-04-22 at 11:28 +0800, Juvenn Woo wrote: >> I'm sorry, but my updated email (with attachments) has been hold for >> moderator approval. >> >> Hi Bastien, can you check the moderation queue, and approve my email >> with the attachments? Or should I repost the files here, it seems >> exceed the max size allowed. > > I don't have moderator access to the list. Send it again without the > attachment, or put the attachment somewhere else. > > Cheers > > -------------- next part -------------- A non-text attachment was scrubbed... Name: enrolled.pgm Type: image/x-portable-graymap Size: 16399 bytes Desc: not available Url : http://lists.reactivated.net/pipermail/fprint/attachments/20110424/d22b8627/enrolled-0001.pgm From rajendra.racha at gmail.com Tue Apr 26 07:59:12 2011 From: rajendra.racha at gmail.com (Rajendra prasad) Date: Tue, 26 Apr 2011 12:29:12 +0530 Subject: [fprint] Cross compiling libfprint for ARM Linux In-Reply-To: <4DAECBFB.20108@gmail.com> References: <1303297379.25922.29.camel@novo.hadess.net> <4DAECBFB.20108@gmail.com> Message-ID: Hi. I cross compiled and loaded all the fprint dependent libraries on my device. But while running the enroll example on device i am getting the below error. ./enroll found device claimed by UPEK TouchChip driver fp:error [fp_dev_open] device initialisation failed, driver=upektc Could not open device. Please suggest me, what could be the problem for getting the above error. On 4/20/11, Rafael Toledo wrote: > Hello, > > Please, tell me your steps: which cross-compiler you used, the links to > download the libs you used. > I stopped when the make can't find '-lss3'. > > On 20-04-2011 08:59, Rajendra prasad wrote: >> Hi. >> >> Thanks for your responce. >> Ok i agree with you. Now i compiled glib and installed as well. >> >> Now im trying to compile fprint library. While make command im getting >> error as follows. >> gdate.h:179: Error: expected declation specifiers or '...' before 'GTime' >> like this im getting for all files in glib include directory. >> >> Pls help me, why im getting the above errors >> >> >> On 4/20/11, Bastien Nocera wrote: >>> On Wed, 2011-04-20 at 12:01 +0530, Rajendra prasad wrote: >>>> Hi. >>>> >>>> This is Rajendra. I am trying to cross compile the libfprint libraries >>>> for arm architecture. >>>> >>>> But while configuring the library im getting configure error as >>>> glib-2.0 not found. >>>> >>>> So i downloaded the glib source from net. But while cross compiling >>>> glib command im getting error as follows. >>>> That error as follows. >>>> -->make >>>> gatomic.c:607: Error: no such instruction: swp %eax,%eax,[%edx]. >>> This is a problem in your cross-compiling setup, or in glib. Not a >>> problem in libfprint anyway. >>> >>>> So ple suggest me, what could be the problem for getting above errror. >>>> And is it possible to compile libfprint witout glib-2.0. >>> Afraid not. >>> >>> Cheers >>> >>> > > -- Sent from my mobile device _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Best Regards R.R.Prasad +91-7893535148 From rafaeldtoledo at gmail.com Tue Apr 26 12:05:48 2011 From: rafaeldtoledo at gmail.com (Rafael Toledo) Date: Tue, 26 Apr 2011 08:05:48 -0300 Subject: [fprint] Cross compiling libfprint for ARM Linux In-Reply-To: References: <1303297379.25922.29.camel@novo.hadess.net> <4DAECBFB.20108@gmail.com> Message-ID: <4DB6A70C.4050503@gmail.com> I'm trying to cross compile, but I can't cross compile nss. How you make it? On 26-04-2011 03:59, Rajendra prasad wrote: > Hi. > > I cross compiled and loaded all the fprint dependent libraries on my device. > But while running the enroll example on device i am getting the below error. > ./enroll > found device claimed by UPEK TouchChip driver > fp:error [fp_dev_open] device initialisation failed, driver=upektc > Could not open device. > > Please suggest me, what could be the problem for getting the above error. > > > > > > > > > > > > > > > > > > > On 4/20/11, Rafael Toledo wrote: >> Hello, >> >> Please, tell me your steps: which cross-compiler you used, the links to >> download the libs you used. >> I stopped when the make can't find '-lss3'. >> >> On 20-04-2011 08:59, Rajendra prasad wrote: >>> Hi. >>> >>> Thanks for your responce. >>> Ok i agree with you. Now i compiled glib and installed as well. >>> >>> Now im trying to compile fprint library. While make command im getting >>> error as follows. >>> gdate.h:179: Error: expected declation specifiers or '...' before 'GTime' >>> like this im getting for all files in glib include directory. >>> >>> Pls help me, why im getting the above errors >>> >>> >>> On 4/20/11, Bastien Nocera wrote: >>>> On Wed, 2011-04-20 at 12:01 +0530, Rajendra prasad wrote: >>>>> Hi. >>>>> >>>>> This is Rajendra. I am trying to cross compile the libfprint libraries >>>>> for arm architecture. >>>>> >>>>> But while configuring the library im getting configure error as >>>>> glib-2.0 not found. >>>>> >>>>> So i downloaded the glib source from net. But while cross compiling >>>>> glib command im getting error as follows. >>>>> That error as follows. >>>>> -->make >>>>> gatomic.c:607: Error: no such instruction: swp %eax,%eax,[%edx]. >>>> This is a problem in your cross-compiling setup, or in glib. Not a >>>> problem in libfprint anyway. >>>> >>>>> So ple suggest me, what could be the problem for getting above errror. >>>>> And is it possible to compile libfprint witout glib-2.0. >>>> Afraid not. >>>> >>>> Cheers >>>> >>>> >> From brian at amason.net Tue Apr 26 17:49:30 2011 From: brian at amason.net (brian@amason.net) Date: Tue, 26 Apr 2011 11:49:30 -0500 Subject: [fprint] Digital Persona 138a:0005 In-Reply-To: <1303810418.2925.9.camel@Linux> References: <1303810418.2925.9.camel@Linux> Message-ID: Carlos and devs, I saw your email. The development group is probably working a full load as it is. I was hoping someone was working on a similar model, and that I could run tests and dump data out for them to see and possibly give me direction on things I could do to help bring this scanner under one of the drivers. I could do some coding also. It's what I do. I don't do much currently, in fact none, in the way of writing device drivers. However, I do know *how* to write Linux device drivers for the 2.6 kernel. I'm not looking to jump in all cold turkey and do it all by myself, but if someone were to give me some directions and tasks to complete I would be more than willing to tackle the task of working with someone in adding this to an existing driver, or create a new one by forking an existing driver for this scanner. However, without knowing which driver might possibly be compatible and which one could be stripped down to a basic shell to begin exploring the capabilities I am unwilling to risk damaging it. Yet. It would be nice to know who really makes the chip, but this is my business laptop, so I will not be hacking this one by disassembling and dissecting and/or modding. At least not until the warranty is up and I am left with no other choice. Doing things at a driver development level I am willing to risk, within reason. I wiped Windows Vista from the laptop, so can't test in Vista. I did keep the emergency restore partition, and might be able to restore Windows Vista to some portion of the disk (or more likely - have it wipe my Linux install and have to restore from a backup). If that was needed for testing purposes. I have not seen a response to my offer to help develop a driver for this and know scratch about fingerprint readers, so I really have no good answer for your question. I will attempt one anyway. Having pictures of the guts of the device would be a starting point. That would show the chip(s) involved and then getting the specs for the chips involved would be the next stage. Getting the specs for the chip(s), may be the tough part. It is essential to find out the capabilities of the chip(s). Once that is known writing the driver should be relatively easy. Brian On Tue, April 26, 2011 4:33 am, Carlos Vedovatti wrote: > Hi Brian, > > ... > I wanted to ask you if you have any idea > of what information is needed from the Validity Inc. to develop a > driver? or we just wait until someone comes with a idea, information, > etc.? > > Basically I wrote to Validity Inc. to see if they could provide > something ... > > Carlos Vedovatti > From lukas.karas at centrum.cz Tue Apr 26 21:15:06 2011 From: lukas.karas at centrum.cz (=?utf-8?q?Luk=C3=A1=C5=A1_Karas?=) Date: Tue, 26 Apr 2011 22:15:06 +0200 Subject: [fprint] Digital Persona 138a:0005 In-Reply-To: <266531701a9dfb4e3fd226500c109bd4.squirrel@www.amason.net> References: <266531701a9dfb4e3fd226500c109bd4.squirrel@www.amason.net> Message-ID: <201104262215.06944.lukas.karas@centrum.cz> 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 at 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 brian at 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 at reactivated.net > http://lists.reactivated.net/mailman/listinfo/fprint From brian at amason.net Wed Apr 27 03:51:38 2011 From: brian at amason.net (brian@amason.net) Date: Tue, 26 Apr 2011 21:51:38 -0500 Subject: [fprint] Digital Persona 138a:0005 In-Reply-To: <201104262215.06944.lukas.karas@centrum.cz> References: <266531701a9dfb4e3fd226500c109bd4.squirrel@www.amason.net> <201104262215.06944.lukas.karas@centrum.cz> Message-ID: <705fb4975558c1b1032827e762b1ff19.squirrel@www.amason.net> 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 at 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 brian at 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 at reactivated.net >> http://lists.reactivated.net/mailman/listinfo/fprint > > From carlos.vedovatti at googlemail.com Wed Apr 27 20:11:33 2011 From: carlos.vedovatti at googlemail.com (Carlos Vedovatti) Date: Wed, 27 Apr 2011 21:11:33 +0200 Subject: [fprint] Digital Persona 138a:0005 In-Reply-To: <705fb4975558c1b1032827e762b1ff19.squirrel@www.amason.net> Message-ID: <1303931494.2836.329.camel@Linux> 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.reactivated.net/pipermail/fprint/attachments/20110427/3ab01831/attachment.html From rajendra.racha at gmail.com Thu Apr 28 09:25:50 2011 From: rajendra.racha at gmail.com (Rajendra prasad) Date: Thu, 28 Apr 2011 13:55:50 +0530 Subject: [fprint] Cross compiling libfprint for ARM Linux In-Reply-To: References: Message-ID: Hi to all. While running enroll application im getting below error. Pls advice me. Upekts:warning [initsm_read_msg_response_cb] expected responce to subcmd 0x08, got response to f0 in state 9 enrolled failed with error -22. On 4/20/11, Rajendra prasad wrote: > Hi. > > This is Rajendra. I am trying to cross compile the libfprint libraries > for arm architecture. > > But while configuring the library im getting configure error as > glib-2.0 not found. > > So i downloaded the glib source from net. But while cross compiling > glib command im getting error as follows. > That error as follows. > -->make > gatomic.c:607: Error: no such instruction: swp %eax,%eax,[%edx]. > > So ple suggest me, what could be the problem for getting above errror. > And is it possible to compile libfprint witout glib-2.0. > > Thanking you. > > -- > Sent from my mobile device > > _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ > > Best Regards > R.R.Prasad > +91-7893535148 > -- Sent from my mobile device _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Best Regards R.R.Prasad +91-7893535148 From carlos.vedovatti at googlemail.com Thu Apr 28 09:47:20 2011 From: carlos.vedovatti at googlemail.com (Carlos Vedovatti) Date: Thu, 28 Apr 2011 10:47:20 +0200 Subject: [fprint] Digital Persona 138a:0005 In-Reply-To: Message-ID: <1303980440.3098.33.camel@Linux> So I found more information from Validity Inc. The sensor is NOT encrypted and keep insisting that the patch for the VFS101 may work on the VFS301. -- Carlos Vedovatti Before printing, think about the environment. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.reactivated.net/pipermail/fprint/attachments/20110428/583e9566/attachment.html From brian at amason.net Thu Apr 28 14:47:11 2011 From: brian at amason.net (brian@amason.net) Date: Thu, 28 Apr 2011 08:47:11 -0500 Subject: [fprint] Digital Persona 138a:0005 In-Reply-To: <1303980440.3098.33.camel@Linux> References: <1303980440.3098.33.camel@Linux> Message-ID: Has anyone examined the debug info on the driver? I note that there appears to be a version of the Validity driver out that includes the patch for the VFS101. So it should not be necessary to patch it anymore. This release came out a few weeks ago, from what I can tell. I will have to compile and test the driver, and will report my results. Hopefully there is some good debugging info. Sounds like we may be close, but will need to do some tweaking on the driver. Also, I can confirm that the Digital Persona identification comes from the usb.ids file. First I manually alterered the file, and later I upgraded it running the command "update-usbids". I'm running a Mepis distro. so debian based. Not sure if this works in every distro. Gotta love the Linux fragmentation. Just not as bad as Unix was. Brian On Thu, April 28, 2011 3:47 am, Carlos Vedovatti wrote: > So I found more information from Validity Inc. The sensor is NOT > encrypted and keep insisting that the patch for the VFS101 may work on > the VFS301. > -- > Carlos Vedovatti > > From n.shatokhin at gmail.com Fri Apr 29 00:04:25 2011 From: n.shatokhin at gmail.com (Nicholas Shatokhin) Date: Fri, 29 Apr 2011 02:04:25 +0300 Subject: [fprint] fprintd dbus Message-ID: How to use dbus with libfprint? I type "qdbus" in console for list of available dbus services, but i can't found fprintd there. When I'm trying run fprintd-* commands from console, I receive: robotex at robotex-laptop:~$ fprintd-list robotex list_devices failed: Launch helper exited with unknown return code 1 robotex at robotex-laptop:~$ fprintd-enroll list_devices failed: Launch helper exited with unknown return code 1 robotex at robotex-laptop:~$ fprintd-verify list_devices failed: Launch helper exited with unknown return code 1 robotex at robotex-laptop:~$ fprintd-delete Usage: fprintd-delete [usernames...] robotex at robotex-laptop:~$ fprintd-delete robotex list_devices failed: Launch helper exited with unknown return code 1 Libfprint API working good. -- ?? ???????????? ????????????? ??????? ??????????? ????? Opera: http://www.opera.com/mail/ From hadess at hadess.net Fri Apr 29 03:45:44 2011 From: hadess at hadess.net (Bastien Nocera) Date: Fri, 29 Apr 2011 03:45:44 +0100 Subject: [fprint] fprintd dbus In-Reply-To: References: Message-ID: <1304045150.13362.26.camel@novo.hadess.net> On Fri, 2011-04-29 at 02:04 +0300, Nicholas Shatokhin wrote: > How to use dbus with libfprint? > > I type "qdbus" in console for list of available dbus services, but i can't > found fprintd there. > > When I'm trying run fprintd-* commands from console, I receive: > > robotex at robotex-laptop:~$ fprintd-list robotex > list_devices failed: Launch helper exited with unknown return code 1 That means that fprintd failed to launch properly. Launch it by hand and see why it fails (don't forget to launch it as root, as that's the user it's supposed to run as). Cheers From brian at amason.net Fri Apr 29 10:03:42 2011 From: brian at amason.net (brian@amason.net) Date: Fri, 29 Apr 2011 04:03:42 -0500 Subject: [fprint] Digital Persona 138a:0005 In-Reply-To: <1303931494.2836.329.camel@Linux> References: <1303931494.2836.329.camel@Linux> Message-ID: <090b11265b6c3cc78585f573d589453c.squirrel@www.amason.net> 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 From kunal.gangakhedkar at gmail.com Fri Apr 29 11:32:39 2011 From: kunal.gangakhedkar at gmail.com (Kunal Gangakhedkar) Date: Fri, 29 Apr 2011 16:02:39 +0530 Subject: [fprint] Digital Persona 138a:0005 In-Reply-To: <090b11265b6c3cc78585f573d589453c.squirrel@www.amason.net> References: <1303931494.2836.329.camel@Linux> <090b11265b6c3cc78585f573d589453c.squirrel@www.amason.net> Message-ID: <201104291602.40415.kunal.gangakhedkar@gmail.com> On Friday 29 Apr 2011 2:33:42 pm brian at 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 From brian at amason.net Fri Apr 29 14:22:02 2011 From: brian at amason.net (brian@amason.net) Date: Fri, 29 Apr 2011 08:22:02 -0500 Subject: [fprint] Digital Persona 138a:0005 In-Reply-To: <201104291602.40415.kunal.gangakhedkar@gmail.com> References: <1303931494.2836.329.camel@Linux> <090b11265b6c3cc78585f573d589453c.squirrel@www.amason.net> <201104291602.40415.kunal.gangakhedkar@gmail.com> Message-ID: <41b510a866d608fe09239bdcfc2b7fc6.squirrel@www.amason.net> > 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 From brian at amason.net Fri Apr 29 16:30:53 2011 From: brian at amason.net (brian@amason.net) Date: Fri, 29 Apr 2011 10:30:53 -0500 Subject: [fprint] Digital Persona 138a:0005 In-Reply-To: <201104291602.40415.kunal.gangakhedkar@gmail.com> References: <1303931494.2836.329.camel@Linux> <090b11265b6c3cc78585f573d589453c.squirrel@www.amason.net> <201104291602.40415.kunal.gangakhedkar@gmail.com> Message-ID: <20b2a235c89ed6a35c6bb00dafc22367.squirrel@www.amason.net> 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 brian at 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 > >