Comment 66 for bug 827669

Revision history for this message
Wolf Geldmacher (wolf-womaro) wrote :

I've got an ASUS BU201LA that also sports a Validity Sensor with Id 0138a:0010.

I got it to work by downloading the source for libfprint from http://www.freedesktop.org/wiki/Software/fprint/Download/ and adding the USBID to the source for vfs5011 like this:

*** vfs5011.c.orig 2015-05-14 19:59:06.489565109 +0200
--- vfs5011.c 2015-05-14 19:59:14.133534986 +0200
***************
*** 992,997 ****
--- 992,998 ----
  }

  static const struct usb_id id_table[] = {
+ { .vendor = 0x138a, .product = 0x0010 /* vfs5010 */ },
   { .vendor = 0x138a, .product = 0x0011 /* vfs5011 */ },
   { .vendor = 0x138a, .product = 0x0017 /* Validity device from Lenovo T440 laptops */ },
   { .vendor = 0x138a, .product = 0x0018 /* one more Validity device */ },

Recompiling results in a libfprint.so.0.0.0 that can be used in the place of the one from the ppa.
Using the fingerprint reader shows the same issues as reported by Ruben in #55 - it works, but
the failure rate when trying to authenticate is quite high.