- 论坛徽章:
- 0
|
如何在4.0f 的系统上安装DE600的网卡！！！！
书上抄来的,首先你要下载到NHD1,然后做成光盘,最后安装.
Contents of 00README.TXT from the web kit with 2 corrections::
------------------------------------------
Tru64 UNIX New Hardware Distribution kit name:
/V4.0F/usr/sys/hardware/base.kit
The following instructions are provided for experienced users.
For detailed instructions on how to install a hardware kit, refer to the
'Release Notes and Installation Instructions' that are provided in the
DOCUMENTATION directory of this CD-ROM. Note that the instructions
in the Version 4.0F installation guide are incorrect and should not be
used to install this version of the NHD kit.
If you need to boot genvmunix at any time after
you have installed hardware support using the New Hardware Distribution process,
the products you have installed will no longer be recognized by the system.
To access all of the kernel modules supplied by genvmunix
and the kernel modules you have added using the New Hardware Distribution
process, you will need to boot /GENERIC, as described
in the installation instructions.
A: Kit Creation
To use the downloaded New Hardware Distribution Kit, you must have either a CD
Recorder and CD-ROM media or a spare disk, such as an RZ26, that does not
have any data on it.
The following steps apply to producing both a CD-ROM and a Local disk kit:
/usr/bin/mkdir /var/tmp/nhd
/usr/bin/chown root.system /var/tmp/nhd
/usr/bin/gzip -dc ee.tar.gz | /usr/bin/tar -C /var/tmp/nhd -xpf -
* Note: the above command should read as follows:
/usr/bin/gzip -dc nhd-v1_1-r7_h1.tar.gz | usr/bin/tar -C /var/tmp/nhd -xpf -
/usr/sbin/mkisofs -R -D -a -o /var/tmp/nhd.iso /var/tmp/nhd
/usr/sbin/disklabel -w -f -t cdfs /var/tmp/nhd.iso
* Note: the above command should read as follows:
/usr/sbin/disklabel -w -t cdfs -f /var/tmp/nhd.iso
/usr/bin/echo "\0\c" | /usr/bin/dd bs=1024k conv=sync >;>;/var/tmp/nhd.iso
CDROM Kit
After you create the nhd.iso file, you can copy it to the recording
system with a CD Recorder, such as a Yamaha CDR400at or Teac CD-R56S, on
Tru64 UNIX using cdrecord-1.6.1 or on Microsoft Windows using Adaptec Easy
CD Creator. Then record the iso image.
Local Disk Kit
For a local disk kit, you must copy the nhd.iso file to the spare disk
using the following commands, with /dev/rz99c being the spare RZ26 disk:
/usr/sbin/disklabel -z /dev/rrz99c
/usr/bin/dd if=/var/tmp/nhd.iso bs=64k of=/dev/rrz99c
B: Kit Installation
Type a return only to complete each Device Name and Kit Name.
1. Shut down the system.
$ /sbin/shutdown -h now
2. Boot the NHD CD-ROM.
>;>;>; boot -fl fax -fi GENERIC <cd-rom>;
3. Enter the device name where the hardware kit resides.
Enter Device Name: <device>;
4. Enter the kit file name.
Enter Kit Name: <kit_file>; (/V4.0F/usr/sys/hardware/base.kit)
5. Follow the remaining instructions as they are displayed by the system.
------------------------------------------------------------------------
3 Installing Hardware Support
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 Distribution process, the
products you have installed will no longer be recognized by the
system. To access all of the kernel modules supplied by genvmunix
and the kernel modules you have added using the New Hardware
Distribution 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:
1. Back up your system.
2. Have in your possession the New Hardware Delivery kit.
3. Determine the name of the New Hardware Delivery kit that you want to
install. This information is provided in the 00README.TXT file on the
New Hardware Delivery CD-ROM.
4. Shut down your system and obtain the following information from the
system console:
a. 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.
b. 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
c. 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:
1. Log in as root or use the su command to gain superuser privileges.
2. Use the shutdown command to halt your system:
% shutdown -h now
3. Enter the following command at the console prompt:
>;>;>; set auto_action halt
4. 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.
5. 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 NHD kit device.
6. After the boot process, 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].
7. 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]. This information is provided in the
00README.TXT file that is on the New Hardware Delivery CD-ROM.
8. 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.
Load the CD-ROM into the drive and press [Return]. The boot utility
reads the selected New Hardware Delivery kit information into memory.
9. The boot utility reissues the Enter Kit Name: prompt.
Press [Return] and continue to the next step.
10. The boot utility reissues the Enter Device Name: prompt.
Press [Return] and continue.
11. 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.
12. 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.
Put the 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.
13. 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.
14. 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:
a. 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]:
b. 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.
c. 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 nand
continue to the next step.
15. After the system builds the new kernel, it loads, installs, and
configures the New Hardware Delivery subsets. At this time, the system
displays information similar to the following:
*** START LOAD HARDWARE KIT (Wed Dec 22 11:10:31 EST 1999) ***
Validating distribution media...
The Hardware Support product has been successfully located.
Checking file system space required to install specified subsets:
File system space checked OK.
4 subset(s) will be installed.
Loading 1 of 4 subset(s)....
New Hardware Base System Support T1.1
Copying from /instkit1/V4.0F/kit (disk)
Verifying Loading 2 of 4 subset(s)....
New Hardware Kernel Modules T1.1
Copying from /instkit1/V4.0F/kit (disk)
Verifying Loading 3 of 4 subset(s)....
New Hardware Kernel Header and Common Files T1.1
Copying from /instkit1/V4.0F/kit (disk)
Verifying Loading 4 of 4 subset(s)....
New Hardware Patch Files T1.1
Copying from /instkit1/V4.0F/kit (disk)
Verifying 4 of 4 subset(s) installed successfully.
Validating distribution media...
The Hardware Support product has been successfully located.
Checking file system space required to install specified subsets:
File system space checked OK.
4 subset(s) will be installed.
Loading 1 of 4 subset(s)....
New Hardware Base System Support T1.1
.
.
.
.
16. The system reboots with the new kernel, and you see the operating
system login window.
17. Log in as root and use the setld -i command to verify that your New
Hardware Delivery kit is installed. Refer to the setld( reference
page for additional information.
18. 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.
19. 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:
1. Log in as root or use the su command to gain superuser privileges.
2. Perform the appropriate preinstallation tasks described in the Tru64
UNIX Installation Guide.
3. 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.
4. Use the shutdown command to halt your system:
% shutdown -h now
5. Enter the following command at the console prompt:
>;>;>; set auto_action halt
6. 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.
7. Perform the appropriate processor-specific boot instructions except for
the actual boot command.
8. Set the bootdef_dev console variable to CD-ROM_device.
>;>;>; set bootdef_dev CD-ROM_device
9. 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 location argument is the device containing the New Hardware
Delivery kit.
10. 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].
11. 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]. This information is provided in the Read
This First letter and in the 00README.TXT file that is on the New
Hardware Delivery CD-ROM.
12. The boot utility issues the following prompt:
Insert media for kit 'dev_name:hw_kit_name', press Return when ready:
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.
The boot utility reads the selected New Hardware Delivery kit into
memory.
13. The boot utility reissues the Enter Kit Name: prompt.
* If you are installing another New Hardware Delivery kit from the
same device, enter the kit name, press [Return], and return to the
previous step.
* If you are not installing another New Hardware Delivery kit or are
installing one from a different device, just press [Return] and
continue.
14. The boot utility reissues the Enter Device Name: prompt.
Press [Return] and continue.
15. The boot utility reissues the following prompt:
Insert boot media, press 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.
16. The boot utility reissues the following prompt:Insert media for kit
'location:hw_kit_name', press Return when ready:
Insert the kit 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.
17. The boot utility issues the following prompt:
Insert boot media, press Return when ready:
Insert the Operating System Volume 1 CD-ROM into the drive and press
[Return].
18. The installation process creates the file systems, loads operating
system subsets, and begins to reboot. Halt the system before it
completes the reboot, insert the New Hardware Delivery CD-ROM, and
enter the following command:
>;>;>; boot -flag fax -file GENERIC CD-ROM_device
19. The boot utility issues the following prompt:
Enter device name:
Enter the name of the CD-ROM drive and press [Return].
20. The boot utility issues the following prompt:
Insert boot media, press Return when ready:
Press [Return].
21. The boot utility issues the following prompt:
Insert media kit and press Return:
Press [Return].
22. The installation process links the kernel objects, configures software
subsets, and loads hardware kits.
23. The boot utility issues the following prompt:
Enter a name for the kernel configuration file. [SYS_NAME]:
In this prompt, SYS_NAME is the name of your kernel configuration file,
set to your system name in uppercase characters. For example, if your
system name is portland, your kernel configuration file is PORTLAND.
24. If the boot utility prompts you to rebuild the kernel, perform the
following steps:
a. 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]:
The options you see depend upon the software subsets that you have
installed.
b. 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.
c. 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 nand
continue to the next step.
25. 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.
26. Log in as root and use the setld -i command to verify that your New
Hardware Delivery kit is installed. Refer to the setld( reference
page for information about this command.
27. Perform the appropriate postinstallation tasks described in the Tru64
UNIX Installation Guide.
28. 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.
29. 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.
30. Check the install logs for errors. These logs are located in the
/var/adm/smlogs directory after the system has been installed.
------------------------------------------------------------------------ |
|
免费注册
发表于 2005-05-30 08:58
