SOFTPAQ NUMBER: N/A
PART NUMBER: N/A
FILE NAME: megaide-2.26j-18.sles8.i586.rpm
TITLE: HP ProLiant Integrated Ultra ATA-100 Dual Channel Driver for SUSE LINUX Enterprise Server 8/UnitedLinux 1.0
VERSION: 2.26j-18
LANGUAGE: English
CATEGORY: Driver - Storage Controllers
DIVISION: N/A
OPERATING SYSTEM: SUSE LINUX Enterprise Server 8/UnitedLinux 1.0
SYSTEM CONFIGURATION: All shipping configurations
PREREQUISITES: N/A
EFFECTIVE DATE: March 15, 2006
ELECTRONIC DISTRIBUTION ALLOWED: Yes
SOFTPAQ UTILITY VERSION: N/A
SUPERSEDES: N/A
SYSTEMS SUPPORTED: HP ProLiant DL320 G2, HP ProLiant ML310, HP ProLiant ML330 G2
DESCRIPTION:
This RPM is used to provide binary driver modules that have been pre-built for United
Linux 1.0 to enable the HP ProLiant Integrated Ultra ATA-100 Dual Channel controller.
The kernels of SUSE LINUX Enterprise Server 8/UnitedLinux 1.0 supported by this binary rpm are:
2.4.21-138
2.4.21-251
2.4.21-261
2.4.21-266
2.4.21-273
2.4.21-278 - SUSE LINUX Enterprise Server 8 SP 4 (x86)
2.4.21-292
FIXES
ENHANCEMENTS
1) Added support for new errata kernels.
Please read this section before proceeding.
This RPM will install binary drivers that will only work with the
SUSE LINUX Enterprise Server 8/UnitedLinux 1.0 kernels listed above. Earlier
or later versions of SUSE LINUX Enterprise Server 8/UnitedLinux 1.0 are not supported. Special actions are required
if you have modified the default kernel configuration for the SUSE LINUX Enterprise Server 8/UnitedLinux 1.0
product. If you have modified the default kernel
configuration you will need to rebuild the kernel to use the updated drivers
after installing the RPM with the --noscripts option.
The megaide driver RPM will not install if it detects that your
configuration is different from the SUSE LINUX Enterprise Server 8/UnitedLinux 1.0 default
Server configuration.
This driver RPM will not install if the loopback device is not configured
but the initrd image is requested since the loopback device is required
to create the initrd image.
INSTALLATION
Login as the system administrator (root), download the RPM to a directory on
your hard drive and change to that directory.
To install the driver type:
# rpm -ivh megaide-2.26j-18.sles8.i586.rpm
Setup is now complete. Please REBOOT your computer NOW!!
To upgrade the driver type:
# rpm -Uvh megaide-2.26j-18.sles8.i586.rpm
Upgrade is Now Complete. Please REBOOT your computer NOW!!
NOTE: If the installation fails or if you see any warning or error messages,
STOP, do NOT reboot the computer. The driver will not be operational and you
must uninstall the driver by typing the following command:
# rpm -e megaide-2.26j-18
The removal of the RPM restores the original megaide.o module,
and builds a new initrd image with the previous driver object module (if any)
and adds yet another grub or lilo entry. You can then boot using this newest
lilo or grub entry, (provided the building of the new initrd image goes well),
or your original lilo or grub entry.
The successful installation will replace the driver that was previously installed
with this version of the driver, create a new Initial
RAM Disk Image (initrd) that contains the megaide-2.26j-18 version of the driver
and modify /etc/lilo.conf (or /boot/grub/menu.lst) to allow the Linux Loader,
lilo (or grub) to boot using the new ramdisk image.
Backups of your previous files will be kept in the /usr/src/HP/driver_backup directory.
The driver will be inserted in the Initial RAM Disk Image (initrd) and is automatically
loaded every time the server boots, provided it is listed in /etc/modules.conf, which,
normally, it is.
NOTE: If the hardware is properly installed and you experience error messages loading the
modules, remove the entire RPM by typing:
# rpm -e megaide-2.26j-18
The removal of the RPM will restore the driver modules, and rebuild and initrd image
for the running kernel and create appropriate entries in
/etc/lilo.conf (or /boot/grub/menu.lst). Additionally you should still be able to
boot using the previous entries still in /etc/lilo.conf or /boot/grub/menu.lst,
provided the driver modules are restored, or were (and thus still are) in the
initrd image.
To check whether the driver is loaded properly, type:
# lsmod
The module named megaide should be displayed.
If you attempt to install the RPM on an unsupported system, you will get an error message.
The driver will not be operational and must be uninstalled by typing the following command:
# rpm -e megaide-2.26j-18
UPGRADING ERRATA KERNELS
Because the driver is not contained inside the Linux kernel, new errata kernels
installed on systems using this driver will fail to create a new initrd and
generate an error during installation. The following steps will allow the user
to add the latest driver module into the errata kernel's directory and create a
new image and boot loader entry. This will allow them to reboot into the upgraded
errata kernel.
1. Boot into the known good kernel (previous kernel)
2. Install the errata kernel rpm. This will give an error about the driver.
The error is expected. However, the kernel should still have placed its modules
in /lib/modules/<kernel version>. The only thing not installed by the errata
kernel rpm is the new initrd (Because of the error mentioned above.).
3. Copy the driver rpm to the / directory.
4. Extract the driver rpm with the following command:
#rpm2cpio <rpm name> | cpio -idum
5. Change directory to locate the driver files tarball:
#cd /opt/lsirpm/megaide
6. Extract the driver files tarball:
#tar xzf <driver>-<id>.tar.gz
7. Copy the driver for the newly installed errata kernel contained in the driver
rpm into the appropriate /lib/modules directory:
#cp lib/modules/<errata version>/kernel/drivers/scsi/<driver.o> \
/lib/modules/<errata version>/kernel/drivers/scsi/<driver.o>
8. Run depmod to add the newly installed driver into the modules.dep file for the upgraded
errata kernel.
#/sbin/depmod -aAq <kernel version>
9. Make a new ramdisk image for the new errata kernel
For Red Hat systems:
#mkinitrd /boot/new.img <kernel version>
For SUSE systems:
#mkinitrd -k <kernel image> -i /boot/new.img
where kernel image is the vmlinuz file installed in /boot by the errata kernel rpm.
10. Add an entry into the grub or lilo file for this new image and kernel. The easiest method
to do this is to copy the entry that is currently the default and modify it to use the
new vmlinuz file and the new initial ramdisk image you created. Then set the default entry
to the new entry you added.
NOTE: For lilo systems don't forget to run /sbin/lilo
11. Reboot into the new kernel image.
Copyright 2002, 2003, 2004, 2005, 2006 Hewlett-Packard Development Company, L.P. Product names mentioned herein
may be trademarks and/or registered trademarks of their respective companies.