Am Sun, 12 Apr 2009 18:50:22 +0200
schrieb Martin Preuss <aquaman...@gmx.de>:
Hallo Martin,
vielen Dank für Deine Antwort.
> [...]
> > Fehlermeldung:
> > Apr 12 16:12:00 pinguinstall chipcardd[3051]: chipcardd.c: 551:
> > Triggering hardware scan Apr 12 16:12:00 pinguinstall
> > chipcardd[3051]: devicemanager.c: 3421: Error scanning
> [...]
>
> Und wie geht es danach weiter?
Wenn ich das Lesegerät wieder in den USB Port einstecke:
Apr 12 18:59:41 pinguinstall kernel: [12168.648334] usb 5-3.3: new full speed
USB device using ehci_hcd and address 12
Apr 12 18:59:41 pinguinstall kernel: [12168.743318] usb 5-3.3: configuration #1
chosen from 1 choice
Apr 12 18:59:41 pinguinstall kernel: [12168.743739] usb 5-3.3: New USB device
found, idVendor=0c4b, idProduct=0300
Apr 12 18:59:41 pinguinstall kernel: [12168.743748] usb 5-3.3: New USB device
strings: Mfr=1, Product=2, SerialNumber=3
Apr 12 18:59:41 pinguinstall kernel: [12168.743753] usb 5-3.3: Product:
cyberJack pinpad(a)
Apr 12 18:59:41 pinguinstall kernel: [12168.743757] usb 5-3.3: Manufacturer:
Reiner-SCT
Apr 12 18:59:41 pinguinstall kernel: [12168.743760] usb 5-3.3: SerialNumber:
xxxxxxxxxx
Apr 12 18:59:41 pinguinstall chipcardd[3051]: chipcardd.c: 551: Triggering
hardware scan
Apr 12 18:59:51 pinguinstall chipcardd[3051]: devicemanager.c: 3421: Error
scanning
Mehr kommt da nicht
>
> Welche Version von Libchipcard ist ueberhaupt installiert? Das sind
> schon mal so Informationen, ohne die man nur raten kann, was da los
> ist...
Hoffe das ist die Info
apt-cache policy libchipcardc2
libchipcardc2:
Installiert: 4.2.7-1
Kandidat: 4.2.7-1
Versions-Tabelle:
*** 4.2.7-1 0
500 ftp://ftp.fu-berlin.de unstable/main Packages
100 /var/lib/dpkg/status
Alles andere was ich noch mit libchipcard finden kann ist auch 4.2.7-1
chipcardd4 --loglevel info --logtype console
5:2009/04/12 18-57-25:chipcardd(5141):chipcardd.c: 738: Chipcardd
v4.2.7.0stable started.
5:2009/04/12 18-57-25:chipcardd(5141):chipcardd.c: 740: LibHAL supported.
3:2009/04/12 18-57-25:chipcardd(5142):chipcardd.c: 683: Old PID file existed,
removed. (Unclean shutdown?)
6:2009/04/12 18-57-25:chipcardd(5143):chipcardd.c: 967: Initializing daemon.
6:2009/04/12 18-57-25:chipcardd(5143):chipcardd.c: 442: Trying
"/etc/chipcard/server/chipcardd.conf"
6:2009/04/12 18-57-25:chipcardd(5143):chipcardd.c: 448: Using configuration
file [/etc/chipcard/server/chipcardd.conf]
6:2009/04/12 18-57-25:chipcardd(5143):chipcardd.c: 1016: Will now initialize
server.
6:2009/04/12 18-57-25:chipcardd(5143):cs_init.c: 349: Server role: standAlone
6:2009/04/12 18-57-25:chipcardd(5143):cs_init.c: 358: Autoconfiguration enabled
6:2009/04/12 18-57-25:chipcardd(5143):cs_init.c: 361: Initialising paths
6:2009/04/12 18-57-25:chipcardd(5143):cs_init.c: 368: Initialising IPC manager
6:2009/04/12 18-57-25:chipcardd(5143):cs_init.c: 110: Listening on
[/var/run/chipcard/chipcard.comm] (local)
6:2009/04/12 18-57-25:chipcardd(5143):devicemanager.c: 91: Initialising
device manager
6:2009/04/12 18-57-25:chipcardd(5143):devicemanager.c: 246: Autoconfiguration
enabled
6:2009/04/12 18-57-25:chipcardd(5143):devicemanager.c: 249: Adding HAL scanner
6:2009/04/12 18-57-25:chipcardd(5143):devicemanager.c: 292: Disabling poll mode
6:2009/04/12 18-57-25:chipcardd(5143):devicemanager.c: 519: Reloading driver
info files
3:2009/04/12 18-57-25:(null)(5141):chipcardd.c: 1236: Closing GWEN
pinguinstall:/home/dirk# 6:2009/04/12 18-57-25:chipcardd(5143):cardmanager.c:
58: Initialising card manager
6:2009/04/12 18-57-25:chipcardd(5143):clientmanager.c: 56: Initialising
client manager
6:2009/04/12 18-57-25:chipcardd(5143):servicemanager.c: 68: Initialising
service manager
6:2009/04/12 18-57-25:chipcardd(5143):cs_tools.c: 99: Hardware scan triggered
6:2009/04/12 18-57-25:chipcardd(5143):chipcardd.c: 1036: Ready to service
requests.
5:2009/04/12 18-57-25:chipcardd(5143):devicemanager.c: 3389: Changes in
hardware list
6:2009/04/12 18-57-25:chipcardd(5143):devicemanager.c: 519: Reloading driver
info files
6:2009/04/12 18-57-26:chipcardd(5143):devicemanager.c: 3299: Device
UsbRaw/05e3/0608 is not a known reader
6:2009/04/12 18-57-26:chipcardd(5143):devicemanager.c: 3299: Device
UsbRaw/05e3/0608 is not a known reader
6:2009/04/12 18-57-26:chipcardd(5143):devicemanager.c: 3299: Device
UsbRaw/05e3/0604 is not a known reader
6:2009/04/12 18-57-26:chipcardd(5143):devicemanager.c: 3299: Device
UsbRaw/046d/c001 is not a known reader
6:2009/04/12 18-57-26:chipcardd(5143):devicemanager.c: 3299: Device
UsbRaw/05e3/000b is not a known reader
6:2009/04/12 18-57-26:chipcardd(5143):devicemanager.c: 3299: Device
UsbRaw/1d6b/0002 is not a known reader
6:2009/04/12 18-57-26:chipcardd(5143):devicemanager.c: 3299: Device
UsbRaw/1d6b/0001 is not a known reader
6:2009/04/12 18-57-26:chipcardd(5143):devicemanager.c: 3299: Device
UsbRaw/1d6b/0001 is not a known reader
6:2009/04/12 18-57-26:chipcardd(5143):devicemanager.c: 3299: Device
UsbRaw/1d6b/0001 is not a known reader
6:2009/04/12 18-57-26:chipcardd(5143):devicemanager.c: 3299: Device
UsbRaw/0603/00f2 is not a known reader
6:2009/04/12 18-57-26:chipcardd(5143):devicemanager.c: 3299: Device
UsbRaw/0603/00f2 is not a known reader
6:2009/04/12 18-57-26:chipcardd(5143):devicemanager.c: 3299: Device
UsbRaw/1d6b/0001 is not a known reader
Bis vorgestern beim Update auf kde4.2 ging immer alles sehr gut und
ohne ein einziges Problem.
Danke
Dirk
------------------------------------------------------------------------------
This SF.net email is sponsored by:
High Quality Requirements in a Collaborative Environment.
Download a free trial of Rational Requirements Composer Now!
http://p.sf.net/sfu/www-ibm-com
_______________________________________________
Aqbanking-devel mailing list
Aqbanking-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aqbanking-devel
