autoconf(4)
NAME
autoconf − diagnostics from the autoconfiguration code
DESCRIPTION
When UNIX bootstraps it probes the innards of the machine it is running on and locates controllers, drives, and other devices, printing out what it finds on the console. This procedure is driven by a system configuration table which is processed by config(8) and compiled into each kernel.
Devices in NEXUS slots are normally noted, thus memory controllers, UNIBUS, MASSBUS, and VAXBI adapters. Devices which are not supported which are found in NEXUS slots are noted also.
VAXBI devices are located by a very deterministic procedure since VAXBI space can be probed completely. Existing devices are noted on the console if they are not configured, or if they are unsupported devices.
MASSBUS devices are located by a very deterministic procedure since MASSBUS space is completely probe-able. If devices exist which are not configured they will be silently ignored; if devices exist of unsupported type they will be noted.
UNIBUS devices are located by probing to see if their control-status registers respond. If not, they are silently ignored. If the control status register responds but the device cannot be made to interrupt, a diagnostic warning will be printed on the console and the device will not be available to the system.
DIAGNOSTICS
No configure routine for cpu type %d. An attempt was made to boot UNIX on a cpu type which it doesn’t (or at least this compiled version of UNIX doesn’t) understand.
mba%d at address 0x%x. A MASSBUS adapter was found at address 0x%x. UNIX will call it mba%d.
%d mba’s not configured. More MASSBUS adapters were found on the machine than were declared in the machine configuration; the excess MASSBUS adapters will not be accessible.
uba%d at address 0x%x. A UNIBUS adapter was found at address 0x%d. UNIX will call it uba%d.
dr32 unsupported at address 0x%d. A DR32 interface was found at address 0x%d, for which UNIX does not have a driver.
ci unsupported at address 0x%d. A CI interface was found at address 0x%d, for which UNIX does not have a driver.
mcr%d at address 0x%x. A memory controller was found at address 0x%d. UNIX will call it mcr%d.
5 mcr’s unsupported at address 0x%d. UNIX supports only 4 memory controllers per cpu.
mpm unsupported at address 0x%x. Multi-port memory is unsupported in the sense that UNIX does not know how to poll it for ECC errors.
%s%d at mba%d drive %d. A tape formatter or a disk was found on the MASSBUS; for disks %s%d will look like “hp0”, for tape formatters like “ht1”. The drive number comes from the unit plug on the drive or in the TM formatter (not on the tape drive; see below).
%s%d at %s%d slave %d (for MASSBUS devices). A tape slave was found on the tape formatter at the indicated drive number (on the front of the tape drive). UNIX will call the device, e.g., tu0. For example, “tu0 at ht0 slave 0”, where tu0 is the name for the tape device and ht0 is the name for the formatter.
%s%d at %s%d slave %d (for UNIBUS and VAXBI devices). Which would look like “ra0 at uq0 slave 0”, where ra0 is the name of a disk drive and uq0 is the name of the port protocol.
%s%d at uba%d csr %o vec %o ipl %x. The device %s%d, e.g. dz0 was found on uba%d at control-status register address %o and with device vector %o. The device interrupted at priority level %x.
%s%d at uba%d csr %o zero vector. The device did not present a valid interrupt vector, rather presented 0 (a passive release condition) to the adapter.
%s%d at uba%d csr %o didn’t interrupt. The device did not interrupt, possibly because it is broken, hung, or not the kind of device it is advertised to be.
%s%d at %s%d csr %o vec %o ipl %x (for UNIBUS and VAXBI controllers). The port %s%d, for example, uq0 was found on controller %s%d at control-status register address %o and with controller interrupt vector %o. The controller interrupted at priority level %x.
%s%d at %s%d csr %o zero vector (for UNIBUS and VAXBI controllers). The port did not present a valid interrupt vector, rather presented 0 (a passive release condition) to the adapter.
%s%d at %s%d csr %o didn’t interrupt (for UNIBUS and VAXBI controllers). The port did not interrupt, possibly because it is broken, hung, or not the kind of port it is advertised to be.
nbia%d at address %x. An nbia adapter was found at a NEXUS.
vaxbi%d at address %x. A vaxbi number was found starting at address %x.
%s%d at vaxbi%d node %d. The device, controller, or adapter %s%d was found on vaxbi%d at node%d.
vaxbi%x node%d, unsupported device type 0x%x. On a vaxbi%x at node%d there is a device with type number 0x%x that is unsupported by this release of ULTRIX.
%s at vaxbi%d node%d option not configured!. A supported vaxbi device %s, found at vaxbi%d node%d was not configured into the system. The device %s will not be seen by the system. To use device %s, configure the system with the device included in the configuration file.
%s at vaxbi%d node%d failed to initialize!. The device did not initialize, possibly because it was broken.