This release note and the software that accompanies it are copyright (c) 2014, Intel Corporation or its suppliers, and may only be installed and used in accordance with the license that accompanies the software. This Software is furnished under license and may only be used or copied in accordance with the terms of that license. No license, express or implied, by estoppel or otherwise, to any intellectual property rights is granted by this document. The Software is subject to change without notice, and should not be construed as a commitment by Intel Corporation or its suppliers to market, license, sell or support any product or technology. Unless otherwise provided for in the license under which this Software is provided, the Software is provided AS IS, with no warranties of any kind, express or implied. Except as expressly permitted by the Software license, neither Intel Corporation nor its suppliers assumes any responsibility or liability for any errors or inaccuracies that may appear herein. Except as expressly permitted by the Software license, no part of the Software may be reproduced, stored in a retrieval system, transmitted in any form, or distributed by any means without the express written consent of Intel Corporation. ========================== Supported RAID Controllers ========================== This download supports Intel(R) RAID controllers with 3108 or 2208 RAID chip and using MegaRAID SAS software stack (RS3SC008, RS3DC080, RS3DC040, RS3WC080, RMS25PB080, RMS25PB040, RMT3PB080, RMS25CB080, RMS25CB040, RMT3CB080, RMS25CB080N, RMS25PB080N, RS25AB080, RS25SB008, RS25DB080, RS25NB008), please verify that this utility has been tested with the RAID card you have chosen to use by checking the drivers web page for your controller at http://support.intel.com. =================== Package Information =================== Driver Version = 6.602.01.00 OS supported = FreeBSD 9.0, 8.3, 8.2, 7.4. (both x86 and x64 versions) ========= Attention ========= N/A ================== Known Restrictions ================== N/A ======================= Contents on the package ======================= This package includes drivers that can be compiled from source files into the kernel as built-in drivers or can be modules that are loaded by the operating system. Both source files and modules are available, but modules with current controller drivers are available for FreeBSD 7.4, 8.2, 8.3, and 9.0. Compiled and tested kernel driver modules for FreeBSD 7.4, located here: 32-bit: components/7.4.0/i386 64-bit: components/7.4.0/amd64 Compiled and tested kernel driver modules for FreeBSD 8.2, located here: 32-bit: components/8.2.0/i386 64-bit: components/8.2.0/amd64 Compiled and tested kernel driver modules for FreeBSD 8.3, located here: 32-bit: components/8.3.0/i386 64-bit: components/8.3.0/amd64 Compiled and tested kernel driver modules for FreeBSD 9.0, located here: 32-bit: components/9.0.0/i386 64-bit: components/9.0.0/amd64 Driver source files for FreeBSD 7.x, 8.x, and 9.x located here: For mfi driver, components/src/mfi.tgz For mrsas driver, components/src/mrsas.tgz =================================================== Drivers and Software for FreeBSD =================================================== o FreeBSD System Administration Information o Installing LSI Drivers and Software under FreeBSD =================================================== FreeBSD System Administration Information =================================================== The latest FreeBSD System Administration information can be found here: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/disks-adding.html Online man pages can be searched here: http://www.freebsd.org/cgi/man.cgi =================================================== Special Notes for FreeBSD9.1 with inbox driver has support for Thunderbolt(device ID 0x005b) =================================================== FreeBSD-9.1-RELEASE is first RELEASED FREEBSD kernel which has mfi driver capability to detect Thunderbolt without any intellegency to switch preferences as explained in this document. FreeBSD-9.1 will have mfi inbuilt into the kernel and without mrsas inbox support. Because of this issue, FreeBSD-9.1 will give priority to driver for Thunderbolt. If user wants to achieve same behavior in FreeBSD-9.1, LSI recommend to switch to next available FreeBSD-x release which can provide this feature. Below is another option to use mrsas Driver for Thunderbolt on FreeBSD-9.1 (not recommended, because it is bit tricky and required extra effots from end user). Customer can create custom ISO image (steps to create custom ISO is documented in section "Creating a Custom ISO Image to Exclude the MFI and MPT Drivers") and replace driver shipped by LSI (check www.lsi.com) along with modified driver. =================================================== 4k sector drives support in FreeBSD =================================================== Application called "gpart" can recognize the partition from 4k sector drives not "fdisk". Systinstall (User interface provided by FreeBSD for Configuration) and installation media cannot detect 4k drives because they use "fdisk" to do partition and fdisk does not understand 4k sectors drives. User should learn "gpart" commands to use 4K sector Drive as Secondary storage. Go through manual page of gpart to learn gpart commands. =================================================== Installing Drivers and Software under FreeBSD =================================================== This section provides detailed instructions for installing the LSI driver under a FreeBSD operating system. The following topics are included in this section: o Driver Installation for FreeBSD o Updating Drivers under FreeBSD =============================== =============================== Driver Installation for FreeBSD =============================== =============================== Note: 1) If your FreeBSD system does not have the mpt driver issue, then before installing the LSI driver, you should already have installed your MegaRAID controller in the system. Consult the installation guide that came with your controller. 2) If your FreeBSD system has the mpt driver issue, then you must disable the mpt driver during the boot process in order to boot your system. Many of the sections in this document describe how to disable the mpt driver during boot, and how to build a kernel without including the mpt module. If you have a MegaRAID controller installed, you must power down and remove the controller from your system and recompile the kernel as described in the sections below. If you leave the controller in your system and boot to a kernel that includes the mpt driver without disabling it first, the driver will claim the device ID and go into a soft reset continuously. Your system will not come out of boot. This section provides details about how to install the driver for your MegaRAID controller under FreeBSD. o If the VDs you have created are your boot device, you install the driver for the controller as you install FreeBSD. o If the operating system is already installed on a unit connected to another controller or to the motherboard, you start FreeBSD and then install the driver. This section includes these topics: o "Obtaining LSI FreeBSD Drivers" o "Creating a FreeBSD Driver Diskette" o "Installing FreeBSD on Storage Managed by a MegaRAID Controller (Primary Storage)" o "Installing the Kernel Driver on a FreeBSD System that Boots from a Device NOT Managed by a MegaRAID Controller(Secondary Storage)" ---------------------------------- Creating a FreeBSD Driver Diskette ---------------------------------- You need a diskette drive if you are going to be installing FreeBSD on a VD or drive managed by a MegaRAID controller card which becomes the boot unit for which your version of FreeBSD does not have a built-in driver. You may also use a USB flash drive. To create a driver diskette 1 Insert a blank diskette and the LSI software CD into a FreeBSD installed system. 2 For FreeBSD 7.4 Navigate to: components/7.4.0 For FreeBSD 8.2 Navigate to: components/8.2.0 For FreeBSD 8.3 Navigate to: components/8.3.0 For FreeBSD 9.0 Navigate to: components/9.0.0 3 Copy the appropriate driver to the diskette, i.e., driver from i386 folder if you are installing a 32-bit FreeBSD, amd64 folder if you are installing 64-bit FreeBSD. You need the driver source from components/src/driver_name.tgz if you are going to update the kernel with a new driver. For example: For mfi driver, the driver source is in components/src/mfi.tgz file. For mrsas driver, the driver source is in components/src/mrsas.tgz. ---------------------------------------------------------------- Installing FreeBSD on Storage Managed by a MegaRAID Controller (Primary Storage) ---------------------------------------------------------------- Use this procedure if your boot unit is going to be managed by the MegaRAID controller. Due to an issue with LSI mpt driver, and FreeBSD versions 6.1-9.X include outdated LSI drivers, your MegaRAID controller for primary storage is impacted. If the mpt driver issue occurs, the system will generate a continuous soft and hard reset and the system cannot boot. The installation disk will not install the OS and the process must be terminated. To avoid the issue with the mpt driver, you need to disable the mpt driver. If you have FreeBSD versions up to 7.4, 8.2, or 9.0, your FreeBSD OS most likely contains the outdated mfi driver in the kernel. A new FreeBSD kernel ISO needs to be created to exclude the outdated mfi driver before you load the updated mfi (ver 4.8 or newer) or mrsas driver. With the newly created FreeBSD kernel ISO and the updated mfi (ver 4.8 or newer) or mrsas driver loaded, you can complete the installation and boot your FreeBSD system through a MegaRAID VD. Please note that this situation would no longer exist when the mpt driver issue is fixed and when the outdated inbox mfi driver is replaced with the new mfi driver. Effort toward the resolution of this problem is underway and in the future the extra steps would not be necessary. This issue is fixed in the 8.3 release of FreeBSD. Please see, "Creating a Custom ISO Image to Exclude the MFI and MPT Drivers" below if your FreeBSD OS has this issue. After you have created a custom FreeBSD Installation disk with the new FreeBSD kernel custom ISO image and you have the mfi (ver 4.8 or newer) or mrsas driver ready, follow the instructions below. It describes how to load the FreeBSD kernel driver module to enable boot device support, and how to then compile the current drivers into the kernel from source files. Prerequisite: You will need an OS Installation CD for FreeBSD 7.4, FreeBSD 8.2, or FreeBSD 9.0 (i386 or amd64) that was created using the instructions in "Creating a Custom ISO Image to Exclude the MFI and MPT Drivers". Although FreeBSD 6.X is not fully supported by LSI, these versions of FreeBSD will also require a custom ISO image if primary storage is required. Note: This procedure is specific to versions of FreeBSD for which a compiled module is available. For other versions of FreeBSD for which a compiled module is not supplied by LSI it is necessary to compile your own module from source files. See "Compiling and Loading the Driver as a Module using kldload (dynamically loadable module)". 1. Disconnect all SCSI, ATA, and SAS devices in the system, except the CD or DVD and hard drives connected to the MegaRAID controller. 2. Create the RAID VDs on the MegaRAID controller using WebBIOS, or Preboot Cli. 3. Insert the FreeBSD Installation disk to CD/DVD drive and boot from it. 4. At the FreeBSD boot menu, select "Escape to loader prompt." (option 6 in FreeBSD 7.x and 8.x, and option 2 in FreeBSD 9.x). 5. Insert the diskette containing driver_name.ko module into the diskette drive. If a USB flash drive will be used, the drive may need to be inserted before booting so that it can be seen in the next step. If this is the case, make sure to boot from the CD/DVD drive and not the USB drive. For mfi driver, the driver_name.ko is mfi.ko. For mrsas driver, the driver_name.ko is mrsas.ko. 6. At the loader prompt. To disable the mpt driver, type the following at the prompt: OK set hint.mpt.0.disable=1 OK set hint.mpt.1.disable=1 NOTE: Disabling the mpt driver should not be required when using a custom ISO image because the mpt driver will not exist if the custom image was created properly. A custom ISO is required only for the OS versions stated in the 'Prerequisite' section above. To load a new driver from a diskette drive: For mfi driver, OK load disk0:mfi.ko For mrsas driver, OK load disk0:mrsas.ko Note: If you have multiple devices/units for OS installation, and the device/ unit that you want to use for the installation is not disk0, please change disk0 to the appropriate number, i.e. disk1 or disk5, etc. The lsdev command lists all of the devices from which it may be possible to load the driver. If a USB flash drive is used, the drive may need to be inserted before booting so that it can be accessed in this step. 7. Continue with the installation by typing: OK boot 8. Install the FreeBSD OS - including kernel source. Please, remember including kernel source files is critical. 9. Remove both the FreeBSD installation disk from the CD/DVD drive and the floppy disk from the floppy drive (or USB flash drive, if used), and reboot. 10.On the bootup, repeat step 4-7. 11.Upon boot, continue with the instruction in the section of "Updating the Kernel with the New Driver Source" for statically linked module. ---------------------------------------------------------------- Creating a Custom ISO Image to Exclude the MFI and MPT Drivers ---------------------------------------------------------------- You must use this procedure if you are "Installing FreeBSD on Storage Managed by a MegaRAID Controller (Primary Storage)" as described in that section. That is, you must use this procedure if the mfi driver must be excluded from the kernel due to the problem described in that section. In this procedure, the mpt driver will also be excluded so that it does not get attached to the MegaRAID controller during the OS installation to primary storage. If the mpt driver attaches to the MegaRAID controller, any drives attached to the MegaRAID controller will not be found during the OS installation process. This procedure was leveraged from the FreeBSD article, FreeBSD Release Engineering, Section 3 Release Building, by Murray Stokely, at this FreeBSD link: http://www.freebsd.org/doc/en_US.ISO8859-1/articles/releng/index.html and the FreeBSD Handbook, Chapter 9 Configuring the FreeBSD Kernel, Section 9.5 Building and Installing a Custom Kernel, at this FreeBSD link: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ \ kernelconfig-building.html Since different versions of FreeBSD have different make files, drivers, build procedures, etc., the simplest way to create a custom ISO image for a specific version of FreeBSD is to install the version of FreeBSD that is needed for the ISO image. The procedure outlined below should work for all supported versions of FreeBSD (currently 7.4, 8.2, 8.3, and 9.0). Some steps are different for 9.0 or later and are noted. 1. Install the version of FreeBSD required onto an available disk that is not attached to a MegaRAID controller. During installation, also install all of the system source code. IT IS REQUIRED THAT THE SYSTEM SOURCE CODE BE INSTALLED FOR THIS PROCEDURE. A network connection may be needed to download the source code that is to be used to build the ISO image. The CD/DVD that is used to install the OS may already contain the source code depending on the type of installation that is on that CD/DVD. Otherwise, you can use the sysinstall utility to download the source. The installed OS will only be used to build the custom ISO and then is no longer required. 2. Boot to the disk with the new FreeBSD OS and change to the /usr/src/sys//conf directory, where is either i386 or amd64, depending on what type of architecture the ISO image will be for. The GENERIC kernel configuration file within this folder must be edited so that the mfi and mpt drivers will not be installed when the new custom ISO is built. The mfi and mpt lines can be removed or commented out, like this (add # before "device"): #device mfi # LSI MegaRAID SAS #device mpt # LSI-Logic MPT-Fusion NOTE: The preferred method when editing the GENERIC configuration file is to copy it into some other file and create a kernel using this new kernel configuration file. However, using that method here would require a more complex procedure and is unnecessary. 3. Issue the following commands, which will build the tools, etc. that are required to build the ISO image. This command could take several hours to complete. # cd /usr/src # make buildworld TARGET= where is the architecture for the ISO image to be created. If the make command fails immediately, it could be that the system source code was not installed properly. You should be able to install the source code using the sysinstall utility. Within sysinstall, the source code can be selected from within the Distributions selection. 4. For version 9.0 or later, the GENERIC kernel must be built in a separate command. Previous versions do not require this step. If building for version 9.0 or later enter the following commands before moving on, otherwise you can skip this step. # cd /usr/src # make buildkernel TARGET= Where is the architecture for the desired ISO image. 5. Finally, to build the ISO image, issue the following commands. The make command could take several hours to complete. See NOTE2 below if building for version 9.0 or later. # cd /usr/src/release # make release BUILDNAME=FBSD_-CUSTOM \ CHROOTDIR=/usr/MyCustomBuild \ EXTSRCDIR=/usr/src \ TARGET= \ NOPORTS=1 \ NODOC=1 \ MAKE_ISOS=1 Where is the FreeBSD version being built and is the architecture for the desired ISO image. The BUILDNAME and CHROOTDIR values are examples. You can set these to whatever you like. Ports and Docs are not included in this example because it's faster and less complex to leave these out of the build. If Ports and Docs were included, the build process could fail because more packages may be needed. Visit freebsd.org for complete documentation on the 'make release' command. NOTE1: The creation of the ISO image is the last step in the make process. If ISO image creation fails, make sure the latest /usr/local/bin/ and /usr/local/lib/ files are copied into the /usr/local/bin and /usr/local/lib folders. If those folders already exist and the files are up to date, the next step is to make sure that the cdrtools package was installed successfully. If not, use sysinstall or some other method to get this package. If the cdrtools package is installed, make sure again that the ../bin and ../lib folders are up to date as described above. Then run the make command again, but use 'rerelease' instead of 'release'. Using 'rerelease' will ensure that the make process starts up from where it failed and not from the beginning of the make process, which could save several hours. NOTE2: For version 9.0 or later, the make release command has been simplified and is shown below. See the Makefile for more information. # cd /usr/src/release # make release TARGET= \ NOPORTS=1 \ NODOC=1 6. After successfully completing the make process, all of the new ISO images will be located in the /R/cdrom directory. NOTE: For version 9.0 or later, the new ISO images will be located in the /usr/obj/usr/src/release directory. ---------------------------------------------------------------------- Installing the Kernel Driver on a FreeBSD System that Boots from a Device NOT Managed by a MegaRAID Controller(Secondary Storage) ---------------------------------------------------------------------- Use the steps in this section if FreeBSD boots from a device NOT managed by a MegaRAID controller, but MegaRAID controller is or will be present on the system and used for managing secondary storage. When you use the VD managed by the MegaRAID controller for secondary storage, you do not need to use a driver diskette for driver installation. Note: Due to an issue with LSI mpt driver in FreeBSD 7.x, 8.x and 9.x, your Megaraid controllers may be impacted. To avoid the issue with mpt driver, you may need to disable the mpt driver before install or boot your FreeBSD system until you exclude the mpt driver from the installed kernel. If the mpt driver is not removed, the system will generate a soft reset and hard reset errors on the bootup. DVD will not load. Tip: Install FreeBSD on the drive attached to the motherboard before installing the MegaRAID controller. This avoids the possibility of installing to the wrong drive or unit. 1 Get the latest driver source files for your version of FreeBSD. See "Obtaining LSI FreeBSD Drivers". A. System does not include an LSI controller before the OS installation: ------------------------------------------------------------------------- 1. Install FreeBSD - including kernel source - on a motherboard attached drive. Please, remember including kernel source files is critical. 2. After the OS installation, please reboot. 3. Follow the instructions for driver installation in "Updating the Kernel with the New Driver Source" for Statically Linked Module, or "Compiling and Loading the Driver as a Module using kldload" for Dynamically Loadable Module. 4. Once FreeBSD is installed and the driver is updated, power down the system and install the MegaRAID controller. For assistance, see the installation guide that came with the controller. B. System includes a Megaraid controller before the OS installation: -------------------------------------------------------------------- 1. Begin the installation process. 2. As the DVD loads, the user is offered boot options. 3. Select "Escape to loader prompt." (option 6 in FreeBSD 7.x and 8.x, and option 2 in FreeBSD 9.x). To disable the mpt driver, type the following at the prompt: OK set hint.mpt.0.disable=1 OK set hint.mpt.1.disable=1 OK boot 4. Proceed with the installation on a disk attached to the motherboard. Be sure to install the full FreeBSD source. 5. After the OS installation, follow the instructions for driver installation in "Updating the Kernel with the New Driver Source" for Statically Linked Module, or "Compiling and Loading the Driver as a Module using kldload" (for Dynamically Loadable Module). ============================== ============================== Updating Drivers under FreeBSD ============================== ============================== Drivers can be updated either from source files or with driver modules. Using source files, you can compile drivers into the kernel or you can create modules for versions of FreeBSD for which LSI does not supply modules. This section includes these topics: o "Updating the Kernel with the New Driver Source" o "Compiling and Loading the Driver as a Module using kldload" (dynamically loadable module) o "Updating the MegaRAID Kernel Driver Module Under FreeBSD" ---------------------------------------------- Updating the Kernel with the New Driver Source ---------------------------------------------- Use this procedure if you wish to update your kernel from driver source files for both dynamically loadable module and statically linked module. To obtain source files, see "Obtaining LSI FreeBSD Drivers". 1. Make sure that kernel source has been installed on the system. The kernel sources are in the /usr/src/sys directory. 2. Proceed to the /usr/src/sys/dev/ directory Check if a directory with the driver name already exists. If it is, move it to a different folder. For example: Do the following for mfi driver. # mv /usr/src/sys/dev/mfi /root/mfi.backup Or do the following for mrsas driver. # mv /usr/src/sys/dev/mrsas /root/mrsas.backup And make sure the directory exists. For example: Perform the following command for mfi driver. # mkdir /usr/src/sys/dev/mfi Or perform the following command for mrsas driver. # mkdir /usr/src/sys/dev/mrsas 3. Proceed to the /usr/src/sys/modules/ directory Check if a directory with the name of your driver already exists. If it is, move it to a different folder. For example: For mfi driver, # mv /usr/src/sys/modules/mfi /root/mfi_module.backup For mrsas driver, # mv /usr/src/sys/modules/mrsas /root/mrsas_module.backup And make sure the directory exists. For example: For mfi driver, # mkdir /usr/src/sys/modules/mfi For mrsas driver, # mkdir /usr/src/sys/modules/mrsas 4. Unpack the compressed driver source file (mfi.tgz for mfi driver and mrsas.tgz for mrsas driver) and move the *.c and *.h files to /usr/src/sys/dev/driver_name (which is mfi for mfi driver and mrsas for mrsas driver), and move the Makefile to the /usr/src/sys/modules/driver_name (which is mfi for mfi driver and mrsas for mrsas driver). For example: # cd /usr/src/sys/dev For mfi driver, # tar -xf mfi.tgz # mv mfi/Makefile /usr/src/sys/modules/mfi/. For mrsas driver, # tar -xf mrsas.tgz # mv mrsas/Makefile /usr/src/sys/modules/mrsas/. 5. At this point, proceed to /usr/src/sys/i386/conf if you are running a 32bit version of FreeBSD /usr/src/sys/amd64/conf if you are running a 64bit version of FreeBSD a. copy the GENERIC configuration file to another name. For example: # cp GENERIC MYKERNEL b. Open your current configuration file: (GENERIC, MYKERNEL, SMP, or PAE or custom config), with vi or other editor. For example: # vi MYKERNEL Comment out the following lines by placing '#' at the beginning of the line: #device cbb # cardbus (yenta) bridge #device mpt # LSI-Logic MPT-Fusion For a dynamically loadable module --------------------------------- Comment out the following line by placing '#' at the beginning of the line. #device mfi # LSI MegaRAID SAS For mrsas driver, comment out the following line by placing '#' at the beginning of the line if it exists. #device mrsas # LSI MegaRAID SAS2 For a statically linked module ------------------------------ For mfi driver, make sure the following line is NOT commented out. device mfi # LSI MegaRAID SAS For mrsas driver, make sure the following line is NOT commented out if it exists. device mrsas # LSI MegaRAID SAS2 If you do not have any MR Liberator or older controller installed in your system, make sure to comment out the following line. #device mfi # LSI MegaRAID SAS c. Save changes. d. In /usr/src/sys/conf/files, do the following: For mfi driver, add the following entries after the entry for "dev/mfi/mfi_cam.c": dev/mfi/mfi_syspd.c optional mfi With an older mfi driver v4.3x on MR Thunderbolt controller support, also add the following: dev/mfi/mfi_fp.c optional mfi dev/mfi/mfi_tbolt.c optional mfi For mrsas driver, make sure the following entries are present. dev/mrsas/mrsas.c optional mrsas dev/mrsas/mrsas_cam.c optional mrsas dev/mrsas/mrsas_ioctl.c optional mrsas NOTE: Each line is an entry in this file. Make sure a newly added entry is on a new line. e. Save changes. f. To compile the kernel, go to /usr/src directory and type the following if your current configuration is MYKERNEL. # cd /usr/src # make buildkernel KERNCONF=MYKERNEL g. To install the new kernel, type the following if your current configuration is MYKERNEL. # make installkernel KERNCONF=MYKERNEL The new kernel will be copied to the /boot/kernel directory. The old kernel will be moved to the /boot/kernel.old directory. 6. Reboot your system. When the system reboots, the new kernel driver module will load automatically. -------------------------------------------------------------------------------------- Compiling and Loading the Driver as a Module using kldload (dynamically linked module) -------------------------------------------------------------------------------------- If you want to use a driver module and LSI does not supply one for your version of FreeBSD, use the following procedure. If you just want to install an LSI-supplied module, see "Updating the MegaRAID Kernel Driver Module Under FreeBSD". Note: You can only use kldload to load the driver as a module if your boot drive is attached to the mother board and is not managed by the MegaRAID controller. To compile the driver as a module 1. Boot to FreeBSD. 2. Obtain driver source files, see "Obtaining LSI FreeBSD Drivers". 3. Prepare your kernel is prepared for Dynamically Loadable Module described in "Updating the Kernel with the New Driver Source" 4. To build the driver module, type the following commands, and press Enter. For mfi driver, # cd /usr/src/sys/modules/mfi # make For mrsas driver, # cd /usr/src/sys/modules/mrsas # make These steps create the driver driver_name.ko module in the /usr/src/sys/modules/driver_name directory. 5. Load the kernel driver module For mfi driver, # cd /usr/src/sys/modules/mfi # kldload -v ./mfi.ko For mrsas driver, # cd /usr/src/sys/modules/mrsas # kldload -v ./mrsas.ko 6. If you wish to load the driver automatically on the bootup - but still be linked dynamically: a. Copy the driver into the boot folder. For mfi driver, # cp /usr/src/sys/modules/mfi/mfi.ko /boot/kernel/mfi.ko For mrsas driver, # cp /usr/src/sys/modules/mrsas/mrsas.ko /boot/kernel/mrsas.ko (Backup the old module in case you want to revert back to it.) b. Add the following line to the file /boot/loader.conf. For mfi driver, mfi_load="YES" For mrsas driver, mrsas_load="YES" -------------------------------------------------------- Updating the MegaRAID Kernel Driver Module Under FreeBSD -------------------------------------------------------- The following steps describe how to update the MegaRAID driver with a kernel driver module under FreeBSD. Make a backup of your original driver before updating in case you need to revert back to it. However, you will not be able to revert back to the original driver if you are booting from that VD. 1. Obtain the driver, see "Obtaining LSI FreeBSD Drivers". 2. Make a backup of any critical data prior to updating the MegaRAID driver. 3. Change the directory to the location with the driver. 4. Copy the driver into /boot/kernel. For mfi driver, # cp mfi.ko /boot/kernel For mrsas driver, # cp mrsas.ko /boot/kernel Make sure the module version matches the FreeBSD version. If the versions don't match there could be a kernel panic. 5. Load the driver. For mfi driver, # kldload -v /boot/kernel/mfi.ko For mrsas driver, # kldload -v /boot/kernel/mrsas.ko If storage is present, you should see information in the system log (usually, /var/log/messages). 6. If you wish to load the driver automatically every time the system reboots, add the following line to the file /boot/loader.conf For mfi driver, mfi_load="YES" For mrsas driver, mrsas_load="YES" ============= Fixes/Updates ============= Version 6.602.01.00 SCGCQ00523785 - Data Corruption observed on JBODs while running IOs with 32k block size. SCGCQ00459075 - On converting from UG to JBOD and vice versa, fw sees reply msQOverflow and hit montask. Version 6.601.07.00 SCGCQ00325392 - Clear "sync_cmd_idx" for MFI/MPT pass through command on completion. SCGCQ00324106 - Wait for IOCTL when OCR is in progress/HBA is not operational SCGCQ00324102 - Do not OCR in case FW flash takes more than 3 min SCGCQ00338058 - RAIDmap free and setup requires specifying ith map SCGCQ00340011 - Fixed kernel panic when issue MegaCLI command. SCGCQ00339814 - Fix for FW reporting of SGL doesn't match header length. SCGCQ00327982 - Check for reset flags in ISR to avoid parallel IO completion when driver is doing OCR SCGCQ00330074 - Fixed Excessive Regtype mismatch Firmware debug message output issue SCGCQ00301726 - Added source code for RAID map functionality. SCGCQ00320759 - Added support for MFI_CMD_ABORT command. SCGCQ00301714 - Online Controller Reset implementation details SCGCQ00301724 - Implemented FastPath I/O support for the MR 5.5 FreeBSD mrsas driver. Version 5.507.02.00 SCGCQ00358240 - Create aliased /dev entry for only first controller(device unit) connected SCGCQ00335534 - FreeBSD-8.3 amd64 and i386 support is added SCGCQ00322284 - 4k sector support SCGCQ00318638 - Added FreeBSD Driver Support for MegaRAID SYSPD SCGCQ00365515 - Remove misplaced files within MR FreeBSD 5.6 project Version 5.506.02.00 SCGCQ00361267 Version 5.505.03.00 SCGCQ00339814 - Fix for FW reporting of SGL doesn't match header length. SCGCQ00340011 - Fixed kernel panic when issue MegaCLI command. SCGCQ00301714 - Online Controller Reset implementation details SCGCQ00301724 - Implemented FastPath I/O support for the MR 5.5 FreeBSD mrsas driver. SCGCQ00301726 - Added source code for RAID map functionality. SCGCQ00320759 - Added support for MFI_CMD_ABORT command. Version 5.504.05.00 Initial Release. *Third-party trademarks are the property of their respective owners.