QLA2462 dual port 4Gb/s FC HBA, Red Hat EL 4 update 4 hardware false detect
Hi,
I am using a QLA2462 dual port 4Gb/s FC HBA with the latest driver from the QLogic website for Red Hat Eneterprise Linux 4 64 bit edition update 4.
Upon booting the system detects the QLA2462 as a 23## series card. The system loads the built in default 23## series drivers. These leaves the HBA unuseable, I cannot connect to it in SAN surfer nor can it detect any devices connected to it.
My solution is to edit the /etc/rc.local file and unload the 23## series driver and then load the correct driver using the "modprobe" command.
The HBA then works fine.
I consider this to be somewhat short of an elegant solution.
What I would like to do is find out at what stage the incorrect driver is being loaded and stop it then, and then load the correct driver.
At the moment I am not booting from the SAN that I am connecting to but I may wish to do so in the future. I assume that I would need to fix this before I could do that.
Could someone please give me some advice about how to stop the kernel loading this incorrect driver and to force it to load the correct driver early enough in the startup process so that I can access the filesystems onboard the SAN connected to the QLA2462?
I have been told that there was a bugzilla about this when update 4 came out and that hwdata-0.146.23.EL-1 addresses it.
The following is the contents of the modprobe.conf file:
alias eth0 tg3
alias eth1 tg3
alias scsi_hostadapter1 ips
alias usb-controller ehci-hcd
alias usb-controller1 uhci-hcd
alias scsi_hostadapter2 aic79xx
#install qla2xxx /sbin/modprobe qla2xxx_conf; /sbin/modprobe --ignore-install qla2xxx
#remove qla2xxx /sbin/modprobe -r --first-time --ignore-remove qla2xxx && { /sbin/modprobe -r --ignore-remove qla2xxx_conf; }
#alias scsi_hostadapter3 qla2xxx_conf ql2xfailover=0
The 3 entries that are commented out were put in by the Qlogic driver automatically.
The following is the contents of the /etc/rc.local file:
#!/bin/sh
#
# This script will be executed *after* all the other init scripts.
# You can put your own initialization stuff in here if you don't
# want to do the full Sys V style init stuff.
modprobe -r qla2322
modprobe -v qla2400
touch /var/lock/subsys/local
As you can see I am unloading the 2322 driver and loading the correct.
The system will load the qla2xxx and qla2400 drivers. I am not 100% but think the 2xxx drivers is the driver which you pass configuration settings such as failover control etc to.
Any suggestions how I can modify my system to fix this problem?
Thanks,
Steve
|