qbankmanager, libchipcard, omnikey 4040, hbci

[Thomas Koch-11]

crosspost from: http://www.onlinebanking-
forum.de/phpBB2/viewtopic.php?p=57218#57218
 
Ich habe mir den PCMCIA Kartenleser Omnikey 4040 gekauft um das HCBI Verfahren
der Volksbank-Raiffeisenbank zu nutzen. Ich benutze Debian (unstable), habe
jetzt qbankmanager, libchipcard und openct installiert und weiss nicht weiter.
Unter QBankManager versuche ich einen neuen HCBI Benutzer anzulegen, aber die
beiden Plugins die geladen werden fordern mich immer nur auf die Karte
einzulegen, obwohl sie schon drin ist.

------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
Libchipcard-devel mailing list
Libchipcard-devel@...
https://lists.sourceforge.net/lists/listinfo/libchipcard-devel

[Micha Lenk]

Hallo Thomas,

Thomas Koch schrieb:
> Ich habe mir den PCMCIA Kartenleser Omnikey 4040 gekauft um das HCBI Verfahren
> der Volksbank-Raiffeisenbank zu nutzen. Ich benutze Debian (unstable), habe
> jetzt qbankmanager, libchipcard und openct installiert und weiss nicht weiter.
> Unter QBankManager versuche ich einen neuen HCBI Benutzer anzulegen, aber die
> beiden Plugins die geladen werden fordern mich immer nur auf die Karte
> einzulegen, obwohl sie schon drin ist.

Funktioniert deine libchipcard-Installation überhaupt? Was gibt z.B. der
Befehl "chipcard-tool list" aus?

Was für eine Ausgabe kriegst du bei eingesteckter Chipkarte bei dem
Befehl "chipcard-tool atr"?

Schöne Grüße
  Micha

------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
Libchipcard-devel mailing list
Libchipcard-devel@...
https://lists.sourceforge.net/lists/listinfo/libchipcard-devel

[Thomas Koch-11]

Hallo Micha,

danke, dass Du antwortest:


%chipcard-tool list                                                                                                                                
%chipcard-tool atr                                                                                                                                
Waiting for card to be inserted: Started.
Waiting for card to be inserted: 5000 of 30000
Waiting for card to be inserted: 10000 of 30000
Waiting for card to be inserted: 15000 of 30000
Waiting for card to be inserted: 20000 of 30000
Waiting for card to be inserted: 25000 of 30000
Waiting for card to be inserted: 30000 of 30000
Waiting for card to be inserted: Finished.
Error in "GetNextCard": Timeout. (1)

Du kannst mich auch über jabber://thkoch2001@... erreichen.

Informationen von reportbug libchipcard:

-- Package-specific info:
Available chipcard readers (output of "chipcard-tool list"):

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.29-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages libchipcard-tools depends on:
ii  adduser      3.110                       add and remove users and groups
ii  libc6        2.9-8                       GNU C Library: Shared libraries
ii  libchipcard- 4.2.7-4                     configuration files for
libchipcar
ii  libchipcardc 4.2.7-4                     library for accessing smartcards
ii  libdbus-1-3  1.2.12-1                    simple interprocess messaging
syst
ii  libgcc1      1:4.4.0-3                   GCC support library
ii  libgwenhywfa 3.8.0-1                     OS abstraction layer
ii  libhal1      0.5.12~git20090406.46dc48-2 Hardware Abstraction Layer -
share
ii  libpcsclite1 1.5.3-1                     Middleware to access a smart card
ii  libstdc++6   4.4.0-3                     The GNU Standard C++ Library v3
ii  procps       1:3.2.7-11                  /proc file system utilities
ii  zlib1g       1:1.2.3.3.dfsg-13           compression library - runtime

Versions of packages libchipcard-tools recommends:
ii  hal          0.5.12~git20090406.46dc48-2 Hardware Abstraction Layer

Versions of packages libchipcard-tools suggests:
pn  libccid                       <none>     (no description available)
pn  libtowitoko2                  <none>     (no description available)


Beste Grüße, Thomas




Am Thursday 07 May 2009 14:03:17 schrieb Micha Lenk:

> Hallo Thomas,
>
> Thomas Koch schrieb:
> > Ich habe mir den PCMCIA Kartenleser Omnikey 4040 gekauft um das HCBI
> > Verfahren der Volksbank-Raiffeisenbank zu nutzen. Ich benutze Debian
> > (unstable), habe jetzt qbankmanager, libchipcard und openct installiert
> > und weiss nicht weiter. Unter QBankManager versuche ich einen neuen HCBI
> > Benutzer anzulegen, aber die beiden Plugins die geladen werden fordern
> > mich immer nur auf die Karte einzulegen, obwohl sie schon drin ist.
>
> Funktioniert deine libchipcard-Installation überhaupt? Was gibt z.B. der
> Befehl "chipcard-tool list" aus?
>
> Was für eine Ausgabe kriegst du bei eingesteckter Chipkarte bei dem
> Befehl "chipcard-tool atr"?
>
> Schöne Grüße
>   Micha

------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
Libchipcard-devel mailing list
Libchipcard-devel@...
https://lists.sourceforge.net/lists/listinfo/libchipcard-devel

[Sascha Silbe-4]

On Wed, May 06, 2009 at 09:59:44PM +0200, Thomas Koch wrote:

> Ich benutze Debian (unstable), habe jetzt qbankmanager, libchipcard
> und openct installiert und weiss nicht weiter.
Ich tippe mal drauf, daß das genauso wie beim 4000 ist und Du den
binary-Treiber vom Hersteller brauchst. OpenCT nützt Dir nichts, darauf
kann libchipcard nicht zugreifen. Siehe auch entsprechender Thread [1]
auf dieser Liste vor einer Weile.


[1] Message-ID: <20090207163356.GA5215@...>

CU Sascha

--
http://sascha.silbe.org/
http://www.infra-silbe.de/

------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
Libchipcard-devel mailing list
Libchipcard-devel@...
https://lists.sourceforge.net/lists/listinfo/libchipcard-devel

[Thomas Koch-11]

Am Thursday 07 May 2009 15:21:53 schrieb Sascha Silbe:
> Ich tippe mal drauf, daß das genauso wie beim 4000 ist und Du den
> binary-Treiber vom Hersteller brauchst. OpenCT nützt Dir nichts, darauf
> kann libchipcard nicht zugreifen. Siehe auch entsprechender Thread [1]
> auf dieser Liste vor einer Weile.

