readme.txt

linux下的无线宽带驱动

   -- On most 2.6 kernels, you should not need the full kernel source
      installed. The /lib/modules directory tree should contain everything
      needed to build a driver. On some distros, you will need to have
      installed the kernel-devel package in order to build new modules.

-- extract the tar file. A good place might be: /tmp

-- cd to where you extracted it, e.g.:   cd /tmp/ibdriver-x.y

-- Build the modules
     $ make

   If you get errors here, then you may not have the necessary
   components installed to build new modules. Check your distro information
   to find out what you need to install to build modules.

   If you do have the correct components installed and still get errors, then
   the most likely cause is that your kernel is newer than the newest kernel
   supported by the driver code. Please report any such errors to the
   sourceforge project (http://sourceforge.net/projects/ibdriver/).
   Often the changes are quite small, so it is worth seeing if you can change
   the source to get it to compile. If you succeed, please post a patch to
   the sourceforge project. We are happy to perform further quality-assurance
   on your code, so it needn't be perfect before you post it.
   A number of patches for newer kernels have been posted by users doing this.
   (Thank you again to all those who have helped the project in this way.)

   -- If you have a really good reason for doing so, you *can* specify a linux
   kernel version different to the one you are currently running.
   **Note** You must have installed the kernel-devel components for the kernel
   you are attempting to build for. Specifically, /lib/modules *must* contain a
   directory matching the kernel name, and that directory must contain a
   'build' subdirectory.

   The kernel version can be overridden using the IB_KERNEL_VERSION variable.
   Eg, to build for a 2.6.15 kernel on a machine running 2.6.17, you could
   proceed as follows:

     $ uname -r
     2.6.17-1.2187_FC5smp

     $ ls /lib/modules
     2.6.15-1.2054_FC5smp  2.6.17-1.2187_FC5smp

     $ make IB_KERNEL_VERSION=2.6.15-1.2054_FC5smp

-- Install the modules (you must be root to do this):
     $ make install

     -- Or, if you built for a version different to the running version:
     $ make IB_KERNEL_VERSION=<kernel-version> install

-- Should you wish to re-run the installation at any time,
   cd to the build directory and
     $ make clean; make; make install

-- To uninstall the files, make the uninstall target (you must be root):
     $ make uninstall

     -- Or $ make IB_KERNEL_VERSION=<kernel-version> uninstall

2. Configure the device

2a. Configuring the PCMCIA device
   The iburst pcmcia module is called "ib-pcmcia". It depends on a central
   module which is called "ib-net". If the configuration is correct, both
   drivers should load automatcially when needed, and unload when not needed.

  [Newer distros with kernel >= 2.6.13]
    **Note these instructions are for the older style pcmcia subsystem. Newer
      distros with kernels >= 2.6.13 may use the newer pccard system, which has
      no config file. If your system does not use/need a pcmcia config file,
      then you should skip this step.
  [/Newer distros]

-- Edit the pcmcia config file. This is usually called /etc/pcmcia/config.
   Insert the following lines. At the bottom is fine, but you may wish to
   order things as per the rest of the file which is alphabetically, per entry
   type. So you would put the "device" entry with the other "device" entries,
   in alphabetical order, and the the "card" entries with the other "card"
   entries.

   device "iburst_cs"
      class "network" module "ib-pcmcia"

   card "ArrayComm ut02"
      manfid 0x02e3, 0x0001
      bind "iburst_cs"

   card "ArrayComm ut02"
      manfid 0x02e3, 0x0002
      bind "iburst_cs"

  **Upgrade note: see UPGRADE.txt.

-- Edit the pcmcia parameters file. This is usually in
   /etc/sysconfig/pcmcia (others) or /etc/default/pcmcia (Debian).

     Add/modify the following line:

     CORE_OPTS="unreset_check=20 unreset_delay=100 unreset_limit=100"


-- Edit/create the appropriate modules configuration file.
   On older kernels, this was usually called /etc/modules.conf. On many 2.6
   kernels this is called /etc/modprobe.conf or /etc/modprobe.d/iburst.

   [Debian]
      Create /etc/modprobe.d/iburst, and insert the line:

      options ib-net ifname="nas-ib%d"

   [/Debian]

   [Ubuntu]
      **Note: Ubuntu is debian based, so the Debian instructiona above will
      probably work. However, the only report we have had used "eth" rather
      than "nas-ib".

      Create /etc/modprobe.d/iburst, and insert the line:

      options ib-net ifname="eth%d"

   [/Ubuntu]

   [Fedora Core (1, 2 & 3)]
      (Fedora Core doesn't always pass CORE_OPTS (above) to the pcmcia module,
      so the options are put into the modules config file as well.)

      Edit /etc/modprobe.conf and add these lines:

      # options for the core pcmcia module
      options pcmcia_core unreset_check=20 unreset_delay=100 unreset_limit=100

      #  alias for the iburst pcmcia driver
      alias iburst_cs ib-pcmcia

   [Fedora Core]

   [Others]
      Edit the modules configuration file and add the line:

      #  for the iburst pcmcia driver
      alias iburst_cs ib-pcmcia

   [/Others]

   [Some Installations]
      Usually the ib-net driver is loaded when a dependent driver, such as
      ib-pcmcia or ib-usb is loaded. Some installations may not load the ib-net
      driver automatically, in which case the following line in the modules
      config should help:

      Add the following line to the modules config file:

      alias ib0 ib-net

   [/Some Installations]


   [Other Parameters]
     The iburst drivers support the following module parameters, any of which
     can be set using an appropriate "options" line in the modules config
     file (/etc/modprobe.conf, etc).

     Example: options ib-pcmcia debug=7 interval=100

     ib-pcmcia
       - debug  values between 0 and 9, with 0 meaning disabled, and 9 meaning
         maximum output (default is 0).

       - io16   value is either 0 or 1, with 1 enabling 16-bit transfers
         to/from the card, and 0 meaning 32-bit transfers (default is 0).

       - interval  values between 10 and 1000, which specify the driver poll
         interval in milliseconds. Smaller settings will increase CPU usage of
         the driver (not normally a problem), and larger values will limit the
         maximum throughput. Eg, a value of 200 will typically limit throughput
         to around 180kbits/sec. (default 10).

       - irq_mask  values in hex, which specify, as a bit-mask, the irq
         interrupts to choose from (default is 0xdeb8 which corresponds to
         interrupts 15, 14, 12, 11, 10, 9, 7, 5, 4, and 3).

       - irq_list  a list of four integers, which specify the interrupts to
         choose from (default is not set).

     ib-net
       - debug  values between 0 and 9, with 0 meaning disabled, and 9 meaning
         maximum output (default is 0).

       - ifname  value is a string, which specifies the text part of the
         interface name to use (default is "ib%d").

     ib-usb
       - debug  value between 0 and 9, with 0 meaning disabled, and 9 meaning
         maximum output (default is 0).

   [/Other Parameters]


   **Upgrade note: see UPGRADE.txt

-- If you are not planning on rebooting, then you need to restart the pcmcia
   service to make it read the new configuration:

     $ service pcmcia restart

     or

     $ /etc/init.d/pcmcia restart


2b. Configuring the USB device
   Depending on distro, kernels arounf 2.6.15 no longer needed manual
   configuration of the USB system to recognise new hardware. So on a newer
   installation, no configuration of the USB sub-system is required.
   A simple test is to connect the USB device, check the logs to see that is
   has been recognised, and then perform lsmod to see if the ib-net and ib-usb
   drivers have been loaded. If not, then you may need to perform the
   configuration below.

   The iburst usb module is called "ib-usb". It depends on a central module
   called "ib-net". If the configuration is correct, both modules should load
   automatically when they are needed, and unload when they are not needed.

-- Add the following lines to /etc/hotplug/usb.usermap:

ib-usb 0x0003 0x0d14 0x0009 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x00000000
ib-usb 0x0003 0x0482 0x0204 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x00000000

-- If you are not planning on rebooting, then you need to restart the hotplug
   service with this command:

        $ service hotplug restart

        or

        $ /etc/init.d/hotplug restart

  [Fedora Core 3 (kernel 2.6.11-1.27_FC3, +others?)]
     hotplug is not a service, but is part of the kernel, so attempting to
     restart it (as above) will fail. In addition, hotplug does not load
     modules automatically from the definitions in usb.usermap (above).
     Instead, it attempts to run a script (in this case "ib-usb") in
     /etc/hotplug/usb. So you need to write it:

     -- Create /etc/hotplug/usb/ib-usb, and insert the following lines:

        #!/bin/sh
        modprobe ib-usb

     -- Make this file executable:
     $ chmod a+x ib-usb

   [/Fedora Core 3 (kernel 2.6.11-1.27_FC3)]


3. Insert/connect the device (PCMCIA or USB)
   It is a good idea to monitor the message log when inserting/connecting
   the device for the first (few) times (as root):

     $ tail -f /var/log/messages

   Insert/connect the device. watch the log for messages (good) or errors
   (bad).

3a. The PCMCIA device.
   The two lights should come on. The power light starts out purple(ish), and
   turns blue after a few seconds. If it does not turn blue, then the
   ib-pcmcia driver has not registered the card. Check the logs to see why.
   The activity light should change from orange to green (usually going
   through red). It then usually flickers a couple of times as it looks for
   the iBurst network.

3b. The USB device.
   The lights all come on when the device is plugged into the external
   power.


4. Set up the pppoe dialler to use the correct interface ("ib0" or "nas-ib0",
   etc), along with your user name and password. If you are using the
   roaring-penguin PPPoE package, you can use "adsl-setup" (as root).
   If you are using Debian, you can use the pppoe dialler that comes with that
   (see the separate instructions in section 4.1 for configuring debian's PPPoE
   dialer) or you can download and configure the roaring-penguin PPPoE dialer.
   Those users using the roaring-penguin dialler see the section 4.2 in this
   file for more details on configuring it.

 **Upgrade notes: see UPGRADE.txt

4.1 Configuring the Debian PPPoE dialler
-- Create /etc/ppp/peers/dsl-provider containing these lines:

        noipdefault
        usepeerdns
        defaultroute
        hide-password
        lcp-echo-interval 20
        lcp-echo-failure 3
        connect /bin/true
        noauth
        persist
        maxfail 0
        mtu 1492
        noaccomp
        default-asyncmap
        plugin rp-pppoe.so nas-ib0
        user "[e-mail]"

-- Add this line to /etc/ppp/pap-secrets:
        [e-mail] * password

-- Add these lines to /etc/network/interfaces:
        iface nas-ib0 inet manual
                up ifconfig $IFACE up
                up pon dsl-provider
                down poff dsl-provider
                down ifconfig $IFACE down


   You can manually start/stop the interface using:

     $ ifup nas-ib0

     and

     $ ifdown nas-ib0

4.2 Configuring the Roaring-Penguin PPPoE dialler

   The simplest way to configure roaring penguin PPPoE is with
   adsl-setup. Answer the questions, and all should be well:
      $ adsl-setup

   Most of the questions are straight forward. For the iburst driver, the
   Ethernet interface you want to use is "ib0" or "nas-ib0"
   (assuming you have setup a single card/modem).