SOLARIS8.TXT Driver File Contents (ARB1663.zip)

****************************************************************************
                                Solaris8.txt
*****************************************************************************

Installation Guide for the LSI Logic SDMS Solaris Driver, Version 4.07.00

This file describes the features and use of the LSI Logic SDMS Device Driver for
the Solaris 8 Operating system. It is divided into the following sections:

Introduction
     Features
     LSI Logic Devices Supported
     Description
     Creating the SYMHISL Driver Update Diskette

How to Install Your SDMS Solaris Driver
     Installing the Driver During Solaris Installation
     Updating Solaris with the driver
     Troubleshooting

******************************* Introduction ********************************

Solaris 8 for x86 is an operating system designed to run on single or multiple
processors. It provides a command line interface environment and a graphical 
environment that incorporates many high level features. Refer to the Sun 
Microsystems Web site, www.sun.com/docs for Solaris 8 X86 documentation for 
further details.
 
The SDMS driver, symhisl, allows the Solaris operating system to interface with
SCSI devices connected to these LSI Logic SCSI controller chips: LSI53C895A,
LSI53C896, LSI53C1010 and LSI53C1000. A list of features associated with this
driver along with its description is described below. The procedures to install
the symhisl driver during a new installation of Solaris 8 or to update the
driver with an existing installation of Solaris 8 are also included.

Note: Current Solaris 8 drivers can be downloaded from the LSI Logic web
      site at http://www.lsilogic.com. After you are connected to this
      web site, place your cursor on the Get Drivers option in the menu
      bar. Click on the Drivers selection. Choose the Solaris operating
      system for SCSI and click on the Go button. Follow the instructions
      on subsequent screens to download the driver.

*******************************************************************************
IMPORTANT: This software has been tested on Solaris 8 FCS. This software will not
run on Solaris 7. LSI Logic assumes no responsibility or liability when a user 
attempts to use this software with older versions of Solaris that LSI Logic has 
not tested. 
*******************************************************************************


*  *  *  *  *  *  *  *  *  *  *  *  * Features *  *  *  *  *  *  *  *  *  *  *  

The symhisl driver supports these features:

o Synchronous negotiation (including Fast SCSI/Ultra SCSI/Ultra2 SCSI)
o Ultra160 Data Transfers (for LSI53C1010 and LSI53C1000)
o Ultra160 Domain Validation
o Ultra160 Double Transition (DT) data transmissions
o Multiple host adapters
o Disconnect/Reselect
o Multiple and non-contiguous Logical Unit Number (LUN) support
o Scatter/Gather
o Wide devices
o Tagged command queuing
o Multiprocessors
o Hot swapping of SCSI devices

*  *  *  *  *  *  *  *  LSI Logic Devices Supported *  *  *  *  *  *  *  *  * 

All LSI Logic devices and host adapters have undergone a name change. They
have transitioned from a SYM prefix to an LSI prefix. No name changes have
occurred for the SDMS Solaris driver.

The symhisl driver is a Solaris 8 32-bit driver and supports these LSI Logic
devices and their associated host adapters:

o  LSI53C895A (LSI8953U)
o  LSI53C896  (LSI22910, LSI21002, LSI22902)
o  LSI53C1000 (LSI8955U*)
o  LSI53C1010 (LSI22915, LSI22903, LSI21040, LSI8955U**)


* 66 MHz
**33 MHz

*  *  *  *  *  *  *  *  *  *  *  *  * Description *  *  *  *  *  *  *  *  *  * 

The SDMS symhisl driver is designed to Sun Microsystems SCSA specifications
for device drivers. This driver allows connection of SCSI devices including 
disk drives, CD-ROMS, and tape drives for PCI-based machines. To support a new
SCSI device, the Solaris 8 x86 architecture requires that the device complies 
to the SCSI standard. 


************************Installing the SDMS Solaris 8 Driver********************* 

This section provides installation instructions for new and existing systems. 
The SYMHISL Driver Update diskette can be used in one of two ways:

1. To use new drivers to install or upgrade the Solaris 8 operating environment
   on a machine with new hardware.
   
   -OR-

2. To add new drivers to support new hardware on an already installed and
   booted system.


*  *  *  *  *  *  *  New System Installation for Solaris *  *  *  *  *  *  * 

