LinuxSir.cn,穿越时空的Linuxsir!

 找回密码
 注册
搜索
热搜: shell linux mysql
查看: 35006|回复: 195

Conexant USB ADSL驱动的解决办法

[复制链接]
发表于 2003-2-8 21:37:34 | 显示全部楼层 |阅读模式
这个连接:
http://adslinux.iespana.es/adsli ... -2003-01-24-src.tgz
可以看得出这个驱动是不久之前刚刚才写出来的。但是下载速度超慢,我正在下,看能不能安装成功,如果成功了,我会第一时间通知大家的(但由于时间关系也只能在明天了,呵呵),同时希望成功的兄弟也上来发个话,多谢!!!

(愿上帝保佑我,我盼这个驱动都盼了将近一年了!)


注意:sourceforge已经有conexant accessrunner usb adsl的project!已经完成!有很多更新的东西!包括pppoe-config,可以驱动起Olitec USB ADSL的cxload.c!!!!

project:
http://sourceforge.net/projects/accessrunner/

新的cxacru-2003-02-12-src.tgz:
http://prdownloads.sourceforge.n ... 12-src.tgz?download


可以驱动起Olitec USB ADSL的cxload.c(包内有说明):
http://prdownloads.sourceforge.n ... -03-09.zip?download

pppoe-config文件:
http://prdownloads.sourceforge.n ... config.txt?download

另一下地址:

http://public.planetmirror.com/pub/SF/accessrunner/
 楼主| 发表于 2003-2-8 21:43:47 | 显示全部楼层
下载完毕!
由于速度很慢,而且怕这个连接关闭,我看我能不能上传上来?
 楼主| 发表于 2003-2-9 19:29:20 | 显示全部楼层
安装说明(英文版)

