Talk:How to enable integrated fingerprint reader with BioAPI
Contents
Changing the installation path
By default, bioapi will install numerous files in /usr/local/{bin,lib,include}, including files with "self-explanatory" names such as /usr/local/bin/Sample. To prevent this pollution:
- Create a dedicated directory,say, /opt/bioapi .
- Append --prefix=/opt/bioapi to the ./configure command of bioapi
- Append /opt/bioapi/bin to $PATH and /opt/bioapi/lib to $LD_LIBRARY_PATH
- Edit the install path in install.sh of the driver
--Thinker 18:06, 30 Oct 2005 (CET)
chmod 777 -R /usr/local/var/bioapi/
Is the above necessary? I just made a debian package of xscreensaver with the patch applied, and when using the bioapi debian pacakge from Michael R. Crusoe's site which has this directory put in /usr/var/bioapi I had not to change the permissions to world-writeable there. Write access to the logfile and usb device are necessary, but that directory works with 755 as well (even though it comes with 777 in Michael's package), and all files and subdirectories are 644/755 too.
--spiney 00:08, 11 Nov 2005 (CET)
Qt Compilation Success
Here it worked with qt ;)
using absolute paths for commands
I don't know whether using absolute paths in the articles is a good idea, at least not for tools like lsusb which are not established utilities (i.e. used for more than a decade or something ;)) and happen to be in different locations in different distributions. E.g. said lsusb resides in /usr/sbin on Debian systems.
--spiney 16:45, 12 Nov 2005 (CET)
BioAPI error #3
Its kind of strage it used to work with everythig (kdm,console,lock,etc) Now it only works with kdm. It allways gives back:
pam_bioapi[8113]: Unable to initialize Bioapi framework, BioAPI error #:3.
Even when I set the right permissions on /proc/bus/usb.
I am able to run the Sample program as normal user after setting the permissions, but when I change within a user session by su I amnot able to run the Sample program a also get an error Code #3.
From an other terminal (alt+strg+Fx) I am able to run the Sample program but at the login I still get the error #3.
I cant remember to have changed anything an d bevor I was able to login in a console with my fingerprint now only kdm is working even kde lock-session isnt working anymore.
Any suggestions ?
Driver Expiring!!!
Don't anyone notice that both betas of the UPEK driver is expiring in about a month in the new year, Jan 1st 2006? They really mean it! I set my computer date to next year and get a message "the driver has expired" when using fingerprint reader! This is a grave threat to our computer lifestyle, i.e. for those of us who got it working and use it daily:) Is there any workaround other than setting the date back a year when new year come and wait for new driver? Is there a way to figure out where exactly in the driver it checked the date and how? The must have set it somewhere in file libtfmessbsp.so, but it is binary and I can't figure out how to Reverse Engineer it.
---Jiang
Yes, the beta driver will expire. The final version (which is due REALLY soon now) will not.
Sumedha
Any news? Just 9 days left to expiry. --Thinker 21:36, 22 Dec 2005 (CET)
Updated xscreensaver patch
I've tried to address some usability issues with the old patch, e.g. that it calls the PAM bioapi module twice before falling back to the normal authentication methods. It can be found on my Fingerprint Reader page, feedback is very welcome.
--spiney 20:36, 22 Dec 2005 (CET)
