Determine the interface driver needed for your interface card
by consulting the tables in “Selecting Device Drivers for Your Interface Cards”.
Look at your /stand/system file to see if the required driver is present. (If you
are also adding an external device such as a printer, consult the tables
in the appropriate chapter and look for the presence of those drivers
in /stand/system also.)
If any necessary static driver is absent, you will need
to rebuild the kernel to include it.
Here is how to rebuild the kernel:
Change directory to the build environment
(/stand/build). There, execute a system preparation script, system_prep. system_prep writes a system file based on your current kernel in
the current directory. (That is, it creates /stand/build/system.) The -v provides verbose explanation
as the script executes.
cd /stand/build
/usr/lbin/sysadm/system_prep -v -s system |
Modify the /stand/build/system file to add the absent driver(s) by invoking the kmsystem command. The -c Y specifies that driver-name
is to be configured into the system.
/usr/sbin/kmsystem -S /stand/build/system -c Y driver-name |
 |
| |
|
 | NOTE: To avoid introducing format errors, do not edit the
HP-UX system description files directly. Instead, use the commands kmsystem and kmtune. These commands are new for Release 11.0; consult kmsystem(1M) and kmtune(1M) in
the HP-UX Reference. |
|
| |
|
Build the new kernel by invoking the mk_kernel command. This action creates /stand/build/vmunix_test, a kernel ready for testing.
/usr/sbin/mk_kernel -s /stand/build/system |
Save the old system file by moving it. Then move the
new system file into place.
mv /stand/system /stand/system.prev
mv /stand/build/system /stand/system |
Prepare for rebooting by invoking the kmupdate command. This action sets a flag that tells the system
to use the new kernel when it restarts.
Notify users that the system will be shut down to configure
the new interface card and any related peripheral device. You can
use the wall command and/or the interactive capabilities of the shutdown command to broadcast a message to users before the system
goes down. See wall(1M) or shutdown(1M) in
the HP-UX Reference.
Bring the system to a halt, using the shutdown command.
Turn off the power to all peripheral devices and then to
the SPU. On systems with powerfail mode, turn off the battery back-up
also. Unplug the power cords.
Select an appropriate slot in the I/O card cage and install
the interface card, following instructions provided with the card
and computer hardware manual.
If you are also configuring a peripheral device to the card,
install it at this time also. Use the cabling recommended in the
hardware documentation.
Record all pertinent information about the installation and
configuration on a worksheet at the back of this document. Keep
accurate records of the interface (as shown on the ID stickers),
slot number, power requirements, and bus address.
Turn on the power to all peripheral devices. Wait for them
to become "ready", then turn on power to the
card cages and SPU.
On booting up, HP-UX detects the new interface and peripheral
device and associates them with their device drivers. insf creates the device special files required to communicate
with the devices.
Verify the configuration by invoking the ioscan command to confirm that the interface card (and any peripheral
devices you configured) are present and device special files have
been created.
In the following sample ioscan output, the LAN card installed in slot 14 of a Model
887 is displayed as hardware path 56 (slot number
times 4).
/usr/sbin/ioscan -C lanmux -f
Class I H/W Path Driver S/W State H/W Type Description
==============================================================
lanmux 0 56 lanmux0 CLAIMED INTERFACE LAN/Console |
For more information on using ioscan, consult Chapter 1 “Getting Started”and the ioscan(1M) manpage.
Printable version
