Please help me get my fingerprint sensor to work.
# cat /etc/redhat-release Fedora release 18 (Spherical Cow) # uname -a Linux laptop1 3.9.6-200.fc18.x86_64 #1 SMP Thu Jun 13 18:56:55 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux # yum list installed | grep fprint fprint_demo.x86_64 0.4-10.fc18.1 @fedora
fprintd.x86_64 0.4.1-4.fc18 @koji-override-1/$releasever fprintd-pam.x86_64 0.4.1-4.fc18 @koji-override-1/$releasever libfprint.x86_64 0.5.0-2.fc18 installed
libfprint-devel.x86_64 0.5.0-2.fc18 installed
Thank you in advance.
j
On Wed, Jun 26, 2013 at 4:03 AM, Jerome Yanga jerome.yanga@gmail.comwrote:
Please help me get my fingerprint sensor to work.
# cat /etc/redhat-release Fedora release 18 (Spherical Cow) # uname -a Linux laptop1 3.9.6-200.fc18.x86_64 #1 SMP Thu Jun 13 18:56:55 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux # yum list installed | grep fprint fprint_demo.x86_64 0.4-10.fc18.1 @fedora
fprintd.x86_64 0.4.1-4.fc18 @koji-override-1/$releasever fprintd-pam.x86_64 0.4.1-4.fc18 @koji-override-1/$releasever libfprint.x86_64 0.5.0-2.fc18 installed
libfprint-devel.x86_64 0.5.0-2.fc18 installed
I suggest you mention what model of laptop you have, or at least what the sensor hardware is. You might also be more specific about what "not working" means.
poc
Oops! I apologize for missing that information.
Laptop Model: HP ENVY dv6t-7300 CTO Quad Edition Notebook PC
Here is what I get from lsusb. # lsusb Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 138a:0018 Validity Sensors, Inc. Bus 001 Device 005: ID 046d:c06a Logitech, Inc. USB Optical Mouse Bus 001 Device 004: ID 064e:c334 Suyin Corp.
I believe the fingerprint reader is the one made by Validity Sensors, Inc.
Here is the verbose output. # lsusb -d 138a:0018 -v
Bus 001 Device 003: ID 138a:0018 Validity Sensors, Inc. Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 255 Vendor Specific Class bDeviceSubClass 17 bDeviceProtocol 255 bMaxPacketSize0 8 idVendor 0x138a Validity Sensors, Inc. idProduct 0x0018 bcdDevice 0.78 iManufacturer 0 iProduct 0 iSerial 1 3568a7d20eb9 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)
Regards, j
On Wed, Jun 26, 2013 at 1:22 AM, Patrick O'Callaghan pocallaghan@gmail.comwrote:
On Wed, Jun 26, 2013 at 4:03 AM, Jerome Yanga jerome.yanga@gmail.comwrote:
Please help me get my fingerprint sensor to work.
# cat /etc/redhat-release Fedora release 18 (Spherical Cow) # uname -a Linux laptop1 3.9.6-200.fc18.x86_64 #1 SMP Thu Jun 13 18:56:55 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux # yum list installed | grep fprint fprint_demo.x86_64 0.4-10.fc18.1 @fedora
fprintd.x86_64 0.4.1-4.fc18 @koji-override-1/$releasever fprintd-pam.x86_64 0.4.1-4.fc18 @koji-override-1/$releasever libfprint.x86_64 0.5.0-2.fc18 installed
libfprint-devel.x86_64 0.5.0-2.fc18 installed
I suggest you mention what model of laptop you have, or at least what the sensor hardware is. You might also be more specific about what "not working" means.
poc
-- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
On 06/26/2013 09:40 AM, Jerome Yanga issued this missive:
Oops! I apologize for missing that information.
Laptop Model: HP ENVY dv6t-7300 CTO Quad Edition Notebook PC
Here is what I get from lsusb. # lsusb Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 138a:0018 Validity Sensors, Inc. Bus 001 Device 005: ID 046d:c06a Logitech, Inc. USB Optical Mouse Bus 001 Device 004: ID 064e:c334 Suyin Corp.
I believe the fingerprint reader is the one made by Validity Sensors, Inc.
Here is the verbose output. # lsusb -d 138a:0018 -v
Bus 001 Device 003: ID 138a:0018 Validity Sensors, Inc. Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 255 Vendor Specific Class bDeviceSubClass 17 bDeviceProtocol 255 bMaxPacketSize0 8 idVendor 0x138a Validity Sensors, Inc. idProduct 0x0018 bcdDevice 0.78 iManufacturer 0 iProduct 0 iSerial 1 3568a7d20eb9 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)
That's useful, but what doesn't work? Does the kernel module for the sensor load (check the output of "dmesg" and "lsmod")? Is the fprint_demo not working? Can't you enroll any prints?
Just saying "help me get it to work" is rather vague. We can't help unless we know what's broken.
On Wed, Jun 26, 2013 at 1:22 AM, Patrick O'Callaghan <pocallaghan@gmail.com mailto:pocallaghan@gmail.com> wrote:
On Wed, Jun 26, 2013 at 4:03 AM, Jerome Yanga <jerome.yanga@gmail.com <mailto:jerome.yanga@gmail.com>> wrote: Please help me get my fingerprint sensor to work. # cat /etc/redhat-release Fedora release 18 (Spherical Cow) # uname -a Linux laptop1 3.9.6-200.fc18.x86_64 #1 SMP Thu Jun 13 18:56:55 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux # yum list installed | grep fprint fprint_demo.x86_64 0.4-10.fc18.1 @fedora fprintd.x86_64 0.4.1-4.fc18 @koji-override-1/$releasever fprintd-pam.x86_64 0.4.1-4.fc18 @koji-override-1/$releasever libfprint.x86_64 0.5.0-2.fc18 installed libfprint-devel.x86_64 0.5.0-2.fc18 installed I suggest you mention what model of laptop you have, or at least what the sensor hardware is. You might also be more specific about what "not working" means. poc -- users mailing list users@lists.fedoraproject.org <mailto:users@lists.fedoraproject.org> To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Here are the info you requested. :)
I get these errors when I attempt to use fprint.
$ fprintd-enroll list_devices failed: No devices available
fprint_demo shows "Status: No devices found"
/var/log/messages file only have these events. Jun 27 10:37:35 pc1 kernel: [ 2.923713] usb 1-1.1: New USB device found, idVendor=138a, idProduct=0018
This is what i see in dmesg. [ 2.837091] usb 1-1.1: new full-speed USB device number 3 using ehci-pci [ 2.923713] usb 1-1.1: New USB device found, idVendor=138a, idProduct=0018 [ 2.923716] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=1
I am not sure what I should be looking for in lsmod so I just pasted what I get. # lsmod Module Size Used by vboxpci 23194 0 vboxnetadp 25670 0 vboxnetflt 23479 0 vboxdrv 296411 3 vboxnetadp,vboxnetflt,vboxpci fuse 82252 3 ebtable_nat 12807 0 ipt_MASQUERADE 12880 1 nf_conntrack_netbios_ns 12665 0 nf_conntrack_broadcast 12527 1 nf_conntrack_netbios_ns ip6table_mangle 12700 1 ip6t_REJECT 12939 2 nf_conntrack_ipv6 18782 23 nf_defrag_ipv6 18205 1 nf_conntrack_ipv6 iptable_nat 13011 1 nf_nat_ipv4 13199 1 iptable_nat nf_nat 25642 3 ipt_MASQUERADE,nf_nat_ipv4,iptable_nat iptable_mangle 12695 1 nf_conntrack_ipv4 14808 20 nf_defrag_ipv4 12673 1 nf_conntrack_ipv4 xt_conntrack 12760 42 nf_conntrack 86438 9 nf_conntrack_netbios_ns,ipt_MASQUERADE,nf_nat,nf_nat_ipv4,xt_conntrack,nf_conntrack_broadcast,iptable_nat,nf_conntrack_ipv4,nf_conntrack_ipv6 ebtable_filter 12827 0 ebtables 30757 2 ebtable_nat,ebtable_filter bnep 19701 2 bluetooth 360184 7 bnep ip6table_filter 12815 1 ip6_tables 26808 2 ip6table_filter,ip6table_mangle be2iscsi 98059 0 iscsi_boot_sysfs 15641 1 be2iscsi bnx2i 54714 0 cnic 62777 1 bnx2i uio 19044 1 cnic cxgb4i 32879 0 cxgb4 126625 1 cxgb4i cxgb3i 32950 0 cxgb3 155598 1 cxgb3i mdio 13435 1 cxgb3 libcxgbi 56492 2 cxgb3i,cxgb4i ib_iser 37806 0 rdma_cm 42166 1 ib_iser ib_addr 13785 1 rdma_cm iw_cm 18221 1 rdma_cm ib_cm 41725 1 rdma_cm ib_sa 32955 2 rdma_cm,ib_cm ib_mad 42244 2 ib_cm,ib_sa ib_core 74064 6 rdma_cm,ib_cm,ib_sa,iw_cm,ib_mad,ib_iser iscsi_tcp 18333 0 libiscsi_tcp 24176 4 cxgb3i,cxgb4i,iscsi_tcp,libcxgbi libiscsi 50542 8 libiscsi_tcp,bnx2i,cxgb3i,cxgb4i,be2iscsi,iscsi_tcp,ib_iser,libcxgbi scsi_transport_iscsi 57595 8 bnx2i,be2iscsi,iscsi_tcp,ib_iser,libcxgbi,libiscsi arc4 12615 2 rt2800pci 18660 0 rt2800lib 64930 1 rt2800pci rt2x00pci 13083 1 rt2800pci rt2x00mmio 13306 1 rt2800pci rt2x00lib 66676 4 rt2x00pci,rt2800lib,rt2800pci,rt2x00mmio eeprom_93cx6 13130 1 rt2800pci mac80211 603815 3 rt2x00lib,rt2x00pci,rt2800lib vhost_net 33984 0 cfg80211 521315 2 mac80211,rt2x00lib snd_hda_codec_hdmi 41088 1 snd_hda_codec_idt 54555 1 snd_hda_intel 44021 5 snd_hda_codec 178680 3 snd_hda_codec_hdmi,snd_hda_codec_idt,snd_hda_intel rtsx_pci_sdmmc 23482 0 snd_hwdep 17650 1 snd_hda_codec uvcvideo 81006 0 videobuf2_vmalloc 13163 1 uvcvideo videobuf2_memops 13161 1 videobuf2_vmalloc videobuf2_core 38816 1 uvcvideo acpi_cpufreq 19612 1 mperf 12607 1 acpi_cpufreq iTCO_wdt 13480 0 rtsx_pci_ms 18151 0 snd_seq 64877 0 snd_seq_device 14136 1 snd_seq snd_pcm 98004 4 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel snd_page_alloc 18268 2 snd_pcm,snd_hda_intel i2c_i801 18135 0 videodev 121874 2 uvcvideo,videobuf2_core media 20444 2 uvcvideo,videodev mmc_core 116274 1 rtsx_pci_sdmmc memstick 16029 1 rtsx_pci_ms coretemp 13435 0 crc_ccitt 12613 1 rt2800lib snd_timer 28690 2 snd_pcm,snd_seq snd 79379 18 snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_hda_codec_idt,snd_pcm,snd_seq,snd_hda_codec,snd_hda_intel,snd_seq_device joydev 17377 0 tun 27097 1 vhost_net macvtap 18240 1 vhost_net macvlan 18775 1 macvtap iTCO_vendor_support 13419 1 iTCO_wdt mei 70834 0 rtsx_pci 33535 2 rtsx_pci_ms,rtsx_pci_sdmmc lpc_ich 16977 0 mfd_core 13182 2 lpc_ich,rtsx_pci hp_wmi 13945 0 sparse_keymap 13526 1 hp_wmi rfkill 21729 6 cfg80211,hp_wmi,bluetooth hp_accel 26012 0 lis3lv02d 19717 1 hp_accel soundcore 14491 1 snd input_polldev 13646 1 lis3lv02d microcode 23448 0 kvm_intel 137762 0 kvm 443356 1 kvm_intel uinput 17614 0 binfmt_misc 17463 1 nouveau 984080 1 i915 615435 3 ttm 79750 1 nouveau i2c_algo_bit 13257 2 i915,nouveau crc32_pclmul 13113 0 drm_kms_helper 46343 2 i915,nouveau crc32c_intel 22079 0 ghash_clmulni_intel 13259 0 drm 272623 7 ttm,i915,drm_kms_helper,nouveau r8169 67628 0 mii 13527 1 r8169 i2c_core 34096 7 drm,i915,i2c_i801,drm_kms_helper,i2c_algo_bit,nouveau,videodev mxm_wmi 12865 1 nouveau wmi 18697 3 hp_wmi,mxm_wmi,nouveau video 18991 2 i915,nouveau sunrpc 256729 1
Thank you for your patience.
j
On Thu, Jun 27, 2013 at 9:31 AM, Rick Stevens ricks@alldigital.com wrote:
On 06/26/2013 09:40 AM, Jerome Yanga issued this missive:
Oops! I apologize for missing that information.
Laptop Model: HP ENVY dv6t-7300 CTO Quad Edition Notebook PC
Here is what I get from lsusb. # lsusb Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 138a:0018 Validity Sensors, Inc. Bus 001 Device 005: ID 046d:c06a Logitech, Inc. USB Optical Mouse Bus 001 Device 004: ID 064e:c334 Suyin Corp.
I believe the fingerprint reader is the one made by Validity Sensors, Inc.
Here is the verbose output. # lsusb -d 138a:0018 -v
Bus 001 Device 003: ID 138a:0018 Validity Sensors, Inc. Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 255 Vendor Specific Class bDeviceSubClass 17 bDeviceProtocol 255 bMaxPacketSize0 8 idVendor 0x138a Validity Sensors, Inc. idProduct 0x0018 bcdDevice 0.78 iManufacturer 0 iProduct 0 iSerial 1 3568a7d20eb9 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)
That's useful, but what doesn't work? Does the kernel module for the sensor load (check the output of "dmesg" and "lsmod")? Is the fprint_demo not working? Can't you enroll any prints?
Just saying "help me get it to work" is rather vague. We can't help unless we know what's broken.
On Wed, Jun 26, 2013 at 1:22 AM, Patrick O'Callaghan
<pocallaghan@gmail.com mailto:pocallaghan@gmail.com**> wrote:
On Wed, Jun 26, 2013 at 4:03 AM, Jerome Yanga <jerome.yanga@gmail.com <mailto:jerome.yanga@gmail.com**>> wrote: Please help me get my fingerprint sensor to work. # cat /etc/redhat-release Fedora release 18 (Spherical Cow) # uname -a Linux laptop1 3.9.6-200.fc18.x86_64 #1 SMP Thu Jun 13 18:56:55 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux # yum list installed | grep fprint fprint_demo.x86_64 0.4-10.fc18.1 @fedora fprintd.x86_64 0.4.1-4.fc18 @koji-override-1/$releasever fprintd-pam.x86_64 0.4.1-4.fc18 @koji-override-1/$releasever libfprint.x86_64 0.5.0-2.fc18 installed libfprint-devel.x86_64 0.5.0-2.fc18 installed I suggest you mention what model of laptop you have, or at least what the sensor hardware is. You might also be more specific about what "not working" means. poc -- users mailing list users@lists.fedoraproject.org <mailto:users@lists.**fedoraproject.org<users@lists.fedoraproject.org>To unsubscribe or change subscription options: https://admin.fedoraproject.**org/mailman/listinfo/users<https://admin.fedoraproject.org/mailman/listinfo/users> Guidelines: http://fedoraproject.org/wiki/**Mailing_list_guidelines<http://fedoraproject.org/wiki/Mailing_list_guidelines> Have a question? Ask away: http://ask.fedoraproject.org-- ------------------------------**------------------------------**----------
- Rick Stevens, Systems Engineer, AllDigital ricks@alldigital.com -
- AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 -
-- When you don't know what to do, walk fast and look worried. -
------------------------------**------------------------------**----------
-- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.**org/mailman/listinfo/usershttps://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/**Mailing_list_guidelineshttp://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
On 27.06.2013 19:59, Jerome Yanga wrote:
Here are the info you requested. :)
I get these errors when I attempt to use fprint.
$ fprintd-enroll list_devices failed: No devices available
fprint_demo shows "Status: No devices found"
/var/log/messages file only have these events. Jun 27 10:37:35 pc1 kernel: [ 2.923713] usb 1-1.1: New USB device found, idVendor=138a, idProduct=0018
https://github.com/maffmeier/fprint_vfs5011 Don't top-post, s'il vous plaît.
poma
Thanks, Poma.
I have compiled and installed the code in the URL you have provided. However, I am still seeing the same issue.
Regards, j
On Thu, Jun 27, 2013 at 12:04 PM, poma pomidorabelisima@gmail.com wrote:
On 27.06.2013 19:59, Jerome Yanga wrote:
Here are the info you requested. :)
I get these errors when I attempt to use fprint.
$ fprintd-enroll list_devices failed: No devices available
fprint_demo shows "Status: No devices found"
/var/log/messages file only have these events. Jun 27 10:37:35 pc1 kernel: [ 2.923713] usb 1-1.1: New USB device
found,
idVendor=138a, idProduct=0018
https://github.com/maffmeier/fprint_vfs5011 Don't top-post, s'il vous plaît.
poma
On 06.07.2013 11:31, Jerome Yanga wrote:
Thanks, Poma.
I have compiled and installed the code in the URL you have provided. However, I am still seeing the same issue.
Don't top-post, s'il vous plaît.
That is a library part - 'libfprint', follows a service part - 'fprintd'. ;)
poma
On Mon, Jul 8, 2013 at 1:40 AM, poma pomidorabelisima@gmail.com wrote:
On 06.07.2013 11:31, Jerome Yanga wrote:
Thanks, Poma.
I have compiled and installed the code in the URL you have provided. However, I am still seeing the same issue.
Don't top-post, s'il vous plaît.
That is a library part - 'libfprint', follows a service part - 'fprintd'. ;)
poma
I didn't realize that the link to fprintd was not created by the libfprint install. I created a symlink for libfprint.so.0 and fprintd works now. Woohoo! Thanks.
regards, j
On 07/08/2013 03:25 PM, Jerome Yanga wrote:
On Mon, Jul 8, 2013 at 1:40 AM, poma <pomidorabelisima@gmail.com mailto:pomidorabelisima@gmail.com> wrote:
On 06.07.2013 11:31, Jerome Yanga wrote: > Thanks, Poma. > > I have compiled and installed the code in the URL you have provided. > However, I am still seeing the same issue. Don't top-post, s'il vous plaît. That is a library part - 'libfprint', follows a service part - 'fprintd'. ;) pomaI didn't realize that the link to fprintd was not created by the libfprint install. I created a symlink for libfprint.so.0 and fprintd works now. Woohoo! Thanks.
regards, j
Hi Jerome,
Do you know what is the difference between this library that you have compiled and the packages in Fedora? I'm asking because I think it is the same project.
I also have a Validity Sensors, which also doesn't work, but mine is a bit different than yours:
$ lsusb | grep -i finger Bus 001 Device 004: ID 138a:0008 Validity Sensors, Inc. VFS300 Fingerprint Reader
$ lsusb -d 138a:0008 -v Bus 001 Device 004: ID 138a:0008 Validity Sensors, Inc. VFS300 Fingerprint Reader Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 255 Vendor Specific Class bDeviceSubClass 16 bDeviceProtocol 255 bMaxPacketSize0 8 idVendor 0x138a Validity Sensors, Inc. idProduct 0x0008 VFS300 Fingerprint Reader bcdDevice c.90 iManufacturer 0 iProduct 0 iSerial 1 bNumConfigurations 1 ..........
These are the packages I have installed:
$ rpm -qa | grep fprint fprintd-0.5.0-1.fc19.x86_64 fprint_demo-0.4-12.fc19.1.x86_64 fprintd-pam-0.5.0-1.fc19.x86_64 libfprint-0.5.0-2.fc19.x86_64
The package in Fedora crashes when I'm configuring my fingerprint. Would you show me the steps you followed to compile the library?
Regards, Germán.
On Mon, Jul 8, 2013 at 1:40 PM, "Germán A. Racca" german.racca@gmail.comwrote:
On 07/08/2013 03:25 PM, Jerome Yanga wrote:
On Mon, Jul 8, 2013 at 1:40 AM, poma <pomidorabelisima@gmail.com <mailto:pomidorabelisima@**gmail.com pomidorabelisima@gmail.com>> wrote:
On 06.07.2013 11:31, Jerome Yanga wrote: > Thanks, Poma. > > I have compiled and installed the code in the URL you haveprovided. > However, I am still seeing the same issue.
Don't top-post, s'il vous plaît. That is a library part - 'libfprint', follows a service part - 'fprintd'. ;) pomaI didn't realize that the link to fprintd was not created by the libfprint install. I created a symlink for libfprint.so.0 and fprintd works now. Woohoo! Thanks.
regards, j
Hi Jerome,
Do you know what is the difference between this library that you have compiled and the packages in Fedora? I'm asking because I think it is the same project.
I also have a Validity Sensors, which also doesn't work, but mine is a bit different than yours:
$ lsusb | grep -i finger Bus 001 Device 004: ID 138a:0008 Validity Sensors, Inc. VFS300 Fingerprint Reader
$ lsusb -d 138a:0008 -v Bus 001 Device 004: ID 138a:0008 Validity Sensors, Inc. VFS300 Fingerprint Reader
Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 255 Vendor Specific Class bDeviceSubClass 16
bDeviceProtocol 255 bMaxPacketSize0 8 idVendor 0x138a Validity Sensors, Inc. idProduct 0x0008 VFS300 Fingerprint Reader bcdDevice c.90
iManufacturer 0 iProduct 0 iSerial 1 bNumConfigurations 1 ..........
These are the packages I have installed:
$ rpm -qa | grep fprint fprintd-0.5.0-1.fc19.x86_64 fprint_demo-0.4-12.fc19.1.x86_**64 fprintd-pam-0.5.0-1.fc19.x86_**64 libfprint-0.5.0-2.fc19.x86_64
The package in Fedora crashes when I'm configuring my fingerprint. Would you show me the steps you followed to compile the library?
Regards, Germán.
-- Germán A. Racca Fedora Package Maintainer https://fedoraproject.org/**wiki/User:Skytuxhttps://fedoraproject.org/wiki/User:Skytux
-- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.**org/mailman/listinfo/usershttps://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/**Mailing_list_guidelineshttp://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
German,
I do not think that you need to compile the newest driver for your sensor as it already exists for your hardware. Just to make sure, please provide the output to the command below.
grep 138a /usr/lib/udev/rules.d/60-fprint-autosuspend.rules
Nevertheless, I merely followed the instructions in INSTALL file that came with the driver.
https://github.com/maffmeier/fprint_vfs5011/blob/master/INSTALL
In my case, I simple ran the command below.
./configure; make; make install
regards, j
On 07/08/2013 05:57 PM, Jerome Yanga wrote:
On Mon, Jul 8, 2013 at 1:40 PM, "Germán A. Racca" <german.racca@gmail.com mailto:german.racca@gmail.com> wrote:
On 07/08/2013 03:25 PM, Jerome Yanga wrote: On Mon, Jul 8, 2013 at 1:40 AM, poma <pomidorabelisima@gmail.com <mailto:pomidorabelisima@gmail.com> <mailto:pomidorabelisima@__gmail.com <mailto:pomidorabelisima@gmail.com>>> wrote: On 06.07.2013 11:31, Jerome Yanga wrote: > Thanks, Poma. > > I have compiled and installed the code in the URL you have provided. > However, I am still seeing the same issue. Don't top-post, s'il vous plaît. That is a library part - 'libfprint', follows a service part - 'fprintd'. ;) poma I didn't realize that the link to fprintd was not created by the libfprint install. I created a symlink for libfprint.so.0 and fprintd works now. Woohoo! Thanks. regards, j Hi Jerome, Do you know what is the difference between this library that you have compiled and the packages in Fedora? I'm asking because I think it is the same project. I also have a Validity Sensors, which also doesn't work, but mine is a bit different than yours: $ lsusb | grep -i finger Bus 001 Device 004: ID 138a:0008 Validity Sensors, Inc. VFS300 Fingerprint Reader $ lsusb -d 138a:0008 -v Bus 001 Device 004: ID 138a:0008 Validity Sensors, Inc. VFS300 Fingerprint Reader Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 255 Vendor Specific Class bDeviceSubClass 16 bDeviceProtocol 255 bMaxPacketSize0 8 idVendor 0x138a Validity Sensors, Inc. idProduct 0x0008 VFS300 Fingerprint Reader bcdDevice c.90 iManufacturer 0 iProduct 0 iSerial 1 bNumConfigurations 1 .......... These are the packages I have installed: $ rpm -qa | grep fprint fprintd-0.5.0-1.fc19.x86_64 fprint_demo-0.4-12.fc19.1.x86___64 fprintd-pam-0.5.0-1.fc19.x86___64 libfprint-0.5.0-2.fc19.x86_64 The package in Fedora crashes when I'm configuring my fingerprint. Would you show me the steps you followed to compile the library? Regards, Germán. -- Germán A. Racca Fedora Package Maintainer https://fedoraproject.org/__wiki/User:Skytux <https://fedoraproject.org/wiki/User:Skytux> -- users mailing list users@lists.fedoraproject.org <mailto:users@lists.fedoraproject.org> To unsubscribe or change subscription options: https://admin.fedoraproject.__org/mailman/listinfo/users <https://admin.fedoraproject.org/mailman/listinfo/users> Guidelines: http://fedoraproject.org/wiki/__Mailing_list_guidelines <http://fedoraproject.org/wiki/Mailing_list_guidelines> Have a question? Ask away: http://ask.fedoraproject.orgGerman,
I do not think that you need to compile the newest driver for your sensor as it already exists for your hardware. Just to make sure, please provide the output to the command below.
grep 138a /usr/lib/udev/rules.d/60-fprint-autosuspend.rules
Nevertheless, I merely followed the instructions in INSTALL file that came with the driver.
https://github.com/maffmeier/fprint_vfs5011/blob/master/INSTALL
In my case, I simple ran the command below.
./configure; make; make install
regards, j
Thanks for your prompt reply Jerome.
This is the output you asked for:
$ grep 138a /usr/lib/udev/rules.d/60-fprint-autosuspend.rules SUBSYSTEM=="usb", ATTRS{idVendor}=="138a", ATTRS{idProduct}=="0001", ATTRS{dev}=="*", ATTR{power/control}="auto" SUBSYSTEM=="usb", ATTRS{idVendor}=="138a", ATTRS{idProduct}=="0005", ATTRS{dev}=="*", ATTR{power/control}="auto" SUBSYSTEM=="usb", ATTRS{idVendor}=="138a", ATTRS{idProduct}=="0008", ATTRS{dev}=="*", ATTR{power/control}="auto"
Regards, Germán.
On Mon, Jul 8, 2013 at 2:02 PM, "Germán A. Racca" german.racca@gmail.comwrote:
On 07/08/2013 05:57 PM, Jerome Yanga wrote:
On Mon, Jul 8, 2013 at 1:40 PM, "Germán A. Racca" <german.racca@gmail.com mailto:german.racca@gmail.com**> wrote:
On 07/08/2013 03:25 PM, Jerome Yanga wrote: On Mon, Jul 8, 2013 at 1:40 AM, poma <pomidorabelisima@gmail.com <mailto:pomidorabelisima@**gmail.com <pomidorabelisima@gmail.com><mailto:pomidorabelisima@__gma**il.com <http://gmail.com> <mailto:pomidorabelisima@**gmail.com <pomidorabelisima@gmail.com>>>>wrote:
On 06.07.2013 11:31, Jerome Yanga wrote: > Thanks, Poma. > > I have compiled and installed the code in the URL you have provided. > However, I am still seeing the same issue. Don't top-post, s'il vous plaît. That is a library part - 'libfprint', follows a service part - 'fprintd'. ;) poma I didn't realize that the link to fprintd was not created by the libfprint install. I created a symlink for libfprint.so.0 and fprintd works now. Woohoo! Thanks. regards, j Hi Jerome, Do you know what is the difference between this library that you have compiled and the packages in Fedora? I'm asking because I think it is the same project. I also have a Validity Sensors, which also doesn't work, but mine is a bit different than yours: $ lsusb | grep -i finger Bus 001 Device 004: ID 138a:0008 Validity Sensors, Inc. VFS300 Fingerprint Reader $ lsusb -d 138a:0008 -v Bus 001 Device 004: ID 138a:0008 Validity Sensors, Inc. VFS300 Fingerprint Reader Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 255 Vendor Specific Class bDeviceSubClass 16 bDeviceProtocol 255 bMaxPacketSize0 8 idVendor 0x138a Validity Sensors, Inc. idProduct 0x0008 VFS300 Fingerprint Reader bcdDevice c.90 iManufacturer 0 iProduct 0 iSerial 1 bNumConfigurations 1 .......... These are the packages I have installed: $ rpm -qa | grep fprint fprintd-0.5.0-1.fc19.x86_64 fprint_demo-0.4-12.fc19.1.x86_**__64 fprintd-pam-0.5.0-1.fc19.x86__**_64 libfprint-0.5.0-2.fc19.x86_64 The package in Fedora crashes when I'm configuring my fingerprint. Would you show me the steps you followed to compile the library? Regards, Germán. -- Germán A. Racca Fedora Package Maintainer https://fedoraproject.org/__**wiki/User:Skytux<https://fedoraproject.org/__wiki/User:Skytux> <https://fedoraproject.org/**wiki/User:Skytux<https://fedoraproject.org/wiki/User:Skytux>-- users mailing list users@lists.fedoraproject.org <mailto:users@lists.**fedoraproject.org<users@lists.fedoraproject.org>To unsubscribe or change subscription options: https://admin.fedoraproject.__**org/mailman/listinfo/users <https://admin.fedoraproject.**org/mailman/listinfo/users<https://admin.fedoraproject.org/mailman/listinfo/users>Guidelines: http://fedoraproject.org/wiki/**__Mailing_list_guidelines<http://fedoraproject.org/wiki/__Mailing_list_guidelines> <http://fedoraproject.org/**wiki/Mailing_list_guidelines<http://fedoraproject.org/wiki/Mailing_list_guidelines>Have a question? Ask away: http://ask.fedoraproject.orgGerman,
I do not think that you need to compile the newest driver for your sensor as it already exists for your hardware. Just to make sure, please provide the output to the command below.
grep 138a /usr/lib/udev/rules.d/60-**fprint-autosuspend.rules
Nevertheless, I merely followed the instructions in INSTALL file that came with the driver.
https://github.com/maffmeier/**fprint_vfs5011/blob/master/**INSTALLhttps://github.com/maffmeier/fprint_vfs5011/blob/master/INSTALL
In my case, I simple ran the command below.
./configure; make; make install
regards, j
Thanks for your prompt reply Jerome.
This is the output you asked for:
$ grep 138a /usr/lib/udev/rules.d/60-**fprint-autosuspend.rules SUBSYSTEM=="usb", ATTRS{idVendor}=="138a", ATTRS{idProduct}=="0001", ATTRS{dev}=="*", ATTR{power/control}="auto" SUBSYSTEM=="usb", ATTRS{idVendor}=="138a", ATTRS{idProduct}=="0005", ATTRS{dev}=="*", ATTR{power/control}="auto" SUBSYSTEM=="usb", ATTRS{idVendor}=="138a", ATTRS{idProduct}=="0008", ATTRS{dev}=="*", ATTR{power/control}="auto"
Regards, Germán.
-- Germán A. Racca Fedora Package Maintainer https://fedoraproject.org/**wiki/User:Skytuxhttps://fedoraproject.org/wiki/User:Skytux -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.**org/mailman/listinfo/usershttps://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/**Mailing_list_guidelineshttp://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
German,
That last line from your output tells me that you shouldn't need to compile the new driver.
The output of your lsusb...
Bus 001 Device 004: ID 138a:0008 Validity Sensors, Inc. VFS300 Fingerprint Reader
coincides with the driver that is loaded in your machine...
SUBSYSTEM=="usb", ATTRS{idVendor}=="138a", ATTRS{idProduct}=="0008", ATTRS{dev}=="*", ATTR{power/control}="auto"
If you are not root, run sudo fprint_demo. This will at least tell you if your system can see your hardware. You can even test it by clicking on the Enroll button. If this works, all you have to do is run fprintd-enroll as the user that you will use your sensor for.
regards, j
On 07/08/2013 06:40 PM, Jerome Yanga wrote:
On Mon, Jul 8, 2013 at 2:02 PM, "Germán A. Racca" <german.racca@gmail.com mailto:german.racca@gmail.com> wrote:
On 07/08/2013 05:57 PM, Jerome Yanga wrote: On Mon, Jul 8, 2013 at 1:40 PM, "Germán A. Racca" <german.racca@gmail.com <mailto:german.racca@gmail.com> <mailto:german.racca@gmail.com <mailto:german.racca@gmail.com>__>> wrote: On 07/08/2013 03:25 PM, Jerome Yanga wrote: On Mon, Jul 8, 2013 at 1:40 AM, poma <pomidorabelisima@gmail.com <mailto:pomidorabelisima@gmail.com> <mailto:pomidorabelisima@__gmail.com <mailto:pomidorabelisima@gmail.com>> <mailto:pomidorabelisima@ <mailto:pomidorabelisima@>__gma__il.com <http://gmail.com> <mailto:pomidorabelisima@__gmail.com <mailto:pomidorabelisima@gmail.com>>>> wrote: On 06.07.2013 11:31, Jerome Yanga wrote: > Thanks, Poma. > > I have compiled and installed the code in the URL you have provided. > However, I am still seeing the same issue. Don't top-post, s'il vous plaît. That is a library part - 'libfprint', follows a service part - 'fprintd'. ;) poma I didn't realize that the link to fprintd was not created by the libfprint install. I created a symlink for libfprint.so.0 and fprintd works now. Woohoo! Thanks. regards, j Hi Jerome, Do you know what is the difference between this library that you have compiled and the packages in Fedora? I'm asking because I think it is the same project. I also have a Validity Sensors, which also doesn't work, but mine is a bit different than yours: $ lsusb | grep -i finger Bus 001 Device 004: ID 138a:0008 Validity Sensors, Inc. VFS300 Fingerprint Reader $ lsusb -d 138a:0008 -v Bus 001 Device 004: ID 138a:0008 Validity Sensors, Inc. VFS300 Fingerprint Reader Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 255 Vendor Specific Class bDeviceSubClass 16 bDeviceProtocol 255 bMaxPacketSize0 8 idVendor 0x138a Validity Sensors, Inc. idProduct 0x0008 VFS300 Fingerprint Reader bcdDevice c.90 iManufacturer 0 iProduct 0 iSerial 1 bNumConfigurations 1 .......... These are the packages I have installed: $ rpm -qa | grep fprint fprintd-0.5.0-1.fc19.x86_64 fprint_demo-0.4-12.fc19.1.x86_____64 fprintd-pam-0.5.0-1.fc19.x86_____64 libfprint-0.5.0-2.fc19.x86_64 The package in Fedora crashes when I'm configuring my fingerprint. Would you show me the steps you followed to compile the library? Regards, Germán. -- Germán A. Racca Fedora Package Maintainer https://fedoraproject.org/____wiki/User:Skytux <https://fedoraproject.org/__wiki/User:Skytux> <https://fedoraproject.org/__wiki/User:Skytux <https://fedoraproject.org/wiki/User:Skytux>> -- users mailing list users@lists.fedoraproject.org <mailto:users@lists.fedoraproject.org> <mailto:users@lists.__fedoraproject.org <mailto:users@lists.fedoraproject.org>> To unsubscribe or change subscription options: https://admin.fedoraproject.____org/mailman/listinfo/users <https://admin.fedoraproject.__org/mailman/listinfo/users <https://admin.fedoraproject.org/mailman/listinfo/users>> Guidelines: http://fedoraproject.org/wiki/____Mailing_list_guidelines <http://fedoraproject.org/wiki/__Mailing_list_guidelines> <http://fedoraproject.org/__wiki/Mailing_list_guidelines <http://fedoraproject.org/wiki/Mailing_list_guidelines>> Have a question? Ask away: http://ask.fedoraproject.org German, I do not think that you need to compile the newest driver for your sensor as it already exists for your hardware. Just to make sure, please provide the output to the command below. grep 138a /usr/lib/udev/rules.d/60-__fprint-autosuspend.rules Nevertheless, I merely followed the instructions in INSTALL file that came with the driver. https://github.com/maffmeier/__fprint_vfs5011/blob/master/__INSTALL <https://github.com/maffmeier/fprint_vfs5011/blob/master/INSTALL> In my case, I simple ran the command below. ./configure; make; make install regards, j Thanks for your prompt reply Jerome. This is the output you asked for: $ grep 138a /usr/lib/udev/rules.d/60-__fprint-autosuspend.rules SUBSYSTEM=="usb", ATTRS{idVendor}=="138a", ATTRS{idProduct}=="0001", ATTRS{dev}=="*", ATTR{power/control}="auto" SUBSYSTEM=="usb", ATTRS{idVendor}=="138a", ATTRS{idProduct}=="0005", ATTRS{dev}=="*", ATTR{power/control}="auto" SUBSYSTEM=="usb", ATTRS{idVendor}=="138a", ATTRS{idProduct}=="0008", ATTRS{dev}=="*", ATTR{power/control}="auto" Regards, Germán. -- Germán A. Racca Fedora Package Maintainer https://fedoraproject.org/__wiki/User:Skytux <https://fedoraproject.org/wiki/User:Skytux> -- users mailing list users@lists.fedoraproject.org <mailto:users@lists.fedoraproject.org> To unsubscribe or change subscription options: https://admin.fedoraproject.__org/mailman/listinfo/users <https://admin.fedoraproject.org/mailman/listinfo/users> Guidelines: http://fedoraproject.org/wiki/__Mailing_list_guidelines <http://fedoraproject.org/wiki/Mailing_list_guidelines> Have a question? Ask away: http://ask.fedoraproject.orgGerman,
That last line from your output tells me that you shouldn't need to compile the new driver.
The output of your lsusb...
Bus 001 Device 004: ID 138a:0008 Validity Sensors, Inc. VFS300 Fingerprint Reader
coincides with the driver that is loaded in your machine...
SUBSYSTEM=="usb", ATTRS{idVendor}=="138a", ATTRS{idProduct}=="0008", ATTRS{dev}=="*", ATTR{power/control}="auto"
If you are not root, run sudo fprint_demo. This will at least tell you if your system can see your hardware. You can even test it by clicking on the Enroll button. If this works, all you have to do is run fprintd-enroll as the user that you will use your sensor for.
regards, j
Jerome,
Yes, I understand. I can successfully open the GUI to configure my fingerprint, but while scanning my finger, the program crashes... that's the reason I asked the steps you followed to make your fingerprint reader to work... I think I can't do anything more than that... I also filed a bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=982018
Anyway, thank you very much Jerome!
All the best, Germán.
Dear Jerome Yanga,
Can you please specify your symlink? I've got the same problem with the same sensor, but I couldn't get it to work!
regards
-- View this message in context: http://fedora.12.x6.nabble.com/138a-0018-Validity-Sensors-will-not-work-tp50... Sent from the Fedora List mailing list archive at Nabble.com.
-
"Germán A. Racca" -
Jerome Yanga -
nimra98 -
Patrick O'Callaghan -
poma -
Rick Stevens