Return to autoconf.4 CVS log

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

Annotation of 43BSDTahoe/man/man4/tahoe/autoconf.4, revision 1.1.1.1

1.1       root        1: .\" Copyright (c) 1986 Regents of the University of California.
                      2: .\" All rights reserved.  The Berkeley software License Agreement
                      3: .\" specifies the terms and conditions for redistribution.
                      4: .\"
                      5: .\"    @(#)autoconf.4  6.2 (Berkeley) 6/30/87
                      6: .\"
                      7: .TH AUTOCONF 4 "June 30, 1987"
                      8: .UC 7
                      9: .SH NAME
                     10: autoconf \- diagnostics from autoconfiguration code
                     11: .SH DESCRIPTION
                     12: When UNIX bootstraps it probes the innards of the machine it is running
                     13: on and locates controllers, drives, and other devices, printing out
                     14: what it finds on the console.  This procedure is driven by a system
                     15: configuration table which is processed by
                     16: .IR config (8)
                     17: and compiled into each kernel.
                     18: .PP
                     19: VERSAbus devices are located by probing to see if their control-status
                     20: registers respond.  If not, they are silently ignored.  If the control
                     21: status register responds but the device cannot be made to interrupt,
                     22: a diagnostic warning will be printed on the console and the device
                     23: will not be available to the system.
                     24: .PP
                     25: A generic system may be built which picks its root device at boot time
                     26: as the ``best'' available device.
                     27: If such a system is booted with the RB_ASKNAME option of (see
                     28: .IR reboot (2v)),
                     29: then the name of the root device is read from the console terminal at boot
                     30: time, and any available device may be used.
                     31: .SH SEE ALSO
                     32: config(8)
                     33: .SH DIAGNOSTICS
                     34: \fBvba%d at %x\fR.  A VERSAbus adapter was found and mapped into the
                     35: address space of the operating system starting at virtual address %x.
                     36: UNIX will call it vba%d.
                     37: .PP
                     38: \fB%s%d at vba%d drive %d\fR.  A tape formatter or a disk was found
                     39: on the VERSAbus; for disks %s%d will look like ``dk0'', for tape formatters
                     40: like ``yc1''.  The drive number comes from the unit plug on the drive
                     41: or in the tape formatter (\fBnot\fR on the tape drive; see below).
                     42: .PP
                     43: \fB%s%d at %s%d slave %d\fR. 
                     44: Which would look like ``yc0 at cy0 slave 0'',
                     45: where \fByc0\fR is the name for the tape device and \fBcy0\fR is the name
                     46: for the formatter.  A tape slave was found on the tape formatter at the
                     47: indicated drive number (on the front of the tape drive).
                     48: UNIX will call the device, e.g., \fBcy0\fR.
                     49: .PP
                     50: \fB%s%d at vba%d csr %x vec %x ipl %x\fR.  The device %s%d, e.g. vd0
                     51: was found on vba%d at control-status register address %x and with
                     52: device vector %x.  The device interrupted at priority level %x.
                     53: .PP
                     54: \fB%s%d at vba%d csr %x no interrupts\fR.  The device was found
                     55: on vba%d at control-status register address %x; no
                     56: interrupts were configured for the device.
                     57: .PP
                     58: \fB%s%d at vba%d csr %x didn't interrupt\fR.  The device did not interrupt,
                     59: likely because it is broken, hung, or not the kind of device it is advertised
                     60: to be.  The csr address is interpreted as described above.
                     61: .PP
                     62: \fB%s%d at %s%d slave %d\fR.
                     63: Which would look like ``dk0 at vd0 slave 0'',
                     64: where \fBdk0\fR is the name of a disk drive and \fBvd0\fR is the name
                     65: of the controller. 
                     66: .SH BUGS
                     67: Very few devices actually figure out their interrupt vector
                     68: by forcing the device to interrupt.  Only the upper megabyte of the
                     69: 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.