Thanks. You're right, the product ID changed. I updated the Info.plist
and was able to get the token to be detected, however it still has
trouble powering the token up. Here's the pcscd -df output:

00000000 debuglog.c:230:DebugLogSetLevel() debug level=debug
00000351 pcscdaemon.c:512:main() pcsc-lite 1.5.4 daemon ready.
00108773 tokenparser.l:175:LTPBundleFindValueWithKey() Value/Key not
defined for: ifdVendorID in
/usr/lib/pcsc/drivers//ifd-ccid.bundle/Contents/Info.plist
00000194 tokenparser.l:175:LTPBundleFindValueWithKey() Value/Key not
defined for: ifdVendorID in
/usr/lib/pcsc/drivers//egate.bundle/Contents/Info.plist
00148182 hotplug_libusb.c:403:HPEstablishUSBNotifications() Driver
ifd-ccid.bundle does not support IFD_GENERATE_HOTPLUG. Using active
polling instead.
00000017 hotplug_libusb.c:412:HPEstablishUSBNotifications() Polling
forced every 1 second(s)
04001698 hotplug_libusb.c:477:HPAddHotPluggable() Adding USB device: 005:012
00000031 readerfactory.c:1024:RFInitializeReader() Attempting startup
of OCS ID-One Cosmo Card 00 00 using
/usr/lib/pcsc/drivers//ifd-ccid.bundle/Contents/Linux/libccid.so
00000120 readerfactory.c:877:RFBindFunctions() Loading IFD Handler 3.0
00000034 ifdhandler.c:1417:init_driver() Driver version: 1.3.10
00000249 ifdhandler.c:1430:init_driver() LogLevel: 0x0003
00000208 ifdhandler.c:1450:init_driver() DriverOptions: 0x0000
00000008 ifdhandler.c:81:IFDHCreateChannelByName() lun: 0, device:
usb:1a74/6356:libusb:005:012
00000541 ccid_usb.c:238:OpenUSBByName() Manufacturer: Ludovic Rousseau
([email protected])
00000214 ccid_usb.c:248:OpenUSBByName() ProductString: Generic CCID driver
00000205 ccid_usb.c:254:OpenUSBByName() Copyright: This driver is
protected by terms of the GNU Lesser General Public License version
2.1, or (at your option) any later version.
00062133 ccid_usb.c:410:OpenUSBByName() Found Vendor/Product:
1A74/6356 (OCS ID-One Cosmo Card)
00000012 ccid_usb.c:412:OpenUSBByName() Using USB bus/device: 005/012
00004233 ccid_usb.c:784:get_data_rates() IFD does not support
GET_DATA_RATES request: Success
00032970 commands.c:152:CmdPowerOn() bResponseType: 0x73
00010995 ifdhandler.c:334:IFDHGetCapabilities() tag: 0xFB0,
usb:1a74/6356:libusb:005:012 (lun: 0)
00000012 readerfactory.c:249:RFAddReader() Using the pcscd polling thread
00012024 ifdhandler.c:1002:IFDHPowerICC() action: PowerUp,
usb:1a74/6356:libusb:005:012 (lun: 0)
00014992 commands.c:152:CmdPowerOn() bResponseType: 0x72
00000030 ifdhandler.c:1055:IFDHPowerICC() PowerUp failed
00000020 eventhandler.c:292:EHStatusHandlerThread() Error powering up
card: -2146435050 0x80100016
00000016 ifdhandler.c:334:IFDHGetCapabilities() tag: 0xFAE,
usb:1a74/6356:libusb:005:012 (lun: 0)
00000011 ifdhandler.c:377:IFDHGetCapabilities() Reader supports 1 slot(s)

And here's the output of parse > output.txt

Parsing USB bus/device: 005/012
 idVendor:  0x1A74  iManufacturer: OCS ID-One Cosmo Card
 idProduct: 0x6356  iProduct: USB Smart Chip Device
  Found a possibly CCID/ICCD device (bInterfaceClass = 0xFF). Use -p


On Wed, Nov 18, 2009 at 10:39 AM, Michael StJohns <[email protected]> wrote:
> The USB vendor/product id probably changed between versions.  There's an 
> Info.plist file associated with the CCID driver that you can update.  Use 
> "lsusb" with the token inserted and you should be able to capture the changed 
> id.
>
>>http://pcsclite.alioth.debian.org/ccid.html#CCID_compliant
>
> Dr Rousseau will add the details to the next released version if you send him 
> the output from the above.
>
> Enjoy - Mike
>
>
>
> At 09:05 PM 11/17/2009, Sihan Goi wrote:
>>Hi,
>>
>>I have an Oberthur Cosmo 5.4 in USB token form. The reader name is "On
>>Chip Security USB Reader 0". This token works with pcscd, and it
>>detects the insertion/unplugging properly. Oberthur recently fixed a
>>few card issues with a soft mask, and changed the reader name to "On
>>Chip Security 3 USB Reader 0" as well as changed the protocol. As far
>>as I can tell these are the only changes.
>>
>>This new token does not work with pcscd. I tried running "pcscd -df"
>>but upon token insertion, nothing happens at all. Is there an easy way
>>to support the new token?
>>
>>Thanks.
>>
>>--
>>- Goi Sihan
>>[email protected]
>>_______________________________________________
>>Muscle mailing list
>>[email protected]
>>http://lists.drizzle.com/mailman/listinfo/muscle
>
>
> _______________________________________________
> Muscle mailing list
> [email protected]
> http://lists.drizzle.com/mailman/listinfo/muscle
>



-- 
- Goi Sihan
[email protected]

_______________________________________________
Muscle mailing list
[email protected]
http://lists.drizzle.com/mailman/listinfo/muscle

Reply via email to