Download Crossplatform UI
Ubuntu, download here
Fedora, download here
Opensuse, download here
The UI software setup package under Linux (Ubuntu, openSUSE, Fedora,…) system contains the driver of USB data card and offers different driver source codes according to different Linux kernel versions. They are put under the setup path: /usr/local/bin/ztemtApp/zteusbserial, and saved in different sub-folders.
The setup package will automatically compile the corresponding driver
version and load the driver (insmod ztemt.ko) during the installation.
Therefore, you need to install gcc compiler and kernel development
package (kernel-devel) in advance.
Ubuntu9.04 system is an exception because the USB driver module
has already existed in this version of system kernel. The setup
package will omit the step of compiling the driver after confirming that
the system version is Ubuntu9.04; instead, it would modify the system
pilot configuration (menu.lst) in order to support different ZTE USB
data cards.
You need insert USB data card when installing UI software under
Ubuntu9.04 system, otherwise, you are unable to install the driver
parameters of this type of data card. Please pay attention to it.
Premise condition of installing UI software
Since the installation of Linux system package is rather complicated,
you need have certain experiences of using Linux system to complete
the installation. It’s recommended to select the corresponding package
upon the system installation, which is the simplest method.
In order to offer those users who are not familiar with Linux system
installation a reference and quick installation guide, and provide the
troubleshooting methods to the technical staff, we hereby write this
document.
(The installation methods may vary among different types of Linux
system. Here we take openSUSE for example)
gcc compiler and kernel-devel should be installed in the system
because the driver needs to be compiled during the installation. If gcc
compiler and kernel-devel are not yet installed, install them from their
respective Linux system installation CD.
Install gcc
Recommended method: when installing Linux system, select gcc
relevant package at “Development Tools”.
Or install it again from CD after the system is installed.
Open SUSE: it’s recommened to install with yast setup package
manager. Select software, search the setup package from CD and then
select Install.
Take gcc package installed under openSUSE11.1 system for example.
The relevant packages installed are listed as below (for reference
only):
gcc-4.3-34.168
gcc-c++-4.3-34.168
gcc-info-4.3-34.168
gcc43-4.3.3_20081022-9.5
gcc43-info-4.3.3_20081022-9.5
gcc43-gij-4.3.3_20081022-9.2
gcc43-c++-4.3.3_20081022-9.5
libgcc43-4.3.3_20081022-9.5
gcc-gij-4.3-34.168
Ubuntu: Require PC to connect the network, and then use apt-get
install command to install.
e.g.: sudo apt-get install gcc
Feora: use yum command to install. e.g.: yum install gcc.
Install kernel-devel
Select the corresponding package when installing Linux system. The
detailed name and version might vary according to different Linux
system versions.
Or add the corresponding setup package from CD after the system is
installed.
OpenSUSE: it’s recommended to install with yast setup package
manager.
Take openSUSE11.1 system for example. The kernel packages
installed are listed as below (for reference only):
kernel-source-2.6.27.7-9.1
linux-kernel-headers-2.6.27-2.28
kernel-pae-base-2.6.27.7-9.1
kernel-pae-2.6.27.7-9.1
kernel-syms-2.6.27.7-9.1
kernel-pae-extra-2.6.27.7-9.1
Fedora: it’s recommended to use yum manager to install.
e.g., yum install kernel-devel (Require PC to connect the network)
Ubuntu: Require PC to connect the network, and then use apt-get
install to install.
e.g., sudo apt-get install kernel-devel
Get started to installation
After the installation of gcc compiler and kernel-devel, you could start
installing cross-platform UI software.
1. Download the corresponding Linux version package
Download the corresponding Linux version package on our website
www.mtsindia.in/mblaze.
Generally, there are three kinds of packages for different Linux OS.
CrossPlatformUI-Vx.x.x-i386-ubuntu.deb
This is DEB format setup package used for Ubuntu system
CrossPlatformUI-Vx.x.x-i586.opensuse.rpm
openSUSE system setup package
CrossPlatformUI-Vx.x.x-i586.fedora.rpm
Fedora system setup package
2. Double-click the package to install
Insert the USB data card, and double click the setup package.
3. Adopt command line to install
Open the terminal program and key in the command:
sudo rpm –ivh /media/cdrom0/
CrossPlatformUI-Vx.x.x-i586.opensuse.rpm #openSUSE
sudo rpm –ivh /media/cdrom0/
CrossPlatformUI-Vx.x.x-i586.fedora.rpm #Fedora
sudo dpkg –i /media/cdrom0/ CrossPlatformUI-Vx.x.x-i586.ubuntu.deb
#Ubuntu
Because it requires super user authority during the installation, it might
ask you to input super user password.
4. Adopt command line to uninstall
Open the terminal program and key in the command:
sudo rpm –e CrossPlatformUI ( #Fedora/openSUSE case
sensitive)
sudo dpkg –r CrossPlatformUI ( #Ubuntu )
sudo dpkg –P CrossPlatformUI ( #Ubuntu )
5. Common problems during the installation
Authority problem
This problem occurs as the common users are installing. The
installation can’t be completed because there is no enough authority.
Please use sudo command to install (shown as above)
Old version not removed yet
The old version must be removed before installation, otherwise the
installation will fail.
Uninstall method:
sudo rpm –e CrossPlatformUI ( #Fedora/openSUSE case
sensitive)
or: sudo dpkg –r CrossPlatformUI ( #Ubuntu )
or: sudo dpkg –P CrossPlatformUI ( #Ubuntu )
Conflict among setup packages
If there is any conflict between the setup package and other software
(generally, this won’t happen), you could perform compulsory
installation (not recommended).
Method:
sudo dpkg –i --force-all CrossPlatformUI-Vx.x.x-i586.ubuntu.deb
This method is just currently applicable for the problem occurred under
Ubuntu9.04 system.
Due to the driver problem, we will provide another
zteusbserial-V1.0.deb setup package, which will have conflict with
CrossPlatformUI software. Use the command above to solve the
problem. The consequent versions will integrate the driver into UI Sotware
Get Started to Run UI
After all above installations, you could start running UI software.
Firstly insert the data card into USB port, wait for the driver to
recognize USB data card, and then run UI program.
Two methods to run UI software:
1. Click the shortcut menu: Menu ->Connection->MBlaze （for
customers）
2. Execute ztemtapp command through terminal program （for
technical, market support staff）
a) After running UI in this way, the following information will
display on the terminal, which will be used to track the problem.
b) If the shared library required by UI are not completely installed,
you will see the system prompt of missing libaudio2 library after
executing ztemtapp command.
See the figure below:
Common Problems and Troubleshooting
Has UI software been installed or not?
If UI software has been installed, the program would be installed at the
following path: /usr/local/bin/ztemtApp. Execute the program through
ztemtapp command.
You could use the command line to inquire the name of the package
where the files are saved. The name will be used when you want to
remove UI software. For example, if you want to inquire which package
ztemtapp file is installed, you could run:
rpm –qf /bin/ztemtapp or dpkg –S ztemtapp
If it’s already been installed, the following information will return:
“CrossPlatformUI-V2.x.x-*”, and the package name is
CrossPlatformUI.
Can USB
device be used or not
If the driver is installed successfully, you could inquire that ztemt.ko
module has been loaded into the system through lsmod | grep ztemt
command. At this point, you will find the device files such as ttyUSB0,
ttyUSB1…under the directory: /dev/ after inserting the data card (1~ 2
seconds). ttyUSB0 corresponds to modem port.
If the installation fails, you will not find /dev/ttyUSB0. You are prompted
with “Can’t find device” when running UI.
Why is there no response when clicking Application Internet
MBlaze?
Solution: Input “ztemtapp” at the command line
(Applications->accessories->terminal); If the system prompts you with
“can’t find command”, the installation isn’t successful, you need install
the software again.
If the system prompts you with “missing libaudio2” library, you need
install the corresponding library file.
What shall we do if there is a prompt with “Can’t access the
terminal or can’t find the device” after clicking MBlaze?
Solution: use the command “ls /dev/ttyU*” to check whether or not
/dev/ttyUSB0, /dev/ttyUSB1, /dev/ttyUSB2 and /dev/ttyUSB3 exist. If
they don’t exist, the device might be not be properly driven. You could
manually compile and load the driver which is placed at
/usr/local/bin/ztemtApp/, or seek for technical support.
What shall we do if there is a prompt with “insmod ztemt.ko
failure” during the installation?
There are two reasons:
1. This usually happens as you remove UI and install again. You need
restart to load normally because the driver module is not well
compatible with the system.
2. It also happens under Ubuntu9.04 version system because the USB
driver has already existed in the system and the ztemt.ko driver file
provided by UI can’t be loaded again. However, we have built-in the
automatic judgment and handling over Ubuntu9.04 in the setup
package; if such an error occurs to your system unexpectedly, use the
following method to manually pass two parameters to the kernel, and
make the kernel support ZTE USB data card.
Method: under the system startup interface, move the highlight to
ubuntu9.04, press “e” key to edit, select the item you want to start, add
space after the word splash, input “usbserial.vendor=0x19d2
usbserial.product=0xfff1”, press “Enter” to confirm and press “b” to
start.
(The pvid value might vary among different data cards. Use the
command “lsusb” to view.)
Manually compile the driver
1. In some special cases, the setup package can’t automatically
compile the driver, so you need change the configurations yourself and
manually compile the driver.
Method: enter the directory: /usr/local/bin/ztemtApp/zteusbserial, and
find the corresponding kernel version of current system.
For example: if the operating system is 2.6.27 kernel, please use the
driver in 2.6.27 folder; if the operating system is the version below
2.6.27, use the driver in below2.6.27 folder. Enter the directory,
execute make command. If the compiling is successful, ztemt.ko driver
will be generated in current directory.
Execute insmod ztemt.ko to load and copy the ztemt.ko under
zteusbserial directory.
2. If it prompts with “Can’t find kernel source code”, please change the
path of KERNELDIR in Makefile.
(e.g.: KERNELDIR=/usr/src/kernels/2.6.27.4-79.fc10.i686)，and
compile it again.
3. If you didn’t find the similar path in the system, follow the method
above to install the kernel development package.
Configuration file path
When Linux setup program is being executed, UI configuration file, PC
SMS inbox and phonebook will be saved in user’s directory.
~/.ztemtapp/ZTEEVDO/
Can’t exit due to exception of UI software
In some rare cases, UI process is locked and can’t exit, it will occupy
USB device file and driver; it causes the failure of un-installation, and
UI program prompts with “Still can’t find the device” after the device is
plug out and plug in again.
In this case you could use killall -9 App to end UI process and let the
system release all used resources.
Plug in/out the device to normally run UI software.
What shall we do if the uninstall fails and the software package can’t be
installed again?
The common users use “sudo dpkg -i --forece-all setup package name”
to perform compulsory installation, and this will cover some remaining
information and has no influence upon the system. Root users don’t
need sudo. Please note that there are two “-” before force and there is
no space between “force” and “-all”.
Unable to run the UI after software installation and the following
prompt appears (Fedora12 system)
Loading XCommm failed due to selunux settings. See the solutions
below:
Enter the directory of /etc/selinux, edit the config file and replace
“SELLINUX=enforcing” with “SELLINUX=disabled”. Refer to the
following command
Restart your PC after changing the config file, and then you could run
the UI normally. Or you could check if SELINUX is disabled or not in
the config file prior to the installation of Fedora12 system; if not, Please
change it.
