Date: Sat, 23 Jun 2007 12:47:45 +0200 From: Fredrik Lindberg <fli+freebsd-hackers@shapeshifter.se> To: Patrick Tracanelli <eksffa@freebsdbrasil.com.br> Cc: hackers@freebsd.org Subject: Re: UPEK/TouchChip Biometric Device problem Message-ID: <467CFA51.40101@shapeshifter.se> In-Reply-To: <467CA46E.6070705@freebsdbrasil.com.br> References: <467C343C.60707@freebsdbrasil.com.br> <467C3D4F.5030106@shapeshifter.se> <467CA46E.6070705@freebsdbrasil.com.br>
next in thread | previous in thread | raw e-mail | index | archive | help
Patrick Tracanelli wrote: >> >>> >>> All threads purged from ugen1.1 >>> All threads purged from ugen1.2 >>> All threads purged from ugen1.3 >> >> Harmless, as far as I know. >> >>> >>> What is this about "threads purged"? Also, the port want libintl.so.6 >>> while 6.2-STABLE has libintl.so.8. I have tried 1) linking .8 to .6 >>> and also copied .6 from another system (also, 6.2-STABLE) to the >>> current one. Didnt work both way. Same behavior, exactly. >> >> This is because of a gettext library bump, I just found out about it >> (although it happened in march), and I have know good solution to it. >> Installing an old version of gettext should of course work, but that's >> ugly. > > So, this has nothing to do with the fact that the device can not be > initiated? > This is _exactly_ the same device as you have been using in the past with libtfmessbsp.so ? Because if you try to use it with an unsupported device you'll get the "unable to attach" message. Those "All threads purged" have "always" been there, it appears to happen with other devices as well http://lists.freebsd.org/pipermail/freebsd-bugs/2006-May/018361.html 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). At least that will give a hint if it's talking to the device or not. Fredrik
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?467CFA51.40101>