Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for 06cb:00bd #72

Open
mariobodemann opened this issue Jun 24, 2019 · 41 comments
Open

Add support for 06cb:00bd #72

mariobodemann opened this issue Jun 24, 2019 · 41 comments

Comments

@mariobodemann
Copy link

@mariobodemann mariobodemann commented Jun 24, 2019

Hey,

I hope I am not overlooking something, but currently I don't seem able to see the fingerprint sensor from the Lenovo T490S supported.

I ran

lsusb | grep -i 06cb

Bus 001 Device 010: ID 06cb:00bd Synaptics, Inc.

and build the prototype from master (8b80cfe):

cd prototype; make; ./prototype

Prototype version 15
No devices found

Can I somehow support you in implementing this reader?

@JohnAZoidberg
Copy link

@JohnAZoidberg JohnAZoidberg commented Jun 24, 2019

You can try to add your device here and see if it does something useful then.

@mariobodemann
Copy link
Author

@mariobodemann mariobodemann commented Jun 24, 2019

Hey thanks,

I added (inspired by the other devices with the same (v?)endor)

{ .vid = 0x06cb, .pid = 0x00bd, .hasLed = 0, .hasBios = -1, .requiresReset = 0, .hasRawOutput = -1 },

and get this result prototype.log ending on Incomplete reverse engineering.

So I fear it didn't do the thing we want it to do?

@t-8ch
Copy link

@t-8ch t-8ch commented Jun 27, 2019

This should end up in one of the next proper versions of libfprint: https://gitlab.freedesktop.org/vincenth/libfprint/tree/synaptics-driver-20190617 (I think)

@Ana06
Copy link

@Ana06 Ana06 commented Jul 7, 2019

I also have a T490s, whose fingerprint doesn't work. What is the state of this? Something I can do to help?

@pblack476
Copy link

@pblack476 pblack476 commented Jul 14, 2019

Is the reader on the X1 Extreme among the ones being worked on? I have one and would like to know if I can offer any assistance whatsoever.

@ab-pm
Copy link

@ab-pm ab-pm commented Aug 2, 2019

According to this forum response, Lenovo, Redhat and Synaptics are working on a driver.
Also it looks like someone started working on it in this libfprint repository.

@parkerlreed
Copy link

@parkerlreed parkerlreed commented Aug 2, 2019

Here's to hoping this applies to the rest of the devices too

138a:0094 checking in

EDIT: :O https://gitlab.freedesktop.org/vincenth/libfprint/blob/synaptics-driver-20190617/libfprint/fprint-list-udev-rules.c#L30

@t-8ch
Copy link

@t-8ch t-8ch commented Aug 3, 2019

EDIT: :O https://gitlab.freedesktop.org/vincenth/libfprint/blob/synaptics-driver-20190617/libfprint/fprint-list-udev-rules.c#L30

This list has been there for some time and I don't think it gives any information about the currently ongoing work.

@parkerlreed
Copy link

@parkerlreed parkerlreed commented Aug 6, 2019

Ahh, poop. Thanks.

@polatsinan
Copy link

@polatsinan polatsinan commented Nov 22, 2019

On my ThinkPad T495s I have the following device:
Bus 004 Device 006: ID 06cb:00bd Synaptics, Inc.

I added the following to main.c, compiled and ran it:
{ .vid = 0x06cb, .pid = 0x00bd, .hasLed = 0, .hasBios = -1, .requiresReset = 0, .hasRawOutput = -1 },

Result:


[...]

usb read:
0000 01 04 
Expected at char 000
0000 01 04 
Incomplete reverse engineering

Anything I can do?

@bumbummen99
Copy link

@bumbummen99 bumbummen99 commented Nov 22, 2019

