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
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
|
dnl $OpenBSD: prep,v 1.27 2015/09/20 15:24:39 miod Exp $
Before you install your system, you should identify your system family and
familiarize yourself with the ARCBios setup and how to run programs from
the Command monitor prompt.
Identifying your system:
Due to significant design differences in SGI systems, OpenBSD
needs to use different kernels, depending on the system family.
There are currently five system families supported by OpenBSD:
IP22 family:
Indigo (R4x00 flavour only)
Indigo2, Challenge M
Indy, Challenge S
IP26 family:
POWER Indigo2 (R8000)
IP27 family:
Origin 200, Onyx 2
Origin 2000
IP28 family:
POWER Indigo2 R10000
IP30 family:
Octane, Octane 2
IP32 family:
O2, O2+
IP35 family:
dnl Origin 300, Origin 3000, Onyx 300
Origin 350, Onyx 350
Fuel
Tezro
Onyx 4
You should use the kernels (bsd and bsd.rd) with the IP suffix
matching your family number, except for IP35 systems which use
IP27 kernels.
On Indigo2 systems, the particular family is not always easy to
figure out. When in doubt, access the maintenance console (see
below) and enter the ``version'' command. Its output will report
the IPxx family number of the system.
Accessing the Maintenance Console:
When the system starts up, press the ESC key or use the mouse and
click the ``stop for maintenance'' button. Once in the System
Maintenance Menu, select '5' (or click the appropriate icon if you
are using the graphics console) to go into the Command Monitor.
If the internal disk with the lowest SCSI ID does not contain a
valid Volume Header, but is bootable, the Maintenance Console will
be entered by default.
The first time the Maintenance Console is entered, it may be
necessary to force a reset of the environment to its default
settings by entering the ``resetenv'' command at the chevron
prompt. If some variables have been set explicitly, this may
disturb the normal OpenBSD boot process.
Switching from serial to graphics console and vice versa:
To change to serial console, go into the ARCBios Maintenance Console
and change the ``console'' environment variable, and power-cycle
the machine.
>> setenv console d
will select 8N1, no flow control, serial console on the first serial
port (labeled ``(1)''), while
>> setenv console g
will select the graphics console.
The speed of the serial console is controlled by the ``dbaud'' environment
variable, and defaults to 9600 bps if this variable is not set.
Not all graphics options are currently supported by OpenBSD. If your
system is configured for graphics console but the kernel does not
support your frame buffer, it will fallback to serial console on the
first serial port.
As of OpenBSD OSREV, the only unsupported graphics console devices are:
- Infinite Reality (Kona) frame buffer on IP27/IP35 Onyx systems
- Voyager (Ultimate Vision) frame buffer on IP35 Onyx 4 systems
Switching from L1 console to serial console and vice versa:
IP35 systems without a graphics console can have the PROM console output
either on the L1 console serial port, or the regular serial port.
The `console' command at the PROM prompt, can select between them:
>> console sc
will switch to the L1 serial port, while
>> console ioc3
or
>> console ioc4
will select the regular serial port, depending on the I/O board type.
On Fuel systems, there is no external L1 serial port, so `console sc'
should never be used on these machines.
Origin 300 and 3000 families can switch between `sc' and `ioc3', while
Origin 350 and 3500 families (including Tezro and Onyx 4) can switch
between `sc' and `ioc4'.
The OpenBSD kernel only supports serial console on the regular serial
ports; if your PROM console is on the L1 port, the kernel console will
nevertheless pick the first IOC3 or IOC4 serial port.
Setting the environment:
When setting up the system to boot from disk, the ``OSLoader''
environment variable will need to be changed.
Its default value is ``sashARCS'', ``sash'' or ``sash64'', which is
IRIX's standalone shell and loader. Set it to ``boot'', the name under
which the OpenBSD boot loader has been installed.
The kernel image loaded by default is specified in the ``OSLoadFilename''
variable, which defaults to ``unix''. To boot OpenBSD, set it to
``bsd''.
To enable automatic booting of OpenBSD once the machine has passed its
diagnostic tests, change the value of ``AutoLoad'' to ``Yes''.
|
