Z-Com XG-762N User Manual
1
The User Guide of XG-762N USB Linux Driver
2
1. Introduction
Because more and more people install the Linux operating system in the desktop and
notebook, we provide the Linux solution of our XG-762N802.11a+b+g Wireless LAN
Card. XG-762N provides 802.11 a+b+g wireless solution for USB interface. In our
XG-762N solution, we can run in the Infrastructure (Managed), Ad-hoc or AP (Master)
modes. One can easily change these modes. This document is intended to describe how to
setup and how to use XG-762Nunder the Linux operating system.
1.1 Requirements:
1. Kernel 2.4.20+ . The driver had successfullybuilt in Redhat9, Fedora Core2,3 ,and
Debian 3.1. You can easily build it without any problem
2. To build XG-762Nyou will need: Configured kernel source code for the kernel you
are running. Ideally, Configured means that you have at least run 'make config',
'make menuconfig', or 'make xconfig'. If your platform is not SMP system, please
don't config SMP supported, because when module loaded, this will make
unresolved symbol.
3. Make sure your kernel usb 2.0 support is running
- Use lsmod to check "ehci-hcd" module is loaded.
- If host is not support usb 2.0, XG-762N will run under pure-b mode.
3
2. Building the device driver
tar zxv
f XG-
762N
LnxDrv
_xxxx.tar.gz
# if the kernel is 2.6.x, turn on this
In this section, we will describe how to build our XG-762NLinux driver under the Linux
operating system.
2.1 Package Extraction
# where xxxx is the version number, such as 2_0_0_0
The first thing one should do is to uncompress this package by tar. After untaringthis
package, you can see the source files. One should change directory into this directory for
proceeding the next step.
2.2 Build and install the driver
The package contains drivers for XG-762N. If you doesn¡¯t have specified request, both of
them will be installed.
Under the extracted directory, there is a Makefile in it. Because our driver can support for
kernel 2.4 and kernel 2.6, there are two sets of rule in the Makefile. One has to modify
the Makefile according to the path of ¡°ker nel source tree¡± and the version of the kernel
in your system. In the Makefile, you may see the following statements,
#KERN_26=y
#KERNEL_SOURCE=/usr/src/linux-2.6.7
# if the kernel is 2.4.x, turn on this
KERN_24=y
KERNEL_SOURCE=/usr/src/linux-2.4.20-8
If you want to build the kernel under the kernel of 2.4.x, one has to set the variable
KERN_24=y and comment the KERN_26=y like that as the example above and modify
the variable KERNEL_SOURCE to the path which you install the kernel source. After
doing these things, one just need to type the ¡°make¡±, and the driver module will be
generated and installed.
2.3 Install individual driver
If you only need driver of XG-762N, you can issue :
4
make clean
make XG-762NREV_B=0
make XG-762NREV_B=0 install
to install the driver.
2.4 Build the debugging tool
There are two debugging tools in this package, ¡°apdbg¡±and ¡°menudbg¡±. Run ¡°make
debug¡±to compile them both. If you don¡¯t have the ncurse library, you may get some
error messages while compiling menudbg. You can ignore it and get apdbg only.
5
3. Getting Start
3.1 Load the driver
Generally, the driver is automatically loaded when the XG-762N dongle inserts. If not,
one can use the modprobe ¨Cv XG-762N to load our driver. In order to check whether our
driver is loaded successfully, one can use the ¡°lsmod¡± for t hi s check. If our dri ver is
loaded successfully, the following messages should be seen
...
XG-762N183576 0 (unused)
...
Please note that the 183576 may not be the same as that in your system.
3.2 Open the network interface
In our driver, we will stop all the commands until the network interface assigned to us is
opened. You can open the network interface by the following command
]$ ifconfig ethX up
or
]$ ifconfig ethX <IP address>
3.3 Configure the Wireless settings
In our driver, we support the wireless extension commands to control our driver.
PARAMETERS:
essid :
Set the ESSID (or Network Name - in some products it may also called Domain
ID). The ESSID is used to identify cells which are part of the same virtual
network.
Examples:
mode:
Set the operation mode of our device.
Examples:
mode:
Managed (Infrastructure Station mode)
Ah-hoc (Ad hoc mode)
Master (Access Point mode)
channel:
Set the channel in the device.
6
Example:
iwconfig ethX power off
#
Turn off power saving mode
iwconfig ethX channel <channel>
The channel can vary from 1 to 14. One should note that, the set channel
command will NOT work under the Managed (infrastructure mode). Because
in the in this mode, the channel should change to channel of the AP we want to
associate.
rts[_threshold]:
Set the RTS Threshold.
Example:
frag[_threshold]:
Set the Fragmentation Threshold.
Example:
key/enc[ryption]:
Used to manipulate encryption or scrambling keys and encryption mode. To set
the current encryption key, just enter the key in hex digits as
XXXX-XXXX-XXXX-XXXX or XXXXXXXX. To set a key other than the current
key, append [index] to the key itself. You can also enter the key as an ASCII
string by using the s: prefix. To change which key is the current active key, just
enter [index] (without entering any key value). off and on disable and reenable
encryption, open set the system in open mode (accept non-encrypted packets)
and restricted discard non-encrypted packets.
Examples :
power:
Used to manipulate the power management scheme mode.
Examples:
3.4 Private commands
Loading...