Alexander Botev | 21 Feb 13:08 2015
Picon

Re: fprtind and PAM on wake from LID open

Hi,

So I have the problem that often after LID open it seems that fprintd does not seem to respond to the PAM module, thus I have about 30 sec of no way of logging in my session, which is a bit frustrating - I get the screen, but no option for finger verification or password. After ~30-40sec I get the password field finally, but note that fprintd has 10 sec timeout in the PAM module. After putting out debug on I got this:

Feb 21 10:04:44 botev-ThinkPad-T440 systemd-logind[556]: Lid closed.
Feb 21 10:04:44 botev-ThinkPad-T440 systemd-logind[556]: Suspending...
Feb 21 10:16:06 botev-ThinkPad-T440 unity[2100]: pam_fprintd(unity): timeout specified as: 10
Feb 21 10:16:06 botev-ThinkPad-T440 systemd-logind[556]: Operation finished.
Feb 21 10:16:06 botev-ThinkPad-T440 systemd-logind[556]: Lid opened.
Feb 21 10:16:32 botev-ThinkPad-T440 unity[2100]: pam_fprintd(unity): get_devices failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

Any idea how to fix this or what exactly is the issue?

Best regards,
Alex

On 21 February 2015 at 12:01, Alexander Botev <botevmg <at> gmail.com> wrote:
Hi,

So I have the problem that often after LID open it seems that fprintd does not seem to respond to the PAM module, thus I have about 30 sec of no way of logging in my session, which is a bit frustrating - I get the screen, but no option for finger verification or password. After ~30-40sec I get the password field finally, but note that fprintd has 10 sec timeout in the PAM module. After putting out debug on I got this:

Feb 21 10:04:44 botev-ThinkPad-T440 systemd-logind[556]: Lid closed.
Feb 21 10:04:44 botev-ThinkPad-T440 systemd-logind[556]: Suspending...
Feb 21 10:16:06 botev-ThinkPad-T440 unity[2100]: pam_fprintd(unity): timeout specified as: 10
Feb 21 10:16:06 botev-ThinkPad-T440 systemd-logind[556]: Operation finished.
Feb 21 10:16:06 botev-ThinkPad-T440 systemd-logind[556]: Lid opened.
Feb 21 10:16:32 botev-ThinkPad-T440 unity[2100]: pam_fprintd(unity): get_devices failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

Any idea how to fix this or what exactly is the issue?

Best regards,
Alex

_______________________________________________
fprint mailing list
fprint <at> lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/fprint
Carlos Olmedo Escobar | 6 Feb 17:22 2015
Picon

[PATCH vfs101] Logical conjunction always evaluates to false.

Signed-off-by: Carlos Olmedo Escobar <carlos.olmedo.e <at> gmail.com>
---
 libfprint/drivers/vfs101.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/libfprint/drivers/vfs101.c b/libfprint/drivers/vfs101.c
