4.4BSD/usr/share/man/cat4/vax/autoconf.0

AUTOCONF(4)                 BSD Programmer's Manual                AUTOCONF(4)

NNAAMMEE
     aauuttooccoonnff - diagnostics from the autoconfiguration code

DDEESSCCRRIIPPTTIIOONN
     When UNIX bootstraps it probes the innards of the machine on which it is
     running and locates controllers, drives, and other devices.  Each item
     found is recorded on the console.  This procedure is driven by a system
     configuration table which is processed by config(8) and compiled into
     each kernel.

     On the VAX, devices in NEXUS slots are normally noted, thus memory con-
     trollers, UNIBUS and MASSBUS adaptors.  Devices which are not supported
     which are found in NEXUS slots are noted also.  The Q-bus on the MICROVAX
     is configured in the same way as the UNIBUS.

     MASSBUS devices are located by a very deterministic procedure since
     MASSBUS space is completely probe-able.  If devices exist which are not
     configured they will be silently ignored; if devices exist of unsupported
     type they will be noted.

     UNIBUS devices are located by probing to see if their control-status reg-
     isters respond.  If not, they are silently ignored.  If the control sta-
     tus register responds but the device cannot be made to interrupt, a diag-
     nostic warning will be printed on the console and the device will not be
     available to the system.

     Normally, the system uses the disk from which it was loaded as the root
     filesystem.  If that is not possible, a generic system will pick its root
     device as the ``best'' available device (MASSBUS disks are better than
     SMD UNIBUS disks are better than RK07s; the device must be drive 0 to be
     considered).  If such a system is booted with the RB_ASKNAME option (see
     reboot(2)),  then the name of the root device is read from the console
     terminal at boot time, and any available device may be used.

DDIIAAGGNNOOSSTTIICCSS
     ccppuu ttyyppee %%dd nnoott ccoonnffiigguurreedd..  You tried to boot UNIX on a CPU type which
     it doesn't (or at least this compiled version of UNIX doesn't) under-
     stand.

     mmbbaa%%dd aatt ttrr%%dd..  A MASSBUS adapter was found in `tr%d' (the NEXUS slot
     number).  UNIX will call it `mba%d'.

     %%dd mmbbaa''ss nnoott ccoonnffiigguurreedd..  More MASSBUS adapters were found on the machine
     than were declared in the machine configuration; the excess MASSBUS
     adapters will not be accessible.

     uubbaa%%dd aatt ttrr%%dd..  A UNIBUS adapter was found in `tr%d' (the NEXUS slot num-
     ber).  UNIX will call it `uba%d'.

     ddrr3322 uunnssuuppppoorrtteedd ((aatt ttrr %%dd))..  A DR32 interface was found in a NEXUS, for
     which UNIX does not have a driver.

     ccii uunnssuuppppoorrtteedd ((aatt ttrr %%dd))..  A CI interface was found in a NEXUS, for
     which UNIX does not have a driver.

     mmccrr%%dd aatt ttrr%%dd..  A memory controller was found in `tr%d' (the NEXUS slot
     number).  UNIX will call it `mcr%d'.

     55 mmccrr''ss uunnssuuppppoorrtteedd..  UNIX supports only 4 memory controllers per CPU.

     mmppmm uunnssuuppppoorrtteedd ((aatt ttrr%%dd))..  Multi-port memory is unsupported in the sense
     that UNIX does not know how to poll it for ECC errors.


     %%ss%%dd aatt mmbbaa%%dd ddrriivvee %%dd..  A tape formatter or a disk was found on the
     MASSBUS; for disks `%s%d' will look like ``hp0'', for tape formatters
     like ``ht1''. The drive number comes from the unit plug on the drive or
     in the TM formatter (_n_o_t on the tape drive; see below).

     %%ss%%dd aatt %%ss%%dd ssllaavvee %%dd..  (For MASSBUS devices).  Which would look like
     ``tu0 at ht0 slave 0'', where ``tu0'' is the name for the tape device and
     ``ht0'' is the name for the formatter.  A tape slave was found on the
     tape formatter at the indicated drive number (on the front of the tape
     drive).  UNIX will call the device, e.g., ``tu0''.

     %%ss%%dd aatt uubbaa%%dd ccssrr %%oo vveecc %%oo iippll %%xx..  The device `%s%d', e.g.  ``dz0'' was
     found on `uba%d' at control-status register address `%o' and with device
     vector `%o'. The device interrupted at priority level `%x'.

     %%ss%%dd aatt uubbaa%%dd ccssrr %%oo zzeerroo vveeccttoorr..  The device did not present a valid in-
     terrupt vector, rather presented 0 (a passive release condition) to the
     adapter.

     %%ss%%dd aatt uubbaa%%dd ccssrr %%oo ddiiddnn''tt iinntteerrrruupptt..  The device did not interrupt,
     likely because it is broken, hung, or not the kind of device it is adver-
     tised to be.

     %%ss%%dd aatt %%ss%%dd ssllaavvee %%dd..  (For UNIBUS devices).  Which would look like
     ``up0 at sc0 slave 0'', where ``up0'' is the name of a disk drive and
     ``sc0'' is the name of the controller.  Analogous to MASSBUS case.

SSEEEE AALLSSOO
     intro(4),  boot(8),  config(8)

HHIISSTTOORRYY
     The aauuttooccoonnff feature appeared in 4.1BSD.

4th Berkeley Distribution        June 5, 1993                                2