|
Contents:
TokenExpress Adapter Driver Installation For UNIX: SCO, UNIVEL, Interactive
Installing and using the UNIX drivers
Before you begin
- Install and configure the TokenExpress adapter according to the
instructions in the Intel TokenExpress LAN Adapters: Installation
and Configuration Guide. Write down the configuration settings
assigned to the adapter; you'll be asked to supply them when
installing the driver.
- Make sure you have the correct driver disk from this packet. Check
the label for your version of UNIX and your TokenExpress adapter.
Also, if you're unfamiliar with basic UNIX operations, have a copy
of your UNIX system documentation handy.
Installing the drivers
This document includes instructions on installing the drivers for the
following UNIX operating systems:
- SCO UNIX V Release 3.2.4 (Open Desktop 2.0)
- Univel UNIX System V Release 4.2 (UnixWare)
- Interactive UNIX Release 3.2 Version 3.0
Note: UnixWare 2.0 driver can either be a native UNIX driver or a
transmogrified NetWare server driver. Intel will be providing a
transmogrified driver for our adapter and they will be available on our
offline services once they have completed testing. Currently do not
have an anticipated date for availability.
If you get an error message
If you get an error message from the UNIX driver, see "Error messages
for UNIX driver software" listed below for explanations and a list of
possible solutions.
Installing The Driver Software For SCO UNIX System V Release 3.2.4 Networks (Open Desktop 2.0)
To install the driver software
- Log in as root and type this at the UNIX command prompt:
custom <enter>
If you plan on using Drive 1 of this computer for the driver disk,
include after the custom command:
-m /dev/rfd1
- From the main menu, choose "Install," then "A new product," then
"Entire Product."
- When the program prompts you, insert the Intel adapter driver disk
and press <enter>. The program notifies you that the driver will be
installed. Press <enter> to continue with the installation.
- After the files are installed, the program asks if you want to
relink the kernel. Answer "No" to postpone the rebuild until after
you have set up the driver.
- Quit from each submenu until the UNIX prompt is displayed. Remove
the disk from the drive and continue with the next procedure.
To rebuild the UNIX kernel
- Type at the UNIX command prompt:
netconfig <enter>
- The program asks if you want to install or remove the driver.
Choose Install.
- The program asks a series of questions about the adapter's
configuration. Make sure the settings you specify are the settings
that were used to configure the board.
Note: When specifying the DMA channel for the EISA 16/4 board, enter
-1.
A message appears saying that the driver is being activated.
- The program asks if you want to relink the kernel. Answer "Yes." It
takes several minutes to build the kernel. Then, the program asks
if you want the kernel to boot by default and if you want the
kernel environment rebuilt. Answer "Yes" to each of these
questions.
- After the kernel is set up, make sure that the driver information
contained in /etc/strcf and /etc/rc2.d/S85tcp is correct. If any
information is missing or different from the examples below, use an
editor to modify the file.
If you're installing the driver for the EISA/32 adapter, substitute
xtr for otr.
- The boot macro section near the end of /etc/strcf should contain
this line:
cenetb ip /dev/otr otr 0
If you have multiple adapters installed, the file should also
contain these lines:
cenetb ip /dev/otr otr 1 (for a second adapter)
cenetb ip /dev/otr otr 2 (for a third adapter)
- The Start action at the beginning of /etc/rc2.d/S85tcp should
contain this line:
ifconfig otr0 hostname -trailers
If you have multiple adapters installed, the file should also
contain these lines:
ifc
ifconfig otr2 hostname3 -trailers (for third adapter)
Where hostname is a unique name assigned to this adapter. You must
specify this name preceded by the internet address in the
/etc/hosts file. For example, 128.215.1.164 hostname
Make sure you enter the same hostname in /etc/rc2.d/S85tcp and
/etc/hosts.
- Shut down the system and restart your computer.
- Once the system is up, log in as root and enter this command to
verify the presence of the driver:
netstat -i <enter>
The driver is listed as otr0 (for the first adapter), otr1 (for the
second adapter), or otr2 (for the third adapter).
If you're using the EISA/32 adapter, the driver is listed as xtr
instead of otr.
For more information
At the command prompt, type man otr or man otrstat.
(For the EISA/32, type man xtr or man xtrstat.)
Installing The Driver Software For Univel Unix System V Release 4.2 Networks (Unixware)
First time installation of the driver software.
If your computer already has the driver installed, follow the
instruction below titled "If the driver is installed already."
- Log in as root and type this command at the UNIX command prompt:
pkgadd -d diskette1 <enter>
If you plan on using Drive 1 for the Intel disk, specify diskette2
instead of diskette1 at the command prompt.
- When the program prompts you, insert the Intel driver disk and type
Go <enter>
- The program asks if you want to install all the packages contained
on the disk. Press <enter> to install all the packages.
- The program asks a series of questions about the adapter's
configuration. Make sure the settings you specify are the settings
that were used to configure the board.
Note: When specifying the DMA channel for the EISA board,
select "None."
- The program now rebuilds the UNIX kernel. This may take a few
minutes. Once it builds the kernel, remove the Intel disk and type
q (for quit).
- Make sure that the driver information contained in the files
/etc/confnet.d/netdrivers and /etc/confnet.d/inet/interface is
correct. If any information is missing or incorrect, use an editor
to modify the file.
If you're installing the driver for the EISA/32 adapter, substitute
xtr for otr.
If you have multiple adapters installed, the file should contain
these lines:
otr:1:hostname1:/dev/otr1:-trailers
otr:2:hostname2:/dev/otr2:-trailers
where hostname is a host name different to and separate from the
nodename/UNIX name of the machine.
- Shut down the system and restart your computer.
- Once the system is up, log in as root and enter this command to
verify the presence of the driver:
netstat -i <enter>
The driver is listed as otr0 (for the first adapter), otr1 (for the
second adapter), or otr2 (for the third adapter).
If you're using the EISA/32 adapter, the driver is listed as xtr
instead of otr.
If the driver is installed already
You need to remove the driver from the kernel and install the driver
again (specifying the total number of adapters you have). After you
complete these steps, follow the procedure in the previous section, "To
install the driver software for the first time."
- 1. Log in as root, and enter this at the UNIX prompt:
sysadm <enter>
- Select Software Install & Removal.
- Select Remove packages.
- Tell the program the name of the software packages and their
location when asked. The driver is listed as otr0 (only adapter),
otr1 (second adapter). If you're using the EISA/32 adapter, the
driver is listed as xtr instead of otr.
- Select Save. The program removes the package and rebuilds the
kernel. This may take a few minutes.
For more information
From the /usr/ucb/man directory, type man otr or man otrstat.
(For the EISA/32, type man xtr or man xtrstat.)
Installing The Driver Software For Interactive Unix Rel3.2 V3.0 Networks
To install the driver software
If your computer already has the TokenExpress adapter driver installed,
log in as root and skip to the procedure below titled "To rebuild the
UNIX kernal."
- Log in as root and type this at the UNIX command prompt:
sysadm installpkg <enter>
- The program displays a list of drives and disk sizes. Select the
drive and the size disk you are using. The program prompts you to
insert the driver disk.
- The program asks which packages you want to install. Press q then
<enter> to install all the packages. Answer OK to continue with the
installation.
After the packages are installed, the program asks if you want to
install another package. Answer No. The program returns to the
command prompt.
- Remove the disk from the drive and continue with the procedure
below.
To rebuild the UNIX kernel
- At the command prompt, type:
sysadm software <enter>
- Choose Netdrvr, then Configure, then Otr0 for the first adapter,
Otr1 for the second adapter, or 0tr2 for the third adapter.
If you're using an EISA/32 adapter, select Xtr0, Xtr1, or Xtr2.
- The program asks a series of questions about the adapter's
configuration. Make sure the settings you specify are the settings
used to configure the board.
- The program asks if you want to build the new UNIX kernel. Answer
Yes. From the Kernel Configuration menu, choose "Build" then "Build
a Kernel." It may take a few minutes to build the kernel.
Afterwards, the program asks for a description of the kernel
(entering one is optional).
- From the Kernel Configuration menu, choose "Install." The program
displays a list of kernels. Select the kernel you just built. (You
can identify the new kernel by the date and time displayed.) Then
choose "Install."
- The program asks if you want to shut down the system. Do not shut
it down. Instead, quit out of each submenu until the Software menu
appears.
- Set up the driver for TCP/IP.
- Choose "TCPIP," then "HBTCP," then "Addinterface."
- Choose "Add a third party Ethernet driver." Even though it says
Ethernet*, this is the correct option.
- The program asks for the driver name, hostname, netmask, and
broadcast address. Enter the settings appropriate for your setup.
For an ISA 16s or EISA 16/4 adapter, the driver name is otr0
(only adapter), otr1 (second adapter) or otr2 (third
adapter).
For an EISA/32 adapter, the driver name is xtr0 (only
adapter), xtr1 (second adapter) or xtr2 (third adapter).
The hostname can be found in the /etc/host file. After
entering your settings, type q to Quit.
- Quit out of each submenu until the root prompt appears.
- Shut down the system and restart the computer. The driver
installation is complete.
For more information
At the command prompt, type man otr or man otrstat.
(For EISA/32, type man xtr or man xtrstat)
Error Messages For Unix* Driver Software
Number / Message
001E:
Adapter doesn't interrupt.
* Make sure the adapter's interrupt level is configured in
TokenSet; then, run the diagnostics again.
002E:
Adapter initialization failed.
* Make sure the adapter's configuration settings are correct
and don't conflict with any other device in this computer.
003E:
Adapter has initial DMA error.
* Make sure the adapter's configuration settings are correct
and don't conflict with any other device in this computer.
* This computer may not support bus master mode properly. Try
moving the adapter to another computer to see if it works
properly there.
004E:
Adapter timed out in initialize command.
* Make sure the adapter's configuration settings are correct
and don't conflict with any other device in this computer.
* Make sure the adapter's settings match the settings specified
during the driver installation.
005W:
Couldn't find major number.
The driver information contained in the file /etc/inet/strcf
may be incorrect. Try reinstalling the driver. Refer to the
instructions in the installation guide for the driver.
006W:
Unknown major number.
* See suggested action for 005W.
007W:
Adapter lobewire fault.
* Make sure the network cable is securely connected to the
adapter and to the MAU.
* Make sure the cable you're using is one of the cables Intel
recommends. Refer to the adapter's installation guide for the
cable recommendations.
* If the previous suggestions haven't helped, there may be a
problem with another node.
008W:
Adapter has been removed from ring by an external authority.
* Reboot this computer so that the adapter can attempt to
reattach itself to the ring.
* If error repeats, LAN security may not allow this computer to
access the Token Ring.
009W:
Adapter has been removed from ring during beacon processing.
* See suggested action for 007W.
010E:
Adapter has closed with adapter check hardware error.
* Make sure the cable is securely connected and in good
condition (no damage, no bent pins, etc.).
011E:
Adapter is an XT adapter. Must be at least an AT-adapter.
* The driver works with TokenExpress EISA and ISA adapters
only. Try using it with one of these adapters.
012E:
Configuration conflict Adapter configured for IRQ 10. Driver
configured for IRQ 9.
* Make sure the adapter's settings match the driver
configuration settings.
013E:
Configuration conflict: Adapter has RPL enabled. Must be
disabled.
* The driver won't work when the adapter is set for RPL.
Reconfigure the adapter and disable remote boot.
014E:
Configuration conflict: Adapter configured for DMA 5. Driver
configured for DMA 6.
* See suggested action for 012E.
015E:
Configuration conflict: Adapter is in an 8-bit slot. Must be
in a 16-bit slot.
* Reinstall the adapter in a 16-bit slot.
016E:
Adapter failed internal diagnostics.
* Make sure the adapter's configuration settings are correct
and don't conflict with any other device in this computer.
Run diagnostics; then, contact your dealer or Intel's
Customer Support.
017E:
Adapter timeout on internal
* The adapter may be defective. Run diagnostics; then,contact
your dealer or Intel's Customer Support.
018E:
Download code contained illegal length
* The driver software may be corrupted. Contact your dealer or
Intel Customer Support for a replacement.
019E:
Adapter opened failed with node address error.
* The adapter's burned-in node address may be defective. Run
the diagnostics; then, contact your dealer or Intel Customer
Support for a replacement.
* The user-specified node address may be incorrect. Check that
the address specified in the space.c file is correct. For SCO
UNIX 3.2 and Interactive UNIX V Rel. 4, the space.c file is
located in the /etc/conf/pack.d/otr directory. For
Interactive UNIX V Rel. 3.2, the space.c file is located in
the /etc/conf/pack.d/otrx directory where x is 0 (only
adapter), 1 (second adapter) or 2 (third adapter).
020E:
Adapter open failed with list size error.
* See suggested action for 018E.
021E:
Adapter open failed with buffersize error.
* See suggested action for 017E.
022E:
Adapter open failed with expansion RAM error.
* See suggested action for 017E.
023E:
Adapter open failed with transmit buffer count error.
* See suggested action for 018E.
024E:
Adapter open failed with invalid open options error.
* See suggested action for 018E.
025E:
Adapter open failed with xx error during the YY phase.
* See suggested action for 007W.
Second Edition, April 1994 304774-002
Copyright(c) Intel Corporation. All rights reserved.
Intel Corporation, 5200 N.E. Elam Young Parkway, Hillsboro, OR
97124-6497.
Intel Corporation assumes no responsibility for errors or omissions in
this document. Nor does Intel make any commitment to update the
information contained herein.
The Intel logo is a registered trademark of Intel Corporation,
registered in the United States of America and other countries.
TokenExpress is a trademark of Intel Corporation.
All other brand and product names are trademarks of their respective
owners.
This applies to:
| 