index db0b06e..84624eb 100644
--- a/libfprint/drivers/vfs101.c
+++ b/libfprint/drivers/vfs101.c
 <at>  <at>  -186,7 +186,7  <at>  <at>  static int result_codes[2][RESULT_COUNT] =
 static int result_code(struct fp_img_dev *dev, int result)
 {
 	/* Check result value */
-	if (result < 0 && result >= RESULT_COUNT)
+	if (result < 0 || result >= RESULT_COUNT)
 		return result;

 	/* Return result code */
--

-- 
2.1.4

_______________________________________________
fprint mailing list
fprint <at> lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/fprint
Bastien Nocera | 3 Feb 17:45 2015
Picon

fprintd and libfprint 0.6.0 released

Hey,

libfprint NEWS
--------------

2015-02-03: v0.6.0 release

* Drivers:
  - Reduce duplication between AES3500 and AES4000 drivers and 
    add support for AES3500 device
  - Add support for UPEK 147e:2020 and Upek Eikon 2 devices
  - Add EgisTec ES603 driver
  - Add VFS5011 driver
  - Always perform 5 scans for image enrollment
  - Better verification with AES1660 driver
  - Better verification for a number of AES drivers

* Library:
  - Always use Pixman for image manipulation, gdk-pixbuf and ImageMagick
    are not supported any more.

* Udev rules:
  - Fix warning when USB hub or system does not support power management

fprintd NEWS
------------

version 0.6.0:
- Fix warning in fprintd.pod file
- Reduce logging during normal operation
- Fix eventfd leak in PAM module
- List possible values for finger when enrolling
- Fix possible crash in fprintd-verify
- Fix listing and deleting fingerprints when there's more than
  one reader available

URLs
----

http://people.freedesktop.org/~hadess/libfprint-0.6.0.tar.xz
http://people.freedesktop.org/~hadess/fprintd-0.6.0.tar.xz

Cheers

_______________________________________________
fprint mailing list
fprint <at> lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/fprint
Per-Ola Gustavsson | 31 Dec 19:15 2014
Picon

vfs5011 support

I had a look at the vfs5011. I got it working by removing the line 770
in file libfprint/drivers/vfs5011.c --"RECV(VFS5011_IN_ENDPOINT_CTRL2,
8)". As stated in the comment below in the c file, somehow it only
works in the windows driver. Strangely about one success in four tries
in libfprint on my machine. (I wouldn't be surprised if there is
something weird with the (Intel) usb bus/driver.) If there is a
timeout in the communication with the usb device libfprint tries to
g_malloc0 (or some kind of malloc) 2^64 - 4 bytes of data, naturally
this fails. I cannot find any code where this could occur.

Enroll stages is limited to one, makes it fail often. A work around is
to enroll using the same finger as several different using
fprintd-enroll -f.

Btw, the libfprint "SSM: sequential state machine" is quite flawed.
Why isn't there a normal message loop system and threading? Maybe glib
style? I haven't looked deeply into poll.c but I have a hunch it's
functionality should be reimplemented in a very different way.

vfs5011.c doesn't handle libusb async calls in a correct or polite
manner. It hi'jacks the thread of libusb and fills it's stack with
recursive calls and memory allocations. I believe this is causing race
conditions and other anomalies, at least noticed in the malloc fail
described above. I haven't looked at any other drivers than vfs5011
but I believe SSM can be improved to handle async callbacks and
threads (and race conditions) without breaking the driver interface.
It might not be urgent but it obviously is crashing in an unintended
way if anything unexpected occurs.

I got a bit offtopic here... I guess no one really is using their
finger print reader anyway.

(I have Thinkpad X1 Carbon 2:nd gen 20A8 for the record)

Per-Ola Gustavsson
http://marsba.se

