[04f3:0903] Elan Microelectronics Corp fingerprint reader not recognised
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libfprint |
New
|
Undecided
|
Unassigned | ||
libfprint (Debian) |
New
|
Undecided
|
Unassigned | ||
libfprint (Ubuntu) |
Fix Released
|
Undecided
|
Nur Sandi |
Bug Description
Running "fprint-demo" with this hardware installed reports "No devices found".
This is the integrated reader in new ASUS ZenBook UX390UA laptops.
lsusb -v output here: http://
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: libfprint0 1:0.6.0-2
ProcVersionSign
Uname: Linux 4.8.0-27-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Nov 12 15:59:17 2016
InstallationDate: Installed on 2016-11-08 (3 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
SourcePackage: libfprint
UpgradeStatus: No upgrade log present (probably fresh install)
Barry Price (barryprice) wrote : | #1 |
- Dependencies.txt Edit (2.6 KiB, text/plain; charset="utf-8")
- JournalErrors.txt Edit (41.3 KiB, text/plain; charset="utf-8")
- ProcEnviron.txt Edit (349 bytes, text/plain; charset="utf-8")
Nuno (nmrcardoso) wrote : | #2 |
Nuno (nmrcardoso) wrote : | #3 |
Here is my output for that device:
Bus 001 Device 005: ID 04f3:0903 Elan Microelectronics Corp.
Couldn't open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x04f3 Elan Microelectronics Corp.
idProduct 0x0903
bcdDevice 1.35
iManufacturer 1
iProduct 2
iSerial 0
bNumConfigura
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 62
bNumInterfaces 1
bConfigurat
iConfiguration 0
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescript
bInterfac
bAlternat
bNumEndpoints 5
bInterfac
bInterfac
bInterfac
iInterface 0
** UNRECOGNIZED: 09 21 10 01 00 01 22 15 00
Endpoint Descriptor:
bLength 7
Transfer Type Bulk
Synch Type None
Usage Type Data
bInterval 1
Endpoint Descriptor:
bLength 7
Transfer Type Bulk
Synch Type None
Usage Type Data
bInterval 1
Endpoint Descriptor:
bLength 7
Transfer Type Bulk
Synch Type None
Usage Type Data
bInterval 1
Endpoint Descriptor:
bLength 7
Transfer Type Bulk
Synch Type None
Usage Type Data
bInterval 1
Endpoint Descriptor:
bLength 7
Transfer Type Bulk
Synch Type None
Usage Type Data
bInterval 1
Launchpad Janitor (janitor) wrote : | #4 |
Status changed to 'Confirmed' because the bug affects multiple users.
Changed in libfprint (Ubuntu): | |
status: | New → Confirmed |
Dmitry Korotovsky (rmpic30) wrote : | #5 |
Same issue.
$ sudo fprintd-enroll
list_devices failed: No devices available
lshw:
Dmitry Korotovsky (rmpic30) wrote : | #6 |
ASUS ZenBook UX390UA
$ uname -a
Linux korotovskii 4.8.6-040806-
$ lsb_release -a
Distributor ID: Ubuntu
Description: Ubuntu 16.04.1 LTS
Release: 16.04
Codename: xenial
Corentin Dancette (cdancette) wrote : | #7 |
Same here with ubuntu 17.04, Asus ZenBook UX360UAK
$ uname -a
Linux zenbook 4.10.4-
Aless Jeant (aless-jeant) wrote : | #8 |
Same here,
~ uname -a
Linux Zenbook3 4.10.0-19-generic #21-Ubuntu SMP Thu Apr 6 17:04:57 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
~lsusb -v
Bus 001 Device 004: ID 04f3:0903 Elan Microelectronics Corp.
Couldn't open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x04f3 Elan Microelectronics Corp.
idProduct 0x0903
bcdDevice 1.35
iManufacturer 1
iProduct 2
iSerial 0
bNumConfigura
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 62
bNumInterfaces 1
bConfigurat
iConfiguration 0
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescript
bInterfac
bAlternat
bNumEndpoints 5
bInterfac
bInterfac
bInterfac
iInterface 0
** UNRECOGNIZED: 09 21 10 01 00 01 22 15 00
Endpoint Descriptor:
bLength 7
Transfer Type Bulk
Synch Type None
Usage Type Data
bInterval 1
Endpoint Descriptor:
bLength 7
Transfer Type Bulk
Synch Type None
Usage Type Data
bInterval 1
Endpoint Descriptor:
bLength 7
Transfer Type Bulk
Synch Type None
Usage Type Data
bInterval 1
Endpoint Descriptor:
bLength 7
Transfer Type Bulk
Synch Type None
Usage Type Data
bInterval 1
Endpoint Descriptor:
bLength 7
Transfer Type Bulk
Synch Type None
Usage Typ...
William Elliott (willdorf) wrote : | #9 |
Same here with Asus ZenBook UX330UA
gerrit (gerrit-damen) wrote : | #10 |
Patrick Hofmann (pahofmann) wrote : | #11 |
Can confirm on UX330UA.
$lsusb
Bus 001 Device 004: ID 04f3:0903 Elan Microelectronics Corp.
Couldn't open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x04f3 Elan Microelectronics Corp.
idProduct 0x0903
bcdDevice 1.35
iManufacturer 1
iProduct 2
iSerial 0
bNumConfigura
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 62
bNumInterfaces 1
bConfigurat
iConfiguration 0
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescript
bInterfac
bAlternat
bNumEndpoints 5
bInterfac
bInterfac
bInterfac
iInterface 0
** UNRECOGNIZED: 09 21 10 01 00 01 22 15 00
Endpoint Descriptor:
bLength 7
Transfer Type Bulk
Synch Type None
Usage Type Data
bInterval 1
Endpoint Descriptor:
bLength 7
Transfer Type Bulk
Synch Type None
Usage Type Data
bInterval 1
Endpoint Descriptor:
bLength 7
Transfer Type Bulk
Synch Type None
Usage Type Data
bInterval 1
Endpoint Descriptor:
bLength 7
Transfer Type Bulk
Synch Type None
Usage Type Data
bInterval 1
Endpoint Descriptor:
bLength 7
Transfer Type Bulk
Synch Type None
Usage Type Data
bInterval 1
Isaac Emesowum (iemesowum) wrote : | #12 |
- lsusb -v (manual grep for elan) Edit (3.1 KiB, text/plain)
Confirmed on UX390U.
This bug should actually be a feature request. There is currently no support for elantech fingerprint scanners in libfprint. Someone needs to write a driver for it. It's proprietary, so that might be tricky.
Daniel Verstegen (verstegen-daan) wrote : | #13 |
Yep, same here:
Asus Zenbook UX430U
Bus 001 Device 004: ID 04f3:0903 Elan Microelectronics Corp.
Couldn't open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x04f3 Elan Microelectronics Corp.
idProduct 0x0903
bcdDevice 1.35
iManufacturer 1
iProduct 2
iSerial 0
bNumConfigura
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 62
bNumInterfaces 1
bConfigurat
iConfiguration 0
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescript
bInterfac
bAlternat
bNumEndpoints 5
bInterfac
bInterfac
bInterfac
iInterface 0
** UNRECOGNIZED: 09 21 10 01 00 01 22 15 00
Endpoint Descriptor:
bLength 7
Transfer Type Bulk
Synch Type None
Usage Type Data
bInterval 1
Endpoint Descriptor:
bLength 7
Transfer Type Bulk
Synch Type None
Usage Type Data
bInterval 1
Endpoint Descriptor:
bLength 7
Transfer Type Bulk
Synch Type None
Usage Type Data
bInterval 1
Endpoint Descriptor:
bLength 7
Transfer Type Bulk
Synch Type None
Usage Type Data
bInterval 1
Endpoint Descriptor:
bLength 7
Transfer Type Bulk
Synch Type None
Usage Type Data
bInterval 1
Tony Tascioglu (tonytash) wrote : | #14 |
Fingerprint scanner on Asus UX330UA running Ubuntu 17.04 and Linux Mint 18.2 not working either.
Bus 001 Device 004: ID 04f3:0903 Elan Microelectronics Corp.
Couldn't open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x04f3 Elan Microelectronics Corp.
idProduct 0x0903
bcdDevice 1.35
iManufacturer 1
iProduct 2
iSerial 0
bNumConfigura
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 62
bNumInterfaces 1
bConfigurat
iConfiguration 0
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescript
bInterfac
bAlternat
bNumEndpoints 5
bInterfac
bInterfac
bInterfac
iInterface 0
** UNRECOGNIZED: 09 21 10 01 00 01 22 15 00
Endpoint Descriptor:
bLength 7
Transfer Type Bulk
Synch Type None
Usage Type Data
bInterval 1
Endpoint Descriptor:
bLength 7
Transfer Type Bulk
Synch Type None
Usage Type Data
bInterval 1
Endpoint Descriptor:
bLength 7
Transfer Type Bulk
Synch Type None
Usage Type Data
bInterval 1
Endpoint Descriptor:
bLength 7
Transfer Type Bulk
Synch Type None
Usage Type Data
bInterval 1
Endpoint Descriptor:
bLength 7
Transfer Type Bulk
Synch Type None
Usage Type Data
Tony Tascioglu (tonytash) wrote : | #15 |
- Fingerprint reader driver from ASUS for WIndows 10 Edit (7.2 MiB, application/zip)
If it helps, I have attached the driver provided by ASUS for Windows 10 from their website.
Arash (ara4sh) wrote : | #17 |
Same issue Asus UX490
Casey Salvador (csalvador) wrote : | #18 |
I'm having the same issue with Asus UX430UA as well.
Dylan Borg (borgdylan) wrote : | #19 |
The same device i on the Zenbook Pro UX550 as well.
Dmitry Korotovsky (rmpic30) wrote : | #20 |
Looks like I would change my laptop a way faster than Ubuntu team would fix this bug =/
Manuel Matas (manuelmatas) wrote : | #21 |
Same issue with Asus UX550VE. No devices found on Fingerprint GUI 1.09.
Toky RALALA (ralala-toky) wrote : | #22 |
I'm confirming the same issue on ASUS UX530UX too
skilo (ramskilo) wrote : | #23 |
Same here with Zenbook UX430UN.
There's a kernel module named elan_i2c that makes me wonder:
modinfo elan_i2c
filename: /lib/modules/
version: 1.6.2
license: GPL
description: Elan I2C/SMBus Touchpad driver
author: Duson Lin <email address hidden>
srcversion: 775624509AF5920
alias: i2c:elan_i2c
alias: acpi*:ELAN1000:*
alias: acpi*:ELAN0608:*
alias: acpi*:ELAN0605:*
alias: acpi*:ELAN0600:*
alias: acpi*:ELAN0100:*
alias: acpi*:ELAN0000:*
depends:
intree: Y
vermagic: 4.10.0-38-generic SMP mod_unload
Since the fingerprint sensor is part of the touchpad, it could be managed by this module (?). But in my configuration this is not loaded by default, and it is loaded instead hid_multitouch.ko.
Unfortunately neither load this manually and remove hid_multitouch resolves.
Hope this helps
Dani (dtalens) wrote : | #24 |
I'm confirming the same issue on Xiaomi Air 13 2017
lsusb -v output here: http://
Linux 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Distributor ID: Ubuntu
Description: Ubuntu 17.10
Release: 17.10
Codename: artful
yanqian (yanqian) wrote : | #25 |
same issue on ASUS UX310UAK.
Bus 001 Device 005: ID 04f3:0903 Elan Microelectronics Corp.
Jerome B (revv-k) wrote : | #26 |
Same here, with ASUS UX430UA
Alberto Martino (malbertom) wrote : | #27 |
Same here, with ASUS UX430UA
Alberto Martino (malbertom) wrote : | #28 |
Seems that someone is working on that:
https://<email address hidden>
last message 08-11-2017
Alberto Martino (malbertom) wrote : | #29 |
found the git repo
https:/
Andrea Nisticò (andrean.pk) wrote : | #30 |
Did someone try this libfprint's branch with 04f3:0903 (ELAN on Asus UX530UX)?
Isaac Emesowum (iemesowum) wrote : Re: [Bug 1641290] Re: [04f3:0903] Elan Microelectronics Corp fingerprint reader not recognised | #31 |
I gave it a try with 04f3:0903:
"This program will enroll your right index finger, unconditionally
overwriting any right-index print that was enrolled previously. If you want
to continue, press enter, otherwise hit Ctrl+C
Found device claimed by ElanTech Fingerprint Sensor driver
Opened device. It's now time to enroll your finger.
You will need to successfully scan your finger 5 times to complete the
process.
Scan your finger now.
async:error [fpi_drvcb_
sync:error [fp_enroll_
I used the 'enroll' example binary after building the code at that
location. It's not a device file permission issue. Has this worked for
anyone else?
Isaac
On Nov 28, 2017 13:31, "Andrea Nisticò" <email address hidden> wrote:
Did someone try this libfprint's branch with 04f3:0903 (ELAN on Asus
UX530UX)?
--
You received this bug notification because you are subscribed to the bug
report.
https:/
Title:
[04f3:0903] Elan Microelectronics Corp fingerprint reader not
recognised
Status in libfprint package in Ubuntu:
Confirmed
Bug description:
Running "fprint-demo" with this hardware installed reports "No devices
found".
This is the integrated reader in new ASUS ZenBook UX390UA laptops.
lsusb -v output here: http://
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: libfprint0 1:0.6.0-2
ProcVersionSi
Uname: Linux 4.8.0-27-generic x86_64
NonfreeKernel
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Nov 12 15:59:17 2016
InstallationDate: Installed on 2016-11-08 (3 days ago)
InstallationM
SourcePackage: libfprint
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https:/
1290/+subscriptions
JM (josemesnaola) wrote : | #32 |
I also gave it a try with 04f3:0903 in ASUS UX490UA.
Unfortunately I obtain the same results as Isaac Emesowum (iemesowum).
Once compiled and installed I'm able to execute fprint_demo (as superuser) and when I try to enroll I get the following errors (I enabled debugging):
elan:debug [elan_cmd_cb] unexpected transfer length
drv:debug [fpi_ssm_
drv:debug [fpi_ssm_
elan:debug [init_complete]
fp:debug [fpi_imgdev_
async:error [fpi_drvcb_
async:debug [fpi_drvcb_
async:debug [fp_async_
elan:debug [dev_deactivate]
I also executed enroll (in examples folder) with the same result.
I don't know anything about lsusb so I didn't manage to understand what was going on.
Alberto Martino (malbertom) wrote : | #33 |
The branch sbechet/libfprint is only a "first try"
the developer hasn't figured out yet how to make elan work.
At the moment the device is only added to be a "supported device" but the code on the file
https:/
throws an error (-71) on this method:
static void elan_cmd_cb(struct libusb_transfer *transfer)
on line 197 -> else if (transfer->length != transfer-
I'm reporting here the message from Igor Filatov to Sébastien Béchet
> With these devices the scanned area is so small that not many minutiae can
> be found there. I got like 5 o so with my finger and that's what I can
> visually confirm looking at the scanned images. It's not about image
> quality. I think original drivers could be using a different algorithm.
>
> Looks like your device doesn't react normally to 402a (not unexpected). It's
> the third init command in elan.h. Try removing it. Actually, you can try
> removing all commands not found in you traces. Just don't remove the arrays
> with commands for now, leave empty if needed.
>
> It doesn't seem to complicated to adapt the driver based on your traces but
> don't think I'll have any time for it soon…
Guilherme de Lázari da Costa e Silva (glazari) wrote : | #34 |
January 2018 still not working for 04f3:0c1a on Xiaomi notebook Pro
Lord_JABA (lordjaba) wrote : | #35 |
Same on 2017 xiomi notebook air 13.
lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 8087:0a2b Intel Corp.
Bus 001 Device 003: ID 04f3:0c1a Elan Microelectronics Corp.
Bus 001 Device 002: ID 04f2:b5a3 Chicony Electronics Co., Ltd
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
uname -a:
Linux slider 4.13.0-32-generic #35~16.04.1-Ubuntu SMP Thu Jan 25 10:13:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
Timur Celik (clktmr) wrote : | #36 |
Current official master branch works for me (UX430UA [04f3:0903]).
The only change I made was adding my device to the driver:
@@ -608,6 +608,7 @@ static void dev_deactivate(
static const struct usb_id id_table[] = {
{.vendor = 0x04f3,.product = 0x0907},
+ {.vendor = 0x04f3,.product = 0x0903},
{0, 0, 0,},
};
1 comments hidden Loading more comments | view all 153 comments |
Timur Celik (clktmr) wrote : | #38 |
I added that line to drivers/elan.c. However, after some testing it's not working reliably for me. My fingerprint is recognized in about 1 out of 10 cases only. libfprint doesn't seem to like the images provided by the sensor. Possibly some improvement in the image processing is necessary. I will look into this if I find the time.
SN (sigma343) wrote : | #39 |
where did you find the source code? all the downloads I have seen dont have a elan.c file in the drivers folder.
Timur Celik (clktmr) wrote : | #40 |
73 comments hidden Loading more comments | view all 153 comments |
Ares (aresaguilarsotos) wrote : | #114 |
@Igor,
Hi,
Do you know if it is possible to install libfprint 0.8.3 on Ubuntu 18.10? I would love to try the driver on my ZenBook.
Igor Filatov (iafilatov) wrote : | #115 |
@Ares
0.8.3 is not in the Ubuntu package repos yet so the only way is to install from source https:/
Angel (4ng3ll) wrote : | #116 |
Hello, I followed all the instructions and apparently I could install fprint correctly. However when I run sudo ./img_capture I got an error message. Also is not possible to enroll and fprint_demo cannot fing any device.
I tried to look for the error 903 but the github page is no longer available
I'm running it in ubuntu 18.10 if that helps.
I hope anyone can help me out
The error message is:
(process:3360): libfprint-DEBUG: 20:49:10.427: 161437947: ../libfprint/
(process:3360): libfprint-DEBUG: 20:49:10.432: registered driver upekts
(process:3360): libfprint-DEBUG: 20:49:10.432: registered driver upektc
(process:3360): libfprint-DEBUG: 20:49:10.432: registered driver upeksonly
(process:3360): libfprint-DEBUG: 20:49:10.432: registered driver vcom5s
(process:3360): libfprint-DEBUG: 20:49:10.432: registered driver uru4000
(process:3360): libfprint-DEBUG: 20:49:10.432: registered driver aes1610
(process:3360): libfprint-DEBUG: 20:49:10.433: registered driver aes1660
(process:3360): libfprint-DEBUG: 20:49:10.433: registered driver aes2501
(process:3360): libfprint-DEBUG: 20:49:10.433: registered driver aes2550
(process:3360): libfprint-DEBUG: 20:49:10.433: registered driver aes2660
(process:3360): libfprint-DEBUG: 20:49:10.433: registered driver aes3500
(process:3360): libfprint-DEBUG: 20:49:10.433: registered driver aes4000
(process:3360): libfprint-DEBUG: 20:49:10.433: registered driver vfs101
(process:3360): libfprint-DEBUG: 20:49:10.433: registered driver vfs301
(process:3360): libfprint-DEBUG: 20:49:10.433: registered driver vfs5011
(process:3360): libfprint-DEBUG: 20:49:10.433: registered driver upektc_img
(process:3360): libfprint-DEBUG: 20:49:10.433: registered driver etes603
(process:3360): libfprint-DEBUG: 20:49:10.433: registered driver vfs0050
(process:3360): libfprint-DEBUG: 20:49:10.433: registered driver elan
(process:3360): libfprint-DEBUG: 20:49:10.433: driver elan supports USB device 04f3:0c10
(process:3360): libfprint-DEBUG: 20:49:10.433: selected driver elan supports USB device 04f3:0c10
Found device claimed by ElanTech Fingerprint Sensor driver
(process:3360): libfprint-
(process:3360): libfprint-
(process:3360): libfprint-
(process:3360): libfprint-
(process:3360): libfprint-
Opened device. It's now time to scan your finger.
(process:3360): libfprint-
(process:3360): libfprint-
(process:3360): libfprint-DEBUG: 20:49:10.546: action 4
(process:3360): libfprint-
(process:3360): libfprint-
(process:3360): libfprint-
(process:3360): libfprint-
(process:3360): libfprint-
Igor Filatov (iafilatov) wrote : | #117 |
@Angel
> (process:3360): libfprint-
It appears that you have libfprint with a bug that's been fixed some time ago. It looks like an unstable version could've appeared in repos due to misunderstanding of some sort (see https:/
Behrad Khodayar (behradkhodayar) wrote : | #118 |
My Device is AsusPro B9440UA, with the same driver:
Bus 001 Device 003: ID 04f3:0903 Elan Microelectronics Corp.
Unfortunately not supported yet
Rafik Farhad (rafikfarhad) wrote : | #119 |
Same for Ausu Vivobook S15 S530UN
uname -a:
Linux epicalypto 4.18.0-16-generic #17~18.04.1-Ubuntu SMP Tue Feb 12 13:35:51 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 8087:0a2b Intel Corp.
Bus 001 Device 003: ID 13d3:56c1 IMC Networks
Bus 001 Device 002: ID 25a7:fa61
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Changed in libfprint (Ubuntu): | |
status: | Confirmed → Invalid |
status: | Invalid → Incomplete |
1 comments hidden Loading more comments | view all 153 comments |
Miguel Ferrer (ingferrermiguel) wrote : | #121 |
I'm having the same issue with Asus UX430UA as well.
Changed in libfprint (Ubuntu): | |
status: | Incomplete → Confirmed |
status: | Confirmed → Incomplete |
Diogo Falcomer (diogo-falcomer) wrote : | #122 |
Here i have the same issue, and plus the right touchpad button doesn`t work too.
I`m using ubuntu 19.04 in a Notebook xiaomi air 13 (2017).
Bus 001 Device 004: ID 04f3:0c1a Elan Microelectronics Corp
:~$ fprintd-enroll
list_devices failed: No devices available
Maarten Fonville (maarten-fonville) wrote : | #123 |
I experience the same issue. Problem is that even the most recent libfprint does not support i2c devices yet (only USB)
KozArt (kozart) wrote : | #124 |
The same here...
Asus Vivobook S15 S510UN
Fingerprint not found
Nikhil (nikhil2110) wrote : | #125 |
Same not working Goodix Fingerprint Sensor in Ubuntu 18.04 LTS.
rustyx (rustyx2) wrote : | #126 |
FWIW, the 04f3:0903 ELAN device stops working in Windows 10 too, if I touch it too much and/or at the wrong moment. But in Windows I don't have to swipe it at all, it somehow works by touch. Also during enrollment.
Hayden (duckduckgo) wrote : | #127 |
ASUS Vivobook S13 ASUS S330UA
Running "fprint-demo" reports "No devices found".
Edyta (edytka) wrote : | #128 |
ASUS VIvobook S14 S410UA the same problem
Gonçalo (gmatosferreira) wrote : | #129 |
VivoBook_ASUSLaptop X530FN_S530FN the same problem
Ethan Walker (ethanmwalker) wrote : | #130 |
I'm having the same issue on an ASUS ZenBook S UX391UA in ubuntu 19.10, kernel version 5.4.2-050402-
hurelhuyag (hurelhuyag) wrote : | #131 |
I have Vivobook F510UA laptop. Yes this affecting me too.
Gabriel Cabana (cabg2101) wrote : | #132 |
Asus Zenbook Flip 14 (UX461UA). Affected by the problem as well. Ubuntu 18.04, kernel 5.0.0-37-generic.
Coder Dmitry (webocoders) wrote : | #133 |
I'm having the same issue on an Asus Zenbook UX391U
Linux mint 19.3
kernel version 5.3.0-24
lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 27c6:5201
Bus 001 Device 003: ID 8087:0a2b Intel Corp.
Bus 001 Device 002: ID 13d3:56b9 IMC Networks
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
lspci
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 08)
00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (rev 07)
00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 08)
00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21)
00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21)
00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0 (rev 21)
00:15.1 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #1 (rev 21)
00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21)
00:1c.0 PCI bridge: Intel Corporation Device 9d13 (rev f1)
00:1c.4 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #5 (rev f1)
00:1d.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #9 (rev f1)
00:1f.0 ISA bridge: Intel Corporation Intel(R) 100 Series Chipset Family LPC Controller/eSPI Controller - 9D4E (rev 21)
00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)
00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
01:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78)
6d:00.0 Non-Volatile memory controller: Toshiba America Info Systems NVMe Controller (rev 01)
dpcat237 (denys) wrote : | #134 |
I have Asus UX331UN laptop and this affects me too.
Psenik1 (psenik1) wrote : | #135 |
Affects me too.
I have ASUS UX 331UA
Charls P John (charlspjohn) wrote : | #136 |
Saket Singh (sakets542) wrote : | #137 |
I have asus vivobook s14 s430 and i have the same issue.
Maneesh Singh (maneesh.ubuntu) wrote : | #138 |
I am facing the same issue. Tried on 18.04lts and 20.04lts. I have asus vivobook x507uf.
Sebastien Bacher (seb128) wrote : | #139 |
Could anyone still having an issue on the newest focal LTS open a new report using
$ ubuntu-bug libfprint
the fingerprint stack has quite some work this cycle and having decide specifics is needed
Maarten Fonville (maarten-fonville) wrote : | #140 |
@Sebastien Bacher, I filed a new bug at https:/
Trayan (trayan) wrote : | #141 |
Same Here, Asus VivoBook N580v. Please fix
David Olthaar (imdavid) wrote : | #142 |
Also for me for Asus Vivobook 15:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 13d3:56dd IMC Networks
Bus 001 Device 003: ID 13d3:3491 IMC Networks
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Changed in libfprint (Ubuntu): | |
status: | Incomplete → Confirmed |
Luis Oliveira (mehrlicht) wrote : | #143 |
It affects me too:
ASUS VivoBook S15 S530FN
Ubuntu 20.04 Focal Fossa
Saket Singh (sakets542) wrote : | #144 |
It affects me too:
ASUS vivobook s430FA s series
Ubuntu 20.04 Focal Fossa
Changed in libfprint (Ubuntu): | |
assignee: | nobody → Nur Sandi (nursandi) |
Marco Trevisan (Treviño) (3v1n0) wrote : | #145 |
Drivers requests are upstream issues and as such should be redirected to the official wiki:
- https:/
As per this, I'm closing all the requests, I please you to update that wiki page if needed.
Changed in libfprint (Ubuntu): | |
status: | Confirmed → Invalid |
status: | Invalid → Fix Released |
ganeshpokale (ganeshpokale) wrote : | #146 |
I have asus vivobook s14 facing same same issue.
Azhar (azhar-munshi-99) wrote : | #147 |
I have Asus vivobook v15 x512fl and elementary os but the fingerprint sensor could not be detected.
x12 (kobadmitrii) wrote : | #148 |
I am seeing a problem not asus zenbook um431d.
Mayra Díaz Tramontana (mayra2001) wrote : | #149 |
It affects me too, I have an Asus Zenbook flip UX461UN and it doesnt recognize the fingerprint reader
Darshil Shah (darshil97) wrote : | #150 |
It affects me too. I am using Asus ViviBook F571.
Del Marshall (del-marshall) wrote : | #151 |
Same issue, fingerprint reader not recognized. ASUS VivoBook K-513 Linux Mint 20.3
Tecix (tex460) wrote : | #152 |
My laptop is Asus Vivobook A412F and fingerprint reader was not listed with lsusb, lspci, lshw commands.
However, I don't know why the fprintd-enroll command working and I can register fingerprints, but then cannot verify after that.
hurelhuyag (hurelhuyag) wrote : | #153 |
I'm on Asus F510UA fresh 23.04 installed. It is now working. But hard to use it.
On Windows, I just press my finger on the sensor it works. But on Ubuntu, it requires me to swipe my finger and I did it. It never match my previously registered fingerprints.
Same here but with ASUS ux360uak and "Bus 001 Device 005: ID 04f3:0903 Elan Microelectronics Corp"
Not recognized either.