Brief instructions (for RFC1483/2684 routed and PPP over ATM (PPPoA) protocols, but you can modify for others):
.- Download driver from http://adslinux.iespana.es/adsli ... -2003-01-24-src.tgz
.- Copy to /usr directory from Linux.
.- Change to /usr directory (cd /usr).
.- Uncompress archive (tar -zxvf cxacru-2003-01-24-src.tgz).
.- Download Linux kernel code source from (http://www.kernel.org), same version that you are running. Type uname -r to know version.
.- Copy Linux kernel code source downloaded to /usr/src and uncompress it.
.- go to /usr/src/linux directory and type: make mrproper
.- Select this options after you type: make menuconfig (or if you prefer graphic mode then make xconfig).

Code maturity level options
  • Prompt for development and/or incomplete code/drivers

    Loadable module support
  • Enable loadable module support
  • Set version information on all module symbols
  • Kernel module loader

    Networking options

    <*> Packet socket

    <*> Unix domain sockets
  • TCP/IP networking
  • Asynchronous Transfer Mode (ATM)

    USB support

    <*> Support for USB
  • Preliminary USB device filesystem

    <M> UHCI

    <M> OHCI

    If you are using RFC1483/2684 then choose:

    Networking options
  • Asynchronous Transfer Mode (ATM)
  • Classical IP over ATM

    If you are using PPP over ATM (PPPoA) then choose:

    Network Device Support

    <M > PPP (point-to-point protocol) support

    <M> PPP Deflate compression

    <M> PPP over ATM

    And unselect this option:

    Processor type and features

    [ ] Symmetric multi-processing support

    Exit and save configuration (ONLY SAVE INFORMATION, AFTER NOT COMPILE KERNEL CODE SOURCE).

    .- Go to /usr/cxacru directory and type make to compile and install the driver.
    .- Edit /etc/cxacru file
    .- Change protocol mode in file if it is necessary:
    PROTOCOL_MODE=1 # 1 = RFC1483/2684 routed, 2 = PPP over ATM (pppoa)
    .- Change VPI, VCI according your provider:
    # ATM
    VPI=8
    VCI=32
    This values are for Telefonica, in Spain.
    .- For RFC1483/2684 routed put your configuration in:
    # Specific for RFC1483/2684 routed
    IP_ADDRESS=
    NETMASK=255.255.255.0
    GATEWAY=
    .- If you are using static DNS servers as RFC1483/2684 routed then put into /etc/resolv.conf. Example:
    nameserver 10.1.10.1
    nameserver 10.1.10.2
    (This is an example, not use this values).
    .- If you are using ppp over atm then edit /etc/ppp file. Example:
    lock
    defaultroute
    noipdefault
    noauth
    sync
    noaccomp
    nopcomp
    noccp
    novj
    holdoff 4
    persist
    maxfail 25
    usepeerdns
    passive
    asyncmap 0
    lcp-echo-interval 2
    lcp-echo-failure 7
    name any
    user any
    plugin /usr/lib/pppd/plugins/pppoatm.so
    VPI.VCI
    (Change VPI and VCI (between VPI and VCI is a ".") according your provider). Also, you must edit chap-secrets and pap-secrets files according your provider.

    .- Add a new line in /etc/hotplug/blacklist file:
    usbcam

    .- Running the driver:
    Unplug the modem if it was connected.
    Plug the modem.
    To start driver type:
    cxstart.sh
    To stop driver type:
    cxstop.sh
    If your driver is running ok then you can it installs as service (go to /usr/cxacru directory and type make add_service then go to your service manager and start service cxacru or restart your computer).


    但是很失败,虽然这是for Conexant USB ADSL的,但是目前我还没能把他驱动起来,居然是:sorry,i didn‘t find ADSL
    晕啊!!

    有兄弟成功过吗???
  •  楼主| 发表于 2003-2-9 21:44:38 | 显示全部楼层
    Linuxfans.org上面的tideboy兄给了我如下建议,也希望对其他兄弟有帮助:

    上面这个驱动可算是一个福音,特别是对我这种使用实达5000UB(conexant accessrunner 芯片),不过它只提供了rfc1483 route 和ppp over atm 的脚本,实际上很多用户所属的ISP是使用ATM rfc1483 brige桥接,并且采用pppoe连接ISP的。

    特别注意的地方可能有以下几点,害得我花费了好几个晚上,最后发现原来如此。
    1、2.4.18以后的内核实际上不需要重新编者按译,但是得重新make menuconfig,按上述配置。最好是make modouls,make modules_install,不然可能会出现找不到模块的情况。
    2、一定要安装linux-atm软件包。
    3、实际上对任何该类USB ADSL,驱动程序只是前面一步(cxload.sh),后面的script是针对各种连接协议配置的,需要根据自已的实际情况改变。
    4、对rfc1483 route或ppp over atm的情况,我没试成功,因为自已是用rfc1483 bridge的,但是这个脚本和驱动里面无法配置atm0 的硬件地址,将atm0 ifconfig为ether的hw时不成功。很奇怪,hw address 是 00-00-00.....,配置ADSL-setup时提示无法定位atm0的link 方式(not ethernet)。
    5、对rfc1483 brige的情况,以上步骤有好几步得需要更改。
    a、如果是2.4.18以前的内核,需要patch rfc1483/2684的补丁,使内核支持rfc1483 bridge,只需要编译MODULES。然后insmod br2684(关键),不要将br2684编入内核中,要编成MODULES。
    b、安装linux-atm后,一定要安装1483 bridge usespace ,一般是br2684ctl.c或者br011220.c,注意这个小程序只能在2.4.19以上的内核下自动可以编译,在以前的内核下必须先补丁内核。否则可能会出现一些错误。反正我在2.4.18下编了好久没成功。
    c、编译好后,执行br2684ctl -c 0 -e 0 itf.VPI.VCI(根据当地的值填),使之出现nas0界面。然后 ifconfig nas0....注意设定hw address, 或自动配上去。
    d、route。
    e、adsl-setup中,网络界面选择nas0,DNS由sever指定。
    f、adsl-start,出现ppp0 interface ,,,,OK

    以上只是自已的经历,还望指正。
    有几个地方还没有设置好。
    一是自动加载驱动不太稳定,关机后开机,驱动好象正常,但是MODEM实际上灯并没亮,驱动硬件实际上并没成功,再次cxstop.sh然后cxstart.sh驱动OK。可能有些MODEM不一样。
    二是对rfc1483 bridge还没有完全配置好,如果不配置atmarpd/atm0,好象连上去没感觉,整了好久也没有整出一个自动驱动并且连接上ADSL的scripts.
    三是连接上后,ADSL不稳定,虽然一点不会断线,但是经常打开网站的时候提示连接被拒绝,刷新几次又OK了。

    另外,上面这些设置可以参照的网站:
    http://home.sch.bme.hu/~cell/br2684/
    发表于 2003-2-10 03:01:18 | 显示全部楼层
    顶.头都顶破了,绝好的东西.兄弟是很多人的救命恩人呀.
    发表于 2003-2-10 17:54:51 | 显示全部楼层
    好!我也来顶一下!!!:rolleyes:
    发表于 2003-2-10 20:06:15 | 显示全部楼层
    哪有PPPoE软件?
     楼主| 发表于 2003-2-10 20:46:45 | 显示全部楼层
    还是不成啊,运行cxload.sh还是说Error I didn't find ADSL modem…………………………………………
    发表于 2003-2-13 21:39:54 | 显示全部楼层
    我也来顶一下~!!
    总算看到曙光了
    发表于 2003-2-13 21:56:11 | 显示全部楼层

    苦战了几天,终于成了,太兴奋了,^_^

    首先感谢dragonnapalm,要不是他找到了驱动,我还在苦苦的搜寻。
    我的猫是实达的5800ub,usb接口的adsl,协议为ppp over atm。
    系统是RH8.0,linux 核心就是RH8.0自带的。
    我的安装过程如下:
    1,下载上面的驱动,解开压缩包。
    2,拷贝刚才解开的文件夹cxacru到/usr目录
    3,进入cxacru,执行make命令
    4,完毕之后就会有以下几个命令在/usr/sbin目录下
    cxioctl        cxnet2down.sh  cxnetup.sh     cxstop.sh
    cxload         cxnet2up.sh    cxpm           cxunload.sh
    cxload.sh      cxnetdown.sh   cxstart.sh

    5,cxstart.sh用来起动猫,并执行pppd拨号。cxstop.sh用来切断pppd连接并且关闭猫。
    cxload.sh载入猫的微代码,对猫进行初试化。cxstart.sh自动调用了cxload.sh。
    我们只要cxstart.sh起动,cxstop.sh关闭就行了。

    6,如果用的系统是比较新的,没有必要重新编译核心。RH8.0的核心是2.4.18
    pppoa模块已经编译好了。如果不确定的话,执行find /lib -name ppp* -print
    看是否有pppoatm.o。没有的话就要重新编译核心了。

    7,要注意的是:RH8.0系统自带的PPP软件包不包含pppoatm.so(这个共享库能够让pppd执行
    ppp over atm拨号,检查一下是
    否有/usr/lib/pppd/plugins/pppoatm.so)。
    所以要到网上找到ppp-2.4.0b2-2的rpm包,然后用rpm -e ppp卸载掉原先的软件包,
    再rpm -ivh ppp*安装新的ppp软件包

    8,既然要用pppd来拨号就要编辑好相关的文件。进入/etc/ppp目录,编辑三个文件:
    chat-secrets,pap-secrets,options。pap-secrets和chat-secrets的内容相同,类似于:
    # Secrets for authentication using CHAP
    # client        server  secret                  IP addresses
    "adsl@local"    *       "adsl"
    (注:adsl@local是上网用的帐号,adsl是密码)

    options内容为:
    lock
    defaultroute
    noipdefault
    noauth
    holdoff 4
    maxfail 25
    persist
    asyncmap 0
    lcp-echo-interval  2
    lcp-echo-failure   7
    name adsl@local           <--adsl@local是我的帐号,改成你的。
    user adsl@local             <--同上
    plugin /usr/lib/pppd/plugins/pppoatm.so
    0.200                              <---0 是我的vpi值,200是vci值

    9,修改/etc/cxacru,我的如下:
    #
    # Config file for Conexant AccessRunner
    #

    # Driver mode
    DRIVER_MODE=1  # 1 = normal, 2 = debug

    # Protocol
    PROTOCOL_MODE=2  # 1 = RFC1483/2684 routed, 2 = PPP over ATM (pppoa)

    # Paths
    BINARY_PATH="/usr/sbin"
    ATM_PATH=""

    # ATM
    VPI=0
    VCI=200

    # Specific for RFC1483/2684 routed
    IP_ADDRESS=
    NETMASK=255.255.255.0
    GATEWAY=

    10,Add a new line in /etc/hotplug/blacklist file:
    usbcam

    11,好了,到了这里基本上一切ok了!让我们试试吧。
    a,首先cxstop.sh,关闭猫。
    b,然后cxstart.sh,重新起动猫并且会自动进行pppd连接
    你应该看到类似的提示:

    >>> Inits Conexant AccessRunner <<<

    >>> Loading firmware...
    Conexant AccessRunner microcode upload program
    Josep Comas <jcomas@gna.es>. 24/1/2003

    I found ADSL modem with VendorID = 0572 & ProductID = cafe
    Loading and sending /usr/sbin/cxinit.bin...
    Sending is finished!

    >>> Loading driver...
    Launching driver in normal mode...
    Using /lib/modules/2.4.18-14/kernel/drivers/usb/cxacru.o
    Warning: loading /lib/modules/2.4.18-14/kernel/drivers/usb/cxacru.o will taint the kernel: forced load
      See http://www.tux.org/lkml/#export-tainted for information about tainted modules
    Module cxacru loaded, with warnings

    /usr/sbin/cxload.sh successful
    Setting PPP over ATM...
    >>> Setting PPPoA <<<

    >>> Loading ppp_generic...

    >>> Loading pppoatm...

    >>> Activating send/receive data...
    Conexant AccessRunner ioctl call
    Josep Comas <jcomas@gna.es>. 24/1/2003

    I found ADSL modem with VendorID = 0572 & ProductID = cafe

    >>> Loading pppd daemon...

    /usr/sbin/cxnet2up.sh successful

    c,用ifconfig命令查看是否出现了ppp0的连接,如果有的话,恭喜你,成了。
    lo        Link encapocal Loopback
              inet addr:127.0.0.1  Mask:255.0.0.0
              UP LOOPBACK RUNNING  MTU:16436  Metric:1
              RX packets:244 errors:0 dropped:0 overruns:0 frame:0
              TX packets:244 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:0
              RX bytes:16856 (16.4 Kb)  TX bytes:16856 (16.4 Kb)
    ppp0      Link encapoint-to-Point Protocol
              inet addr:61.154.28.177  P-t-P:61.154.28.1  Mask:255.255.255.255
              UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1500  Metric:1
              RX packets:285 errors:0 dropped:0 overruns:0 frame:0
              TX packets:392 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:3
              RX bytes:134727 (131.5 Kb)  TX bytes:79519 (77.6 Kb)

    以上是我查的结果。

    注:如果你有eth0连接,可能会出现一切正常但无法ping到外面的现象。试着关眛h0,重新起动adsl。

    这里有一篇非常有用的HOWTO,虽然是针对阿尔卡特的usb adsl,但ppp连接部分讲的很明白。
    SpeedTouch USB Linux Driver HOWTO
    (C) 2001, Johan Verrept
    Preface
    After a serious session of postponing and not feeling like it, I wrote this HOWTO. It contains everything I can think of that you could/should/have to know to use this driver to it's fullest capabilities. This HOWTO has explicit support for PPPoA and PPPoE, but the driver can accommodate any ATM protocol available.
    Copyright Information
    This document is copyrighted  2001 by Johan Verrept.
    Permission is granted to copy, distribute and/or modify this document  under the terms of the GNU Free Documentation License, Version 1.1  or any later version published by the Free Software Foundation;
    Driver Description
    This is a driver for the Alcatel SpeedTouch USB ADSL modem. The driver itself consists of two different parts. A kernel part and a user space part. Both parts were released by Alcatel's modem branch, now part of Thomson Multimedia. The kernel module is released under the GNU General Public License. The current maintainer is Duncan Sands. The kernel module is responsible for all data traffic. It is modeled as a Linux ATM card. This allows you to use a wide range of protocols like PPPoA, RFC2684 Bridging (allowing PPPoE), and others over PVC's and it supports ATM signaling (SVC's).
    The user space part is maintained by Alcatel/Thomson. It is distributed as a binary-only application. The Alcatel/Thomson application only does management and firmware downloading.
    The driver supports Plug-N-Play by using the Linux Hotplugging package.

    The choice between PPPoA and PPPoE depends on you provider. Most providers support one protocol, some both.  Consult the FAQ to see which protocol is applicable to you. If you can choose, PPPoA has the least overhead and thus best performance...
    The First Step: Downloading.
    General
    You will need to download quite a few packages to get this thing running.

        * The Binary Management Application (speedmgmt) from Alcatel/Thomson.
        * The Open Source Kernel Module written by Johan Verrept and maintained by Duncan Sands. The current developement version is available via anonymous cvs (replace modulename with speedtouch).
        * The Linux Hotplugging Package
        * The SARLib
        * Linux Kernel 2.4.2 or above.

    A number of these you will have to patch and/or compile yourself.
    PPPoA
    If your provider uses PPPoA you will need:

        * For kernels older than 2.4.15, the PPPoA kernel patch (grab the most recent one smaller than your current kernel version) by Jens Axboe. Newer kernels already include this patch.
        * A PPP over ATM aware PPP daemon. To see if you already have one, run the command
          find /usr/lib/pppd -name pppoatm.so If the result is "No such file or directory" then you will have to download an ATM aware PPP daemon. Try these packages, or install the ppp and linux-atm packages from SuSe (version 8.1 or newer).
          Remark: Debian users can use alien to change rpm packages into the Debian deb format.

    PPPoE
    If your provider uses PPPoE, you will need:

        * A PPPoE aware PPP daemon, such as a recent version of the ppp package or Roaring Penguin PPPoE.
        * RFC2684 Bridging kernel patch and configuration utility

    The Second Step: Patching the kernel
    Untarring the kernel
    For this you will need root permissions.
    Go to the directory where the kernel needs to be compiled.
    cd /usr/src/ Now,  move the old Linux kernel away:
    mv linux linux.old Remark: usually this is a symbolic link that can also be deleted.

    Untar your new kernel:
    If this is linux-2.4.x.tar.gz :
    tar zxvf linux-2.4.x.tar.gz If this is linux-2.4.x.tar.bz2:
    cat linux-2.4.x.tar.bz2 | bunzip2 - | tar xvf - As a good measure, move your kernel and put a symbolic link.
    mv linux linux-2.4.x
    ln -s linux-2.4.x linux Remark: Off course, do not forget to replace the 'x' with your version number!
    Remark: Do not apply both the PPPoA and PPPoE patches!  They collide.
    Remark: If you are using Mandrake 8.0, you can skip this part. The kernel supplied with Mandrake 8.0 already contains the nescessary patches.
    Remark: If you are using Mandrake 8.1, you can skip this HOWTO! Mandrake 8.1 contains an rpm with the driver.

    Applying PPPoA patches
    Only necessary if you are going to use PPPoA! Only necessary if your kernel is older than 2.4.15!
    Now, go to the kernel directory.
    cd /usr/src/linux Unzip the patch:
    gzip -d pppoatm-1.gz Apply the patch:
    patch -p1 -s -E < /path/to/pppoatm-1 Ready.

    Applying PPPoE patches
    Only necessary if you are going to use PPPoE!
    Now, go to the kernel directory.
    cd /usr/src/linux Unzip the patch:
    gzip -d  br2684-against2.4.2.diff.gz Apply the patch:
    patch -p1 -s -E < /path/to/br2684-against2.4.2.diff Ready.
    The Third Step: Configuring the kernel
    For easily configuring the kernel type:
    cd /usr/src/linux/
    make menuconfig You will need to set the following options:

        * Code Maturity Level Options
              o Prompt for development and/or incomplete code/drivers [Y]
        * Loadable Module Support
              o Enable Loadable Module Support [Y]
        * Processor type and features
              o Symmetric multi-processing support [N]
        * General Setup
              o Support for hot-pluggable devices [Y]
        * Networking Options
              o Packet Socket [Y]
              o Asynchronous Transfer Mode (ATM) (EXPERIMENTAL) [Y]
        * Network Device Support
              o PPP (Point-to-Point Protocol) Support [Y]
              o PPP Deflate Compression [Y]
        * USB Support
              o Support for USB [Y]
              o Preliminary USB Device Filesystem [Y]
              o UHCI (Intel PIIX4, VIA,...) Support [M]
              o OHCI (Compaq, iMacs, OPTi, SiS, ALi, ...) support [M]

    For PPPoA you will need the following  options:

        * Network Device Support
              o PPP Over ATM (EXPERIMENTAL) [Y]

    For PPPoE you will need these options:

        * Networking Options
              o RFC 1483/2684 Bridged protocols [Y]
        * Network Device Support
              o PPP Over Ethernet (EXPERIMENTAL) [Y]

    Be sure to turn off SMP!!
    Remark: These are the options needed to get this driver running. you will also have to enable the other drivers you need for your system.  A good starting point to determine what these are are the (currently) loaded modules. For more information on how to build a kernel see the Linux Kernel HOWTO.
    The Fourth Step: Building and Installing the Kernel
    After configuring, this is easy!
    Go to the kernel directory.
    cd /usr/src/linux Type:
    make dep
    make bzImage
    make modules
    make install
    make modules_install Congratulations with your new kernel!
    Do not forget to reboot before you continue!
    Remark: If your kernel refuses to build correctly, try to do a:
    make mrproper Before you try the above sequence.

    As a quick check you can type:
    uname -a to see if your new kernel has booted. It should return something like:
    Linux infinty 2.4.4 #4 Sun May 6 04:09:45 CEST 2001 i686 unknown If there are any problems in installing and getting your kernel to run, please consult the Linux Kernel HOWTO or the documentation of your distribution.
    The Fifth Step: Building the SpeedTouch Kernel Module
    Untar and build the SARLib:
    tar zxvf sarlib-0.2.x.tgz
    cd sarlib
    make Remark:  If the compilation of the following step fails, add a link as follows:
    ln -s sarlib-0.2.x sarlib Untar, build and install the SpeedTouch module:
    tar zxvf speedtouch-1.x.tar.gz
    cd SpeedTouch
    make
    make install Ready!

    Remark: Make sure you untar both packages in the same directory, otherwise the speedtouch module does not build.

    Remark:  If you see errors like:
    depmod: *** Unresolved symbols in /lib/modules/2.4.2/kernel/drivers/usb/speedtch.o You can ignore them, the module will work.

    Remark: If you are using speedtouch-1.0.tar.gz, you can edit speedtouch.c before building and installing it and remove the following line:

    #define DEBUG_PACKET 1

    This will cause the module to use a LOT less CPU resources.

    The Sixth Step: Installing Hotplugging.
    If you have downloaded the RPM, you do:
    rpm --install hotplug-XXXXX-1.noarch.rpm If you downloaded the source archive:
    tar zxvf hotplug-XXXXX-1.tar.gz
    make install Remark: This only work smoothly for RedHat systems, installation instruction for other distributions can be found in the hotplug README file.

    Now, to make sure your hotplugging subsystem is started at boot time:
    cd /etc/rc.d/rc3.d
    ln -s ../init.d/hotplug S07hotplug To make sure hotpluggin is disabled at shutdown, add:
    cd /etc/rc.d/rc3.d
    ln -s ../init.d/hotplug K07hotplug
    The Seventh Step: Installing the Binary Management Application
    Untar and install mgmt:
    tar zxvf speedmgmt-1.x.tar.gz
    cd mgmt
    make install
    The Eight Step:  Installing PPPoA/PPPoE
    Installing PPPoA
    First  we need the pppd.
    If /dev/ppp does not exist, we need to create it ourself:
    cd /dev
    ./MAKEDEV ppp If your distribution does not include the MAKEDEV script, or it fails to create the correct device,
    you can use the following command:
    mknod /dev/ppp c 108 0 Now we install the pppd daemon:
    rpm --install ppp-2.4.0b2-2.i386.rpm Remark:    Problems have been reported with package ppp-2.4.0-2.i386.rpm, that is why I list a beta package here.
    Remark: If installation of this pacakge fails because PAM has not been installed (for example on a  SuSE 7.1), please download the source archive and compile the pppd by hand.
    Installing PPPoE
    First we install the ATM Package:
    tar zxvf atm-0.78.tar.gz
    cd atm
    make
    make install Remark: In RH 7.0, this package will probably fail the compiling process. Do not worry, we only need the header files.

    Now we compile and install the br2684ctl utility,
    cc -o br2684ctl brctl-010226.c -latm
    cp br2684ctl /usr/sbin/ Make sure you do not have a pppd installed on your system. It will be overwritten!
    Now we install the pppd daemon:
    tar zxvf ppp-2.4.0-pppoe4.tgz
    cd ppp-2.4.0.pppoe4
    ./configure
    make
    make install If you chose to use roaring penguin PPPoE, please consult the included install instructions.
    The Ninth Step: Configuring the system
    Configuring the usb subsystem
    Add the following line to /etc/fstab:
    /dev/usb /proc/bus/usb/ usbdevfs defaults 0 0 This will mount usbdevfs at boot time.

    Remark:  If you are using mgmt version 1.3.1 or older, you must mount is under /proc/bus/usb/
    Version 1.3.2 will also look in /dev/usb/.
    Remark:  If this gives errors during booting, check whether /dev/usb is not already there. If it already exists, replace /dev/usb in the above line with /dev/invalid . The exact name does not matter, as long as it does not exist.

    To mount it now type:
    mount -a
    Configuring PPPoA
    Edit the file /etc/ppp/options and replace its contents with the following:
    lock
    defaultroute
    noipdefault
    noauth
    holdoff 4
    maxfail 25
    persist
    asyncmap 0
    lcp-echo-interval  2
    lcp-echo-failure   7
    name user@domain
    user user@domain

    plugin /usr/lib/pppd/plugins/pppoatm.so
    0.38
    These settings will cause pppd to check the link state and time out a connection after 14 seconds if the link is broken. I chose this value because If  the ADSL line looses sync, it will take about 10 seconds to resync.

    Remarks:
    You will need to replace the two "user@domain"s with your ADSL username.

    Also, in the above example "0.38" is the VPI/VCI ATM pair for the author's provider. You  will need to know what the correct values are for your provider, and substitute those. If these values are incorrect, you may sync, but will not be able to connect to your ISP's IP  layer, and probably be frustrated. These values can be obtained from the Window's  Alcatel client, your ISP or the FAQ

    Edit the file /etc/ppp/chap-secrets and replace its contents with the following:
    # Secrets for authentication using CHAP
    # client        server  secret                  IP addresses
    user@domain     *       password Now put the same contents in /etc/ppp/pap-secrets.

    Remark:   You will need to replace "user@domain" with your ADSL username and "password" with your ADSL password.
    Configuring PPPoE
    Edit the file /etc/ppp/options and replace its contents with the following:
    lock
    defaultroute
    noipdefault
    noauth
    holdoff 4
    maxfail 25
    persist
    asyncmap 0
    name user@domain
    user user@domain
    lcp-echo-interval 2
    lcp-echo-failure   7
    plugin /usr/lib/pppd/plugins/pppoe.so
    nas0 These settings will cause pppd check the link state and to time out a connection after 14 seconds if the link is broken. I chose this value because If  the ADSL line looses sync, it will take about 10 seconds to resync.

    Remark: You will need to replace the two "user@domain"s with your ADSL username.

    Edit the file /etc/ppp/chap-secrets and replace its contents with the following:
    # Secrets for authentication using CHAP
    # client        server  secret                  IP addresses
    user@domain     *       password Now put the same contents in /etc/ppp/pap-secrets.

    Remark: You will need to replace the "user@domain"s with your ADSL username and "password" with your real password..

    The Tenth Step: Running the driver
    If everything went according to plan, the driver should start as soon as you plug in the SpeedTouch USB modem. If the driver is installed correctly, you will see the following sequence when plugging in the modem:

       1. Both LED's green for a very short period.
       2. Left LED is blinking, right LED is green.
       3. Left LED is green, right LED is green/red
       4. Left LED is green, right LED is blinking
       5. Both LED's are green.

    In your /var/log/messages file or on your console you will see at plugin:
    Speedmgmt[1234]: Alcatel SpeedTouch USB Management daemon started.
    Speedmgmt[1234]: (C) Alcatel 2001, Version 1.3.1 Remark: If you are not seeing the version number, you are using version 1.3 and you MUST upgrade. The 1.3 version has a bug that will severely limit your upstream bandwidth.

    At then end of the sequence when both LED's are green  something like the following will appear:
    Speedmgmt[1234]: Modem initialized at 1120 kbit/s downstream and 128 kbit/s upstream Remark: the numbers in the message are purely dependent on your ISP and your subscription.

    If you want to dial in to your ISP, do the following:
    For PPPoE only:
    br2684ctl -b -c 0 -a 0.VP.VC Remark: VP and VC are to be replaced with the VP/VC values of your ISP. You  will need to know what the correct values are for your provider, and substitute those. If these values are incorrect, you may sync, but will not be able to connect to your ISP's IP  layer, and probably be frustrated. These values can be obtained from the Window's  Alcatel client, your ISP or the FAQ

    For PPPoE and PPPoA:
    pppd You can check your /var/log/messages to see if everything went ok.

    For PPPoA this should be something like this:
    pppd[1234]: Plugin /usr/lib/pppd/plugins/pppoatm.so loaded.
    pppd[1234]: PPPoATM plugin_init
    pppd[1324]: PPPoATM setdevname_pppoatm
    pppd[1324]: PPPoATM setdevname_pppoatm - SUCCESS
    pppd[1235]: pppd 2.4.0b1 started by root, uid 0
    pppd[1235]: Using interface ppp0
    pppd[1235]: Connect: ppp0 <--> 0.38
    pppd[1235]: local  IP address xxx.xxx.xxx.xxx
    pppd[1235]: remote IP address yyy.yyy.yyy.yyy For  PPPoE this gives something like:
    pppd[1234]: PPPoE Plugin Initialized
    pppd[1235]: pppd 2.4.0 started by root, uid 0
    pppd[1235]: Sending PADI
    pppd[1235]: HOST_UNIQ successful match
    pppd[1235]: HOST_UNIQ successful match
    pppd[1235]: Got connection: 3b8
    pppd[1235]: Connecting PPPoE socket: 00:90:1a:10:11:bd b803 nas0 0x807bdc0
    pppd[1235]: Using interface ppp0
    pppd[1235]: Connect: ppp0 <--> nas0
    pppd[1235]: local IP address xxx.xxx.xxx.xxx
    pppd[1235]: remote IP address yyy.yyy.yyy.yyy Congratulations! You are online!
    Remark:  If ppp refuses to connect, please consult the Linux PPP HOWTO.

    Appendix A: Troubleshooting
    When I plug in my modem, nothing happens.
    Check whether hotplugging is working. If you plug in a USB device, the console should give something like:

    /sbin/hotplug: arguments (usb) env (PWD=/etc/hotplug HOSTNAME=infinty DEVICE=/proc/bus/usb/001/002 ACTION=remove DEBUG=yes MACHTYPE=i386-redhat-linux-gnu OLDPWD=/ DEVFS=/proc/bus/usb TYPE=9/0/0 SHLVL=1 SHELL=/bin/zsh HOSTTYPE=i386 OSTYPE=linux-gnu HOME=/ TERM=dumb PATH=/bin:/sbin:/usr/sbin:/usr/bin PRODUCT=451/1446/100 _=/usr/bin/env)

    If this is not happening, check whether hotplugging was enabled in the kernel.

    If the LED's of the modem do not start their sequence, check whether the usb subsystem is started.
    lsmod This command should return something like:
    Module                  Size  Used by
    speedtch               10128   2  (autoclean)
    uhci                   18496   0  (unused)
    usb-ohci               16160   0  (unused) If  the uhci or usb-ohci is missing, try modprobing them:
    modprobe uhci
    modprobe usb-ohci Remark:  You will need only one of them to get things working!

    If modprobe complains about not finding the modules, go back to the section about configuring the kernel, verify the configuration of the USB subsystem. If nothing is wrong, go the section of making the kernel and rerun:
    make install
    make install_modules
    reboot If this is all ok, check whether mgmt is running.
    ps -ef | grep mgmt This should return a line like:

    root      3215     1  0 19:41 ?        00:00:00 /usr/sbin/speedmgmt

    If it does not, then check your /var/log/messages.
    If this shows something like:

    kernel: usb.c: registered new driver Alcatel SpeedTouch USB
    Speedmgmt[1234]: Alcatel SpeedTouch USB Management daemon started.
    Speedmgmt[1234]: (C) Alcatel 2001, Version 1.3.1
    Speedmgmt[1234]: bulk_write: Invalid argument
    Speedmgmt[1234]: bulk_read: Invalid argument
    Speedmgmt[1234]: bulk_write: Invalid argument
    Speedmgmt[1234]: bulk_read: Invalid argument
    Speedmgmt[1234]: USBDEVFS_SUBMITURB: Invalid argument

    Then you forgot to mount usbdevfs on /proc/bus/usb/!
    Check whether you added the line to /etc/fstab. If you have, type:
    mount -a If this does not work, check whether you have enabled the usbdevice filesystem in you kernel configuration.
    When I plug in my modem, the LED sequence finishes ok, but I cannot log on.
    Check your console or /var/log/messages file to see when ppp says.
    If it says something like this:

    pppd[1234]: LCP: timeout sending Config-Requests

    Go to /proc/net/atm and do:
    cat "/proc/net/atm/Alcatel SpeedTouch USB:0" If this file is not there,
    the speedtouch module is missing.  Repeat step 5.
    The output should be something like:
    Speed Touch USB:0 (00:90:0d:xx:xx:xx)
    AAL0: tx 0 ( 0 err ), rx 0 ( 0 err, 0 drop )
    AAL5: tx 0 ( 0 err ), rx 0 ( 0 err, 0 drop ) If the numbers are all 0's,
    the ppp daemon is wrongly configured and it is not sending data to the modem.
    If the numbers are NOT zero, check whether you have used the correct VP/VC settings and
    the correct protocol!
    When I plug in the modem the LED sequence stops when the left one is green and
    the right one is red/green.
    You are using the Alcatel managment tool Version 1.3.2, which does not work correctly. Please upgrade to 1.3.3 or a  more recent version.

    When I plugin my modem, the LED sequence never goes beyond step two and the syslog gives something like:
    Speedmgmt[1234]: Alcatel SpeedTouch USB Management daemon started.
    Speedmgmt[1234]: (C) Alcatel 2001, Version 1.3.3
    kernel: usb_control/bulk_msg: timeout
    Speedmgmt[1234]: bulk_write: Connection timed out
    kernel: usbdevfs: USBDEVFS_BULK failed dev 3 ep 0x5 len 991 ret -110
    kernel: usb_control/bulk_msg: timeout Please install the Alcatel management tool version 1.3.4 or later.
    When I plug in the modem and it reaches sync, the system hangs.
    Turn off SMP support in  your kernel!
    The connection comes up, but it is very slow, especially upstream.
    Upgrade your mgmt module to the latest version.
    Everything seems to work ok, but ppp refuses to connect.
    Please consult the Linux PPP HOWTO.

    pppd connects fine, but when I try to reach webpage, it doesn't work.

    You can try two things.
    First, try to add the following option to your /etc/ppp/options file.
    usepeerdns OR  figure out the dns server of your provider (see Windows).
    and edit your /etc/resolv.conf file.
    It should look something like:
    nameserver
    nameserver aaa.bbb.ccc.ddd
    nameserver eee.fff.ggg.hhh with aaa.bbb.ccc.ddd  and eee.fff.ggg.hhh mathcing the ip addresses of your providers primary and secondary dns.
    Remark: If you have only one ip address, just leave out the second line.
    Appendix B: Some possible tweaks
    Running without hotplugging.
    It is entirely possible to run this driver without using the hotplugging package.  You can then disable the kernel option and not install the hotplugging package.
    If you wish to do this, you have to insert the speedtch.o module by hand and start the mgmt daemon by hand.
    modprobe speedtch.o
    /usr/sbin/speedmgmt & There are no real rules. Just make sure you insert the module before the line is in sync. From speedmgmt version 1.3.3 onwards, it no longer matters when you insert the kernel module.
    Automatically dialing in at modem plugin.
    It is possible to have your system automatically dial in when your modem is plugged in.
    To do this you will have to edit the /etc/hotplug/usb/speedtouch file.
    For PPPoA it should look something like:
    #!/bin/bash

    # configuration and startup-script for the Alcatel SpeedTouch USB modem

    case $ACTION in

    add)
    # start
    mesg SpeedTouch Inserting module.
    modprobe -k speedtch

    mesg SpeedTouch Attempting to start management deamon
    /usr/sbin/mgmt &

    # allow the modem to come into sync.
    sleep 15;

    # startup pppd
    pppd
    ;;
    remove)
    killall mgmt
    ;; esac For PPPoE It should be something like:
    #!/bin/bash

    # configuration and startup-script for the Alcatel SpeedTouch USB modem

    case $ACTION in

    add)
    # start
    mesg SpeedTouch Inserting module.
    modprobe -k speedtch

    mesg SpeedTouch Attempting to start management deamon
    /usr/sbin/mgmt &

    # allow the modem to come into sync.
    sleep 15;

    # startup pppd
    br2684ctl -b -c 0 -a 0.VP.VC
    pppd
    ;;
    remove)
    killall mgmt
    ;; esac Remark: don't forget to adjust the VP/VC values!

    Important: There is a catch here though. The hotplugging system does not yet support remove events. This means you will have to kill your pppd or br2684ctl utility by hand otherwise you have problems when plugging the modem in again.

    Appendix C: Links
    The following links can prove useful:

        * There is a FAQ available.
        * Some other HOWTO's are also available:
              o French PPPoA mini-HOWTO
        o English PPPoE mini-HOWTO
    :    * SuSe has a SpeedTouch webpage.
        * The SpeedTouch Kernel Homepage
        * Linux-USB homepage
        * Linux-ATM homepage
        * Linux PPP HOWTO
        * Linux Kernel HOWTO

    Appendix C: Credits
    This HOWTO was based on the mini-HOWTO's of Chris Jones and  Pedro Ramos Silva.
    您需要登录后才可以回帖 登录 | 注册

    本版积分规则

    快速回复 返回顶部 返回列表