I downloaded the rpm files then used rpm2tgz to make slackware packages.

Resurrecting this thread because the RocketRaid driver is also broken in the 2.6.38 kernel branch. Down this patch to fix the RocketRaid driver. The patch also includes the .37 patch posted by Niel.

Thanks, tux_dude!

I'm going to switch over to a 2.6.38 kernel over the next few days myself and will take a look at this.

Could someone post a patch for the rr62x?

thanks Tux_dude the patch worked.

Managed to get it to patch the rocket raid 622 source and installed. Back in working order

That patch link appears to be dead. Any chance someone can repost the patch on a more permanent page? or perhaps email it to me at kushieda @ zetsuboushita . net

Link to patch worked fine just now...

I get connection timeouts trying to access it. when I try to visit the parent domain homeunix.net I get redirected to http://free.domain.name/

OK, just sent it to your e-mail...

Thank you!

Thank you for this solution Mr. Horn. I suspect this will do the trick for me. Unfortunately, I'm such a flaming rookie that I don't know how to apply it. I'm a junior Windows systems admin tinkering with Linux and trying to go deeper down the "penguin hole," as it were. I have no programming skills to speak of, which is probably why trying to apply this patch just leaves me with questions.

I'm running kernel 2.6.37.1-1.2-desktop from openSUSE 11.4, with a RocketRaid 2320 card installed which was previously being used by a Windows XP x64 partition.

Niels Horn's patch looks to me either like C code, or a shell script. Does "Make" automatically recognize the directories the script calls, and integrates this code into the "osm_linux.c" code file, or must the user inject the patch text manually into osm_linux.c?

Thank you in advance!

Hi,

Patches are normally applied to the source code after "unpacking" the source (usually supplied as a "tarball" - something similar to a "zipped file" in Windows) and before building the sources.
The program to apply the patches is called "patch".

To know how the patch program works, type "man patch" in a terminal screen.
Usually it is done with:
patch -p1 < (name_of_patch_file)

Hope this helps you a bit!

Niels

Greetings.

Took me a lot of needle-in-the-haystack probing, but I found out about the patch program and it was exactly what I needed!

I compiled the driver and it works like a charm; no kernel panic and I can see all my array disks in /dev.

Awesome work! Thanks again.

Is there anyone that can email the patch to testonej (at) gmail.com. I would be happy to post it in a permanent location and post the link here.

Thanks!

Just sent it...