On Nov 18, 2007 1:48 AM, Daniel Drake <[EMAIL PROTECTED]> wrote: > Try configuring libfprint with --enable-debug-log so that we get more > details of the failure.
Sorry for not posting the details before, I ran as myself and got an error "could not claim interface 0", as root I get a bulk read error -110, is that a timeout from errno.h? The error after read_data with a len of 20, is called from do_init, I guess the write_regv with the init_1 register structure has register values which dont work to init the aes1610 even though the call itself does not appear to fail... In addition to just changing the usb id in aes2501.c, I also changed the dimensions from 192x16 to 128x8 (after seeing the authentec so-called "specs" webpage) , there were some #defines and in some places the 192 value hardcoded. Pasting the log as nonroot and then root: fp:debug [fp_init] fp:debug [register_driver] registered driver upekts fp:debug [register_driver] registered driver uru4000 fp:debug [register_driver] registered driver aes1610 fp:debug [register_driver] registered driver aes4000 fp:debug [register_driver] registered driver upektc fp:debug [find_supporting_driver] driver aes1610 supports USB device 08ff:1600 aes1610:error [dev_init] could not claim interface 0 fp:error [fp_dev_open] device initialisation failed, driver=aes1610 fp:debug [fp_exit] Now as root: fp:debug [fp_init] fp:debug [register_driver] registered driver upekts fp:debug [register_driver] registered driver uru4000 fp:debug [register_driver] registered driver aes1610 fp:debug [register_driver] registered driver aes4000 fp:debug [register_driver] registered driver upektc fp:debug [find_supporting_driver] driver aes1610 supports USB device 08ff:1600 aes1610:debug [write_regv] write 38 regs aes1610:debug [read_data] len=20 aes1610:error [read_data] bulk read error -110 fp:error [fp_dev_open] device initialisation failed, driver=aes1610 fp:debug [fp_exit] -- "Thou shalt not follow the null pointer for at it's end madness and chaos lie." _______________________________________________ fprint mailing list [email protected] http://lists.reactivated.net/mailman/listinfo/fprint