@polatsinan As far as i am informed (got the T495 too) it should work with fprintd being ported to libfprint2 (https://gitlab.freedesktop.org/libfprint/libfprint/merge_requests/63/commits) which has just been merged.

Also note that a firmware update of the device will be required for that to work according to this discussion (https://gitlab.freedesktop.org/libfprint/libfprint/issues/181)

@alxchk
Copy link

@alxchk alxchk commented Feb 15, 2020

Just in case for those who cares -
Works on latest libfprintd/fprintd + firmware

Bus 001 Device 003: ID 06cb:00bd Synaptics, Inc. 

> fprintd-verify 
Using device /net/reactivated/Fprint/Device/0
Listing enrolled fingers:
 - #0: right-index-finger
Verify result: verify-match (done)

@FalcoSuessgott
Copy link

@FalcoSuessgott FalcoSuessgott commented Feb 26, 2020

@alxchk
Can you describe what u did to get it working?

@bumbummen99
Copy link

@bumbummen99 bumbummen99 commented Feb 26, 2020

@FalcoSuessgott You have to update the driver of your device (enable testing repositories to get the latest since it is not stable) and use the latest libfprint and fprintd (propably custom built since there is no up to date PPA).

@Chrescht
Copy link

@Chrescht Chrescht commented Apr 9, 2020

@bumbummen99 thanks, but could you be more specific, what libfprint version works?
I have currently version 1.90.1 and I keep getting errors about the device being already open:
Using device /net/reactivated/Fprint/Device/0
failed to claim device: Open failed with error: Device 06cb:00bd is already open

@FreezFree
Copy link

@FreezFree FreezFree commented May 10, 2020

Same problem here with the Version 1.90.1:
$ fprintd-verify
Using device /net/reactivated/Fprint/Device/0 failed to claim device: Open failed with error: The driver encountered a protocol error with the device.

Reinstall doesn't help.

Thinkpad T495
Fedora release 32 (Thirty Two)

@jamescassell
Copy link

@jamescassell jamescassell commented May 10, 2020

You need the firmware update from lvfs-testing.

@bumbummen99
Copy link

@bumbummen99 bumbummen99 commented May 10, 2020

There are issues with the current testing firmware that are fixed and it is being released currently.

@mandresve
Copy link

@mandresve mandresve commented May 19, 2020

Hello. There's suport for 06cb:00be | Synaptics? If not, how can I help?
I'm running Manjaro (Arch) latest ver.

@charleswilmot
Copy link

@charleswilmot charleswilmot commented Jun 3, 2020

Just reporting. Issue still occurs on

Fedora 32
Lenovo Carbon X1 gen 8
fprintd version 1.90.1

with firmware info

├─Prometheus:
│ │   Device ID:           d432baa2162a32c1554ef24bd8281953b9d07r11
│ │   Summary:             Fingerprint reader
│ │   Current version:     10.01.3121519
│ │   Vendor:              Synaptics (USB:0x06CB)
│ │   Install Duration:    2 seconds
│ │   Device Flags:        • Updatable
│ │                        • Cryptographic hash verification is available
│ │ 
│ └─Prometheus IOTA Config:
│       Device ID:         8dcffb5d059857368caa2b7b22371ebd831b0r0c
│       Current version:   0022
│       Minimum Version:   0022
│       Vendor:            Synaptics (USB:0x06CB)
│       Device Flags:      • Updatable

No newer firmware seem to be available after enabling

fwupdmgr enable-remote lvfs-testing
fwupdmgr update
• Prometheus has no available firmware updates

EDIT: problem fixed on my system

I needed to update fwupd before updating the fingerprint reader's firmware
Everything is working as a charm now

@vinayakumarb
Copy link

@vinayakumarb vinayakumarb commented Jul 8, 2020

Just reporting. Issue still occurs on

Fedora 32
Lenovo Carbon X1 gen 8
fprintd version 1.90.1

with firmware info

├─Prometheus:
│ │   Device ID:           d432baa2162a32c1554ef24bd8281953b9d07r11
│ │   Summary:             Fingerprint reader
│ │   Current version:     10.01.3121519
│ │   Vendor:              Synaptics (USB:0x06CB)
│ │   Install Duration:    2 seconds
│ │   Device Flags:        • Updatable
│ │                        • Cryptographic hash verification is available
│ │ 
│ └─Prometheus IOTA Config:
│       Device ID:         8dcffb5d059857368caa2b7b22371ebd831b0r0c
│       Current version:   0022
│       Minimum Version:   0022
│       Vendor:            Synaptics (USB:0x06CB)
│       Device Flags:      • Updatable

No newer firmware seem to be available after enabling

fwupdmgr enable-remote lvfs-testing
fwupdmgr update
• Prometheus has no available firmware updates

EDIT: problem fixed on my system

I needed to update fwupd before updating the fingerprint reader's firmware
Everything is working as a charm now

Thanks, Works fine on Ubuntu 20.4 now after said steps.

@kleash
Copy link

@kleash kleash commented Jul 23, 2020

@charleswilmot @vinayakumarb Can you please share exact steps you did to make it working.

I did following steps but fprintd-verify still throws same error:
sudo apt-get update
sudo apt-get upgrade
fwupdmgr enable-remote lvfs-testing
fwupdmgr update

@charleswilmot
Copy link

@charleswilmot charleswilmot commented Jul 24, 2020

@kleash same step as you did, but on a different OS.

@Vozf
Copy link

@Vozf Vozf commented Aug 4, 2020

For me it helped to reboot and do fwupdmgr update
After that login with fingerprint started working

@amtux
Copy link

@amtux amtux commented Aug 8, 2020

thanks for the heads up @Vozf.
I ran into the same issue where I enabled lvfs-testing and no still no updates were available but showed up after doing a reboot!

@kleash
Copy link

@kleash kleash commented Aug 11, 2020

@Vozf @amtux which linux you guys are using? bcoz it's not working for me in Ubuntu 20.04

@Vozf
Copy link

@Vozf Vozf commented Aug 11, 2020

Ubuntu 20.04 :)

@amtux
Copy link

@amtux amtux commented Aug 11, 2020

@Vozf @amtux which linux you guys are using? bcoz it's not working for me in Ubuntu 20.04

Manjaro with Kernel version 5.7.9

@JAicewizard
Copy link

@JAicewizard JAicewizard commented Aug 14, 2020

I just rebooted as that is supposed to get the updates to show up, but now fwupdmgr doesnt show the fingerprint reader at all.
Does anyone know how this would even be possible, or better yet, how to get it to show up again?
factory reset from bios worked, but I am still curious how this happened...

EDIT:
After rebooting I still had no firmware update. A better way is to run fwupdmgr refresh to refresh the sources.
Also the newest firmware is available on lvs non-stable now, so you should use that. (https://fwupd.org/lvfs/devices/com.synaptics.prometheus.firmware)

@mickare
Copy link

@mickare mickare commented Sep 5, 2020

Hi, thanks to everyone i got the fingerprint sensor 06cb:00bd on my new Lenovo T14 working. 😄

System: Arch Linux 5.8.3-2-MANJARO

Steps:

  1. (Optional ?) Upgrade Kernel to >= 5.8
  2. Install fwupdmgr via: pacman -S fwupd
  3. Check if your device is listed: fwupdmgr get-devices, if not reboot
  4. Enable "Linux Vendor Firmware Service" via: fwupdmgr enable-remote lvfs
  5. Refresh firmware list: fwupdmgr refresh
  6. Run fwupdmgr update and update both Prometheus devices.
  7. Reboot

Unfortunately fingerprint-gui does not detect the device; but you can either register your fingerprints via the system settings (Gnome: Settings > Users > Your User > Fingerprint Login); or use the fprintd command line: man fprintd

PS: Upgrade your kernel to at least 5.8 for the latest drivers for the AMD Ryzen 7 Pro 4750U; if not your CPU is ~50% slower.

@amtux
Copy link

@amtux amtux commented Sep 5, 2020

@mickare - agree. i had a bunch of issues with 5.7.x on T14s with Ryzen 7 4750U, CPU issues and other stuff like mic not working and random GPU crashes when external monitor was plugged in via DP/HDMI. Linux 5.8 fixed all the issues and it's running ever more stable on 5.8.3 right now.

@JAicewizard
Copy link

@JAicewizard JAicewizard commented Sep 6, 2020

5.8 made a lot of things better on my T14, I think the no mic was actually listed on the arch wiki.

@Punkoivan
Copy link

@Punkoivan Punkoivan commented Sep 30, 2020

@mickare thank you, now sensor works on my t14 even without reboot.

Folks, may be we can close the issue?

@victortrac
Copy link

@victortrac victortrac commented Sep 30, 2020

I think this can be closed.

@sreehax
Copy link

@sreehax sreehax commented Oct 2, 2020

I'm on Void Linux on my ThinkPad X1 Carbon Gen 7 and I tried all the steps with enabling lvfs-testing and rebooting and all but it still says
list_devices failed: No devices available

@sreehax
Copy link

@sreehax sreehax commented Oct 2, 2020

I have Bus 001 Device 006: ID 06cb:00bd Synaptics, Inc. in lsusb

@caj-larsson
Copy link

@caj-larsson caj-larsson commented Feb 5, 2021

This sensor works for me for an hour to a day before i can no longer verify any part of my finger, how can I debug this? Is this a sensitivity issue or potentially noise in the images matched? While I know my finger print does change over time, I know the sensor works fine in windows so it definitely seem to be an issue with my system or this driver

@matiaslopezd
Copy link

@matiaslopezd matiaslopezd commented Feb 11, 2021

The way to fix this is to reboot your laptop, log in, open the terminal and enter:

fwupdmgr update

Then reboot (will be part of update) and you will available to use the fingerprint. 😄

EDIT: I have Ubuntu 20.10. If you have Ubuntu <= 20.04.2, update to 20.10 or later.

@Vicsuka
Copy link

@Vicsuka Vicsuka commented Feb 11, 2021

├─Touchpad: │ Current version: 1.2.3078276 │ Bootloader Version: 8.0 │ Vendor: Synaptics (HIDRAW:0x06CB) │ Device Flags: • Internal device │ • Updatable
Ubuntu 20.04.2 LTS, update doesn't work. Anyone else having the same device?

@matiaslopezd
Copy link

@matiaslopezd matiaslopezd commented Feb 11, 2021

@Vicsuka update to 20.10, I had a lot of issues inclusive in an empty disk installation of 20.04.2.

@Photon89
Copy link

@Photon89 Photon89 commented Aug 14, 2021

Unfortunately fingerprint-gui does not detect the device; but you can either register your fingerprints via the system settings (Gnome: Settings > Users > Your User > Fingerprint Login); or use the fprintd command line: man fprintd

This solved it for me, thanks @mickare!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests