User manual

You can check that the driver is loaded properly with lsmod.
/sbin/lsmod | grep acqrsPCI
If lsmod does not report a module named acqrsPCI, then the kernel module is not loaded into the kernel. Read the
section below.
You can check that a device node has been created.
ls -l /dev/acqrsPCI
If the device node /dev/acqrsPCI is not present on your system, the Acqiris Software will not be able to access
the device. Read more in the section below.
The drv-install script has the following additional functionality:
drv-install rem to remove the driver and load script
drv-install res to restart the driver
Loading the module into the kernel
If you are running a Linux distribution that does not use the standard paths for the load scripts, you have to load the
device driver manually.
The kernel module should be present in the kernel modules directory. Check with the following command:
ls -l /lib/modules/$(uname -r)/extra/acqrsPCI.ko
First update the kernel modules dependencies:
/sbin/depmod -a
Then load the kernel module:
/sbin/modprobe -v /lib/modules/$(uname -r)/extra/acqrsPCI.ko
The acqrsPCI kernel module should now be loaded correctly. Check with lsmod.
You can add the command above to your /etc/rc.local file. It is run at system startup and will load the
acqrsPCI kernel module automatically when your computer is restarted.
Creating the device driver node
For systems using udev (the dynamic /dev/ hierarchy) or running kernels above 2.6.17, the device driver node may
not be created automatically. You can do it with mknod running the following command:
/bin/mknod -m 666 /dev/acqrsPCI c 124 0
You can check that the device node has been created:
ls -l /dev/acqrsPCI
You can add the mknod command to your /etc/rc.local file. It is run at system startup and will create the
/dev/acqrsPCI device node automatically when your computer is restarted.
Note that the permissions that are set in this example (-m 666) gives access to the Acqiris instruments to all the users.
This may not be what you expect and these permissions can be adjusted to fit your requirements. The basic rule is
that any user that wants to use the Acqiris instruments has to get read and write access to /dev/acqrsPCI.
2.3.3. Environment variables for the Firmware
Automatic loading of the firmware needed by 12-bit, analyzer, and averager modules relies on the environment
variable AcqirisDxDir pointing to the directory containing the file AqDrv4.ini which in turn points to the directory
containing the Firmware .bit files. Therefore, assuming that your Firmware is in /usr/local/AcqirisLinux/Firmware
and that AqDrv4.ini is in /usr/local/AcqirisLinux/demo then you must edit AqDrv4.ini so that it contains the line
fpgaPath=/usr/local/AcqirisLinux/Firmware
Then, if your shell is csh or tcsh modify the /etc/csh.login file to contain the line
setenv AcqirisDxDir /usr/local/AcqirisLinux/demo
or, if your shell is bash, ksh, zsh or sh, modify the /etc/profile file to contain the lines
AcqirisDxDir=/usr/local/AcqirisLinux/demo
export AcqirisDxDir
User Manual: Agilent Acqiris 10-bit Digitizers Page 13 of 43