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