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