Upek Fingerprint Reader does not work

Bug #429070 reported by tassini
64
This bug affects 13 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

Hello!

I am using Ubuntu 9.04 (Intrepid Ibex) Desktop AMD64 on a Clevo M720R notebook. I was able to make the Upek Trouchstrip (ID 147e:2016 Upek Biometric Touchchip/Touchstrip Fingerprint Sensor) work with fingerprint -demo after a lot of very complex procedures (I have to compile a lot of things). With Karmic Koala Desktop AMD64, the problem is the same. Although lsusb lists the device correctly, I can not use ir. And besides, the sensor become very hot after a while.

ProblemType: Bug
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ubuntu 3985 F.... pulseaudio
CRDA: Error: [Errno 2] Arquivo ou diretório inexistente
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf1100000 irq 22'
   Mixer name : 'Realtek ALC883'
   Components : 'HDA:10ec0883,15580721,00100002 HDA:10573055,10573055,00100700'
   Controls : 28
   Simple ctrls : 17
Date: Sun Sep 13 21:03:13 2009
DistroRelease: Ubuntu 9.10
LiveMediaBuild: Ubuntu 9.10 "Karmic Koala" - Alpha amd64 (20090902.1)
MachineType: Positivo Positivo Mobile
Package: linux-image-2.6.31-9-generic 2.6.31-9.29
PccardctlIdent:

PccardctlStatus:

ProcCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash -- locale=pt_BR console-setup/layoutcode?=br console-setup/modelcode?=abnt2
ProcEnviron:
 PATH=(custom, no user)
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-9.29-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-9-generic N/A
 linux-firmware 1.16
RfKill:
 1: phy1: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
Uname: Linux 2.6.31-9-generic x86_64
dmi.bios.date: 12/19/2008
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: SROSA001.86C.0038.D.081219
dmi.board.name: M720R
dmi.board.vendor: CLEVO Co.
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: CLEVO Co.
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrSROSA001.86C.0038.D.081219:bd12/19/2008:svnPositivo:pnPositivoMobile:pvr14PO_POS:rvnCLEVOCo.:rnM720R:rvrNotApplicable:cvnCLEVOCo.:ct1:cvrN/A:
dmi.product.name: Positivo Mobile
dmi.product.version: 14PO_POS
dmi.sys.vendor: Positivo

Revision history for this message
tassini (tassini) wrote :
Revision history for this message
Noel J. Bergman (noeljb) wrote :

