Re: MUSCLE and gemplus readers.
Dr S N Henson wrote: > > I've been testing out MUSCLE and some related software with some gemplus > readers, all with RHL 6.1 2.2.12 kernel and RHL7.0 2.2.16 with > backported USB and 2.4.5. > > I haven't got the USB reader GemPC430 to work though. All I get when I > plug the reader in is a message saying no driver supports the device. > This also happens with 2.4.5 kernel. Any pointers as to the possible > cause? Could you please copy the message, it would be very helpful. Also, what do you use to install pcsc-lite: the tarball or a rpm package? Which version is it? Here is a list of possible cause: - the first versions of the debian package were not compiled with USB support, maybe it was the same for the rpms. - if you have USB support compiled as module, you have to install the usb-uhci module "by hand" - if you get the following message, you may not have copied the bundle to the right location. pcscd:pcscdaemon.c 126: /var/run/pcscd.pid pcscd:pcscdaemon.c 146: main: PC/SC Lite Daemon Ready. pcscd: hotplug_linux.c 146: No bundle files in pcsc drivers directory I hope this helps, JLuc. *** Linux Smart Card Developers - M.U.S.C.L.E. (Movement for the Use of Smart Cards in a Linux Environment) http://www.linuxnet.com/smartcard/index.html ***
Re: MUSCLE and gemplus readers.
Jean-Luc GIRAUD wrote: > > Dr S N Henson wrote: > > > > I've been testing out MUSCLE and some related software with some gemplus > > readers, all with RHL 6.1 2.2.12 kernel and RHL7.0 2.2.16 with > > backported USB and 2.4.5. > > > > I haven't got the USB reader GemPC430 to work though. All I get when I > > plug the reader in is a message saying no driver supports the device. > > This also happens with 2.4.5 kernel. Any pointers as to the possible > > cause? > > Could you please copy the message, it would be very helpful. Also, what > do you use to install pcsc-lite: the tarball or a rpm package? Which > version is it? > > Here is a list of possible cause: > - the first versions of the debian package were not compiled with USB > support, maybe it was the same for the rpms. > - if you have USB support compiled as module, you have to install the > usb-uhci module "by hand" > - if you get the following message, you may not have copied the bundle > to the right location. > pcscd:pcscdaemon.c 126: /var/run/pcscd.pid > pcscd:pcscdaemon.c 146: main: PC/SC Lite Daemon Ready. > pcscd: hotplug_linux.c 146: No bundle files in pcsc drivers directory > I suspect the answer is 'none of the above' :-) The precise message I get is: usb.c: USB device 2 (vend/prod 0x8e6/0x430) is not claimed by any active driver. I'm compiling MUSCLE 0.9.1 and the GemPC430 driver from source. There are a few problems with 'make install' in MUSCLE, at least on my setup: for example it installs reader.conf in /usr/local/etc but expects to find it in /etc and it doesn't seem to install the pcsd binary (well script) anywhere. pcsd doesn't give any error message on start up. Presumably the hotplug support registers the vend/prod id when it looks through the bundle, my guess is that it isn't doing that for some reason, but I'm not familiar enough with how Linux USB works to trace it any further. BTW do you know anything about the GPR400 device driver? One problem I get with that is that after the 'power down' command it stays powered down and doesn't respond to any commands (including 'reset' which I believe is supposed to power it up again). A reboot or eject/reinsert is needed. Steve. -- Dr Stephen N. Henson. http://www.drh-consultancy.demon.co.uk/ Personal Email: [EMAIL PROTECTED] Senior crypto engineer, Celo Communications: http://www.celocom.com/ Core developer of the OpenSSL project: http://www.openssl.org/ Business Email: [EMAIL PROTECTED] PGP key: via homepage. *** Linux Smart Card Developers - M.U.S.C.L.E. (Movement for the Use of Smart Cards in a Linux Environment) http://www.linuxnet.com/smartcard/index.html ***
Re: MUSCLE and gemplus readers.
Dr S N Henson wrote: > > I suspect the answer is 'none of the above' :-) Yes and no :-) (see below). > > I'm compiling MUSCLE 0.9.1 and the GemPC430 driver from source. There > are a few problems with 'make install' in MUSCLE, at least on my setup: > for example it installs reader.conf in /usr/local/etc but expects to > find it in /etc and it doesn't seem to install the pcsd binary (well > script) anywhere. The default 'make install' does not compile pcscd with usb support (which was the reason of the "problem" with the packages). You should first './configure --enable-usb' to enable usb support. If you have the GemPC430 bundle in the 'drivers' folder of the pcsc install, it should work. > BTW do you know anything about the GPR400 device driver? One problem I > get with that is that after the 'power down' command it stays powered > down and doesn't respond to any commands (including 'reset' which I > believe is supposed to power it up again). A reboot or eject/reinsert is > needed. I don't know anything about it. I'll see if I can find out anything regarding this issue. Cheers, JLuc. *** Linux Smart Card Developers - M.U.S.C.L.E. (Movement for the Use of Smart Cards in a Linux Environment) http://www.linuxnet.com/smartcard/index.html ***
Re: MUSCLE and gemplus readers.
Jean-Luc GIRAUD wrote: > > Dr S N Henson wrote: > > > > I suspect the answer is 'none of the above' :-) > > Yes and no :-) (see below). > > > > > I'm compiling MUSCLE 0.9.1 and the GemPC430 driver from source. There > > are a few problems with 'make install' in MUSCLE, at least on my setup: > > for example it installs reader.conf in /usr/local/etc but expects to > > find it in /etc and it doesn't seem to install the pcsd binary (well > > script) anywhere. > > The default 'make install' does not compile pcscd with usb support > (which was the reason of the "problem" with the packages). You should > first './configure --enable-usb' to enable usb support. If you have the > GemPC430 bundle in the 'drivers' folder of the pcsc install, it should > work. > I did run ./configure with --enable-usb. I also ran pcsd under strace and it seems to be reading the 'bundle' files and there's also some additional activity when the reader is plugged in. Steve. -- Dr Stephen N. Henson. http://www.drh-consultancy.demon.co.uk/ Personal Email: [EMAIL PROTECTED] Senior crypto engineer, Celo Communications: http://www.celocom.com/ Core developer of the OpenSSL project: http://www.openssl.org/ Business Email: [EMAIL PROTECTED] PGP key: via homepage. *** Linux Smart Card Developers - M.U.S.C.L.E. (Movement for the Use of Smart Cards in a Linux Environment) http://www.linuxnet.com/smartcard/index.html ***
Re: MUSCLE and gemplus readers.
Jean-Luc GIRAUD wrote: > > > > > > I'm compiling MUSCLE 0.9.1 and the GemPC430 driver from source. There > > are a few problems with 'make install' in MUSCLE, at least on my setup: > > for example it installs reader.conf in /usr/local/etc but expects to > > find it in /etc and it doesn't seem to install the pcsd binary (well > > script) anywhere. > > The default 'make install' does not compile pcscd with usb support > (which was the reason of the "problem" with the packages). You should > first './configure --enable-usb' to enable usb support. If you have the > GemPC430 bundle in the 'drivers' folder of the pcsc install, it should > work. > A bit more progress. I've enabled debugging output and more importantly edited syslog.conf so it doesn't throw debugging output away :-) I get the following on startup: Jun 5 17:19:24 localhost pcscd:pcscdaemon.c 128: main: PC/SC Lite Daemon Ready. Jun 5 17:19:24 localhost pcscd: bundleparser.l 95: Value/Key not defined for: CFBundleExecutable I'll see if I can trace it a bit further. Looks like it doesn't like the bundle config file for some reason. Steve. -- Dr Stephen N. Henson. http://www.drh-consultancy.demon.co.uk/ Personal Email: [EMAIL PROTECTED] Senior crypto engineer, Celo Communications: http://www.celocom.com/ Core developer of the OpenSSL project: http://www.openssl.org/ Business Email: [EMAIL PROTECTED] PGP key: via homepage. *** Linux Smart Card Developers - M.U.S.C.L.E. (Movement for the Use of Smart Cards in a Linux Environment) http://www.linuxnet.com/smartcard/index.html ***
Re: MUSCLE and gemplus readers.
David Corcoran wrote: > > Hi, > > Try removing bundleparser.c and doing the ./configure --enable-usb > and everything over again. > That did the trick. I still get a few kernel warning messages when I plug the device in but I can now access the reader, thanks. Steve. -- Dr Stephen N. Henson. http://www.drh-consultancy.demon.co.uk/ Personal Email: [EMAIL PROTECTED] Senior crypto engineer, Celo Communications: http://www.celocom.com/ Core developer of the OpenSSL project: http://www.openssl.org/ Business Email: [EMAIL PROTECTED] PGP key: via homepage. *** Linux Smart Card Developers - M.U.S.C.L.E. (Movement for the Use of Smart Cards in a Linux Environment) http://www.linuxnet.com/smartcard/index.html ***
Re: MUSCLE and gemplus readers.
Hello all... Now I have yet ANOTHER twist to all this... On Tue, Jun 05, 2001 at 08:44:42PM +0100, Dr S N Henson wrote: > David Corcoran wrote: > > > > Hi, > > > > Try removing bundleparser.c and doing the ./configure --enable-usb > > and everything over again. > > > That did the trick. I still get a few kernel warning messages when I > plug the device in but I can now access the reader, thanks. I just recently got the American Express reader which is a GemPlus GCR 435. A wild guess would be an OEM version of the 430. Sure enough... Tweak a constant in usbserial.c and a couple of strings in ifd-GemPC430.bundle/Contents/Info.plist and the 430 driver drives the 435 reader (yes, the vendor code is the same and the product code changed from 0x430 to 0x435). Right now, it looks like we have to have two different bundles to support two different readers even though the drivers are virtually identical (other than the vendor code). Correct? If so, we should add something in here to support the 435? Somehow. > Steve. > -- > Dr Stephen N. Henson. http://www.drh-consultancy.demon.co.uk/ > Personal Email: [EMAIL PROTECTED] > Senior crypto engineer, Celo Communications: http://www.celocom.com/ > Core developer of the OpenSSL project: http://www.openssl.org/ > Business Email: [EMAIL PROTECTED] PGP key: via homepage. > *** > Linux Smart Card Developers - M.U.S.C.L.E. > (Movement for the Use of Smart Cards in a Linux Environment) > http://www.linuxnet.com/smartcard/index.html > *** Mike -- Michael H. Warfield| (770) 985-6132 | [EMAIL PROTECTED] (The Mad Wizard) | (678) 463-0932 | http://www.wittsend.com/mhw/ NIC whois: MHW9 | An optimist believes we live in the best of all PGP Key: 0xDF1DD471| possible worlds. A pessimist is sure of it! *** Linux Smart Card Developers - M.U.S.C.L.E. (Movement for the Use of Smart Cards in a Linux Environment) http://www.linuxnet.com/smartcard/index.html ***
Re: MUSCLE and gemplus readers.
On Tue, Jun 05, 2001 at 08:44:42PM +0100, Dr S N Henson wrote: > David Corcoran wrote: > > Hi, > > Try removing bundleparser.c and doing the ./configure --enable-usb > > and everything over again. > That did the trick. I still get a few kernel warning messages when I > plug the device in but I can now access the reader, thanks. Hmmm... I see a warning message like this: Jun 6 01:43:30 alcove kernel: usbdevfs: process 12931 (pcscd) did not claim interface 0 before use That's with Linux 2.4.5 and the GemPlus 435 reader I'm working with. > Steve. > -- > Dr Stephen N. Henson. http://www.drh-consultancy.demon.co.uk/ > Personal Email: [EMAIL PROTECTED] > Senior crypto engineer, Celo Communications: http://www.celocom.com/ > Core developer of the OpenSSL project: http://www.openssl.org/ > Business Email: [EMAIL PROTECTED] PGP key: via homepage. > *** > Linux Smart Card Developers - M.U.S.C.L.E. > (Movement for the Use of Smart Cards in a Linux Environment) > http://www.linuxnet.com/smartcard/index.html > *** Mike -- Michael H. Warfield| (770) 985-6132 | [EMAIL PROTECTED] (The Mad Wizard) | (678) 463-0932 | http://www.wittsend.com/mhw/ NIC whois: MHW9 | An optimist believes we live in the best of all PGP Key: 0xDF1DD471| possible worlds. A pessimist is sure of it! *** Linux Smart Card Developers - M.U.S.C.L.E. (Movement for the Use of Smart Cards in a Linux Environment) http://www.linuxnet.com/smartcard/index.html ***
