Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
Configuring HP-UX For Peripherals: HP 9000 Computers > Chapter 1 Getting Started

Configuring HP-UX for any Peripheral (A Summary)

» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Index

Prepare by gathering information required for the successful configuration of the peripheral. Considerations vary and are discussed in each peripheral-specific chapter. For example:

  • Have you prepared the physical location for the peripheral device?

  • To what interface are you connecting the peripheral?

  • What device drivers are required by the peripheral device?

In virtually all cases, the System Administration Manager (SAM) provides the simplest interface for configuring HP-UX for any standard peripheral device. If you must use the command line interface instead of SAM, the following procedure will familiarize you with the task.

  1. Determine the device drivers needed for your peripheral device and interface by consulting the tables in the chapter devoted to that class of peripheral device. If any necessary static device driver is absent from the kernel, you will need to rebuild the kernel to include it.

    Here is how to rebuild the kernel:

    1. 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
    2. 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.
    3. Build the new kernel by invoking the mk_kernel command. This creates /stand/build/vmunix_test, a kernel ready for testing.

      /usr/sbin/mk_kernel -s /stand/build/system
    4. 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
    5. Prepare for rebooting by invoking the kmupdate command. This sets a flag that tells the system to use the new kernel when it restarts.

      /usr/sbin/kmupdate
  2. Notify users that the system must be rebooted.

  3. Shut down and halt the system using the /usr/sbin/shutdown -h command.

    1. When HALTED, you may cycle power appears on the screen, turn off the computer and unplug the power cord. This is recommended for all devices; for SCSI devices and interface cards, it is required.

    2. Install the peripheral device, following directions in the supplied hardware documentation.

    3. Power on the peripheral devices and wait for them to signal ready; then power on the computer system, which will cause your system to reboot. As HP-UX reboots, it will create the device special files required by the new peripheral device in the appropriate /dev directories.

      NOTE: Before attempting to reboot using the new kernel, the system startup scripts save a copy of the old kernel in /stand/vmunix.prev. If the new kernel won't boot, use this copy of the old kernel, together with the copy of the old system file you saved in /stand/system.prev, to restart the system.
  4. Verify the configuration by invoking the ioscan command, as discussed earlier in this chapter.

Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 2000 Hewlett-Packard Development Company, L.P.