Ich glaube nicht, dass der fehlende Binärtreiber das Problem ist. Wenn ich das
./install in dem Treiber tar.gz von omnikey aufrufe sagt es mit, es sei für
meinen Kernel kein Treibersource verfügbar. Das entspricht meiner Vermutung,
das die omnikey 4040 vom aktuellen Linux-Kernel unterstützt wird. Eine Suche
nach "omnikey 4040 linux" liefert Hinweise auf ein Linux-Modul.

Außerdem:

%lsmod | grep 4040                                                                                                          
cm4040_cs               7424  1
pcmcia                 27416  1 cm4040_cs
%uname -a                                                                                                                    
Linux jona 2.6.29-1-amd64 #1 SMP Fri Apr 17 10:12:36 UTC 2009 x86_64 GNU/Linux


------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
Libchipcard-devel mailing list
Libchipcard-devel@...
https://lists.sourceforge.net/lists/listinfo/libchipcard-devel

[Micha Lenk]

Hallo Thomas,

Thomas Koch schrieb:

> Am Thursday 07 May 2009 15:21:53 schrieb Sascha Silbe:
>> Ich tippe mal drauf, daß das genauso wie beim 4000 ist und Du den
>> binary-Treiber vom Hersteller brauchst. OpenCT nützt Dir nichts, darauf
>> kann libchipcard nicht zugreifen. Siehe auch entsprechender Thread [1]
>> auf dieser Liste vor einer Weile.
>
> Ich glaube nicht, dass der fehlende Binärtreiber das Problem ist. Wenn ich das
> ./install in dem Treiber tar.gz von omnikey aufrufe sagt es mit, es sei für
> meinen Kernel kein Treibersource verfügbar. Das entspricht meiner Vermutung,
> das die omnikey 4040 vom aktuellen Linux-Kernel unterstützt wird. Eine Suche
> nach "omnikey 4040 linux" liefert Hinweise auf ein Linux-Modul.

Doch, Sascha hat vermutlich recht: Du brauchst noch Bestandteile vom
Hersteller-Treiber. Das Kernel-Modul enthält so weit ich weiß nur den
Teil des Treibers, der im Kernel-Space laufen muss.

Auf der Hersteller-Seite findest Du den Treiber, wenn du das Häkchen bei
"auch abgekündigte Produkte anzeigen" anklickst. So weit ich das hier
aus den XML-Dateien von libchipcard richtig verstehe, benötigst du
allerdings den Treiber für das Modell CardMan 4000, auch wenn du einen
CardMan 4040 hast (zumindest sind beide Modelle in der Datei
omnikey4000_ifd.xml aufgelistet). Die Datei, die du für den CardMan 4000
unter Linux herunter laden kannst, heißt
cm4000_installer_v2_4_0_src.tar.gz und enthält eine Datei libcm4000.so,
die Du auf deinem Rechner am besten in das Verzeichnis /usr/local/lib/
kopierst.

Tut es damit?

Ob es mit dem vom Hersteller angebotenen Teriber für den CardMan 4040
auch klappt, könnte man auch mal noch ausprobieren. Von den angebotenen
Dateien wähle dafür die Datei "CardMan 4040 PC/SC for Linux" und du
kriegst ein Archiv namens ifdok_cm4040_lnx-2.0.0.tar.gz zum Download
angeboten. Darin enthalten ist die Datei ifdok_cm4040_lnx-2.0.0.so, die
Du wieder in das Verzeichnis /usr/local/lib/ kopieren kannst. Jetzt
fehlt allerdings noch die XML-Beschreibungsdatei für libchipcard. Dafür
kannst du mal die angehängte XML-Datei ausprobieren, deren Inhalt ich
aus der o.g. Datei omnikey4000_ifd.xml abgeleitet habe. Diese Datei
kopierst du zum Test in das Verzeichnis /usr/share/chipcard/server/drivers/

Tut es damit?

Ansonsten hoffe ich, dass dir Martin Preuß (CC) noch Tipps geben kann.

Schöne Grüße
  Micha

------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
Libchipcard-devel mailing list
Libchipcard-devel@...
https://lists.sourceforge.net/lists/listinfo/libchipcard-devel

[Micha Lenk]

Hallo nochmal,

Micha Lenk schrieb:

> Ob es mit dem vom Hersteller angebotenen Teriber für den CardMan 4040
> auch klappt, könnte man auch mal noch ausprobieren. Von den angebotenen
> Dateien wähle dafür die Datei "CardMan 4040 PC/SC for Linux" und du
> kriegst ein Archiv namens ifdok_cm4040_lnx-2.0.0.tar.gz zum Download
> angeboten. Darin enthalten ist die Datei ifdok_cm4040_lnx-2.0.0.so, die
> Du wieder in das Verzeichnis /usr/local/lib/ kopieren kannst. Jetzt
> fehlt allerdings noch die XML-Beschreibungsdatei für libchipcard. Dafür
> kannst du mal die angehängte XML-Datei ausprobieren, deren Inhalt ich
> aus der o.g. Datei omnikey4000_ifd.xml abgeleitet habe. Diese Datei
> kopierst du zum Test in das Verzeichnis /usr/share/chipcard/server/drivers/
>
> Tut es damit?

Anbei der versprochene Anhang.

Schöne Grüße
  Micha


<driver name="cm_4040_ifd" type="ifd">
  <short>Driver for Omnikey CardMan 4040</short>
  <manufacturer>
    <name>Omnikey</name>
    <url>http://www.omnikey.at</url>
  </manufacturer>

  <lib>
    <names>
      <name>ifdok_cm4040_lnx-2.0.0.so</name>
    </names>
   
    <locations>
      <loc>/lib</loc>
      <loc>/usr/lib</loc>
      <loc>/usr/local/lib</loc>
      <loc>/usr/lib/pcsc/drivers</loc>
      <loc>/usr/local/lib/pcsc/drivers</loc>
      <loc>/lib64</loc>
      <loc>/usr/lib64</loc>
      <loc>/usr/local/lib64</loc>
      <loc>/usr/lib64/pcsc/drivers</loc>
      <loc>/usr/local/lib64/pcsc/drivers</loc>
    </locations>
   
    <downloads>
      <url>http://www.omnikey.at</url>
      <filename></filename>
    </downloads>
  </lib>

  <readers>
 
    <reader name="omnikey_cm4040_test" busType="Pcmcia"
            vendor="0x0223" product="0x0200" >
      <short>Omnikey CardMan 4040 TEST</short>
      <autoport>
        <mode>pos</mode>
        <busorder>Pcmcia</busorder>
        <sortkey>BusPos</sortKey>
        <offset>0</offset>
      </autoport>
     
      <ports>
        <port value="0">Device0</port>
        <port value="1">Device1</port>
        <port value="2">Device2</port>
        <port value="3">Device3</port>
        <port value="4">Device4</port>
        <port value="5">Device5</port>
        <port value="6">Device6</port>
        <port value="7">Device7</port>
      </ports>

    </reader>

  </readers>


