/[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.12 Revision 1.13
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/1.0 --> 5<!-- See http://creativecommons.org/licenses/by-sa/1.0 -->
6 6
7<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-mips-bootloader.xml,v 1.12 2006/01/19 21:48:10 neysx Exp $ --> 7<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-mips-bootloader.xml,v 1.13 2006/02/27 00:55:34 fox2mike Exp $ -->
8 8
9<sections> 9<sections>
10 10
11<version>1.8</version> 11<version>1.10</version>
12<date>2006-01-19</date> 12<date>2006-02-27</date>
13 13
14<section id="sgi"> 14<section id="sgi">
15<title>Silicon Graphics Machines -- Setting Up Arcboot</title> 15<title>Silicon Graphics Machines -- Setting Up arcboot/arcload</title>
16<subsection>
17<title>Which one?</title>
18<body>
19
20<p>
21On SGI machines, you have two options for bootloaders. <c>arcboot</c> and
22<c>arcload</c>. The table below lists the pros and cons for each bootloader.
23</p>
24
25<table>
26<tr>
27 <th> </th>
28 <th>arcboot</th>
29</tr>
30<tr>
31 <th>+</th>
32 <ti>
33 It can load off EXT2 and EXT3 partitions, so no need to store them in the
34 volume header
35 </ti>
36</tr>
37<tr>
38 <th>-</th>
39 <ti>
40 It doesn't work on Octane/Octane2, Origin 200/2000 or
41 Indigo2 Impact (R10000)
42 </ti>
43</tr>
44</table>
45
46<table>
47<tr>
48 <th> </th>
49 <th>arcload</th>
50</tr>
51<tr>
52 <th>+</th>
53 <ti>
54 It boots ALL Linux-compatable SGI systems
55 </ti>
56</tr>
57<tr>
58 <th>-</th>
59 <ti>
60 Currently, It cannot read EXT2/EXT3 partitions, and so needs the kernels
61 and config file to be placed in the volume header
62 </ti>
63</tr>
64</table>
65
66<note>
67The SGI volume header filenames are limited to 8 characters, and there may be no
68more than 16 files contained in a single volume header.
69</note>
70
71</body>
72</subsection>
73
16<subsection> 74<subsection>
17<title>Installing arcboot</title> 75<title>Installing arcboot</title>
18<body> 76<body>
19 77
20<p> 78<p>
43<p> 101<p>
44That should have installed two tools, <c>arcboot</c> which sits in the volume 102That should have installed two tools, <c>arcboot</c> which sits in the volume
45header and loads kernels for us, and <c>dvhtool</c> which helps us put 103header and loads kernels for us, and <c>dvhtool</c> which helps us put
46<c>arcboot</c> into the volume header. 104<c>arcboot</c> into the volume header.
47</p> 105</p>
48<p> 106
49The magic binary we want, hides in <path>/usr/lib/arcboot</path> -- on IP22
50systems (Indy, Indigo 2, Challenge S), it'll be called
51<path>arcboot.ip22</path>. Other systems should be similar. We
52first copy this file into the volume header.
53</p> 107<p>
108The <c>arcboot</c> binary lurks in <path>/usr/lib/arcboot</path>. The name of
109the binary depends on the machine it's compiled for.
110</p>
111
112<ul>
113 <li>
114 <c>arcboot.ip22</c>: The binary for Indy, Indigo2 (R4k) and Challenge S
115 systems
116 </li>
117 <li>
118 <c>arcboot.ip32</c>: The binary for O2 systems
119 </li>
120</ul>
54 121
55<pre caption="Installing arcboot into the volume header"> 122<pre caption="Installing arcboot into the volume header">
56# <i>dvhtool --unix-to-vh /usr/lib/arcboot/arcboot.ip?? arcboot</i> 123# <i>dvhtool --unix-to-vh /usr/lib/arcboot/arcboot.ip?? arcboot</i>
57</pre> 124</pre>
58 125
68Entry #3, name "arcboot", start 21260, bytes 51448 135Entry #3, name "arcboot", start 21260, bytes 51448
69# 136#
70</pre> 137</pre>
71 138
72<note> 139<note>
73You'll notice that in my case, I've got two old kernels sitting around there, 140You'll notice that in the example above, there are two old kernels sitting
74<path>linux</path> and <path>newlinux</path>. This is a hangover from before we 141around, <path>linux</path> and <path>newlinux</path>. This is a hangover from
75started using <c>arcboot</c>. Their presence doesn't matter -- just so long as 142before we started using <c>arcboot</c>. Their presence doesn't matter -- just
76<c>arcboot</c> is present, everything is fine. 143so long as <c>arcboot</c> is present, everything is fine.
77</note> 144</note>
78
79</body>
80</subsection>
81
82<subsection>
83<title>Configuring arcboot</title>
84
85<body>
86 145
87<p> 146<p>
88If you've ever set up the Linux Loader (<c>lilo</c>) before, you'll find that 147If you've ever set up the Linux Loader (<c>lilo</c>) before, you'll find that
89<c>arcboot</c> employs a similar syntax in its configuration file. Bear in mind 148<c>arcboot</c> employs a similar syntax in its configuration file. Bear in mind
90though; <c>arcboot</c> expects to find its configuration file existing on an 149though; <c>arcboot</c> expects to find its configuration file existing on an
91EXT2/3 partition as <path>/etc/arcboot.conf</path>. The easiest way around this 150EXT2/3 partition as <path>/etc/arcboot.conf</path>. The easiest way around this
92is to make sure <path>/boot</path> is an EXT2/3 partition and that there's a 151is to make sure <path>/boot</path> is an EXT2/3 partition and that there's a
93file called <path>arcboot.conf</path> inside the <path>/boot/etc</path> 152file called <path>arcboot.conf</path> inside the <path>/boot/etc</path>
94directory. An example config can be found in 153directory. An example config can be found in
95<path>/etc/arcboot.conf.sample</path> 154<path>/etc/arcboot.conf.sample</path>.
96</p> 155</p>
156
157<note>
158Adjust the paths accordingly if you
159don't have a separate <path>/boot</path> partition.
160</note>
97 161
98<pre caption="Putting arcboot.conf in its place"> 162<pre caption="Putting arcboot.conf in its place">
99<comment>(Create the /boot/etc directory)</comment> 163<comment>(Create the /boot/etc directory)</comment>
100# <i>mkdir /boot/etc</i> 164# <i>mkdir /boot/etc</i>
101 165
109# <i>(cd /boot; ln -s . boot)</i> 173# <i>(cd /boot; ln -s . boot)</i>
110</pre> 174</pre>
111 175
112<p> 176<p>
113You can then edit <path>/etc/arcboot.conf</path> to your own preference. 177You can then edit <path>/etc/arcboot.conf</path> to your own preference.
114Personally, I prefer to set up two kernel images: <path>new</path>, a freshly built 178One possible layout, is to set up two kernel images: <path>new</path>, a
115image that may or may not work; and <path>working</path>, a proven trustworthy 179freshly built image that may or may not work; and <path>working</path>, a
116kernel image. My <path>arcboot.conf</path> looks a bit like this. 180proven trustworthy kernel image. The <path>arcboot.conf</path> for that
181setup looks a bit like this.
117</p> 182</p>
118 183
119<pre caption="Example arcboot.conf"> 184<pre caption="Example arcboot.conf">
120<comment># arcboot.conf</comment> 185<comment># arcboot.conf</comment>
121<comment>#</comment> 186<comment>#</comment>
122<comment># copyright 2002 Guido Guenther &lt;agx@sigxcpu.org&gt;</comment> 187<comment># copyright 2002 Guido Guenther &lt;agx@sigxcpu.org&gt;</comment>
123<comment>#</comment> 188<comment>#</comment>
189<comment># known working version</comment>
124label=working 190label=working
125 image=/vmlinux 191 image=/vmlinux
126 append="root=/dev/sda3" 192 append="root=/dev/sda3"
127 193
128<comment># backup version</comment> 194<comment># fresh "untested" version</comment>
129label=new 195label=new
130 image=/vmlinux-new 196 image=/vmlinux-new
131 append="root=/dev/sda3" 197 append="root=/dev/sda3"
132</pre> 198</pre>
133 199
138<uri link="#reboot">Rebooting the System</uri>. 204<uri link="#reboot">Rebooting the System</uri>.
139</p> 205</p>
140 206
141</body> 207</body>
142</subsection> 208</subsection>
209
210<subsection>
211<title>Installing arcload</title>
212<body>
213
214<p>
215<c>arcload</c> was written for machines that require 64-bit kernels, and
216therefore can't use <c>arcboot</c> (which can't easily be compiled as a 64-bit
217binary). It also works around peculiarities that arise when loading kernels
218directly from the volume header. So, now you know what this is about, we
219can proceed with the installation:
220</p>
221
222<pre caption="Merging arcload and dvhtool">
223# <i>emerge arcload dvhtool</i>
224</pre>
225
226<p>
227Once this has finished, you should find the <c>arcload</c> binary in
228<path>/usr/lib/arcload</path>. Now, two files exist:
229</p>
230
231<ul>
232 <li>
233 <c>sashARCS</c>: The 32-bit binary for Indy, Indigo2 (R4k), Challenge S
234 and O2 systems
235 </li>
236 <li>
237 <c>sash64</c>: The 64-bit binary for Octane/Octane2, Origin 200/2000 and
238 Indigo2 Impact systems
239 </li>
240</ul>
241
242<p>
243Use <c>dvhtool</c> to install the appropriate binary for your system into the
244volume header:
245</p>
246
247<pre caption="Placing arcload in the volume header">
248<comment>(Indy/Indigo2/Challenge S/O2 users)</comment>
249# <i>dvhtool --unix-to-vh /usr/lib/arcload/sashARCS sashARCS</i>
250
251<comment>(Indigo2 Impact/Octane/Octane2/Origin 200/Origin 2000 users)</comment>
252# <i>dvhtool --unix-to-vh /usr/lib/arcload/sash64 sash64</i>
253</pre>
254
255<note>
256You don't have to use the name <c>sashARCS</c> or <c>sash64</c>, unless you are
257installing to the volume header of a bootable CD. For normal boot from
258hard-disk, you may name them something else if you wish.
259</note>
260
261<p>
262Now just use <c>dvhtool</c> to verify they are in the volume header.
263</p>
264
265<pre caption="Checking arcload is present in the volume header">
266# <i>dvhtool --print-volume-directory</i>
267----- directory entries -----
268Entry #0, name "sash64", start 4, bytes 55859
269#
270</pre>
271
272<p>
273Now, the <c>arc.cf</c> file has a C-like syntax. For the full detail on how
274one configures it, see the <uri
275link="http://www.linux-mips.org/wiki/Arcload">arcload page on the
276Linux/MIPS wiki</uri>. In short, you define a number of options, which you
277enable and disable at boot time using the <c>OSLoadFilename</c> variable.
278</p>
279
280<pre caption="An example arc.cf">
281<comment># ARCLoad Configuration</comment>
282
283<comment># Some default settings...</comment>
284append "root=/dev/sda3";
285append "ro";
286append "console=ttyS0,9600";
287
288<comment># Our main definition. ip28 may be changed if you wish.</comment>
289ip28 {
290 <comment># Definition for a "working" kernel</comment>
291 <comment># Select this by setting OSLoadFilename="ip28(working)"</comment>
292 working {
293 description "SGI Indigo2 Impact R10000\n\r";
294 image system "/working";
295 }
296
297 <comment># Definition for a "new" kernel</comment>
298 <comment># Select this by setting OSLoadFilename="ip28(new)"</comment>
299 new {
300 description "SGI Indigo2 Impact R10000 - Testing Kernel\n\r";
301 image system "/new";
302 }
303
304 <comment># For debugging a kernel</comment>
305 <comment># Select this by setting OSLoadFilename="ip28(working,debug)"</comment>
306 <comment># or OSLoadFilename="ip28(new,debug)"</comment>
307 debug {
308 description "Debug console";
309 append "init=/bin/bash";
310 }
311}
312</pre>
313
314<p>
315This 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.
317</p>
318
319<pre caption="Placing arc.cf and kernel in the volume header">
320# <i>dvhtool --unix-to-vh arc.cf arc.cf</i>
321# <i>dvhtool --unix-to-vh /usr/src/linux/vmlinux new</i>
322</pre>
323
324<p>
325With this done, now all that's left is to set some options in the PROM. See the
326section on <uri link="#reboot">Rebooting the System</uri>.
327</p>
328
329</body>
330</subsection>
331
143</section> 332</section>
144 333
145<section id="cobalt"> 334<section id="cobalt">
146<title>Cobalt MicroServers -- Setting Up CoLo</title> 335<title>Cobalt MicroServers -- Setting Up CoLo</title>
147<subsection> 336<subsection>
154number of serious limitations. 343number of serious limitations.
155</p> 344</p>
156 345
157<ul> 346<ul>
158 <li> 347 <li>
159 There's a 675kB limit on kernels. The current size of Linux 2.4 makes it 348 There's a 675kB (approximate) limit on kernels. The current size of Linux
160 damn near impossible to make a kernel this size. Linux 2.6 is totally out 349 2.4 makes it damn near impossible to make a kernel this size. Linux 2.6 is
161 of the question. 350 totally out of the question.
162 </li> 351 </li>
163 <li> 352 <li>
164 64-bit kernels are not supported by the stock firmware (although these are 353 64-bit kernels are not supported by the stock firmware (although these are
165 highly experimental on Cobalt machines at this time) 354 highly experimental on Cobalt machines at this time)
166 </li> 355 </li>
252scripts. 441scripts.
253</note> 442</note>
254 443
255<p> 444<p>
256It is also possible to ask a question, such as which kernel &amp; configuration 445It is also possible to ask a question, such as which kernel &amp; configuration
257you'd like to boot, with a default timeout. This is the configuration I use on 446you'd like to boot, with a default timeout. This configuration does exactly
258my Cobalt server: 447this, asks the user which kernel they wish to use, and executes the chosen
448image. <path>vmlinux.gz.new</path> and <path>vmlinux.gz.working</path> may be
449actual kernel images, or just symlinks pointing to the kernel images on that
450disk. The <c>50</c> argument to <c>select</c> specifies that it should proceed
451with the first option ("Working") after 50/10 seconds.
259</p> 452</p>
260
261<impo>
262Please note that you need to be using CoLo v1.12 or v1.13 to use the <c>menu</c>
263command. The following example won't work with v1.11.
264</impo>
265
266<impo>
267The <c>menu</c> command was replaced by the <c>select</c> command in CoLo v1.14.
268If you've installed a later version by hand, have a look at
269<path>menu.colo</path> in the <path>examples</path> subdirectory of the CoLo
270distribution.
271</impo>
272 453
273<pre caption="Menu-based configuration"> 454<pre caption="Menu-based configuration">
274<comment>#:CoLo:#</comment> 455<comment>#:CoLo:#</comment>
275 456
276lcd "Mounting hda1" 457lcd "Mounting hda1"
277mount hda1 458mount hda1
278menu "Which Kernel?" 50 Working working New new 459select "Which Kernel?" 50 Working New
279lcd "Loading Linux" {menu-option} 460
280load /kernel.gz.{menu-option} 461goto {menu-option}
462var image-name vmlinux.gz.working
463goto 3f
464@var image-name vmlinux.gz.working
465goto 2f
466@var image-name vmlinux.gz.new
467
468@lcd "Loading Linux" {image-name}
469load /{image-name}
281lcd "Booting..." 470lcd "Booting..."
282execute root=/dev/hda5 ro console=ttyS0,115200 471execute root=/dev/hda5 ro console=ttyS0,115200
283boot 472boot
284</pre> 473</pre>
285 474
286<p> 475<p>
287The above script asks the user which kernel he/she would like to boot (either 476See the documentation in <path>/usr/share/doc/colo-VERSION</path> for more
288New or Working), then loads <path>vmlinux.gz.new</path> or 477details.
289<path>vmlinux.gz.working</path> depending on the selection. If a selection is
290not made within 5 seconds (50/10ths of a second) it boots the first option.
291</p> 478</p>
479
292</body> 480</body>
293 481
294</subsection> 482</subsection>
295</section> 483</section>
296 484
305you're going to be logged in at a physical terminal. On Cobalt machines, this 493you're going to be logged in at a physical terminal. On Cobalt machines, this
306is particularly bad -- there's no such thing as a physical terminal. 494is particularly bad -- there's no such thing as a physical terminal.
307</p> 495</p>
308 496
309<note> 497<note>
310Those who do have the luxury of a supported framebuffer may skip this section if 498Those who do have the luxury of a supported video chipset may skip this section if
311they wish. 499they wish.
312</note> 500</note>
313 501
314<p> 502<p>
315First, pull up an editor and hack away at <path>/etc/inittab</path>. Further 503First, pull up an editor and hack away at <path>/etc/inittab</path>. Further
393cdimage ~# <i>reboot</i> 581cdimage ~# <i>reboot</i>
394</pre> 582</pre>
395 583
396<note> 584<note>
397<e>Cobalt Users:</e> The rest of this section covers the setting up of the SGI 585<e>Cobalt Users:</e> The rest of this section covers the setting up of the SGI
398PROM so that it boots <c>arcboot</c> off disk and loads Linux. This is not 586PROM so that it boots <c>arcboot</c>/<c>arcload</c> off disk and loads Linux.
399applicable to the setup of Cobalt servers. In fact, all your work is done -- 587This is not applicable to the setup of Cobalt servers. In fact, all your work
400there is no configuration needed for the first boot up, you can skip to the next 588is done -- there is no configuration needed for the first boot up, you can skip
401section: <uri link="?part=1&amp;chap=11">Finalising your Gentoo 589to the next section: <uri link="?part=1&amp;chap=11">Finalising your Gentoo
402Installation</uri> 590Installation</uri>
403</note> 591</note>
404 592
405</body> 593</body>
406</subsection> 594</subsection>
407</section> 595</section>
408<section> 596<section>
409<title>Tweaking the SGI PROM</title> 597<title>Tweaking the SGI PROM</title>
410<subsection> 598<subsection>
599<title>Setting generic PROM settings</title>
411<body> 600<body>
601
602<p>
603Now that you've installed the bootloader, you're ready to reboot the machine.
604</p>
605
606<pre caption="Rebooting">
607<comment>(Exit the chroot environment)</comment>
608# <i>exit</i>
609
610<comment>(Unmount the drives)</comment>
611# <i>umount /gentoo/boot</i>
612# <i>umount /gentoo</i>
613
614<comment>(Reboot)</comment>
615# <i>reboot</i>
616</pre>
412 617
413<p> 618<p>
414When you are rebooted, go to the <e>System Maintenance Menu</e> and select 619When you are rebooted, go to the <e>System Maintenance Menu</e> and select
415<e>Enter Command Monitor</e> (<c>5</c>). If you want to test your new Gentoo 620<e>Enter Command Monitor</e> (<c>5</c>) like you did when you netbooted the
416installation, you can just run <c>boot -f &lt;kernel name&gt;</c>. To have your 621machine.
417system permanently boot into the Gentoo installation, you need to set some
418variables in the SGI PROM:
419</p> 622</p>
420 623
421<pre caption="Configuring the PROM to Boot Gentoo"> 624<pre caption="Configuring the PROM to Boot Gentoo">
4221) Start System 6251) Start System
4232) Install System Software 6262) Install System Software
4265) Enter Command Monitor 6295) Enter Command Monitor
427 630
428Option? <i>5</i> 631Option? <i>5</i>
429Command Monitor. Type "exit" to return to the menu. 632Command Monitor. Type "exit" to return to the menu.
430 633
634<comment>(Set some options which are common for both arcload and arcboot)</comment>
635
636<comment>(Provide the location of the Volume Header)</comment>
637&gt;&gt; <i>setenv SystemPartition scsi(0)disk(1)rdisk(0)partition(8)</i>
638
639<comment>(Automatically boot Gentoo)</comment>
640&gt;&gt; <i>setenv AutoLoad Yes</i>
641
642<comment>(Set the timezone)</comment>
643&gt;&gt; <i>setenv TimeZone EST5EDT</i>
644
645<comment>(Use the serial console - graphic adapter users should have "g" instead of "d1" (one))</comment>
646&gt;&gt; <i>setenv console d1</i>
647
648<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>
650&gt;&gt; <i>setenv dbaud 9600</i>
651</pre>
652
653<p>
654Now, the next settings depend on how you are booting the system.
655</p>
656
657</body>
658</subsection>
659
660<subsection>
661<title>Settings for direct volume-header booting</title>
662<body>
663
664<p>
665This is covered here for completeness. It's recommended that users look into
666installing <c>arcboot</c> or <c>arcload</c> instead.
667</p>
668
669<note>
670This only works on the Indy, Indigo2 (R4k) and Challenge S.
671</note>
672
673<pre caption="PROM settings for booting off the volume header">
431<comment>(&lt;root device&gt; = Gentoo's root partition, e.g. /dev/sda3)</comment> 674<comment>(&lt;root device&gt; = Gentoo's root partition, e.g. /dev/sda3)</comment>
432&gt;&gt; <i>setenv OSLoadPartition &lt;root device&gt;</i> 675&gt;&gt; <i>setenv OSLoadPartition &lt;root device&gt;</i>
433 676
434<comment>(To list the available kernels, type "ls")</comment> 677<comment>(To list the available kernels, type "ls")</comment>
435&gt;&gt; <i>setenv OSLoader &lt;kernel name&gt;</i> 678&gt;&gt; <i>setenv OSLoader &lt;kernel name&gt;</i>
436&gt;&gt; <i>setenv OSLoadFilename &lt;kernel name&gt;</i> 679&gt;&gt; <i>setenv OSLoadFilename &lt;kernel name&gt;</i>
437 680
438<comment>(Declare the kernel parameters you want to pass)</comment> 681<comment>(Declare the kernel parameters you want to pass)</comment>
439&gt;&gt; <i>setenv OSLoadOptions &lt;kernel parameters&gt;</i> 682&gt;&gt; <i>setenv OSLoadOptions &lt;kernel parameters&gt;</i>
683</pre>
440 684
441<comment>(Provide the location of the Volume Header)</comment> 685<p>
686If you wish to try a kernel without messing with kernel parameters, you may do
687so using the <c>boot -f</c> PROM command:
688</p>
689
690<pre caption="Booting without changing environment variables">
691<comment>(Booting a kernel, "new", with additional options)</comment>
692# <i>boot -f new root=/dev/sda3 ro</i>
693</pre>
694
695</body>
696</subsection>
697
698<subsection>
699<title>Settings for arcload</title>
700<body>
701
702<p>
703<c>arcload</c> uses the <c>OSLoadFilename</c> option to specify which options to
704set from <path>arc.cf</path>. The configuration file is essentially a script,
705with the top-level blocks defining boot images for different systems, and inside
706that, optional settings. Thus, setting <c>OSLoadFilename=mysys(serial)</c>
707pulls in the settings for the <c>mysys</c> block, then sets further options
708overridden in <c>serial</c>.
709</p>
710
711<p>
712In the example file above, we have one system block defined, <c>ip28</c> with
713<c>working</c>, <c>new</c> and <c>debug</c> options available. We define our
714PROM variables as so:
715</p>
716
717<pre caption="PROM settings for using arcload">
718<comment>(Select arcload as the bootloader:- sash64 or sashARCS)</comment>
719&gt;&gt; setenv OSLoader sash64
720
721<comment>(Use the "working" kernel image, defined in "ip28" section of arc.cf)</comment>
722&gt;&gt; setenv OSLoadFilename ip28(working)
723</pre>
724
725</body>
726</subsection>
727
728<subsection>
729<title>Settings for arcboot</title>
730<body>
731
732<p>
733<c>arcboot</c> loads its configuration file and kernels from your
734<path>/boot</path> partition, which needs to be formatted either EXT2 or EXT3.
735Thus <c>OSLoadPartition</c> needs to point to that partition. <c>OSLoader</c>
736should point to the <c>arcboot</c> binary in the volume header, and
737<c>OSLoadFilename</c> is the image name being used.
738</p>
739
740<pre caption="PROM settings for using arcboot">
741<comment>(Read configuration and kernels from SCSI ID# 1, partition 0 -- sda1)</comment>
442&gt;&gt; <i>setenv SystemPartition scsi(0)disk(1)rdisk(0)partition(8)</i> 742&gt;&gt; <i>setenv OSLoadPartition scsi(0)disk(1)rdisk(0)partition(0)</i>
443 743
444<comment>(Automatically boot Gentoo)</comment> 744<comment>(Use arcboot as the bootloader)</comment>
445&gt;&gt; <i>setenv AutoLoad Yes</i> 745&gt;&gt; <i>setenv OSLoader arcload</i>
446 746
447<comment>(Set the timezone)</comment> 747<comment>(Which boot image in arcboot.conf to load)</comment>
448&gt;&gt; <i>setenv TimeZone EST5EDT</i> 748&gt;&gt; <i>setenv OSLoadFilename working</i>
749</pre>
449 750
450<comment>(Use the serial console - graphic adapter users should have "g" instead of "d1" (one))</comment> 751<p>
451&gt;&gt; <i>setenv console d1</i> 752When testing kernels via <c>arcboot</c> you can specify an alternate image like
753so (where <c>new</c> is the alternate image):
452</pre> 754</p>
755
756<pre caption="Specifying an alternate image">
757# <i>boot new</i>
758</pre>
759
760</body>
761</subsection>
762
763<subsection>
764<title>All Done</title>
765<body>
453 766
454<p> 767<p>
455Now you're ready to enjoy Gentoo! Boot in your Gentoo installation and finish 768Now you're ready to enjoy Gentoo! Boot in your Gentoo installation and finish
456up with <uri link="?part=1&amp;chap=11">Finalizing your Gentoo 769up with <uri link="?part=1&amp;chap=11">Finalizing your Gentoo
457Installation</uri>. 770Installation</uri>.

Legend:
Removed from v.1.12  
changed lines
  Added in v.1.13

  ViewVC Help
Powered by ViewVC 1.1.20