Arch Linux

miro279

Member

Registered: 2010-10-02

Posts: 156

[SOLVED] libfprint-0.4.0-1 in debug mode (x86_64)?

After installing a new version of libfprint some days ago I get a lot of debug information when suing:

 
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 upekts supports USB device 0483:2016
fp:debug [find_supporting_driver] selected driver upekts supports USB device 0483:2016
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
fp:debug [load_from_file] from /root/.fprint/prints/0001/00000000/7
fp:debug [fp_print_data_from_data] buffer size 226
fp:debug [print_data_new] length=216 driver=01 devtype=0000
Scan right index finger on UPEK TouchStrip
sync:debug [fp_verify_finger_img] to be handled by upekts
async:debug [fp_async_verify_start] 
drv:debug [__ssm_call_handler] 0x712280 entering state 0
drv:debug [__ssm_call_handler] 0x7122c0 entering state 0
drv:debug [__ssm_call_handler] 0x7122c0 entering state 1
upekts:debug [__handle_incoming_msg] A=03 B=00 len=5
upekts:debug [__handle_incoming_msg] cmd 3 from device to driver
drv:debug [__ssm_call_handler] 0x7122c0 entering state 2
upekts:debug [alloc_send_cmdresponse_transfer] seq=04 len=8
upekts:debug [initsm_send_msg_cb] state 2 completed
drv:debug [__ssm_call_handler] 0x7122c0 entering state 3
upekts:debug [__handle_incoming_msg] A=05 B=00 len=1
upekts:debug [__handle_incoming_msg] cmd 5 from device to driver
drv:debug [__ssm_call_handler] 0x7122c0 entering state 4
upekts:debug [alloc_send_cmd28_transfer] seq=00 subcmd=06 with 1 bytes of data
upekts:debug [initsm_send_msg_cb] state 4 completed
drv:debug [__ssm_call_handler] 0x7122c0 entering state 5

and so on..
The good thing is that the driver is working again which it didn't in the previous version from arch  repository. Still I'd prefere not to get this console output everytime. Is there a switch I somewhere or is this compiled in the package itself?

Last edited by miro279 (2011-11-15 05:44:58)

miro279

Member

Registered: 2010-10-02

Posts: 156

Re: [SOLVED] libfprint-0.4.0-1 in debug mode (x86_64)?

solved in libfprint-0-4-0-2