Configuring HP-UX for an HP Terminal or for a Modem

Determine which driver is required for the terminal or modem by consulting Table 3-1 “Serial Configurations for Terminals and Modems”

Determine whether the driver is present in the kernel by invoking the command, /usr/sbin/ioscan -fn -C tty, from the system console or any login to the system using an active terminal.

If the necessary driver is present in the kernel (likely), the ioscan output of a Series 700 might resemble this:

/usr/sbin/ioscan -d asio0 -fn
 
Class     I  H/W Path  Driver       S/W State  H/W Type  Description
=========================================================================
tty       0  2/0/4     asio0        CLAIMED   INTERFACE  Built-in RS-232-C
                      /dev/tty0p0
tty       1  2/0/5     asio0        CLAIMED   INTERFACE  Built-in RS-232-C
                      /dev/tty1p0

Similarly, the ioscan output of a Series 800 system might resemble this:

/usr/sbin/ioscan -d mux4 -fn
 
Class     I  H/W Path  Driver       S/W State  H/W Type   Description
=====================================================================
tty       0  56/0     mux4          CLAIMED    INTERFACE  MUX
                      /dev/diag/mux0     /dev/diag/tty0p0   /dev/tty0p0
                      /dev/diag/tty0p1   /dev/mux0          /dev/tty0p1

The -fn option caused ioscan to display the device special files created by insf. insf automatically creates device special files appropriate for terminals at each serial port. The sample device special file highlighted communicates with port 1 (p1) of the MUX card found at card instance 0 of tty class.

You can display the device file's characteristics by invoking /usr/sbin/lssf on the file. By comparing lssf and ll output, you can see that bits 16 to 23 of the minor number (0x000100) correspond to the port number of 1. (See Appendix C for explanation of bit assignments.)

/usr/sbin/lssf /dev/tty0p1
mux4 card instance 0 port 1 hardwired at address 56/0 /dev/tty0p1
 
ll /dev/tty0p1
crw-rw-rw-   1 bin      bin      178 0x000100 Mar 16 18:29 /dev/tty0p1

If you are configuring a terminal without having to install an interface card, you can physically connect the terminal, as described in its owner's manual. Then, skip ahead to “Additionally Configuring HP-UX for a Terminal”, the next section.
If you are configuring a modem to an existing port, note the hardware address (or card instance number) and port number you will be using from the ioscan output. Then, skip ahead to “Additionally Configuring HP-UX for a Modem”, later in this chapter.

If the necessary driver is not present in the kernel, and is a static driver, you will need to rebuild the kernel to include the additional driver. If the driver is a dynamic driver, no rebuild is necessary. (This situation might occur if you have to add hardware to configure additional terminals or if you are running a minimal kernel.)

To rebuild your kernel and include an additional driver, here is what to do:

Identify the needed driver by consulting the table in “Selecting Device Drivers for Terminals and Modems”, earlier in this chapter.
Change directory to the build environment (/stand/build). There, execute a system preparation script, system_prep, which extracts the system file from the current kernel and writes a system file in your 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.
/usr/sbin/kmupdate

Bring down the system with sufficient grace period to allow users to exit their files. You can execute /usr/sbin/shutdown -r or /usr/sbin/reboot.
If you are installing an interface card, bring the system to a halt (that is, use the -h option). See shutdown(1M) or reboot(1M) in the HP-UX Reference. Power off all peripherals, and then the SPU. Perform the physical installation, as described in the hardware manual accompanying the interface card or other device. Power on all peripherals, and then the SPU.
Once the system boots from the newly created kernel, HP-UX detects the new terminal and associates it with its driver. insf automatically creates the device special files necessary to communicate directly with the terminal.
Invoke /usr/sbin/ioscan -C tty -fn to confirm that the I/O subsystem finds the terminal. Your output should now resemble the ioscan output shown in step 2.
Proceed to “Additionally Configuring HP-UX for a Terminal” or “Additionally Configuring HP-UX for a Modem” (later in this chapter), depending on which device you are configuring.

Configuring HP-UX for an HP Terminal or for a Modem

Technical documentation

» Table of Contents

» Index