|
|
1.1 root 1: .TH AUTOCONF 4 5/10/81
2: .UC 4
3: .SH NAME
4: autoconf \- diagnostics from autoconfiguartion code
5: .SH DESCRIPTION
6: When UNIX bootstraps it probes the innards of the machine it is running
7: on and locates controllers, drives, and other devices, printing out
8: what it finds on the console. This procedure is driven by a system
9: configuration table which is processed by
10: .IR config (8)
11: and compiled into each kernel.
12: .PP
13: VERSABUS devices are located by probing to see if their control-status
14: registers respond. If not, they are silently ignored. If the control
15: status register responds but the device cannot be made to interrupt,
16: a diagnostic warning will be printed on the console and the device
17: will not be available to the system.
18: .PP
19: A generic system may be built which picks its root device at boot time
20: as the ``best'' available device.
21: If such a system is booted with the RB_ASKNAME option of (see
22: .IR reboot (2v)),
23: then the name of the root device is read from the console terminal at boot
24: time, and any available device may be used.
25: .SH SEE ALSO
26: config(8)
27: .SH DIAGNOSTICS
28: .PP
29: \fB%s%d at vba address %o vec %o\fR. The device %s%d, e.g. fsd0
30: was found on the bus at control-status register address %o and with
31: device vector %o.
32: .PP
33: \fB%s%d at vba address %o didn't interrupt\fR. The device did not interrupt,
34: likely because it is broken, hung, or not the kind of device it is advertised
35: to be.
36: .PP
37: \fB%s%d at %s%d slave %d\fR.
38: Which would look like ``smd0 at vd0 slave 0'',
39: where \fBsmd0\fR is the name of a disk drive and \fBvd0\fR is the name
40: of the controller.
41: .SH BUGS
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.