</driver>


------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
Libchipcard-devel mailing list
Libchipcard-devel@...
https://lists.sourceforge.net/lists/listinfo/libchipcard-devel

[Christopher Intemann-2]

unsubscribe

------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
Libchipcard-devel mailing list
Libchipcard-devel@...
https://lists.sourceforge.net/lists/listinfo/libchipcard-devel

[Thomas Koch-11]

Hallo Micha,

Ich habe beide *.so Treiber in /usr/lib und /usr/local/lib kopiert sowie Deine
angehängte xml Datei an den genannten Ort. Wir sind einen Schritt weiter

chipcard-tool list                                                                                            
~
Server: 4a031df3
  Readers:
  - auto1-omnikey_cm4040 (omnikey_cm4040, port 0)

Allerdings ist der output von chipcard-tool atr unverändert und auch
qbankmanager findet immer noch nichts.

Beste Grüße, Thomas






------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
Libchipcard-devel mailing list
Libchipcard-devel@...
https://lists.sourceforge.net/lists/listinfo/libchipcard-devel

[Thomas Koch-11]

Ich vergaß zu schreiben, dass ich rebooten musste, damit ich einen output auf
chipcart-tool list bekam.
Das könnte noch interessant sein:

1017%chipcard-tool -v check                                                                                        
  Readers:
  - auto1-omnikey_cm4040 (omnikey_cm4040, port 0): error
Event log:
19:52:48 Reader listing
19:52:48 Driver error (Loading library)

1018%chipcard-tool -v check                                                                                        
  Readers:
  - auto1-omnikey_cm4040 (omnikey_cm4040, port 0): error
Event log:
19:52:52 Reader listing

1019%chipcard-tool -v check                                                                                        
  Readers:
  - auto1-omnikey_cm4040 (omnikey_cm4040, port 0): error
Event log:
19:52:58 Reader listing

1020%chipcard-tool -v check                                                                                        
ERROR: Timeout.

Im syslog steht:
devicemanager.c: 2091: Error in driver "4a03250d": Loading library (1)

Beste Grüße, Thomas




------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
Libchipcard-devel mailing list
Libchipcard-devel@...
https://lists.sourceforge.net/lists/listinfo/libchipcard-devel

[Martin Preuss]

Moin,

On Donnerstag, 7. Mai 2009, Thomas Koch wrote:
[...]
> 19:52:48 Driver error (Loading library)
[...]

Es scheint hier ein Problem beim Laden des Treibers zu geben.

Du kannst ja mal folgendes probieren:
- "file PFAD_ZU_ifdok_cm4040_lnx-2.0.0.so"
- "ldd PFAD_ZU_ifdok_cm4040_lnx-2.0.0.so"

Kommen da vernuenftige Ausgaben?


Gruss
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/


------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
Libchipcard-devel mailing list
Libchipcard-devel@...
https://lists.sourceforge.net/lists/listinfo/libchipcard-devel

[Joachim Breitner-2]

Hi Thomas,

Am Donnerstag, den 07.05.2009, 20:48 +0200 schrieb Thomas Koch:
> devicemanager.c: 2091: Error in driver "4a03250d": Loading library (1)

ich hatte nen ähnlichen Leser (CM4000), und das war halt unzuverlässig –
da musste ich ab und zu eine wilde Kombination aus Kernelmodul
laden/entladen und libchipcard stoppen/starten machen, bis das lief.
Aber dann tats auch...


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


------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
Libchipcard-devel mailing list
Libchipcard-devel@...
https://lists.sourceforge.net/lists/listinfo/libchipcard-devel

[Micha Lenk]

Hallo Thomas,

Thomas Koch schrieb:
> Ich habe beide *.so Treiber in /usr/lib und /usr/local/lib kopiert sowie Deine
> angehängte xml Datei an den genannten Ort. Wir sind einen Schritt weiter

Hmm, aber welche .so nutzt der Treiber denn jetzt?

> chipcard-tool list                                                                                            
> ~
> Server: 4a031df3
>   Readers:
>   - auto1-omnikey_cm4040 (omnikey_cm4040, port 0)

Das ist doch mal ein Anfang. Ich vermute, dass momentan die libcm4000.so
genutzt wird.

> Allerdings ist der output von chipcard-tool atr unverändert und auch
> qbankmanager findet immer noch nichts.

Ja, Schade. Übrigens: Ohne Erfolg mit "chipcard-tool atr" wird
QBankmanager auch nix finden.

Jetzt heißt es Debuggen: Am besten legst Du dafür eine Datei
/etc/default/libchipcard-tools an mit der folgenden Zeile (alles eine
Zeile):

DAEMON_ARGS="--pidfile $PIDFILE --exit-on-error --logtype console
--loglevel debug"

Wenn Du dann den Daemon neu startest, bekommst Du viele zusätzliche
Log-Meldungen angezeigt, die hoffentlich bei der Fehlersuche helfen.
Welche Optionen der Daemon akzeptiert, erfährst du mit
"/usr/sbin/chipcardd4 --help". Die Optionen "--pidfile $PIDFILE
--exit-on-error" solltest du allerdings beibehalten -- die braucht das
Init-Script.

Das Wochenende jetzt bin ich unterwegs und kann leider nicht weiter
E-Mailen. Aber vermutlich kann beim Debugging eh besser Martin weiter
helfen... ;)

Wie auch immer: Ich hoffe, dass du das noch irgendwie hinbekommst... :)

Schöne Grüße
  Micha

------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
Libchipcard-devel mailing list
Libchipcard-devel@...
https://lists.sourceforge.net/lists/listinfo/libchipcard-devel

[Thomas Koch-11]

> DAEMON_ARGS="--pidfile $PIDFILE --exit-on-error --logtype console
> --loglevel debug"

