©Copyright 2004-2005 Marvell®.
All rights reserved.

yukonos5.htm created 21-Jul-2005

Readme File for yukonos5 driver v7.11.1.3

Marvell Yukon Ethernet Adapter


This file contains





1  Overview

The mrvl ODI driver supports the Marvell Yukon Ethernet Adapter
on SCO OpenServer 5.0.7.

2  Required Files

For proper software installation the following package file is required:
yukonos5.tar .
In the text below the expression <package file> refers to this file.

Driver packages downloaded from our web site may be available in a
compressed format (.Z files). The downloaded package has to be uncompressed
before installation. 

To uncompress the downloaded driver package, proceed as follows:

1.	Go to the directory where the compressed driver package yukonos5.tar.Z
	is located.

2.	Uncompress the file with the following command:
	uncompress yukonos5.tar.Z

3.	You will get a tar - file.
	Untar the file: tar -xvf yukonos5.tar.

4.	You will get an installable volume file e.g.: VOL.000.000
	Move this volume file to the target directory that you want to install from.

5.	IMPORTANT: If the target machine supports multiple CPUs and your OS needs to
	be configured for synchronous multiprocessing (including Hyper-Threading on
	Intel CPUs) you must have installed the following software packages for
	OpenServer release 5.0.7:

	- SCO OpenServer(TM) Maintenance Pack 3 (osr507mp3):
	  SCO OpenServer Maintenance Packages are available for download from the
	  SCO OpenServer Release 5.0.7 Maintenance Package web page:
	  http://www.sco.com/support/update/download/osr507mp.html

	- SCO OpenSever(TM) Release 5.0.7 Update Pack 3 (osr507up3):
	  SCO OpenServer Update Packages are available for download from the SCO
	  OpenServer Release 5.0.7 Update Package web page:
	  http://www.sco.com/support/update/download/osr507up.html

	  This package comprises Update Package 1 and 2, plus Hyper-Threading
	  Technology.

	A general link to the SCO OpenServer update package and maintanance package
	web sites is: http://www.sco.com/support/update/download/osr507list.html 

3  Installation of the software package

1. Start the software manager from the graphical user interface or execute
   the command 'scoadmin software' from the console.

2. Select the menue: Software -> Install New ...

3. Select the corresponding host machine from the menue e.g.: From <your machine>
   and press continue.

4. Unless you have received the install volume file on CD select the media type
   of the install package (e.g.: Media Images) and press continue.

   If the install media file is on CD select 'CD-ROM Drive' and press continue.

5. Enter the image directory where your install package is located.
   Do not specify the name of the install package in the directory path.

6. The contents of the install package is displayed in a new window. Select the
   appropriate software package and press the install button.


4  Removal of the software package

1. Start the software manager from the graphical user interface or execute
   the command 'scoadmin software' from the console.

2. Select the driver package from the list of software packages and click onto
   the Software menue.

3. Select 'Remove Software' from the item list and press 'Remove' button in the
   subsequent window. The software package will be removed from your computer.

5  Configuration of a new network device

1. Start the system administration from the graphical user interface and double
   click on the 'Network' folder. Then double click on the 'Network Configuration
   Manager' folder. Alternatively you can also run the command 'scoadmin network'
   from the console.

2. In the 'Network Configuration Manager' window select the 'Add new LAN adapter'
   item in the 'Hardware' menu.

3. Provided the network interface card has been plugged in the PCI Express slot
   the corresponding device driver will be displayed in the configuration window.
   Choose the network device driver from the list that you want to configure
   and press 'Continue' .

4. A configuration window is shown. You may choose the maximum speed of the
   network interface. You can also choose the 'Advanced Options...' button to
   change optional configuration settings of the network interface card. 
   To continue the configuration click on the 'OK' button.

5. Ignore the message 'Please verify adapter is set to the configuration just
   entered' and click on the 'OK' button.

6. In the next configuration window you may choose the protocol stack that you
   want to configure on the driver. Choose 'SCO TCP/IP' for the TCP/IP protocol
   stack and click on the 'Add' button'.

7. In the next configuration window enter the protocol specific data e.g. IP 
   address and netmask ... Then click on the 'OK' button to finish network 
   configuration.

8. The next window informs you about successful completion of the network
   configuration. Just click on the 'OK' button.

9. Upon exiting the 'Network Configuration Manager' the system prompts for
   rebuilding the kernel. You should confirm building a new kernel by clicking on
   the 'Yes' button.

   After building the kernel please answer the following two questions with 'y'
   (yes) to activate the network device driver.

   a) Do you want this kernel to boot by default ? (y/n)
   b) Do you want the kernel environment rebuilt ? (y/n)

   Press enter to continue.

10. When rebuilding the kernel has finished you should reboot the system.


6  Remove an existing network device

1. Start the system administration from the graphical user interface and double
   click on the 'Network' folder. Then double click on the 'Network Configuration
   Manager' folder. Alternatively you can also run the command 'scoadmin network'
   from the console.

2. Select the network device driver from the list of devices and click on the 
   item 'Remove network device' in the 'Hardware' menu.

3. You will be prompted for removal of the network device driver.
   Confirm the removal by clicking on the 'Yes' button otherwise click on the
   'No' button to abort the operation.

4. The removal of the device driver will be indicated in a separate message window.
   Click on the 'Ok' button.

5. Upon exiting the 'Network Configuration Manager' the system prompts for
   rebuilding the kernel. You should confirm building a new kernel by clicking on
   the 'Yes' button.

   After building the kernel please answer the following two questions with 'y'
   (yes) to activate the network device driver.

   a) Do you want this kernel to boot by default ? (y/n)
   b) Do you want the kernel environment rebuilt ? (y/n)

   Press enter to continue.

6. When rebuilding the kernel has finished you should reboot the system.


7  Parameters

Parameters can be set by means of the "Network Configuration Manager". 
There are two possibilities to set the paramters:
- during the installation of the driver, or 
- after the installation by selecting "Hardware->Modify Hardware 
  Configuration" and the <Advanced> button.

NOTE: Once a parameter has been reconfigured for an existing network device
the kernel must be rebuild and the system must be rebooted for the changes
to take effect. 

- Alternate MAC Address 

Change the adapter's current receive address or use 'default' for the built
in factory address. A valid MAC address consists of the following hexadecimal
format: xx:xx:xx:xx:xx:xx

Default: default

By default the network adapter's burnt-in factory address is used as the
station's current network address, which represents the receive address for
the protocol data.

- TX queue size (KBytes)
- RX queue size (KBytes)

These both parameters define the transmit and receive queue size in kilo
bytes. Large queue sizes may be used if data bursts from / to the network
may overrrun the receive / transmit capacity of the driver. Transmit and
receive queues buffer outgoing and incoming data.

Values : 1 2 3
Default: 2

- Duplex Capabilities

Specify the duplex capabilities of the physical port.

Values : both, full, half
Default: both

The duplex capabilities define the link mode of the media access connector
of the physical port. Possible values are: both, full, and half. 
Also refer to the parameter "Auto-Negotiation" that allows the following 
combinations of settings:

-    Auto Negotation: on        Duplex Capabilities: both
     This combination forces the port to start the auto-negotiation
     process with the best result of full-duplex or half-duplex.

-    Auto Negotation: on        Duplex Capabilities: full
     This combination forces the port to start the auto-negotiation
     process with the result of full-duplex operation mode only.

-    Auto Negotation: on        Duplex Capabilities: half
     This combination forces the port to start the auto-negotiation
     process with the result of half-duplex operation mode only.

-    Auto Negotation: off       Duplex Capabilities: both
     This combination is not valid and causes the driver to start the 
     auto-negotiation process with the best result of full-duplex or 
     half-duplex.

-    Auto Negotation: off       Duplex Capabilities: full
     If this operation mode is specified, the corresponding MAC is forced
     to work in full-duplex mode only. If the remote MAC does not support
     full-duplex mode the link will fail.

      In full-duplex mode there is no need for the Transmit Media Access
      Management to avoid contention with other traffic on the medium. The
      frame transmission may be initiated after the interframe delay 
      regardless of the	presence of any receive activity. In full-duplex 
      mode the MAC sublayer does not perform carrier extension or frame 
      bursting.

-    Auto Negotation: off       Duplex Capabilities: half
     If this operation mode is specified, the corresponding MAC is forced
     to work in half-duplex mode only. In half-duplex mode the Transmit 
     Media	Access Management attempts to avoid contention with any other 
     traffic on the medium by monitoring the carrier sense signal 
     provided by the Physical Layer Signaling (PLS) component and 
     deferring to passing traffic.

-    Auto Negotation: sense     Duplex Capabilities: <any value>
     If the auto-negotation parameter is set to `sense` any value of 
     Duplex Capabilities is ignored. In this operation mode the 
     corresponding MAC will check the carrier for the best possible mode.
     This depends on the capabilities of other stations in the network.


- Auto-Negotiation

Values : sense, on, off.
Default: on

Auto-negotiation is the capability to detect the modes of operation 
supported by the device at the other end of a link segment, to determine
common abilities, and to configure the network adapter for joint 
operation.

- Flow Control Mode

Values : Sym, SymOrRem, LocSend, None
Default: SymOrRem

This parameter can be used to set the flow control capabilities that the 
port reports during auto-negotiation. 

The following modes are possible:
- Sym (Symmetric) both link partners are allowed to send PAUSE frames.
- SymOrRem (SymmetricOrRemote) both or only remote partner are allowed 
  to send PAUSE frames.
- LocSend (LocalSend) only local link partner is allowed to send PAUSE 
  frames.
- None: no link partner is allowed to send PAUSE frames.

NOTE: This parameter is ignored if auto-negotiation is set to Off.


- Master/Slave mode

Set Role in Master-Slave-Negotiation (1000Base-T only).

Values : auto, master, slave
Default: auto

This parameter is only valid for copper adapters. For two 1000Base-T ports
to communicate, one must take the role as master (providing timing 
information), while the other must be slave. Usually, this is negotiated 
between the two ports during link establishment. If this fails, a port 
can be forced to a specific setting with this parameter.


- Speed

Specify the link speed of the corresponding port. This parameter is only 
valid for copper adapters.

Values : auto,10,100,1000
Default: auto

						***End of Readme File***