Mariusz Ciszewski | 23 Mar 12:43 2014
Picon

Fwd: MiniPC with USB fingerprint as logging on terminal for smart home

Dear All

After my previous experiences I think you are my last chance to find sollution in my topic:

http://ubuntuforums.org/showthread.php?t=2212639&p=12964496#post12964496

http://darkblue.homeip.net/fingerprint/Forum/topic.php?TopicId=376&Posts=0

I'm searching for sollution to check the person after she or he came into home. I found it would be simplest for me using any mini PC and linux logon using fingerprint action (USB fingerprint reader connected). Then - script placed in autostart (executed if user logged succesfully). After script is executed then logged out uotomatically. And fingerprint system is ready again for check next person coming into home.

Please help, or please let me know who should I ask for help.

It strange but as I experienced - to find programist knowing fingerprint issues for linux is almost impossible.

For more details please check:
http://darkblue.homeip.net/fingerprint/Forum/topic.php?TopicId=376&Posts=0

or please contact me here or directly.

Thank you very much.
Best regards

Mariusz Ciszewski

_______________________________________________
fprint mailing list
fprint <at> lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/fprint
Martin Hejnfelt | 20 Mar 21:52 2014
Picon

EgisTec ES603 Error -22

Hi,

I'm working with a EgisTec ES603 (1c7a:0603). I am using the current
HEAD from anarsoul git repository.

When I try to enroll or identify (with async methods), sometimes it
works, but most of the time I get a result of -22 (EINVAL) in the
callback. I tried debugging it, and it seems the error comes in the
sanitize_img function (imgdev.c line 93) from a check of the image
height (line 106-111, error comes in 110). By enabling logging, I can
see that during an enroll sequence, my callback function is called twice
from one call. The first call is good, where I get an FP_ENROLL_PASS
swipe and the function exits as it should. It then immediately gets
called again, however this is the one that fails with error -22.

I then enabled logging in the library, and it seems that it detects the
finger twice or something, and then removes some empty lines that end up
with a blank image. Here's some debug output to gaze upon:

drv:debug [__ssm_call_handler] 0x7fbae0000910 entering state 13
drv:debug [__ssm_call_handler] 0x7fbae0000910 entering state 12
drv:debug [__ssm_call_handler] 0x7fbae0000910 entering state 13
fp:debug [fpi_imgdev_report_finger_status] finger on sensor
drv:debug [fpi_ssm_mark_completed] 0x7fbae0000910 completed with status
0
drv:debug [__ssm_call_handler] 0x7fbae0000a10 entering state 0
etes603:debug [m_capture_state] Capturing a fingerprint...
drv:debug [__ssm_call_handler] 0x7fbae0000a10 entering state 1
drv:debug [__ssm_call_handler] 0x7fbae0000a10 entering state 2
drv:debug [__ssm_call_handler] 0x7fbae0000a10 entering state 3
etes603:debug [m_capture_state] Capturing a 1st frame...
drv:debug [__ssm_call_handler] 0x7fbae0000a10 entering state 4
drv:debug [__ssm_call_handler] 0x7fbae0000a10 entering state 5
etes603:debug [m_capture_state] Capturing a 2nd frame...
drv:debug [__ssm_call_handler] 0x7fbae0000a10 entering state 4
drv:debug [__ssm_call_handler] 0x7fbae0000a10 entering state 5
etes603:debug [process_remove_fp_end] Removing 354 empty lines from
image
etes603:debug [process_remove_fp_end] Removing 0 empty lines from image
fp:debug [fpi_img_new] length=163840
etes603:debug [m_capture_state] Sending the raw fingerprint image
(0x640)
fp:debug [fpi_imgdev_image_captured] 
fp:debug [fpi_img_detect_minutiae] minutiae scan completed in 0.057886
secs
fp:debug [fpi_img_detect_minutiae] detected 97 minutiae
fp:debug [print_data_new] driver=12 devtype=0000
fp:debug [print_data_new] driver=12 devtype=0000
fp:debug [fpi_imgdev_report_finger_status] finger removed
fp:debug [fpi_imgdev_report_finger_status] reporting enroll result
async:debug [fpi_drvcb_enroll_stage_completed] result 3
Enroll stage callback
Enrolling 41EB2014-617A-4953-8283-0B9DD01653FB
System output: Accepted, scan finger again... (1/5)
drv:debug [fpi_ssm_mark_completed] 0x7fbae0000a10 completed with status
0
etes603:debug [m_capture_complete] Device is still active, restarting
finger detection
drv:debug [__ssm_call_handler] 0x7fbae0000a10 entering state 0
drv:debug [__ssm_call_handler] 0x7fbae0000a10 entering state 1
drv:debug [__ssm_call_handler] 0x7fbae0000a10 entering state 2
drv:debug [__ssm_call_handler] 0x7fbae0000a10 entering state 3
drv:debug [__ssm_call_handler] 0x7fbae0000a10 entering state 4
drv:debug [__ssm_call_handler] 0x7fbae0000a10 entering state 5
drv:debug [__ssm_call_handler] 0x7fbae0000a10 entering state 6
drv:debug [__ssm_call_handler] 0x7fbae0000a10 entering state 7
drv:debug [__ssm_call_handler] 0x7fbae0000a10 entering state 8
drv:debug [__ssm_call_handler] 0x7fbae0000a10 entering state 9
drv:debug [__ssm_call_handler] 0x7fbae0000a10 entering state 10
drv:debug [__ssm_call_handler] 0x7fbae0000a10 entering state 11
drv:debug [__ssm_call_handler] 0x7fbae0000a10 entering state 12
drv:debug [__ssm_call_handler] 0x7fbae0000a10 entering state 13
fp:debug [fpi_imgdev_report_finger_status] finger on sensor
drv:debug [fpi_ssm_mark_completed] 0x7fbae0000a10 completed with status
0
drv:debug [__ssm_call_handler] 0x7fbae000afc0 entering state 0
etes603:debug [m_capture_state] Capturing a fingerprint...
drv:debug [__ssm_call_handler] 0x7fbae000afc0 entering state 1
drv:debug [__ssm_call_handler] 0x7fbae000afc0 entering state 2
drv:debug [__ssm_call_handler] 0x7fbae000afc0 entering state 3
etes603:debug [m_capture_state] Capturing a 1st frame...
drv:debug [__ssm_call_handler] 0x7fbae000afc0 entering state 4
drv:debug [__ssm_call_handler] 0x7fbae000afc0 entering state 5
etes603:debug [m_capture_state] Capturing a 2nd frame...
drv:debug [__ssm_call_handler] 0x7fbae000afc0 entering state 4
drv:debug [__ssm_call_handler] 0x7fbae000afc0 entering state 5
etes603:debug [process_remove_fp_end] Removing 498 empty lines from
image
etes603:debug [process_remove_fp_end] Removing 496 empty lines from
image
fp:debug [fpi_img_new] length=0
etes603:debug [m_capture_state] Sending the raw fingerprint image (0x0)
fp:debug [fpi_imgdev_image_captured] 
fp:error [sanitize_image] no image height assigned
fp:debug [fpi_imgdev_report_finger_status] finger removed
fp:debug [fpi_imgdev_report_finger_status] reporting enroll result
async:debug [fpi_drvcb_enroll_stage_completed] result -22
Enroll stage callback
Enrolling 41EB2014-617A-4953-8283-0B9DD01653FB
Enroll failed with error -22
System output: Enroll error!
async:debug [fp_async_enroll_stop] 
etes603:debug [dev_deactivate] deactivating
etes603:debug [m_exit_start] Switching device to idle mode
drv:debug [__ssm_call_handler] 0x7fbae0000a10 entering state 0
drv:debug [fpi_ssm_mark_completed] 0x7fbae000afc0 completed with status
0
etes603:debug [m_capture_complete] And it's over.
drv:debug [__ssm_call_handler] 0x7fbae0000a10 entering state 1
drv:debug [fpi_ssm_mark_completed] 0x7fbae0000a10 completed with status
0
etes603:debug [m_exit_complete] The device is now in idle state
fp:debug [fpi_imgdev_deactivate_complete] 
async:debug [fpi_drvcb_enroll_stopped] 

This comes from a single swipe...