What software are you using? Have you been in touch with Daniel Drake (q.v., http://www.reactivated.net/fprint/wiki/Upeksonly)?

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: New → Triaged
Revision history for this message
xq19space (tuxlux) wrote :

Same problem here. Have tried everything in dozens of forums.

Can confirm on two different notebooks with UPEK.

Issue needs to be addressed and not pushed aside.

This device is used on many new notebooks now.

Revision history for this message
Mary Margaret (otterjet) wrote :

Just purchased new MALIBAL/Satori (Clevo)

UPEK TouchStrip (147e:2016)

61: USB 00.0: 0000 Unclassified device
  [Created at usb.122]
  UDI: /org/freedesktop/Hal/devices/usb_device_147e_2016_noserial_if0
  Unique ID: PYMB.kCK_SDPAt9A
  Parent ID: zPk0.7gZT0a5zLs5
  SysFS ID: /devices/pci0000:00/0000:00:1a.1/usb4/4-1/4-1:1.0
  SysFS BusID: 4-1:1.0
  Hardware Class: unknown
  Model: "TouchStrip Fingerprint Sensor"
  Hotplug: USB
  Vendor: usb 0x147e "TouchStrip"
  Device: usb 0x2016 "Fingerprint Sensor"
  Revision: "0.01"
  Speed: 12 Mbps
  Module Alias: "usb:v147Ep2016d0001dc00dsc00dp00icFFisc00ip00"
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #67 (Hub)

I've tried every thread and posting to get this to work. Results are always the same; no device detected; USB Device not detected.

Tried:
http://ubuntuforums.org/showthread.php?t=1227680
http://www.thinkwiki.org/wiki/How_to_enable_the_fingerprint_reader_with_ThinkFinger
http://www.reactivated.net/weblog/archives/2008/07/upek-touchstrip-sensor-only-147e2016-on-linux/
http://knowledge76.com/index.php/Fingerprint_Reader_Installation

Nothing works.

If anyone get this resolved please post a solution. We need this to work.

Revision history for this message
tassini (tassini) wrote :

As I said, with Jaunty Jackalope AMD64, i was able to make the reader work for login and for sudo, following this instructions:

http://knowledge76.com/index.php/Fingerprint_Reader_Installation

but PAM is not working with Karmic Koala. I was able to enroll all fingers, but could not use it to login or sudo as i did before.

Also i realized that Fedora Core R11 Gnome AMD64 can make the reader work out of the box, using the live cd. Can we just copy the Fedora configuration?

Thanks

Revision history for this message
Corey Quinn (kb1jwq) wrote :

Can confirm that it doesn't work in the latest Lucid beta.

Revision history for this message
tassini (tassini) wrote : Re: [Bug 429070] Re: Upek Fingerprint Reader does not work

Em Seg, 2010-03-29 às 20:37 +0000, KB1JWQ escreveu:

I tried the Alpha 3 and it didn't work, but I have not yet tried the
Beta. I have already downloaded it. As soon as possible I will test with
it and let you know.

Thanks in advance!!

> Can confirm that it doesn't work in the latest Lucid beta.
>

Revision history for this message
tassini (tassini) wrote :

Em Dom, 2010-04-04 às 10:31 +0000, tassini escreveu:

I does not work with Lucid Beta 1.

> Em Seg, 2010-03-29 às 20:37 +0000, KB1JWQ escreveu:
>
> I tried the Alpha 3 and it didn't work, but I have not yet tried the
> Beta. I have already downloaded it. As soon as possible I will test with
> it and let you know.
>
> Thanks in advance!!
>
> > Can confirm that it doesn't work in the latest Lucid beta.
> >
>

Revision history for this message
tassini (tassini) wrote :

Em Ter, 2010-04-06 às 09:58 +0000, tassini escreveu:

Hello,

And it does not work with Beta 2 either...

I am starting to doubt if it will work again with any future release of
Ubuntu. It seems that fingerprint reader is not important *enough* to
Ubuntu to justify any investment of time in developing a working
solution...

> Em Dom, 2010-04-04 às 10:31 +0000, tassini escreveu:
>
> I does not work with Lucid Beta 1.
>
>
> > Em Seg, 2010-03-29 às 20:37 +0000, KB1JWQ escreveu:
> >
> > I tried the Alpha 3 and it didn't work, but I have not yet tried the
> > Beta. I have already downloaded it. As soon as possible I will test with
> > it and let you know.
> >
> > Thanks in advance!!
> >
> > > Can confirm that it doesn't work in the latest Lucid beta.
> > >
> >
>

Revision history for this message
Mtt.Castelli (mtt.castelli) wrote :

I also can confirm that it doesn't work in the latest Lucid _final_ release.

damn it!

Revision history for this message
andypiper (andypiperuk) wrote :

I have one of these devices working with Fingerprint GUI http://www.n-view.net/Appliance/fingerprint/ on Ubuntu 10.04 final.

Revision history for this message
tassini (tassini) wrote :

Will this bug be addressed someday? In two or three years, this Upek device will be so old that no "live" notebook will be using it.

Changed in linux (Ubuntu):
status: Triaged → Confirmed
Revision history for this message
Aryan Pourbaghery J. (prodgnius) wrote :

Hey everybody,
I guess I've figured it out too! A detailed yet-quite-long roadmap is here: https://launchpad.net/~fingerprint/+archive/fprint
Mine is a Sony Vaio VGN-SZ780N5 with a UPEK TouchStrip (147e:2016) coprocessor(check here whether yours is supported too: http://reactivated.net/fprint/wiki/Supported_devices ). It works just fine on Ubuntu Lucid Lynx 10.04 final (only! for Karmic you have to get the relevant packages in spite of one minor fault with the UI which is correctable by changing commands from gksu to gksu-polkit). I had to install a few libraries and firmwares though, including libfprint, fprint-demo,fprintd, libpam-fprintd (do not confuse it with libpam-fprint, the final “d” means sth!) and gksu-polkit.
The steps are typically as follows:
1. sudo add-apt-repository ppa:fingerprint/fprint
(which as of today till the day it is fixed will not work(!) and you have to manually add these two lines to your software resources under system>administration>software resources:
deb http://ppa.launchpad.net/fingerprint/fprint/ubuntu lucid main
deb-src http://ppa.launchpad.net/fingerprint/fprint/ubuntu lucid main )
2. sudo apt-get update
3. sudo apt-get install libfprint0 fprint-demo
4. sudo apt-get install libpam-fprintd
5. If there were no errors on the way (except the ones already mentioned) you are good to go. go to Applications > Accessories > fprint where you can enroll,verify,... your fingerprints and oh! BTW you might wanna restart or wait a few minutes for the 1st time of running fprint-demo cause it seems to need a little bit of time to signal the sensor for the first time. go to System > Preferences > About Me and on the top right corner you should see the Enable Fingerprint Login button. Bingo!

Revision history for this message
tassini (tassini) wrote :

Hi Aryan Pourbaghery J.!

Thank you for your detailed instructions. It worked for me, but after enabling fingerprint login button, i could not use the wireless network!! The network manager icon does not appear until disabling fingerprint button. Any idea?

Thanks in advance!

Revision history for this message
Aryan Pourbaghery J. (prodgnius) wrote :

Well, glad to hear you are at least up and running with your fingerprint sensor. yet for the mentioned issue I'd just as soon ask whether you are sure if it is a wireless functionality loss/malfunction or rather merely a slight issue of display with the UI. Odds are most probably against the former and hopefully for the latter! however, since you do not have access to the network manager icon on the taskbar panel (and as for the worst case scenario I would assume you do not have access to the launcher provided in the main menu>Administration>NetworkTools and System>Preferences>Network Connections either! Cause if you have, then it is a lot easier to track down the problem.), we should first carry out a couple of diagnostics.
While you have the finger print login enable do the following:
$ ifconfig
The result is similar to
eth0 Link encap:Ethernet ....

lo Link encap:Local Loopback ....

wlan0 Link encap:Ethernet ....
or use
$ netstat -i
In the results for either commands, see if there is any one named wlan0 like the above or sth similarly named(in case you have more than one wireless adapters you should be looking for more than one "wlan"s quite certainly in order of wlan0,wlan1,...).
if so then you are blessed. There is probably nothing wrong with your wireless lan and it's just a UI bug.
if not then try the following:
$ sudo ifconfig wlan0 up
or
$ sudo ifup wlan0
then check up again if your wireless is up running via ifconfig or netstat as above.
if your wlan is up then check your connectivity via
ping www.google.com
if the result is similar ,in appearance, to
64 bytes from hb-in-f104.1e100.net (74.125.87.104): icmp_seq=1 ttl=50 time=341 ms
then everything is fine! you are already connected.
if not do the following and repeat the above steps.
$ sudo /etc/init.d/networking restart

No good news yet? then just check the results of the below commands and let us know about it all, so we can dig alittle bit more in:
$ sudo nano /etc/network/interfaces
or
$ sudo vi /etc/network/interfaces

and
$ sudo nano /etc/resolv.conf
or
$ sudo vi /etc/resolv.conf

Bst Rgrds n Lkng Frwrd 2 hrng Gd nws,
Aryan

Revision history for this message
felixcorrales (felixcorrales-yahoo) wrote :

Ubuntu 10.04, fingerprint-gui-0.14

I had a network problem too, after I followed the next procedure

http://www.n-view.net/Appliance/fingerprint/Install-step-by-step.pdf

I solved my network problems by using the "Password Store"

"There are applications that need a password for encrypting or decrypting something on your system.
Probably gnome-keyring is the most widespread of such applications. Also an encrypted home
directory needs a password to decrypt when a user logs in. These applications sometimes get their
key for decrypting (e.g. for the password safe) by querying the PAM session environment for the
password given by the user at login. But when the user was logged in with a fingerprint there is no
password stored in the PAM session environment. So the application will prompt the user for a
password when needed (e.g. if a wireless WPA connection has to be established by the Gnome
Network Manager or if you want to access your email account with Evolution) even if the user was
logged in already.

Since version 0.11 of Fingerprint GUI there is a solution: You can use some removable media
(USB stick) to save your (encrypted) password there. If the media is connected to your machine
while you login with your fingerprint the “pam_fingerprint-gui.so” module can decrypt the
password and send it to the PAM session environment."

http://darkblue.homeip.net/fingerprint/Forum/topic.php?TopicId=37&Posts=2

Revision history for this message
Brad Figg (brad-figg) wrote : Unsupported series, setting status to "Won't Fix".

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.