jona# /etc/init.d/libchipcard-tools start
Starting libchipcard daemon: 5:2009/05/08
08-18-43:chipcardd(6522):chipcardd.c:  738: Chipcardd v4.2.7.0stable started.                                                                                                                    
5:2009/05/08 08-18-43:chipcardd(6522):chipcardd.c:  740: LibHAL supported.                                            
7:2009/05/08 08-18-43:chipcardd(6522):chipcardd.c:  763: Daemon forked, father
exiting                                
7:2009/05/08 08-18-43:chipcardd(6522):stopped                                                                        
3:2009/05/08 08-18-43:(null)(6522):chipcardd.c: 1236: Closing GWEN                                                    
chipcardd4.                                                                                                          
jona# 7:2009/05/08 08-18-43:chipcardd(6523):chipcardd.c:  802: Watcher now
supervising daemon 6524
6:2009/05/08 08-18-43:chipcardd(6524):chipcardd.c:  967: Initializing daemon.                    
6:2009/05/08 08-18-43:chipcardd(6524):chipcardd.c:  442: Trying
"/etc/chipcard/server/chipcardd.conf"
6:2009/05/08 08-18-43:chipcardd(6524):chipcardd.c:  448: Using configuration
file [/etc/chipcard/server/chipcardd.conf]                                                                                                                    
6:2009/05/08 08-18-43:chipcardd(6524):chipcardd.c: 1016: Will now initialize
server.                                  
6:2009/05/08 08-18-43:chipcardd(6524):cs_init.c:  349: Server role: standAlone                                        
6:2009/05/08 08-18-43:chipcardd(6524):cs_init.c:  358: Autoconfiguration
enabled                                      
6:2009/05/08 08-18-43:chipcardd(6524):cs_init.c:  361: Initialising paths                                            
6:2009/05/08 08-18-43:chipcardd(6524):cs_init.c:  368: Initialising IPC
manager                                      
6:2009/05/08 08-18-43:chipcardd(6524):cs_init.c:  110: Listening on
[/var/run/chipcard/chipcard.comm] (local)        
6:2009/05/08 08-18-43:chipcardd(6524):devicemanager.c:   91: Initialising
device manager                              
6:2009/05/08 08-18-43:chipcardd(6524):devicemanager.c:  246: Autoconfiguration
enabled                                
6:2009/05/08 08-18-43:chipcardd(6524):devicemanager.c:  249: Adding HAL
scanner                                      
6:2009/05/08 08-18-43:chipcardd(6524):devicemanager.c:  302: Disabling poll
mode                                      
6:2009/05/08 08-18-43:chipcardd(6524):devicemanager.c:  529: Reloading driver
info files                              
7:2009/05/08 08-18-43:chipcardd(6524):driverinfo.c:  235: Reading driver file
"/usr/share/chipcard/server/drivers/ccid_ifd.xml"                                                                                                            
7:2009/05/08 08-18-43:chipcardd(6524):driverinfo.c:  102: File not found in
search paths                              
7:2009/05/08 08-18-43:chipcardd(6524):driverinfo.c:  235: Reading driver file
"/usr/share/chipcard/server/drivers/scmx32_ifd.xml"                                                                                                          
7:2009/05/08 08-18-43:chipcardd(6524):driverinfo.c:  102: File not found in
search paths                              
7:2009/05/08 08-18-43:chipcardd(6524):driverinfo.c:  235: Reading driver file
"/usr/share/chipcard/server/drivers/omnikey2020_ifd.xml"                                                                                                      
7:2009/05/08 08-18-43:chipcardd(6524):driverinfo.c:  102: File not found in
search paths                              
7:2009/05/08 08-18-43:chipcardd(6524):driverinfo.c:  235: Reading driver file
"/usr/share/chipcard/server/drivers/cyberjack_ctapi.xml"                                                                                                      
7:2009/05/08 08-18-43:chipcardd(6524):driverinfo.c:  102: File not found in
search paths                              
7:2009/05/08 08-18-43:chipcardd(6524):driverinfo.c:  235: Reading driver file
"/usr/share/chipcard/server/drivers/o2micro_ctapi.xml"                                                                                                        
7:2009/05/08 08-18-43:chipcardd(6524):driverinfo.c:  102: File not found in
search paths                              
7:2009/05/08 08-18-43:chipcardd(6524):driverinfo.c:  235: Reading driver file
"/usr/share/chipcard/server/drivers/cherry_ctapi.xml"                                                                                                        
7:2009/05/08 08-18-43:chipcardd(6524):driverinfo.c:  102: File not found in
search paths                              
7:2009/05/08 08-18-43:chipcardd(6524):driverinfo.c:  235: Reading driver file
"/usr/share/chipcard/server/drivers/orga_ctapi.xml"                                                                                                          
7:2009/05/08 08-18-43:chipcardd(6524):driverinfo.c:  102: File not found in
search paths                              
7:2009/05/08 08-18-43:chipcardd(6524):driverinfo.c:  235: Reading driver file
"/usr/share/chipcard/server/drivers/kobil_ctapi.xml"                                                                                                          
7:2009/05/08 08-18-43:chipcardd(6524):driverinfo.c:  102: File not found in
search paths                              
7:2009/05/08 08-18-43:chipcardd(6524):driverinfo.c:  235: Reading driver file
"/usr/share/chipcard/server/drivers/celectronic_ctapi.xml"                                                                                                    
7:2009/05/08 08-18-43:chipcardd(6524):driverinfo.c:  102: File not found in
search paths                              
7:2009/05/08 08-18-43:chipcardd(6524):driverinfo.c:  235: Reading driver file
"/usr/share/chipcard/server/drivers/ccid_serial_ifd.xml"                                                                                                      
7:2009/05/08 08-18-43:chipcardd(6524):driverinfo.c:  102: File not found in
search paths                              
7:2009/05/08 08-18-43:chipcardd(6524):driverinfo.c:  235: Reading driver file
"/usr/share/chipcard/server/drivers/tow_ctapi.xml"                                                                                                            
7:2009/05/08 08-18-43:chipcardd(6524):driverinfo.c:  102: File not found in
search paths                              
7:2009/05/08 08-18-43:chipcardd(6524):driverinfo.c:  235: Reading driver file
"/usr/share/chipcard/server/drivers/omnikey4040_ifd.xml"                                                                                                      
7:2009/05/08 08-18-43:chipcardd(6524):driverinfo.c:  102: File not found in
search paths                              
7:2009/05/08 08-18-43:chipcardd(6524):driverinfo.c:  235: Reading driver file
"/usr/share/chipcard/server/drivers/omnikey4000_ifd.xml"                                                                                                      
7:2009/05/08 08-18-43:chipcardd(6524):driverinfo.c:   81: File found:
/usr/lib/libcm4000.so                          
7:2009/05/08 08-18-43:chipcardd(6524):driverinfo.c:  235: Reading driver file
"/usr/share/chipcard/server/drivers/scm33x_ifd.xml"                                                                                                          
7:2009/05/08 08-18-43:chipcardd(6524):driverinfo.c:  102: File not found in
search paths                              
6:2009/05/08 08-18-43:chipcardd(6524):cardmanager.c:   58: Initialising card
manager                                  
6:2009/05/08 08-18-43:chipcardd(6524):clientmanager.c:   56: Initialising
client manager                              
6:2009/05/08 08-18-43:chipcardd(6524):servicemanager.c:   68: Initialising
service manager                            
6:2009/05/08 08-18-43:chipcardd(6524):cs_tools.c:   99: Hardware scan
triggered                                      
6:2009/05/08 08-18-43:chipcardd(6524):chipcardd.c: 1036: Ready to service
requests.                                  
7:2009/05/08 08-18-43:chipcardd(6524):devmonitor.c:  638: Device UsbRaw/5/3 is
new (046d/c016)                        
7:2009/05/08 08-18-43:chipcardd(6524):devmonitor.c:  638: Device UsbRaw/5/2 is
new (1241/1603)                        
7:2009/05/08 08-18-43:chipcardd(6524):devmonitor.c:  638: Device UsbRaw/5/2 is
new (1241/1603)                        
7:2009/05/08 08-18-43:chipcardd(6524):devmonitor.c:  638: Device pcmcia/0/0 is
new (0223/0200)                        
7:2009/05/08 08-18-43:chipcardd(6524):devmonitor.c:  638: Device UsbRaw/3/1 is
new (1d6b/0002)                        
7:2009/05/08 08-18-43:chipcardd(6524):devmonitor.c:  638: Device UsbRaw/7/1 is
new (1d6b/0001)                        
7:2009/05/08 08-18-43:chipcardd(6524):devmonitor.c:  638: Device UsbRaw/6/1 is
new (1d6b/0001)                        
7:2009/05/08 08-18-43:chipcardd(6524):devmonitor.c:  638: Device UsbRaw/5/2 is
new (1241/1603)                        
7:2009/05/08 08-18-43:chipcardd(6524):devmonitor.c:  638: Device UsbRaw/5/2 is
new (1241/1603)                        
7:2009/05/08 08-18-43:chipcardd(6524):devmonitor.c:  638: Device UsbRaw/5/1 is
new (1d6b/0001)                        
7:2009/05/08 08-18-43:chipcardd(6524):devmonitor.c:  638: Device UsbRaw/1/1 is
new (1d6b/0002)                        
7:2009/05/08 08-18-43:chipcardd(6524):devmonitor.c:  638: Device UsbRaw/4/1 is
new (1d6b/0001)                        
7:2009/05/08 08-18-43:chipcardd(6524):devmonitor.c:  638: Device UsbRaw/2/2 is
new (0483/2016)                        
7:2009/05/08 08-18-43:chipcardd(6524):devmonitor.c:  638: Device UsbRaw/2/1 is
new (1d6b/0001)                        
5:2009/05/08 08-18-43:chipcardd(6524):devicemanager.c: 3399: Changes in
hardware list                                
6:2009/05/08 08-18-43:chipcardd(6524):devicemanager.c:  529: Reloading driver
info files                              
7:2009/05/08 08-18-43:chipcardd(6524):driverinfo.c:  235: Reading driver file
"/usr/share/chipcard/server/drivers/ccid_ifd.xml"                                                                                                            
7:2009/05/08 08-18-43:chipcardd(6524):driverinfo.c:  102: File not found in
search paths                              
7:2009/05/08 08-18-43:chipcardd(6524):driverinfo.c:  235: Reading driver file
"/usr/share/chipcard/server/drivers/scmx32_ifd.xml"                                                                                                          
7:2009/05/08 08-18-43:chipcardd(6524):driverinfo.c:  102: File not found in
search paths                              
7:2009/05/08 08-18-43:chipcardd(6524):driverinfo.c:  235: Reading driver file
"/usr/share/chipcard/server/drivers/omnikey2020_ifd.xml"                                                                                                      
7:2009/05/08 08-18-43:chipcardd(6524):driverinfo.c:  102: File not found in
search paths                              
7:2009/05/08 08-18-43:chipcardd(6524):driverinfo.c:  235: Reading driver file
"/usr/share/chipcard/server/drivers/cyberjack_ctapi.xml"                                                                                                      
7:2009/05/08 08-18-43:chipcardd(6524):driverinfo.c:  102: File not found in
search paths                              
7:2009/05/08 08-18-43:chipcardd(6524):driverinfo.c:  235: Reading driver file
"/usr/share/chipcard/server/drivers/o2micro_ctapi.xml"                                                                                                        
7:2009/05/08 08-18-43:chipcardd(6524):driverinfo.c:  102: File not found in
search paths                              
7:2009/05/08 08-18-43:chipcardd(6524):driverinfo.c:  235: Reading driver file
"/usr/share/chipcard/server/drivers/cherry_ctapi.xml"                                                                                                        
7:2009/05/08 08-18-43:chipcardd(6524):driverinfo.c:  102: File not found in
search paths                              
7:2009/05/08 08-18-43:chipcardd(6524):driverinfo.c:  235: Reading driver file
"/usr/share/chipcard/server/drivers/orga_ctapi.xml"                                                                                                          
7:2009/05/08 08-18-43:chipcardd(6524):driverinfo.c:  102: File not found in
search paths                              
7:2009/05/08 08-18-43:chipcardd(6524):driverinfo.c:  235: Reading driver file
"/usr/share/chipcard/server/drivers/kobil_ctapi.xml"                                                                                                          
7:2009/05/08 08-18-43:chipcardd(6524):driverinfo.c:  102: File not found in
search paths                              
7:2009/05/08 08-18-43:chipcardd(6524):driverinfo.c:  235: Reading driver file
"/usr/share/chipcard/server/drivers/celectronic_ctapi.xml"                                                                                                    
7:2009/05/08 08-18-43:chipcardd(6524):driverinfo.c:  102: File not found in
search paths                              
7:2009/05/08 08-18-43:chipcardd(6524):driverinfo.c:  235: Reading driver file
"/usr/share/chipcard/server/drivers/ccid_serial_ifd.xml"                                                                                                      
7:2009/05/08 08-18-43:chipcardd(6524):driverinfo.c:  102: File not found in
search paths                              
7:2009/05/08 08-18-43:chipcardd(6524):driverinfo.c:  235: Reading driver file
"/usr/share/chipcard/server/drivers/tow_ctapi.xml"                                                                                                            
7:2009/05/08 08-18-43:chipcardd(6524):driverinfo.c:  102: File not found in
search paths                              
7:2009/05/08 08-18-43:chipcardd(6524):driverinfo.c:  235: Reading driver file
"/usr/share/chipcard/server/drivers/omnikey4040_ifd.xml"                                                                                                      
7:2009/05/08 08-18-43:chipcardd(6524):driverinfo.c:  102: File not found in
search paths                              
7:2009/05/08 08-18-43:chipcardd(6524):driverinfo.c:  235: Reading driver file
"/usr/share/chipcard/server/drivers/omnikey4000_ifd.xml"                                                                                                      
7:2009/05/08 08-18-43:chipcardd(6524):driverinfo.c:   81: File found:
/usr/lib/libcm4000.so                          
7:2009/05/08 08-18-43:chipcardd(6524):driverinfo.c:  235: Reading driver file
"/usr/share/chipcard/server/drivers/scm33x_ifd.xml"                                                                                                          
7:2009/05/08 08-18-43:chipcardd(6524):driverinfo.c:  102: File not found in
search paths                              
7:2009/05/08 08-18-43:chipcardd(6524):devicemanager.c: 3150: Device
UsbRaw/046d/c016 up                              
6:2009/05/08 08-18-43:chipcardd(6524):devicemanager.c: 3309: Device
UsbRaw/046d/c016 is not a known reader            
7:2009/05/08 08-18-43:chipcardd(6524):devicemanager.c: 3150: Device
UsbRaw/1241/1603 up                              
6:2009/05/08 08-18-43:chipcardd(6524):devicemanager.c: 3309: Device
UsbRaw/1241/1603 is not a known reader            
7:2009/05/08 08-18-43:chipcardd(6524):devicemanager.c: 3150: Device
UsbRaw/1241/1603 up                              
6:2009/05/08 08-18-43:chipcardd(6524):devicemanager.c: 3309: Device
UsbRaw/1241/1603 is not a known reader            
7:2009/05/08 08-18-43:chipcardd(6524):devicemanager.c: 3150: Device
pcmcia/0223/0200 up                              
5:2009/05/08 08-18-43:chipcardd(6524):devicemanager.c: 3240: AUTOCONFIG:
Created new reader "auto1-omnikey_cm4040" (pcmcia/0223/0200)                                                                                                      
5:2009/05/08 08-18-43:chipcardd(6524):devicemanager.c: 3254: Automatically
assigned port 0 to reader "auto1-omnikey_cm4040"                                                                                                                
7:2009/05/08 08-18-43:chipcardd(6524):clr_notification.c:  162: Mask for
reader:add is 00000400                      
6:2009/05/08 08-18-43:chipcardd(6524):clr_notification.c:  190: Sending
notification reader:add to all clients        
7:2009/05/08 08-18-43:chipcardd(6524):devicemanager.c: 3150: Device
UsbRaw/1d6b/0002 up                              
6:2009/05/08 08-18-43:chipcardd(6524):devicemanager.c: 3309: Device
UsbRaw/1d6b/0002 is not a known reader            
7:2009/05/08 08-18-43:chipcardd(6524):devicemanager.c: 3150: Device
UsbRaw/1d6b/0001 up                              
6:2009/05/08 08-18-43:chipcardd(6524):devicemanager.c: 3309: Device
UsbRaw/1d6b/0001 is not a known reader            
7:2009/05/08 08-18-43:chipcardd(6524):devicemanager.c: 3150: Device
UsbRaw/1d6b/0001 up                              
6:2009/05/08 08-18-43:chipcardd(6524):devicemanager.c: 3309: Device
UsbRaw/1d6b/0001 is not a known reader            
7:2009/05/08 08-18-43:chipcardd(6524):devicemanager.c: 3150: Device
UsbRaw/1241/1603 up                              
6:2009/05/08 08-18-43:chipcardd(6524):devicemanager.c: 3309: Device
UsbRaw/1241/1603 is not a known reader            
7:2009/05/08 08-18-43:chipcardd(6524):devicemanager.c: 3150: Device
UsbRaw/1241/1603 up                              
6:2009/05/08 08-18-43:chipcardd(6524):devicemanager.c: 3309: Device
UsbRaw/1241/1603 is not a known reader            
7:2009/05/08 08-18-43:chipcardd(6524):devicemanager.c: 3150: Device
UsbRaw/1d6b/0001 up                              
6:2009/05/08 08-18-43:chipcardd(6524):devicemanager.c: 3309: Device
UsbRaw/1d6b/0001 is not a known reader            
7:2009/05/08 08-18-43:chipcardd(6524):devicemanager.c: 3150: Device
UsbRaw/1d6b/0002 up                              
6:2009/05/08 08-18-43:chipcardd(6524):devicemanager.c: 3309: Device
UsbRaw/1d6b/0002 is not a known reader            
7:2009/05/08 08-18-43:chipcardd(6524):devicemanager.c: 3150: Device
UsbRaw/1d6b/0001 up                              
6:2009/05/08 08-18-43:chipcardd(6524):devicemanager.c: 3309: Device
UsbRaw/1d6b/0001 is not a known reader            
7:2009/05/08 08-18-43:chipcardd(6524):devicemanager.c: 3150: Device
UsbRaw/0483/2016 up                              
6:2009/05/08 08-18-43:chipcardd(6524):devicemanager.c: 3309: Device
UsbRaw/0483/2016 is not a known reader            
7:2009/05/08 08-18-43:chipcardd(6524):devicemanager.c: 3150: Device
UsbRaw/1d6b/0001 up                              
6:2009/05/08 08-18-43:chipcardd(6524):devicemanager.c: 3309: Device
UsbRaw/1d6b/0001 is not a known reader            