>
> Hi Frank, Please try to compile and test libfprint from
> https://github.com/anarsoul/libfprint I have no vfs5011 hardware, and I'd like to be sure that everything
> from git master is working before pushing it to fd.o and asking
> Bastien to make a release. Thanks! Regards,
> Vasily On Thu, Dec 18, 2014 at 11:52 PM, Dr. No
> <bartsimpson at betriebsdirektor.de> wrote:
> > Hi Vasily,
> > yes the patch apply to the 0.5.1 version.
> > My system is an Fedora 21.
> >
> > I can't seen any crashes, only USB errors:
> >
> > wrong finger:
> > Dez 18 21:33:44 XXXXXX dbus[999]: [system] Activating via systemd:
> > service name='net.reactivated.Fprint' unit='fprintd.service'
> > Dez 18 21:33:44 XXXXXX dbus[999]: [system] Successfully activated
> > service 'net.reactivated.Fprint'
> > Dez 18 21:33:44 XXXXXX fprintd[3524]: Launching FprintObject
> > Dez 18 21:33:44 XXXXXX fprintd[3524]: ** Message: D-Bus service launched
> > with name: net.reactivated.Fprint
> > Dez 18 21:33:44 XXXXXX fprintd[3524]: ** Message: entering main loop
> > Dez 18 21:33:44 XXXXXX fprintd[3524]: ** Message: user 'frank' claiming
> > the device: 0
> > Dez 18 21:33:45 XXXXXX fprintd[3524]: ** Message: now monitoring fd 15
> > Dez 18 21:33:45 XXXXXX kernel: usb 2-7: reset full-speed USB device
> > number 3 using xhci_hcd
> > Dez 18 21:33:45 XXXXXX kernel: xhci_hcd 0000:00:14.0: Setup ERROR: setup
> > context command for slot 2.
> > Dez 18 21:33:45 XXXXXX kernel: usb 2-7: hub failed to enable device,
> > error -22
> > Dez 18 21:33:45 XXXXXX kernel: usb 2-7: reset full-speed USB device
> > number 3 using xhci_hcd
> > Dez 18 21:33:45 XXXXXX kernel: xhci_hcd 0000:00:14.0: Setup ERROR: setup
> > context command for slot 2.
> > Dez 18 21:33:45 XXXXXX kernel: usb 2-7: hub failed to enable device,
> > error -22
> > Dez 18 21:33:45 XXXXXX kernel: usb 2-7: reset full-speed USB device
> > number 3 using xhci_hcd
> > Dez 18 21:33:45 XXXXXX kernel: xhci_hcd 0000:00:14.0: xHCI
> > xhci_drop_endpoint called with disabled ep ffff880424b5b400
> > Dez 18 21:33:45 XXXXXX kernel: xhci_hcd 0000:00:14.0: xHCI
> > xhci_drop_endpoint called with disabled ep ffff880424b5b448
> > Dez 18 21:33:45 XXXXXX kernel: xhci_hcd 0000:00:14.0: xHCI
> > xhci_drop_endpoint called with disabled ep ffff880424b5b490
> > Dez 18 21:33:45 XXXXXX kernel: xhci_hcd 0000:00:14.0: xHCI
> > xhci_drop_endpoint called with disabled ep ffff880424b5b4d8
> > Dez 18 21:33:46 XXXXXX fprintd[3524]: ** Message: device 0 claim status 0
> > Dez 18 21:33:46 XXXXXX fprintd[3524]: ** Message: adding finger 7 to the
> > gallery
> > Dez 18 21:33:46 XXXXXX fprintd[3524]: ** Message: start identification
> > device 0
> > Dez 18 21:33:46 XXXXXX kernel: xhci_hcd 0000:00:14.0: WARN Event TRB for
> > slot 2 ep 4 with no TDs queued?
> > Dez 18 21:34:35 XXXXXX kernel: xhci_hcd 0000:00:14.0: WARN Event TRB for
> > slot 2 ep 4 with no TDs queued?
> > Dez 18 21:34:35 XXXXXX fprintd[3524]: ** Message: identify_cb: result
> > verify-no-match (0)
> > Dez 18 21:34:35 XXXXXX fprintd[3524]: ** Message: no longer monitoring fd 15
> > Dez 18 21:34:35 XXXXXX fprintd[3524]: ** Message: released device 0
> > Dez 18 21:35:05 XXXXXX fprintd[3524]: ** Message: No devices in use, exit
> >
> >
> > right finger:
> > Dez 18 21:36:27 XXXXXX fprintd[3546]: ** Message: user 'frank' claiming
> > the device: 0
> > Dez 18 21:36:27 XXXXXX fprintd[3546]: ** Message: now monitoring fd 15
> > Dez 18 21:36:27 XXXXXX kernel: usb 2-7: reset full-speed USB device
> > number 3 using xhci_hcd
> > Dez 18 21:36:27 XXXXXX kernel: xhci_hcd 0000:00:14.0: Setup ERROR: setup
> > context command for slot 2.
> > Dez 18 21:36:27 XXXXXX kernel: usb 2-7: hub failed to enable device,
> > error -22
> > Dez 18 21:36:27 XXXXXX kernel: usb 2-7: reset full-speed USB device
> > number 3 using xhci_hcd
> > Dez 18 21:36:27 XXXXXX kernel: xhci_hcd 0000:00:14.0: Setup ERROR: setup
> > context command for slot 2.
> > Dez 18 21:36:27 XXXXXX kernel: usb 2-7: hub failed to enable device,
> > error -22
> > Dez 18 21:36:28 XXXXXX kernel: usb 2-7: reset full-speed USB device
> > number 3 using xhci_hcd
> > Dez 18 21:36:28 XXXXXX kernel: xhci_hcd 0000:00:14.0: xHCI
> > xhci_drop_endpoint called with disabled ep ffff880424b5b400
> > Dez 18 21:36:28 XXXXXX kernel: xhci_hcd 0000:00:14.0: xHCI
> > xhci_drop_endpoint called with disabled ep ffff880424b5b448
> > Dez 18 21:36:28 XXXXXX kernel: xhci_hcd 0000:00:14.0: xHCI
> > xhci_drop_endpoint called with disabled ep ffff880424b5b490
> > Dez 18 21:36:28 XXXXXX kernel: xhci_hcd 0000:00:14.0: xHCI
> > xhci_drop_endpoint called with disabled ep ffff880424b5b4d8
> > Dez 18 21:36:28 XXXXXX fprintd[3546]: ** Message: device 0 claim status 0
> > Dez 18 21:36:28 XXXXXX fprintd[3546]: ** Message: adding finger 7 to the
> > gallery
> > Dez 18 21:36:28 XXXXXX fprintd[3546]: ** Message: start identification
> > device 0
> > Dez 18 21:36:28 XXXXXX kernel: xhci_hcd 0000:00:14.0: WARN Event TRB for
> > slot 2 ep 4 with no TDs queued?
> > Dez 18 21:36:29 XXXXXX kernel: xhci_hcd 0000:00:14.0: WARN Event TRB for
> > slot 2 ep 4 with no TDs queued?
> > Dez 18 21:36:29 XXXXXX fprintd[3546]: ** Message: identify_cb: result
> > verify-match (1)
> > Dez 18 21:36:29 XXXXXX fprintd[3546]: ** Message: no longer monitoring fd 15
> > Dez 18 21:36:29 XXXXXX fprintd[3546]: ** Message: released device 0
> >
> >
> > Regards,
> > Frank
> >
> > Am 18.12.2014 um 21:20 schrieb Vasily Khoruzhick:
> >> Hi Frank,
> >>
> >> I've just got a report at
> >> https://bugs.freedesktop.org/show_bug.cgi?id=61692 that it doesn't
> >> work.
> >> Did you actually test it?
> >>
> >> Regards,
> >> Vasily
> >
> >>>
> >
_______________________________________________
fprint mailing list
fprint <at> lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/fprint
Vasily Khoruzhick | 18 Dec 19:24 2014
Picon
Gravatar

