[138a:0090] Validity Sensors fingerprint reader not recognized

Bug #1619589 reported by Nikolay Makhotkin on 2016-09-02
90
This bug affects 20 people
Affects Status Importance Assigned to Milestone
libfprint
Unknown
Wishlist
libfprint (Ubuntu)
Undecided
Unassigned

Bug Description

I have Lenovo Thnikpad X1 Carbon 4th Gen and it has 1382:0090 Validity sensor device.

I use Ubuntu 16.04.

Fprint won't recognize the device. Running fprint_demo, I receive a Status: No devices found message.

$ lsusb -s 001:006 -v

Bus 001 Device 006: ID 138a:0090 Validity Sensors, Inc.
Couldn't open device, some information will be missing
Device Descriptor:
  bLength 18
  bDescriptorType 1
  bcdUSB 2.00
  bDeviceClass 255 Vendor Specific Class
  bDeviceSubClass 16
  bDeviceProtocol 255
  bMaxPacketSize0 8
  idVendor 0x138a Validity Sensors, Inc.
  idProduct 0x0090
  bcdDevice 1.64
  iManufacturer 0
  iProduct 0
  iSerial 1
  bNumConfigurations 1
  Configuration Descriptor:
    bLength 9
    bDescriptorType 2
    wTotalLength 53
    bNumInterfaces 1
    bConfigurationValue 1
    iConfiguration 0
    bmAttributes 0xa0
      (Bus Powered)
      Remote Wakeup
    MaxPower 100mA
    Interface Descriptor:
      bLength 9
      bDescriptorType 4
      bInterfaceNumber 0
      bAlternateSetting 0
      bNumEndpoints 5
      bInterfaceClass 255 Vendor Specific Class
      bInterfaceSubClass 0
      bInterfaceProtocol 0
      iInterface 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x01 EP 1 OUT
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0040 1x 64 bytes
        bInterval 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x81 EP 1 IN
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0040 1x 64 bytes
        bInterval 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x82 EP 2 IN
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0040 1x 64 bytes
        bInterval 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x83 EP 3 IN
        bmAttributes 3
          Transfer Type Interrupt
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0008 1x 8 bytes
        bInterval 4
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x84 EP 4 IN
        bmAttributes 3
          Transfer Type Interrupt
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0010 1x 16 bytes
        bInterval 10

Andreas Pflug (pgadmin-j) wrote :

Same for me. Apparently, all newer Thinkpads are affected.

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in libfprint (Ubuntu):
status: New → Confirmed
albflo (albflo) wrote :

Yes I can confirm this also for the Thinkpad Yoga 260!

Artem Silenkov (asilenkov) wrote :

Sadly protocol is crypted for X1 4Gen so no reverse engineering is possible.
More information is here: https://bugs.freedesktop.org/show_bug.cgi?id=94536

Changed in libfprint:
importance: Unknown → Wishlist
status: Unknown → Confirmed
Sergent Reznov (reznov9185) wrote :

Having the same issue in my T470.

Changed in libfprint:
status: Confirmed → In Progress
Changed in libfprint:
status: In Progress → Unknown
gahrb (gahrb) wrote :

https://github.com/3v1n0/libfprint/blob/vfs0090/README.md

Someone managed to get it working. But only "if the device has been initialized with a Windows VirtualBox (sharing USB) guest or with a Windows installation in bare metal"

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.