Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email email@example.com
Re: [Muscle] Problems with Omnikey CardMan 2020 USB
From: Maurizio Napolitano (maurizio.napolitanogmail.com)
Date: Fri Apr 01 2005 - 02:38:58 CST
On Feb 16, 2005 5:59 PM, Maurizio Napolitano
> I solved the problem!
> My hotplug configuration create the device on /dev/cm0 but the driver
> for pcscd want it on /dev/usb/cm0.
The right way (for the udev users that need a only one cardman omnikey2020)
- echo 'BUS="usb", KERNEL="cm[0-9]*", NAME="usb/cm0"' >
- /etc/init.d/udev restart
- create a configuration file for udev with this istruction
BUS="usb", KERNEL="cm[0-9]*", NAME="usb/cm0"
eg. (for the file cardman2020.rules)
echo 'BUS="usb", KERNEL="cm[0-9]*", NAME="usb/cm0"' > cardman2020.rules
- place this file on the directory where your udev deamon create the
cp cardman2020.rules /etc/udev/rules.d
- restart the udev deamon
The problem is the binary library distributed by Omnikey.
This library want have always the device on /dev/usb/cm0.
All the default configuration for udev that i knonw create this device
(where X is a number from 0 to ... X).
On my machine i use another input usb device and, udev, create for me
/dev/cm1 or /dev/cm0 (depends on the sequence that i use to plug my
input device on my usb hub).
I solved with this stupid hack, so udev create for me always the device
/dev/usb/cm0 without check if the smartcard reader is on the first or
on the second position (aka is /dev/cm0 or /dev/cm1).
I hope that this message can be useful for other cardman2020 users.
Sorry for my bad english.
Muscle mailing list