|
|
1.1 ! root 1: .\" Copyright (c) 1980 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) 5/15/86 ! 6: .\" ! 7: .TH AUTOCONF 4 "May 15, 1986" ! 8: .UC 4 ! 9: .SH NAME ! 10: autoconf \- diagnostics from the autoconfiguration code ! 11: .SH DESCRIPTION ! 12: When UNIX bootstraps it probes the innards of the machine ! 13: on which it is running ! 14: and locates controllers, drives, and other devices, printing out ! 15: what it finds on the console. This procedure is driven by a system ! 16: configuration table which is processed by ! 17: .IR config (8) ! 18: and compiled into each kernel. ! 19: .PP ! 20: On the VAX, ! 21: devices in NEXUS slots are normally noted, thus memory controllers, ! 22: UNIBUS and MASSBUS adaptors. Devices which are not supported which ! 23: are found in NEXUS slots are noted also. ! 24: The Q-bus on the MICROVAX is configured in the same way as the UNIBUS. ! 25: .PP ! 26: MASSBUS devices are located by a very deterministic procedure since ! 27: MASSBUS space is completely probe-able. If devices exist which ! 28: are not configured they will be silently ignored; if devices exist of ! 29: unsupported type they will be noted. ! 30: .PP ! 31: UNIBUS devices are located by probing to see if their control-status ! 32: registers respond. If not, they are silently ignored. If the control ! 33: status register responds but the device cannot be made to interrupt, ! 34: a diagnostic warning will be printed on the console and the device ! 35: will not be available to the system. ! 36: .PP ! 37: Normally, the system uses the disk from which it was loaded as the root ! 38: filesystem. ! 39: If that is not possible, ! 40: a generic system will pick its root device ! 41: as the ``best'' available device (MASSBUS disks are better than ! 42: SMD UNIBUS disks are better than RK07's; the device must be drive 0 ! 43: to be considered). ! 44: If such a system is booted with the RB_ASKNAME option (see ! 45: .IR reboot (2)), ! 46: then the name of the root device is read from the console terminal at boot ! 47: time, and any available device may be used. ! 48: .SH SEE ALSO ! 49: intro(4), boot(8), config(8) ! 50: .SH DIAGNOSTICS ! 51: \fBcpu type %d not configured\fR. You tried to boot UNIX on a cpu ! 52: type which it doesn't (or at least this compiled version of UNIX doesn't) ! 53: understand. ! 54: .PP ! 55: \fBmba%d at tr%d\fR. A MASSBUS adapter was found in tr%d (the NEXUS ! 56: slot number). UNIX will call it mba%d. ! 57: .PP ! 58: \fB%d mba's not configured\fR. More MASSBUS adapters were found on ! 59: the machine than were declared in the machine configuration; the excess ! 60: MASSBUS adapters will not be accessible. ! 61: .PP ! 62: \fBuba%d at tr%d\fR. A UNIBUS adapter was found in tr%d (the NEXUS ! 63: slot number). UNIX will call it uba%d. ! 64: .PP ! 65: \fBdr32 unsupported (at tr %d)\fR. A DR32 interface was found in ! 66: a NEXUS, for which UNIX does not have a driver. ! 67: .PP ! 68: \fBci unsupported (at tr %d)\fR. A CI interface was found in ! 69: a NEXUS, for which UNIX does not have a driver. ! 70: .PP ! 71: \fBmcr%d at tr%d\fR. A memory controller was found in tr%d (the NEXUS ! 72: slot number). UNIX will call it mcr%d. ! 73: .PP ! 74: \fB5 mcr's unsupported\fR. UNIX supports only 4 memory controllers ! 75: per cpu. ! 76: .PP ! 77: \fBmpm unsupported (at tr%d)\fR. Multi-port memory is unsupported ! 78: in the sense that UNIX does not know how to poll it for ECC errors. ! 79: .PP ! 80: \fB%s%d at mba%d drive %d\fR. A tape formatter or a disk was found ! 81: on the MASSBUS; for disks %s%d will look like ``hp0'', for tape formatters ! 82: like ``ht1''. The drive number comes from the unit plug on the drive ! 83: or in the TM formatter (\fBnot\fR on the tape drive; see below). ! 84: .PP ! 85: \fB%s%d at %s%d slave %d\fR. (For MASSBUS devices). ! 86: Which would look like ``tu0 at ht0 slave 0'', ! 87: where \fBtu0\fR is the name for the tape device and \fBht0\fR is the name ! 88: for the formatter. A tape slave was found on the tape formatter at the ! 89: indicated drive number (on the front of the tape drive). ! 90: UNIX will call the device, e.g., \fBtu0\fR. ! 91: .PP ! 92: \fB%s%d at uba%d csr %o vec %o ipl %x\fR. The device %s%d, e.g. dz0 ! 93: was found on uba%d at control-status register address %o and with ! 94: device vector %o. The device interrupted at priority level %x. ! 95: .PP ! 96: \fB%s%d at uba%d csr %o zero vector\fR. The device did not present ! 97: a valid interrupt vector, rather presented 0 (a passive release condition) ! 98: to the adapter. ! 99: .PP ! 100: \fB%s%d at uba%d csr %o didn't interrupt\fR. The device did not interrupt, ! 101: likely because it is broken, hung, or not the kind of device it is advertised ! 102: to be. ! 103: .PP ! 104: \fB%s%d at %s%d slave %d\fR. (For UNIBUS devices). ! 105: Which would look like ``up0 at sc0 slave 0'', ! 106: where \fBup0\fR is the name of a disk drive and \fBsc0\fR is the name ! 107: of the controller. Analogous to MASSBUS case.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.