Re: vfs5011 support

On Thu, Dec 18, 2014 at 9:21 PM, Dr. No <bartsimpson <at> betriebsdirektor.de> wrote:
> Hi,

Hi Dr. No,

I've made several changes to one attached to
https://bugs.freedesktop.org/show_bug.cgi?id=61692
Please re-download it and test on your T440. Thanks!

Regards,
Vasily

P.S. Please keep maillist in CC!

> yes it works.
> I have tested the one at the attachment.
> System: T440p from Lenovo.
>
> Regards,
> Frank
>
> Am 18.12.2014 um 19:15 schrieb Vasily Khoruzhick:
>> Hi,
>>
>> I've just attached version with minor fixups to
>> https://bugs.freedesktop.org/show_bug.cgi?id=61692
>> Please test if it works for you, and if it does - I'll merge it into libfprint.
>>
>> Thanks!
>>
>> Regards,
>> Vasily
>>
>> On Thu, Dec 18, 2014 at 8:56 PM, Dr. No <bartsimpson <at> betriebsdirektor.de> wrote:
>>> Hello Vasily,
>>> are there something news on it?
>>> On http://cgit.freedesktop.org/libfprint/libfprint/ I can't found the
>>> patch include.
>>>
>>> Thanks,
>>> Frank
>>>
>>> _______________________________________________
>>> fprint mailing list
>>> fprint <at> lists.freedesktop.org
>>> http://lists.freedesktop.org/mailman/listinfo/fprint
>
_______________________________________________
fprint mailing list
fprint <at> lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/fprint
Dr. No | 18 Dec 18:56 2014
Picon