You have the option of installing from a bootable Solaris 8 CD-ROM labelled
Software 1 of 2 or a Solaris 8 Diskette. These installation steps refer to the 
Solaris Device Configuration Assistant Diskette as the boot diskette. If
installing from the Solaris 8 bootable CD-ROM, ignore the information about
reinserting and/or removing the Solaris Device Configuration Assistant Diskette.

The new system installation instructions follow:


To use the driver on the SYMHISL Driver Update diskette to install Solaris 8 
(Intel Platform Edition) on a machine, follow the steps below. Use the 
appropriate Solaris Device Configuration Assistant Diskette appropriate for
your release of Solaris 8 as the boot diskette.

1.  Insert the Solaris Device Configuration Assistant Diskette into your 
    machine's diskette drive. Also insert the Solaris Installation CD-ROM;
    or for network installation, verify with your system administrator that
    the Solaris Network Installation image is available on your network.

2.  Turn on your machine.

3.  When the Solaris Device Configuration Assistant screen appears, choose
    F4_Add Driver. The Bus Enumeration screen appears.

    Then, the Install Supplemental Drivers screen appears.

4.  Remove the Solaris Device Configuration Assistant Diskette from the
    diskette drive and insert the first Solaris Driver ITU diskette you want.

5.  Press F2_Continue.

6.  The Loading Supplemental Driver Software screen appears, along with a
    progress bar that shows the percentage of drivers that have been extracted
    from the diskette. Drivers are read into memory and survive long enough 
    for the system to successfully boot to its installation program. When all
    the new drivers on the diskette have been processed, the Continue
    Supplemental Driver Installation screen appears.

7.  Remove the Solaris Driver ITU diskette from the diskette drive and insert 
    the next Solaris Driver ITU diskette you want, if any for other devices.
    If so, continue with Step 8; otherwise, proceed to step 10.

8.  Press F2_Continue.

    The Loading Driver Update Software screen appears, along with a progress 
    bar that shows the percentage of drivers that have been extracted from the
    diskette. Drivers are read into memory and survive long enough for the 
    system to successfully boot to its installation program. When all the new 
    drivers on the diskette have been processed, the Continue Supplemental
    Driver Installation screen appears.

9.  Repeat Step 4 through Step 8 until all the Solaris Driver ITU
    diskettes you want are installed.

10. When all the drivers are processed, remove the Solaris Driver ITU diskette 
    from the diskette drive and reinsert the Solaris Device Configuration
    Assistant Diskette. Press F4 when done adding supplemental drivers.

    After pressing F4, the Identified Device Drivers screen appears with a list
    of all device drivers. For example, you would see at least symhisl-Device
    Driver.


    IMPORTANT: Do not remove the Solaris Device Configuration Assistant
               Diskette from the diskette drive until you see the following
               message displayed in a dialog box:

               "If you want to bypass the device configuration and
               boot screens when the system reboots, eject the
               Device Configuration Assistant/Boot diskette now."

               This message actually appears during Step 16.

11. Press F2_Continue.

    The Solaris Device Configuration Assistant screen appears.

12. Press F2_Continue.

    The Bus Enumeration screen appears.

    The Scanning Devices screen appears. System devices are scanned. When
    scanning is complete, the Identified Devices screen appears.

13. Press F2_Continue.

    The message "Loading driver ..." appears followed by messages about the
    drivers that are required to boot your system. After a few seconds, the
    Boot Solaris screen appears.

14. At the Boot Solaris screen, select the device controller attached to the
    device that contains your install medium.

15. Press F2_Continue.

    Drivers for the device controller that you selected are displayed. Your
    system boots to run the install program. The install program starts and 
    your machine begins booting the complete Solaris operating environment.

16. Proceed to configure your system when prompted to do so. After configuring
    your system, click on the Begin Installation button.

    The message indicated above appears now:

               "If you want to bypass the device configuration and
               boot screens when the system reboots, eject the
               Device Configuration Assistant/Boot diskette now."

   
17. Remove the Solaris Device Configuration Assistant Diskette.

    Some time later, the following messages appear and prompt you to
    insert each of the Solaris Driver ITU diskette(s) required to
    install into your machine:

    Installing unbundled device driver support
    Extracting driver list from tree..
    <ITU diskette name> driver-name...

    Please insert the Driver Update diskette labeled <ITU diskette name>
    Press <ENTER> when ready.

18. Reinsert the SYMHISL Driver ITU diskette that you inserted earlier into the
    diskette drive.

