1.\" $NetBSD: autoconf.4,v 1.15 2017/08/01 11:11:17 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. 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 February 17, 2017 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. 59Devices which are not supported which are 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. 71If devices exist which 72are not configured they will be silently ignored; if devices exist of 73unsupported type they will be noted. 74.Pp 75.Tn UNIBUS 76devices are located by probing to see if their control-status 77registers respond. 78If not, they are silently ignored. 79If 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.Nx 109on a 110.Tn CPU 111type which it doesn't (or at least this compiled version of 112.Nx 113doesn't) 114understand. 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.Nx 124will call it 125.Ql mba%d . 126.It %d mba's not configured. 127More 128.Tn MASSBUS 129adapters were found on 130the machine than were declared in the machine configuration; the excess 131.Tn MASSBUS 132adapters will not be accessible. 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.It dr32 unsupported (at tr %d). 145A 146.Tn DR Ns 32 147interface was found in 148a 149.Tn NEXUS , 150for which 151.Nx 152does not have a driver. 153.It ci unsupported (at tr %d). 154A 155.Tn CI 156interface was found in 157a 158.Tn NEXUS , 159for which 160.Nx 161does not have a driver. 162.It mcr%d at tr%d. 163A memory controller was found in 164.Ql tr%d 165(the 166.Tn NEXUS 167slot number). 168.Nx 169will call it 170.Ql mcr%d . 171.It 5 mcr's unsupported. 172.Nx 173supports only 4 memory controllers 174per 175.Tn CPU . 176.It mpm unsupported (at tr%d). 177Multi-port memory is unsupported 178in the sense that 179.Nx 180does not know how to poll it for 181.Tn ECC 182errors. 183.It %s%d at mba%d drive %d. 184A tape formatter or a disk was found 185on the 186.Tn MASSBUS ; 187for disks 188.Ql %s%d 189will look like 190.Dq Li hp0 , 191for tape formatters 192like 193.Dq Li ht1 . 194The drive number comes from the unit plug on the drive 195or in the 196.Tn TM 197formatter 198.Pf ( Em not 199on the tape drive; see below). 200.It %s%d at %s%d slave %d. 201(For 202.Tn MASSBUS 203devices). 204Which would look like 205.Dq Li tu0 at ht0 slave 0 , 206where 207.Dq Li tu0 208is the name for the tape device and 209.Dq Li ht0 210is the name 211for the formatter. 212A tape slave was found on the tape formatter at the 213indicated drive number (on the front of the tape drive). 214.Ux 215will call the device, e.g., 216.Dq Li tu0 . 217.It "%s%d at uba%d csr %o vec %o ipl %x." 218The device 219.Ql %s%d , 220e.g. 221.Dq Li dz0 222was found on 223.Ql uba%d 224at control-status register address 225.Ql \&%o 226and with 227device vector 228.Ql \&%o . 229The device interrupted at priority level 230.Ql \&%x . 231.It %s%d at uba%d csr %o zero vector. 232The device did not present 233a valid interrupt vector, rather presented 0 (a passive release condition) 234to the adapter. 235.It %s%d at uba%d csr %o didn't interrupt. 236The device did not interrupt, 237likely because it is broken, hung, or not the kind of device it is advertised 238to be. 239.It %s%d at %s%d slave %d. 240(For UNIBUS devices). 241Which would look like 242.Dq Li up0 at sc0 slave 0 , 243where 244.Dq Li up0 245is the name of a disk drive and 246.Dq Li sc0 247is the name 248of the controller. 249Analogous to 250.Tn MASSBUS 251case. 252.El 253.Sh SEE ALSO 254.Xr config 1 , 255.Xr vax/intro 4 , 256.Xr boot 8 257.Sh HISTORY 258The 259.Nm 260feature 261appeared in 262.Bx 4.1 . 263