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

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

NNAAMMEE
     aauuttooccoonnff - diagnostics from autoconfiguration code

DDEESSCCRRIIPPTTIIOONN
     When UNIX bootstraps it probes the innards of the machine it is running
     on and locates controllers, drives, and other devices, printing out what
     it finds on the console.  This procedure is driven by a system configura-
     tion table which is processed by config(8) and compiled into each kernel.

     VERSAbus devices are located by probing to see if their control-status
     registers respond.  If not, they are silently ignored.  If the control
     status register responds but the device cannot be made to interrupt, a
     diagnostic warning will be printed on the console and the device will not
     be available to the system.

     A generic system may be built which picks its root device at boot time as
     the ``best'' available device.  If such a system is booted with the
     RB_ASKNAME option of (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
     vvbbaa%%dd aatt %%xx..  A VERSAbus adapter was found and mapped into the address
     space of the operating system starting at virtual address `%x'. UNIX will
     call it `vba%d'.

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

     %%ss%%dd aatt %%ss%%dd ssllaavvee %%dd..  Which would look like `yc0 at cy0 slave 0%',
     where _y_c_0 is the name for the tape device and _c_y_0 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 de-
     vice, e.g., cy0.

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

     %%ss%%dd aatt vvbbaa%%dd ccssrr %%xx nnoo iinntteerrrruuppttss..  The device was found on `vba%d' at
     control-status register address `%x'; no interrupts were configured for
     the device.

     %%ss%%dd aatt vvbbaa%%dd ccssrr %%xx 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.  The csr address is interpreted as described above.

     %%ss%%dd aatt %%ss%%dd ssllaavvee %%dd..  Which would look like `dk0 at vd0 slave 0', where
     _d_k_0 is the name of a disk drive and _v_d_0 is the name of the controller.

SSEEEE AALLSSOO
     config(8)

HHIISSTTOORRYY
     The aauuttooccoonnff special file appeared in 4.3BSD-Tahoe.

BBUUGGSS
     Very few devices actually figure out their interrupt vector by forcing
     the device to interrupt.  Only the upper megabyte of the VERSAbus address
     space is mapped into the system's virtual address space.

4.3-Tahoe Berkeley Distribution  June 5, 1993                                1