Emmer

Here the rr2680 drivers : https://download.xpenology.fr/drivers/rr2680.ko Same warning has before (viewtopic.php?f=2&t=1361&hilit=rocketraid&start=580#p42804), unload mvsas module before loading rr2680.ko ! Thank you very very much.

I'm having a lot of trouble getting this one compiled http://www.highpoint-tech.com/BIOS_Driv ... _24.tar.gz downloaded the source and toolchain and make cross_compile=toolchain kerneldir=source/linux-3.10.x but nothing happens, i think there might be something wrong with the driver package, but i could be doing something really stupid. if anybody has some tips or a vm to cross compile for 5.2 that would be great

Hi @R&R, I've been trying to get the driver for rr2680 compiled but it's getting very frustrating, do you have any tips on how to go about it? the things come in sort of packed automatic installer files. i get the drivers out, but when i try to crosscompile with the right toolchain, and the right kerneldir it just does nothing when you press enter. compiling it against the running kernel works just fine. Any help would be very much apreciated

Hello there, I'm not sure if i'm posting in the right place, but it's about nanoboot anyway. I've compiled a driver with the tools and kernel sources of dsm, for highpoint rocketraid 2600 So now i have a .ko driver which i can insmod, which works fine, and if i put it in /etc/rc everything is pretty much seamless. However, i've been trying to compile it into the kernel and boot image. And i haven't been able to do so. The tiny wiki about it is not extremely descriptive, except for compiling a new kernel, not adding drivers. So i've been wondering, is there anybody that might be able to help me with this? It's been several years since i've been fiddling with kernel mods so i'm quite rusty. The point where i'm sortof stuck at is how you would get your new driver to show up in the menuconfig, so you can check it to compile as a module. Theres a patch script that comes with the highpoint sources, which i could probably modify to run against the source tree of the non running kernel. If that's the way it's done then i'll go do that, but i'm sure there must be an easier way to accomplish this that i'm missing. So any help would be much apreciated. If anybody else wants the compiled driver give me a shout and i'll go find a fileshare site somewhere to put it on. thanks