[Pcsclite-muscle] Gemalto (was Gemplus) GemPC Key SmartCard Reader not working in debian stretch

[Wolfgang Pichler]

Hi,

i’ve also thought about a bug in the libusb - but also an upgrade to the latest libusb did not help. The same (latest) libusb version on amd64 did work - and on arm it did not work.

So - yes - without the workaround i have two Gemalto sticks - one is working - the other one not.

I am using this sticks on a raspberry - running a customized raspbian (odoo PosBox Image)

https://downloads.raspberrypi.org/raspbian_lite_latest


I’ve not tried an upgrade to the latest linux kernel - because i do not have a cross compile environment here - and i do not assume that it will have to do something with the bug.

Do you have a raspberry for testing ? I can send you these two sticks if you want.

br,
Wolfgang

> Am 22.05.2017 um 11:38 schrieb Ludovic Rousseau <ludovic.rousseau at gmail.com>:
> 
> 2017-05-22 11:26 GMT+02:00 Wolfgang Pichler <wpichler at callino.at <mailto:wpichler at callino.at>>:
> Hi,
> 
> Hello,
>  
> 
> i will try to collect this data.
> 
> An other thing i forgot to mention here - for me the bug only encountered on arm architecture (i have no idea why…) - the same lib versions on i386 / amd64 did worked.
> 
> I suspect a bug in the USB hardware or USB Linux layer of your arm platform then.
> 
> I just talked to a USB expert and the reader (USB device) has no idea of the reception buffer size. So the problem should not be in the reader (for this bug).
> 
> I found the problem by adding some debug lines - to see where it does not get the correct answer. At this point i recongnised that the lib request to ready 65535 bytes from the usb stack - which seemed to be too much ;-). So i simply used a fixed value - which will be enough for my needs (signing a 256 bytes hash). But as said - this is just a workaround for me - no bug fix.
> 
> The only difference i found between the two sticks is - that the one which worked announced on more speed entry than the other stick. The rest ist identically.
> 
> Without your change you have a working reader and a non working one?
> 
> Using the same hardware and software platform?
>  
> Here is the original thread for reference:
> http://lists.alioth.debian.org/pipermail/pcsclite-muscle/Week-of-Mon-20170220/000823.html <http://lists.alioth.debian.org/pipermail/pcsclite-muscle/Week-of-Mon-20170220/000823.html>
> 
> I forgot to answer - sorry.
> 
> The plattform is not a 2 byte int plattform. 
>  
> 
> The bug must be somewhere, where it does calculate the read size…
> 
> Try to upgrade to a recent Linux kernel.
> Are you using Linux?
> 
> Bye
> 
> -- 
>  Dr. Ludovic Rousseau
> _______________________________________________
> Pcsclite-muscle mailing list
> Pcsclite-muscle at lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pcsclite-muscle

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pcsclite-muscle/attachments/20170522/674da98b/attachment.html>