19. Press Enter.

    Packages and/or patches that contain the new drivers are installed from
    the diskette onto your machine. Messages about each installation appear
    accordingly.

    When the prompt asking:

    Do you want to create a new instance of this package [y, n, ?, q] 
    Type y for YES and press Enter.

20. Remove the Driver ITU diskette from the diskette drive if drivers on other
    Solaris Driver ITU diskettes are required. The system will prompt you with
    this message:    

   "If you have additional Update diskettes to install (such as video), please 
    insert diskette now."

    "Additional Update Diskettes?" 

21. Type y for Yess if applicable.

    Repeat this process until all drivers you need are installed.

    When you type n for No and press Enter, this message appears:

    "Installation of <SYMhisl.2> was successful." 

    The system automatically reboots your machine.

When the Solaris operating environment is finished booting and running, the
new devices whose drivers that you installed are available for use. To verify
the version number for the Solaris 8 symhisl driver, type at the prompt:

    # modinfo | grep sym

The system will display the version number.


*  *  *  *  *  * Existing System Installation for Solaris *  *  *  *  *  *  * 

Before adding new or updated drivers, the newly supported hardware devices
should be installed and configured according to the instructions in the
corresponding Device Reference Page, if any. See the Device Reference Manual
for Solaris (Intel Platform Edition).

When the Solaris Intel Platform Edition software is already installed, the
simplest way to add new or updated drivers is to install the Driver ITU
diskettes as patches on your system. For more information about managing
diskettes and drives, see the System Administration Guide.

To add new or updated drivers, follow these steps:

1.  Go to the root directory.

2.  To see if the Volume Management software is running on the machine that
    you are updating, type at the command prompt:

    ps -ef | grep vold

3.  To temporarily stop Volume Management if it is running, type this command
    at the system prompt:

    # /etc/init.d/volmgt stop

4.  Insert the Solaris Driver ITU diskette into the diskette drive.

5.  Mount the Solaris Driver ITU diskette at the /mnt mount point:

    # mount -F pcfs /dev/diskette /mnt

    Note: You must mount the Solaris Driver ITU diskette at this point
          in the file structure to update your system successfully.

6.  Execute the install script on the diskette:

    # /mnt/DU/sol_28/i86pc/Tools/install.sh -i

    The install.sh script searches for all new or updated drivers on the
    diskette. When a new or updated driver is found, this prompt appears:

    Unconditionally installing ITUs <ITU driver names>
    (Some messages appear stating that your installing).
    Then, the message prompts:

    "Do you want to create a new instance of this package [y, n, ?, q]"

7.  Type n for no.

    Then, the message prompts:
    "Do you want to overwrite this installed instance [y, n, ?, q]" 

8.  Type y for yes to overwrite the old driver.

9.  When the installation has completed, and the install.sh script exits, 
    unmount the diskette by typing at the command prompt:

    # cd /
    # umount /mnt

10. Remove the Solaris Driver ITU diskette from the diskette drive.

11. Reboot your machine by typing at the command prompt:

    # touch /reconfigure
    # reboot

12. If you have not already done so, turn off your system, add the new 
    hardware, and turn on your system again.

13. At the << Current Boot Parameters >> prompt, type:

    b -r
  
    to force reconfiguration of the machine.

When the Solaris 8 operating environment is finished booting and running, the
new devices whose drivers that you installed are available for use. To verify
the version number of the Solaris 8 symhisl driver, type at the prompt:

    # modinfo | grep sym

The system will display the version number.

   
***********************************Troubleshooting*****************************

Some informational or potential error messages may be preceded by a warning
message and displayed by the operating system. In the listed message
descriptions, the SYMHISL<n> signifies that <n> can be replaced by a number
assigned to it by the operating system. That value helps to identify the
SCSI bus that is reporting the error.  <s> and <x> are placeholders for strings
and numbers that the system will display.

SYMHISL<n>: This hardware not supported by this driver

     SYMHISL has been told to control a LSI53C895A, LSI53C896, LSI53C1010 or
     LSI53C1000 controller, which is made by a manufacturer other than
     LSI Logic. This adapter requires a special driver provided by that
     manufacturer. Please contact the manufacturer for assistance.

SYMHISL<n>: Failed to map device registers

     SYMHISL was unable to access the hardware registers necessary for
     operation. The operating system did not properly configure the PCI
     device.

