Return to autoconf.4 CVS log

Up to [CSRG BSD Unix] / 43BSDTahoe / man / man4 / tahoe

Initial revision

.\" Copyright (c) 1986 Regents of the University of California.
.\" All rights reserved.  The Berkeley software License Agreement
.\" specifies the terms and conditions for redistribution.
.\"
.\"	@(#)autoconf.4	6.2 (Berkeley) 6/30/87
.\"
.TH AUTOCONF 4 "June 30, 1987"
.UC 7
.SH NAME
autoconf \- diagnostics from autoconfiguration code
.SH DESCRIPTION
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
configuration table which is processed by
.IR config (8)
and compiled into each kernel.
.PP
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.
.PP
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
.IR reboot (2v)),
then the name of the root device is read from the console terminal at boot
time, and any available device may be used.
.SH SEE ALSO
config(8)
.SH DIAGNOSTICS
\fBvba%d at %x\fR.  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.
.PP
\fB%s%d at vba%d drive %d\fR.  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 (\fBnot\fR on the tape drive; see below).
.PP
\fB%s%d at %s%d slave %d\fR. 
Which would look like ``yc0 at cy0 slave 0'',
where \fByc0\fR is the name for the tape device and \fBcy0\fR 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., \fBcy0\fR.
.PP
\fB%s%d at vba%d csr %x vec %x ipl %x\fR.  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.
.PP
\fB%s%d at vba%d csr %x no interrupts\fR.  The device was found
on vba%d at control-status register address %x; no
interrupts were configured for the device.
.PP
\fB%s%d at vba%d csr %x didn't interrupt\fR.  The device did not interrupt,
likely because it is broken, hung, or not the kind of device it is advertised
to be.  The csr address is interpreted as described above.
.PP
\fB%s%d at %s%d slave %d\fR.
Which would look like ``dk0 at vd0 slave 0'',
where \fBdk0\fR is the name of a disk drive and \fBvd0\fR is the name
of the controller. 
.SH BUGS
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.

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.