Fusion MPT Package - Binary Images ==================================================== Binaries have been generated for use with Red Hat Linux 7.0, 7.1, 7.2, ASE 2.1, 7.3. These binaries may be used to upgrade a driver without rebuilding the kernel or used to upgrade the driver during install ==================================================== Upgrading the Driver During Installation ----------------------------------------- Step 1: For the version of Red Hat of interest, uncompress the tarball. # tar xzvf redhat70-.tar.gz Step 2: Transfer the driver disk image of interest to a diskette using dd or raw-write. For a 686-type of processor and Red Hat 7.0 Linux, # dd if=rh70i686.img of=/dev/fd0 Remark: Red Hat installs binaries that are compatible with your processor. Therefore, if you have a 686-type processor but use the 386 install diskette, installation will be successful but reboot will fail. The failure will be due to the 386 driver binaries from the diskette not being compatible with the 686 binaries installed by Red Hat. You must select the disk that matches your system processor type. Recovery: Make a bootable driver disk when the installer presents the option. If the normal boot fails, reboot using the bootable diskette. Using the appropriate driver disk, install the binaries as in Step 5 below. You must re-create your ramdisk images. First, # ls /lib/modules and write down the directory names. For example, you might see 2.4.7-10 2.4.7-10smp For each directory in /lib/modules. For the example, # cd /boot # /sbin/mkinitrd -f initrd-2.4.7-10.img 2.4.7-10 # /sbin/mkinitrd -f initrd-2.4.7-10smp.img 2.4.7-10smp Finally, if you installed LILO, you must re-run LILO, # lilo -v Reboot. Step 3: Red Hat 7.0, 7.1, 7.1SBE, ASE 2.1, 7.3 Boot the installation material. At the first screen, enter linux dd when the boot: prompt appears (the installer will then to prompt for the driver update diskette). Option for Red Hat 7.1, ASE 2.1, 7.3: ------------------------------------ Boot the installation material. At the first screen, enter linux dd updates when the boot: prompt appears (the installer will then to prompt for the driver update diskette and the updates disk). Use the same diskette for both. If the update script is successfully executed by the installer, Step 5 below is unnecessary. To determine if execution was successful, on reboot, log in a root. # cd /lib/modules # find -name mptbase.o If the script was executed successfully, mptbase.o will show once for each kernel directory. That is, find will return: 2.4.7-10/kernel/drivers/message/fusion/mptbase.o 2.4.7-10smp/kernel/drivers/message/fusion/mptbase.o Step 3: Red Hat 7.2 When driver update disks are used, incorrect boot images are created by the Red Hat 7.2 installer. To use driver update disks, the user requires three (3) floppy diskettes. One disk is the diskette written in Step 2 and contains the driver. The second disk contains a new boot image and the third contains patches to the Red Hat installer program. Step 3a: Create diskette 2. The new boot image (boot.img) is available in the redhat72-.tar.gz tarball # dd if=boot.img of=/dev/fd0 Step 3b: Create diskette 3. The installer update image (update_disk-20020117.img) is available in the redhat72-.tar.gz tarball # dd if=update-disk-20020117.img of=/dev/fd0 The boot and update disk images may be obtained from: ftp://updates.redhat.com/7.2/en/os/images/i386 Step 3c: Boot the installation material. At the first screen, enter linux dd updates when the boot: prompt appears (the installer will then to prompt for the driver update diskette and the installer update disk). Step 4: Continue with normal installation. Step 5: Once installation is complete and reboot is successful, execute the post-installation script. Insert the driver update disk into the floppy disk drive then # mount /dev/fd0 # cd /mnt/floppy # ./post_install.scr # cd # umount /dev/fd0 Proceed with normal usage.