*****************************************************************************
WIN2000.TXT
*****************************************************************************
Installation Guide for the LSI Logic FC Driver: SYMMPI.SYS V1.03.00
This file describes the features and use of the LSI Logic FC device
drivers for the Windows 2000 operating system environment. It is divided
into the following sections:
Introduction for Windows 2000
Features
LSI Logic Devices Supported
Description
Installing the Driver(s)
New System Installation
Existing System Installation
Performance Tuning
Large Block Size Support
Maximum Number of Concurrent I/Os
Miniport Driver Configuration Options
Troubleshooting
.........................................................................
1.0 Introduction for Windows 2000
Windows 2000 is an operating system designed to run on Intel-architecture
processors using current technology. It provides a graphical user interface
environment incorporating many high-level features (refer to the Microsoft
Windows 2000 documentation for details).
An I/O manager handles I/O requests in Windows 2000. To address a SCSI
peripheral, the I/O manager goes through the appropriate drivers. Windows 2000
provides class drivers for hard disk, floptical, CD-ROM, printer, and scanner
peripherals. Other class drivers, provided by peripheral manufacturers, may be
added to support new devices. Tape device support is built into the operating
system itself and does not require a class driver.
Microsoft provides the port driver and LSI Logic provides the miniport driver,
called SYMMPI.SYS. This driver completes the path to the LSI Logic Fibre
Channel (FC) controller with an optional FC BIOS.
LSI Logic uses the same filenames for their drivers for different Windows
operating systems. The driver files are packaged either in separate
subdirectories based on the Windows operating system or on different flex
disks. To determine the driver file for Windows 2000, note that the
filename ends with .SYS. For example, SYMMPI.SYS. (The same is true for
Windows NT 4.0.)
To determine the operating system version, go into Windows Explorer, display
the driver file, right click on the filename, click on Properties, and click
on the Version tab. Finally, click on the Internal Filename in the lower
section. For Windows 2000, the filename appears as filename (Win2K).
The next sections describe these drivers and their installation.
.........................................................................
1.1 Features
The SYMMPI.SYS miniport driver supports these features:
o Supports 1Gbaud Fibre Channel transfers (for LSIFC909)
o Supports 2Gbaud Fibre Channel transfers (for LSIFC929 and LSIFC919)
o Support LSI Logic MPT common software interface
o Supports multiple host adapters
o Supports multiple Logical Unit Numbers (LUNs)
o Supports Scatter-Gather
o Supports SCSI pass-through functionality
o Supports disk array configurations with no LUN 0
o Supports disk array configurations with non-contiguous LUNs
o Auto request sense
o Maximum block size support: 1 MB
.........................................................................
1.2 LSI Logic Devices Supported
The SYMMPI.SYS driver is named "LSI Logic PCI SCSI/FC MPI Miniport Driver" for
driver installation. It supports the following devices and their associated
host adapters:
o LSIFC909 (LSI40909G, LSI40909G-S)
o LSIFC919 (LSI40919O, LSI40919LO, LSI40919H, LSI40919LH)
o LSIFC929 (LSI44929O, LSI44929LO, LSI44929H, LSI44929LH, 7004G2-LC)
.........................................................................
1.3 Description
The SYMMPI.SYS driver meets the Microsoft specification for miniport drivers.
This driver allows connection of Fibre Channel devices including disk drives,
CD-ROMs, and tape drives for PCI-based machines. To support a different Fibre
Channel device type, the Windows 2000 architecture requires that a class driver
for that type of device be present (usually supplied by Microsoft, or possibly
by the peripheral manufacturer). No changes to SYMMPI.SYS are required.
The driver is only supported under Windows NT 4.0 and Windows 2000.
A Windows application passes SCSI commands directly to the Fibre Channel
Protocol (FCP) devices by using the SCSI pass-through facility. This facility
allows applications to directly control and access devices by filling in a
data structure and calling into the port or class driver. Refer to the
Microsoft Windows 2000 documentation for more details.
............................................................................
2.0 Installing the SYMMPI.SYS Driver
This procedure installs the SYMMPI.SYS driver onto a new or existing
Windows 2000 system. Depending upon the media used to distribute LSI Logic
drivers (web or CD-ROM), you will create a driver diskette.
Copy the files listed below to the root directory of a clean diskette. Label
this diskette "Windows 2000 Driver Diskette". You will use this diskette
during the installation process.
\txtsetup.oem
\symmpi.sys
\symmpi.tag
\oemsetup.inf
............................................................................
2.1 New System Installation
This procedure installs the SYMMPI.SYS driver onto a Windows 2000 system.
Use this procedure when installing Windows 2000 onto an unused drive.
Windows 2000 automatically adds the driver to the registry and copies the
driver to the appropriate directory.
The method for installing Windows 2000 on a new system involves using a CD-ROM.
Refer to the Microsoft document for installing Windows 2000 using boot floppy
diskettes.
2.2.1 CD-ROM Installation
1. Start the Windows 2000 installation by booting from the Windows 2000 CD-ROM:
The system BIOS must support booting from a CD-ROM. BIOS settings may need
to be changed to allow CD-ROM booting.
2. Press the F6 key to install the SYMMPI.SYS driver when the screen displays
"Windows 2000 Setup".
This must be done or else these new driver will not be recognized. If only
the SYMMPI.SYS driver is needed, no user action is required as they will be
loaded from the CD-ROM automatically.
Note: Be sure to press the F6 key as any driver loaded later in the
installation process is not recognized by the Windows setup.
If F6 is not pressed, all devices controlled by the drivers are
not available during Windows 2000 setup.
3. Choose S to specify an additional device when the screen displays "Setup
could not determine the type of one or more mass storage devices...".
NOTE: If this screen is not displayed as the first user input, then
pressing the F6 key was not seen by the setup program. Reboot the
system and try again.
The system prompts for the manufacturer-supplied hardware support disk.
4. Insert the appropriate driver diskette containing the Windows 2000
driver required to support your LSI Logic adapter(s) and press Enter.
NOTE: Current Windows 2000 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 Windows 2000 operating
system for Fibre Channel and click on the Go button. Follow the
instructions on subsequent screens to download the drivers.
5. Press Enter to proceed.
Return to the Windows 2000 Setup screen.
6. Press Enter to proceed.
The message about setup loading files appears.
7. Follow the Microsoft Windows 2000 installation procedure at this point.
............................................................................
2.2 Existing System Installation
This procedure installs or upgrades the SYMMPI.SYS drivers onto an existing
Windows 2000 system.
NOTE: When a LSI Logic FC adapter is added to an existing system installation,
the new adapter is automatically detected at the next reboot. When the
Device Driver Wizard appears at boot, click on the Next button and
continue at step 8 below.
1. Boot Windows 2000 and log on as Administrator.
2. Right-click on My Computer
3. Click on the Properties selection.
4. Click on the Hardware tab, and then the Device Manager button.
5. Click the "+" to the left of the SCSI and RAID controllers line. Find the
adapter desired for the driver upgrade and double-click the entry. Click
on the Driver tab.
6. Information on the currently installed driver is displayed, and additional
driver details can be viewed by clicking the "Driver Details" button.
7. Click on the "Update Driver" button to update the existing driver. The
Upgrade Device Driver Wizard begins.
8. Click on the Next button.
9. Click on the "Display a list of known drivers..." button to select it,
then click on the Next button.
10. Click on the "Have Disk" button and type the path to the driver, or click
on the Browse button. After the path to the driver has been established,
click the OK button.
11. Select the driver from the list and click on the Next button.
12. Click on the Next button again to start the driver update.
In some cases, a message will display saying that this driver is not
digitally signed. This message informs you that a nonsigned driver is
being installed.
Note: Drivers are digitally signed by the Microsoft Windows Hardware
Quality Lab (WHQL). Due to the time lag between the general
customer release by LSI of Windows drivers and the completion of WHQL
testing, some drivers distributed with adapters or downloaded from
the www.lsilogic.com web site may not be digitally signed.
13. Click No to cancel the installation if a nonsigned driver is not desired.
or
Click Yes to continue the installation.
The system will load the driver from the Windows 2000 driver diskette.
A message box may display indicating that the target (existing) driver is
newer than the source (upgrade) driver.
14. Click No to cancel the driver upgrade at this point.
or
Click Yes to continue the installation.
The system copies the driver to the system disk. For any adapter other
than the boot adapter, the updated driver will become active immediately.
For the boot adapter, a message box displays indicating that you must
reboot your system for the new driver to take effect.
15. Click on the Finish button to complete the driver upgrade.
............................................................................
2.3 Performance Tuning for Windows 2000
Windows 2000 has registry entries that can be used to tune the performance
of SCSI I/O for certain configurations. The tunable parameters are large
transfer block size support and a guaranteed number of concurrent I/Os for a
particular SCSI bus.
............................................................................
2.3.1 Large Block Size Support
The SYMMPI.SYS drivers can support up to a 1 MB transfer size in Windows 2000;
however, the default Windows 2000 transfer size is 64K. To enable better
performance, the driver installation process adds a registry entry to enable
a maximum 256K transfer size. Also, the file mpi_256K.reg can be used to set
or re-enable a 256K maximum, but it can be edited to set other desired maximum
transfer sizes. There are two methods to add this registry setting.
1. Locate the mpi_256K.reg data file (supplied with the driver files) using
Windows Explorer and double-click on the file.
-OR-
2. Type at the command prompt:
regedit mpi_256K.reg
This inserts an entry in the registry to enable 256K block size support.
Editing the mpi_256K.reg can set any maximum block size between 64K and
1 MB (-8 KB). The formula to calculate the proper value for MaximumSGList is:
MaximumSGList = (Maximum Block Size)/4K +1
For 256K: 256K/4K = 64, add 1 for 65 (decimal) or 0x41(hexadecimal). The
maximum value allowed for MaximumSGLIst is 255 or 0xFF. This denotes an
absolute maximum transfer size of 1040384, which is 8K less than 1 MB
(1040384/4K = 0xFE, add 1 for 0xFF or 255). Be sure to read the information
in the mpi_256K.reg data file before editing it.
The system must be rebooted for the new registry setting to be effective.
To reset the maximum block size to the default of 64K, follow the instructions
above, except use mpidfblk.reg as the data file.
............................................................................
2.3.2 Maximum Number of Concurrent I/Os (Guaranteed)
Windows 2000 guarantees a maximum of 32 concurrent I/Os active on a
particular SCSI bus. However, due to the method of memory allocation, the
actual limit of concurrent I/Os can vary greatly between various drivers or
versions of drivers. This can have a huge impact on performance benchmarking
between different driver versions or adapter vendors. In effect, one adapter
may actually be able to have 70 or 80 I/Os outstanding, while another adapter
could only have 32. This can also affect systems with high performance storage
subsystems, such as disk arrays.
In order to enable better performance, the driver installation process adds a
registry entry to supprt 128 concurrent I/Os. If a different maximum value is
desired, the file mpi100io.reg can be used to add a registry entry to guarantee
the desired number of concurrent I/Os.
There are two methods to add this registry setting. One is to locate the
mpi100io.reg data file (supplied with the driver files) using Windows Explorer
and double click on the file. The other method is to type at the command
prompt:
regedit mpi100io.reg
This inserts an entry in the registry to guarantee a maximum of 100
concurrent I/Os per adapter.
If a maximum other than 100 is desired, the mpi100io.reg can be edited;
however, setting this value to a high number uses increasing amounts of
non-paged pool memory, a critical NT resource. High values for this setting
can degrade system performance. Be sure to read the information in the
mpi100io.reg data file before editing it.
The system must be rebooted for the new registry setting to be effective.
To reset the guaranteed number of concurrent I/Os to the default of 32,
follow the instructions above, except use mpidefio.reg as the data file.
............................................................................
2.3.3 Miniport Driver Configuration Options
The SYMMPI driver is configured by default to provide optimum performance
in most standard systems. Some non-standard systems may require some fine
tuning to obtain peak system memory utilization and performance. After
installation, if less than advertised functionality and performance is
observed on any platform, please contact LSI Logic support. Go to the LSI Logic
Technical Support Home Page, which is located at:
http://www.lsilogic.com/support/index.html
and call the listed number for assistance.
LSI can provide additional registry settings if required, to customize the
driver for specific systems and applications.
............................................................................
3.0 Troubleshooting
The SYMMPI.SYS driver will log error messages to the system error log. For
these errors, the system errorlog EventID will be 11, and the specific error
code values will be displayed at offset 0x10. Data should be displayed in
words. The error codes that are followed by an asterisk are extended error
codes, only logged if extended error logging is enabled.
The following error codes all have a value of 0x00000006 at address 0x34 in
the error log details.
Error Code Description
.......... .........................................
0x00000001 Could not read the PCI BARs correctly
0x00000002 Could not read the PCI IO address space correctly
0x00000003 Device would not come to the READY state
0x00000004 System did not provide non-cached memory to the driver
0x00000005 Device did not restart after a fatal error
0x00000006 Device would not transition to the Operational state.
0x00000007 Device would not transition from READY state within the SCSI
Reset function
0x00000008 Device would not transition from RESET state within the SCSI
Reset function
0x00000009 Device would not transition from FAILED state within the SCSI
Reset function
0x0000000A Device would not transition to OPERATIONAL after running out
of resources
0x0000000B Device would not transition to READY after kickstart
0x0000000C Driver wanted to reset the device but the NoBoardReset flag
prevented it
0x0000000D Handshake of a IOCFacts message failed
0x0000000E* IOs were lost due to an external event
0x0000000F Handshake of PortFacts message failed
0x00000010 Handshake of IOCConfig message failed
0x00000011* IO returned because a CA condition is pending
0x00000012* IO returned for lack of Request resources
0x00000013* IO returned for lack of Request Sense Buffer resources
0x00000014* IO returned because of active reset condition
0x00000015* IO returned because of too many outstanding buffers or chain
buffer resources
0x00000016* Issuing Task Management bus reset message
0x00000017* Received Task Management reply
0x00000018 PCI Peer device controls this device
0x00000019 Invalid Initiator ID set in device
The following error codes all have a value of 0x00000005 at address 0x34 in
the error log details.
Error Code Description
.......... .........................................
0xXXXXXXXX Invalid function code detected within the reply message
The following error codes all have a value of 0x00000009 at address 0x34 in
the error log details.
Error Code Description
.......... .........................................
0xXXXXXXXX The Log value was returned in the SCSI IO Error Reply Message
The following error codes all have a value of 0x00000003 at address 0x34 in
the error log details.
Error Code Description
.......... .........................................
0xXXXXXXXX The Log value returned in the EventNotify Reply Message
Download Driver Pack
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.