Re: vfs5011 support

Hello Vasily,
are there something news on it?
On http://cgit.freedesktop.org/libfprint/libfprint/ I can't found the
patch include.

Thanks,
Frank

_______________________________________________
fprint mailing list
fprint <at> lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/fprint
David Pérez | 6 Dec 08:53 2014
Picon

Device 138a:003f

Hi,

This is my first message to this forum.

I'm using Ubuntu 14.10 and it seems that this device:

Bus 003 Device 002: ID 138a:003f Validity Sensors, Inc. 

isn't supported.

The computer model is HP Probook 650 G1.

This is the related Ubuntu bug:

Are there any plans to support it?

Regards,

David
_______________________________________________
fprint mailing list
fprint <at> lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/fprint
embar | 29 Nov 17:20 2014
Picon

0a5c:5801 Broadcom fingerprint reader support (DELL Latitude 6440)

Hi,

I have DELL Latitude 6440 with fingerprint reader.
But device is not recognized by fprint 0.5.1

> lsusb
Bus 002 Device 003: ID 0a5c:5801 Broadcom Corp. BCM5880 Secure
Applications Processor with fingerprint swipe sensor
Bus 002 Device 002: ID 8087:8000 Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0c45:64d0 Microdia
Bus 001 Device 002: ID 8087:8008 Intel Corp.
Bus 001 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 003 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

> lsusb -d 0a5c:5801 -v

Bus 002 Device 003: ID 0a5c:5801 Broadcom Corp. BCM5880 Secure
Applications Processor with fingerprint swipe sensor
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               1.10
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0        64
  idVendor           0x0a5c Broadcom Corp.
  idProduct          0x5801 BCM5880 Secure Applications Processor with
fingerprint swipe sensor
  bcdDevice            1.01
  iManufacturer           1 Broadcom Corp
  iProduct                2 5880
  iSerial                 3 0123456789ABCD
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength          171
    bNumInterfaces          3
    bConfigurationValue     0
    iConfiguration          0
    bmAttributes         0xe0
      Self Powered
      Remote Wakeup
    MaxPower              100mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           3
      bInterfaceClass       254 Application Specific Interface
      bInterfaceSubClass      0
      bInterfaceProtocol      0
      iInterface              4 Broadcom USH w/swipe sensor
      ** UNRECOGNIZED:  10 25 00 00 00 00 00 00 00 00 00 00 00 00 00 00
      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     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     0x85  EP 5 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0010  1x 16 bytes
        bInterval              32
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       0
      bNumEndpoints           3
      bInterfaceClass        11 Chip/SmartCard
      bInterfaceSubClass      0
      bInterfaceProtocol      0
      iInterface              5 Contacted SmartCard
      ChipCard Interface Descriptor:
        bLength                54
        bDescriptorType        33
        bcdCCID              1.00
        nMaxSlotIndex           0
        bVoltageSupport         7  5.0V 3.0V 1.8V
        dwProtocols             3  T=0 T=1
        dwDefaultClock       4000
        dwMaxiumumClock      4000
        bNumClockSupported      0
        dwDataRate           9600 bps
        dwMaxDataRate      250000 bps
        bNumDataRatesSupp.      0
        dwMaxIFSD             247
        dwSyncProtocols  00000000
        dwMechanical     00000000
        dwFeatures       000102BA
          Auto configuration based on ATR
          Auto voltage selection
          Auto clock change
          Auto baud rate change
          Auto PPS made by CCID
          NAD value other than 0x00 accpeted
          TPDU level exchange
        dwMaxCCIDMsgLen       271
        bClassGetResponse      00
        bClassEnvelope         00
        wlcdLayout           none
        bPINSupport             0
        bMaxCCIDBusySlots       1
      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     0x02  EP 2 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     0x86  EP 6 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0010  1x 16 bytes
        bInterval              32
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        3
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass       254 Application Specific Interface
      bInterfaceSubClass      0
      bInterfaceProtocol      0
      iInterface              7 Broadcom USH
      ** UNRECOGNIZED:  10 26 00 00 00 00 00 00 00 00 00 00 00 00 00 00
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x87  EP 7 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0010  1x 16 bytes
        bInterval              32
