Troubleshooting
Appendix B
VME-SB2020/NI-VXI Solaris Getting Started
B-2
© National Instruments Corporation
If the driver is not in memory and you are using Solaris 1.x, use the command
nivxi.LOAD
to
load the driver. If you are using Solaris 2.x, or if
nivxi.LOAD
did not load the driver, there is a
problem with the system configuration. Check your installation and check with your system
administrator.
If the driver is loaded in memory, the version may have become corrupted. Proceed by
unloading and then reloading the driver as described in Chapter 3.
vxiinit Cannot Find libnivxi.so
When using
vxiinit
, you may receive the following error message:
ld.so.l: vxiinit: fatal: libnivxi.so: can't open file: errno = 2
This message is caused by the driver being unable to find the shared object file,
libnivxi.so
.
Check to make sure the environment variable
LD_LIBRARY_PATH
is pointing to the directory
containing the NI-VXI software. Refer to the Using the NI-VXI Software section of Chapter 3
for more information.
Note:
This error message can also occur when using
resman
or
victext
.
Problems when Using resman
If you receive errors or warnings from
resman
, the problem could be in a number of areas. The
first thing to remember is that
resman
is a Resource Manager for VXI systems. Because you
are using a VME system, if you receive a warning that
resman
cannot find a Slot 0 device, or
that devices are not responding to MODID lines, you can ignore these warnings. These items are
relevant to VXI systems only.
If you receive warnings other than those just discussed, you may have resource conflicts between
the SB-MXI and the VME chassis in your system. First make sure that you have used the
non-VXI Device Editor in
vxitedit
to inform
resman
of the memory requirements of all
the non-VXI devices in your system.
Another cause can be due to system conflicts with the SB-MXI configuration. If you have
verified that you do not have a conflict with any of the SB-MXI configuration settings, your
problem might be with the MXIbus cables in your system.
The following symptoms can indicate a problem with the MXIbus cable:
•
resman
finds the SB-MXI board at Logical Address 0 but does not detect the VXI/VME
chassis.
•
resman
previously worked, but now produces errors.
