diff options
Diffstat (limited to 'static/netbsd/man4/man4.vax/autoconf.4 3.html')
| -rw-r--r-- | static/netbsd/man4/man4.vax/autoconf.4 3.html | 136 |
1 files changed, 0 insertions, 136 deletions
diff --git a/static/netbsd/man4/man4.vax/autoconf.4 3.html b/static/netbsd/man4/man4.vax/autoconf.4 3.html deleted file mode 100644 index ad3d0792..00000000 --- a/static/netbsd/man4/man4.vax/autoconf.4 3.html +++ /dev/null @@ -1,136 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">AUTOCONF(4)</td> - <td class="head-vol">Device Drivers Manual (vax)</td> - <td class="head-rtitle">AUTOCONF(4)</td> - </tr> -</table> -<div class="manual-text"> -<section class="Sh"> -<h1 class="Sh" id="NAME"><a class="permalink" href="#NAME">NAME</a></h1> -<p class="Pp"><code class="Nm">autoconf</code> — - <span class="Nd">diagnostics from the autoconfiguration code</span></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1> -<p class="Pp">When <span class="Ux">NetBSD</span> bootstraps it probes the - innards of the machine on which it is running and locates controllers, - drives, and other devices. Each item found is recorded on the console. This - procedure is driven by a system configuration table which is processed by - <a class="Xr">config(1)</a> and compiled into each kernel.</p> -<p class="Pp">On the VAX, devices in NEXUS slots are normally noted, thus memory - controllers, UNIBUS and MASSBUS adaptors. Devices which are not supported - which are found in NEXUS slots are noted also. The Q-bus on the MICROVAX is - configured in the same way as the UNIBUS.</p> -<p class="Pp">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.</p> -<p class="Pp">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.</p> -<p class="Pp">Normally, the system uses the disk from which it was loaded as the - root filesystem. If that is not possible, a generic system will pick its - root device as the “best” available device (MASSBUS disks are - better than SMD UNIBUS disks are better than RK07s; the device must be drive - 0 to be considered). If such a system is booted with the - <code class="Dv">RB_ASKNAME</code> option (see <a class="Xr">reboot(2)</a>), - then the name of the root device is read from the console terminal at boot - time, and any available device may be used.</p> -</section> -<section class="Sh"> -<h1 class="Sh" id="DIAGNOSTICS"><a class="permalink" href="#DIAGNOSTICS">DIAGNOSTICS</a></h1> -<dl class="Bl-diag"> - <dt>cpu type %d not configured.</dt> - <dd>You tried to boot <span class="Ux">NetBSD</span> on a CPU type which it - doesn't (or at least this compiled version of - <span class="Ux">NetBSD</span> doesn't) understand.</dd> - <dt>mba%d at tr%d.</dt> - <dd>A MASSBUS adapter was found in - ‘<code class="Li">tr%d</code>’ (the NEXUS slot number). - <span class="Ux">NetBSD</span> will call it - ‘<code class="Li">mba%d</code>’.</dd> - <dt>%d mba's not configured.</dt> - <dd>More MASSBUS adapters were found on the machine than were declared in the - machine configuration; the excess MASSBUS adapters will not be - accessible.</dd> - <dt>uba%d at tr%d.</dt> - <dd>A UNIBUS adapter was found in ‘<code class="Li">tr%d</code>’ - (the NEXUS slot number). <span class="Ux">NetBSD</span> will call it - ‘<code class="Li">uba%d</code>’.</dd> - <dt>dr32 unsupported (at tr %d).</dt> - <dd>A DR32 interface was found in a NEXUS, for which - <span class="Ux">NetBSD</span> does not have a driver.</dd> - <dt>ci unsupported (at tr %d).</dt> - <dd>A CI interface was found in a NEXUS, for which - <span class="Ux">NetBSD</span> does not have a driver.</dd> - <dt>mcr%d at tr%d.</dt> - <dd>A memory controller was found in - ‘<code class="Li">tr%d</code>’ (the NEXUS slot number). - <span class="Ux">NetBSD</span> will call it - ‘<code class="Li">mcr%d</code>’.</dd> - <dt>5 mcr's unsupported.</dt> - <dd><span class="Ux">NetBSD</span> supports only 4 memory controllers per - CPU.</dd> - <dt>mpm unsupported (at tr%d).</dt> - <dd>Multi-port memory is unsupported in the sense that - <span class="Ux">NetBSD</span> does not know how to poll it for ECC - errors.</dd> - <dt id="not">%s%d at mba%d drive %d.</dt> - <dd>A tape formatter or a disk was found on the MASSBUS; for disks - ‘<code class="Li">%s%d</code>’ will look like - “<code class="Li">hp0</code>”, for tape formatters like - “<code class="Li">ht1</code>”. The drive number comes from - the unit plug on the drive or in the TM formatter - (<a class="permalink" href="#not"><i class="Em">not</i></a> on the tape - drive; see below).</dd> - <dt>%s%d at %s%d slave %d.</dt> - <dd>(For MASSBUS devices). Which would look like “<code class="Li">tu0 - at ht0 slave 0</code>”, where - “<code class="Li">tu0</code>” is the name for the tape - device and “<code class="Li">ht0</code>” is the name for the - formatter. A tape slave was found on the tape formatter at the indicated - drive number (on the front of the tape drive). - <span class="Ux">UNIX</span> will call the device, e.g., - “<code class="Li">tu0</code>”.</dd> - <dt>%s%d at uba%d csr %o vec %o ipl %x.</dt> - <dd>The device ‘<code class="Li">%s%d</code>’, e.g. - “<code class="Li">dz0</code>” was found on - ‘<code class="Li">uba%d</code>’ at control-status register - address ‘<code class="Li">%o</code>’ and with device vector - ‘<code class="Li">%o</code>’. The device interrupted at - priority level ‘<code class="Li">%x</code>’.</dd> - <dt>%s%d at uba%d csr %o zero vector.</dt> - <dd>The device did not present a valid interrupt vector, rather presented 0 (a - passive release condition) to the adapter.</dd> - <dt>%s%d at uba%d csr %o didn't interrupt.</dt> - <dd>The device did not interrupt, likely because it is broken, hung, or not - the kind of device it is advertised to be.</dd> - <dt>%s%d at %s%d slave %d.</dt> - <dd>(For UNIBUS devices). Which would look like “<code class="Li">up0 - at sc0 slave 0</code>”, where - “<code class="Li">up0</code>” is the name of a disk drive - and “<code class="Li">sc0</code>” is the name of the - controller. Analogous to MASSBUS case.</dd> -</dl> -</section> -<section class="Sh"> -<h1 class="Sh" id="SEE_ALSO"><a class="permalink" href="#SEE_ALSO">SEE - ALSO</a></h1> -<p class="Pp"><a class="Xr">config(1)</a>, <a class="Xr">vax/intro(4)</a>, - <a class="Xr">boot(8)</a></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="HISTORY"><a class="permalink" href="#HISTORY">HISTORY</a></h1> -<p class="Pp">The <code class="Nm">autoconf</code> feature appeared in - <span class="Ux">4.1BSD</span>.</p> -</section> -</div> -<table class="foot"> - <tr> - <td class="foot-date">February 17, 2017</td> - <td class="foot-os">NetBSD 10.1</td> - </tr> -</table> |