SYMHISL<n>: NVS error, failed to restore value of 'reg' property

     SYMHISL was able to access the resources needed to determine NVS 
     configuration but was not able to return the system to its prior state. 
     Further configuration errors may occur.

SYMHISL<n>: NVS error, failed to map system memory
            NVS data can't be used

SYMHISL<n>: NVS error, failed to update 'reg' property
            NVS data can't be used

SYMHISL<n>: NVS error, failed to allocate memory
            NVS data can't be used
   
SYMHISL<n>: NVS error, unable to find 'reg' property
            NVS data can't be used
  
     For each of the above errors, SYMHISL was not able to access NVS
     configuration data to see if it exists. On some systems, this will not
     be a problem. On other systems, however, NVS data contains the 
     configuration information for this adapter and SYMHISL is not able to 
     use that configuration. This may cause the user to manually configure 
     the driver using the symhisl.conf configuration file. Please refer to the 
     man page driver.conf(4), which is the standard reference on how to edit
     the symhisl.conf file. The instructions for editing symhisl.conf can also
     be found in the path /kernel/drv/symhisl.conf.

SYMHISL<n>: Hardware not properly enabled by system, cmd=xxxxh

     The system has not properly enabled the configuration resources that 
     SYMHISL needs in order to use this hardware. The cmd=xxxxh value needs to
     be reported to technical support.

SYMHISL<n>: Unsupported 64-bit register address
            Please load 64-bit version of kernel and driver

     This version of the SYMHISL driver does not support physical addresses 
     using 64-bit values. Contact LSI Logic Technical Support at 719-533-7230
     to determine if a new driver is available to support 64-bit version. 

SYMHISL<n>: The host adapter id in the .conf file is being ignored 
            because the SCSI BIOS Configuration Utility will override it.

     The symhisl.conf file has a line (scsi-initiator-id=x) which is used to
     change the host adapter SCSI ID. That line is being ignored because the 
     SCSI BIOS Configuration Utility has set the SCSI ID. Please use the SCSI
     BIOS Configuration Utility to change the SCSI ID.

SYMHISL<n>: Ignored invalid scsi-initiator-id value = <x>

     The symhisl.conf file has an invalid scsi-initiator-id value as displayed 
     in the error message. The allowable values are in the range 0..15.

SYMHISL<n>: <s> property value is too large
            Using maximum value of <x>

     A property value in the symhisl.conf value is greater than the maximum
     allowed value. The driver will use the value <x> instead.

SYMHISL<n>: <s> property value is too small
            Using default value of <x>

     A property value in the symhisl.conf value is less than the minimum
     allowed value. The driver will use the value <x> instead.

SYMHISL<n>: Could not allocate memory to read configuration data

     The driver was unable to allocate memory required to process the 
     configuration data. This means that the configuration was not properly 
     determined. To fix this you may need to manually configure the driver 
     using the symhisl.conf file.

SYMHISL<n>: Failure reading NVM configuration data

     The driver was unable to read the configuration data supplied by the SCSI
     BIOS Configuration Utility. This means that the configuration was not
     properly determined. To fix this you may need to manually configure the
     driver using the symhisl.conf file.

SYMHISL<n>: Failure reading NVM manufacturing data

     The driver was unable to read the configuration data supplied by the 
     manufacturer. This means that the adapter configuration may be incorrect
     and unknown errors may occur. Please contact your manufacturer for a
     replacement adapter.

SYMHISL<n>: The boot ROM configuration utility has SCAM enabled 
	    but this driver is not capable of SCAM. Please disable SCAM
	    in the boot ROM.

     Some older versions of the SDMS Boot ROM are capable of using the SCAM
     protocol to assign SCSI IDs. The SYMHISL driver is not capable of using 
     SCAM. In order to properly configure your system, please disable SCAM 
     using the SCSI BIOS Configuration Utility.

SYMHISL<n>: Configuration data is corrupt and will be ignored

     The configuration data provided by the SCSI BIOS Configuration Utility
     has been determined to be corrupted. Run the SCSI BIOS Configuration
     Utility to correct this error.

SYMHISL<n>: Unknown synchronous value in NVM data = <x>

     The SYMHISL driver needs to be updated to understand this new synchronous
     configuration data value. Until the driver is updated, synchronous mode 
     will be disabled.

