1.\" Copyright (c) 1980, 1991, 1993 2.\" The Regents of the University of California. All rights reserved. 3.\" 4.\" Redistribution and use in source and binary forms, with or without 5.\" modification, are permitted provided that the following conditions 6.\" are met: 7.\" 1. Redistributions of source code must retain the above copyright 8.\" notice, this list of conditions and the following disclaimer. 9.\" 2. Redistributions in binary form must reproduce the above copyright 10.\" notice, this list of conditions and the following disclaimer in the 11.\" documentation and/or other materials provided with the distribution. 12.\" 3. All advertising materials mentioning features or use of this software 13.\" must display the following acknowledgement: 14.\" This product includes software developed by the University of 15.\" California, Berkeley and its contributors. 16.\" 4. Neither the name of the University nor the names of its contributors 17.\" may be used to endorse or promote products derived from this software 18.\" without specific prior written permission. 19.\" 20.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND 21.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE 22.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE 23.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE 24.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL 25.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 26.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 27.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 28.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 29.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 30.\" SUCH DAMAGE. 31.\" 32.\" @(#)autoconf.4 8.1 (Berkeley) 6/5/93 33.\" 34.Dd June 5, 1993 35.Dt AUTOCONF 4 36.Os BSD 4 37.Sh NAME 38.Nm autoconf 39.Nd "diagnostics from the autoconfiguration code" 40.Sh DESCRIPTION 41When 42.Tn UNIX 43bootstraps it probes the innards of the machine 44on which it is running and 45locates controllers, drives, and other devices. 46Each item found is recorded on the console. 47This procedure is driven by a system 48configuration table which is processed by 49.Xr config 8 50and compiled into each kernel. 51.Pp 52On the 53.Tn VAX , 54devices in 55.Tn NEXUS 56slots are normally noted, thus memory controllers, 57.Tn UNIBUS 58and 59.Tn MASSBUS 60adaptors. Devices which are not supported which 61are found in 62.Tn NEXUS 63slots are noted also. 64The Q-bus on the 65.Tn MICROVAX 66is configured in the same way as the 67.Tn UNIBUS. 68.Pp 69.Tn MASSBUS 70devices are located by a very deterministic procedure since 71.Tn MASSBUS 72space is completely probe-able. If devices exist which 73are not configured they will be silently ignored; if devices exist of 74unsupported type they will be noted. 75.Pp 76.Tn UNIBUS 77devices are located by probing to see if their control-status 78registers respond. If not, they are silently ignored. If the control 79status register responds but the device cannot be made to interrupt, 80a diagnostic warning will be printed on the console and the device 81will not be available to the system. 82.Pp 83Normally, the system uses the disk from which it was loaded as the root 84filesystem. 85If that is not possible, 86a generic system will pick its root device 87as the 88.Dq best 89available device 90.Pf ( Tn MASSBUS 91disks are better than 92.Tn SMD UNIBUS 93disks are better than 94.Tn RK07 Ns s ; 95the device must be drive 0 96to be considered). 97If such a system is booted with the 98.Dv RB_ASKNAME 99option (see 100.Xr reboot 2 ) , 101then the name of the root device is read from the console terminal at boot 102time, and any available device may be used. 103.Sh DIAGNOSTICS 104.Bl -diag 105.It cpu type %d not configured. 106You tried to boot 107.Tn UNIX 108on a 109.Tn CPU 110type which it doesn't (or at least this compiled version of 111.Tn UNIX 112doesn't) 113understand. 114.Pp 115.It mba%d at tr%d. 116A 117.Tn MASSBUS 118adapter was found in 119.Ql tr%d 120(the 121.Tn NEXUS 122slot number). 123.Tn UNIX 124will call it 125.Ql mba%d . 126.Pp 127.It %d mba's not configured. 128More 129.Tn MASSBUS 130adapters were found on 131the machine than were declared in the machine configuration; the excess 132.Tn MASSBUS 133adapters will not be accessible. 134.Pp 135.It uba%d at tr%d. 136A 137.Tn UNIBUS 138adapter was found in 139.Ql tr%d 140(the 141.Tn NEXUS 142slot number). 143.Tn UNIX 144will call it 145.Ql uba%d . 146.Pp 147.It dr32 unsupported (at tr %d). 148A 149.Tn DR Ns 32 150interface was found in 151a 152.Tn NEXUS , 153for which 154.Tn UNIX 155does not have a driver. 156.Pp 157.It ci unsupported (at tr %d). 158A 159.Tn CI 160interface was found in 161a 162.Tn NEXUS , 163for which 164.Tn UNIX 165does not have a driver. 166.Pp 167.It mcr%d at tr%d. 168A memory controller was found in 169.Ql tr%d 170(the 171.Tn NEXUS 172slot number). 173.Tn UNIX 174will call it 175.Ql mcr%d . 176.Pp 177.It 5 mcr's unsupported. 178.Tn UNIX 179supports only 4 memory controllers 180per 181.Tn CPU . 182.Pp 183.It mpm unsupported (at tr%d). 184Multi-port memory is unsupported 185in the sense that 186.Tn UNIX 187does not know how to poll it for 188.Tn ECC 189errors. 190.Pp 191.It %s%d at mba%d drive %d. 192A tape formatter or a disk was found 193on the 194.Tn MASSBUS ; 195for disks 196.Ql %s%d 197will look like 198.Dq Li hp0 , 199for tape formatters 200like 201.Dq Li ht1 . 202The drive number comes from the unit plug on the drive 203or in the 204.Tn TM 205formatter 206.Pf ( Em not 207on the tape drive; see below). 208.Pp 209.It %s%d at %s%d slave %d. 210(For 211.Tn MASSBUS 212devices). 213Which would look like 214.Dq Li tu0 at ht0 slave 0 , 215where 216.Dq Li tu0 217is the name for the tape device and 218.Dq Li ht0 219is the name 220for the formatter. A tape slave was found on the tape formatter at the 221indicated drive number (on the front of the tape drive). 222.Ux 223will call the device, e.g., 224.Dq Li tu0 . 225.Pp 226.It "%s%d at uba%d csr %o vec %o ipl %x." 227The device 228.Ql %s%d , 229e.g. 230.Dq Li dz0 231was found on 232.Ql uba%d 233at control-status register address 234.Ql \&%o 235and with 236device vector 237.Ql \&%o . 238The device interrupted at priority level 239.Ql \&%x . 240.Pp 241.It %s%d at uba%d csr %o zero vector. 242The device did not present 243a valid interrupt vector, rather presented 0 (a passive release condition) 244to the adapter. 245.Pp 246.It %s%d at uba%d csr %o didn't interrupt. 247The device did not interrupt, 248likely because it is broken, hung, or not the kind of device it is advertised 249to be. 250.Pp 251.It %s%d at %s%d slave %d. 252(For UNIBUS devices). 253Which would look like 254.Dq Li up0 at sc0 slave 0 , 255where 256.Dq Li up0 257is the name of a disk drive and 258.Dq Li sc0 259is the name 260of the controller. Analogous to 261.Tn MASSBUS 262case. 263.El 264.Sh SEE ALSO 265.Xr intro 4 , 266.Xr boot 8 , 267.Xr config 8 268.Sh HISTORY 269The 270.Nm 271feature 272appeared in 273.Bx 4.1 . 274