Enroll stage callback
Enrolling 41EB2014-617A-4953-8283-0B9DD01653FB
System output: Accepted, scan finger again... (1/5)

is the output from my callback function, and as you can see it gets
called twice from a single scan:

Enroll stage callback
Enrolling 41EB2014-617A-4953-8283-0B9DD01653FB
Enroll failed with error -22
System output: Enroll error!

Now the code works fine with the integrated UPEK (147e:2016) in my
laptop, so any clues here?

Thanks in advance!

Kind regards,
Martin Hejnfelt
Vasily Khoruzhick | 20 Mar 09:04 2014
Picon

Re: Call for testing: UPEK 147e:1001, AES1660, AES1610, AES2501, AES2550, AES2810, AES2660

Hi Julian,

According to log, it looks like one control transfer (write reg) of
deinit sequence timed out. Does it happen all the time?

Please note, that with latest changes all imaging devices do 5 scans
for enrollment.

Regards
Vasily

On Thu, Mar 20, 2014 at 9:13 AM, Julian Sikorski <belegdol <at> gmail.com> wrote:
> W dniu 16.03.2014 11:45, Vasily Khoruzhick pisze:
>> Hi to all fingerprint scanner users,
>>
>> It's another call for libfprint testing.
>>
>> Good news to all UPEK 147e:1001 users - I've added support for that
>> device into upeksonly driver - so it worth testing. It also may work
>> for 147e:1002 device - just try to add its USB IDs into upeksonly.c
>> and use UPEKSONLY_1001 variant for it.
>>
>> Also I've improved image assembling utilities for all AuthenTec
>> scanners, so now match rate is a bit better for AES1660 scanner - so
>> all AES1660 are encouraged to test my changes as well.
>>
>> All changes are pushed into master branch of
>> git://github.com/anarsoul/libfprint.git repo.
>>
>> To obtain the code do:
>>
>> git clone git://github.com/anarsoul/libfprint.git
>>
>> Use instructions from [1] to compile and test it. Thanks!
>>
>> Regards,
>> Vasily
>>
>> P.S. PLEASE KEEP FPRINT MAILLIST IN CC!
>>
>> [1] http://lists.freedesktop.org/archives/fprint/2012-November/000330.html
>>
> Hello,
>
> 147e:1001 does not seem to be working here. When I open fprint_demo and
> pick a finger to enroll, the child window shows nothing for a while.
> When I scan my finger regardless, a scan will appear at some point, but
> with a message "enrollment failed due to bad scan data, press cancel to
> continue". Logs attached.
>
> Best regards,
> Julian
Vasily Khoruzhick | 16 Mar 11:45 2014
Picon

Call for testing: UPEK 147e:1001, AES1660, AES1610, AES2501, AES2550, AES2810, AES2660

Hi to all fingerprint scanner users,

It's another call for libfprint testing.

Good news to all UPEK 147e:1001 users - I've added support for that
device into upeksonly driver - so it worth testing. It also may work
for 147e:1002 device - just try to add its USB IDs into upeksonly.c
and use UPEKSONLY_1001 variant for it.

Also I've improved image assembling utilities for all AuthenTec
scanners, so now match rate is a bit better for AES1660 scanner - so
all AES1660 are encouraged to test my changes as well.

All changes are pushed into master branch of
git://github.com/anarsoul/libfprint.git repo.

To obtain the code do:

git clone git://github.com/anarsoul/libfprint.git

Use instructions from [1] to compile and test it. Thanks!

Regards,
Vasily

P.S. PLEASE KEEP FPRINT MAILLIST IN CC!

[1] http://lists.freedesktop.org/archives/fprint/2012-November/000330.html
Anatoly Thernytskyi | 21 Feb 13:13 2014
Picon

(no subject)

Hello, I have this problem http://lists.freedesktop.org/archives/fprint/2012-April/000137.html
with fingeprint digitalPersona  U.are.U 4000B. Please, help me. I don't have any ideas how fix this bug. Thank you very much.
_______________________________________________
fprint mailing list
fprint <at> lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/fprint
Fabian Zaremba | 18 Jan 06:32 2014
Picon

Egistec S801U

Hello,

