VFS451 is not recognished by the library. Ubuntu bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/745505
*** This bug has been marked as a duplicate of bug 37574 ***
Sorry, didn't found it by searching
It is not the same peripherial
(In reply to comment #3) > It is not the same peripherial My mistake, started with "VFS", and filed at about the same time, my brain didn't parse it all.
I can confirm this bug. Bus 006 Device 059: ID 138a:0007 Validity Sensors, Inc. VFS451 Fingerprint Reader Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 255 Vendor Specific Class bDeviceSubClass 19 bDeviceProtocol 255 bMaxPacketSize0 8 idVendor 0x138a Validity Sensors, Inc. idProduct 0x0007 VFS451 Fingerprint Reader bcdDevice 0.72 iManufacturer 0 iProduct 0 iSerial 1 0020a0d79688 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 46 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 4 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 Device Status: 0x0000 (Bus Powered) I tested with libfprint 0.4.0, normal and with vfs301 patch from Andree https://github.com/andree182/vfs301/tarball/master I added to that driver the 138a:0007, the fprint_demo detects it but does not work.
Confirmed bug on Hp 2540p notebook. Bus 001 Device 005: ID 138a:0007 Validity Sensors, Inc. VFS451 Fingerprint Reader
Is it available as a standalone USB device? Any chance to get logs captured by USBSniff under windows? See http://www.freedesktop.org/wiki/Software/fprint/libfprint/USB%20sniffing
If needed, I can provide usb sniffs about it.
(In reply to comment #8) > If needed, I can provide usb sniffs about it. It would be nice
Created attachment 70605 [details] capture trace with usblyzer I have added a trace, if it is not valid or you need more of them, please tell me as fast as you can, because I am doing it with USBlyzer, which is free for 30 days... Hope it helps, looking for fast ACK :D
Please capture at least 3 sniffs with similar conditions, i.e. start capture on _clean_ boot, do capture of same event. Need them to analyze what part of traffic changes
Dear Sender, I will be out of office till 3rd Dec and will have very limited access to my emails. For urge matters pls email to; dgfemabuit@dhl.com For "very" urgent matters pls call me fm my mobile; +90 533 502 3090 Regards, Mucahid Zeyrek
Hi, I own a device with this reader and would like to help to get it supported. I am not a developer, but capable of entering console commands, testing an output, modifying a config file, compiling in a kernel module. I could also create a clean account that a developer could tunnel into if that helps. Let me know if i can help.
(In reply to comment #13) > Hi, I own a device with this reader and would like to help to get it > supported. I am not a developer, but capable of entering console commands, > testing an output, modifying a config file, compiling in a kernel module. I > could also create a clean account that a developer could tunnel into if that > helps. Let me know if i can help. Hi Andreas, As I already said, it's close to impossible to develop a driver without device available at hands. But I can guide someone who want to develop driver for libfprint.
Same here, elitebook 8440p Bus 001 Device 004: ID 138a:0007 Validity Sensors, Inc. VFS451 Fingerprint Reader
(In reply to Vasily Khoruzhick from comment #14) > (In reply to comment #13) > > Hi, I own a device with this reader and would like to help to get it > > supported. I am not a developer, but capable of entering console commands, > > testing an output, modifying a config file, compiling in a kernel module. I > > could also create a clean account that a developer could tunnel into if that > > helps. Let me know if i can help. > > Hi Andreas, > > As I already said, it's close to impossible to develop a driver without > device available at hands. But I can guide someone who want to develop > driver for libfprint. Roughly how much effort would it take to make this driver?
Created attachment 121731 [details] attachment-10894-0.html Dear Sender / Colleague, You will receive this Out of Office notification only once. I will be out of office between 15/FEB - 18/FEB due to biz travel and will have limited access to my emails. There might be some delays for my replies. Resume to work on 19/FEB. For "very" urgent matters pls call / text me fm my mobile B.Rgds, Mucahid Zeyrek +90 533 5023090 (GMT +3)
(In reply to ncdehnel from comment #16) > Roughly how much effort would it take to make this driver? Depends. If protocol is not encrypted and device doesn't require any fancy handshake, it takes 2-3 days for me.
I have a laptop with one of these devices and am thinking about either volunteering for instruction or mailing it to you for you to do it. I assume reverse engineering the device won't require destructive modification of it?
(In reply to ncdehnel from comment #19) > I have a laptop with one of these devices and am thinking about either > volunteering for instruction or mailing it to you for you to do it. I assume > reverse engineering the device won't require destructive modification of it? meant to reply to (In reply to Vasily Khoruzhick from comment #18) > (In reply to ncdehnel from comment #16) > > Roughly how much effort would it take to make this driver? > > Depends. If protocol is not encrypted and device doesn't require any fancy > handshake, it takes 2-3 days for me.
(In reply to ncdehnel from comment #19) > I have a laptop with one of these devices and am thinking about either > volunteering for instruction or mailing it to you for you to do it. I assume > reverse engineering the device won't require destructive modification of it? Usually I use VM with Windows in it and Linux host with wireshark to capture USB traffic. So it doesn't require any hw modifications at all.
I have one of these fingerprint readers. conor@Lappy:~$ lsusb | grep Validity Bus 001 Device 004: ID 138a:0007 Validity Sensors, Inc. VFS451 Fingerprint Reader In an HP Elitebook 8540w. I have never developed drivers before, but If USB captures would help in any way I can provide them. What conditions would need to be sniffed?
Created attachment 134944 [details] attachment-26161-0.html Dear Sender, You will receive this Out of Office notification only once. I will be out of office till 6th Nov due business travels, I will have very very limited access to my emails therefore there might be some delays for my replies. For "very" urgent matters pls call / text me fm my mobile B.Rgds, Mucahid Zeyrek +90 533 5023090 (GMT +1)
Created attachment 139761 [details] attachment-11812-0.html Dear Sender, You will receive this Out of Office notification only once !!! I'm no longer working for DPDHL as of 13th Apr 2018. For EMTO related questions/requests please contact with Charl.Joubert@dhl.com For any other request, incidents, IT Projects, problems and IT support pls contact with dgfemabuit@dhl.com For escalations Burak.Ertuna@dhl.com Best Regards, mucahid@zeyrek.org Best Regards, Mucahid Zeyrek
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/libfprint/libfprint/issues/69.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.