ware configurations. The `hinv`(1M) and `versions`(1M) commands display the hardware and software inventories, respectively. hinv Command The `hinv` command displays the machine's hardware inventory. `hinv` can be run from the Command Monitor or from your system shell prompt. Pertinent information such as the processor type, amount of main memory, and all disks, tape drives, or other devices is included. A sample `hinv` output for a typical workstation is:
    
    
    1 100 MHZ IP22 Processor
    FPU: MIPS R4010 Floating Point Chip Revision: 0.0
    CPU: MIPS R4000 Processor Chip Revision: 3.0
    On-board serial ports: 2
    On-board bi-directional parallel port
    Data cache size: 8 Kbytes
    Instruction cache size: 8 Kbytes
    Secondary unified instruction/data cache size: 1 Mbyte
    Main memory size: 64 Mbytes
    Vino video: unit 1, revision 1
    Iris Audio Processor: version A2 revision 4.1.0
    Integral Ethernet: ec0, version 1
    CDROM: unit 4 on SCSI controller 0

&toccmd=C&tocstate=640:1)[Using the Hardware Inventory](http://techpubs.sgi.com/library/tpl/cgi-bin/getdoc.cgi?coll=0620&db=bks&srch=&fname=/SGI_Developer/DevDriver_PG/sgi_html/ch02.html#id5440326)  
                [Contents of the Inventory](http://techpubs.sgi.com/library/tpl/cgi-bin/getdoc.cgi?coll=0620&db=bks&srch=&fname=/SGI_Developer/DevDriver_PG/sgi_html/ch02.html#id5440338)  
                [Displaying the Inventory with hinv](http://techpubs.sgi.com/library/tpl/cgi-bin/getdoc.cgi?coll=0620&db=bks&srch=&fname=/SGI_Developer/DevDriver_PG/sgi_html/ch02.html#id5440472)  
                [Testing the Inventory In Software](http://techpubs.sgi.com/library/tpl/cgi-bin/getdoc.cgi?coll=0620&db=bks&srch=&fname=/SGI_Developer/DevDriver_PG/sgi_html/ch02.html#id5440571)  
            [Creating an Inventory Entry](http://techpubs.sgi.com/library/tpl/cgi-bin/getdoc.cgi?coll=0620&db=bks&srch=&fname=/SGI_Developer/DevDriver_PG/sgi_html/ch02.html#id5440820)

inventories, respectively. Other commands are presented that report on graphics hardware, the system name, configured printers, and basic system settings. 

### Checking Installed Hardware With hinv

The `hinv` command displays the workstation or server's hardware inventory. This command can be run from the Command (PROM) Monitor or from your system shell prompt. Pertinent information such as the processor type, amount of main memory, and all disks, tape drives, or other devices is included. A sample `hinv` output for a typical workstation is:
    
    
    1 100 MHZ IP22 Processor
    FPU: MIPS R4010 Floating Point Chip Revision: 0.0
    CPU: MIPS R4000 Processor Chip Revision: 3.0
    On-board serial ports: 2
    On-board bi-directional parallel port
    Data cache size: 8 Kbytes
    Instruction cache size: 8 Kbytes
    Secondary unified instruction/data cache size: 1 Mbyte
    Main memory size: 64 Mbytes
    Vino video: unit 1, revision 1

inventories, respectively. Other commands are presented that report on graphics hardware, the system name, configured printers, and basic system settings. 

### Checking Installed Hardware With hinv

The `hinv` command displays the workstation or server's hardware inventory. This command can be run from the Command (PROM) Monitor or from your system shell prompt. Pertinent information such as the processor type, amount of main memory, and all disks, tape drives, or other devices is included. A sample `hinv` output for a typical workstation is:
    
    
    1 100 MHZ IP22 Processor
    FPU: MIPS R4010 Floating Point Chip Revision: 0.0
    CPU: MIPS R4000 Processor Chip Revision: 3.0
    On-board serial ports: 2
    On-board bi-directional parallel port
    Data cache size: 8 Kbytes
    Instruction cache size: 8 Kbytes
    Secondary unified instruction/data cache size: 1 Mbyte
    Main memory size: 64 Mbytes
    Vino video: unit 1, revision 1

). 



( 



c 



April 1990 - 1 - Version 5.0 



HINV(IM) SiUcon Graphics HINV(IM) 

NAME 

hinv - hardware inventory command 

SYNOPSIS 

hinv [ -V ] [ -s ] [ -c class] [ -t type] 

DESCRIPTION 

hinv displays the contents of the system hardware inventory table. This 
table is created each time the system is booted and contains entries describ- 
ing various pieces of hardware in the system. The items in the table include 
main memory size, cache sizes, floating point unit, and disk drives. 
Without arguments, the hinv command will display a one line description of 
each entry in the table. The -v option will give a more verbose description 
of some items in the table. The -c class option will display items from 
class. Classes are processor, disk, memory, serial, parallel, tape, and net- 
work. The -t type option will display items from type. Types are cpu, fpu, 
dcache, icache, memory, and qic. The -s option, when used with either the 
-c or -t options, suppresses output.

html/pr01.html#idintro15)

hardware inventory     

[Hardware Inventory](http://techpubs.jurassic.nl/library/manuals/3000/007-3443-002/sgi_html/ch02.html#id02-confiles1)
    

adding entries to     

[Creating an Inventory Entry](http://techpubs.jurassic.nl/library/manuals/3000/007-3443-002/sgi_html/ch02.html#id02-confiles10)
contents     

[Contents of the Inventory](http://techpubs.jurassic.nl/library/manuals/3000/007-3443-002/sgi_html/ch02.html#id02-confiles2)
hinv displays     

[Displaying the Inventory with hinv](http://techpubs.jurassic.nl/library/manuals/3000/007-3443-002/sgi_html/ch02.html#id02-confiles3)
network driver use     

[Network Inventory Entries](http://techpubs.jurassic.nl/library/manuals/3000/007-3443-002/sgi_html/ch14.html#id16-network14)
software interface to     

[Testing the Inventory In Software](http://techpubs.jurassic.nl/library/manuals/3000/007-3443-002/sgi_html/ch02.html#id02-confiles5)

header files:summary table

html/pr01.html#idintro15)

hardware inventory     

[Hardware Inventory](http://techpubs.jurassic.nl/library/manuals/3000/007-3443-001/sgi_html/ch02.html#id02-confiles1)
    

adding entries to     

[Creating an Inventory Entry](http://techpubs.jurassic.nl/library/manuals/3000/007-3443-001/sgi_html/ch02.html#id02-confiles10)
contents     

[Contents of the Inventory](http://techpubs.jurassic.nl/library/manuals/3000/007-3443-001/sgi_html/ch02.html#id02-confiles2)
hinv displays     

[Displaying the Inventory with hinv](http://techpubs.jurassic.nl/library/manuals/3000/007-3443-001/sgi_html/ch02.html#id02-confiles3)
network driver use     

[Network Inventory Entries](http://techpubs.jurassic.nl/library/manuals/3000/007-3443-001/sgi_html/ch14.html#id16-network14)
software interface to     

[Testing the Inventory In Software](http://techpubs.jurassic.nl/library/manuals/3000/007-3443-001/sgi_html/ch02.html#id02-confiles5)

header files:summary table

alling new hardware. The new hardware should show up in the report after the system is booted following installation, provided that the associated device driver was called and was written correctly.

A full inventory report (`hinv -v`) is almost mandatory documentation for a software problem report, either submitted by your user to you, or by you to Silicon Graphics.

#### Testing the Inventory In Software

Within a shell script, you can test the output of `hinv` most conveniently in the command exit status. The command sets exit status of 0 when it finds or reports any items. It sets status of 1 when it finds no items. The code in [Example 2-1](http://techpubs.jurassic.nl/library/manuals/3000/007-3443-002/sgi_html/ch02.html#id84617) could be used in a shell script to test the existence of a disk controller.

**Example 2-1.Testing the Hardware Inventory in a Shell Script**

alling new hardware. The new hardware should show up in the report after the system is booted following installation, provided that the associated device driver was called and was written correctly.

A full inventory report (`hinv -v`) is almost mandatory documentation for a software problem report, either submitted by your user to you, or by you to Silicon Graphics.

#### Testing the Inventory In Software

Within a shell script, you can test the output of `hinv` most conveniently in the command exit status. The command sets exit status of 0 when it finds or reports any items. It sets status of 1 when it finds no items. The code in [Example 2-1](http://techpubs.jurassic.nl/library/manuals/0000/007-0911-060/sgi_html/ch02.html#id84617) could be used in a shell script to test the existence of a disk controller.

**Example 2-1.Testing the Hardware Inventory in a Shell Script**

alling new hardware. The new hardware should show up in the report after the system is booted following installation, provided that the associated device driver was called and was written correctly.

A full inventory report (`hinv -mv`) is almost mandatory documentation for a software problem report, either submitted by your user to you, or by you to Silicon Graphics.

#### Testing the Inventory In Software

Within a shell script, you can test the output of `hinv` most conveniently in the command exit status. The command sets exit status of 0 when it finds or reports any items. It sets status of 1 when it finds no items. The code in [Example 2-1](http://tech-pubs.net/sgi_developer/books/007-0911-210/ch02.html#LE84617-PARENT "Example 2-1. Testing the Hardware Inventory in a Shell Script") could be used in a shell script to test the existence of a disk controller.

alling new hardware. The new hardware should show up in the report after the system is booted following installation, provided that the associated device driver was called and was written correctly.

A full inventory report (`hinv -v`) is almost mandatory documentation for a software problem report, either submitted by your user to you, or by you to Silicon Graphics.

#### Testing the Inventory In Software

Within a shell script, you can test the output of `hinv` most conveniently in the command exit status. The command sets exit status of 0 when it finds or reports any items. It sets status of 1 when it finds no items. The code in [Example 2-1](http://techpubs.jurassic.nl/library/manuals/3000/007-3443-001/sgi_html/ch02.html#id84617) could be used in a shell script to test the existence of a disk controller.

**Example 2-1.Testing the Hardware Inventory in a Shell Script**

alling new hardware. The new hardware should show up in the report after the system is booted following installation, provided that the associated device driver was called and was written correctly.

A full inventory report (`hinv -mv`) is almost mandatory documentation for a software problem report, either submitted by your user to you, or by you to Silicon Graphics.

#### Testing the Inventory In Software

Within a shell script, you can test the output of `hinv` most conveniently in the command exit status. The command sets exit status of 0 when it finds or reports any items. It sets status of 1 when it finds no items. The code in [Example 2-1](http://techpubs.jurassic.nl/library/manuals/0000/007-0911-210/sgi_html/ch02.html#LE84617-PARENT "Example 2-1. Testing the Hardware Inventory in a Shell Script") could be used in a shell script to test the existence of a disk controller.

wn below. When it locates a board, it adds the board to its hardware inventory. 

  1. Main IO4 board, lower mezzanine position (adapter 5)

  2. Main IO4 board, upper mezzanine position (adapter 6)

  3. Second IO4 board, lower mezzanine position (adapter 5)

  4. Second IO4 board, upper mezzanine position (adapter 6)




The order continues as established above. You can display the contents of the hardware inventory with the `hinv` command, as shown below. The FDDIXPress boards are listed in the order in which they were found.
    
    
    % /sbin/hinv 
    ...
    _description_ : slot #, adapter #, xpi#-xpi#
    _description_ : slot #, adapter #, xpi#-xpi#
    ...
      
  
---

wn below. When it locates a board, it adds the board to its hardware inventory. 

  1. Main IO4 board, lower mezzanine position (adapter 5)

  2. Main IO4 board, upper mezzanine position (adapter 6)

  3. Second IO4 board, lower mezzanine position (adapter 5)

  4. Second IO4 board, upper mezzanine position (adapter 6)




The order continues as established above. You can display the contents of the hardware inventory with the `hinv` command, as shown below. The FDDIXPress boards are listed in the order in which they were found.
    
    
    % /sbin/hinv 
    ...
    _description_ : slot #, adapter #, xpi#-xpi#
    _description_ : slot #, adapter #, xpi#-xpi#
    ...
      
  
---

wn below. When it locates a board, it adds the board to its hardware inventory. 

  1. Main IO4 board, lower mezzanine position (adapter 5)

  2. Main IO4 board, upper mezzanine position (adapter 6)

  3. Second IO4 board, lower mezzanine position (adapter 5)

  4. Second IO4 board, upper mezzanine position (adapter 6)




The order continues as established above. You can display the contents of the hardware inventory with the `hinv` command, as shown below. The FDDIXPress boards are listed in the order in which they were found.
    
    
    % /sbin/hinv 
    ...
    _description_ : slot #, adapter #, xpi#-xpi#
    _description_ : slot #, adapter #, xpi#-xpi#
    ...
      
  
---

wn below. When it locates a board, it adds the board to its hardware inventory. 

  1. Main IO4 board, lower mezzanine position (adapter 5)

  2. Main IO4 board, upper mezzanine position (adapter 6)

  3. Second IO4 board, lower mezzanine position (adapter 5)

  4. Second IO4 board, upper mezzanine position (adapter 6)




The order continues as established above. You can display the contents of the hardware inventory with the `hinv` command, as shown below. The FDDIXPress boards are listed in the order in which they were found.
    
    
    % /sbin/hinv 
    ...
    _description_ : slot #, adapter #, xpi#-xpi#
    _description_ : slot #, adapter #, xpi#-xpi#
    ...
      
  
---

ventory is used by users, administrators, and programmers.

#### Contents of the Inventory

Using database terminology, the hardware inventory consists of a single table with the following columns: 

Class | A code for the class of device; for example, audio, disk, processor, or network.  
---|---  
Type | A code for the type of device within its class; for example, FPU and CPU types within the processor class.  
Controller | When applicable, the number of the controller, board, or attachment.  
Unit | When applicable, the logical unit or device within a Controller number.  
State | A descriptive number, such as the CPU model number.  
  
  


#### Displaying the Inventory with hinv

ventory is used by users, administrators, and programmers.

#### Contents of the Inventory

Using database terminology, the hardware inventory consists of a single table with the following columns: 

Class | A code for the class of device; for example, audio, disk, processor, or network.  
---|---  
Type | A code for the type of device within its class; for example, FPU and CPU types within the processor class.  
Controller | When applicable, the number of the controller, board, or attachment.  
Unit | When applicable, the logical unit or device within a Controller number.  
State | A descriptive number, such as the CPU model number.  
  
  


#### Displaying the Inventory with hinv

ventory is used by users, administrators, and programmers.

#### Contents of the Inventory

Using database terminology, the hardware inventory consists of a single table with the following columns: 

Class | A code for the class of device; for example, audio, disk, processor, or network.  
---|---  
Type | A code for the type of device within its class; for example, FPU and CPU types within the processor class.  
Controller | When applicable, the number of the controller, board, or attachment.  
Unit | When applicable, the logical unit or device within a Controller number.  
State | A descriptive number, such as the CPU model number.  
  
  


#### Displaying the Inventory with hinv

ventory is used by users, administrators, and programmers.

#### Contents of the Inventory

Using database terminology, the hardware inventory consists of a single table with the following columns: 

Class | A code for the class of device; for example, audio, disk, processor, or network.  
---|---  
Type | A code for the type of device within its class; for example, FPU and CPU types within the processor class.  
Controller | When applicable, the number of the controller, board, or attachment.  
Unit | When applicable, the logical unit or device within a Controller number.  
State | A descriptive number, such as the CPU model number.  
  
  


#### Displaying the Inventory with hinv