1. orgdsk8832.zip Driver
2. SCO4.TXT File Contents

SCO4.TXT Driver File Contents (orgdsk8832.zip)

   SCO UNIX 4.X

   Introduction:
   -------------
      This document describes the procedure to install the SCO UNIX driver
      for ALL8832 PCI Fast Ethernet adapter.

   Location of Driver:     \SCO\SUL335TD.Z

   Installing driver procedure on SCO UNIX :
   -----------------------------------------
      Before you start with the installation  process,  make sure that the
      SCO UNIX system is properly installed. Similarly,your adapter should
      also be properly installed in your machine.

      1. Login as root user. (On maintenance mode)

      2. Copy the file SUL335TD.Z to SUL335T.dd.Z on a SCO Unix machine.
         The number in parentheses near the file's name (above) is the
         checksum for the file. To verify, use:
            # doscp A:/sco/SUL335TD.Z /SUL335T.dd.Z
            # sum -r SUL335T.dd.Z
         and compare the results.
         Uncompress SUL335T.dd.Z to SUL335T.dd, using:
            # uncompress SUL335T.dd
         Copy the file to a diskette. To create a 3.5" floppy in drive 0, use:
            # dd if=SUL335T.dd of=/dev/rfd0135ds18
         Mark the diskette:
         ALL8832 PCI Fast Ethernet Controller LLI driver Rel.03.35

       3. Run custom. From the menu select:
          Custom -> Install -> A New Product -> Entire Product
          Put the distribution diskette in the drive and select continue.
          When prompted for distribution floppy 1, just press enter.
          When custom has completed, remove the diskette and quit custom.

       4. Use netconfig utility, avaiable options :
              # netconfig

              The screen will display the following messages, and Select
              item (1) to Add a chain  :

             1) Add a chain
             2) Remove a chain
             3) Reconfigure an element in a chain
             4) Quit

      5. After the above option completed, the screen display next option
         messages :

         Select item (4) : sco_tcp   SCO TCP/IP for UNIX

      6. When the user completed the above option, then various adapter
         drivers in SCO UNIX occur and select "DEC PCI Family Fast Ethernet
         Driver board 0" item.

      7. Add chain sco_tcp -> d21x3 (y/n),   TYPE 'y'

      8. Enter the internet Address of this interface ,
         for example : 192.9.9.1

      9. Enter the netmask for this interface (default 255.255.255.0).

      10. Does the interface use a broadcast address of all 1's (y/n),
          default : y

      11. Enter the boardcast address for this interface,
          default : xxx.xx.x.255             press ENTER

      12. Are these values correct ? (y/n)   TYPE 'y'

      13. Pseudo ttys are currently configured, do you want to:

             1) Add Pseudo ttys
             2) Remove Pseudo ttys
             Select an option or enter q to quit [q]   TYPE 'q'

      14. Available options:

             1) Add a chain
             2) Remove a chain
             3) Reconfigure a element in a chain
             q. Quit

          Select option: q

      15. Do you want to relink to kernel now ?               y

      16. Do you want this kernel to boot by default (y/n)    y

      17. Do you want the kernel environment rebuilt (y/n)    y

      18. Reboot unix
              # shutdown -g0

   Driver Parameters :
   -------------------
      The space.c file contains the different parameters that can be modified.
      They can be divided into several groups:
      1. Port parameters. These include:
            XXX_HW_ACCESSES
            XXX_DC2114X_SERIAL_MODE
            XXX_BUS_ARBITRATION
            XXX_BURST_LENGTH
            XXX_CACHE_ALIGNMENT
            XXX_PASS_BAD_FRAMES
            XXX_BACKOFF_CNTR
            XXX_10MB_THRESHOLD
            XXX_100MB_THRESHOLD
            XXX_PARITY_ERROR_RESPONSE
            XXX_LATENCY_TIMER
            XXX_CRC_CALC
            XXX_DC2114X_GPR_CTRL
            XXX_DC2114X_GPR_DATA
            XXX_TURBO
            XXX_SNOOZE
            XXX_MWI,          /* Enable/Disable MWI extended PCI command */
            XXX_MRM,          /* Enable/Disable MRM extended PCI command */
            XXX_MRL           /* Enable/Disable MRL extended PCI command */
      2. Driver tuning parameters:
            XXX_RX_BUFS_TO_POST
            XXX_RX_PKTS_QUEUED_THRESH_HI
            XXX_RX_PKTS_QUEUED_THRESH_LO
            XXX_MAX_USRS
      3. Driver diagnostics control:
            XXX_DEBUG
      The meaning of each is explained in detail in the space.c file,
      including allowed values for each parameter. The values in space.c
      apply to ALL the installed boards. Space.c is NOT the place to modify
      the board's slot number line. This must be modified in netconfig, by
      running the reconfiguration script.

   Errors and trouble shooting
   -----------------------------------------
      1. Mismatch between PCI configuration and netconfig/space.c:
         In order for the adapter to work correctly, the same values that are
         used during the PCI configuration (e.g CFLT) must be used in the
         space.c file. Mismatches may cause the adapter to malfunction, or
         even hang the system.
         Currently, the PCI setup takes precedence except for the value for
         the latency timer, which is taken from the space.c file.

      2. Wrong HW access method for PCI configuration space:
         If the XXX_HW_ACCESSES parameter in space.c is set to a value not
         supported by your system there will be problems at boot time. Set
         this parameter to a value that is supported by your system.
         By default, the parameter is set so the driver uses 32-bit protected
         mode PCI BIOS calls.

      3. Driver binds to wrong PCI board (network):
         When multiple PCI boards are installed, the chains are bound to the
         adapters in the order that the adapters are found on the PCI bus by
         the PCI BIOS. Thus, d21x0 will bind to the first adapter found by
         the PCI BIOS, d21x1 to the second etc. Removing or adding boards
         without changing the configuration in netconfig can cause a shift in
         the order that chains are bound. Also, mis-identifying the order in
         which the adapters are found by the BIOS can cause wrong bindings.
         This is especially true when usi