1.\" Copyright (c) 1980, 1991 Regents of the University of California. 2.\" 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.\" from: @(#)autoconf.4 6.3 (Berkeley) 3/27/91 33.\" $Id: autoconf.4,v 1.2 1993/08/01 07:36:37 mycroft Exp $ 34.\" 35.Dd March 27, 1991 36.Dt AUTOCONF 4 37.Os BSD 4 38.Sh NAME 39.Nm autoconf 40.Nd "diagnostics from the autoconfiguration code" 41.Sh DESCRIPTION 42When 43.Tn UNIX 44bootstraps it probes the innards of the machine 45on which it is running and 46locates controllers, drives, and other devices. 47Each item found is recorded on the console. 48This procedure is driven by a system 49configuration table which is processed by 50.Xr config 8 51and compiled into each kernel. 52.Pp 53On the 54.Tn VAX , 55devices in 56.Tn NEXUS 57slots are normally noted, thus memory controllers, 58.Tn UNIBUS 59and 60.Tn MASSBUS 61adaptors. Devices which are not supported which 62are found in 63.Tn NEXUS 64slots are noted also. 65The Q-bus on the 66.Tn MICROVAX 67is configured in the same way as the 68.Tn UNIBUS. 69.Pp 70.Tn MASSBUS 71devices are located by a very deterministic procedure since 72.Tn MASSBUS 73space is completely probe-able. If devices exist which 74are not configured they will be silently ignored; if devices exist of 75unsupported type they will be noted. 76.Pp 77.Tn UNIBUS 78devices are located by probing to see if their control-status 79registers respond. If not, they are silently ignored. If the control 80status register responds but the device cannot be made to interrupt, 81a diagnostic warning will be printed on the console and the device 82will not be available to the system. 83.Pp 84Normally, the system uses the disk from which it was loaded as the root 85filesystem. 86If that is not possible, 87a generic system will pick its root device 88as the 89.Dq best 90available device 91.Pf ( Tn MASSBUS 92disks are better than 93.Tn SMD UNIBUS 94disks are better than 95.Tn RK07 Ns s ; 96the device must be drive 0 97to be considered). 98If such a system is booted with the 99.Dv RB_ASKNAME 100option (see 101.Xr reboot 2 ) , 102then the name of the root device is read from the console terminal at boot 103time, and any available device may be used. 104.Sh DIAGNOSTICS 105.Bl -diag 106.It cpu type %d not configured. 107You tried to boot 108.Tn UNIX 109on a 110.Tn CPU 111type which it doesn't (or at least this compiled version of 112.Tn UNIX 113doesn't) 114understand. 115.Pp 116.It mba%d at tr%d. 117A 118.Tn MASSBUS 119adapter was found in 120.Ql tr%d 121(the 122.Tn NEXUS 123slot number). 124.Tn UNIX 125will call it 126.Ql mba%d . 127.Pp 128.It %d mba's not configured. 129More 130.Tn MASSBUS 131adapters were found on 132the machine than were declared in the machine configuration; the excess 133.Tn MASSBUS 134adapters will not be accessible. 135.Pp 136.It uba%d at tr%d. 137A 138.Tn UNIBUS 139adapter was found in 140.Ql tr%d 141(the 142.Tn NEXUS 143slot number). 144.Tn UNIX 145will call it 146.Ql uba%d . 147.Pp 148.It dr32 unsupported (at tr %d). 149A 150.Tn DR Ns 32 151interface was found in 152a 153.Tn NEXUS , 154for which 155.Tn UNIX 156does not have a driver. 157.Pp 158.It ci unsupported (at tr %d). 159A 160.Tn CI 161interface was found in 162a 163.Tn NEXUS , 164for which 165.Tn UNIX 166does not have a driver. 167.Pp 168.It mcr%d at tr%d. 169A memory controller was found in 170.Ql tr%d 171(the 172.Tn NEXUS 173slot number). 174.Tn UNIX 175will call it 176.Ql mcr%d . 177.Pp 178.It 5 mcr's unsupported. 179.Tn UNIX 180supports only 4 memory controllers 181per 182.Tn CPU . 183.Pp 184.It mpm unsupported (at tr%d). 185Multi-port memory is unsupported 186in the sense that 187.Tn UNIX 188does not know how to poll it for 189.Tn ECC 190errors. 191.Pp 192.It %s%d at mba%d drive %d. 193A tape formatter or a disk was found 194on the 195.Tn MASSBUS ; 196for disks 197.Ql %s%d 198will look like 199.Dq Li hp0 , 200for tape formatters 201like 202.Dq Li ht1 . 203The drive number comes from the unit plug on the drive 204or in the 205.Tn TM 206formatter 207.Pf ( Em not 208on the tape drive; see below). 209.Pp 210.It %s%d at %s%d slave %d. 211(For 212.Tn MASSBUS 213devices). 214Which would look like 215.Dq Li tu0 at ht0 slave 0 , 216where 217.Dq Li tu0 218is the name for the tape device and 219.Dq Li ht0 220is the name 221for the formatter. A tape slave was found on the tape formatter at the 222indicated drive number (on the front of the tape drive). 223.Ux 224will call the device, e.g., 225.Dq Li tu0 . 226.Pp 227.It "%s%d at uba%d csr %o vec %o ipl %x." 228The device 229.Ql %s%d , 230e.g. 231.Dq Li dz0 232was found on 233.Ql uba%d 234at control-status register address 235.Ql \&%o 236and with 237device vector 238.Ql \&%o . 239The device interrupted at priority level 240.Ql \&%x . 241.Pp 242.It %s%d at uba%d csr %o zero vector. 243The device did not present 244a valid interrupt vector, rather presented 0 (a passive release condition) 245to the adapter. 246.Pp 247.It %s%d at uba%d csr %o didn't interrupt. 248The device did not interrupt, 249likely because it is broken, hung, or not the kind of device it is advertised 250to be. 251.Pp 252.It %s%d at %s%d slave %d. 253(For UNIBUS devices). 254Which would look like 255.Dq Li up0 at sc0 slave 0 , 256where 257.Dq Li up0 258is the name of a disk drive and 259.Dq Li sc0 260is the name 261of the controller. Analogous to 262.Tn MASSBUS 263case. 264.El 265.Sh SEE ALSO 266.Xr intro 4 , 267.Xr boot 8 , 268.Xr config 8 269.Sh HISTORY 270The 271.Nm 272feature 273appeared in 274.Bx 4.1 . 275