CodeMeter requires a working USB hotplugging infrastructure for the detection of a CmDongle. Thus make sure that the hotplug is working properly.
If hotplugging seems not to work on a new Linux distribution, please check if the new "udev" mechanism is used. If "udev" is used, the problem can be fixed by copying the file /usr/share/CodeMeter/52-codemeter.rules into the directory /etc/udev/rules.d/.
For the communication between CodeMeterLin and the CmDongle, CodeMeterLin requires a Linux kernel (Kernel 2.4.x or Kernel 2.6.x) with support for USB mass storage, human interface (HID) and scsi-generic devices. If you use a self compiled Linux Kernel, please check if you have activated usb-storage and sg-device support (as modules).
General Kernel configuration display settings including USB mass storage or HID (Human Interface Device):
CmDongle via USB as MSD (CmStick, CmStick/M, CmCard):
CONFIG_SYSFS
CONFIG_USB_SUPPORT
CONFIG_USB_*_HCD* (respective Host Controller)
CONFIG_USB_STORAGE
CONFIG_BLK_DEV_SD
CONFIG_BLK_DEV_SG (for passthrough communication)
CONFIG_*_FS (for file I/O, the respective file system)
CmStick via USB as HID:
CONFIG_SYSFS
CONFIG_USB_SUPPORT
CONFIG_USB_*_HCD* (respective Host Controller)
CONFIG_HID
CONFIG_HIDRAW
CONFIG_USB_HID
CmCard via internal card reader (e.g. SDHCI):
CONFIG_SYSFS
CONFIG_MMC
CONFIG_MMC_BLOCK
CONFIG_MMC_* (for the respective card reader)
CONFIG_BLK_DEV_SG (for passthrough communication)
CONFIG_*_FS (for file I/O, the respective file system)
CmCard via ATA:
CONFIG_SYSFS
CONFIG_BLK_DEV_SD
CONFIG_ATA + respective ATA Host adapter/controller
CONFIG_BLK_DEV_SG (for passthrough communication)
CONFIG_*_FS (for file I/O, the respective file system)
If your Linux Kernel is configured properly, use the command:
codemeter-info -L
to get a list of all CmDongles connected to your system. If this is not the case, you have probably a general problem with your Linux Kernel or a Kernel module could not be loaded correctly.