FC2214 QLA linux

[Anil Sonmez]

After installing drivers with INSTALL in hp_qla2x00-2005-09-19.tar file. It created the initrd-2.4.9-e.35smp.img file. And system didnt boot(kernel panic). What I have to do for booting correctly with new initrd?
Another question I put old initrd file back and system boot with old initrd again, I load modules with "modprobe qla2300". Will I have problem if I use old initrd and load modules with modprobe?


2.4.9-e.35smp
Red Hat Linux Advanced Server release 2.1AS
rpm -qa | grep qla-->hp_qla2x00src-7.07.03p3-19a

lsmod | grep qla
qla2300_conf 301376 0 (autoclean)
qla2300 611808 0
scsi_mod 126812 4 [sg qla2300 ide-scsi cciss sd_mod]

cat /etc/modules.conf
alias scsi_hostadapter cciss
post-remove qla2300 rmmod qla2300_conf
alias scsi_hostadapter1 qla2300_conf
alias scsi_hostadapter2 qla2300
alias scsi_hostadapter3 sg
options qla2200 ql2xmaxqdepth=16 qlport_down_retry=30 qlogin_retry_count=16 ql2xfailover=1 ql2xlbType=1 ql2xexcludemodel=0x0
options qla2300 ql2xmaxqdepth=16 qlport_down_retry=30 qlogin_retry_count=16 ql2xfailover=1 ql2xlbType=1 ql2xexcludemodel=0x0

[Matti_Kurkela]

You would need the new initrd only if you wanted to have your root filesystem on a disk attached through the FC card.

If you use the server's internal disk(s) for OS and the FC-attached disks contain only application data, you can modprobe the driver and mount the disks later.

Hmm... you are using RedHat AS 2.1. If I recall correctly, you could add the modprobe command to /etc/rc.modules (create it if it does not exist), so it will be run after initrd operations are complete but while only the root partition is mounted. That way, the standard boot process can mount the FC-attached disks according to their fstab entries, just as normal.

[Alan_152]

some of the later qla drivers need a kernel upgrade to work properly as well.