[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
qla2xxx/2300 and persistent binding
- From: Jussi Silvennoinen <jussi_nahant silvennoinen net>
- To: nahant-list redhat com
- Subject: qla2xxx/2300 and persistent binding
- Date: Wed, 19 Apr 2006 21:26:15 +0300 (EEST)
Hello,
how does one do persistent binding from qla2xxx/2300 on RHEL4
(2.6.9-34.ELsmp.i686)?
scli doesn't work because /dev/qla2xxx is not there, neither does
sansurfer. This is because of the drivermutilation I presume.
Both utilities work fine with the driver available from qlogic's site.
This sort of mutilation which prevents hardware configuration utilities
from being used is most annoying and frankly ADOLESCENT behavior.
I suppose my only course of action is to open up a support request and
spend three days serving their "further information" inquiries and end up
having my hat handed to me with "no it doesn't work" answer.
I suppose I could rig up a shellscript which is run during bootup which
checks is the driver the mutilated one or proper one from qlogic and
compiles&replaces it if needed but I'd rather not go in to that with
hardware which is supposed to be supported. I already have similar things
done for the unsupported hardware in our datacenter (Areca, SSD).
--
Jussi
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]