Hi,

This is very strange to hear. I personally developed an application based on
U.are.U readers and I had two of them -- one from Microsoft (ID 045e:00ca)
and one from Digital Persona (a U.are.U 4000B, probably ID 05ba:000a) and I
noticed no difference in the two devices. They worked equally badly.
Nonetheless, they worked exactly the same way.

A stupid question, but are you running lsusb with root privileges? It may
affect visibility of devices and device discovery that lsusb would otherwise
not trigger.

Regards,
Artem


On Sat, May 23, 2009 at 6:36 PM, Paolo Arnaldo Dallari <
[email protected]> wrote:

> Hi all,
> I am in early stage of developing a program for fingerprint recognize,
> I was using happily a Microsoft Fingerprint reader,
> after I figure out that Microsoft stopped the selling of his fprint
> scanner in 2005, I bought two U.are.U 4000 from digitalpersona hoping
> that everything will be better and without headache knowing that
> U.are.U 4000 is full supported.
>
> I was wrong, I can't get them working,
> even upgrading libfprint from 0.6 to git repo don't fix the problems.
>
> the device opens, lights up even when i ask to enroll, but it don't
> recognize my finger; it's like I never put my finger over the scanner.
> (with fprint-demo from git is the same)
>
> the same problem in the two devs:
> U.are.U 4000 Sensor from digitalpersona
> model: URU4S-U1
> rev. 101
>
>
> p.s.
> Second problem is that if I try to connect the two devices to the
> linux machine it seems from lsusb that only one is connected.
> the first I connect is the one that linux kernel and fprint will find,
> the other it's like not connected.
> But this is not a problem of libfprint I think.
>
> Hoping in precious help,
>
> Best Regards,
>
> --
> Paolo
> _______________________________________________
> fprint mailing list
> [email protected]
> http://lists.reactivated.net/mailman/listinfo/fprint
>
_______________________________________________
fprint mailing list
[email protected]
http://lists.reactivated.net/mailman/listinfo/fprint

Reply via email to