projects / unix-history / blame
| Commit | Line | Data |
|---|---|---|
| b7bb9be5 KM |
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 4.1 (Berkeley) %G% | |
| 6 | .\" | |
| 7 | .TH AUTOCONF 4 10/8/81 | |
| 8 | .UC 4 | |
| 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 | Devices in NEXUS slots are normally noted, thus memory controllers, | |
| 20 | UNIBUS and MASSBUS adaptors. Devices which are not supported which | |
| 21 | are found in NEXUS slots are noted also. | |
| 22 | .PP | |
| 23 | MASSBUS devices are located by a very deterministic procedure since | |
| 24 | MASSBUS space is completely probable very easily. If devices exist which | |
| 25 | are not configured they will be silently ignored; if devices exist of | |
| 26 | unsupported type they will be noted. | |
| 27 | .PP | |
| 28 | UNIBUS devices are located by probing to see if their control-status | |
| 29 | registers respond. If not, they are silently ignored. If the control | |
| 30 | status register responds but the device cannot be made to interrupt, | |
| 31 | a diagnostic warning will be printed on the console and the device | |
| 32 | will not be available to the system. (A command | |
| 33 | .IR attach (8) | |
| 34 | is planned to cause the device to be attached irregardless of its | |
| 35 | failure to interrupt, after the system is bootstrapped, for irksome | |
| 36 | devices. This is not in as of this writing, however.) | |
| 37 | .PP | |
| 38 | A generic system may be built which picks its root device at boot time | |
| 39 | as the ``best'' available device (MASSBUS disks are better than | |
| 40 | SMD UNIBUS disks are better than RK07's; the device must be drive 0 | |
| 41 | to be considered.) | |
| 42 | If such a system is booted with the RB_ASKNAME option of (see | |
| 43 | .IR reboot (2V)), | |
| 44 | then the name of the root device is read from the console terminal at boot | |
| 45 | time, and any available device may be used. | |
| 46 | .SH SEE ALSO | |
| 47 | config(8) | |
| 48 | .SH DIAGNOSTICS | |
| 49 | \fBcpu type %d not configured\fR. You tried to boot UNIX on a cpu | |
| 50 | type which it doesn't (or at least this compiled version of UNIX doesn't) | |
| 51 | understand. | |
| 52 | .PP | |
| 53 | \fBmba%d at tr%d\fR. A MASSBUS adapter was found in tr%d (the NEXUS | |
| 54 | slot number). UNIX will call it mba%d. | |
| 55 | .PP | |
| 56 | \fB%d mba's not configured\fR. More MASSBUS adapters were found on | |
| 57 | the machine than were declared in the machine configuration; the excess | |
| 58 | MASSBUS adapters will not be accessible. | |
| 59 | .PP | |
| 60 | \fBuba%d at tr%d\fR. A UNIBUS adapter was found in tr%d (the NEXUS | |
| 61 | slot number). UNIX will call it uba%d. | |
| 62 | .PP | |
| 63 | \fBdr32 unsupported (at tr %d)\fR. A DR32 interface was found in | |
| 64 | a NEXUS, for which UNIX does not have a driver. | |
| 65 | .PP | |
| 66 | \fBmcr%d at tr%d\fR. A memory controller was found in tr%d (the NEXUS | |
| 67 | slot number). UNIX will call it mcr%d. | |
| 68 | .PP | |
| 69 | \fB5 mcr's unsupported\fR. UNIX supports only 4 memory controllers | |
| 70 | per cpu. | |
| 71 | .PP | |
| 72 | \fBmpm unsupported (at tr%d)\fR. Multi-port memory is unsupported | |
| 73 | in the sense that UNIX does not know how to poll it for ECC errors. | |
| 74 | .PP | |
| 75 | \fB%s%d at mba%d drive %d\fR. A tape formatter or a disk was found | |
| 76 | on the MASSBUS; for disks %s%d will look like ``hp0'', for tape formatters | |
| 77 | like ``ht1'' or ``mt1''. The drive number comes from the unit plug on the drive | |
| 78 | or in the TM formatter (\fBnot\fR on the tape drive; see below). | |
| 79 | .PP | |
| 80 | \fB%s%d at %s%d slave %d\fR. (For MASSBUS devices). | |
| 81 | Which would look like ``tu0 at ht0 slave 0'' or ``mu0 at mt0 slave 0'', | |
| 82 | where \fBtu0\fR or \fBmu0\fR is the name for the tape device | |
| 83 | and \fBht0\fR or \fBmt0\fR is the name | |
| 84 | for the formatter. A tape slave was found on the tape formatter at the | |
| 85 | indicated drive number (on the front of the tape drive). | |
| 86 | UNIX will call the device, e.g., \fBtu0\fR or \fBmu0\fR. | |
| 87 | .PP | |
| 88 | \fB%s%d at uba%d csr %o vec %o ipl %x\fR. The device %s%d, e.g. dz0 | |
| 89 | was found on uba%d at control-status register address %o and with | |
| 90 | device vector %o. The device interrupted at priority level %x. | |
| 91 | .PP | |
| 92 | \fB%s%d at uba%d csr %o zero vector\fR. The device did not present | |
| 93 | a valid interrupt vector, rather presented 0 (a passive release condition) | |
| 94 | to the adapter. | |
| 95 | .PP | |
| 96 | \fB%s%d at uba%d csr %o didn't interrupt\fR. The device did not interrupt, | |
| 97 | likely because it is broken, hung, or not the kind of device it is advertised | |
| 98 | to be. | |
| 99 | .PP | |
| 100 | \fB%s%d at %s%d slave %d\fR. (For UNIBUS devices). | |
| 101 | Which would look like ``up0 at sc0 slave 0'', | |
| 102 | where \fBup0\fR is the name of a disk drive and \fBsc0\fR is the name | |
| 103 | of the controller. Analogous to MASSBUS case. | |
| 104 | .SH BUGS | |
| 105 | Should write | |
| 106 | .IR attach (8) | |
| 107 | and system call it needs to work. |