Ciao a tutti.
da qualche giorno sono diventato un nuovo utente di suse, lo uso costantemente all'università, ma solo da poco l'ho installato sul mio pc di casa (il mio caro vecchio pentium), ora installando il SO non ho avuto problemi di nessun tipo, ma è la configurazione del modem che mi crea delle difficoltà.
vi posto la documentazione relativa al manuale...sono handicappato di brutto lo so...aiutatemi.

[ho visto che un topic simile a questo era già stato fatto, ma nessuno ha risposto, spero ora che almeno qualcuno mi posso indicare la strada la seguire.]

Introduction
------------
This file describes the Linux LAN/WAN driver for the GlobespanVirata ADSL USB adapters.

This driver supports Linux-2.4 kernels. The Linux kernel sources can be download from:
http://www.kernel.org/pub/linux/kernel/v2.4/
The driver supports Linux-2.4 kernels.

The installed system should already have the kernel sources
installed in the /usr/src/linux directory. If they are not there,
try to get them off the installation disks for your distribution,
or download the latest Linux-2.4 kernel , and configure and
build that. One common problem while compiling modules on a new
kernel is not to create link /usr/src/linux which should point to
the relevent kernel source directory. On a freshly installed system
this link might not be present and needs to be created before the
kernel or any driver module can be compiled. There are lots of books
and documents available describing how to extract, configure and
build the kernel from it's sources...

The driver is compiled and tested for:
- RedHat 7.1 : kernels 2.4.2-2 using gcc 2.96
- RedHat 8.0 : kernel 2.4.18-14 using gcc 3.2
- RedHat 9.0 : kernel 2.4.20-8 using gcc 3.2

Release Notes
=============
Current
-------
v1.01.0005E (12/01/2004)
Run-time version: 1.00.0004
Firmware version: Y1.8.1 (Annex A)

-Support for multiple ethernet interface using different VPI/VCI (Rfc1483 mode only)

History
-------
-> v1.01.0004E (05/07/2004)
Run-time version: 1.00.0004
Firmware version: Y1.8.1 (Annex A)

-Endianness Related Fix in USB Interrupt Pipe processing (VTAen36951)

-> v1.01.0003E (08/07/2003)
Run-time version: 1.00.0004
Firmware version: Y1.8.1 (Annex A)

-Firmware has been updated to Y1.8.1

-Merged changes from ATM library

-> v1.01.0002E (06/18/2003)
Run-time version: 1.00.0010
Firmware version: Y1.4.8 (Annex A)

-Firmware has been updated to Y1.4.8 which contains following fixes:
1) Removed the forced re-handshake that was used for cafe biquad training.
Known issues:
2) Watch out for cafe bridged-tap performance.

-VTAen25931: Improper "training" state shown in Cetragate driver.
Driver indicates "training" when the DSL cable is not plugged in.

-> v1.01.0001E (04/28/2003)
- Initial release of driver with support for Linux-2.4 kernels.

Directory Structure
====================
The directory Structure is as follows.
monaco_linux
|
|---ModemDrv
|
|---gpatm
|
|---Gti
|
|---cpl

Compiling the Driver
====================

- Steps to compile are as follows
- build the ATM and Gti libraries in their respective directories as shown
in commands below
% cd gpatm
% make
% cd ../Gti
% make
% cd ..
- Build the driver by running make in ModemDrv directory

The Makefile contains following important options at the top of the file:

LINUX_SRC - Path to the Linux kernel sources [/usr/src/linux]
DEBUG - Output driver debug messages [n]
LAN - Create LAN interface [y]
WAN - Create WAN interfaces [y]
UNITTEST - Used for testing the system [y]
MODULE_PARAMS - Module load parameters

Compiling the Control Panel Application
---------------------------------------
The Makefile understands following target(s).
% make - This is to create the Control panel application. (Command to be executed from directory monaco_linux/cpl.)

Loading Modem Driver
=====================

The module accepts several parameters that can be set when the module is loaded.

Syntax:
insmod ./GSPNModem {Module Options} (Command to be executed from directory monaco_linux/ModemDrv)

Module Options
--------------
Rfc1483Mode default: 0 (Bridged LLC)
Rfc1483VciX default: 85+X (X would be 1,2,3,4)
Rfc1483VpiX default: X (X would be 1,2,3,4)
Rfc2364Mode default: 0 (VC)
Rfc2364Vci default: 100
Rfc2364Vpi default: 100
PVCCount default: 1

VPI and VCI settings to be used according to what's configured.

For example to load the module and to create 4 interfaces using different set of VCI/VPI the command would be as follows:

% insmod ./GSPNModem Rfc1483Mode=0 Rfc1483Vci1=35 Rfc1483Vpi1=0 Rfc1483Vci2=36 Rfc1483Vpi2=1 Rfc1483Vci3=37 Rfc1483Vpi3=2 Rfc1483Vci4=38 Rfc1483Vpi4=3 PVCCount=4

Issuing this command will create 4 ethernet interfaces. ( Combination of Rfc1483Vpi1 and Rfc1483Vci1 will be the first interface, Rfc1483Vpi2 and Rfc1483Vci2 will be 2nd interface and so on.)

The details of various options used in command above is as below

1). PVCCount - This indicates the number of PVCs user wants to configure. Maximum value for this variable in this release is 4 and hence can have any walue between 1 and 4, any value above 4 and below 1 is invalid and driver loading will fail.

2). Rfc1483Vpi1, Rfc1483Vpi2, Rfc1483Vpi3, Rfc1483Vpi4 -- These are 4 different values of the VPIs that user wants to configure.

3). Rfc1483Vci1, Rfc1483Vci2, Rfc1483Vci3, Rfc1483Vci4 -- These are 4 different values of the VCIs that user wants to configure.

4). Rfc1483Mode defines the mode for which the PVC is operating. In this release this value of Rfc1483Mode remains same for all the PVCs which are being created. Thus all VCs using rfc1483 encapsulation will be created using same encapsulation type.

Note: Please note that the VPIs/VCIs of the PVCs should not be conflicting with each other else the driver loading will fail.

Verification of driver loading successfully
===========================================
To determine if the driver has loaded:
% dmesg (or file /var/log/messages)

gp: USB Modem Driver Build

To determine if driver is in data mode.
% dmesg (or file /var/log/messages)

gp: Link established (8000/892)
^^^^ ^^^
^ ^
^ Upstream rate
Downstream rate

Alternatively the control panel application can also be used to get Modem Status as given below.
% gsi_cfg eth2 -s ( The ethernet device depends on what has been configured on the system )
(Command to be executed from monaco_linux/cpl)

Changes required to support the number of MAXIMUM PVCs that user can configure
===============================================================================
1) File Modemdrv/inc/atmuni.h (line 65) contains macro MAX_PVC_SUPPORTED which is presently set to 4. Change this to the desired maximum number of interfaces required.

2) Make changes in file Modemdrv/inc/atmusb.h ( after Line 228) to define the default values of additional VCIs and VPIs. For example if user increases MAX_PVC_SUPPORTED to 5 then add following lines in Modemdrv/inc/atmusb.h
#define RFC1483_DEFAULT_VCI5 90
#define RFC1483_DEFAULT_VPI5 4

3) Add following lines in Modemdrv/src/GULinux.c (After Line 156). This will add the addtional VPI/VCI Configuration parameter to be recognized by insmod command.

MODULE_PARM_DESC(Rfc1483Vci5, "RFC1483 VCI");
MODULE_PARM(Rfc1483Vci5, "h");
MODULE_PARM_DESC(Rfc1483Vpi5, "RFC1483 VPI");
MODULE_PARM(Rfc1483Vpi5, "h");

4) Add following lines in Modemdrv/src/GULinux.c (After Line 106). This will define variables to be used for additional VPI/VCI Configuration.
static u16 Rfc1483Vci5 = RFC1483_DEFAULT_VCI5;
static u16 Rfc1483Vpi5 = RFC1483_DEFAULT_VPI5;

5) Add following lines in Modemdrv/src/GULinux.c (After Line 411 in function GpQueryConfig) This sets the additional VPI/VCI values in internal configuration structure from static variables corresponding to command line parameters)

pCfg->rfc1483Vci[X] = Rfc1483VciX;
pCfg->rfc1483Vpi[X] = Rfc1483VpiX;
X in above two line is the index added. Say if max pvc is modified to 5 then X will be 5.

Unloading the module & the firmware loader
------------------------------------------
To unload an unused module:
% rmmod ./GSPNModem (Command to be executed from directory monaco_linux/ModemDrv)

You may need to exit or disconnect any program current using the module
before it will unload. If the module was configured for LAN, shutdown
the ethernet interface:
% ifconfig eth2 down

Note: If multiple ethernet interfaces are created then all the ethernet interfaces need to be brought down before unloading the driver.

If the module was configured as a WAN device, you may need to disconnect
the PPP daemon (pppd) from the TTY interfaces. Do this by terminating
the PPP daemon:
% killall pppd

LAN Configuration
-----------------
To enable LAN traffic over the ethernet interface:
% ifconfig eth2 192.168.1.200 up

You may also need to modify the netmask and route for the interface.
Refer to the manual pages for ifconfig and route for more information.

To test the LAN connection is alive by pinging the remote side:
% ping 192.168.1.1

To disconnect the LAN inteface:
% ifconfig eth2 down

WAN Configuration
-----------------
The PPP daemon (pppd) talks to the driver over TTY devices. Before the
driver can be used, the devices /dev/ttyG0 and /dev/cug0 need to be
created. This can be performed by executing:
% make devnodes

or by entering the following from the command line:
% mknod /dev/ttyG0 c 43 0
% chown root.uucp /dev/ttyG0
% chmod 0660 /dev/ttyG0

% mknod /dev/cug0 c 44 0
% chown root.uucp /dev/cug0
% chmod 0660 /dev/cug0

Next, PPP needs to be configured as a client to connect to a PPP
server. The PPP server should already be created, and a dialup
user configured. For this example, the user name is "test_user",
and the user password is "test_password".

Add the following (delete the leading spaces, and replace the spaces
with tabs) to: "/etc/ppp/pap-secrets" and "/etc/ppp/chap-secrets"
"test_user" * "test_password"
Please note that user name and passward should be given in double quotes
as shown above.

Create a PPP description file: "/etc/ppp/peers/adsl" that contains:
user "test_user"
ttyG0
sync
mtu 1490
mru 1490
debug

To initiate a WAN connection execute the following:
% pppd call adsl

To test the PPP connection by pinging the remote side:
Do ifconfig -a to get the remote IPADDRESS and then ping the remote.
% ping Remote IPADDRESS

PPPoE Configuration
-------------------
The PPPoE should be installed on the system.

The file /etc/pppoe/pppoe.conf should have ETH=eth1 (where eth1 is the Ethernet card connected to ADSL modem)
and USER=test_user.

To enable the interface:
% ifconfig eth1 up ( eth1 is the ethernet device as configured in file /etc/pppoe/pppoe.conf

Then execute:
adsl-start

Changing Driver and DSP Parameters Configuration
------------------------------------------------

GlobespanVirata provides "gsi_cfg" control panel application ( available in cpl directory in src tree) to enable
customers to change the drivers and DSP parameters on run time.

To see the parameter of the application run following command

gsi_cfg eth1 -h

To change the Driver and DSP parameters. Modify the gp.cfg file and run the control panel with Change configuration option(run -C eth2)

Various modes tested
--------------------

WAN modes tested
1. RFC 2364 PPPoATM NULL encapsulation
2. RFC 2364 PPPoATM LLC encapsulation
3. RFC 2516 PPPoE encapsulation

LAN modes tested
1. RFC 1483 IPoATM bridged LLC encapsulation
2. RFC 1483 IPoATM routed LLC encapsulation

LAN modes which are not tested are
1. RFC 1483 IPoATM bridged VC encapsulation
2. RFC 1483 IPoATM routed VC encapsulation

Known Issues
------------
None so far