I've got the exact same problem here. On this same machine, I was,
before, able to see the emulex HBA. We had to change them for the
QLogic, and since then nothing! I can see that ql2300_conf is loaded
with lsmod, but that's it.

got any luck since your post!?

M. Masson

[root@whml1310 root]# uname -a
Linux whml1310 2.4.21-27.ELsmp #1 SMP Wed Dec 1 21:53:57 EST 2004
x86_64 x86_64 x86_64 GNU/Linux

[root@whml1310 root]# lspci -v
....

21:01.0 Fibre Channel: Unknown device 0076:0300 (rev 01)
Subsystem: QLogic Corp.: Unknown device 0009
Flags: bus master, 66Mhz, medium devsel, latency 64, IRQ 32
I/O ports at 3000 [size=256]
Memory at e5b00000 (64-bit, non-prefetchable) [size=4K]
Expansion ROM at [disabled] [size=128K]
Capabilities: [44] Power Management version 2
Capabilities: [4c] PCI-X non-bridge device.
Capabilities: [54] Message Signalled Interrupts: 64bit+
Queue=0/3 Enable-

29:01.0 Fibre Channel: Unknown device 0076:0300 (rev 01)
Subsystem: QLogic Corp.: Unknown device 0009
Flags: bus master, 66Mhz, medium devsel, latency 64, IRQ 40
I/O ports at 4000 [size=256]
Memory at e8001000 (64-bit, non-prefetchable) [size=4K]
Expansion ROM at [disabled] [size=128K]
Capabilities: [44] Power Management version 2
Capabilities: [4c] PCI-X non-bridge device.
Capabilities: [54] Message Signalled Interrupts: 64bit+
Queue=0/3 Enable-


[root@whml1310 root]# lsmod
Module Size Used by Not tainted
loop 12592 0 (autoclean)
button 4336 0 (unused)
autofs4 16944 0 (autoclean) (unused)
audit 127112 2
tg3 63568 1
floppy 62104 0 (autoclean)
sg 37880 0 (autoclean)
keybdev 3104 0 (unused)
mousedev 6728 0 (unused)
hid 21768 0 (unused)
input 7520 0 [keybdev mousedev hid]
usb-ohci 22928 0 (unused)
usbcore 85152 1 [hid usb-ohci]
ext3 87856 5
jbd 56832 5 [ext3]
qla2300_conf 301688 0
mptscsih 43856 6
mptbase 44064 3 [mptscsih]
diskdumplib 6548 0 [mptscsih mptbase]
sd_mod 14836 12
scsi_mod 129348 -2 [sg mptscsih sd_mod]

[root@whml1310 root]# modprobe qla2300
/lib/modules/2.4.21-27.ELsmp/kernel/drivers/scsi/qla2300.o:
init_module: No such device
Hint: insmod errors can be caused by incorrect module parameters,
including invalid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg
/lib/modules/2.4.21-27.ELsmp/kernel/drivers/scsi/qla2300.o: insmod
/lib/modules/2.4.21-27.ELsmp/kernel/drivers/scsi/qla2300.o failed
/lib/modules/2.4.21-27.ELsmp/kernel/drivers/scsi/qla2300.o: insmod
qla2300 failed