https://bugzilla.novell.com/show_bug.cgi?id=414468
User sbrys@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=414468#c21
--- Comment #21 from Simon Brys 2008-12-17 07:36:24 MST ---
Did some more testing with my ACR38U-CFC-ZET card reader. Sometimes the card is
read and sometimes it isn't. I see this both on Linux and on Windows.
I finally discovered that, in my case, it was due to the reader -- probably bad
build quality.
The following always works for my ACR38U-CFC-ZET reader (both on Linux and
Windows):
1) when you insert the card, there are two possible positions (you have to do
this with some feeling ;-):
- position 1: insert the card gently, until you feel a slight resistance
- position 2: insert the card gently, until you feel a slight resistance, and
then push it approx. one millimeter further, until the card really touches the
inside end of the reader
-> the card needs to be in the first position, i.e. it cannot touch the inside
end
2) with the card inserted in that first position, you need to push the card
downward. E.g. push the reader firmly onto your desk, insert the card into
"position 1", and then push the end of the card that sticks out of the reader
downward onto your desk and hold it there. I guess this somehow pushes the
card's chip more firmly against the chip reader.
It might take some experimenting to get it right. Whenever things go wrong,
it's possible that the PCSC daemon gets into a bad state, and you might need to
restart PCSC and/or remove & re-insert the reader.
My other readers (e.g. the ACR38U-SPC reader) don't require this fiddling
around -- plus they have only 1 possible way to insert the card. Looks like the
ACR38U-CFC-ZET reader is cheap stuff.
So in my case the problem is not related to the ACR38 driver, but to the ACR38
sub-model. But anyway, FYI: I tested this successfully on openSUSE 11.0 with
pcsc-acr38-1.7.9-92.1 and on openSUSE 11.1 with pcsc-acr38-1.7.9-137.40.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.