[Pcsclite-muscle] GemPC430 reader OK on 32-bit Kubuntu 14.10, fails on 64-bit

[Steve Langridge]

Hi Ludovic,

Thanks, your answer put me in the right direction.  The problem was that the 
actual card reader hardware was old, and although it claimed to be able to 
support full-speed usb, it was, in fact, very unreliable (more so on 64-bit 
than 32-bit).  Connecting it via a usb 1.1 hub (thus forcing the speed down) 
made it work fine.

I am looking now to obtain a newer model of the card reader to try out at 
full-speed. 

Thanks and regards,

Steve.

--- Original Message ---
From: Ludovic Rousseau
Sent: Monday 30 June 2014 11:37:10
To: steve at suttridge.co.za, Talks about MUSCLE
Cc: 
Subject: Re: [Pcsclite-muscle] GemPC430 reader OK on 32-bit Kubuntu 14.10, 
fails on 64-bit

2014-06-30 10:44 GMT+02:00 Steve Langridge <steve at suttridge.co.za>:
> Hi All,

Hello,

> I have two systems, one on 32-bit. the other on 64-bit, both Kubuntu 14.10,
> and using a GemPlus 430 card reader.  The pcsc-lite packages are :-
>
> pcscd : 1.8.10-1ubuntu1
> libccid : 1.4.15-1
> libgempc430 : 1.0.7-2
>
> Attached are the (colorised) log files from each of the systems.  This is 
just
> plugging in the card reader (no card present), and later unplugging it.
>
> On the 32-bit system, everything is fine, after plugging the reader in, it is
> polled (quite quickly) [tx: 01 17,  rx: 07 00 00 02 00 00 00 00]
> On the 64-bit system, after plugging in the reader, it is polled (at a 
slower
> rate than the 32-bit system), and after about two or three successful polls
> [tx: 01 17,  rx: 07 00 00 02 00 00 00 00], it no longer receives any replies
> [tx: 01 17,  rx: nothing].
>
> libusb_wrap.c:256:WriteUSB() 003/011: Resource temporarily unavailable
> ifdhandler.c:593:IFDHICCPresence() GCCmdCardStatus failed
> ifdwrapper.c:348:IFDStatusICC() Card not transacted: 612
> eventhandler.c:313:EHStatusHandlerThread() Error communicating to: GemPC430 
00
> 00
>
> These errors are sent to the system log all the while the card reader is
> plugged in.  Because of this, a card can never be recognised when inserted
> into the reader, and also the system log gets very large.
>
> Any one else experiencing this ?

You are using an old reader.
I wrote this driver more than 10 years ago :-)

I would first suspect libusb-0.1.
Maybe you can try with libusb-compat + libusb-1.0

Bye