You are not logged in.
I have a Lenovo IdeaPad 14ARE05 and have installed Arch on it. There were multiple compatibility issues out-of-the-box, but I've been able to resolve most of them. The only major one that remains is the fingerprint sensor.
Bus 003 Device 002: ID 04f3:0c4d Elan Microelectronics Corp. ELAN:Fingerprint
The sensor is detected by fprintd and finger seems to get successfully registered. However, during login, the fingerprint never matches. The sensor isn't faulty as it works perfectly in Windows 10
Offline
Do you use Fingerprint GUI?
Offline
Do you use Fingerprint GUI?
It is installed. Doesn't support my sensor
Offline
According to the list of supported devices that's not true since it is on the list of default supported scanners.
Did you follow the wiki on it?
Last edited by Archlin (2021-01-14 16:00:00)
Offline
Yup. It shows no devices
Offline
Since Fingerprint Gui uses fprintd to get the devices, saying fprintd finds the device but Fingerprint GUi is not is kinda strange.
That's why I ask did you follow the wiki
But back to the issue
Do you get an error other than no match?
Did you verify with "fprintd-verify" and do you get a good verification?
Does "journalctl -f -u fprintd" show anything helpfull?
Last edited by Archlin (2021-01-15 09:13:55)
Offline
fprintd-verify says no-match.
$ journalctl -f -u fprintd
-- Journal begins at Thu 2021-01-14 21:49:26 IST. --
Jan 15 15:01:32 c3po systemd[1]: Starting Fingerprint Authentication Daemon...
Jan 15 15:01:33 c3po systemd[1]: Started Fingerprint Authentication Daemon.
Jan 15 15:02:40 c3po systemd[1]: fprintd.service: Succeeded.Last edited by devmrfitz (2021-01-15 09:33:52)
Offline
What version fprintd do you use? Repo or one oif the AUR versions?
Perhaps this applies to your situation to.
Last edited by Archlin (2021-01-15 11:34:49)
Offline
pacman -Syu fprintd
Offline
sometime if your fingerprint sensor is too small it doesn't work at all I was having the same issue and eventually gave up
Offline
But the sensor's working perfect in windows. If it was too small, wouldn't that hamper it in windows too?
Offline
But the sensor's working perfect in windows. If it was too small, wouldn't that hamper it in windows too?
It will work on fine on windows. but the problem is with the Linux implementation of the drivers. check this github repo
https://github.com/iafilatov/libfprint
check the common problem section. It describes that if the sensor is too small it generates a small image which is not sufficient for correct detection
The project later got merges with libfprint main and now the driver is on the master branch of libfprint but the problem still persists
Offline
devmrfitz wrote:But the sensor's working perfect in windows. If it was too small, wouldn't that hamper it in windows too?
It will work on fine on windows. but the problem is with the Linux implementation of the drivers. check this github repo
https://github.com/iafilatov/libfprintcheck the common problem section. It describes that if the sensor is too small it generates a small image which is not sufficient for correct detection
The project later got merges with libfprint main and now the driver is on the master branch of libfprint but the problem still persists
Didn't understand that. If the sensor is x*y cm, it will provide the x*y image for both OSes, right?
Offline
I didn't thought of this earlier but I am opening a GitHub issue on the drivers repo. If the original creator of the drivers respond back we may find a way to make it work
Offline
Here is the github issue
https://github.com/iafilatov/libfprint/issues/36
but the guy who created this driver doesn't seems very active on github so anyone having the issue try to support my issue so that we have a chance to get his attention
Offline
Here is the github issue
https://github.com/iafilatov/libfprint/issues/36but the guy who created this driver doesn't seems very active on github so anyone having the issue try to support my issue so that we have a chance to get his attention
Done. Also, won't an issue in official libprint repo be helpful?
Offline
Done. Also, won't an issue in official libprint repo be helpful?
You could add 04f3:0c4d to https://gitlab.freedesktop.org/libfprin … %20Devices it already has 04f3:0c4c 04f3:0c4f
Offline
I can't add it in unsupported devices as it is already in supported devices
Offline
Comment on https://gitlab.freedesktop.org/libfprin … issues/263 ? libfprint 1.90.6-1 contains the commit that added support.
Offline