Madge mtok Token Ring Device Driver for Solaris 2.5/x86
=======================================================
April 1996
==========

Summary
-------

This file describes how to install and configure the Madge Smart  16/4
Token Ring  adapter  driver  for  Solaris 2.5/x86.   The  file  covers
device configuration, installation and troubleshooting.

Creating an Installation Disk
-----------------------------

If  you have been shipped the mtok driver on an installation  diskette
then skip this section and proceed to "Device Configuration".

To  create  an  installation  diskette  you will need the mdgsol25.img
diskette image file from the Madge CD or  bulletin  board.   Once  you
have this file on your  Solaris 2.5  system  place  a  blank formatted
diskette in driver A: and enter the following command:

    dd if=mdgsol25.img of=/dev/diskette0

Once  this  command  has  completed  the diskette can  be  used  as an
installation diskette.


Device Configuration
--------------------

Various hardware settings on the adapter, such as ring speed  and  DMA
channel, may be set either with switches on the adapter or a 
configuration utility  supplied  on  the  MDGBOOT  disk  shipped  with
your ringnode.  Refer to the documentation supplied with the Ringnode.

When choosing hardware settings the following points must be remembered

i)  Ensure  that  your  ringnode does not use the same IRQ, and for AT
    ringnodes DMA channel  and I/O location, as other adapters in your
    PC (Most of our adapters default to DMA channel 5).

ii) Make sure that the ring speed selected matches that of the ring to
    which you wish to connect.


Installation
------------

To install the driver insert install floppy in drive, login as 'root',
run the 'volcheck' program and then type at the command prompt:

    pkgadd -d /floppy/floppy0
	
You  will  be  asked  various  questions  by  the Solaris installation 
process, answer these as appropriate for your system.

To remove the driver if necessary type at the command prompt:

    pkgrm mtok

Once the driver has been installed you will need to bind a  networking
protocol stack to the mtok driver.  To bind the  TCP/IP protocol stack
to the mtok driver carry out the following steps:

1. In your /etc directory, create a file called hostname.mtokx.  Where
   'hostname'  is  the  name of your Solaris 2.5 system and 'x' is the
   instance number of the  Madge  adapter being bound.  E.g.  for  the
   first Madge adapter on a system  called  'helios'  you  would  name
   the file 'helios.mtok0', and for the second  adapter you would name
   the file 'helios.mtok1'.
 
2. In the hostname.mtokx file just  created,  enter  the name you wish
   other systems to  use  to  refer  to  your  system.  This  must  be
   different to your host  name.  E.g.  if your host  name is 'helios'
   you could use the name 'helios_ip'.
  
3. In  the  file  called  'hosts'  also  in  the directory /etc add an
   entry that associates an IP address with the name you placed in the
   hostname.mtokx file in step 2. E.g. if the  host  name  is 'helios'
   and its IP address is to be 123.123.123.123 then the entry might be
  
   123.123.123.123    helios_ip
  
4. Re-boot your Solaris 2.5 system.

When the adapter card starts after a reboot, the following warning may
appear during startup:

ip_rput: DL_ERROR_ACK for 29, errno 1, unix 0
ip: joining multicasts failed on mtok0 - will use link layer
		   
This is not a problem and should not affect usage of the driver.		   


Troubleshooting
---------------
   
The  driver  may print out an error  message containing two numbers on
start-up.  The following are the two most common error codes and their
(possible) causes.

Type = 0x08 Value = 0x01
========================

Reason:
-------

The adapter has failed to open onto the ring.  This could be caused by
one of the following:

i)   The lobe cable  is  not  securely attached to the adapter card or
     cabling unit.
       
ii)  The ring speed setting on the card does not match the actual ring
     speed.
       
iii) Insertion onto the ring has been  prevented  by  ring  management
     software.
       
iv)  The ring is beaconing.
      
v)   A ring parameter server on the ring has crashed.
      

Type = 0x07 Value = 0x10
========================

Reason:
-------

The adapter  test  DMA/PIO  transfer  has  failed.  This usually means
that the adapter is in PIO mode and there is some interrupt clash.


If  other  errors  are  encountered  try  running the  DOS diagnostics
program to isolate the problem.

**** End of README.INF ****

