Damien Sauveron wrote:
I did the update. pcsc-lite-1.2.0 works with the reader now (1.1.2 still doesnt).
1. pcsc-lite-1.1.2 and up dont work with acs-drivers.It is strange... have you got log?
The reader is not detected.
Use the LAST release pcsc-lite-1.2.0 from [1] and provide us the log of "pcscd --apdu --foreground"
The problem is still there. I'll post a detailed log tomorrow.2. When I unplug a reader (Iam using acs ACR30U-CFC)Again we need the logs.
from USB-prot, pcscd -d stdout starts flooding the
console with errormessages: "eventhandler.c:319 EHSpawnEventHandler: Error
communicating to: acr30u-cfc 0 0" (repeating till ^C).
Reconnecting the reader to USB will not stop the
errors. I have to kill pcscd and restart.
Is this a problem in the deamon or in the
usb-implementaion of linux?
It seems that the pcscd tryes to access to the "old" devicenumber. Could it be? I dont know how linux handles the devices internally and what the devicenumber really does.
However, the new, respawned instance of pcscd dont access the reconnected reader at all (the led of the reader remains "off").
This is a problem, specially if I want to run the daemon from startscript.
_______________________________________________
Muscle mailing list
[EMAIL PROTECTED]
http://lists.musclecard.com/mailman/listinfo/muscle
