Jump to content

Help installing Unicorn ADSL modem/software


Kieth
 Share

Recommended Posts

I have a new Unicorn ADSL modem, but am unable to understand what I am suppose to do!! :) Would someone be so kind as to interprete the instructions for me.

 

The read me file says:

 

INTRODUCTION:

 

The software for the UNICORN ADSL PCI card consists of two loadable drivers,

the unicorn_atm.o and unicorn_pci.o. The unicorn driver is a standard Linux

ATM driver, that performs segmentation and reassembly (SAR) and flow control.

The unicorn_pci driver contains the ADSL modem software and hardware related

functions. It has been tested with the Linux 2.4.x kernels. Note that to use

PPPoE, PPPoA or RFC2684 protocols, the kernel may need to be patched.

 

COMPILATION:

 

To compile the drivers, unzip and untar the file. In the unicorn directory you

will find the two subdirectories unicorn_atm and unicorn_bus.

You may compile the drivers based on the include files in the kernel source

or standard kernel include files. Set the variable KERNELDIR in the Makefile's

to point to your kernel sources if the first option in chosen.

If you choose the latter, you may need to copy the contents of the kernel

source "include/net" directory into "/usr/include/net/".

Go into these subdirectories and do a "make" and a "make install".

If the compile option "USE_HW_TIMER" is set, the performance is increased,

but the CPU load increased.

Use the same compiler as you use when compiling the linux kernel. The driver has

been tested using gcc-2.96, gcc-2.95.2, gcc-2.91.66 and gcc 3.0.3.

 

 

INSTALLATION:

 

To start the ADSL software, do a "modprobe unicorn_pci". Check in the syslog that

the drivers are started OK. The ADSL line should come up automatically. The status

can also be checked using the "proc" interface (/proc/net/atm/UNICORN\:0".

SHOWTIME in the log or in the status means that ADSL connction is up and ATM cells

may be transmitted and received.

Depending on your network setup, you will need additional software as with any other

ADSL ATM card. For bridged ethernet (RFC2684), the br2684.o module and brctl is needed.

For PPPoE, any pppoe client over the bridged interface (nas0) should work

(Roaring Penguin pppoe client has been tested).

The scripts directory contains some example startup scripts.

 

Bridged (RFC2684) and PPP over Ethernet:

Depending on your kernel, you may need to patch the kernel and enable the option

"RFC1483/2684 Bridged protcols" under "Networking options". Also ATM support needs

to be enabled.

Also the user space daemon "brctl" is needed. Instructions on how to apply the

patch and the brctl and patch sources can be found at http://www.zoftware.org/adsl-pppoe.

 

PPP over ATM:

For PPP over ATM, the module pppoatm.o is needed, together with the pppd plugin

pppoatm.so and a version of pppd that supports plugins.

Currently version ppp-2.4.0b2 supports PPPoATM plugins. A patched version ready for

PPPoATM can be found at http://www.sourceforge.net/.

 

PPPoATM specific pppd options:

llc-encaps: use LLC encapsulation for PPPoATM

vc-encaps: use VC multiplexing for PPPoATM (default)

 

 

MODULE PARAMETERS:

 

Some ADSL paramters can be controlled by setting the moule paramters.

 

unicorn_pci.o:

--------------

 

ActTimeout: Timeout in ms on the duration of the activation state.

 

ActivationMode: This parameter sets in what mode the ADSL modem should be activated.

ANSI mode is 1, G.lite is 2, G.dmt is 4 and MULTI mode is 3.

If you know what mode your DSLAM operates in, use this mode. If not select either

ANSI or MULTI mode.

 

DownstreamRate: The maximum downstream rate in Kbit/sec.

 

AutoActivation: Set this to 1 if you your ADSL modem to start auotmatically (default 1).

 

DebugLevel: To debug the driver, set this to a value different from 0 and enable DEBUG

when compiling.

 

MswDebugLevel: 0 - High level, all traces enabled, 1 - Medium level, info and warnings

enabled, 2 - Low level, only warnings and errors are traced.

 

LCD_Trig: Persistency time (in msec) of Loss of Cell Deliniation defects before

disorderly shutdown (15000 default).

 

LCD_LOF_Trig: Persistency time (in msec) of Loss of Signal and Loss of Frame defects before

disorderly shutdown (5000 default).

 

TrainingDelay: Delay in msec used in training sequence. Default 80.

 

useRFCFixedRate: If 1, rate adaptive disabled. To use with ECI DSLAM in ITU mode.

 

_no_TS652: If set to 1, enable gain table for use without TS652.

 

unicorn_atm.o:

--------------

 

mac_address: If this is specified, the bridged ethernet (RFC2684) will use this

mac (ethernet) address instead of a randomly generated address. Specified as a

12 character ASCII string of hexadecimal numbers.

 

atmready_timeout: The time in seconds to wait for ADSL link up when opening the ATM

socket (default 20 seconds).

 

DebugLevel: Set this if you need to debug the driver.

 

DIV:

 

mswtest contains a simple program to start/stop and get statistics from the ADSL card.

Depending on your distribution, you may need to install atm support (atm-2.4.0) to

compile this program.

 

RELEASE NOTES:

 

(I cut this part out. Kieth)

 

IMPORTANT USB NOTES:

For USB to work correctly, I recommend using kernel 2.4.22 or later, since a lot of bugs has

been fixed in the UHCI and OHCI drivers since early 2.4 kernel releases.

If you have a 2.4.21 kernel (Mandrake 9.1 or 2.4.21-xx) you need to patch the

usb-uhci and usb-ohci drivers to avoid a freeze when starting the unicorn_usb_xxx module.

Copy the patches to the linux source directory and do:

patch -p0 < usb-uhci.patch

patch -p0 < usb-ohci.patch

 

 

 

 

There is a reference to the Makefile, so I am including it below.

 

 

 

#

## Makefile for UNICORN ADSL Modem

#

 

# Version

VERS=0x074

 

# path to kernel headers (must correspond to running kernel)

HPATH=/usr/src/linux/include

MAKE=make

 

.EXPORT_ALL_VARIABLES:

 

DIRS = adsl_status unicorntest tools

DRVDIRS = unicorn_pci unicorn_usb

 

all: all_applis all_drivers

 

all_applis:

for i in $(DIRS) ; do make -C $$i all ; done

 

all_drivers:

for i in $(DRVDIRS) ; do make -C $$i all ; done

 

clean:

for i in $(DIRS) $(DRVDIRS); do (if [ -d $$i ]; then make -C $$i clean; fi); done

 

install: install_applis install_drivers

 

install_applis:

for i in $(DIRS) ; do make -C $$i install prefix=$(prefix); done

 

install_drivers:

for i in $(DRVDIRS) ; do make -C $$i install ; done

/sbin/depmod -ae

 

only_install_drivers:

for i in $(DRVDIRS) ; do make -C $$i install ; done

 

 

 

Thanks for the help.

 

Kieth

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...