On Wed, Sep 10, 2014 at 6:05 AM, Nils Ole Tippenhauer <[email protected]> wrote: > Hi list,
Hi Nils, > I get the following info on dmesg when connecting the scanner: > > usb 1-6: New USB device found, idVendor=147e, idProduct=2016 > usb 1-6: New USB device strings: Mfr=1, Product=2, SerialNumber=0 > usb 1-6: Product: Biometric Coprocessor > usb 1-6: Manufacturer: UPEK They're using the same IDs for 3rd device... Weird. > With the default libfprint from Ubuntu 14.04 (20080303git-ubuntu), the > UPEKE2 driver is loaded in fprint-demo. As far as I can tell, UPEKE2 is > line-based, so the driver is probably incorrect. > > I took the latest libfprint git and disabled the UPEKE2 driver. In that > case, the upektc_img is loaded (sometimes referred to as upekts_img). > With that driver, an image is scanned, but it looks garbled. My guess it > that it is still assuming the device is line-based (from a brief look > into the code). Well, I'm surprised that it was able to communicate to this device :) > Can anyone give me some pointers towards getting the 510 working? Join #fprint channel at irc.freenode.org, and I'll try to help you with debugging this issue. Regards Vasily > > Cheers, > Nils _______________________________________________ fprint mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/fprint
