 |
» |
|
|
|
Begin by reading the system messages displayed by the dmesg command. Then consult this section and “E/ISA Board Power-Up
Messages ” shortly for possible causes and recommended
actions. Verifying
the Syntax of a CFG File | |
If an E/ISA board is not configuring properly, check the CFG file syntax, using the -c option. Note, the eisa_config -c option is useful only for
diagnosing errors in a particular CFG file, not for changing the
configuration. # eisa_config -c HWPC051
Checking this CFG File for correctness:
/sbin/lib/eisa/HWPC051.CFG
Successful syntax verification |
Board Stops
Working or No Non-Volatile Memory (NVM) Driver | |
If a board that was working suddenly stops working or the
system reports that the NVM driver cannot be used, the kernel might
have been altered and now lacks the required device drivers. If
so, you will need to relink the E/ISA board drivers to the kernel. See “Configuring the Software
Required by the E/ISA Board ” or board
documentation supplied by the manufacturer. Added or
Moved Board Does Not Work | |
If you added or moved an E/ISA board that is not working,
check the following: If you added the board using automatic mode, check /etc/eisa/config.err for error messages. Did you add the required drivers to the HP-UX kernel?
If not, see “Configuring the Software
Required by the E/ISA Board ”. If you added the board interactively, did you save
the new configuration before exiting eisa_config? If not, run eisa_config again, add the board again, and then save the
configuration. See "Saving the Configuration and Exiting eisa_config." Did you change any switch and jumper settings to
match the settings specified in /etc/eisa/config.log? If so, verify that you did so accurately. Did you reboot the system after changing the configuration
interactively? If not, reboot the system, taking care to warn users
first. Did you create the necessary device special files
correctly? For HP-supplied boards, insf will have created the necessary device special
files for any attached devices on rebooting. For boards supplied
by a different manufacturer, refer to the documentation shipped
with your board. If the driver is not known to insf, use mknod to create any required device special files.
Board Configuration
Conflicts | |
E/ISA boards use four types of resources: interrupt lines,
DMA channels, register addresses, and memory. If the automatic mode
of eisa_config cannot configure a board due to resource conflicts,
you may still be able to use eisa_config interactively to add a board that had a conflict
or to change choices for a new board. Refer to “Changing
Choices for Board Functions”. If your desired board configuration still causes conflicts,
you may not be able to use certain boards together. Some configurations
are simply not possible; for example, two boards from different
manufacturers may both require the same resource. If this happens,
only one of the boards can be used. Two CFG
Files Have the Same Name | |
If you want to load a CFG file into the /sbin/lib/eisa directory that has the same name as a file already
in that directory, follow these steps: Load the new CFG file from media into a temporary directory. Rename the CFG file, using the same syntax as described in “E/ISA Boards and
CFG Files ”, at the beginning of this
appendix. In the temporary directory, type the following command: Move the renamed CFG file to the /sbin/lib/eisa directory. Type the following command: mv -i newname /sbin/lib/eisa
|
Boards that have duplicate CFG file names must be added using eisa_config interactively (see “Configuring E/ISA
Boards Using Interactive Mode ”) earlier. |
Printable version
