* Thomas Viehmann <[EMAIL PROTECTED]>:
> >>- information what reader you are using (if applicable plus lsusb
> >>  output),
> > Reiner-SCT cyberjack USB (the new one, 0300). Worked just fine with
> > the version in stable and the drivers from Reiner-SCT.
> And the output of lsusb is?

Bus 001 Device 002: ID 0c4b:0300 Reiner SCT Kartensysteme GmbH
cyberJack pinpad(a)

> >>- a copy of your config files,
> > Default, according to libchipcard.de, 'chipcardd2' should take care
> > of the configuration.
> Could you please post a copy of /etc/chipcard2-server/chipcardd2.conf?

enabled="1"
server {
        type="local"
        addr="/tmp/.chipcard2/chipcard2.sock
}

> >>- the exact command lines you are using,
> > Well, since chipcardd2 --dport doesn't list anything, I never got to
> > the point with an actual configuration command.
> Can you please tell me the exact command line you are using?
> "--dport" is not an option of chipcardd2 as shipped by Debian.

I think you misunderstood me.
I just want to run a documented command (at least in --help, since
there are no mangpages whatsoever):
'/usr/sbin/chipcardd2 addreader --dtype list' 
This is the command chipcardd2 tells me to use to list the available
drivers. And since I want to know if the driver for the cyberpad is
available, I run that command. Without succed ("ERROR: No drivers
found")

> >>- the relevant log excerpts.
> > I posted everything I have.
> Chipcardd2 will, in the default configuration shipped by Debian,
> generate output via the syslog facility, usually found in daemon.log.

No, since there is nothing to tell.
I can run chipcardd2 alone, it looks like it detects the reader, but it
doesn't respond (the LED is not on, as with the old chipcardd when it
found the reader). But that's most likely not your fault/problem, since
I have yet to figure out how to use the new tools (I'm used to the well
documented hbcicard, which isn't available anymore).

-- 
Fridtjof Busse


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to