Table of Contents
Advertisement
Linux 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 hptiop.o resides and typing in the command
"insmod hptiop.ko". If you are using a distribution with 2.4 kernel, driver file should
be hptiop.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 hptiop.o. Try to load SCSI
modules first.
E.g. # modprobe sd_mod
# insmod hptiop.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 OpenBuild package for RocketRAID 4320 controller.
To ensure the module has been loaded successfully, you can check the driver
status by typing in the command "cat /proc/scsi/hptiop/x", where x is the
filename you found under /proc/scsi/hptiop/. 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 0 array using 2 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.
Step 3 Configure System to Automatically Load the Driver
Most likely, you will not want to type in "insmod hptiop.ko" each time you boot up
the system. Therefore you must install the module and tell the system about it. To
install the module, type in the following commands (first change directory to where
the proper hptiop.ko locates):
#cp -rf hptiop.ko /lib/modules/'uname –r'/kernel/drivers/scsi/
#depmod
6-17
Hide quick links:
Advertisement
Table of Contents
