/[gentoo]/xml/htdocs/doc/en/handbook/hb-install-mips-bootloader.xml
Gentoo

Diff of /xml/htdocs/doc/en/handbook/hb-install-mips-bootloader.xml

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.15 Revision 1.16
2<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> 2<!DOCTYPE sections SYSTEM "/dtd/book.dtd">
3 3
4<!-- The content of this document is licensed under the CC-BY-SA license --> 4<!-- The content of this document is licensed under the CC-BY-SA license -->
5<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> 5<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
6 6
7<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-mips-bootloader.xml,v 1.15 2006/06/12 10:18:17 neysx Exp $ --> 7<!-- $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 $ -->
8 8
9<sections> 9<sections>
10 10
11<version>1.10</version> 11<version>7.0</version>
12<date>2006-02-27</date> 12<date>2006-08-30</date>
13 13
14<section id="sgi"> 14<section id="sgi">
15<title>Silicon Graphics Machines -- Setting Up arcboot/arcload</title> 15<title>Silicon Graphics Machines -- Setting Up arcload</title>
16<subsection> 16<subsection>
17<title>Which one?</title> 17<title>Which one?</title>
18<body> 18<body>
19 19
20<p> 20<p>
21On SGI machines, you have two options for bootloaders. <c>arcboot</c> and 21On SGI machines, we use the <c>arcload</c> boot loader. In previous releases,
22<c>arcload</c>. The table below lists the pros and cons for each bootloader. 22we also provided <c>arcboot</c>, however it has been officially declared
23obsolete, in favour of <c>arcload</c>.
23</p> 24</p>
24 25
26<!-- Slated for possible removal
25<table> 27<table>
26<tr> 28<tr>
27 <th> </th> 29 <th> </th>
28 <th>arcboot</th> 30 <th>arcboot</th>
29</tr> 31</tr>
60 Currently, It cannot read EXT2/EXT3 partitions, and so needs the kernels 62 Currently, It cannot read EXT2/EXT3 partitions, and so needs the kernels
61 and config file to be placed in the volume header 63 and config file to be placed in the volume header
62 </ti> 64 </ti>
63</tr> 65</tr>
64</table> 66</table>
67-->
65 68
66<note> 69<note>
67The SGI volume header filenames are limited to 8 characters, and there may be 70The SGI volume header filenames are limited to 8 characters, and there may be
68no more than 16 files contained in a single volume header. 71no more than 16 files contained in a single volume header.
69</note> 72</note>
70 73
71</body> 74</body>
72</subsection> 75</subsection>
73 76
74<subsection> 77<!--<subsection>
75<title>Installing arcboot</title> 78<title>Installing arcboot</title>
76<body> 79<body>
80
81<warn>
82<c>arcboot</c> is deprecated and will be removed in future.
83</warn>
77 84
78<p> 85<p>
79Previously in this guide, we showed you how to make a kernel, then copy it to 86Previously in this guide, we showed you how to make a kernel, then copy it to
80the volume header using <c>dvhtool</c>. There were two main flaws with this 87the volume header using <c>dvhtool</c>. There were two main flaws with this
81system: 88system:
118 <c>arcboot.ip32</c>: The binary for O2 systems 125 <c>arcboot.ip32</c>: The binary for O2 systems
119 </li> 126 </li>
120</ul> 127</ul>
121 128
122<pre caption="Installing arcboot into the volume header"> 129<pre caption="Installing arcboot into the volume header">
123# <i>dvhtool --unix-to-vh /usr/lib/arcboot/arcboot.ip?? arcboot</i> 130# <i>dvhtool - -unix-to-vh /usr/lib/arcboot/arcboot.ip?? arcboot</i>
124</pre> 131</pre>
125 132
126<p> 133<p>
127We then verify the presence of the file in the volume header. 134We then verify the presence of the file in the volume header.
128</p> 135</p>
129 136
130<pre caption="Checking if arcboot made it okay"> 137<pre caption="Checking if arcboot made it okay">
131# <i>dvhtool --print-volume-directory</i> 138# <i>dvhtool - -print-volume-directory</i>
132----- directory entries ----- 139- - - - - directory entries - - - - -
133Entry #0, name "linux", start 4, bytes 3262570 140Entry #0, name "linux", start 4, bytes 3262570
134Entry #1, name "newlinux", start 6377, bytes 7619627 141Entry #1, name "newlinux", start 6377, bytes 7619627
135Entry #3, name "arcboot", start 21260, bytes 51448 142Entry #3, name "arcboot", start 21260, bytes 51448
136# 143#
137</pre> 144</pre>
138 145
139<note> 146<note>
140You'll notice that in the example above, there are two old kernels sitting 147You'll notice that in the example above, there are two old kernels sitting
141around, <path>linux</path> and <path>newlinux</path>. This is a hangover from 148around, <path>linux</path> and <path>newlinux</path>. This is a hangover from
142before we started using <c>arcboot</c>. Their presence doesn't matter -- just 149before we started using <c>arcboot</c>. Their presence doesn't matter - - just
143so long as <c>arcboot</c> is present, everything is fine. 150so long as <c>arcboot</c> is present, everything is fine.
144</note> 151</note>
145 152
146<p> 153<p>
147If you've ever set up the Linux Loader (<c>lilo</c>) before, you'll find that 154If you've ever set up the Linux Loader (<c>lilo</c>) before, you'll find that
204link="#reboot">Rebooting the System</uri>. 211link="#reboot">Rebooting the System</uri>.
205</p> 212</p>
206 213
207</body> 214</body>
208</subsection> 215</subsection>
209 216-->
210<subsection> 217<subsection>
211<title>Installing arcload</title> 218<title>Installing arcload</title>
212<body> 219<body>
213 220
214<p> 221<p>
313 320
314<p> 321<p>
315This is then placed in the volume header with <c>sash64</c> (or 322This is then placed in the volume header with <c>sash64</c> (or
316<c>sashARCS</c>) as shown below. Kernels also get placed in the volume header. 323<c>sashARCS</c>) as shown below. Kernels also get placed in the volume header.
317</p> 324</p>
325
326<note>
327With <c>arcload</c> 0.5, it is possible to load these files from an EXT3
328partition, rather than loading these into the volume header. If you are
329using the newer release, you may skip copying these to the volume
330header, and instead, place them in your <c>/boot</c> partition.
331</note>
318 332
319<pre caption="Placing arc.cf and kernel in the volume header"> 333<pre caption="Placing arc.cf and kernel in the volume header">
320# <i>dvhtool --unix-to-vh arc.cf arc.cf</i> 334# <i>dvhtool --unix-to-vh arc.cf arc.cf</i>
321# <i>dvhtool --unix-to-vh /usr/src/linux/vmlinux new</i> 335# <i>dvhtool --unix-to-vh /usr/src/linux/vmlinux new</i>
322</pre> 336</pre>
581cdimage ~# <i>reboot</i> 595cdimage ~# <i>reboot</i>
582</pre> 596</pre>
583 597
584<note> 598<note>
585<e>Cobalt Users:</e> The rest of this section covers the setting up of the SGI 599<e>Cobalt Users:</e> The rest of this section covers the setting up of the SGI
586PROM so that it boots <c>arcboot</c>/<c>arcload</c> off disk and loads Linux. 600PROM so that it boots <!--<c>arcboot</c>/--><c>arcload</c> off disk and loads
601Linux.
587This is not applicable to the setup of Cobalt servers. In fact, all your work 602This is not applicable to the setup of Cobalt servers. In fact, all your work
588is done -- there is no configuration needed for the first boot up, you can skip 603is done -- there is no configuration needed for the first boot up, you can skip
589to the next section: <uri link="?part=1&amp;chap=11">Finalising your Gentoo 604to the next section: <uri link="?part=1&amp;chap=11">Finalising your Gentoo
590Installation</uri> 605Installation</uri>
591</note> 606</note>
6295) Enter Command Monitor 6445) Enter Command Monitor
630 645
631Option? <i>5</i> 646Option? <i>5</i>
632Command Monitor. Type "exit" to return to the menu. 647Command Monitor. Type "exit" to return to the menu.
633 648
634<comment>(Set some options which are common for both arcload and arcboot)</comment> 649<comment>(Set some options for arcload)</comment>
635 650
636<comment>(Provide the location of the Volume Header)</comment> 651<comment>(Provide the location of the Volume Header)</comment>
637&gt;&gt; <i>setenv SystemPartition scsi(0)disk(1)rdisk(0)partition(8)</i> 652&gt;&gt; <i>setenv SystemPartition scsi(0)disk(1)rdisk(0)partition(8)</i>
638 653
639<comment>(Automatically boot Gentoo)</comment> 654<comment>(Automatically boot Gentoo)</comment>
643&gt;&gt; <i>setenv TimeZone EST5EDT</i> 658&gt;&gt; <i>setenv TimeZone EST5EDT</i>
644 659
645<comment>(Use the serial console - graphic adapter users should have "g" instead of "d1" (one))</comment> 660<comment>(Use the serial console - graphic adapter users should have "g" instead of "d1" (one))</comment>
646&gt;&gt; <i>setenv console d1</i> 661&gt;&gt; <i>setenv console d1</i>
647 662
648<comment>(Setting the serial console baud rate. This is optional, 9600 is the ) 663<comment>(Setting the serial console baud rate. This is optional, 9600 is the )
649(default setting, although one may use rates up to 38400 if that is desired. )</comment> 664(default setting, although one may use rates up to 38400 if that is desired. )</comment>
650&gt;&gt; <i>setenv dbaud 9600</i> 665&gt;&gt; <i>setenv dbaud 9600</i>
651</pre> 666</pre>
652 667
653<p> 668<p>
661<title>Settings for direct volume-header booting</title> 676<title>Settings for direct volume-header booting</title>
662<body> 677<body>
663 678
664<p> 679<p>
665This is covered here for completeness. It's recommended that users look into 680This is covered here for completeness. It's recommended that users look into
666installing <c>arcboot</c> or <c>arcload</c> instead. 681installing <c>arcload</c> instead.
667</p> 682</p>
668 683
669<note> 684<note>
670This only works on the Indy, Indigo2 (R4k) and Challenge S. 685This only works on the Indy, Indigo2 (R4k) and Challenge S.
671</note> 686</note>
723</pre> 738</pre>
724 739
725</body> 740</body>
726</subsection> 741</subsection>
727 742
743<!-- Slated for removal
728<subsection> 744<subsection>
729<title>Settings for arcboot</title> 745<title>Settings for arcboot</title>
730<body> 746<body>
731 747
732<p> 748<p>
736should point to the <c>arcboot</c> binary in the volume header, and 752should point to the <c>arcboot</c> binary in the volume header, and
737<c>OSLoadFilename</c> is the image name being used. 753<c>OSLoadFilename</c> is the image name being used.
738</p> 754</p>
739 755
740<pre caption="PROM settings for using arcboot"> 756<pre caption="PROM settings for using arcboot">
741<comment>(Read configuration and kernels from SCSI ID# 1, partition 0 -- sda1)</comment> 757<comment>(Read configuration and kernels from SCSI ID# 1, partition 0 - - sda1)</comment>
742&gt;&gt; <i>setenv OSLoadPartition scsi(0)disk(1)rdisk(0)partition(0)</i> 758&gt;&gt; <i>setenv OSLoadPartition scsi(0)disk(1)rdisk(0)partition(0)</i>
743 759
744<comment>(Use arcboot as the bootloader)</comment> 760<comment>(Use arcboot as the bootloader)</comment>
745&gt;&gt; <i>setenv OSLoader arcload</i> 761&gt;&gt; <i>setenv OSLoader arcboot</i>
746 762
747<comment>(Which boot image in arcboot.conf to load)</comment> 763<comment>(Which boot image in arcboot.conf to load)</comment>
748&gt;&gt; <i>setenv OSLoadFilename working</i> 764&gt;&gt; <i>setenv OSLoadFilename working</i>
749</pre> 765</pre>
750 766
756<pre caption="Specifying an alternate image"> 772<pre caption="Specifying an alternate image">
757# <i>boot new</i> 773# <i>boot new</i>
758</pre> 774</pre>
759 775
760</body> 776</body>
761</subsection> 777</subsection> -->
762 778
763<subsection> 779<subsection>
764<title>All Done</title> 780<title>All Done</title>
765<body> 781<body>
766 782

Legend:
Removed from v.1.15  
changed lines
  Added in v.1.16

  ViewVC Help
Powered by ViewVC 1.1.20