[Go to CFHT Home Page] Man Pages
Back to Software Index  BORDER=0Manpage Top Level
    prtconf(1M) manual page Table of Contents

Name

prtconf - print system configuration

SPARC Synopsis

/usr/sbin/prtconf [ -F ] [ -p ] [ -P ] [ -v ] [ -V ]

x86 SYNOPSIS

/usr/sbin/prtconf [ -P ] [ -v ]

Availability

SUNWcsu

Description

The prtconf command prints the system configuration information. The output includes the total amount of memory, and the configuration of system peripherals formatted as a device tree.

Options

-P
Include information about pseudo devices. By default, information regarding pseudo devices is omitted.
-v
Specifies verbose mode.
-F
(SPARC only). Return the device pathname of the console frame buffer, if one exists. If there is no frame buffer, prtconf returns a non-zero exit code. This flag overrides all others, and returns only the name of the console, frame buffer device or a non-zero exit code. For example, if the console frame buffer on a SPARCstation 1 is cgthree in SBus slot #3, the command returns: /sbus@1,f80000000/cgthree@3,0. This option could be used to create a symlink for /dev/fb to the actual console device.
-p
(SPARC only). Displays information derived from the device tree provided by the firmware (PROM).
-V
(SPARC only). Display platform-dependent PROM version information. This flag must be used by itself, as it overrides all others. The output is a string. The format of the string is arbitrary and platform-dependent.

Exit Status

If successful, prtconf returns 0. If an error occurs, prtconf prints an error message and returns 1. For example, when an illegal option is specified, prtconf returns 1. On a SPARC system, when the -F option is specified and the console output device is not a framebuffer, prtconf returns 1.

SPARC Examples

Running prtconf on a Sun4/65 series machine produces the following sample output: 


example% prtconf
System Configuration:  Sun Microsystems  sun4c
Memory size: 16 Megabytes
System Peripherals (Software Nodes):
Sun 4_65
    options, instance #0
    zs, instance #0
    zs, instance #1
    fd (driver not attached)
    audio (driver not attached)
    sbus, instance #0
        dma, instance #0
        esp, instance #0
            sd (driver not attached)
            st (driver not attached)
            sd, instance #0
            sd, instance #1 (driver not attached)
            sd, instance #2 (driver not attached)
            sd, instance #3
            sd, instance #4 (driver not attached)
            sd, instance #5 (driver not attached)
            sd, instance #6 (driver not attached)
        le, instance #0
        cgsix (driver not attached)
    auxiliary-io (driver not attached)
    interrupt-enable (driver not attached)
    memory-error (driver not attached)
    counter-timer (driver not attached)
    eeprom (driver not attached)
    pseudo, instance #0

x86 EXAMPLES

Running prtconf on an x86 machine produces the following sample output: 


example% prtconf
System Configuration:  Sun Microsystems  i86pc
Memory size: 32 Megabytes
System Peripherals (Software Nodes):
 
i86pc
    eisa, instance #0
        kd, instance #0
        ata, instance #0
            cmdk, instance #0
        aha, instance #0
            cmdk, instance #1 (driver not attached)
            cmdk, instance #2 (driver not attached)
            cmdk, instance #3 (driver not attached)
            cmdk, instance #4 (driver not attached)
            cmdk, instance #5 (driver not attached)
            cmdk, instance #6 (driver not attached)
            cmdk, instance #7
        chanmux, instance #0
        asy, instance #0
        asy, instance #1
        elx, instance #0
        elx, instance #1 (driver not attached)
        elx, instance #2 (driver not attached)
        elx, instance #3 (driver not attached)
        fdc, instance #0
            fd, instance #0
            fd, instance #1
    options, instance #0
    objmgr, instance #0
    pseudo, instance #0
example%

See Also

modinfo(1M) , sysdef(1M)

SPARC Only

openprom(7D)

Notes

The output of the prtconf command is highly dependent on the version of the PROM installed in the system. The output will be affected in potentially all circumstances.

The driver not attached message means that no driver is currently attached to that instance of the device. In general, drivers are loaded and installed (and attached to hardware instances) on demand, and when needed, and may be uninstalled and unloaded when the device is not in use.

Table of Contents