Hi. This is a common problem with pl2303 chip based cables. Have You tried
Your cable under windows? Did it work? I think it si the first step to do -
I suppose You got a windows driver along with the cable. In linux the
problem is that most cables aren't recognized by pl2303 kernel module
because of different (not known by pl2303 module) vendor and product IDs.
The solution is to add the vendorID and productID to the module, recompile
the kernel module and it is... only the half of success. I had the same
problem with my Ours Technologies Inc DKU-5 cable for 3100 (also with pl2303
chip). I've added support to the pl2303 module and now linux recognizes the
cable and creates /dev/ttyUSB0 device - this is the port which should be set
in gammu config. But there is another problem - gammu cannot communicate
with the phone. It isonly the gammu problem - I think that gammu doesn't
support the cable because there was not support for it in pl2303 and once
the support is added gammu programmers should add the support for the cable.
So I think it's only a matter of time (and reporting the new supported cable
to gammu programmers, once You make sure Your cable is supported by pl2303
kernel module).



Things to do:

First check the vendorID and productID of the cable - plug in the cable to
the USB port and in console type:

lsusb -v

this should list all usb ports and vendor/product IDs of devices atatched to
them.

Get the kernel source and hack the pl2303.h and pl2303.c files - inpl2303.h
add definitions of the IDs (in the same way the rest of IDs are listed). for
example:

#define AMC_CA42_VENDOR_ID 0x****

#define AMC_CA42_PRODUCT_ID 0x****

In pl2303.c add a line like this:

 { USB_DEVICE(AMC_CA42_VENDOR_ID, AMC_CA42_PRODUCT_ID) },

(You will find the place where to add it - just add it among the similar
entries.

Compile the module, install it, atthtch the cable to the USB port and write
in console:

dmesg | tail

If in the output is information about the device created for the cable (eg.
/dev/ttyUSB0) it's ok.

Now You can check if gammu communicates with the phone (but I suppose it
won't).

Now submit the change of the pl2303 module yuo have made and wait till it is
officially added to the kernel. Then you should inform gammu programmers
that new cable is supported by the kernel and tell them to add support for
the cable in gammu.

KERNEL=="ttyUSB[0-4]*", SYSFS{idVendor}=="6547", SYSFS{idProduct}=="0232", NAME="mobile", MODE="666", GROUP="uucp"

apt-get install fuse

modprobe fuse

$ mkdir ArkMicroUSB2Serial
$ cd ArkMicroUSB2Serial
$ wget http://avr.auctionant.de/ark3116_linux_driver/releases/ark3116-0.4.1.tgz
$ tar -xzf ark3116-0.4.1.tgz
$ cd ark3116
$ make

# to test it
$ sudo modprobe usbserial; sudo insmod ark3116

# at this point you should see a ttyUSB0 device
# ls -l /dev/ttyUSB*

# to install it permenantly do
$ sudo make install

# install the kernel headers if you still don't have them - this for some reason does not include the usb-serial.h we need
$ sudo apt-get install linux-kernel-headers-`uname -r`

# download the source for the kernel - this is big - about 60 MB
$ sudo apt-get source linux-headers-`uname -r`

# change the owner (to yourself) of the files cause they are owned by some other dude (UID 2500)
$ sudo chown -R $UID:$UID linux-source-2.6.15-2.6.15/

# now move this to the correct place
$ sudo mv linux-source-2.6.15-2.6.15 /usr/src/

# and link it to symbolic name 'linux' which is what most apps expect
$ cd /usr/src
$ ln -s linux-source-2.6.15-2.6.15 linux