New hardware support provides the kernel modules required for your system to communicate with new hardware without the need to upgrade to a new version of the operating system.
This chapter provides the information necessary for you to perform the following user actions:
Understand new hardware support concepts.
Know what to do before you install a New Hardware Delivery kit.
Be able to install a New Hardware Delivery kit onto a running system.
Be able to install a New Hardware Delivery kit while performing a full installation.
3.1 New Hardware Support Overview
All system hardware requires supporting modules in the operating system kernel. Without this kernel support, the operating system cannot interact with the hardware and may fail to function altogether.
A New Hardware Delivery kit includes kernel modules that let your system support new or upgraded hardware without updating to a new version of the operating system. The kit is distributed on CD-ROM and can be installed directly from the distribution media.
The New Hardware Delivery kit lets you install new hardware support without reinstalling
the base operating system.
However, you must reboot your system to build a
kernel that includes the modules that support your new hardware.
The
bootlink
process builds a generic kernel in memory, using generic
kernel modules along with those included in your New Hardware Delivery kit.
This bootlinked
kernel is not written to disk, but allows the
boot
utility
to include the hardware support modules into your running kernel.
Note
If you need to boot
genvmunix
at any time after you have installed hardware support using the New Hardware Delivery process, the products you have installed will no longer be recognized by the system. To access all of the kernel modules supplied bygenvmunix
and the kernel modules you have added using the New Hardware Delivery process, you must boot/GENERIC
using the following command:boot -fi GENERIC
3.2 Hardware Support Installation Prerequisites
Before you install a New Hardware Delivery kit, do the following:
Back up your system.
Have in your possession the New Hardware Delivery kit.
Determine the name of the New Hardware Delivery kit that you want to install. For this version of the New Hardware Delivery software, the kit name is:
/V4.0F/usr/sys/hardware/base.kit
Shut down your system and obtain the following information from the system console:
Determine if the
bootdef_dev
console variable
is set.
To find out, enter the following command at the console prompt:
>>> show bootdef_dev
Your output will be similar to the following:
bootdef_dev dka0.0.0.1001.0
In this example, the
bootdef_dev
console variable is set to
dka0.0.0.1001.0
.
If the
bootdef_dev
console variable is not set, you must
determine the console device name of your system disk.
To determine the console name of your system disk, enter the following command at the console prompt:
>>>
show dev
Your output will be similar to the following:
dka0.0.0.1001.0 DKA0 RZ28D 0010
dka500.5.0.0.1001.0 DKA500 RRD46 0557
dva0.0.0.0.1 DVA0
ewa0.0.0.1000.0 EWA0 hw_ethernet_address
pka0.7.0.1001.0 PKA0 SCSI Bus ID 7 5.01
pkb0.7.0.1001.0 PKB0 SCSI Bus ID 7 5.01
Hard disk drive types have an
RZ
prefix; in this
example, the console device name of the RZ28D-type hard disk drive is
DKA0
.
Determine if the
auto_action
console variable
is set to
HALT
.
To find out, enter the following command
at the console prompt:
>>>
show auto_action
Your output will be similar to the following:
auto_action BOOT
In this example, the
auto_action
console variable
is set to
BOOT
.
If the
auto_action
console variable is not set to
HALT
, enter the following command at the console prompt:
>>> set auto_action HALT
Determine the console device name of your CD-ROM drive or the local disk drive that contains the New Hardware Delivery kit. To find out, enter the following command at the console prompt:
>>>
show dev
Your output will be similar to the following:
dka0.0.0.1001.0 DKA0 RZ28D 0010
dka100.1.0.0.5.0 DKA100 RZ28D 0372
dka500.5.0.0.1001.0 DKA500 RRD46 0557
dva0.0.0.0.1 DVA0
ewa0.0.0.1000.0 EWA0 hw_ethernet_address
pka0.7.0.1001.0 PKA0 SCSI Bus ID 7 5.01
pkb0.7.0.1001.0 PKB0 SCSI Bus ID 7 5.01
CD-ROM drive types have an
RRD
prefix; in this
example, the console device name of the RRD46-type CD-ROM drive
is
DKA500
.
Local disks have an
RZ
prefix; in this example, the
console device name of the RZ28D local disk drive is
DKA100
.
3.3 Adding Hardware Support to a Running System
Before you follow the procedure in this section, make sure that you have completed the applicable prerequisite tasks in Section 3.2.
Follow these steps to install a New Hardware Delivery kit:
Log in as
root
or use the
su
command to gain superuser privileges.
Use the
shutdown
command to halt your system:
% shutdown -h now
Enter the following command at the console prompt:
>>> set auto_action halt
Turn off your system, unplug all power cords, and follow the instructions in the hardware documentation to install the new hardware. Reconnect all power cords and turn on your system.
Enter the following command at the console prompt:
>>> boot -flag fax -file GENERIC CD-ROM_device
The following list describes this command line:
The
-flag fax
option defines boot flags:
f
for a New Hardware Delivery kit,
a
for multiuser mode, and
x
to boot a different
osf_boot
file.
The
-file GENERIC
option tells the kernel
to bootlink using the file
GENERIC
.
The optional CD-ROM_device argument is the console device name of your New Hardware Delivery kit device.
After the boot process
starts, the
boot
utility issues the following prompt:
Enter Device Name:
Enter the console device
name for the CD-ROM drive or local disk that contains the New Hardware Delivery kit,
such as
DKA500
, and press
[Return].
The
boot
utility issues the following prompt:
Enter Kit Name:
Enter the name of the New Hardware Delivery kit that you
want to install and press
[Return].
For Tru64 UNIX Version
4.0F systems, the kit name is:
/V4.0F/usr/sys/hardware/base.kit
The
boot
utility issues the following prompt:
Insert media for kit 'device:hw_kit_name', press Return when ready:
In this prompt, device is the device name that you entered in step 6, and hw_kit_name is the New Hardware Delivery kit name that you entered in step 7.
Press
[Return].
The
boot
utility reads
the selected New Hardware Delivery kit information into memory.
The
boot
utility reissues the
Enter Kit Name:
prompt.
Press [Return] and continue to the next step.
The
boot
utility reissues the
Enter Device Name:
prompt.
Press [Return] and continue to the next step.
The
boot
utility issues the following prompt:
Insert boot media, hit <return> when ready:
Because you are adding hardware support to a running system and the system disk is your boot media, just press [Return]. The generic kernel modules are read so that the bootlink process can build the kernel in memory in the next step.
The
boot
utility links the kernel objects
and issues the following prompt:
Insert media for kit 'dev_name:hw_kit_name', press Return when ready:
In this prompt, dev_name is the device name that you entered in step 6 and hw_kit_name is the New Hardware Delivery kit name that you entered in step 7.
Press [Return]. The New Hardware Delivery kernel modules are read and the bootlink process builds the kernel in memory.
The
boot
utility issues the following prompt:
Insert boot media, press Return when ready:
Because
the boot media is still your installed system disk, just press
[Return].
The
boot
utility loads and configures the New Hardware Delivery
kit.
Note
During this step of the installation, the New Hardware Delivery kit will appear to be in a loop, reloading itself multiple times. This behavior is normal for this installation and may take up to 30 minutes to complete; please wait for the system to finish loading the software. Do not eject the CD-ROM or type [Ctrl/C] during this part of the installation.
If a kernel build is required, the installation process issues the following prompt:
Enter a name for the kernel configuration file. [SYS_NAME]:
In this prompt, the default SYS_NAME is the name of your existing kernel configuration file, usually your system name in uppercase characters.
If you select the default, you are asked to confirm your selection.
If you then confirm your selection of the default, the old kernel configuration
file is backed up to
SYS_NAME.bck
.
Perform the following steps:
When you see a prompt similar to the following, select the kernel options you want:
*** KERNEL OPTION SELECTION *** Selection Kernel Option -------------------------------------------------------------- 1 System V Devices 2 Logical Volume Manager (LVM) 3 NTP V3 Kernel Phase Lock Loop (NTP_TIME) 4 Kernel Breakpoint Debugger (KDEBUG) 5 Packetfilter driver (PACKETFILTER) 6 Point-to-Point Protocol (PPP) 7 STREAMS pckt module (PCKT) 8 Data Link Bridge (DLPI V2.0 Service Class 1) 9 X/Open Transport Interface (XTISO, TIMOD, TIRDWR) 10 ISO 9660 Compact Disc File System (CDFS) 11 Audit Subsystem 12 ACL Subsystem 13 Logical Storage Manager (LSM) 14 Advanced File System (ADVFS) 15 All of the above 16 None of the above 17 Help 18 Display all options again -------------------------------------------------------------- Enter the selection number for each kernel option you want. For example, 1 3 [16]:
After selecting kernel options, you see a prompt similar to the following:
You selected the following kernel options: System V Devices Logical Volume Manager (LVM) NTP V3 Kernel Phase Lock Loop (NTP_TIME) Kernel Breakpoint Debugger (KDEBUG) Packetfilter driver (PACKETFILTER) Point-to-Point Protocol (PPP) STREAMS pckt module (PCKT) Data Link Bridge (DLPI V2.0 Service Class 1) X/Open Transport Interface (XTISO, TIMOD, TIRDWR) ISO 9660 Compact Disc File System (CDFS) Audit Subsystem ACL Subsystem Logical Storage Manager (LSM) Advanced File System (ADVFS) Is that correct? (y/n) [y]:
If the list is correct, enter
y
and
continue to the next step.
If the list is not correct, enter
n
to return to the previous step and select kernel options again.
The
boot
utility asks if you want to edit
the
/usr/sys/conf/SYS_NAME
kernel
configuration file.
Note
Under most circumstances, you do not have to edit this file.
If you want to edit the configuration file, enter
y
.
The configuration file will be opened in an editor window.
You can edit the file and continue to the next step.
If you do not want to edit the configuration file, enter
n
and continue to the next step.
After the system builds the new kernel, it loads, installs, and configures the New Hardware Delivery subsets.
The system reboots with the new kernel, and you see the operating system login window.
Log in as
root
and use the
setld
-i
command to verify that your New Hardware Delivery kit is installed.
Refer to
the
setld
(8)
reference page for additional information.
Check to make sure that the installed files are where you
want them and that the new hardware product is operational.
You can use the
setld -i
command to verify installed software subsets.
Check to make sure that the
/GENERIC
file was rebuilt correctly by issuing the following command:
#
cat /GENERIC | grep -e module_name.mod
In this example,
module_name.mod
is the name of the module file or
files that you loaded.
If the
.mod
file was supplied
in the
/opt
directory, the full pathname and file name
should be in the
/GENERIC
file.
3.4 Adding Hardware Support During a Full Installation
Before you follow the procedure in this section, make sure that you have completed the applicable prerequisite tasks in Section 3.2.
Follow these steps to install a New Hardware Delivery kit in conjunction with a full installation of the operating system:
Log in as
root
or use the
su
command to gain superuser privileges.
Perform the appropriate preinstallation tasks described in the Tru64 UNIX Installation Guide.
Proceed to the next step if you are performing a default or cloned installation.
If you are performing a custom installation, plan your system disk space before proceeding to the next step.
Note
Depending on the installation type you select, some of the system messages may differ. This document describes only the task required to install the New Hardware Delivery kit. Refer to the Tru64 UNIX Installation Guide for an explanation of the different types of installations you can perform.
Use the
shutdown
command to halt your system:
%
shutdown -h now
Enter the following command at the console prompt:
>>> set auto_action halt
Turn off your system, unplug all power cords, and follow the instructions in the hardware documentation to install the new hardware. Reconnect all power cords and turn on your system.
Perform the appropriate processor-specific
boot instructions except for the actual
boot
command.
Set the
bootdef_dev
console variable
to CD-ROM_device.
>>>
set bootdef_dev CD-ROM_device
Insert the New Hardware Delivery CD-ROM into the CD-ROM drive, and enter the following command:
>>>
boot -flag fax -file GENERIC CD-ROM_device
The following list describes this command line:
The
-flag fax
option defines boot flags:
f
for a New Hardware Delivery kit,
a
for multiuser mode, and
x
to boot a different
osf_boot
file.
The
-file GENERIC
option tells the kernel
to bootlink using the file
GENERIC
.
The location argument is the device containing the New Hardware Delivery kit.
During the boot process,
the
boot
utility issues the following prompt:
Enter Device Name:
Enter the console device name for the device that contains the New Hardware Delivery kit and press [Return].
The
boot
utility issues the following prompt:
Enter Kit Name:
Enter the name of the New Hardware Delivery
kit that you want to install and press
[Return].
For Tru64
UNIX Version 4.0F systems, the kit name is:
/V4.0F/usr/sys/hardware/base.kit
The
boot
utility issues the following prompt:
Insert media for kit 'dev_name:hw_kit_name',hit return when ready, or 'q' to quit this kit:
In this prompt, dev_name is the kit location you entered in step 10 and hw_kit_name is the New Hardware Delivery kit name that you entered in step 11.
Press
[Return].
The
boot
utility reads the selected New Hardware Delivery
kit into memory.
The
boot
utility issues the following prompt:
Enter Hardware Kit Name, or <return> if done with dev_name
Press [Return].
The
boot
utility issues the following prompt.
Enter Device Name, or <return> if done:
Press [Return].
The
boot
utility issues the following prompt:
Insert boot media, hit <return> when ready:
Insert the Operating System Volume 1 CD-ROM into the drive and press [Return]. The generic kernel modules are read so that the bootlink process can build the kernel in memory in the next step.
The
boot
utility issues the following prompt:
Insert media for kit 'location:hw_kit_name', hit <return> when ready or 'q' to quit:
Insert the New Hardware Delivery CD-ROM into the drive and press [Return]. The New Hardware Delivery kernel modules are read and the bootlink process builds the kernel in memory.
The
boot
utility issues the following prompt:
Insert boot media, hit <return> when ready:
Insert the Operating System Volume 1 CD-ROM into the drive and press [Return].
The installation process creates the file systems, loads operating system subsets, and begins to reboot.
Note
You must halt the system at this point and boot the New Hardware Delivery media as described in the following steps. If you do not boot the New Hardware Delivery media at this point, the installation will fail.
Halt the system before it completes the reboot, insert the New Hardware Delivery CD-ROM into the CD-ROM drive, and enter the following command:
>>> boot -flag fax -file GENERIC CD-ROM_device
The
boot
utility issues the following prompt:
Enter device name, or <return> if done:
Enter the name of the CD-ROM drive and press [Return].
The
boot
utility issues the following prompt:
Enter the hardware kit name, or <return> if done with CD-ROM_device:
Enter
/V4.0F/usr/sys/hardware/base.kit
and press
[Return].
The
boot
utility issues the following prompt:
Insert media for <kit_name> hit <return> when ready or 'q' to quit this kit:
Press [Return].
The
boot
utility issues the following prompt:
Enter hardware kit name or <return> if done
Press [Return].
The
boot
utility issues the following prompt:
Enter device name or <return> if done
Press [Return].
The
boot
utility issues the following prompt:
Insert boot media, hit <return> when ready:
Press [Return]. The boot media is the boot disk that has just been installed. The systems boots the newly installed software, links the kernel objects, configures software subsets, and loads hardware kits.
The
boot
utility issues the following prompt:
Insert media for <kit_name> hit <return> when ready or 'q' to quit:
Put the NHD CD-ROM in the drive and press [Return].
The
boot
utility issues the following prompt:
Insert boot media, hit return when ready
Press [Return]. The boot media is the boot disk that has just been installed. The systems boots the newly installed software, links the kernel objects, configures software subsets, and loads the hardware kits.
Note
During this step of the installation, the New Hardware Delivery kit will appear to be in a loop, reloading itself multiple times. This behavior is normal for this installation and may take up to 30 minutes to complete; please wait for the system to finish loading the software. Do not eject the CD-ROM or type [Ctrl/C] during this part of the installation.
The
boot
utility rebuilds your operating
system kernel and reboots with the new kernel.
After a successful reboot,
you see the operating system login window.
Log in as
root
and use the
setld
-i
command to verify that your New Hardware Delivery kit is installed.
Refer to
the
setld
(8)
reference page for information about this command.
Perform the appropriate postinstallation tasks described in the Tru64 UNIX Installation Guide.
Check to make sure that the installed files are where you
want them and that the new hardware product is operational.
You can use the
setld -i
command to verify installed software subsets.
Check to make sure that the
/GENERIC
file was rebuilt correctly by issuing the following command:
#
cat /GENERIC | grep -e module_name.mod
In this example,
module_name.mod
is the name of the module file or
files that you loaded.
If the
.mod
file was supplied
in the
/opt
directory, the full pathname and file name
should be in the
/GENERIC
file.
Check the install logs for errors.
These logs are located
in the
/var/adm/smlogs
directory after the system has
been installed.