CentOS - Aug 2005 - How to prevent loading qla2300.o module

I apologize in advance as this is not really at CentOS specific issue, 
but I don't know where else to turn.  We are configuring some Dell 
1850s for a customer, and they have all been configured with a QLogic 
dual channel HBA.  But no storage has been (or will be in the near 
future) attached to these HBAs.  During the boot process (both for the 
kickstart and after the OS has been installed), there is a 2 minute 
delay (1 minute for each channel) while the qla2300.o module is loaded 
and the HBA probes for any attached storage.

How can I configure the kernel to ignore the QLogic HBA?  It's not that 
critical for the kickstart process (although that would be nice too).

Thanks,
Alfred

Alfred von Campe wrote:
> I apologize in advance as this is not really at CentOS specific issue, 
> but I don't know where else to turn. We are configuring some Dell 
> 1850s for a customer, and they have all been configured with a QLogic 
> dual channel HBA. But no storage has been (or will be in the near 
> future) attached to these HBAs. During the boot process (both for the 
> kickstart and after the OS has been installed), there is a 2 minute 
> delay (1 minute for each channel) while the qla2300.o module is loaded 
> and the HBA probes for any attached storage.
>
> How can I configure the kernel to ignore the QLogic HBA? It's not that 
> critical for the kickstart process (although that would be nice too).
Off of the top of my head, I don't know what to do about kickstart, but 
look in the /etc/modprobe.conf to see what options are passed to loaded 
modules. If your module is in there, try removing the line. If it is not 
in there, try the /etc/modules file (if it exists, RH/CentOS doesn't 
usually have one these days).

Hope this helps,

--Shawn