Linux(Fedora,Red Hat,SuSE) Driver Support
Step 2 Test the Driver Module
You can test out the module to ensure that it works for your system by changing
working directory to the location where rr26xx.ko resides and typing in the command
“insmod rr26xx.ko”. If you are using a distribution with 2.4 kernel it should be
“insmod rr26xx.o”.
Sometimes insmod will report “unresolved symbols” when you attempt to load the
module. This can be caused by two ways:
1. You haven’t loaded the SCSI module before loading rr26xx.ko. Try to load SCSI
modules first.
E.g. # modprobe scsi_mod
# modprobe sd_mod
# insmod ./rr26xx.ko
2. You are using a kernel that is build off a different configuration with the driver. In
this case the precompiled drivers cannot be used. You can build a driver for your
kernel using Open Source package for RocketRAID controller.
To ensure the module has been loaded successfully, you can check the driver
status by typing in the command “cat /proc/scsi/rr26xx/x”,where x is the
filename you found under /proc/scsi/rr26xx/. You should see the driver banner
and a list of attached drives. You can now access the drives as a SCSI device (the
first device is /dev/sda, then /dev/sdb, etc.).
Example:
You have configured a RAID 5 array using 4 disks. It will be registered to system
as device /dev/sda. You can use “fdisk /dev/sda” to create a partition on it, which
will be /dev/sda1, and use “mkfs /dev/sda1” to setup a file system on the
partition. Then you can mount /dev/sda1 to somewhere to access it.
6-6