SYMHISL<n>: Unknown width value in NVM data = <x>

     The SYMHISL driver needs to be updated to understand this new wide
     configuration data value. Until the driver is updated, wide mode will
     be disabled.

SYMHISL<n>: Unable to make reset notification callbacks

     The SYMHISL was unable to notify the target device driver of a SCSI bus
     reset. The target driver may start to malfunction because of this.

SYMHISL<n>: Disabling queue tags for target ID <x>

     The SYMHISL driver has determined that the specified target is no longer 
     responding to queue tagged I/O in a proper manner and has disabled queue 
     tags for that device. This usually means that the specified device does 
     not support queue tags. To disable this message, disable queue tags for 
     the given device using the SCSI BIOS Configuration Utility.

SYMHISL<n>: Device (ID=<x>, LUN=<x>) not supported

     A Solaris target driver attempted to initialize a device whose SCSI target
     ID was out of the support range or whose LUN was not zero. This warning is
     most likely triggered by illegal entries in the target driver's conf file.

SYMHISL<n>: ddi_dma_sync() failed for data buffer
            Data corruption may occur
SYMHISL<n>: ddi_dma_sync() failed for I/O data at <xxxxxxxx>
            Data corruption may occur
SYMHISL<n>: ddi_dma_sync() failed for Adapter data
            Data corruption may occur

     A call to the operating system's ddi_sync_dma function failed.  As a
     result, the system data caches may not be properly synchronized with
     system main memory. This may result in data corruption or failure of
     the symhisl driver to function properly.

SYMHISL<n>: ddi_dma_numwin() failed
SYMHISL<n>: ddi_dma_getwin() failed
SYMHISL<n>: ddi_dma_alloc_handle: <xx>h unknown/impossible
SYMHISL<n>: ddi_dma_buf_bind_handle: DDI_DMA_INUSE impossible
SYMHISL<n>: ddi_dma_buf_bind_handle: <xx>h unknown/impossible
SYMHISL<n>: ddi_dma_unbind_handle: failed

     The operating system failed to respond to the named routine in a known
     manner. This is a fatal error that is not recoverable. Please report this
     error to LSI Logic Technical Support by calling 719-533-7230.

SYMHISL<n>: Device in a slave-only slot and is unusable
SYMHISL<n>: Hi-level interrupts not supported.

     The adapter is in a slot that cannot be used with this driver. Please 
     try moving the adapter to a different PCI slot.

SYMHISL<n>: Failed to attach. This adapter will not be installed.

     Because of the previous error, this adapter could not be "attached" to the
     I/O subsystem and will not be accessible. See the previous error message 
     and solve that problem. 

SYMHISL<n>: Failed to allocate memory

     The SYMHISL driver was unable to allocate the memory needed during
     initialization. You may have run out of available memory.

SYMHISL<n>: Unbind failed!

     The driver had a problem when attempting to unload itself.
     This is a fatal error.

SYMHISL<n>: Unable to obtain soft state structure

     The SYMHISL driver was unable to initialize a required data structure and
     therefore did not load. Please call technical support at 719-533-7230.

SYMHISL<n>: Failed to attach interrupt handler

     The SYMHISL driver was unable to initialize the interrupt handler as 
     required. Please call technical support at 719-533-7230.

SYMHISL<n>: The adapter is malfunctioning
SYMHISL<n>: The adapter is either malfunctioning, of an unknown type,
            or a revision that is not supported

     The driver is not able to communicate with the hardware. You may need to
     update your driver or your hardware.

SYMHISL<n>: Failed to create DMI minor node

     The SYMHISL driver was unable to create a device node for the driver's
     DMI interface. If you are not using the DMI then you may safely ignore
     this message.

SYMHISL<n>: Could not attach to the SCSI subsystem

     The SYMHISL driver was unable to communicate with the Solaris 8 SCSA
     subsystem. You may need to update your driver.

Download Driver Pack

How To Update Drivers Manually

After your driver has been downloaded, follow these simple steps to install it.

  • Expand the archive file (if the download file is in zip or rar format).

  • If the expanded file has an .exe extension, double click it and follow the installation instructions.

  • Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.

  • Find the device and model you want to update in the device list.

  • Double-click on it to open the Properties dialog box.

  • From the Properties dialog box, select the Driver tab.

  • Click the Update Driver button, then follow the instructions.

Very important: You must reboot your system to ensure that any driver updates have taken effect.

For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.

server: web2, load: 0.61