jona# chipcard-tool atr

  String size is 171:
  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 63 68 69 70 63 61 72 64 2d 74 6f ion="chipcard-to
  0050: 6f 6c 22 0a 63 68 61 72 20 47 77 65 6e 56 65 72 ol".char GwenVer
  0060: 73 69 6f 6e 3d 22 33 2e 38 2e 30 73 74 61 62 6c sion="3.8.0stabl
  0070: 65 2d 30 22 0a 63 68 61 72 20 43 68 69 70 63 61 e-0".char Chipca
  0080: 72 64 56 65 72 73 69 6f 6e 3d 22 34 2e 32 2e 37 rdVersion="4.2.7
  0090: 2e 30 73 74 61 62 6c 65 22 0a 63 68 61 72 20 53 .0stable".char S
  00a0: 79 73 74 65 6d 3d 22 22 0a 7d 0a                ystem="".}.    
7:2009/05/08 08-20-21:chipcardd(6524):devicemanager.c: 1937: Command
"Client_Ready" not handled by device manager
5:2009/05/08 08-20-21:chipcardd(6524):clr_clientready.c:  105: Client
"4a03cec5" started (chipcard-tool, Gwen 3.8.0stable-0, ChipCard 4.2.7.0stable)                                                                                        
7:2009/05/08 08-20-21:chipcardd(6524):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/05/08 08-20-21:chipcardd(6524):devicemanager.c: 1937: Command
"Client_StartWait" not handled by device manager
5:2009/05/08 08-20-21:chipcardd(6524):clr_startwait.c:   70: Client 4a03cec5:
StartWait [chipcard-tool/nobody]        
3:2009/05/08 08-20-21:chipcardd(6524):devicemanager.c: 1756: Incrementing
active reader count auto1-omnikey_cm4040 (4a03cec4) [1]                                                                                                          
3:2009/05/08 08-20-21:chipcardd(6524):dm_driver.c:  359: Incrementing active
readers count of driver cm_4000_ifd [4a03cec4](0->1)                                                                                                          
6:2009/05/08 08-20-21:chipcardd(6524):dm_driver.c:  362: Some readers active,
driver leaving idle mode                

