Linux - EnterpriseThis forum is for all items relating to using Linux in the Enterprise.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have installed 2 FC qlogic cards into a machine running 2xopterons and hardware raid1 ultra320 scsi disks. The scis is shown to trhe system as just one disk. the kernel is 2.6.13 and has both the LSI(scsi raid controller) and the qlogic drivers compiled in statically. When I boot the system with the two FCs connected to my san... i can see the disks that are presented while the machine boots but i think becuase it detects the FCs first it assignes them sda in /dev which was hte original SCSI boot drive and so can get past boot.
I've googled for similar problems and they all revolve around loading the modules in a different order at boot time. But what shuild i do if ive compiled the drivers into kernel statically?
Don't compile them in statically, there's no way you can fix the problem without mucking with the order in which the kernel starts the drivers anyway so the best fix is to just run a modular kernel, like you should anyway.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.