1.\" Copyright (c) 1986, 1991, 1993
2.\"	The Regents of the University of California.  All rights reserved.
3.\"
4.\" %sccs.include.redist.man%
5.\"
6.\"     @(#)autoconf.4	8.1 (Berkeley) 06/05/93
7.\"
8.Dd
9.Dt AUTOCONF 4 tahoe
10.Os BSD 4.3t
11.Sh NAME
12.Nm autoconf
13.Nd diagnostics from autoconfiguration code
14.Sh DESCRIPTION
15When
16.Tn UNIX
17bootstraps it probes the innards of the machine it is running
18on and locates controllers, drives, and other devices, printing out
19what it finds on the console.  This procedure is driven by a system
20configuration table which is processed by
21.Xr config 8
22and compiled into each kernel.
23.Pp
24.Tn VERSAbus
25devices are located by probing to see if their control-status
26registers respond.  If not, they are silently ignored.  If the control
27status register responds but the device cannot be made to interrupt,
28a diagnostic warning will be printed on the console and the device
29will not be available to the system.
30.Pp
31A generic system may be built which picks its root device at boot time
32as the
33.Dq best
34available device.
35If such a system is booted with the
36.Dv RB_ASKNAME
37option of (see
38.Xr reboot 2 ) ,
39then the name of the root device is read from the console terminal at boot
40time, and any available device may be used.
41.Sh DIAGNOSTICS
42.Bl -diag
43.It vba%d at %x.
44A
45.Tn VERSAbus
46adapter was found and mapped into the
47address space of the operating system starting at virtual address
48.Sq Li  %x .
49.Tn UNIX
50will call it
51.Sq Li vba%d .
52.It %s%d at vba%d drive %d.
53A tape formatter or a disk was found
54on the
55.Tn VERSAbus ;
56for disks
57.Sq Li %s%d
58will look like
59.Sq Li dk0 ,
60for tape formatters
61like
62.Sq Li yc1 .
63The drive number comes from the unit plug on the drive
64or in the tape formatter
65.Pf ( Em not
66on the tape drive; see below).
67.It %s%d at %s%d slave %d.
68Which would look like
69.Sq Li yc0 at cy0 slave 0% ,
70where
71.Em yc0
72is the name for the tape device and
73.Em cy0
74is the name
75for the formatter.  A tape slave was found on the tape formatter at the
76indicated drive number (on the front of the tape drive).
77.Tn UNIX
78will call the device, e.g.,
79.Li cy0.
80.It %s%d at vba%d csr %x vec %x ipl %x.
81The device
82.Sq Li %s%d ,
83e.g.
84.Sq Li vd0
85was found on
86.Sq Li vba%d
87at control-status register address
88.Sq Li %x
89and with
90device vector
91.Sq Li %x .
92The device interrupted at priority level
93.Sq Li %x .
94.It %s%d at vba%d csr %x no interrupts.
95The device was found
96on
97.Sq Li vba%d
98at control-status register address
99.Sq Li %x ;
100no
101interrupts were configured for the device.
102.It %s%d at vba%d csr %x didn't interrupt.
103The device did not interrupt,
104likely because it is broken, hung, or not the kind of device it is advertised
105to be.  The csr address is interpreted as described above.
106.It %s%d at %s%d slave %d.
107Which would look like
108.Sq Li dk0 at vd0 slave 0 ,
109where
110.Em dk0
111is the name of a disk drive and
112.Em vd0
113is the name
114of the controller.
115.El
116.Sh SEE ALSO
117.Xr config 8
118.Sh HISTORY
119The
120.Nm
121special file appeared in
122.Bx 4.3 tahoe .
123.Sh BUGS
124Very few devices actually figure out their interrupt vector
125by forcing the device to interrupt.  Only the upper megabyte of the
126.Tn VERSAbus
127address space is mapped into the system's virtual address space.
128