Configuring HP-UX For Peripherals

Chapter 4 107
Configuring Terminals and Modems
Configuring HP-UX for an HP Terminal or for a Modem
Configuring HP-UX for an HP Terminal or for
a Modem
Step 1. Determine which driver is required for the terminal or modem by
consulting Table 4-1, “Serial Configurations for Terminals and Modems.”
Step 2. 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