Waiting for card to be inserted: Started.
Waiting for card to be inserted: 5000 of 30000
6:2009/05/08 08-20-31:chipcardd(6524):devicemanager.c:  823: Starting driver
"cm_4000_ifd"
Waiting for card to be inserted: 10000 of 30000                                          
6:2009/05/08 08-20-31:chipcardd(6524):devicemanager.c:  916: Starting driver
process for driver "cm_4000_ifd" (/usr/lib/chipcard/server/drivers/ifd)                                                                                        
6:2009/05/08 08-20-31:chipcardd(6524):devicemanager.c:  917: Arguments are: "
-l /usr/lib/libcm4000.so --logtype file --logfile
/var/log/chipcard/drivers/cm_4000_ifd/@reader@.log -t local -a
/var/run/chipcard/chipcard.comm -p 0 -i 4a03cec4"                                                                                                                  
6:2009/05/08 08-20-31:chipcardd(6524):devicemanager.c:  936: Process started                                          
7:2009/05/08 08-20-31:chipcardd(6524):clr_notification.c:  162: Mask for
driver:start is 00000001                    
6:2009/05/08 08-20-31:chipcardd(6524):clr_notification.c:  190: Sending
notification driver:start to all clients      
7:2009/05/08 08-20-31:chipcardd(6524):clr_notification.c:  207: Client
"4a03cec5" is not interested in driver:start [00000000]                                                                                                              
7:2009/05/08 08-20-31:chipcardd(6524):devicemanager.c: 1209: still waiting for
driver start                          
7:2009/05/08 08-20-31:chipcardd(6524):devicemanager.c: 1209: still waiting for
driver start                          
7:2009/05/08 08-20-31:chipcardd(6524):devicemanager.c: 1209: still waiting for
driver start                          
7:2009/05/08 08-20-31:chipcardd(6524):devicemanager.c: 1209: still waiting for
driver start                          
7:2009/05/08 08-20-31:chipcardd(6524):devicemanager.c: 1209: still waiting for
driver start                          
7:2009/05/08 08-20-31:chipcardd(6524):devicemanager.c: 1209: still waiting for
driver start                          
7:2009/05/08 08-20-31:chipcardd(6524):devicemanager.c: 1209: still waiting for
driver start                          
7:2009/05/08 08-20-31:chipcardd(6524):devicemanager.c: 1209: still waiting for
driver start                          
7:2009/05/08 08-20-31:chipcardd(6524):devicemanager.c: 1209: still waiting for
driver start                          
  String size is 120:                                                                                                
  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 61 30 33 63 65 63 34 22 0a 69 6e 74 20 ="4a03cec4".int                                              
  0050: 20 63 6f 64 65 3d 22 31 22 0a 63 68 61 72 20 74  code="1".char t
  0060: 65 78 74 3d 22 4c 6f 61 64 69 6e 67 20 6c 69 62 ext="Loading lib
  0070: 72 61 72 79 22 0a 7d 0a                         rary".}.
