summaryrefslogtreecommitdiff
path: root/static/netbsd/man4/man4.hp300/autoconf.4 3.html
blob: 9507fdd291612d6042029195f804005dbc71380c (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
<table class="head">
  <tr>
    <td class="head-ltitle">AUTOCONF(4)</td>
    <td class="head-vol">Device Drivers Manual (hp300)</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> &#x2014;
    <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, printing out what it finds 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">Autoconfiguration on the HP300s is similar to that on the VAX, the
    primary difference is in the naming conventions. On the HP300, if devices
    exist which are not configured they will be ignored; if devices exist of
    unsupported type they will be ignored.</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 use
    &#x2018;<code class="Li">rd0</code>&#x2019; if it exists. 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>SPU type not configured</dt>
  <dd>You tried to boot <span class="Ux">NetBSD</span> on an SPU type which it
      doesn't (or at least this compiled version of
      <span class="Ux">NetBSD</span> doesn't) understand.</dd>
  <dt>nhpib%d at intio0 addr 0x478000 ipl %d</dt>
  <dd></dd>
  <dt>nhpib%d at dio0 scode %d ipl %d</dt>
  <dd></dd>
  <dt>fhpib%d at dio0 scode %d ipl %d</dt>
  <dd></dd>
  <dt>hpibbus%d at nhpib%d</dt>
  <dd></dd>
  <dt>hpibbus%d at fhpib%d</dt>
  <dd>An HP-IB was found at the internal bus or scode %d (the select code) with
      ipl %d (interrupt priority level). <span class="Ux">NetBSD</span> will
      call it hpibbus%d.</dd>
  <dt>%s%d at hpibbus%d slave %d punit %d</dt>
  <dd></dd>
  <dt>%s%d: %s</dt>
  <dd>An HP-IB disk or tape controller was found. For disks
      &#x2018;<code class="Li">%s%d</code>&#x2019; will look like
      &#x2018;<code class="Li">rd0</code>&#x2019;, for tapes like
      &#x2018;<code class="Li">ct0</code>&#x2019;. The
      &#x2018;<code class="Li">%s</code>&#x2019; in the first line will be a
      product type like ``7945A'' or ``9144''. The slave number comes from the
      address select switches on the drive.</dd>
  <dt>dvbox0 at intio0 addr 0x560000</dt>
  <dd></dd>
  <dt>dvbox%d at dio0 scode %d</dt>
  <dd></dd>
  <dt>gbox0 at intio0 addr 0x560000</dt>
  <dd></dd>
  <dt>gbox%d at dio0 scode %d</dt>
  <dd></dd>
  <dt>hyper%d at dio0 scode %d</dt>
  <dd></dd>
  <dt>rbox0 at intio0 addr 0x560000</dt>
  <dd></dd>
  <dt>rbox%d at dio0 scode %d</dt>
  <dd></dd>
  <dt>topcat0 at intio0 addr 0x560000</dt>
  <dd></dd>
  <dt>topcat%d at dio0 scode %d</dt>
  <dd></dd>
  <dt>tvrx%d at dio0 scode %d</dt>
  <dd></dd>
  <dt>gendiofb%d at dio0 scode %d</dt>
  <dd></dd>
  <dt>sti%d at sgc0 slot %d</dt>
  <dd>A bit mapped display was found either at the ``internal'' address, at some
      ``external'' select code, or at some SGC bus slot. If it exists, the
      internal display will always be unit 0.</dd>
  <dt>%s%d at dio0 scode %d ipl %d</dt>
  <dd>Another peripheral controller was found at the indicated select code and
      with indicated interrupt priority level.
      &#x2018;<code class="Li">%s</code>&#x2019; will be one of
      <a class="Xr">com(4)</a> (single-port serial interfaces),
      <a class="Xr">hp300/dcm(4)</a> (four-port serial interfaces), or
      <a class="Xr">le(4)</a> (LAN cards). The slave number comes from the
      address select switches on the interface card.</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">hp300/intro(4)</a>,
    <a class="Xr">boot(8)</a></p>
<p class="Pp"><cite class="Rs"><span class="RsT">4.3BSD for the HP300</span>,
    <span class="RsO">in the distribution documentation
  package</span>.</cite></p>
</section>
</div>
<table class="foot">
  <tr>
    <td class="foot-date">June 17, 2022</td>
    <td class="foot-os">NetBSD 10.1</td>
  </tr>
</table>