[Rocks-Discuss] Adding drivers to compute node using driver disk image without driver source
Brett Whitty
I'm attempting to add a compute node to an existing Rocks 5.2 cluster
that has an LSI SAS2008 RAID controller (it's a Supermicro blade
server). This requires having the mpt2sas drivers at boot time for the
drives to be recognized. Fortunately, Supermicro has an mpt2sas RHEL
5.3 driver disk available (and I've found how to strip the signatures
so that it'll work with CentOS 5.3). Unfortunately, the Rocks
documentation I've been able to find only tells me how to get drivers
installed and into the boot images if I've got the source code, which
I don't have (and haven't had much luck getting after some
correspondence with Supermicro).
I have a general idea that I can inject the mpt2sas .ko files into
modules.cgz in the boot image (and modify the relevant conf files),
and have played with this a little bit, but that's deeper than I'd
like to go with it at the moment if I don't have to.
So my questions are:
Can I make the driver disk image that I have available to the
installer at PXE boot time in some automated fashion to get these
drivers installed?
Can I do something different with the rocks repository build that
doesn't require having the driver source, but lets me use the binaries
from the driver disk instead?
Or failing that, assuming CentOS 5.4 is released in a month, how soon
after can we expect a Rocks release that will incorporate it? (just
looking for a guesstimate)
Thanks,
Brett
P.S.: In follow up to my previous post a few weeks back about having a
broken installer during the Rocks 5.2 upgrade --- it was my restore
roll. There was a rogue RPM polluting my contrib dir, and once that
was removed and the repository was rebuilt, everything was cool after
that. Thanks guys for pointing me in the right direction.
H.G Li
As I known that the binary driver disk, which released for CentOS 5.2, is
not work for ROCKS 5.1. I installed the driver with command "build dd" , and
then provide the driver with an floppy. But the installer complaint "The
driver disk is invalid for this release of ROCKS". I even try to rebuild a
new kernel with the
driver source code, but I failed.
Finally, I extract the "pcitable", "moduleinfo" and other files, expect the
binary driver module, from the binary driver disk. Then downloaded the ROCKS
source tree , and patched the driver module file into the "initrd.img". It
works correctly for me.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.sdsc.edu/pipermail/npaci-rocks-discussion/attachments/20090924/978e99a7/attachment.html