My system is Lucid 32bit with fprint_demo v0.4 and libfprint.debug0 (0.1.0~pre2-1~ppa7~lucid1) installed from https://launchpad.net/~fingerprint/+archive/fprint The fingerprint device is U.are.U 4000, Model No. URU4S-U1, Revision 101, external connected to USB. There is also a built-in device from UPEK in that machine. The output from "lsusb" is:
Bus 005 Device 003: ID 0483:2016 SGS Thomson Microelectronics Fingerprint Reader Bus 005 Device 002: ID 0a5c:2110 Broadcom Corp. Bluetooth Controller Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 004: ID 05ba:0007 DigitalPersona, Inc. Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub If I run fprint_demo and chose the URU4000 for enrollment, the lights of the URU4000 are switched on but a finger-touch isn't recognized. After pressing the "quit"-button fprint_demo exits and the lights stay switched on. The device works on Windows XP with the software coming on their driver CD. Here is the debug output from libfprint.debug0: ------------------- fp:debug [fp_init] fp:debug [register_driver] registered driver upekts 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 [find_supporting_driver] driver upekts supports USB device 0483:2016 fp:debug [find_supporting_driver] driver uru4000 supports USB device 05ba:0007 async:debug [fp_async_dev_open] ** Message: now monitoring fd 10 async:debug [fpi_drvcb_open_complete] status 0 async:debug [fp_async_enroll_start] starting enrollment fp:debug [generic_acquire_start] action 1 drv:debug [__ssm_call_handler] 0x90db0c0 entering state 0 uru4000:debug [sm_read_reg] read reg 7 uru4000:debug [sm_read_reg_cb] reg value 85 drv:debug [__ssm_call_handler] 0x90db0c0 entering state 1 drv:debug [__ssm_call_handler] 0x90db0c0 entering state 2 drv:debug [__ssm_call_handler] 0x9184308 entering state 0 uru4000:debug [sm_set_hwstat] set 05 drv:debug [__ssm_call_handler] 0x9184308 entering state 1 uru4000:debug [sm_read_reg] read reg 7 uru4000:debug [irq_handler] recv irq type 56aa uru4000:debug [irq_handler] ignoring interrupt uru4000:debug [sm_read_reg_cb] reg value 1 drv:debug [__ssm_call_handler] 0x9184308 entering state 2 drv:debug [fpi_ssm_mark_completed] 0x9184308 completed with status 0 drv:debug [__ssm_call_handler] 0x90db0c0 entering state 3 uru4000:debug [sm_set_hwstat] set 81 drv:debug [__ssm_call_handler] 0x90db0c0 entering state 4 drv:debug [__ssm_call_handler] 0x91e0ce0 entering state 0 drv:debug [__ssm_call_handler] 0x91e0ce0 entering state 1 uru4000:debug [fwfixer_run_state] looking for encryption byte at 510 uru4000:debug [fwfixer_read_cb] data: 21 10 01 drv:debug [__ssm_call_handler] 0x91e0ce0 entering state 1 uru4000:debug [fwfixer_run_state] looking for encryption byte at 62d uru4000:debug [fwfixer_read_cb] data: 0f e0 f2 drv:debug [__ssm_call_handler] 0x91e0ce0 entering state 1 uru4000:debug [fwfixer_run_state] looking for encryption byte at 792 uru4000:debug [fwfixer_read_cb] data: ff 07 41 uru4000:debug [fwfixer_read_cb] using offset 792 drv:debug [__ssm_call_handler] 0x91e0ce0 entering state 2 uru4000:debug [fwfixer_run_state] encryption is already disabled drv:debug [fpi_ssm_mark_completed] 0x91e0ce0 completed with status 0 drv:debug [__ssm_call_handler] 0x90db0c0 entering state 5 drv:debug [__ssm_call_handler] 0x90d1ec0 entering state 0 drv:debug [__ssm_call_handler] 0x90d1ec0 entering state 1 uru4000:debug [sm_set_hwstat] set 01 drv:debug [__ssm_call_handler] 0x90d1ec0 entering state 2 uru4000:debug [sm_read_reg] read reg 7 uru4000:debug [sm_read_reg_cb] reg value 0 drv:debug [__ssm_call_handler] 0x90d1ec0 entering state 3 drv:debug [fpi_ssm_mark_completed] 0x90d1ec0 completed with status 0 drv:debug [__ssm_call_handler] 0x90db0c0 entering state 6 poll:debug [fpi_timeout_add] in 300ms poll:debug [get_next_timeout_expiry] next timeout in 0.299993s poll:debug [get_next_timeout_expiry] next timeout in 0.299959s poll:debug [get_next_timeout_expiry] next timeout in 0.289200s uru4000:debug [irq_handler] recv irq type 56aa drv:debug [__ssm_call_handler] 0x90db0c0 entering state 7 poll:debug [fpi_timeout_cancel] drv:debug [fpi_ssm_mark_completed] 0x90db0c0 completed with status 0 fp:debug [fpi_imgdev_activate_complete] status 0 async:debug [fpi_drvcb_enroll_started] status 0 uru4000:debug [irq_handler] recv irq type 0200 fp:debug [fpi_imgdev_report_finger_status] finger removed fp:debug [fpi_imgdev_report_finger_status] ignoring status report WAITING FOR FINGER-TOUCH HERE AFTER SOME SECONDS CLICKED QUIT-BUTTON async:debug [fp_async_enroll_stop] drv:debug [__ssm_call_handler] 0x917eb68 entering state 0 uru4000:debug [sm_set_mode] mode 00 drv:debug [__ssm_call_handler] 0x917eb68 entering state 1 uru4000:debug [sm_set_hwstat] set 80 drv:debug [fpi_ssm_mark_completed] 0x917eb68 completed with status 0 uru4000:debug [irq_handler] cancelled fp:debug [fpi_imgdev_deactivate_complete] async:debug [fpi_drvcb_enroll_stopped] sync:debug [fp_dev_close] async:debug [fpi_drvcb_close_complete] ** Message: no longer monitoring fd 10 sync:debug [sync_close_cb] fp:debug [fp_exit] ------------------- Is there any solution for this issue? Regards Wolfgang Ullrich e-Mail: [email protected] _______________________________________________ fprint mailing list [email protected] http://lists.reactivated.net/mailman/listinfo/fprint
