Problems with Highpoint Rocketraid 2210

[rshol]

Running CentOS 5 x86_64 and trying to use a Highpoint Rocketraid 2210. I this has been a major pain.

I got the driver initially installed and running and the OS installed. Now I need to run the utility to complete the install. Hpoint provides two files, a driver daemon and a utility, in this case a cli utility, as rpm's but not speciffically for RHEL or CentOS 5.

First a bonehead problem. When trying to install the driver daemon I installed both the x86_64 and i586 versions. I had to use the options in rpm --nosignature --nodigest to get them to install. Now I can't get rid of them. When I run rpm -ev it says that the packages are uninstalled. But when I run rpm -Uvh it says the packages are already installed. How can I get rid of 'em? (I know that's not really a hardware support question, but I'm getting to one).

So the real question is this. When I upgrade the kernel using yum, I get a kernel panic, not syncing message on reboot. I presume this is because the new kernel is not loading the driver for the controller. How can I configure things so that the new kernel sees the driver?

[rshol]

Got the rpms to uninstall by doing rpm --rebuilddb and then rpm -ev. Rebooted and installed only the x86_64 driver daemon. System still reports it is not loaded. Any hints appreciated.

[rshol]

Got the system daemon running by a more diligent reading of the friendly manual. But the problem still remains about being unable to run and updated kernel. After updating the kernel and rebooting I get the following error message.

Redhat nash version 5.1.19.6 starting
Unable to access resume device (Label=SWAP-sda2)
mount: could not find file system '/dev/root'
setuproot: movind /dev failed: No such file or directory
setuproot: error mounting /procs: No such file or directory
setuproot: error mounting /sys: No such file or directory
switchroot: mount failed: No such file or directory
Kernel panic - Not syncing: Attempted to kill init

I am assuming, although I do not know for sure, that the cause of this is that the new kernel does not know where to find or to load the driver for the Rocketraid, rr2210.ko. Any thoughts on the correctness of my assumption or how to fix the problem appreciated.

[gerroldk]

I have/had exectly the same problem with the rocketraid 1740. I managed to work around the problem by performing the following:
- Copied the rr174x.ko driver file from /lib/modules/2.6.18-8.el5/update to /lib/modules.2.6.18.1.6.el5
- a 'grep rr174x *' on /lib/modules/2.6.18-8.el5, compared to ''grep rr174x *' /lib/modules.2.6.18.1.6.el5
- added 'missing' lines to modules.alias, modules.dep and modules.pcimap

Not sure why/how this helps, but it dis it for me.

Gerrold

[gerroldk]

Running '/sbin/depmod' appears to have the same result on the above mentioned files.

Question remains for me why the yum-update of the kernel does not do this?