Kyocera KE 301 and Linux

A year ago, a Kyocera KE 301 Japanese-made CDMA2000 phone ( Skylink , Belsel / Diallog ) came into my hands. The phone works fine as a CDMA-1x modem, but neither Ubuntu nor Xandros (eee pc 1000) out of the box understand it.

For use as a modem, a USB cable and a disk with windows drivers are supplied to the phone.
It was not immediately possible to find a way for bread crumbs.
The first thing that has become clear is that a normally connected modem looks like this:
typing dmesg | tail dmesg | tail after connecting the USB cable in the console should appear a line like this:
[ . ] usb - : pl2303 converter now attached to ttyUSB0
No specific article on the connection of this particular model was found, therefore, looking at your dmesg and seeing:
[ 738.220000] usb 1-2: new full speed USB device using uhci_hcd and address 2
[ 738.380000] usb 1-2: configuration #1 chosen from 1 choice
went "lamb" trails.

Starting with what is already there, the windows driver consists of 2 files:
MDMSAUSB.inf
SER2PL.sys
I learned from the inf-file that the cable is not at all a simple (in other words straight) cable, but a USB-Serial.
Searching SER2PL showed that the converter is based on the Prolific PL2303 chip, which theoretically is supported by Debian, which is already a big plus.

The solution below is equally true for xandros (the version installed on eeepc 1000 was used) and ubuntu 9.04 (installed on the desktop), in the case of xandros it was a little more complicated, this will be marked in the text.
')
lsmod, depmod, lsusb, modprobe, console, lsmod, depmod, lsusb, modprobe, utilities lsmod, depmod, lsusb, modprobe, kernel module, sudo administrative access (or in the case of xandros sudo su ), and some text editor.

Step One: Run the lsusb console before connecting
Bus 001 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 005 Device 001: ID 0000:0000
Bus 004 Device 001: ID 0000:0000
and after connecting
Bus 001 Device 001: ID 0000:0000
Bus 001 Device 004: ID 2900 : 0016
Bus 002 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 005 Device 001: ID 0000:0000
Bus 004 Device 001: ID 0000:0000
We identify the device by 2 parameters vid and pid (abbreviated from vendor id and product id), they are highlighted in bold. While the USB cable can be disconnected.

Step two: To support the device’s PL2303 linux system, you need to load the pl2303 kernel module
for this you need to execute the command
sudo modprobe pl2303 sudo required for this operation
If there were no error messages, you can check whether the kernel module pl2303 is loaded on your system.
lsmod | grep pl2303 command lsmod | grep pl2303 lsmod | grep pl2303 , if among the lines that appear there is a line pl2303 in the first column and zero in the last column, we move to the next step.
Important note for Xandros : Out of the box, the pl2303 module is not available. You can enable it by performing several manipulations:
in the /lib/modules/2.6.21.4-eeepc/kernel/drivers/usb/serial/ folder
instead of /2.6.21.4-eeepc/ should look for your version of the kernel if you updated it
There is a file pl2303.ko.huawei , which you need to rename or copy into the same folder with the name pl2303.ko and execute the sudo depmod and only after that move on to the next step.

Step Three: Defining a USB device with a given vid: pid as a pl2303 device.
Important note: you need to load the PL2303 module before executing the following command
String
sudo echo 2900 0016 >/sys/bus/usb-serial/drivers/pl2303/new_id
The specified vid: pid combination is added to the pl2303 devices, the next time the cable is connected, the system will use the pl2303 module / driver for interaction.
In the case of xandros, you must first run sudo su , and then echo 2900 0016 >/sys/bus/usb-serial/drivers/pl2303/new_id

Now the cable can be connected and run lsmod |grep pl2303 , among the lines should be one in which pl2303 will be in the first column and 1 in the last.
and watch dmesg |tail
[10442.180000] usb 1-2: new full speed USB device using uhci_hcd and address 5
[10442.340000] usb 1-2: configuration #1 chosen from 1 choice
[10442.350000] pl2303 1-2:1.0: pl2303 converter detected
[10442.350000] usb 1-2: pl2303 converter now attached to ttyUSB0 dmesg |tail
[10442.180000] usb 1-2: new full speed USB device using uhci_hcd and address 5
[10442.340000] usb 1-2: configuration #1 chosen from 1 choice
[10442.350000] pl2303 1-2:1.0: pl2303 converter detected
[10442.350000] usb 1-2: pl2303 converter now attached to ttyUSB0
Bold indicates that the device has been successfully recognized and connected.

To “fix” the result of what was done (if everything worked): add the line pl2303 to the / etc / modules file - this will enable the autoloading of the module when the system starts.

The rest of the setting for connecting to the Internet has been repeatedly described and is of no interest.
By the way, in xandros you should check the / etc / ppp / peers / cdma file, so that / dev / xxx instead of xxx is ttyUSB0 (observe the case of characters) by running sudo pppd call cdma after all of the above, you can connect to the Internet without tuning ( works on Belsel / Diallog, it was not possible to check with Skylink)

ps: in xandros, after rebooting, I had to re-enter sudo su; echo 2900 0016> / ... this is the only thing that could not be done (your suggestions in the comments).
pps: while I decided to write an article - the phone was removed from the sale (on the site skylink there is no longer, while at Diallog he not only stayed on the site, but also participates in the promotion).

Thank you FRAGIL3 for the possibility of publishing this article.
Thanks to AER and LOR for the solution described in the third step.