I found a repository on github containing libfprint support for the 
Egistec S801U (ID 1c7a:0801 LighTuning Technology Inc. Fingerprint Reader):
https://github.com/lielfr/Libfprint-for-Egistec-S801U

However, as this seems to be based on a 0.4.x branch I rebased this on 
the current git repo for personal use.

I was able to get this working using an additional patch against 
libfprint imgdev.c found in Bug 30287 - 
https://bugs.freedesktop.org/show_bug.cgi?id=30287 - without this patch 
the device would not accept a second scan after the first failed but 
instead loop in verify_retry_scan until timeout.

You can find my patchset against current git master (commit 35e356f6) here:
https://nf-design.eu/cloud/d/3a191bd2b2/

Some parts of it are still a bit crude, like inclusion of the driver in 
core.c or libfprint/Makefile.am. Additionally, I just took the first 
available driver id 19.

Any chance these patches could get into upstream?

Thank you,
Fabian Zaremba
Nikolay Amiantov | 12 Jan 18:44 2014
Picon

vfs5011 support

Hello,
There is a working patchset for fprint providing vfs5011 support (not mine):
https://github.com/ars3niy/fprint_vfs5011
It supports at least three different sensors -- I've just made a pull request which enables support of the third. Any hope of getting this into upstream?

Thanks,
Nikolay Amiantov.
_______________________________________________
fprint mailing list
fprint <at> lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/fprint
BigSmoke | 10 Jan 14:57 2014
Picon

Fwd: libfingerprint success report for Lenovo T61

Hi,

I just subscribed because I want to report that libfingerprint is working for my device.

VendorID: 0483
ProductID: 2016

Laptop is a Lenovo T61.

Thank you guys for the great work on this project! You've just made my life a little bit easier. :-)

Cheers,
Rowan

_______________________________________________
fprint mailing list
fprint <at> lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/fprint
Fralaltro | 5 Jan 19:24 2014
Picon

Broadcom BCM5880

Hi guys,

I don't know if I'm writing in the right place.

I have a new Dell laptop with a Broadcom BCM5880 with fingerprint reader and it's not supported on Linux.

$ lsusb
Bus 001 Device 002: ID 8087:8000 Intel Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 004: ID 0a5c:5801 Broadcom Corp. BCM5880 Secure Applications Processor with fingerprint swipe sensor
Bus 002 Device 003: ID 1bcf:2985 Sunplus Innovation Technology Inc. 
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

I'm able to sniff USB packets in Windows through USBPcap with Wireshark.

Would you be interested in trying to create a driver for this?

It seems to be quite a common chipset in many laptops.

I would love to help, possibly learning something from all this.

Let me know.

Best,

Fran
_______________________________________________
fprint mailing list
fprint <at> lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/fprint
pietrek -- | 1 Dec 17:03 2013
Picon

Re: aes3400


I used data from windows to improve a bit quality of image, but enroll 
still returns FP_ENROLL_PASS or FP_ENROLL_RETRY.
Is this quality still not good enough?
     Piotr jarosz

Attachment (aes3400.c): text/x-csrc, 5887 bytes
_______________________________________________
fprint mailing list
fprint <at> lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/fprint
pietrek -- | 8 Dec 14:30 2013
Picon

aes3400

Hi,
thanks for your help. Now my AES3400 works.
I used functions
r = fp_dev_img_capture(capture_device, 0, &img);
r = fpi_img_to_print_data( (struct fp_img_dev *) &capture_device /* ugly 
hack ;pp */,img,&enrolled_print);
to enroll image and
r = fpi_img_compare_print_data_to_gallery(data, gal, tolerance, &n);
to verify it. Could you default export those functions default?
I found how to do contionous scanning on my aes3400( { 0x81, 0x05 } ),
but if this register isn't cleaned after scanning reader doesn't stop 
sending scans and usb buffer overflows
so I have to reopen device. Is it possible in this library to write 
register and flush usb buffer after scanning?
I also  attach my driver, could you add it to the library?
     Piotr Jarosz

Attachment (aes3400.c): text/x-csrc, 5804 bytes
_______________________________________________
fprint mailing list
fprint <at> lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/fprint

Gmane