[Gllug] megaraid2

[Andrew Halliwell]

And verily, didst Daniel Andersson announce to the hordes:
> have downloaded it, but have no idea how to put it into the kernel
> do i just replace megaraid.c/.h with the megaraid2-stuff?
> anyone know? :)

In what form does it take?
Is it compilable against the kernel as a standalone module (in the same way
that the nvidia kernel module is) or does it need to be implanted into the
kernel tree and made along with the rest?

If the first: Just untar it, cd to the directory and make.
That should be all that's necessary. Then either make install or copy the
resultant .o file into /lib/modules/<kernel-version>/kernel/drivers/scsi/.

If it's one that needs to be copied into the kernel tree, is it a patch or
just a few files to put into the tree?

Anyway, assuming you've made the module and copied it, and assuming the
module is called megaraid2 and doesn't replace the original megaraid driver...
This is where things might get tricky cos you may need a reboot.
This depends on how the disks are setup.
Is there an independent boot drive and the megaraid drives used for storage,
or is it booting off the megaraid drives?

If it's just using the raid drives for storage, umount their partitions,
rmmod megaraid, modprobe megaraid2 and mount them again.

If they mount ok, then you can edit /etc/modules.conf and change
scsi_hostadapter to megaraid2 so it'll load that module at boot.


If the thing's booting off the drives...
It's prolly not a good idea, unless you have someone who can handle a rescue
system sitting by the machine. After all, you'd need to edit modules.conf
changing scsi_hostadapter to megaraid2, and then reboot. The new module will
be loaded and the drives will ATTEMPT to mount... But if the driver fails,
you'll be stuffed without someone there to boot rescue and change the
scsi_hostadapter field back.


-- 
Gllug mailing list  -  Gllug at linux.co.uk
http://list.ftech.net/mailman/listinfo/gllug