Problems with Highpoint Rocketraid 2210
Posted: 2007/06/07 04:35:43
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?
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?