| 1 |
neysx 07/02/07 15:12:44 |
| 2 |
|
| 3 |
Modified: hb-install-mips-bootloader.xml |
| 4 |
Log: |
| 5 |
#165769 arcload Installation Instruction Update |
| 6 |
|
| 7 |
Revision Changes Path |
| 8 |
1.17 xml/htdocs/doc/en/handbook/hb-install-mips-bootloader.xml |
| 9 |
|
| 10 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-install-mips-bootloader.xml?rev=1.17&view=markup |
| 11 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-install-mips-bootloader.xml?rev=1.17&content-type=text/plain |
| 12 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-install-mips-bootloader.xml?r1=1.16&r2=1.17 |
| 13 |
|
| 14 |
Index: hb-install-mips-bootloader.xml |
| 15 |
=================================================================== |
| 16 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-mips-bootloader.xml,v |
| 17 |
retrieving revision 1.16 |
| 18 |
retrieving revision 1.17 |
| 19 |
diff -u -r1.16 -r1.17 |
| 20 |
--- hb-install-mips-bootloader.xml 30 Aug 2006 22:52:28 -0000 1.16 |
| 21 |
+++ hb-install-mips-bootloader.xml 7 Feb 2007 15:12:43 -0000 1.17 |
| 22 |
@@ -4,12 +4,12 @@ |
| 23 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
| 24 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
| 25 |
|
| 26 |
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-mips-bootloader.xml,v 1.16 2006/08/30 22:52:28 nightmorph Exp $ --> |
| 27 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-mips-bootloader.xml,v 1.17 2007/02/07 15:12:43 neysx Exp $ --> |
| 28 |
|
| 29 |
<sections> |
| 30 |
|
| 31 |
-<version>7.0</version> |
| 32 |
-<date>2006-08-30</date> |
| 33 |
+<version>7.1</version> |
| 34 |
+<date>2007-02-08</date> |
| 35 |
|
| 36 |
<section id="sgi"> |
| 37 |
<title>Silicon Graphics Machines -- Setting Up arcload</title> |
| 38 |
@@ -20,52 +20,9 @@ |
| 39 |
<p> |
| 40 |
On SGI machines, we use the <c>arcload</c> boot loader. In previous releases, |
| 41 |
we also provided <c>arcboot</c>, however it has been officially declared |
| 42 |
-obsolete, in favour of <c>arcload</c>. |
| 43 |
+obsolete, in favour of <c>arcload</c>. |
| 44 |
</p> |
| 45 |
|
| 46 |
-<!-- Slated for possible removal |
| 47 |
-<table> |
| 48 |
-<tr> |
| 49 |
- <th> </th> |
| 50 |
- <th>arcboot</th> |
| 51 |
-</tr> |
| 52 |
-<tr> |
| 53 |
- <th>+</th> |
| 54 |
- <ti> |
| 55 |
- It can load off EXT2 and EXT3 partitions, so no need to store them in the |
| 56 |
- volume header |
| 57 |
- </ti> |
| 58 |
-</tr> |
| 59 |
-<tr> |
| 60 |
- <th>-</th> |
| 61 |
- <ti> |
| 62 |
- It doesn't work on Octane/Octane2, Origin 200/2000 or Indigo2 Impact |
| 63 |
- (R10000) |
| 64 |
- </ti> |
| 65 |
-</tr> |
| 66 |
-</table> |
| 67 |
- |
| 68 |
-<table> |
| 69 |
-<tr> |
| 70 |
- <th> </th> |
| 71 |
- <th>arcload</th> |
| 72 |
-</tr> |
| 73 |
-<tr> |
| 74 |
- <th>+</th> |
| 75 |
- <ti> |
| 76 |
- It boots ALL Linux-compatible SGI systems |
| 77 |
- </ti> |
| 78 |
-</tr> |
| 79 |
-<tr> |
| 80 |
- <th>-</th> |
| 81 |
- <ti> |
| 82 |
- Currently, It cannot read EXT2/EXT3 partitions, and so needs the kernels |
| 83 |
- and config file to be placed in the volume header |
| 84 |
- </ti> |
| 85 |
-</tr> |
| 86 |
-</table> |
| 87 |
---> |
| 88 |
- |
| 89 |
<note> |
| 90 |
The SGI volume header filenames are limited to 8 characters, and there may be |
| 91 |
no more than 16 files contained in a single volume header. |
| 92 |
@@ -74,146 +31,6 @@ |
| 93 |
</body> |
| 94 |
</subsection> |
| 95 |
|
| 96 |
-<!--<subsection> |
| 97 |
-<title>Installing arcboot</title> |
| 98 |
-<body> |
| 99 |
- |
| 100 |
-<warn> |
| 101 |
-<c>arcboot</c> is deprecated and will be removed in future. |
| 102 |
-</warn> |
| 103 |
- |
| 104 |
-<p> |
| 105 |
-Previously in this guide, we showed you how to make a kernel, then copy it to |
| 106 |
-the volume header using <c>dvhtool</c>. There were two main flaws with this |
| 107 |
-system: |
| 108 |
-</p> |
| 109 |
- |
| 110 |
-<ul> |
| 111 |
- <li>This is not supported on all SGI systems</li> |
| 112 |
- <li>It requires a significantly larger volume header</li> |
| 113 |
-</ul> |
| 114 |
- |
| 115 |
-<p> |
| 116 |
-In order to boot the machine, a bootloader, <c>arcboot</c> was developed for |
| 117 |
-this purpose. Instead of putting the kernel directly into the volume header, we |
| 118 |
-leave it in <path>/boot</path> (which resides on a EXT2/3 partition), and tell |
| 119 |
-<c>arcboot</c> (which sits in the volume header in place of the kernel) where |
| 120 |
-to find it. So our first step, is to emerge some tools that we'll use later... |
| 121 |
-</p> |
| 122 |
- |
| 123 |
-<pre caption="Installing the required tools"> |
| 124 |
-# <i>emerge dvhtool arcboot</i> |
| 125 |
-</pre> |
| 126 |
- |
| 127 |
-<p> |
| 128 |
-That should have installed two tools, <c>arcboot</c> which sits in the volume |
| 129 |
-header and loads kernels for us, and <c>dvhtool</c> which helps us put |
| 130 |
-<c>arcboot</c> into the volume header. |
| 131 |
-</p> |
| 132 |
- |
| 133 |
-<p> |
| 134 |
-The <c>arcboot</c> binary lurks in <path>/usr/lib/arcboot</path>. The name of |
| 135 |
-the binary depends on the machine it's compiled for. |
| 136 |
-</p> |
| 137 |
- |
| 138 |
-<ul> |
| 139 |
- <li> |
| 140 |
- <c>arcboot.ip22</c>: The binary for Indy, Indigo2 (R4k) and Challenge S |
| 141 |
- systems |
| 142 |
- </li> |
| 143 |
- <li> |
| 144 |
- <c>arcboot.ip32</c>: The binary for O2 systems |
| 145 |
- </li> |
| 146 |
-</ul> |
| 147 |
- |
| 148 |
-<pre caption="Installing arcboot into the volume header"> |
| 149 |
-# <i>dvhtool - -unix-to-vh /usr/lib/arcboot/arcboot.ip?? arcboot</i> |
| 150 |
-</pre> |
| 151 |
- |
| 152 |
-<p> |
| 153 |
-We then verify the presence of the file in the volume header. |
| 154 |
-</p> |
| 155 |
- |
| 156 |
-<pre caption="Checking if arcboot made it okay"> |
| 157 |
-# <i>dvhtool - -print-volume-directory</i> |
| 158 |
-- - - - - directory entries - - - - - |
| 159 |
-Entry #0, name "linux", start 4, bytes 3262570 |
| 160 |
-Entry #1, name "newlinux", start 6377, bytes 7619627 |
| 161 |
-Entry #3, name "arcboot", start 21260, bytes 51448 |
| 162 |
-# |
| 163 |
-</pre> |
| 164 |
- |
| 165 |
-<note> |
| 166 |
-You'll notice that in the example above, there are two old kernels sitting |
| 167 |
-around, <path>linux</path> and <path>newlinux</path>. This is a hangover from |
| 168 |
-before we started using <c>arcboot</c>. Their presence doesn't matter - - just |
| 169 |
-so long as <c>arcboot</c> is present, everything is fine. |
| 170 |
-</note> |
| 171 |
- |
| 172 |
-<p> |
| 173 |
-If you've ever set up the Linux Loader (<c>lilo</c>) before, you'll find that |
| 174 |
-<c>arcboot</c> employs a similar syntax in its configuration file. Bear in mind |
| 175 |
-though; <c>arcboot</c> expects to find its configuration file existing on an |
| 176 |
-EXT2/3 partition as <path>/etc/arcboot.conf</path>. The easiest way around this |
| 177 |
-is to make sure <path>/boot</path> is an EXT2/3 partition and that there's a |
| 178 |
-file called <path>arcboot.conf</path> inside the <path>/boot/etc</path> |
| 179 |
-directory. An example config can be found in |
| 180 |
-<path>/etc/arcboot.conf.sample</path>. |
| 181 |
-</p> |
| 182 |
- |
| 183 |
-<note> |
| 184 |
-Adjust the paths accordingly if you don't have a separate <path>/boot</path> |
| 185 |
-partition. |
| 186 |
-</note> |
| 187 |
- |
| 188 |
-<pre caption="Putting arcboot.conf in its place"> |
| 189 |
-<comment>(Create the /boot/etc directory)</comment> |
| 190 |
-# <i>mkdir /boot/etc</i> |
| 191 |
- |
| 192 |
-<comment>(Put our configuration into the target directory)</comment> |
| 193 |
-# <i>cp /etc/arcboot.conf.sample /boot/etc/arcboot.conf</i> |
| 194 |
- |
| 195 |
-<comment>(Create a symlink back to /etc)</comment> |
| 196 |
-# <i>ln -s /boot/etc/arcboot.conf /etc/arcboot.conf</i> |
| 197 |
- |
| 198 |
-<comment>(... and a symlink in /boot pointing to itself)</comment> |
| 199 |
-# <i>(cd /boot; ln -s . boot)</i> |
| 200 |
-</pre> |
| 201 |
- |
| 202 |
-<p> |
| 203 |
-You can then edit <path>/etc/arcboot.conf</path> to your own preference. One |
| 204 |
-possible layout, is to set up two kernel images: <path>new</path>, a freshly |
| 205 |
-built image that may or may not work; and <path>working</path>, a proven |
| 206 |
-trustworthy kernel image. The <path>arcboot.conf</path> for that setup looks a |
| 207 |
-bit like this. |
| 208 |
-</p> |
| 209 |
- |
| 210 |
-<pre caption="Example arcboot.conf"> |
| 211 |
-<comment># arcboot.conf</comment> |
| 212 |
-<comment>#</comment> |
| 213 |
-<comment># copyright 2002 Guido Guenther <agx@×××××××.org></comment> |
| 214 |
-<comment>#</comment> |
| 215 |
-<comment># known working version</comment> |
| 216 |
-label=working |
| 217 |
- image=/vmlinux |
| 218 |
- append="root=/dev/sda3" |
| 219 |
- |
| 220 |
-<comment># fresh "untested" version</comment> |
| 221 |
-label=new |
| 222 |
- image=/vmlinux-new |
| 223 |
- append="root=/dev/sda3" |
| 224 |
-</pre> |
| 225 |
- |
| 226 |
-<p> |
| 227 |
-Once that is set up, there's then just some little tweaks that you need to do |
| 228 |
-within the SGI PROM to make this magic work. This is covered in, not the next |
| 229 |
-section (that's for Cobalt servers) but the following section <uri |
| 230 |
-link="#reboot">Rebooting the System</uri>. |
| 231 |
-</p> |
| 232 |
- |
| 233 |
-</body> |
| 234 |
-</subsection> |
| 235 |
---> |
| 236 |
<subsection> |
| 237 |
<title>Installing arcload</title> |
| 238 |
<body> |
| 239 |
@@ -319,17 +136,13 @@ |
| 240 |
</pre> |
| 241 |
|
| 242 |
<p> |
| 243 |
-This is then placed in the volume header with <c>sash64</c> (or |
| 244 |
-<c>sashARCS</c>) as shown below. Kernels also get placed in the volume header. |
| 245 |
+Starting with <c>arcload-0.5</c>, <path>arc.cf</path> and kernels may |
| 246 |
+reside either in the volume header, or on an EXT2/3 partition. If you wish to |
| 247 |
+utilise this newer feature, you may instead place the files in your |
| 248 |
+<path>/boot</path> partition (or <path>/</path> if your boot partition is not |
| 249 |
+separate). |
| 250 |
</p> |
| 251 |
|
| 252 |
-<note> |
| 253 |
-With <c>arcload</c> 0.5, it is possible to load these files from an EXT3 |
| 254 |
-partition, rather than loading these into the volume header. If you are |
| 255 |
-using the newer release, you may skip copying these to the volume |
| 256 |
-header, and instead, place them in your <c>/boot</c> partition. |
| 257 |
-</note> |
| 258 |
- |
| 259 |
<pre caption="Placing arc.cf and kernel in the volume header"> |
| 260 |
# <i>dvhtool --unix-to-vh arc.cf arc.cf</i> |
| 261 |
# <i>dvhtool --unix-to-vh /usr/src/linux/vmlinux new</i> |
| 262 |
@@ -597,7 +410,7 @@ |
| 263 |
|
| 264 |
<note> |
| 265 |
<e>Cobalt Users:</e> The rest of this section covers the setting up of the SGI |
| 266 |
-PROM so that it boots <!--<c>arcboot</c>/--><c>arcload</c> off disk and loads |
| 267 |
+PROM so that it boots <c>arcload</c> off disk and loads |
| 268 |
Linux. |
| 269 |
This is not applicable to the setup of Cobalt servers. In fact, all your work |
| 270 |
is done -- there is no configuration needed for the first boot up, you can skip |
| 271 |
@@ -731,50 +544,35 @@ |
| 272 |
|
| 273 |
<pre caption="PROM settings for using arcload"> |
| 274 |
<comment>(Select arcload as the bootloader:- sash64 or sashARCS)</comment> |
| 275 |
->> setenv OSLoader sash64 |
| 276 |
+>> <i>setenv OSLoader sash64</i> |
| 277 |
|
| 278 |
<comment>(Use the "working" kernel image, defined in "ip28" section of arc.cf)</comment> |
| 279 |
->> setenv OSLoadFilename ip28(working) |
| 280 |
+>> <i>setenv OSLoadFilename ip28(working)</i> |
| 281 |
</pre> |
| 282 |
|
| 283 |
-</body> |
| 284 |
-</subsection> |
| 285 |
- |
| 286 |
-<!-- Slated for removal |
| 287 |
-<subsection> |
| 288 |
-<title>Settings for arcboot</title> |
| 289 |
-<body> |
| 290 |
- |
| 291 |
<p> |
| 292 |
-<c>arcboot</c> loads its configuration file and kernels from your |
| 293 |
-<path>/boot</path> partition, which needs to be formatted either EXT2 or EXT3. |
| 294 |
-Thus <c>OSLoadPartition</c> needs to point to that partition. <c>OSLoader</c> |
| 295 |
-should point to the <c>arcboot</c> binary in the volume header, and |
| 296 |
-<c>OSLoadFilename</c> is the image name being used. |
| 297 |
+Starting with <c>arcload-0.5</c>, files no longer need to be placed in the |
| 298 |
+volume header -- they may be placed in an EXT2/3 partition instead. To tell |
| 299 |
+<c>arcload</c> where to look for its configuration file and kernels, one must |
| 300 |
+set the <c>OSLoadPartition</c> PROM variable. The exact value here will depend |
| 301 |
+on where your disk resides on the SCSI bus. Use the <c>SystemPartition</c> PROM |
| 302 |
+variable as a guide -- only the partition number should need to change. |
| 303 |
</p> |
| 304 |
|
| 305 |
-<pre caption="PROM settings for using arcboot"> |
| 306 |
-<comment>(Read configuration and kernels from SCSI ID# 1, partition 0 - - sda1)</comment> |
| 307 |
->> <i>setenv OSLoadPartition scsi(0)disk(1)rdisk(0)partition(0)</i> |
| 308 |
- |
| 309 |
-<comment>(Use arcboot as the bootloader)</comment> |
| 310 |
->> <i>setenv OSLoader arcboot</i> |
| 311 |
- |
| 312 |
-<comment>(Which boot image in arcboot.conf to load)</comment> |
| 313 |
->> <i>setenv OSLoadFilename working</i> |
| 314 |
-</pre> |
| 315 |
+<note> |
| 316 |
+Partitions are numbered starting at 0, not 1 as is the case in Linux. |
| 317 |
+</note> |
| 318 |
|
| 319 |
-<p> |
| 320 |
-When testing kernels via <c>arcboot</c> you can specify an alternate image like |
| 321 |
-so (where <c>new</c> is the alternate image): |
| 322 |
-</p> |
| 323 |
+<pre caption="Telling arcload where to find arc.cf"> |
| 324 |
+<comment>(If you wish to load from the volume header -- use partition 8)</comment> |
| 325 |
+>> <i>setenv OSLoadPartition scsi(0)disk(1)rdisk(0)partition(8)</i> |
| 326 |
|
| 327 |
-<pre caption="Specifying an alternate image"> |
| 328 |
-# <i>boot new</i> |
| 329 |
+<comment>(Otherwise, specify the partition and filesystem type)</comment> |
| 330 |
+>> <i>setenv OSLoadPartition scsi(0)disk(1)rdisk(0)partition(0)[ext2]</i> |
| 331 |
</pre> |
| 332 |
|
| 333 |
</body> |
| 334 |
-</subsection> --> |
| 335 |
+</subsection> |
| 336 |
|
| 337 |
<subsection> |
| 338 |
<title>All Done</title> |
| 339 |
|
| 340 |
|
| 341 |
|
| 342 |
-- |
| 343 |
gentoo-doc-cvs@g.o mailing list |
Archives