7:2009/05/08 08-20-31:chipcardd(6524):devicemanager.c: 1972: Driver 4a03cec8:
DriverReady
3:2009/05/08 08-20-31:chipcardd(6524):devicemanager.c: 2091: Error in driver
"4a03cec4": Loading library (1)
6:2009/05/08 08-20-31:chipcardd(6524):devicemanager.c:  478: Abandoning driver
4a03cec4
7:2009/05/08 08-20-31:chipcardd(6524):clr_notification.c:  162: Mask for
driver:error is 00000008
6:2009/05/08 08-20-31:chipcardd(6524):clr_notification.c:  190: Sending
notification driver:error to all clients
7:2009/05/08 08-20-31:chipcardd(6524):clr_notification.c:  207: Client
"4a03cec5" is not interested in driver:error [00000000]
6:2009/05/08 08-20-31:chipcardd(6524):devicemanager.c:  511: Abandoning reader
3:2009/05/08 08-20-31:chipcardd(6524):devicemanager.c:  452: Decrementing
active reader count auto1-omnikey_cm4040 (4a03cec4) [2->6]
3:2009/05/08 08-20-31:chipcardd(6524):dm_driver.c:  377: Decrementing active
readers count of driver cm_4000_ifd [4a03cec4](1->0)
6:2009/05/08 08-20-31:chipcardd(6524):dm_driver.c:  381: No readers active,
driver entering idle mode
7:2009/05/08 08-20-31:chipcardd(6524):clr_notification.c:  162: Mask for
reader:error is 00000200
6:2009/05/08 08-20-31:chipcardd(6524):clr_notification.c:  190: Sending
notification reader:error to all clients
7:2009/05/08 08-20-31:chipcardd(6524):clr_notification.c:  207: Client
"4a03cec5" is not interested in reader:error [00000000]
Waiting for card to be inserted: 15000 of 30000
Waiting for card to be inserted: 20000 of 30000
Waiting for card to be inserted: 25000 of 30000
Waiting for card to be inserted: 30000 of 30000
5:2009/05/08 08-20-51:chipcardd(6524):devicemanager.c: 1033: Reenabling driver
"cm_4000_ifd"
Waiting for card to be inserted: Finished.
Error in "GetNextCard": Timeout. (1)
5:2009/05/08 08-20-56:chipcardd(6524):clientmanager.c:  398: Removing client
4a03cec5 [chipcard-tool/nobody]
jona# 7:2009/05/08 08-21-06:chipcardd(6524):clr_notification.c:  162: Mask for
reader:down is 00000100
6:2009/05/08 08-21-06:chipcardd(6524):clr_notification.c:  190: Sending
notification reader:down to all clients


------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
Libchipcard-devel mailing list
Libchipcard-devel@...
https://lists.sourceforge.net/lists/listinfo/libchipcard-devel

