Comments for dsd's weblog

Comment on Announcing fprint project by Alex VanDeusen

Alex VanDeusen — Wed, 23 Jul 2008 21:28:11 +0000

Hi I have a motion computing tablet model m1400. I am running the 32bit hardy version. It uses the authentec 2501 fingerprint scanner. I installed your software using debs someone pointed me to (version 0.6) However it does not recognize the hardware. After some searching I found a post that states the following:

I have a Motion Computing M1400 Tablet with an AES2500 chip (or
something like that). The aes2501 driver works perfectly fine with
it, but I needed to add 0×08ff:0×2500 to the driver’s vender/product
table. Other than that it works great!

BTW, I could not create an account on the Wiki to put this on the
Supported Devices page, it did not give me an option to create an
account.

Regards,
Daniel Hazelbaker

So my question is how do you get the libfprint to support this device? I dont know how to add it and then compile it.

Comment on UPEK TouchStrip Sensor-only (147e:2016) on Linux by Lapoz

Lapoz — Wed, 23 Jul 2008 19:54:51 +0000

It’s frustrating, I didn’t imagine it would be so hard to match my own fingerprints :D
I’ve managed to do it two times, then nothing.
What is good : the most or the less minutiae ?

Comment on UPEK TouchStrip Sensor-only (147e:2016) on Linux by Lapoz

Lapoz — Wed, 23 Jul 2008 19:35:50 +0000

I have tried it today, thanks a lot for your work !
The installation went OK, but I’m unable to verify my fingers after enrolling them…
Still playing, my best score is 10 minutiae :-(

My configuration: Ubuntu 8.04 LTS on Keynux Jet SR (based on Clevo M720R).

Comment on UK Student loans company by violet

violet — Wed, 23 Jul 2008 16:10:15 +0000

For two years the Student Loan Co. sent me nothing , no deferement forms no contact what so ever , now Credit Solutions are making my life a misery , even though it took them 8 weeks to send me a deferement form , they expect it to be returned to them a.s.a.p!!!

Comment on Fedora/RPM packaging by Rahul Sundaram

Rahul Sundaram — Tue, 22 Jul 2008 18:48:51 +0000

Newer versions of RPM can detect more build requirements at runtime but it is still provided explicitly for compatibility reasons at times. Yes, build customization can be a problem but the solution atleast in this case is to work with Fedora to split up packages more granularly. In fedora-devel list, some of the OLPC folks pointed a few issues related to this which are being resolved in the development branch of Fedora (Rawhide).

“. Not everything can be done through koji/mock, e.g. you still need to use rpmbuild to build OLPC’s kernel. Also, rpmbuild is the only tool that can build a source RPM, I think”

I am not sure where you get this impression. Every single package is build using Koji (http://koji.fedoraproject.org) which itself uses mock directly against the spec files. You do not need rpmbuild at all. Maybe OLPC is doing something different that I am not aware of. Feel free to login to #fedora-devel and ask if you have doubts. Good to hear a different perspective nevertheless.

Comment on Fedora/RPM packaging by Daniel Drake

Daniel Drake — Tue, 22 Jul 2008 16:35:01 +0000

Yes, gnome-python2 is already split up into subpackages in Fedora, but not well enough at the moment. https://bugzilla.redhat.com/show_bug.cgi?id=456122

Comment on Fedora/RPM packaging by Mart Raudsepp

Mart Raudsepp — Tue, 22 Jul 2008 15:53:08 +0000

Regarding the GNOME python bindings (gnome-python, gnome-python-desktop and gnome-python-extras tarballs), one can just split it out into multiple packages. I figured binary distributions are doing it long ago, as it’s easier for them, but I guess not then…
For Gentoo ford_prefect will be committing the split up packages to portage soon as his first bigger thing as an official Gentoo developer :) So we will have packages for every binding separately, so you won’t need to pull in the whole stack through libgnome bindings just because you just want to “import gconf”. The old package will be converted to a meta package that pulls in all the separate ones, so that the files installed by the monolith will be the same as when installed by the meta package, for easier migration by packages - they can gradually stop rdepending on the big thing at their leisure, considering their time and concerning keyword visibility matching.

As for runtime dependencies, there are at least scripts around for Gentoo as well that can list you what packages are needed at runtime as figured out by it (of course doesn’t find dlopened stuff, probably just like Fedora, etc), so it’s easier to get a starting point to put in the ebuild. That said, in the GNOME world (and I imagine in most places), we just go with what configure.in checks and they are often listed all at once in variables in the same place and later those variables are used as necessary (sometimes inside various conditionals, like if a feature was enabled or not) , so that it’s easy to see minimal version dependency changes for example.
For instance in gtkhtml’s configure.in (just happened to be unpacked here):

# Required Package Versions
m4_define([gtk_minimum_version], [2.10.0])
m4_define([gail_minimum_version], [1.1.0])
m4_define([gnome_icon_theme_minimum_version], [1.2.0])
m4_define([libbonoboui_minimum_version], [2.2.4])
m4_define([libglade_minimum_version], [2.0.0])
m4_define([libgnomeui_minimum_version], [2.0.0])

That said, these scripts and such tools should get collected better and perhaps integrated into a smaller number of tools

Comment on UPEK TouchStrip Sensor-only (147e:2016) on Linux by Nuno Milheiro

Nuno Milheiro — Mon, 21 Jul 2008 21:52:51 +0000

Is it possible to use ths driver without libusb-1.0 ? I would prefer no to. Is it a feature libusb stable lacks or just a choice of implementation?

thanks

Comment on More fprint releases by ark4

ark4 — Thu, 17 Jul 2008 10:55:12 +0000

Works great in a P105-S9339, but don’t show fingerprint image.
Say “Non-imaging device” could you tell me how to add that funcionality ? :D

Comment on UPEK TouchStrip Sensor-only (147e:2016) on Linux by Daniel Drake

Daniel Drake — Mon, 14 Jul 2008 02:58:13 +0000

Not sure that I understand your confusion, since both of those are correct. upeksonly says “I support 147e, the other variant is upekts.” upekts says “I don’t support 147e, use upeksonly”

but I took a guess at what is a little unclear and changed upeksonly to read as follows:
This driver supports fingerprint readers found embedded into many commercial laptops, including some System76 laptops and IBM/Lenovo ThinkPads. The device sits on the USB bus with USB ID 147e:2016. The driver does not support the TouchStrip variants which include a biometric co-processor. The co-processor variants have a different USB ID and are instead supported by the upekts driver.

As for it not working, you need to be using the latest git sources, not any released version. If you still have troubles, please use the mailing list.