Hi, Try with the last version of PC/SC Lite available on [1]. If you have again the same problem report your problem with log on [2]. For the log, start "pcscd -a -f -d stdout". You can also log information from the Cardman 2020. For this follow this procedure: ------------------------------ Getting Debug Information ------------------------------ The kernel module implements functionality for dynamically changing the debug log level: to enable this feature create a file /etc/cm2020dbglvl.conf which contains the debug level to use. # touch /etc/cm2020dbglvl.conf # echo "<dbg level to use>" > /etc/cm2020dbglvl.conf
Meaning of fhe debug levels: 0 : No mesages show up 1 : Only very important messages (messages which shoud always be shown) 2 : Main function entry/exit points 3 : Helper functions entry/exit points 4 : Inforamtions from within main functions 5 : Information from within helper functions >6: All other informations The debug messages are sent to your system log file (usually this is /var/log/messages); so you can read the messages by using the commands "dmesg" or "tail -f <path-to-your-system-log-file>". [1] http://alioth.debian.org/projects/pcsclite/ [2] http://alioth.debian.org/tracker/?atid=410085&group_id=1225&func=browse Regards, Damien Sauveron Selon Dominik Fischer <[EMAIL PROTECTED]>: > Hello, > > we are observing a strange behaviour regarding pcsc-lite-1.1.2-beta4 in > connection with /proc/bus/usb (usbdevfs). > When starting pcscd on boot it first works as suggested, but after a few > minutes pcscd complains about not being able > to open /proc/bus/usb/XXX ("USB path seems to have disappeared"). But > when examining this path from commandline > (ls, etc.) everything looks allright. Trying to connect with pcsc_scan > leads to pcscd syslog entries telling us, that there are > no filehandles left. As a consequence the pcscd usb hotplugging is > disabled. > > We are using kernel 2.4.21 with bluetooth-patch mh2 and kmesg-patch. > Hotplugging is enabled and our cardreader is a > cm2020. The readerdriver sometimes is unloaded before the usb-error > occurs and sometimes it is still functional (ATR is > still read and logged by pcscd), but pcscd cannot manage to dispatch > messages to it. > > Has anyone seen this kind of behaviour? > > Thanks in advance for any help! > > Kind regards > Dominik Fischer > > _______________________________________________ > Muscle mailing list > [EMAIL PROTECTED] > http://lists.musclecard.com/mailman/listinfo/muscle > ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/ _______________________________________________ Muscle mailing list [EMAIL PROTECTED] http://lists.musclecard.com/mailman/listinfo/muscle