[Martin Preuss]

Moin,

interessant waere vielleicht das driver.log fuer den TReiber (ich weiss nicht,
wo das unter DEbian ist, aber vermutlich sowas wie
/var/log/chipcard/drivers/NAME/driver.log oder so).

Und was ist nun das Ergebnis der 2 Kommandos, die ich in meiner vorigen Mail
beschrieben hatte?


Gruss
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/


------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
Libchipcard-devel mailing list
Libchipcard-devel@...
https://lists.sourceforge.net/lists/listinfo/libchipcard-devel

[Thomas Koch-11]

Am Thursday 07 May 2009 21:06:38 schrieb Martin Preuss:
> Du kannst ja mal folgendes probieren:
> - "file PFAD_ZU_ifdok_cm4040_lnx-2.0.0.so"
> - "ldd PFAD_ZU_ifdok_cm4040_lnx-2.0.0.so"
>
> Kommen da vernuenftige Ausgaben?
Was ist schon vernünftig?

1018%file ifdok_cm4040_lnx_x64-2.0.0.so                                                                
/usr/local/lib
ifdok_cm4040_lnx_x64-2.0.0.so: ELF 64-bit LSB shared object, x86-64, version 1
(SYSV), dynamically linked, not stripped
1019%ldd ifdok_cm4040_lnx_x64-2.0.0.so                                                                
/usr/local/lib
        linux-vdso.so.1 =>  (0x00007fff9f3ff000)
        libpthread.so.0 => /lib/libpthread.so.0 (0x00007f7096ed6000)
        libc.so.6 => /lib/libc.so.6 (0x00007f7096b83000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f7097221000)
1020%file libcm4000.so                                                                                
/usr/local/lib
libcm4000.so: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV),
dynamically linked, not stripped
1021%ldd libcm4000.so                                                                                  
/usr/local/lib
        statically linked




------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
Libchipcard-devel mailing list
Libchipcard-devel@...
https://lists.sourceforge.net/lists/listinfo/libchipcard-devel

[Thomas Koch-11]

Am Friday 08 May 2009 09:25:13 schrieb Martin Preuss:
> interessant waere vielleicht das driver.log fuer den TReiber (ich weiss
> nicht, wo das unter DEbian ist, aber vermutlich sowas wie
> /var/log/chipcard/drivers/NAME/driver.log oder so).

cat /var/log/daemon.log | grep chipcard > chipcard.log





------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
Libchipcard-devel mailing list
Libchipcard-devel@...
https://lists.sourceforge.net/lists/listinfo/libchipcard-devel

[Martin Preuss]

Moin,

On Freitag, 8. Mai 2009, Thomas Koch wrote:

> Am Thursday 07 May 2009 21:06:38 schrieb Martin Preuss:
> > Du kannst ja mal folgendes probieren:
> > - "file PFAD_ZU_ifdok_cm4040_lnx-2.0.0.so"
> > - "ldd PFAD_ZU_ifdok_cm4040_lnx-2.0.0.so"
> >
> > Kommen da vernuenftige Ausgaben?
>
> Was ist schon vernünftig?
>
> 1018%file ifdok_cm4040_lnx_x64-2.0.0.so
> /usr/local/lib
> ifdok_cm4040_lnx_x64-2.0.0.so: ELF 64-bit LSB shared object, x86-64,
> version 1 (SYSV), dynamically linked, not stripped

[...]
> libcm4000.so: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV),
> dynamically linked, not stripped
[...]

Na, das hier ist nicht vernuenftig: Die eine Bibliothek ist eine 64-Bit-Lib,
die andere eine 32-Bit-lib. Beides kann man nicht mischen. Was fuer ein System
hast Du denn genau? Faehrst Du ein 64-Bit-System?

Soweit ich weiss hilft hier die Ausgabe von "uname -a" wohl nicht weiter, weil
man sich bei irgendeiner Debian-Version offensichtlich dazu entschieden hat,
einem 32-Bit-System einen 64-Bit-Kernel zu verpassen...


Gruss
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/


------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
Libchipcard-devel mailing list
Libchipcard-devel@...
https://lists.sourceforge.net/lists/listinfo/libchipcard-devel

[Martin Preuss]

Moin,

On Freitag, 8. Mai 2009, Thomas Koch wrote:
> Am Friday 08 May 2009 09:25:13 schrieb Martin Preuss:
> > interessant waere vielleicht das driver.log fuer den TReiber (ich weiss
> > nicht, wo das unter DEbian ist, aber vermutlich sowas wie
> > /var/log/chipcard/drivers/NAME/driver.log oder so).
>
> cat /var/log/daemon.log | grep chipcard > chipcard.log
[...]

Nein, das meine ich nicht, das ist das Log vom Daemon. Was ich meine sind die
Treiber- und Leser-Logs, und die speichert Libchipcard in eigenen Dateien (ich
weiss bei Debian aber halt nicht wo, da kann Micha sicher mehr zu sagen).

Im Log des Treibers koennte man vielleicht sehen, warum die Datei nicht
geladen werden konnte.


Gruss
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/


------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
Libchipcard-devel mailing list
Libchipcard-devel@...
https://lists.sourceforge.net/lists/listinfo/libchipcard-devel

[Micha Lenk]

Hallo Thomas,

On Fri, May 08, 2009 at 11:08:11AM +0200, Martin Preuss wrote:

> On Freitag, 8. Mai 2009, Thomas Koch wrote:
> > Am Friday 08 May 2009 09:25:13 schrieb Martin Preuss:
> > > interessant waere vielleicht das driver.log fuer den TReiber (ich weiss
> > > nicht, wo das unter DEbian ist, aber vermutlich sowas wie
> > > /var/log/chipcard/drivers/NAME/driver.log oder so).
> >
> > cat /var/log/daemon.log | grep chipcard > chipcard.log
> [...]
>
> Nein, das meine ich nicht, das ist das Log vom Daemon. Was ich meine sind die
> Treiber- und Leser-Logs, und die speichert Libchipcard in eigenen Dateien (ich
> weiss bei Debian aber halt nicht wo, da kann Micha sicher mehr zu sagen).

Ja, sehr viel genauer weiß ich's leider auch nicht: Irgendwo in einer
der Dateien unterhalb von /var/log/chipcard/drivers/ sind die relevanten
Logs. Welches Verzeichnis und welche Datei das genau ist, hängt leider
auch vom geladenen Treiber ab.

Schöne Grüße
  Micha

------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
Libchipcard-devel mailing list
Libchipcard-devel@...
https://lists.sourceforge.net/lists/listinfo/libchipcard-devel