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
On 11/08/05, Shawn M. Jones smj@littleprojects.org wrote:
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).
For kickstart I think you'll need to remove the qla module from the initrd and rebuild it.
Will.
On Aug 11, 2005, at 0:45, Shawn M. Jones wrote:
Alfred von Campe wrote:
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).
Nope, that didn't work. The good news is that in RHEL4 (CentOS 4) the delay is only 20 seconds instead of 60 for each channel (so 40 total), which is almost tolerable :-).
Alfred
On 12/08/05, Alfred von Campe alfred@110.net wrote:
On Aug 11, 2005, at 0:45, Shawn M. Jones wrote:
Alfred von Campe wrote:
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).
Nope, that didn't work. The good news is that in RHEL4 (CentOS 4) the delay is only 20 seconds instead of 60 for each channel (so 40 total), which is almost tolerable :-).
Again, the module's probably included in the initrd because it was in /etc/modprobe.conf when the initrd was built. To have a shufty at what's in your initrd try something like the following...
[wmcdonald@willspc initrd]$ pwd /home/wmcdonald/initrd [wmcdonald@willspc initrd]$ cp /boot/initrd- 2.6.9-5.0.5.EL.img initrd-2.6.9-5.0.5.EL.img.gz [wmcdonald@willspc initrd]$ gunzip initrd-2.6.9-5.0.5.EL.img.gz [wmcdonald@willspc initrd]$ ls initrd-2.6.9-5.0.5.EL.img [wmcdonald@willspc initrd]$ file initrd-2.6.9-5.0.5.EL.img initrd-2.6.9-5.0.5.EL.img: ASCII cpio archive (SVR4 with no CRC) [wmcdonald@willspc initrd]$ cpio -i initrd-2.6.9-5.0.5.EL.img (Doh) [wmcdonald@willspc initrd]$ cat initrd-2.6.9-5.0.5.EL.img | cpio -i <snip errors> 4016 blocks [wmcdonald@willspc initrd]$ ls -l total 2048 drwxr-xr-x 2 wmcdonald wmcdonald 4096 Aug 4 16:23 bin drwxr-xr-x 2 wmcdonald wmcdonald 4096 Aug 4 16:23 dev drwxr-xr-x 4 wmcdonald wmcdonald 4096 Aug 4 16:23 etc -rwxr-xr-x 1 wmcdonald wmcdonald 1139 Aug 4 16:23 init -rw-r--r-- 1 wmcdonald wmcdonald 2056192 Aug 4 16:23 initrd-2.6.9-5.0.5.EL.img drwxr-xr-x 2 wmcdonald wmcdonald 4096 Aug 4 16:23 lib drwxr-xr-x 2 wmcdonald wmcdonald 4096 Aug 4 16:23 loopfs drwxr-xr-x 2 wmcdonald wmcdonald 4096 Aug 4 16:23 proc lrwxrwxrwx 1 wmcdonald wmcdonald 3 Aug 4 16:23 sbin -> bin drwxr-xr-x 2 wmcdonald wmcdonald 4096 Aug 4 16:23 sys drwxr-xr-x 2 wmcdonald wmcdonald 4096 Aug 4 16:23 sysroot
Then have a prod around in /lib. If the qla module isn't listed in there it could be compiled into your kernel which might necessitate a rebuild if you can be bothered.
Will.
-
Alfred von Campe -
Shawn M. Jones -
Will McDonald