[Log in to get rid of this advertisement]

Hi there,

I was wondering if anybody had this problem: I'm trying to compile Highpoint Rocketraid 2310 driver v2.2 on CentOS 5.3 x86_64 (kernel 2.6.18-128.el5). When I run make I get this warning:

and make install gives me this error:

Did anyone else have this problem and how did you fix this?

Thanks in advance.

It seems you need to build the sata_mv module for your kernel. I found some info about it here:
http://hardware4linux.info/module/sata_mv/
You can see if that matches the hardware you are using.
cheers,
jdk

Well, the thing is sata_mv is loaded into kernel already but make doesn't find it for some reason. How could I "tell" it that's the module is actually present? Thanks.

What is the output of the above command?
cheers,
jdk

Why bother? It's "fake RAID":
http://linuxmafia.com/faq/Hardware/s...#highpoint2310

I would either take it back, complaining bitterly that selling "fake RAID" cards is tantamout to fraud;
or just use it as an expensive disk controller for Linux s/w RAID.

BTW, I got sucked in by a "works w/ Linux" claim on the box of an earlier Highpoint Rocketraid card.
It's "fake RAID" & not worth the money paid for the card, nor the time to compile the driver.

http://www.google.com/linux?q=%22fake+RAID

This one gave me a little bit of a headache so I thought I'd post some notes from my experience with a RocketRaid 1740 PCI card on CentOS 5.4.

First, some clarification on the error. The message "No module sata_mv found for kernel..." is from mkinitrd. It is unhappy because the "sata_mv.ko" module is missing and there is still a dependency for it. The module is missing because the install script you just ran... deleted it. This is actually okay for the most part since that module is very incompatible with the one from highpoint. So basically, you don't have or want the sata_mv module, you just want to tell your system to ignore it.

The good thing about this error is that it happens at the very last stage of the install script. This means that the module is very likely already compiled and installed in the correct location. Your kernel version and card type will vary but the path is probably something like...
/lib/modules/2.6.18-164.el5/kernel/drivers/scsi/rr174x/rr174x.ko

I haven't figured out how to properly remove the dependency for sata_mv but was able to get around it by specifying the "--builtin=sata_mv" option to mkinitrd. I don't really like the idea of telling the system a module is built into the kernel when in fact it's actually missing. You may want to "blacklist" sata_mv which might help prevent devices even trying to bind to it. Anyway if you have the module in the correct location you can now run mkinitrd by hand or you can edit the install script and re-run "make install".

The install script is triggered by "make install". It is located at "osm/linux/install.sh" in the package folder and is also kinda lame. It actually renames your ramdisk module image in "/boot" before successfully creating a new image. That means that if you get this error you should NOT reboot your machine until renaming the boot image back to match your kernel. Anyway, whenever I use this script I modify it in a few ways. I replace any calls to "modinfo" with "/sbin/modinfo" and "mkinitrd" with "mkinitrd --builtin=sata_mv". I usually have the appropriate sbin folders in the path but, like I said, this script is kinda lame. Make sure you check the locations for those commands on your system before making changes. Also, when I run "make install" I don't use sudo but instead become root using "su -".

As a side note, it may be possible to totally avoid this issue by simply installing linux with your raid card detached. For obvious reasons, this isn't an option for everyone.


p.s. It's not related to compiling this module but with this card and my hardware I needed to add the kernel argument "edd=off" after my system began to hang during boot.