Lenovo Yoga 6-13ALC6 fingerprint reader support

Hey Fedora folks, I’ve been trying to get the fingerprint reader on my laptop working but I’m not sure if it is supported. I have no idea what the hardware for it is specifically, as the Lenovo support site has two different manufacturers of fingerprint reader hardware listed as being used in this model (Goodix and Synaptics) and I’m not sure which one is in my laptop.

I checked and I do have libfprint installed and it is at version 1.94.4-2.fc37.x86_64.

So I guess I have a couple of questions here then: first would be how I can tell the exact hardware being used in the laptop, second would be once I am able to find that how can I check if it is supported?

If it is not supported, could someone also point me in the right direction for where to request that support be added for this hardware?

For reference, this is the exact laptop model I’m using: https://pcsupport.lenovo.com/us/en/products/laptops-and-netbooks/yoga-series/yoga-6-13alc6/82nd

I have found the exact fingerprint model, so I guess my first question has been answered. I checked on the libfprint documentation and it seems this exact model is still listed as unsupported however there is active work being done on it with an experimental driver for this available as of 2 months ago. Hopefully this means it will hit supported status soon.

Device for reference:

[user@host ~]$ sudo lsusb -vd 27c6:55b4

Bus 003 Device 002: ID 27c6:55b4 Shenzhen Goodix Technology Co.,Ltd. Fingerprint Reader
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass          239 Miscellaneous Device
  bDeviceSubClass         2 
  bDeviceProtocol         1 Interface Association
  bMaxPacketSize0        64
  idVendor           0x27c6 Shenzhen Goodix Technology Co.,Ltd.
  idProduct          0x55b4 Fingerprint Reader
  bcdDevice            1.00
  iManufacturer           1 Generic
  iProduct                2 Goodix FingerPrint Device
  iSerial                 0 
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength       0x0020
    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           2
      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     0x0200  1x 512 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     0x0200  1x 512 bytes
        bInterval               0
Device Qualifier (for other device speed):
  bLength                10
  bDescriptorType         6
  bcdUSB               2.00
  bDeviceClass          239 Miscellaneous Device
  bDeviceSubClass         2 
  bDeviceProtocol         1 Interface Association
  bMaxPacketSize0        64
  bNumConfigurations      1
Device Status:     0x0000
  (Bus Powered)

The chipset info is there. 27c6:55b4
Thus the info to use when searching for a driver is there.

Yes I know, I said this in my comment below the main post if you read the whole thing. I was able to find the hardware info and this exact fingerprint reader is marked as unsupported in their documentation. I even linked the exact issue tracking this hardware, and there is an experimental driver in development for it.