Re: [Muscle] PCSCD Not reading Smart Card

[Wesley Nugent]

On Thu, Aug 7, 2008 at 9:38 PM, Wesley Nugent <[EMAIL PROTECTED]> wrote: I've got PCSCD loaded and running, it sees my smart card reader, sees me insert a card, but when I use a utility (the only one I have currently) to try to read the card, I cannot read the card. Let me explain a little. I work for a company that sells Point of Sale Thin Client Stations. These Thin Client Stations have always run busybox and have had an older version of pcscd running with some binary utilities to read and write the card. I'm not sure where these utilities came from, just they are called scard-read and scard-write. They worked with this setup. I'm doing development on a new thin client using Debian instead of busybox. I unfortunately do not have the source code from the previous binaries. The old terminals had a 2.4 kernel, the new one has 2.6. What is the version of pcscs-lite on the old terminals? Use "pcscd -v" old terminals: pcsc-lite version 1.1.1. New terminal: pcsc-lite version 1.3.2 FYI, I tried using the old one on there but it said that it wasn't running when I ran my read/write programs. I have done apt-get install pcscd and apt-get install libasedrive-usb. /var/log/syslog shows the card. I run the scard-read, it shows: Established context Check the connected readers reader=AseIIIeUSB 00 00 Please select reader from the list: Then there is a blinking cursor. If I hit enter, I get segfault. Can you use gdb to get a backtrace of the segfault? Bye Ok, this is what I get: (gdb) run /usr/local/bin/scard-read Starting the program: /usr/local/bin/scard-read Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". Failed to read a valid object file image from memory. (no debugging symbols found) (no debugging symbols found) [New Thread -1209727296 (LWP 10210)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) Established context Check the connected readers reader=AseIIIeUSB 00 00 Please select reader from the list: waiting on status change! Card Connect Program received signal SIGSEGV. Segmentation Fault. [Switching to Thread -1209727296 (LWP 10210)] 9xb7ec0463 in strlen () from /lib/tls/i686/cmov/libc.so.6 (gdb) If I type in AseIIIeUSB taht I see, it shows: Card Connect The specified reader name is not recognized Program exited normally (gdb) Thank you for the assistance. --

_______________________________________________
Muscle mailing list
Muscle@lists.musclecard.com
http://lists.drizzle.com/mailman/listinfo/muscle