When performing a driver update, some guidelines should be adhered to. It is safe to do a clean reboot after storage driver update because the init scripts associated with each run level have dependencies on modules and their in-memory versions vis-a-vis their versions in modules.dep file on the hard disk. Performing a reboot will ensure the updated driver version to be loaded into the memory.
Weak-module script and RHEL 5 driver update using DKMS:
The weak-modules script makes available a kernel module compatible with the RHEL 5 Driver Update Program to a specified version of the kernel. This script is usually launched after each kernel upgrade to make available 3rd party modules installed for a previous version of the kernel to the new kernel version. Third party modules that are not compatible with the RHEL 5 Driver Update Program still require manual intervention each time the kernel is upgraded. So ideally the system administrator will need to determine whether the to-be-updated driver is part of this program. Otherwise there will be scenarios where the weak-modules script will not link the updated module to the kernel image.
This might result in system hang or corruption of the in-memory module."
A related RH kbase article exists at http://kbase.redhat.com/faq/FAQ_42_12862.shtm

 out of  found this valuable. Do you find this valuable?    

• Post reply

Show Last Reply