Device Status:     0x0000
  (Bus Powered)

I could help to impleement somehow, if you would guide me.

--
embar

_______________________________________________
fprint mailing list
fprint <at> lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/fprint
Alexander Martin | 30 Oct 20:42 2014
Picon

Image Format Returned from fprint

Hi fprint community!

I am interested in using this tool and was curious about the type of image that is returned from the fingerprint reader. Is it JPG, PNG, WSQ, etc.?

Thanks,
Alex
_______________________________________________
fprint mailing list
fprint <at> lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/fprint
Brian Bouterse | 28 Oct 23:54 2014
Picon
Gravatar

T530 Device not seen in FC20

I have a ThinkPad T530 laptop. I have installed libfprint, fprintd, and the demo example on Fedora 20. I was able to run the demo, and it showed me the GUI. However at the bottom I see 'Status: No devices found'.

I believe I have a fingerprint scanner. Most photos have a small rectangle with a light, but mine is a small square to the right of the trackpad.

Here is my output from lsusb:

Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 005: ID 5986:02d2 Acer, Inc 
Bus 001 Device 004: ID 0a5c:21e6 Broadcom Corp. BCM20702 Bluetooth 4.0 [ThinkPad]
Bus 001 Device 003: ID 2687:fb01  
Bus 001 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 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

The end of this thread [0] says that the broadcom is likely the right one, but that my system isn't recognizing it as a device. What is the state of T530 ThinkPad support, and how can I get some fingerprint awesomeness going?

Thanks!
Brian


--
Brian Bouterse
_______________________________________________
fprint mailing list
fprint <at> lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/fprint
Daniel Päßler | 14 Oct 14:02 2014
Picon
Picon

Device 138a:0007 (VFS451)

Hi,

I own this device in an Elitebook 8740w and spent the last days 
searching for a solution to get it to work.

Actually it looks like there is still a bunch of users asking for 
support, but as this is an older device, there seems to be no big effort 
on getting it to work.
Is there any chance for me (as a non-programmer) to help in any way?
I read a lot about USB-Sniffing, which may be helpful (and some of the 
users seems to have already done this).
If I could be able to get one of the Boards off of ebay, would it help 
if I send this to a developer?

There was Linux support from HP for some devices from Validity Inc. in 
SUSE Linux Enterprise a few years ago. I found some libraries, scripts, 
programs and even patches for libfprint.
Is there a chance that these files (though they are old) can help 
developing a driver? Maybe someone can have a look at them, they are here:

https://www.dropbox.com/sh/qbbogrkozlomytw/AABcJkDKWk0K9AT6_-g0HDQwa?dl=0

Is there anything else I can do or provide to help?

Thanks,

Daniel

Gmane