Support for Lenovo Integrated Smart Card Reader

[Daniel-345]

Dear list,

libccid/pcscd support[1] an integrated cardreader found in some Lenovo
notebooks[2]. I tried to make it work using libchipcardd but my attempts
remained unsuccessfull.
I added the device ID / a reader section to
/etc/udev/libchipcard.rules
/usr/share/chipcard/server/drivers/ccid_ifd.xml
and tried to use 'open' within cardcommander or "chipcard-tool [check|list|
monitor]" which didnt recognize any card.
Also starting as "chipcardd4 -f -v --loglevel debug --logtype console" did not
produce any output which would suggest the cardreader has been detected.
Hibiscus words fine using this reader, though it has alternative ways of
accessing the device and I'd like to use libchipcard-based software.

I'll be happy for any hints and suggestions. If there is further information
needed, just ask, I'll try to provide it.


Sincerely,

Daniel

[1] http://packages.debian.org/lenny/libccid (worked for me with pcsc_scan)
[2] http://www.thinkwiki.org/wiki/Lenovo_Integrated_Smart_Card_Reader

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Libchipcard-devel mailing list
Libchipcard-devel@...
https://lists.sourceforge.net/lists/listinfo/libchipcard-devel

[Martin Preuss]

Hi,

On Sonntag, 18. Januar 2009, Daniel wrote:
[...]
> I added the device ID / a reader section to
> /etc/udev/libchipcard.rules
> /usr/share/chipcard/server/drivers/ccid_ifd.xml
[...]

What USB ids does the reader show (product id, manufacturer id)?


Regards
Martin

--
"Things are only impossible until they're not"

Martin Preuss - http://www2.aquamaniac.de/
AqBanking - http://www.aqbanking.de/
LibChipcard - http://www.libchipcard.de/

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Libchipcard-devel mailing list
Libchipcard-devel@...
https://lists.sourceforge.net/lists/listinfo/libchipcard-devel

[Joachim Breitner-2]

Hi,

Am Montag, den 19.01.2009, 08:23 +0100 schrieb Martin Preuss:

> Hi,
>
> On Sonntag, 18. Januar 2009, Daniel wrote:
> [...]
> > I added the device ID / a reader section to
> > /etc/udev/libchipcard.rules
> > /usr/share/chipcard/server/drivers/ccid_ifd.xml
> [...]
>
> What USB ids does the reader show (product id, manufacturer id)?

I just received the (most likely) same reader. Here is what lsusb says:

Bus 001 Device 002: ID 08e6:34ec Gemplus

What is needed to make libchipcardd talk to a libccid reader?
http://www2.aquamaniac.de/sites/libchipcard/readers.php#ccid seems to
indicated that libchipcardd can use these directly. Is that right?

Greetings,
Joachim
--
Joachim "nomeata" Breitner
  mail: mail@... | ICQ# 74513189 | GPG-Key: 4743206C
  JID: nomeata@... | http://www.joachim-breitner.de/
  Debian Developer: nomeata@...


------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Libchipcard-devel mailing list
Libchipcard-devel@...
https://lists.sourceforge.net/lists/listinfo/libchipcard-devel

[Joachim Breitner-2]

Hi,

Am Donnerstag, den 22.01.2009, 14:37 +0100 schrieb Joachim Breitner:

> Am Montag, den 19.01.2009, 08:23 +0100 schrieb Martin Preuss:
> > Hi,
> >
> > On Sonntag, 18. Januar 2009, Daniel wrote:
> > [...]
> > > I added the device ID / a reader section to
> > > /etc/udev/libchipcard.rules
> > > /usr/share/chipcard/server/drivers/ccid_ifd.xml
> > [...]
> >
> > What USB ids does the reader show (product id, manufacturer id)?
>
> I just received the (most likely) same reader. Here is what lsusb says:
>
> Bus 001 Device 002: ID 08e6:34ec Gemplus
>
> What is needed to make libchipcardd talk to a libccid reader?
> http://www2.aquamaniac.de/sites/libchipcard/readers.php#ccid seems to
> indicated that libchipcardd can use these directly. Is that right?

it seems that I need 4.2.4, probably due to the hal interaction.

I have added the attached snippet
to /usr/share/chipcard/server/drivers/ccid_ifd.xml but chipcard has
trouble talking to the reader:

chipcardd starting
...
7:2009/01/22 15-15-44:chipcardd(30696):devicemanager.c: 3140: Device UsbRaw/08e6/34ec up
5:2009/01/22 15-15-44:chipcardd(30696):devicemanager.c: 3230: AUTOCONFIG: Created new reader "auto1-ccid_gempc_express" (UsbRaw/08e6/34ec)
5:2009/01/22 15-15-44:chipcardd(30696):devicemanager.c: 3266: Assigned device path "usb:08e6/34ec:libusb:001:002" to reader "auto1-ccid_gempc_express"
7:2009/01/22 15-15-44:chipcardd(30696):clr_notification.c:  162: Mask for reader:add is 00000400
6:2009/01/22 15-15-44:chipcardd(30696):clr_notification.c:  190: Sending notification reader:add to all clients
...
(now running geldkarte loaded)
...
 String size is 167:
  0000: 69 70 63 20 7b 0a 63 68 61 72 20 69 64 3d 22 31 ipc {.char id="1
  0010: 22 0a 63 68 61 72 20 63 6d 64 3d 22 43 6c 69 65 ".char cmd="Clie
  0020: 6e 74 5f 52 65 61 64 79 22 0a 7d 0a 64 61 74 61 nt_Ready".}.data
  0030: 20 7b 0a 63 68 61 72 20 41 70 70 6c 69 63 61 74  {.char Applicat
  0040: 69 6f 6e 3d 22 67 65 6c 64 6b 61 72 74 65 22 0a ion="geldkarte".
  0050: 63 68 61 72 20 47 77 65 6e 56 65 72 73 69 6f 6e char GwenVersion
  0060: 3d 22 33 2e 36 2e 30 73 74 61 62 6c 65 2d 30 22 ="3.6.0stable-0"
  0070: 0a 63 68 61 72 20 43 68 69 70 63 61 72 64 56 65 .char ChipcardVe
  0080: 72 73 69 6f 6e 3d 22 34 2e 32 2e 34 2e 30 73 74 rsion="4.2.4.0st
  0090: 61 62 6c 65 22 0a 63 68 61 72 20 53 79 73 74 65 able".char Syste
  00a0: 6d 3d 22 22 0a 7d 0a                            m="".}.
7:2009/01/22 15-16-42:chipcardd(30696):devicemanager.c: 1927: Command "Client_Ready" not handled by device manager
5:2009/01/22 15-16-42:chipcardd(30696):clr_clientready.c:  105: Client "49787f92" started (geldkarte, Gwen 3.6.0stable-0, ChipCard 4.2.4.0stable)
7:2009/01/22 15-16-42:chipcardd(30696):clr_clientready.c:  137: Response sent.
  String size is 57:
  0000: 69 70 63 20 7b 0a 63 68 61 72 20 69 64 3d 22 32 ipc {.char id="2
  0010: 22 0a 63 68 61 72 20 63 6d 64 3d 22 43 6c 69 65 ".char cmd="Clie
  0020: 6e 74 5f 53 74 61 72 74 57 61 69 74 22 0a 7d 0a nt_StartWait".}.
  0030: 64 61 74 61 20 7b 0a 7d 0a                      data {.}.
7:2009/01/22 15-16-42:chipcardd(30696):devicemanager.c: 1927: Command "Client_StartWait" not handled by device manager
5:2009/01/22 15-16-42:chipcardd(30696):clr_startwait.c:   70: Client 49787f92: StartWait [geldkarte/nobody]
3:2009/01/22 15-16-42:chipcardd(30696):devicemanager.c: 1746: Incrementing active reader count auto1-ccid_gempc_express (49787f91) [1]
3:2009/01/22 15-16-42:chipcardd(30696):dm_driver.c:  359: Incrementing active readers count of driver ccid_ifd [49787f91](0->1)
6:2009/01/22 15-16-42:chipcardd(30696):dm_driver.c:  362: Some readers active, driver leaving idle mode
(now a delay)
6:2009/01/22 15-16-52:chipcardd(30696):devicemanager.c:  813: Starting driver "ccid_ifd"
6:2009/01/22 15-16-52:chipcardd(30696):devicemanager.c:  906: Starting driver process for driver "ccid_ifd" (/usr/lib/chipcard/server/drivers/ifd)
6:2009/01/22 15-16-52:chipcardd(30696):devicemanager.c:  907: Arguments are: " -l /usr/lib/pcsc/drivers/ifd-ccid.bundle/Contents/Linux/libccid.so.1.3.8 --logtype file --logfile /var/log/chipcard/drivers/ccid_ifd/@reader@.log -t local -a /var/run/chipcard/chipcard.comm -p 0 -i 49787f91"
6:2009/01/22 15-16-52:chipcardd(30696):devicemanager.c:  926: Process started
7:2009/01/22 15-16-52:chipcardd(30696):clr_notification.c:  162: Mask for driver:start is 00000001
6:2009/01/22 15-16-52:chipcardd(30696):clr_notification.c:  190: Sending notification driver:start to all clients
7:2009/01/22 15-16-52:chipcardd(30696):clr_notification.c:  207: Client "49787f92" is not interested in driver:start [00000000]
7:2009/01/22 15-16-52:chipcardd(30696):devicemanager.c: 1199: still waiting for driver start
7:2009/01/22 15-16-52:chipcardd(30696):devicemanager.c: 1199: still waiting for driver start
7:2009/01/22 15-16-52:chipcardd(30696):devicemanager.c: 1199: still waiting for driver start
7:2009/01/22 15-16-52:chipcardd(30696):devicemanager.c: 1199: still waiting for driver start
7:2009/01/22 15-16-52:chipcardd(30696):devicemanager.c: 1199: still waiting for driver start
  String size is 119:
  0000: 69 70 63 20 7b 0a 63 68 61 72 20 69 64 3d 22 31 ipc {.char id="1
  0010: 22 0a 63 68 61 72 20 63 6d 64 3d 22 44 72 69 76 ".char cmd="Driv
  0020: 65 72 5f 52 65 61 64 79 22 0a 7d 0a 64 61 74 61 er_Ready".}.data
  0030: 20 7b 0a 63 68 61 72 20 64 72 69 76 65 72 49 64  {.char driverId
  0040: 3d 22 34 39 37 38 37 66 39 31 22 0a 69 6e 74 20 ="49787f91".int
  0050: 20 63 6f 64 65 3d 22 30 22 0a 63 68 61 72 20 74  code="0".char t
  0060: 65 78 74 3d 22 4c 69 62 72 61 72 79 20 6c 6f 61 ext="Library loa
  0070: 64 65 64 22 0a 7d 0a                            ded".}.
7:2009/01/22 15-16-52:chipcardd(30696):devicemanager.c: 1962: Driver 49787f95: DriverReady
5:2009/01/22 15-16-52:chipcardd(30696):devicemanager.c: 2108: Driver "49787f91" (ccid_ifd) is up (Library loaded)
7:2009/01/22 15-16-52:chipcardd(30696):clr_notification.c:  162: Mask for driver:up is 00000002
6:2009/01/22 15-16-52:chipcardd(30696):clr_notification.c:  190: Sending notification driver:up to all clients
7:2009/01/22 15-16-52:chipcardd(30696):clr_notification.c:  207: Client "49787f92" is not interested in driver:up [00000000]
7:2009/01/22 15-16-52:chipcardd(30696):clr_notification.c:  162: Mask for reader:start is 00000040
6:2009/01/22 15-16-52:chipcardd(30696):clr_notification.c:  190: Sending notification reader:start to all clients
7:2009/01/22 15-16-52:chipcardd(30696):clr_notification.c:  207: Client "49787f92" is not interested in reader:start [00000000]
7:2009/01/22 15-16-52:chipcardd(30696):devicemanager.c: 1561: Still some time left
7:2009/01/22 15-16-52:chipcardd(30696):devicemanager.c: 1561: Still some time left
7:2009/01/22 15-16-53:chipcardd(30696):devicemanager.c: 1561: Still some time left
7:2009/01/22 15-16-53:chipcardd(30696):devicemanager.c: 1561: Still some time left
7:2009/01/22 15-16-53:chipcardd(30696):devicemanager.c: 1561: Still some time left
  String size is 186:
  0000: 69 70 63 20 7b 0a 63 68 61 72 20 69 64 3d 22 32 ipc {.char id="2
  0010: 22 0a 63 68 61 72 20 72 65 66 69 64 3d 22 32 22 ".char refid="2"
  0020: 0a 63 68 61 72 20 63 6d 64 3d 22 44 72 69 76 65 .char cmd="Drive
  0030: 72 5f 53 74 61 72 74 52 65 61 64 65 72 52 65 73 r_StartReaderRes
  0040: 70 6f 6e 73 65 22 0a 7d 0a 64 61 74 61 20 7b 0a ponse".}.data {.
  0050: 63 68 61 72 20 72 65 61 64 65 72 49 64 3d 22 34 char readerId="4
  0060: 39 37 38 37 66 39 31 22 0a 63 68 61 72 20 69 6e 9787f91".char in
  0070: 66 6f 3d 22 75 6e 69 74 30 25 33 44 25 32 32 69 fo="unit0%3D%22i
  0080: 63 63 31 25 32 32 22 0a 69 6e 74 20 20 63 6f 64 cc1%22".int  cod
  0090: 65 3d 22 30 22 0a 63 68 61 72 20 74 65 78 74 3d e="0".char text=
  00a0: 22 52 65 61 64 65 72 20 75 70 20 61 6e 64 20 77 "Reader up and w
  00b0: 61 69 74 69 6e 67 22 0a 7d 0a                   aiting".}.
5:2009/01/22 15-16-53:chipcardd(30696):devicemanager.c: 1503: Reader "auto1-ccid_gempc_express" is up (Reader up and waiting)
7:2009/01/22 15-16-53:chipcardd(30696):clr_notification.c:  162: Mask for reader:up is 00000080
6:2009/01/22 15-16-53:chipcardd(30696):clr_notification.c:  190: Sending notification reader:up to all clients
7:2009/01/22 15-16-53:chipcardd(30696):clr_notification.c:  207: Client "49787f92" is not interested in reader:up [00000000]
  String size is 262:
  0000: 69 70 63 20 7b 0a 63 68 61 72 20 69 64 3d 22 33 ipc {.char id="3
  0010: 22 0a 63 68 61 72 20 63 6d 64 3d 22 44 72 69 76 ".char cmd="Driv
  0020: 65 72 5f 43 61 72 64 49 6e 73 65 72 74 65 64 22 er_CardInserted"
  0030: 0a 7d 0a 64 61 74 61 20 7b 0a 63 68 61 72 20 72 .}.data {.char r
  0040: 65 61 64 65 72 49 64 3d 22 34 39 37 38 37 66 39 eaderId="49787f9
  0050: 31 22 0a 63 68 61 72 20 64 72 69 76 65 72 73 52 1".char driversR
  0060: 65 61 64 65 72 49 64 3d 22 30 30 30 30 30 30 30 eaderId="0000000
  0070: 31 22 0a 69 6e 74 20 20 73 6c 6f 74 6e 75 6d 3d 1".int  slotnum=
  0080: 22 30 22 0a 69 6e 74 20 20 63 61 72 64 6e 75 6d "0".int  cardnum
  0090: 3d 22 31 22 0a 62 69 6e 20 20 61 74 72 3d 22 33 ="1".bin  atr="3
  00a0: 42 45 46 30 30 46 46 38 31 33 31 46 45 34 35 36 BEF00FF8131FE456
  00b0: 35 36 33 31 31 30 38 34 33 30 32 35 30 30 30 31 5631108430250001
  00c0: 30 36 34 36 30 30 30 30 31 30 35 33 30 33 35 22 064600001053035"
  00d0: 0a 63 68 61 72 20 63 61 72 64 54 79 70 65 3d 22 .char cardType="
  00e0: 50 52 4f 43 45 53 53 4f 52 22 0a 63 68 61 72 20 PROCESSOR".char
  00f0: 64 72 69 76 65 72 49 64 3d 22 34 39 37 38 37 66 driverId="49787f
  0100: 39 31 22 0a 7d 0a                               91".}.
7:2009/01/22 15-16-53:chipcardd(30696):devicemanager.c: 2170: Driver 49787f95: Card inserted
5:2009/01/22 15-16-53:chipcardd(30696):devicemanager.c: 2286: New card "00000000" found in reader "auto1-ccid_gempc_express"(49787f91)
7:2009/01/22 15-16-53:chipcardd(30696):cardmanager.c:  138: New card added
4:2009/01/22 15-16-53:chipcardd(30696):clientmanager.c:  197: Advertising card "00000001" to all interested clients
5:2009/01/22 15-16-53:chipcardd(30696):clr_startwait.c:  136: Advertising card "00000001" to client "49787f92" [geldkarte/nobody]
7:2009/01/22 15-16-53:chipcardd(30696):clr_notification.c:  162: Mask for card:inserted is 00010000
6:2009/01/22 15-16-53:chipcardd(30696):clr_notification.c:  190: Sending notification card:inserted to all clients
7:2009/01/22 15-16-53:chipcardd(30696):clr_notification.c:  207: Client "49787f92" is not interested in card:inserted [00000000]
  String size is 79:
  0000: 69 70 63 20 7b 0a 63 68 61 72 20 69 64 3d 22 33 ipc {.char id="3
  0010: 22 0a 63 68 61 72 20 63 6d 64 3d 22 43 6c 69 65 ".char cmd="Clie
  0020: 6e 74 5f 54 61 6b 65 43 61 72 64 22 0a 7d 0a 64 nt_TakeCard".}.d
  0030: 61 74 61 20 7b 0a 63 68 61 72 20 63 61 72 64 69 ata {.char cardi
  0040: 64 3d 22 30 30 30 30 30 30 30 31 22 0a 7d 0a    d="00000001".}.
7:2009/01/22 15-16-53:chipcardd(30696):devicemanager.c: 1927: Command "Client_TakeCard" not handled by device manager
5:2009/01/22 15-16-53:chipcardd(30696):clr_takecard.c:   83: Client 49787f92: TakeCard [geldkarte/nobody]
5:2009/01/22 15-16-53:chipcardd(30696):clr_takecard.c:  166: Enqueued TakeCard request for card "00000001" and client "49787f92"
3:2009/01/22 15-16-53:chipcardd(30696):clr_takecard.c:  185: Working on TakeCard request 49787f9a
6:2009/01/22 15-16-53:chipcardd(30696):clr_takecard.c:  204: Step 1 (49787f9a)
5:2009/01/22 15-16-53:chipcardd(30696):cm_card.c:  183: Lock request granted
6:2009/01/22 15-16-53:chipcardd(30696):clr_takecard.c:  239: Card lock acquired, now locking slot (49787f9a)
3:2009/01/22 15-16-53:chipcardd(30696):clr_takecard.c:  185: Working on TakeCard request 49787f9a
6:2009/01/22 15-16-53:chipcardd(30696):clr_takecard.c:  275: Step 2 (49787f9a)
5:2009/01/22 15-16-53:chipcardd(30696):lockmanager.c:  167: Lock request granted
  String size is 122:
  0000: 69 70 63 20 7b 0a 63 68 61 72 20 69 64 3d 22 34 ipc {.char id="4
  0010: 22 0a 63 68 61 72 20 63 6d 64 3d 22 43 6c 69 65 ".char cmd="Clie
  0020: 6e 74 5f 43 6f 6d 6d 61 6e 64 43 61 72 64 22 0a nt_CommandCard".
  0030: 7d 0a 64 61 74 61 20 7b 0a 63 68 61 72 20 63 61 }.data {.char ca
  0040: 72 64 69 64 3d 22 30 30 30 30 30 30 30 31 22 0a rdid="00000001".
  0050: 62 69 6e 20 20 64 61 74 61 3d 22 30 30 41 34 30 bin  data="00A40
  0060: 30 30 43 22 0a 63 68 61 72 20 74 61 72 67 65 74 00C".char target
  0070: 3d 22 63 61 72 64 22 0a 7d 0a                   ="card".}.
7:2009/01/22 15-16-53:chipcardd(30696):devicemanager.c: 1927: Command "Client_CommandCard" not handled by device manager
5:2009/01/22 15-16-53:chipcardd(30696):clr_execapdu.c:   88: Client 49787f92: ExecApdu [geldkarte/nobody]
7:2009/01/22 15-16-53:chipcardd(30696):lockmanager.c:  284: slot currently locked by "49787fd5" (wanted: 49787fd5)
5:2009/01/22 15-16-53:chipcardd(30696):clr_execapdu.c:  231: Enqueued ExecApdu request for card "00000001" and client "49787f92"
7:2009/01/22 15-16-53:chipcardd(30696):clr_execapdu.c:  332: Working on CardCommand request
7:2009/01/22 15-16-53:chipcardd(30696):clr_execapdu.c:  246: Working on ExecApdu request
7:2009/01/22 15-16-53:chipcardd(30696):clr_execapdu.c:  332: Working on CardCommand request
7:2009/01/22 15-16-53:chipcardd(30696):clr_execapdu.c:  246: Working on ExecApdu request
7:2009/01/22 15-16-53:chipcardd(30696):clr_execapdu.c:  332: Working on CardCommand request
7:2009/01/22 15-16-53:chipcardd(30696):clr_execapdu.c:  246: Working on ExecApdu request
  String size is 188:
  0000: 69 70 63 20 7b 0a 63 68 61 72 20 69 64 3d 22 34 ipc {.char id="4
  0010: 22 0a 63 68 61 72 20 72 65 66 69 64 3d 22 33 22 ".char refid="3"
  0020: 0a 63 68 61 72 20 63 6d 64 3d 22 44 72 69 76 65 .char cmd="Drive
  0030: 72 5f 43 61 72 64 43 6f 6d 6d 61 6e 64 52 65 73 r_CardCommandRes
  0040: 70 6f 6e 73 65 22 0a 7d 0a 64 61 74 61 20 7b 0a ponse".}.data {.
  0050: 69 6e 74 20 20 63 6f 64 65 3d 22 2d 31 30 30 22 int  code="-100"
  0060: 0a 63 68 61 72 20 74 65 78 74 3d 22 55 6e 6b 6e .char text="Unkn
  0070: 6f 77 20 65 72 72 6f 72 20 63 6f 64 65 22 0a 63 ow error code".c
  0080: 68 61 72 20 72 65 61 64 65 72 49 64 3d 22 34 39 har readerId="49
  0090: 37 38 37 66 39 31 22 0a 69 6e 74 20 20 73 6c 6f 787f91".int  slo
  00a0: 74 6e 75 6d 3d 22 30 22 0a 69 6e 74 20 20 63 61 tnum="0".int  ca
  00b0: 72 64 6e 75 6d 3d 22 31 22 0a 7d 0a             rdnum="1".}.
7:2009/01/22 15-16-53:chipcardd(30696):clr_execapdu.c:  332: Working on CardCommand request
7:2009/01/22 15-16-53:chipcardd(30696):clr_execapdu.c:  246: Working on ExecApdu request
7:2009/01/22 15-16-53:chipcardd(30696):clr_execapdu.c:  272: Sending response to CommandCard
5:2009/01/22 15-16-53:chipcardd(30696):clientmanager.c:  490: Resetting card "00000001"
5:2009/01/22 15-16-53:chipcardd(30696):cm_card.c:  280: Unlocking card from client 49787f92
6:2009/01/22 15-16-53:chipcardd(30696):clientmanager.c:  326: Card "00000001" unlocked from client
5:2009/01/22 15-16-53:chipcardd(30696):lockmanager.c:  222: Removing lock of client "49787f92" on slot
5:2009/01/22 15-16-53:chipcardd(30696):clientmanager.c:  398: Removing client 49787f92 [geldkarte/nobody]


While the geldkarte command shows:
$ geldkarte loaded
Waiting for card to be inserted: Started.
Waiting for card to be inserted: 5000 of 20000
Waiting for card to be inserted: 10000 of 20000
Waiting for card to be inserted: Finished.
3:2009/01/22 15-16-53:geldkarte3(30697):clientlcc_cmd.c:  483: Command error -100 (Unknow error code)
3:2009/01/22 15-16-53:geldkarte3(30697):clientlcc_cmd.c:  532: Error response for request "commandCard"
ERROR: Error executing command CardOpen (3).
3:2009/01/22 15-16-53:geldkarte3(30697):client.c:  361: Still 1 cards in use at LC_Client_free!

And the file /var/log/chipcard/drivers/ccid_ifd/auto1-ccid_gempc_express.log shows:
5:2009/01/22 15-16-52:auto1-ccid_gempc_express(30698):d_startreader.c:  223: Init reader auto1-ccid_gempc_express
5:2009/01/22 15-16-53:auto1-ccid_gempc_express(30698):d_startreader.c:  249: ReaderInfo: unit0="icc1"
5:2009/01/22 15-16-53:auto1-ccid_gempc_express(30698):d_startreader.c:  256: Reader up and waiting
5:2009/01/22 15-16-53:auto1-ccid_gempc_express(30698):d_startreader.c:  268: Reader start handled
5:2009/01/22 15-16-53:auto1-ccid_gempc_express(30698):d_work.c:  128: Card inserted, trying to connect it
5:2009/01/22 15-16-53:auto1-ccid_gempc_express(30698):d_work.c:  142: Status changed on slot 0 (00000000->00030000) (cardnum 0)
3:2009/01/22 15-16-53:auto1-ccid_gempc_express(30698):driverifd.c:  451: CCID error on "CCIDTransmit/Control": 612
3:2009/01/22 15-16-53:auto1-ccid_gempc_express(30698):d_cardcommand.c:  153: Error executing APDU (00000064)
5:2009/01/22 15-16-53:auto1-ccid_gempc_express(30698):d_resetcard.c:   81: Resetting card
5:2009/01/22 15-17-43:auto1-ccid_gempc_express(30698):d_stopreader.c:   47: Disconnecting reader
5:2009/01/22 15-17-43:auto1-ccid_gempc_express(30698):d_stopreader.c:   60: Deinit succeeded


Any idea what might be wrong?

Thanks,
Joachim

--
Joachim "nomeata" Breitner
  mail: mail@... | ICQ# 74513189 | GPG-Key: 4743206C
  JID: nomeata@... | http://www.joachim-breitner.de/
  Debian Developer: nomeata@...

    <reader name="ccid_gempc_express" busType="UsbRaw"
            addressType="devicePath"
            devicePathTmpl="usb:$(vendorId:04x)/$(productId:04x):libusb:$(busName):$(deviceName)"
            vendor="0x08e6" product="0x34ec" >
      <short>GemPC Express</short>
      <!--
        <flags>
          <flag>keypad</flag>
        </flags>
      -->
    </reader>



------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Libchipcard-devel mailing list
Libchipcard-devel@...
https://lists.sourceforge.net/lists/listinfo/libchipcard-devel

[Martin Preuss]

Hi,

On Donnerstag, 22. Januar 2009, Joachim Breitner wrote:
[...]
> Bus 001 Device 002: ID 08e6:34ec Gemplus
>
> What is needed to make libchipcardd talk to a libccid reader?
> http://www2.aquamaniac.de/sites/libchipcard/readers.php#ccid seems to
> indicated that libchipcardd can use these directly. Is that right?
[...]

Libchipcard uses the free CCID driver to contact those readers. If you give me
the name of the reader I can add an entry for it into the driver description
file (that's what's needed to announce a new reader to libchipcard).


Regards
Martin



--
"Things are only impossible until they're not"

Martin Preuss - http://www2.aquamaniac.de/
AqBanking - http://www.aqbanking.de/
LibChipcard - http://www.libchipcard.de/

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Libchipcard-devel mailing list
Libchipcard-devel@...
https://lists.sourceforge.net/lists/listinfo/libchipcard-devel

[Joachim Breitner-2]

Hi,

Am Donnerstag, den 22.01.2009, 15:25 +0100 schrieb Martin Preuss:
> Libchipcard uses the free CCID driver to contact those readers. If you give me
> the name of the reader I can add an entry for it into the driver description
> file (that's what's needed to announce a new reader to libchipcard).

see my other mail.

At least on Debian, libccid ships a file /etc/libccid_Info.plist that
lists the usb ids and a human readable name for all supported drivers.
Maybe this can be used directly, so new supported drivers in libccid
will automatically appear in libchipcard?

Greetings,
Joachim

--
Joachim "nomeata" Breitner
  mail: mail@... | ICQ# 74513189 | GPG-Key: 4743206C
  JID: nomeata@... | http://www.joachim-breitner.de/
  Debian Developer: nomeata@...


------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Libchipcard-devel mailing list
Libchipcard-devel@...
https://lists.sourceforge.net/lists/listinfo/libchipcard-devel

[Joachim Breitner-2]

Hi again,

Am Donnerstag, den 22.01.2009, 15:20 +0100 schrieb Joachim Breitner:
> Any idea what might be wrong?

actually, I can open both my Geldkarten as well as my OpenGPG with
cardcommander:

Card: open
Waiting for a card to be inserted...
Waiting for card to be inserted: Started.
Waiting for card to be inserted: 5000 of 20000
Waiting for card to be inserted: Finished.
Card is open, info follows:
  Card
  ===========================================================================
  Card id       : 00000003
  Card type     : PROCESSOR
  Driver type   : ccid_ifd
  Reader type   : ccid_gempc_express
  Card types    : ddv1 geldkarte ProcessorCard
  Reader flags  : auto
  ATR
  ---------------------------------------------------------------------------
    String size is 25:
    0000: 3b ff 18 00 ff 81 31 3c 45 65 63 0d 02 31 02 50 ;.....1<Eec..1.P
    0010: 00 10 90 14 05 00 04 10 3e                      ........>
  ===========================================================================

but I can’t access the Krankenversicherunskarte this way, and kvkcard
does not work either (as if the card is broken – can’t test this ATM).

Maybe that helps.

Greetings,
Joachim

--
Joachim "nomeata" Breitner
  mail: mail@... | ICQ# 74513189 | GPG-Key: 4743206C
  JID: nomeata@... | http://www.joachim-breitner.de/
  Debian Developer: nomeata@...


------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Libchipcard-devel mailing list
Libchipcard-devel@...
https://lists.sourceforge.net/lists/listinfo/libchipcard-devel

[Martin Preuss]

Hi,

On Donnerstag, 22. Januar 2009, Joachim Breitner wrote:
[...]
> but I can’t access the Krankenversicherunskarte this way, and kvkcard
> does not work either (as if the card is broken – can’t test this ATM).
[...]

Unfortunately this is totally normal: KV cards are memory cards, and those
cards aren't supported by most IFD drivers (because in the beginning nobody
seemed to have thought of memory cards  when designing PC/SC).

Some manufacturers provide proprietary extensions to support memory cards,
others allow the use of the protocol "RAW" to talk to such cards (libchipcard
supports this approach).

So when using IFD drivers in many cases KV cards are inaccessible.


Regards
Martin



--
"Things are only impossible until they're not"

Martin Preuss - http://www2.aquamaniac.de/
AqBanking - http://www.aqbanking.de/
LibChipcard - http://www.libchipcard.de/

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Libchipcard-devel mailing list
Libchipcard-devel@...
https://lists.sourceforge.net/lists/listinfo/libchipcard-devel

[Daniel-345]

Hi everyone,

> > I added the device ID / a reader section to
> > /etc/udev/libchipcard.rules
> > /usr/share/chipcard/server/drivers/ccid_ifd.xml

> What USB ids does the reader show (product id, manufacturer id)?
As in the ThinkWiki link I attached [1], it is
Bus 006 Device 002: ID 17ef:1003 Lenovo
for me, as well.
I attached a complete lsusb output, in case it come in handy for anyone.


Sincerely,

Daniel

[1] http://www.thinkwiki.org/wiki/Lenovo_Integrated_Smart_Card_Reader


Bus 006 Device 002: ID 17ef:1003 Lenovo
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0         8
  idVendor           0x17ef Lenovo
  idProduct          0x1003
  bcdDevice            1.00
  iManufacturer           1 Lenovo
  iProduct                2 Integrated Smart Card Reader
  iSerial                 0
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           93
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0
    bmAttributes         0xa0
      (Bus Powered)
      Remote Wakeup
    MaxPower              100mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           3
      bInterfaceClass        11 Chip/SmartCard
      bInterfaceSubClass      0
      bInterfaceProtocol      0
      iInterface              0
      ChipCard Interface Descriptor:
        bLength                54
        bDescriptorType        33
        bcdCCID              1.00
        nMaxSlotIndex           0
        bVoltageSupport         7  5.0V 3.0V 1.8V
        dwProtocols             3  T=0 T=1
        dwDefaultClock       4000
        dwMaxiumumClock      4000
        bNumClockSupported      0
        dwDataRate          10752 bps
        dwMaxDataRate      500000 bps
        bNumDataRatesSupp.      0
        dwMaxIFSD             254
        dwSyncProtocols  00000000
        dwMechanical     00000000
        dwFeatures       00010230
          Auto clock change
          Auto baud rate change
          NAD value other than 0x00 accpeted
          TPDU level exchange
        dwMaxCCIDMsgLen       271
        bClassGetResponse      00
        bClassEnvelope         00
        wlcdLayout           none
        bPINSupport             0
        bMaxCCIDBusySlots       1
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82  EP 2 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0008  1x 8 bytes
        bInterval              24
Device Status:     0x0000
  (Bus Powered)

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Libchipcard-devel mailing list
Libchipcard-devel@...
https://lists.sourceforge.net/lists/listinfo/libchipcard-devel

[Daniel-345]

Hi everyone,

On Thursday 22 January 2009 14:37:45 Joachim Breitner wrote:
> > > I added the device ID / a reader section to
> > > /etc/udev/libchipcard.rules
> > > /usr/share/chipcard/server/drivers/ccid_ifd.xml
> > What USB ids does the reader show (product id, manufacturer id)?
> I just received the (most likely) same reader. Here is what lsusb says:
> Bus 001 Device 002: ID 08e6:34ec Gemplus
No, this is a different reader. Are you sure it is internal/integrated and not
the external one Lenovo offers as an accessory?
Though the one I mentioned connects via USB, it is an actual part of the
notebook, like the fingerprint readers which connect via USB too and are
built into the case, hence the word "Integrated" in the name.


Sincerely,

Daniel

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Libchipcard-devel mailing list
Libchipcard-devel@...
https://lists.sourceforge.net/lists/listinfo/libchipcard-devel

[Joachim Breitner]

Hi,

Am Donnerstag, den 22.01.2009, 17:27 +0100 schrieb Daniel:

> On Thursday 22 January 2009 14:37:45 Joachim Breitner wrote:
> > > > I added the device ID / a reader section to
> > > > /etc/udev/libchipcard.rules
> > > > /usr/share/chipcard/server/drivers/ccid_ifd.xml
> > > What USB ids does the reader show (product id, manufacturer id)?
> > I just received the (most likely) same reader. Here is what lsusb says:
> > Bus 001 Device 002: ID 08e6:34ec Gemplus
> No, this is a different reader. Are you sure it is internal/integrated and not
> the external one Lenovo offers as an accessory?
> Though the one I mentioned connects via USB, it is an actual part of the
> notebook, like the fingerprint readers which connect via USB too and are
> built into the case, hence the word "Integrated" in the name.

you are right, mine is not the integrated one. I didn’t know there were
integrated – what model do you have? And you should probably try
libchipcard 4.2.4, as we had the same symptoms at first.

Martin, thx for the clarification WRT to memory cards. Did the other
errors tell you something?

Greetings,
Joachim
--
Joachim "nomeata" Breitner
Debian Developer
  nomeata@... | ICQ# 74513189 | GPG-Keyid: 4743206C
  JID: nomeata@... | http://people.debian.org/~nomeata


------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Libchipcard-devel mailing list
Libchipcard-devel@...
https://lists.sourceforge.net/lists/listinfo/libchipcard-devel

[Martin Preuss]

Hi,

On Donnerstag, 22. Januar 2009, Daniel wrote:
[...]
> > What USB ids does the reader show (product id, manufacturer id)?
>
> As in the ThinkWiki link I attached [1], it is
> Bus 006 Device 002: ID 17ef:1003 Lenovo
> for me, as well.
[...]

I know, and it should already be supported by the latest libchipcard 4.2.4 (as
of today).


Regards
Martin



--
"Things are only impossible until they're not"

Martin Preuss - http://www2.aquamaniac.de/
AqBanking - http://www.aqbanking.de/
LibChipcard - http://www.libchipcard.de/

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Libchipcard-devel mailing list
Libchipcard-devel@...
https://lists.sourceforge.net/lists/listinfo/libchipcard-devel

[Martin Preuss]

Hi,

On Donnerstag, 22. Januar 2009, Joachim Breitner wrote:
[...]
> Martin, thx for the clarification WRT to memory cards. Did the other
> errors tell you something?
[...]

What other errors are you referring to? I thought you already are able to open
cards with card commander?


Regards
Martin



--
"Things are only impossible until they're not"

Martin Preuss - http://www2.aquamaniac.de/
AqBanking - http://www.aqbanking.de/
LibChipcard - http://www.libchipcard.de/

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Libchipcard-devel mailing list
Libchipcard-devel@...
https://lists.sourceforge.net/lists/listinfo/libchipcard-devel

[Joachim Breitner-2]

Hi,

Am Donnerstag, den 22.01.2009, 18:00 +0100 schrieb Martin Preuss:
> On Donnerstag, 22. Januar 2009, Joachim Breitner wrote:
> [...]
> > Martin, thx for the clarification WRT to memory cards. Did the other
> > errors tell you something?
> [...]
>
> What other errors are you referring to? I thought you already are able to open
> cards with card commander?

The mail from Thu, 22 Jan 2009 15:20:35 +0100 contains the logs. I can
open the card, but I can not use geldkarte to read it (nor use
qbankmanager to do online banking).

Greetings,
Joachim


--
Joachim Breitner
  e-Mail: mail@...
  Homepage: http://www.joachim-breitner.de
  ICQ#: 74513189
  Jabber-ID: nomeata@...


------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Libchipcard-devel mailing list
Libchipcard-devel@...
https://lists.sourceforge.net/lists/listinfo/libchipcard-devel

[Martin Preuss]

Hi,

On Donnerstag, 22. Januar 2009, Joachim Breitner wrote:
[...]
> The mail from Thu, 22 Jan 2009 15:20:35 +0100 contains the logs. I can
> open the card, but I can not use geldkarte to read it (nor use
> qbankmanager to do online banking).
[...]

Ok, in this case I need a different log: Please set the ENV
variable "LC_LOGLEVEL=info" (or "debug" for that matter) and try
again "geldkarte loaded".

The console should show much more info which might help solve the problem.


Regards
Martin




--
"Things are only impossible until they're not"

Martin Preuss - http://www2.aquamaniac.de/
AqBanking - http://www.aqbanking.de/
LibChipcard - http://www.libchipcard.de/

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Libchipcard-devel mailing list
Libchipcard-devel@...
https://lists.sourceforge.net/lists/listinfo/libchipcard-devel

[Daniel-345]

Hi,

> you are right, mine is not the integrated one. I didn’t know there were
> integrated – what model do you have?
As the ThinkWiki-Article indicates, a T61. To be more specific, a 7658CTO.

> And you should probably try
> libchipcard 4.2.4, as we had the same symptoms at first.
I'll try it out as soon as I have the time.


Sincerely,

Daniel

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Libchipcard-devel mailing list
Libchipcard-devel@...
https://lists.sourceforge.net/lists/listinfo/libchipcard-devel

[Daniel-345]

Hi,

> > > What USB ids does the reader show (product id, manufacturer id)?
> > As in the ThinkWiki link I attached [1], it is
> > Bus 006 Device 002: ID 17ef:1003 Lenovo
> > for me, as well.
> I know, and it should already be supported by the latest libchipcard 4.2.4
> (as of today).
Wasn't aware of that; I thought you didn't recieve the mail I sent before, as
I accidently replied to you, not to the list at first. :-)
Thanks, I'll give it a try as soon as possible.


Sincerely,

Daniel

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Libchipcard-devel mailing list
Libchipcard-devel@...
https://lists.sourceforge.net/lists/listinfo/libchipcard-devel

[Joachim Breitner-2]

Hi,

Am Donnerstag, den 22.01.2009, 18:08 +0100 schrieb Martin Preuss:

> Hi,
>
> On Donnerstag, 22. Januar 2009, Joachim Breitner wrote:
> [...]
> > The mail from Thu, 22 Jan 2009 15:20:35 +0100 contains the logs. I can
> > open the card, but I can not use geldkarte to read it (nor use
> > qbankmanager to do online banking).
> [...]
>
> Ok, in this case I need a different log: Please set the ENV
> variable "LC_LOGLEVEL=info" (or "debug" for that matter) and try
> again "geldkarte loaded".
>
> The console should show much more info which might help solve the problem.

Here is what geldkarte says:

$ LC_LOGLEVEL=debug  geldkarte -v -v -v -v loaded
Connecting to server.
Connected.
Waiting for card...
Found a card.
Opening card.
3:2009/01/22 23-20-51:geldkarte3(1396):clientlcc_cmd.c:  483: Command error -100 (Unknow error code)
3:2009/01/22 23-20-51:geldkarte3(1396):clientlcc_cmd.c:  532: Error response for request "commandCard"
ERROR: Error executing command CardOpen (3).
3:2009/01/22 23-20-51:geldkarte3(1396):client.c:  361: Still 1 cards in use at LC_Client_free!


and here is what chipcardd says during that:

  String size is 167:
  0000: 69 70 63 20 7b 0a 63 68 61 72 20 69 64 3d 22 31 ipc {.char id="1
  0010: 22 0a 63 68 61 72 20 63 6d 64 3d 22 43 6c 69 65 ".char cmd="Clie
  0020: 6e 74 5f 52 65 61 64 79 22 0a 7d 0a 64 61 74 61 nt_Ready".}.data
  0030: 20 7b 0a 63 68 61 72 20 41 70 70 6c 69 63 61 74  {.char Applicat
  0040: 69 6f 6e 3d 22 67 65 6c 64 6b 61 72 74 65 22 0a ion="geldkarte".
  0050: 63 68 61 72 20 47 77 65 6e 56 65 72 73 69 6f 6e char GwenVersion
  0060: 3d 22 33 2e 36 2e 30 73 74 61 62 6c 65 2d 30 22 ="3.6.0stable-0"
  0070: 0a 63 68 61 72 20 43 68 69 70 63 61 72 64 56 65 .char ChipcardVe
  0080: 72 73 69 6f 6e 3d 22 34 2e 32 2e 34 2e 30 73 74 rsion="4.2.4.0st
  0090: 61 62 6c 65 22 0a 63 68 61 72 20 53 79 73 74 65 able".char Syste
  00a0: 6d 3d 22 22 0a 7d 0a                            m="".}.
7:2009/01/22 23-20-51:chipcardd(1338):devicemanager.c: 1927: Command "Client_Ready" not handled by device manager
5:2009/01/22 23-20-51:chipcardd(1338):clr_clientready.c:  105: Client "4978f025" started (geldkarte, Gwen 3.6.0stable-0, ChipCard 4.2.4.0stable)
7:2009/01/22 23-20-51:chipcardd(1338):clr_clientready.c:  137: Response sent.
  String size is 57:
  0000: 69 70 63 20 7b 0a 63 68 61 72 20 69 64 3d 22 32 ipc {.char id="2
  0010: 22 0a 63 68 61 72 20 63 6d 64 3d 22 43 6c 69 65 ".char cmd="Clie
  0020: 6e 74 5f 53 74 61 72 74 57 61 69 74 22 0a 7d 0a nt_StartWait".}.
  0030: 64 61 74 61 20 7b 0a 7d 0a                      data {.}.
7:2009/01/22 23-20-51:chipcardd(1338):devicemanager.c: 1927: Command "Client_StartWait" not handled by device manager
5:2009/01/22 23-20-51:chipcardd(1338):clr_startwait.c:   70: Client 4978f025: StartWait [geldkarte/nobody]
5:2009/01/22 23-20-51:chipcardd(1338):clr_startwait.c:  136: Advertising card "00000003" to client "4978f025" [geldkarte/nobody]
5:2009/01/22 23-20-51:chipcardd(1338):cardmanager.c:  377: Keep time counter restarted
5:2009/01/22 23-20-51:chipcardd(1338):cardmanager.c:  392: No longer allowing reader to shut down
7:2009/01/22 23-20-51:chipcardd(1338):cardmanager.c:  311: Card too long unused
7:2009/01/22 23-20-51:chipcardd(1338):cardmanager.c:  311: Card too long unused
7:2009/01/22 23-20-51:chipcardd(1338):cardmanager.c:  311: Card too long unused
7:2009/01/22 23-20-51:chipcardd(1338):cardmanager.c:  311: Card too long unused
  String size is 79:
  0000: 69 70 63 20 7b 0a 63 68 61 72 20 69 64 3d 22 33 ipc {.char id="3
  0010: 22 0a 63 68 61 72 20 63 6d 64 3d 22 43 6c 69 65 ".char cmd="Clie
  0020: 6e 74 5f 54 61 6b 65 43 61 72 64 22 0a 7d 0a 64 nt_TakeCard".}.d
  0030: 61 74 61 20 7b 0a 63 68 61 72 20 63 61 72 64 69 ata {.char cardi
  0040: 64 3d 22 30 30 30 30 30 30 30 33 22 0a 7d 0a    d="00000003".}.
7:2009/01/22 23-20-51:chipcardd(1338):devicemanager.c: 1927: Command "Client_TakeCard" not handled by device manager
5:2009/01/22 23-20-51:chipcardd(1338):clr_takecard.c:   83: Client 4978f025: TakeCard [geldkarte/nobody]
5:2009/01/22 23-20-51:chipcardd(1338):clr_takecard.c:  166: Enqueued TakeCard request for card "00000003" and client "4978f025"
3:2009/01/22 23-20-51:chipcardd(1338):clr_takecard.c:  185: Working on TakeCard request 4978f029
6:2009/01/22 23-20-51:chipcardd(1338):clr_takecard.c:  204: Step 1 (4978f029)
5:2009/01/22 23-20-51:chipcardd(1338):cm_card.c:  183: Lock request granted
6:2009/01/22 23-20-51:chipcardd(1338):clr_takecard.c:  239: Card lock acquired, now locking slot (4978f029)
3:2009/01/22 23-20-51:chipcardd(1338):clr_takecard.c:  185: Working on TakeCard request 4978f029
6:2009/01/22 23-20-51:chipcardd(1338):clr_takecard.c:  275: Step 2 (4978f029)
5:2009/01/22 23-20-51:chipcardd(1338):lockmanager.c:  167: Lock request granted
  String size is 122:
  0000: 69 70 63 20 7b 0a 63 68 61 72 20 69 64 3d 22 34 ipc {.char id="4
  0010: 22 0a 63 68 61 72 20 63 6d 64 3d 22 43 6c 69 65 ".char cmd="Clie
  0020: 6e 74 5f 43 6f 6d 6d 61 6e 64 43 61 72 64 22 0a nt_CommandCard".
  0030: 7d 0a 64 61 74 61 20 7b 0a 63 68 61 72 20 63 61 }.data {.char ca
  0040: 72 64 69 64 3d 22 30 30 30 30 30 30 30 33 22 0a rdid="00000003".
  0050: 62 69 6e 20 20 64 61 74 61 3d 22 30 30 41 34 30 bin  data="00A40
  0060: 30 30 43 22 0a 63 68 61 72 20 74 61 72 67 65 74 00C".char target
  0070: 3d 22 63 61 72 64 22 0a 7d 0a                   ="card".}.
7:2009/01/22 23-20-51:chipcardd(1338):devicemanager.c: 1927: Command "Client_CommandCard" not handled by device manager
5:2009/01/22 23-20-51:chipcardd(1338):clr_execapdu.c:   88: Client 4978f025: ExecApdu [geldkarte/nobody]
7:2009/01/22 23-20-51:chipcardd(1338):lockmanager.c:  284: slot currently locked by "4978efea" (wanted: 4978efea)
5:2009/01/22 23-20-51:chipcardd(1338):clr_execapdu.c:  231: Enqueued ExecApdu request for card "00000003" and client "4978f025"
7:2009/01/22 23-20-51:chipcardd(1338):clr_execapdu.c:  332: Working on CardCommand request
7:2009/01/22 23-20-51:chipcardd(1338):clr_execapdu.c:  246: Working on ExecApdu request
7:2009/01/22 23-20-51:chipcardd(1338):clr_execapdu.c:  332: Working on CardCommand request
7:2009/01/22 23-20-51:chipcardd(1338):clr_execapdu.c:  246: Working on ExecApdu request
7:2009/01/22 23-20-51:chipcardd(1338):clr_execapdu.c:  332: Working on CardCommand request
7:2009/01/22 23-20-51:chipcardd(1338):clr_execapdu.c:  246: Working on ExecApdu request
7:2009/01/22 23-20-51:chipcardd(1338):clr_execapdu.c:  332: Working on CardCommand request
7:2009/01/22 23-20-51:chipcardd(1338):clr_execapdu.c:  246: Working on ExecApdu request
7:2009/01/22 23-20-51:chipcardd(1338):clr_execapdu.c:  332: Working on CardCommand request
7:2009/01/22 23-20-51:chipcardd(1338):clr_execapdu.c:  246: Working on ExecApdu request
  String size is 188:
  0000: 69 70 63 20 7b 0a 63 68 61 72 20 69 64 3d 22 35 ipc {.char id="5
  0010: 22 0a 63 68 61 72 20 72 65 66 69 64 3d 22 35 22 ".char refid="5"
  0020: 0a 63 68 61 72 20 63 6d 64 3d 22 44 72 69 76 65 .char cmd="Drive
  0030: 72 5f 43 61 72 64 43 6f 6d 6d 61 6e 64 52 65 73 r_CardCommandRes
  0040: 70 6f 6e 73 65 22 0a 7d 0a 64 61 74 61 20 7b 0a ponse".}.data {.
  0050: 69 6e 74 20 20 63 6f 64 65 3d 22 2d 31 30 30 22 int  code="-100"
  0060: 0a 63 68 61 72 20 74 65 78 74 3d 22 55 6e 6b 6e .char text="Unkn
  0070: 6f 77 20 65 72 72 6f 72 20 63 6f 64 65 22 0a 63 ow error code".c
  0080: 68 61 72 20 72 65 61 64 65 72 49 64 3d 22 34 39 har readerId="49
  0090: 37 38 65 66 64 31 22 0a 69 6e 74 20 20 73 6c 6f 78efd1".int  slo
  00a0: 74 6e 75 6d 3d 22 30 22 0a 69 6e 74 20 20 63 61 tnum="0".int  ca
  00b0: 72 64 6e 75 6d 3d 22 31 22 0a 7d 0a             rdnum="1".}.
7:2009/01/22 23-20-51:chipcardd(1338):clr_execapdu.c:  332: Working on CardCommand request
7:2009/01/22 23-20-51:chipcardd(1338):clr_execapdu.c:  246: Working on ExecApdu request
7:2009/01/22 23-20-51:chipcardd(1338):clr_execapdu.c:  272: Sending response to CommandCard
5:2009/01/22 23-20-51:chipcardd(1338):clientmanager.c:  490: Resetting card "00000003"
5:2009/01/22 23-20-51:chipcardd(1338):cm_card.c:  280: Unlocking card from client 4978f025
6:2009/01/22 23-20-51:chipcardd(1338):clientmanager.c:  326: Card "00000003" unlocked from client
5:2009/01/22 23-20-51:chipcardd(1338):lockmanager.c:  222: Removing lock of client "4978f025" on slot
5:2009/01/22 23-20-51:chipcardd(1338):clientmanager.c:  398: Removing client 4978f025 [geldkarte/nobody]
7:2009/01/22 23-21-11:chipcardd(1338):cardmanager.c:  311: Card too long unused
6:2009/01/22 23-21-11:chipcardd(1338):cardmanager.c:  316: Keep time exceeded
7:2009/01/22 23-21-11:chipcardd(1338):cardmanager.c:  318: Allowing reader to shut down

I hope this helps some more.

I’m running on amd64, if that makes a difference...

Thanks,
Joachim

--
Joachim "nomeata" Breitner
  mail: mail@... | ICQ# 74513189 | GPG-Key: 4743206C
  JID: nomeata@... | http://www.joachim-breitner.de/
  Debian Developer: nomeata@...


------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Libchipcard-devel mailing list
Libchipcard-devel@...
https://lists.sourceforge.net/lists/listinfo/libchipcard-devel

[Martin Preuss]

Hi,

On Donnerstag, 22. Januar 2009, Joachim Breitner wrote:
> Am Donnerstag, den 22.01.2009, 18:08 +0100 schrieb Martin Preuss:
[...]

> 23-20-51:chipcardd(1338):clr_execapdu.c:  246: Working on ExecApdu request
> String size is 188:
>   0000: 69 70 63 20 7b 0a 63 68 61 72 20 69 64 3d 22 35 ipc {.char id="5
>   0010: 22 0a 63 68 61 72 20 72 65 66 69 64 3d 22 35 22 ".char refid="5"
>   0020: 0a 63 68 61 72 20 63 6d 64 3d 22 44 72 69 76 65 .char cmd="Drive
>   0030: 72 5f 43 61 72 64 43 6f 6d 6d 61 6e 64 52 65 73 r_CardCommandRes
>   0040: 70 6f 6e 73 65 22 0a 7d 0a 64 61 74 61 20 7b 0a ponse".}.data {.
>   0050: 69 6e 74 20 20 63 6f 64 65 3d 22 2d 31 30 30 22 int  code="-100"
>   0060: 0a 63 68 61 72 20 74 65 78 74 3d 22 55 6e 6b 6e .char text="Unkn
>   0070: 6f 77 20 65 72 72 6f 72 20 63 6f 64 65 22 0a 63 ow error code".c
>   0080: 68 61 72 20 72 65 61 64 65 72 49 64 3d 22 34 39 har readerId="49
>   0090: 37 38 65 66 64 31 22 0a 69 6e 74 20 20 73 6c 6f 78efd1".int  slo
>   00a0: 74 6e 75 6d 3d 22 30 22 0a 69 6e 74 20 20 63 61 tnum="0".int  ca
>   00b0: 72 64 6e 75 6d 3d 22 31 22 0a 7d 0a             rdnum="1".}.

[...]

Hmm, ok, so it is the driver which reports an error... Is there anything in
the driver/reader log (in a folder "/var/log/chipcard" or something similiar
there should be a subfolder "drivers" where you'll find all driver/reader
logs. The one for your reader might contain important information).


Regards
Martin


--
"Things are only impossible until they're not"

Martin Preuss - http://www2.aquamaniac.de/
AqBanking - http://www.aqbanking.de/
LibChipcard - http://www.libchipcard.de/

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Libchipcard-devel mailing list
Libchipcard-devel@...
https://lists.sourceforge.net/lists/listinfo/libchipcard-devel

[Joachim Breitner-2]

Hi,

Am Donnerstag, den 22.01.2009, 23:45 +0100 schrieb Martin Preuss:

> Hi,
>
> On Donnerstag, 22. Januar 2009, Joachim Breitner wrote:
> > Am Donnerstag, den 22.01.2009, 18:08 +0100 schrieb Martin Preuss:
> [...]
> > 23-20-51:chipcardd(1338):clr_execapdu.c:  246: Working on ExecApdu request
> > String size is 188:
> >   0000: 69 70 63 20 7b 0a 63 68 61 72 20 69 64 3d 22 35 ipc {.char id="5
> >   0010: 22 0a 63 68 61 72 20 72 65 66 69 64 3d 22 35 22 ".char refid="5"
> >   0020: 0a 63 68 61 72 20 63 6d 64 3d 22 44 72 69 76 65 .char cmd="Drive
> >   0030: 72 5f 43 61 72 64 43 6f 6d 6d 61 6e 64 52 65 73 r_CardCommandRes
> >   0040: 70 6f 6e 73 65 22 0a 7d 0a 64 61 74 61 20 7b 0a ponse".}.data {.
> >   0050: 69 6e 74 20 20 63 6f 64 65 3d 22 2d 31 30 30 22 int  code="-100"
> >   0060: 0a 63 68 61 72 20 74 65 78 74 3d 22 55 6e 6b 6e .char text="Unkn
> >   0070: 6f 77 20 65 72 72 6f 72 20 63 6f 64 65 22 0a 63 ow error code".c
> >   0080: 68 61 72 20 72 65 61 64 65 72 49 64 3d 22 34 39 har readerId="49
> >   0090: 37 38 65 66 64 31 22 0a 69 6e 74 20 20 73 6c 6f 78efd1".int  slo
> >   00a0: 74 6e 75 6d 3d 22 30 22 0a 69 6e 74 20 20 63 61 tnum="0".int  ca
> >   00b0: 72 64 6e 75 6d 3d 22 31 22 0a 7d 0a             rdnum="1".}.
> [...]
>
> Hmm, ok, so it is the driver which reports an error... Is there anything in
> the driver/reader log (in a folder "/var/log/chipcard" or something similiar
> there should be a subfolder "drivers" where you'll find all driver/reader
> logs. The one for your reader might contain important information).

Sorry for not sending it with that mail (although I did send it with my
first mail with logs – just to my defense :-):

5:2009/01/22 23-20-26:auto1-ccid_gempc_express(1394):d_startreader.c:  223: Init reader auto1-ccid_gempc_express
5:2009/01/22 23-20-27:auto1-ccid_gempc_express(1394):d_startreader.c:  249: ReaderInfo: unit0="icc1"
5:2009/01/22 23-20-27:auto1-ccid_gempc_express(1394):d_startreader.c:  256: Reader up and waiting
5:2009/01/22 23-20-27:auto1-ccid_gempc_express(1394):d_startreader.c:  268: Reader start handled
5:2009/01/22 23-20-27:auto1-ccid_gempc_express(1394):d_work.c:  128: Card inserted, trying to connect it
5:2009/01/22 23-20-27:auto1-ccid_gempc_express(1394):d_work.c:  142: Status changed on slot 0 (00000000->00030000) (cardnum 0)
3:2009/01/22 23-20-27:auto1-ccid_gempc_express(1394):driverifd.c:  451: CCID error on "CCIDTransmit/Control": 612
3:2009/01/22 23-20-27:auto1-ccid_gempc_express(1394):d_cardcommand.c:  153: Error executing APDU (00000064)
5:2009/01/22 23-20-27:auto1-ccid_gempc_express(1394):d_resetcard.c:   81: Resetting card
3:2009/01/22 23-20-51:auto1-ccid_gempc_express(1394):driverifd.c:  451: CCID error on "CCIDTransmit/Control": 612
3:2009/01/22 23-20-51:auto1-ccid_gempc_express(1394):d_cardcommand.c:  153: Error executing APDU (00000064)
5:2009/01/22 23-20-51:auto1-ccid_gempc_express(1394):d_resetcard.c:   81: Resetting card
5:2009/01/22 23-21-41:auto1-ccid_gempc_express(1394):d_stopreader.c:   47: Disconnecting reader
5:2009/01/22 23-21-41:auto1-ccid_gempc_express(1394):d_stopreader.c:   60: Deinit succeeded

I tried to google for these errors, but I didn’t find anything
revealing.

Thanks for having a look,
Joachim
--
Joachim "nomeata" Breitner
  mail: mail@... | ICQ# 74513189 | GPG-Key: 4743206C
  JID: nomeata@... | http://www.joachim-breitner.de/
  Debian Developer: nomeata@...


------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Libchipcard-devel mailing list
Libchipcard-devel@...
https://lists.sourceforge.net/lists/listinfo/libchipcard-devel