Kyocera KE 301 and Linux
A year ago, a Japanese-made phone Kyocera KE 301 CDMA2000 ( Skylink , Belsel / Diallog ) fell 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 with the phone.
It was not possible to immediately find the way through bread crumbs.
The first thing that became clear is that a normally connected modem looks something like this:
typing
I went "ram" paths.
Starting with what already exists, the windows driver consists of 2 files:
MDMSAUSB.inf
SER2PL.sys
From the inf file I learned that the cable is not at all a simple (in other words, straight) cable, but a USB-Serial.
Searching for SER2PL - showed that the converter is based on the Prolific PL2303 chip, which is theoretically 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 turned out a little more complicated, there will be notes about this in the text.
You need a console, utilities
Step one: after executing in the console
: out of the box, pl2303 is not available. You can enable it by performing several manipulations: instead of searching for your kernel version
in the folder , if you updated it there is a file that needs to be renamed or copied to the same folder with the name and the command is executed and only then move on to the next step. Step Three: Identify the USB device with the given vid: pid as a pl2303 device. Important Note: The load module PL2303 is necessary to perform the following command string to pl2303 devices Adds the specified combination vid: pid, the next time you connect the cable system will use the module / driver for pl2303 interaction. In the case of xandros
you have to first complete it
Now the cable can be connected and executed
and watch Highlighted in bold means that the device is successfully recognized and connected. To “fix” the result of the work done (if everything worked): add the line pl2303 to the / etc / modules file - this will enable the module to start automatically at system startup. The rest of the settings for connecting to the Internet has been repeatedly described and is not of interest. By the way, in xandros you should check the file / etc / ppp / peers / cdma, so that / dev / xxx instead of xxx is exactly ttyUSB0 (observe the case of characters) by doing
ps: in xandros, after rebooting, I had to enter sudo su again; echo 2900 0016> / ... this is so far the only thing that could not be done (your suggestions in the comment).
pps: while I decided to write an article - the phone was removed from sale (I don’t already have it on the skylink website, but at Diallog it not only stayed on the website, it also takes part in the promotion).
Thanks FRAGIL3 for the opportunity to publish this article.
Thanks to AER and ENT for the solution described in the third step
For use as a modem, a USB cable and a disk with windows drivers are supplied with the phone.
It was not possible to immediately find the way through bread crumbs.
The first thing that became clear is that a normally connected modem looks something like this:
typing
dmesg | tail
after connecting a USB cable, the console should display a line like this:
No specific article on connecting this particular model was found, therefore, looking at your own and seeing:[ хх.ххх ] usb х-х: pl2303 converter now attached to ttyUSB0
dmesg
[ 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
I went "ram" paths.
Starting with what already exists, the windows driver consists of 2 files:
MDMSAUSB.inf
SER2PL.sys
From the inf file I learned that the cable is not at all a simple (in other words, straight) cable, but a USB-Serial.
Searching for SER2PL - showed that the converter is based on the Prolific PL2303 chip, which is theoretically 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 turned out a little more complicated, there will be notes about this in the text.
You need a console, utilities
lsmod, depmod, lsusb, modprobe,
, the pl2303 kernel module, administrative access via sudo
(or in the case of xandros sudo su
), and some kind of text editor.Step one: after executing in the console
lsusb
before connecting
and after connecting,
We identify the device by 2 parameters vid and pid (short for vendor id and product id), they are highlighted in bold. While the USB cable can be disconnected.
Step two: To support the device with the PL2303 linux system, you must load the pl2303 kernel module;
for this, you must execute the sudo command for this operation.
If there are no error messages, you can check whether the pl2303 kernel module is loaded on your system.
Having executed the command , if among the appeared lines there is a line in the first column and zero in the last column, we move to the next step. Important Note for XandrosBus 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
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
sudo modprobe pl2303
lsmod | grep pl2303
pl2303
: out of the box, pl2303 is not available. You can enable it by performing several manipulations: instead of searching for your kernel version
in the folder , if you updated it there is a file that needs to be renamed or copied to the same folder with the name and the command is executed and only then move on to the next step. Step Three: Identify the USB device with the given vid: pid as a pl2303 device. Important Note: The load module PL2303 is necessary to perform the following command string to pl2303 devices Adds the specified combination vid: pid, the next time you connect the cable system will use the module / driver for pl2303 interaction. In the case of xandros
/lib/modules/2.6.21.4-eeepc/kernel/drivers/usb/serial/
/2.6.21.4-eeepc/
pl2303.ko.huawei
pl2303.ko
sudo depmod
sudo echo 2900 0016 >/sys/bus/usb-serial/drivers/pl2303/new_id
you have to first complete it
sudo su
, and then echo 2900 0016 >/sys/bus/usb-serial/drivers/pl2303/new_id
Now the cable can be connected and executed
lsmod |grep pl2303
, among the lines should be one in which it pl2303
appears in the first column and 1
- in the last. and watch Highlighted in bold means that the device is successfully recognized and connected. To “fix” the result of the work done (if everything worked): add the line pl2303 to the / etc / modules file - this will enable the module to start automatically at system startup. The rest of the settings for connecting to the Internet has been repeatedly described and is not of interest. By the way, in xandros you should check the file / etc / ppp / peers / cdma, so that / dev / xxx instead of xxx is exactly ttyUSB0 (observe the case of characters) by doing
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
sudo pppd call cdma
after all of the above, it will be possible to establish a connection to the Internet without debugging (it works on Belsel / Diallog, it was not possible to check with Skylink) ps: in xandros, after rebooting, I had to enter sudo su again; echo 2900 0016> / ... this is so far the only thing that could not be done (your suggestions in the comment).
pps: while I decided to write an article - the phone was removed from sale (I don’t already have it on the skylink website, but at Diallog it not only stayed on the website, it also takes part in the promotion).
Thanks FRAGIL3 for the opportunity to publish this article.
Thanks to AER and ENT for the solution described in the third step