From owner-freebsd-hackers@FreeBSD.ORG Sat Jun 23 13:37:18 2007 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6A0E716A41F for ; Sat, 23 Jun 2007 13:37:18 +0000 (UTC) (envelope-from fli+freebsd-hackers@shapeshifter.se) Received: from mx1.h3q.net (mx1.h3q.net [212.37.5.30]) by mx1.freebsd.org (Postfix) with ESMTP id 1EF8F13C44C for ; Sat, 23 Jun 2007 13:37:18 +0000 (UTC) (envelope-from fli+freebsd-hackers@shapeshifter.se) Received: from [192.168.1.100] (81-232-22-115-no50.tbcn.telia.com [81.232.22.115]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: fli@shapeshifter.se) by mx1.h3q.net (Postfix) with ESMTP id 5529A78C20; Sat, 23 Jun 2007 15:37:16 +0200 (CEST) Message-ID: <467D2200.4020507@shapeshifter.se> Date: Sat, 23 Jun 2007 15:37:04 +0200 From: Fredrik Lindberg User-Agent: Thunderbird 2.0.0.0 (X11/20070610) MIME-Version: 1.0 To: Patrick Tracanelli References: <467C343C.60707@freebsdbrasil.com.br> <467C3D4F.5030106@shapeshifter.se> <467CA46E.6070705@freebsdbrasil.com.br> <467CFA51.40101@shapeshifter.se> <467D1553.7060808@freebsdbrasil.com.br> In-Reply-To: <467D1553.7060808@freebsdbrasil.com.br> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: hackers@freebsd.org Subject: Re: UPEK/TouchChip Biometric Device problem X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Jun 2007 13:37:18 -0000 Patrick Tracanelli wrote: > Fredrik Lindberg wrote: >> This is _exactly_ the same device as you have been using in the past >> with libtfmessbsp.so ? > > No, not the same hardware, but same model/chipset. > >> Because if you try to use it with an unsupported device you'll get >> the "unable to attach" message. > > Its a 0x2016 device from 0x0483 vendor. This is the only thing that is > "the same" as the previously used device. > >> >> Since the binary is built on top of libusb you can turn on debugging >> in libusb by setting the environment variable USB_DEBUG (the larger >> value the more verbose debugging). > > Goood hint,thank you. > > Here is what I get: > > # bbdm -b "{5550454b-2054-464d-2f45-535320425350}" -m filedb -c eksffa ; > echo $? > usb_set_debug: Setting debugging level to 3 (on) > usb_os_find_busses: Found /dev/usb0 > usb_os_find_busses: Found /dev/usb1 > usb_os_find_busses: Found /dev/usb2 > usb_os_find_busses: Found /dev/usb3 > usb_os_find_busses: Found /dev/usb4 > usb_os_find_devices: Found /dev/ugen1 on /dev/usb2 Ok, then at least it's talking to the device. I had a user who had about the same problem as you, it turned out that the particular device he was using wasn't supported by the driver, when he tried another device everything worked as expected. I can't seem to find his usb vendor, device pair though. If I remember correctly, libtfmessbsp.so only supports TCD41 swipe readers. Fredrik