1.\" Copyright (c) 1980, 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
10.Os BSD 4
11.Sh NAME
12.Nm autoconf
13.Nd "diagnostics from the autoconfiguration code"
14.Sh DESCRIPTION
15When
16.Tn UNIX
17bootstraps it probes the innards of the machine
18on which it is running and
19locates controllers, drives, and other devices.
20Each item found is recorded on the console.
21This procedure is driven by a system
22configuration table which is processed by
23.Xr config 8
24and compiled into each kernel.
25.Pp
26On the
27.Tn VAX ,
28devices in
29.Tn NEXUS
30slots are normally noted, thus memory controllers,
31.Tn UNIBUS
32and
33.Tn MASSBUS
34adaptors.  Devices which are not supported which
35are found in
36.Tn NEXUS
37slots are noted also.
38The Q-bus on the
39.Tn MICROVAX
40is configured in the same way as the
41.Tn UNIBUS.
42.Pp
43.Tn MASSBUS
44devices are located by a very deterministic procedure since
45.Tn MASSBUS
46space is completely probe-able.  If devices exist which
47are not configured they will be silently ignored; if devices exist of
48unsupported type they will be noted.
49.Pp
50.Tn UNIBUS
51devices are located by probing to see if their control-status
52registers respond.  If not, they are silently ignored.  If the control
53status register responds but the device cannot be made to interrupt,
54a diagnostic warning will be printed on the console and the device
55will not be available to the system.
56.Pp
57Normally, the system uses the disk from which it was loaded as the root
58filesystem.
59If that is not possible,
60a generic system will pick its root device
61as the
62.Dq best
63available device
64.Pf ( Tn MASSBUS
65disks are better than
66.Tn SMD UNIBUS
67disks are better than
68.Tn RK07 Ns s ;
69the device must be drive 0
70to be considered).
71If such a system is booted with the
72.Dv RB_ASKNAME
73option (see
74.Xr reboot 2 ) ,
75then the name of the root device is read from the console terminal at boot
76time, and any available device may be used.
77.Sh DIAGNOSTICS
78.Bl -diag
79.It cpu type %d not configured.
80You tried to boot
81.Tn UNIX
82on a
83.Tn CPU
84type which it doesn't (or at least this compiled version of
85.Tn UNIX
86doesn't)
87understand.
88.Pp
89.It mba%d at tr%d.
90A
91.Tn MASSBUS
92adapter was found in
93.Ql tr%d
94(the
95.Tn NEXUS
96slot number).
97.Tn UNIX
98will call it
99.Ql mba%d .
100.Pp
101.It %d mba's not configured.
102More
103.Tn MASSBUS
104adapters were found on
105the machine than were declared in the machine configuration; the excess
106.Tn MASSBUS
107adapters will not be accessible.
108.Pp
109.It uba%d at tr%d.
110A
111.Tn UNIBUS
112adapter was found in
113.Ql tr%d
114(the
115.Tn NEXUS
116slot number).
117.Tn UNIX
118will call it
119.Ql uba%d .
120.Pp
121.It dr32 unsupported (at tr %d).
122A
123.Tn DR Ns 32
124interface was found in
125a
126.Tn NEXUS ,
127for which
128.Tn UNIX
129does not have a driver.
130.Pp
131.It ci unsupported (at tr %d).
132A
133.Tn CI
134interface was found in
135a
136.Tn NEXUS ,
137for which
138.Tn UNIX
139does not have a driver.
140.Pp
141.It mcr%d at tr%d.
142A memory controller was found in
143.Ql tr%d
144(the
145.Tn NEXUS
146slot number).
147.Tn UNIX
148will call it
149.Ql mcr%d .
150.Pp
151.It 5 mcr's unsupported.
152.Tn UNIX
153supports only 4 memory controllers
154per
155.Tn CPU .
156.Pp
157.It mpm unsupported (at tr%d).
158Multi-port memory is unsupported
159in the sense that
160.Tn UNIX
161does not know how to poll it for
162.Tn ECC
163errors.
164.Pp
165.It %s%d at mba%d drive %d.
166A tape formatter or a disk was found
167on the
168.Tn MASSBUS ;
169for disks
170.Ql %s%d
171will look like
172.Dq Li hp0 ,
173for tape formatters
174like
175.Dq Li ht1 .
176The drive number comes from the unit plug on the drive
177or in the
178.Tn TM
179formatter
180.Pf ( Em not
181on the tape drive; see below).
182.Pp
183.It %s%d at %s%d slave %d.
184(For
185.Tn MASSBUS
186devices).
187Which would look like
188.Dq Li tu0 at ht0 slave 0 ,
189where
190.Dq Li tu0
191is the name for the tape device and
192.Dq Li ht0
193is the name
194for the formatter.  A tape slave was found on the tape formatter at the
195indicated drive number (on the front of the tape drive).
196.Ux
197will call the device, e.g.,
198.Dq Li tu0 .
199.Pp
200.It "%s%d at uba%d csr %o vec %o ipl %x."
201The device
202.Ql %s%d ,
203e.g.
204.Dq Li dz0
205was found on
206.Ql uba%d
207at control-status register address
208.Ql \&%o
209and with
210device vector
211.Ql \&%o .
212The device interrupted at priority level
213.Ql \&%x .
214.Pp
215.It %s%d at uba%d csr %o zero vector.
216The device did not present
217a valid interrupt vector, rather presented 0 (a passive release condition)
218to the adapter.
219.Pp
220.It %s%d at uba%d csr %o didn't interrupt.
221The device did not interrupt,
222likely because it is broken, hung, or not the kind of device it is advertised
223to be.
224.Pp
225.It %s%d at %s%d slave %d.
226(For UNIBUS devices).
227Which would look like
228.Dq Li up0 at sc0 slave 0 ,
229where
230.Dq Li up0
231is the name of a disk drive and
232.Dq Li sc0
233is the name
234of the controller.  Analogous to
235.Tn MASSBUS
236case.
237.El
238.Sh SEE ALSO
239.Xr intro 4 ,
240.Xr boot 8 ,
241.Xr config 8
242.Sh HISTORY
243The
244.Nm
245feature
246appeared in
247.Bx 4.1 .
248