Mackenzie Morgan wrote: > On Mon, 2008-11-17 at 01:11 +0100, Martin Weinelt wrote: > >> Hello, >> >> well I don't believe so, as it is not working with upeksonly right now >> and VMWare shows me as the title for the Adapter (when connecting it): >> UPEK Biometric Coprocessor. >> >> So is VMWare lying about this? >> > > If you have 147e:2016, it's the sensor-only one and would be expected to > work with upeksonly. I don't know how recent of libfprint you're using > though. If you're on 0.0.6, it doesn't have upeksonly at all. I don't > know what to debug, I just saw that in that post you mentioned using > upekts with 147e:2016, which is an impossible combination. > > Here is some more recent --enable-debug-log activated output of me trying to enroll my index finger via fprint_demo
--- fprint_demo 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 [find_supporting_driver] driver upeksonly supports USB device 147e:2016 async:debug [fp_async_dev_open] ** Message: now monitoring fd 4 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] 0xc9f030 entering state 0 upeksonly:debug [write_regs_iterate] set 49=00 drv:debug [fpi_ssm_mark_aborted] error 4 from state 0 drv:debug [fpi_ssm_mark_completed] 0xc9f030 completed with status 4 fp:debug [fpi_imgdev_activate_complete] status 4 async:debug [fpi_drvcb_enroll_started] status 4 async:debug [fpi_drvcb_enroll_started] adjusted to -4 async:debug [fp_async_enroll_stop] upeksonly:debug [deactivate_done] fp:debug [fpi_imgdev_deactivate_complete] async:debug [fpi_drvcb_enroll_stopped] async:debug [fp_async_enroll_stop] fp:error [img_dev_enroll_stop] BUG at imgdev.c:420 upeksonly:debug [deactivate_done] Speicherzugriffsfehler speicherzugriffsfehler = memory access error _______________________________________________ fprint mailing list [email protected] http://lists.reactivated.net/mailman/listinfo/fprint
