HP IO Accelerator Driver and Management Software 2.2.0 Release Notes

Errata 16
or an earlier release of 2.6.[31-32] and are running ext4, add the driver option enable_discard=0 to
disable trim/discard at the driver layer. For more information, see the kernel patch
(http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=5328e635315734d).
Driver might not autoload in some distributions
When using certain Linux operating systems, the driver installation package might not properly configure
itself to be automatically loaded in all run level boot sequences. To verify whether the driver is properly
configured, after you have installed the driver, run the following command at a shell prompt:
$ chkconfig –list | grep iodrive
The following appears:
$ iodrive 0:off 1:on 2:on 3:on 4:on 5:on 6:off
The results inform you that the driver loads if the server is booted at run levels 1-5. At a minimum, the run
levels at which you use or maintain the IO Accelerator must be enabled. If those run levels are not
enabled, run the following commands at a shell prompt (with root privilege):
$ chkconfig --del iodrive
$ chkconfig --add iodrive
$ chkconfig --list | grep iodrive
The previous results appear:
$ iodrive 0:off 1:on 2:on 3:on 4:on 5:on 6:off
If you need further assistance, contact HP Customer Support (http://www.hp.com/support).
RHEL4 2.6.9-22 kernel does not work with 320GB IO
Accelerators
Because of limitations in the 2.6.9-22 kernel shipped with early versions of RHEL4, the 320GB IO
Accelerator and 640GB IO Accelerator Duo cards do not work when running this kernel.
Newer RHEL4 kernels support the larger devices.
Modinfo module parameters not reported under RHEL4
The IO Accelerator driver does not properly report the load-time parameters when the modinfo
command is run. Obtain the list of supported parameters from the User Guide that came with your IO
Accelerator or by running the modinfo command on a newer system. The module parameters are
identical between Linux distributions when using the same driver version.
Source rpm build fails in Chaos 4.3 with ccache enabled
By default, Chaos has the ccache package installed. If an attempt is made to build the RPM from source
with ccache enabled, the result is an error message.
Remove or disable ccache before building the driver.