[gentoo-doc-cvs] cvs commit: handbook-mips.xml

[Josh Saddler]

nightmorph    06/02/12 14:31:58

  Modified:    xml/htdocs/doc/en/handbook/draft/2006.0 handbook-mips.xml
                        hb-install-mips-bootloader.xml
                        hb-install-mips-disk.xml hb-install-mips-kernel.xml
                        hb-install-mips-medium.xml index.xml
  Log:
  Added patches to the mips stuff as per bug 111652 to bring everything up
  to date. Also edited index.xml to reflect the now present mips
  handbook.

Revision  Changes    Path
1.2       +6 -6      xml/htdocs/doc/en/handbook/draft/2006.0/handbook-mips.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/handbook-mips.xml?rev=1.2&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/handbook-mips.xml?rev=1.2&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/handbook-mips.xml.diff?r1=1.1&r2=1.2&cvsroot=gentoo

Index: handbook-mips.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/handbook-mips.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- handbook-mips.xml	12 Feb 2006 13:54:32 -0000	1.1
+++ handbook-mips.xml	12 Feb 2006 14:31:58 -0000	1.2
@@ -1,7 +1,7 @@
 <?xml version='1.0' encoding='UTF-8'?>
 <!DOCTYPE book SYSTEM "/dtd/book.dtd">
 
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/handbook-mips.xml,v 1.1 2006/02/12 13:54:32 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/handbook-mips.xml,v 1.2 2006/02/12 14:31:58 nightmorph Exp $ -->
 
 <book link="handbook-mips.xml">
 <title>Gentoo Linux/MIPS Handbook</title>
@@ -90,7 +90,7 @@
   <mail link="kumba@g.o">Joshua Kinard</mail>
 </author>
 <author title="Editor">
-  <mail link="stuartl@××××××××××××××××××.org">Stuart Longland</mail>
+  <mail link="redhatter@g.o">Stuart Longland</mail>
 </author>
 <author title="Editor">
   <mail link="dertobi123@g.o">Tobias Scherbaum</mail>
@@ -124,8 +124,8 @@
 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
 <license/>
 
-<version>4.3</version>
-<date>2005-12-19</date>
+<version>4.4</version>
+<date>2006-01-01</date>
 
 <part>
 <title>Installing Gentoo</title>
@@ -175,7 +175,7 @@
 Gentoo installs work through a stage3 archive. In this chapter we
 describe how you extract the stage3 archive and configure Portage.
 </abstract>
-  <include href="hb-install-stage.xml"/>
+  <include href="hb-install-mips-stage.xml"/>
 </chapter>
 
 <chapter>
@@ -221,7 +221,7 @@
 <abstract>
 On both Silicon Graphics machines, and on Cobalt servers, both require the use
 of a bootloader to load the kernel.  This section covers setting up
-arcboot (for SGI machines) and colo for Cobalt servers.
+arcboot/arcload (for SGI machines) and colo for Cobalt servers.
 </abstract>
   <include href="hb-install-mips-bootloader.xml"/>
 </chapter>



1.2       +379 -66   xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-mips-bootloader.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-mips-bootloader.xml?rev=1.2&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-mips-bootloader.xml?rev=1.2&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-mips-bootloader.xml.diff?r1=1.1&r2=1.2&cvsroot=gentoo

Index: hb-install-mips-bootloader.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-mips-bootloader.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- hb-install-mips-bootloader.xml	12 Feb 2006 13:54:32 -0000	1.1
+++ hb-install-mips-bootloader.xml	12 Feb 2006 14:31:58 -0000	1.2
@@ -4,15 +4,73 @@
 <!-- The content of this document is licensed under the CC-BY-SA license -->
 <!-- See http://creativecommons.org/licenses/by-sa/1.0 -->
 
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-mips-bootloader.xml,v 1.1 2006/02/12 13:54:32 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-mips-bootloader.xml,v 1.2 2006/02/12 14:31:58 nightmorph Exp $ -->
 
 <sections>
 
-<version>1.8</version>
-<date>2006-01-19</date>
+<version>1.9</version>
+<date>2006-02-12</date>
 
 <section id="sgi">
-<title>Silicon Graphics Machines -- Setting Up Arcboot</title>
+<title>Silicon Graphics Machines -- Setting Up arcboot/arcload</title>
+<subsection>
+<title>Which one?</title>
+<body>
+
+<p>
+On SGI machines, you have two options for bootloaders.  <c>arcboot</c> and
+<c>arcload</c>.  The table below lists the pros and cons for each bootloader.
+</p>
+
+<table>
+<tr>
+  <th> </th>
+  <th>arcboot</th>
+</tr>
+<tr>
+  <th>+</th>
+  <ti>
+    It can load off EXT2 and EXT3 partitions, so no need to store them in the
+    volume header
+  </ti>
+</tr>
+<tr>
+  <th>-</th>
+  <ti>
+    It doesn't work on Octane/Octane2, Origin 200/2000 or
+    Indigo2 Impact (R10000)
+  </ti>
+</tr>
+</table>
+
+<table>
+<tr>
+  <th> </th>
+  <th>arcload</th>
+</tr>
+<tr>
+  <th>+</th>
+  <ti>
+    It boots ALL Linux-compatable SGI systems
+  </ti>
+</tr>
+<tr>
+  <th>-</th>
+  <ti>
+    Currently, It cannot read EXT2/EXT3 partitions, and so needs the kernels
+    and config file to be placed in the volume header
+  </ti>
+</tr>
+</table>
+
+<note>
+The SGI volume header filenames are limited to 8 characters, and there may be no
+more than 16 files contained in a single volume header.
+</note>
+
+</body>
+</subsection>
+
 <subsection>
 <title>Installing arcboot</title>
 <body>
@@ -45,13 +103,22 @@
 header and loads kernels for us, and <c>dvhtool</c> which helps us put
 <c>arcboot</c> into the volume header.
 </p>
+
 <p>
-The magic binary we want, hides in <path>/usr/lib/arcboot</path> -- on IP22
-systems (Indy, Indigo 2, Challenge S), it'll be called
-<path>arcboot.ip22</path>.  Other systems should be similar.  We
-first copy this file into the volume header.
+The <c>arcboot</c> binary lurks in <path>/usr/lib/arcboot</path>.  The name of
+the binary depends on the machine it's compiled for.
 </p>
 
+<ul>
+  <li>
+    <c>arcboot.ip22</c>: The binary for Indy, Indigo2 (R4k) and Challenge S
+    systems
+  </li>
+  <li>
+    <c>arcboot.ip32</c>: The binary for O2 systems
+  </li>
+</ul>
+
 <pre caption="Installing arcboot into the volume header">
 # <i>dvhtool --unix-to-vh /usr/lib/arcboot/arcboot.ip?? arcboot</i>
 </pre>
@@ -70,20 +137,12 @@
 </pre>
 
 <note>
-You'll notice that in my case, I've got two old kernels sitting around there,
-<path>linux</path> and <path>newlinux</path>.  This is a hangover from before we
-started using <c>arcboot</c>.  Their presence doesn't matter -- just so long as
-<c>arcboot</c> is present, everything is fine.
+You'll notice that in the example above, there are two old kernels sitting
+around, <path>linux</path> and <path>newlinux</path>.  This is a hangover from
+before we started using <c>arcboot</c>.  Their presence doesn't matter -- just
+so long as <c>arcboot</c> is present, everything is fine.
 </note>
 
-</body>
-</subsection>
-
-<subsection>
-<title>Configuring arcboot</title>
-
-<body>
-
 <p>
 If you've ever set up the Linux Loader (<c>lilo</c>) before, you'll find that
 <c>arcboot</c> employs a similar syntax in its configuration file.  Bear in mind
@@ -92,9 +151,14 @@
 is to make sure <path>/boot</path> is an EXT2/3 partition and that there's a
 file called <path>arcboot.conf</path> inside the <path>/boot/etc</path>
 directory.  An example config can be found in
-<path>/etc/arcboot.conf.sample</path>
+<path>/etc/arcboot.conf.sample</path>.
 </p>
 
+<note>
+Adjust the paths accordingly if you
+don't have a separate <path>/boot</path> partition.
+</note>
+
 <pre caption="Putting arcboot.conf in its place">
 <comment>(Create the /boot/etc directory)</comment>
 # <i>mkdir /boot/etc</i>
@@ -111,9 +175,10 @@
 
 <p>
 You can then edit <path>/etc/arcboot.conf</path> to your own preference.
-Personally, I prefer to set up two kernel images: <path>new</path>, a freshly built
-image that may or may not work; and <path>working</path>, a proven trustworthy 
-kernel image.  My <path>arcboot.conf</path> looks a bit like this.
+One possible layout, is to set up two kernel images: <path>new</path>, a
+freshly built image that may or may not work; and <path>working</path>, a
+proven trustworthy kernel image.  The <path>arcboot.conf</path> for that
+setup looks a bit like this.
 </p>
 
 <pre caption="Example arcboot.conf">
@@ -121,11 +186,12 @@
 <comment>#</comment>
 <comment># copyright 2002 Guido Guenther &lt;agx@×××××××.org&gt;</comment>
 <comment>#</comment>
+<comment># known working version</comment>
 label=working
         image=/vmlinux
         append="root=/dev/sda3"
 
-<comment># backup version</comment>
+<comment># fresh "untested" version</comment>
 label=new
         image=/vmlinux-new
         append="root=/dev/sda3"
@@ -140,6 +206,129 @@
 
 </body>
 </subsection>
+
+<subsection>
+<title>Installing arcload</title>
+<body>
+
+<p>
+<c>arcload</c> was written for machines that require 64-bit kernels, and
+therefore can't use <c>arcboot</c> (which can't easily be compiled as a 64-bit
+binary).  It also works around peculiarities that arise when loading kernels
+directly from the volume header.  So, now you know what this is about, we
+can proceed with the installation:
+</p>
+
+<pre caption="Merging arcload and dvhtool">
+# <i>emerge arcload dvhtool</i>
+</pre>
+
+<p>
+Once this has finished, you should find the <c>arcload</c> binary in
+<path>/usr/lib/arcload</path>.  Now, two files exist:
+</p>
+
+<ul>
+  <li>
+    <c>sashARCS</c>: The 32-bit binary for Indy, Indigo2 (R4k), Challenge S
+    and O2 systems
+  </li>
+  <li>
+    <c>sash64</c>: The 64-bit binary for Octane/Octane2, Origin 200/2000 and
+    Indigo2 Impact systems
+  </li>
+</ul>
+
+<p>
+Use <c>dvhtool</c> to install the appropriate binary for your system into the
+volume header:
+</p>
+
+<pre caption="Placing arcload in the volume header">
+<comment>(Indy/Indigo2/Challenge S/O2 users)</comment>
+# <i>dvhtool --unix-to-vh /usr/lib/arcload/sashARCS sashARCS</i>
+
+<comment>(Indigo2 Impact/Octane/Octane2/Origin 200/Origin 2000 users)</comment>
+# <i>dvhtool --unix-to-vh /usr/lib/arcload/sash64 sash64</i>
+</pre>
+
+<note>
+You don't have to use the name <c>sashARCS</c> or <c>sash64</c>, unless you are
+installing to the volume header of a bootable CD.  For normal boot from
+hard-disk, you may name them something else if you wish.
+</note>
+
+<p>
+Now just use <c>dvhtool</c> to verify they are in the volume header.
+</p>
+
+<pre caption="Checking arcload is present in the volume header">
+# <i>dvhtool --print-volume-directory</i>
+----- directory entries -----
+Entry #0, name "sash64", start 4, bytes 55859
+#
+</pre>
+
+<p>
+Now, the <c>arc.cf</c> file has a C-like syntax.  For the full detail on how
+one configures it, see the <uri
+link="http://www.linux-mips.org/wiki/Arcload">arcload page on the
+Linux/MIPS wiki</uri>.  In short, you define a number of options, which you
+enable and disable at boot time using the <c>OSLoadFilename</c> variable.
+</p>
+
+<pre caption="An example arc.cf">
+<comment># ARCLoad Configuration</comment>
+
+<comment># Some default settings...</comment>
+append  "root=/dev/sda3";
+append  "ro";
+append  "console=ttyS0,9600";
+
+<comment># Our main definition.  ip28 may be changed if you wish.</comment>
+ip28 {
+        <comment># Definition for a "working" kernel</comment>
+        <comment># Select this by setting OSLoadFilename="ip28(working)"</comment>
+        working {
+                description     "SGI Indigo2 Impact R10000\n\r";
+                image system    "/working";
+        }
+
+        <comment># Definition for a "new" kernel</comment>
+        <comment># Select this by setting OSLoadFilename="ip28(new)"</comment>
+        new {
+                description     "SGI Indigo2 Impact R10000 - Testing Kernel\n\r";
+                image system    "/new";
+        }
+
+        <comment># For debugging a kernel</comment>
+        <comment># Select this by setting OSLoadFilename="ip28(working,debug)"</comment>
+        <comment># or OSLoadFilename="ip28(new,debug)"</comment>
+        debug {
+                description     "Debug console";
+                append          "init=/bin/bash";
+        }
+}
+</pre>
+
+<p>
+This is then placed in the volume header with <c>sash64</c> (or
+<c>sashARCS</c>) as shown below.  Kernels also get placed in the volume header.
+</p>
+
+<pre caption="Placing arc.cf and kernel in the volume header">
+# <i>dvhtool --unix-to-vh arc.cf arc.cf</i>
+# <i>dvhtool --unix-to-vh /usr/src/linux/vmlinux new</i>
+</pre>
+
+<p>
+With this done, now all that's left is to set some options in the PROM.  See the
+section on <uri link="#reboot">Rebooting the System</uri>.
+</p>
+
+</body>
+</subsection>
+
 </section>
 
 <section id="cobalt">
@@ -156,9 +345,9 @@
 
 <ul>
   <li>
-    There's a 675kB limit on kernels.  The current size of Linux 2.4 makes it
-    damn near impossible to make a kernel this size.  Linux 2.6 is totally out
-    of the question.
+    There's a 675kB (approximate) limit on kernels.  The current size of Linux
+    2.4 makes it damn near impossible to make a kernel this size.  Linux 2.6 is
+    totally out of the question.
   </li>
   <li>
     64-bit kernels are not supported by the stock firmware (although these are
@@ -254,41 +443,40 @@
 
 <p>
 It is also possible to ask a question, such as which kernel &amp; configuration
-you'd like to boot, with a default timeout.  This is the configuration I use on
-my Cobalt server:
+you'd like to boot, with a default timeout.  This configuration does exactly
+this, asks the user which kernel they wish to use, and executes the chosen
+image.  <path>vmlinux.gz.new</path> and <path>vmlinux.gz.working</path> may be
+actual kernel images, or just symlinks pointing to the kernel images on that
+disk.  The <c>50</c> argument to <c>select</c> specifies that it should proceed
+with the first option ("Working") after 50/10 seconds.
 </p>
 
-<impo>
-Please note that you need to be using CoLo v1.12 or v1.13 to use the <c>menu</c>
-command. The following example won't work with v1.11.
-</impo>
-
-<impo>
-The <c>menu</c> command was replaced by the <c>select</c> command in CoLo v1.14.
-If you've installed a later version by hand, have a look at
-<path>menu.colo</path> in the <path>examples</path> subdirectory of the CoLo
-distribution.
-</impo>
-
 <pre caption="Menu-based configuration">
 <comment>#:CoLo:#</comment>
 
 lcd "Mounting hda1"
 mount hda1
-menu "Which Kernel?" 50 Working working New new
-lcd "Loading Linux" {menu-option}
-load /kernel.gz.{menu-option}
+select "Which Kernel?" 50 Working New
+
+goto {menu-option}
+var image-name vmlinux.gz.working
+goto 3f
+@var image-name vmlinux.gz.working
+goto 2f
+@var image-name vmlinux.gz.new
+
+@lcd "Loading Linux" {image-name}
+load /{image-name}
 lcd "Booting..."
 execute root=/dev/hda5 ro console=ttyS0,115200
 boot
 </pre>
 
 <p>
-The above script asks the user which kernel he/she would like to boot (either
-New or Working), then loads <path>vmlinux.gz.new</path> or
-<path>vmlinux.gz.working</path> depending on the selection.  If a selection is
-not made within 5 seconds (50/10ths of a second) it boots the first option.
+See the documentation in <path>/usr/share/doc/colo-VERSION</path> for more
+details.
 </p>
+
 </body>
 
 </subsection>
@@ -307,7 +495,7 @@
 </p>
 
 <note>
-Those who do have the luxury of a supported framebuffer may skip this section if
+Those who do have the luxury of a supported video chipset may skip this section if
 they wish.
 </note>
 
@@ -395,10 +583,10 @@
 
 <note>
 <e>Cobalt Users:</e> The rest of this section covers the setting up of the SGI
-PROM so that it boots <c>arcboot</c> off disk and loads Linux.  This is not
-applicable to the setup of Cobalt servers.  In fact, all your work is done --
-there is no configuration needed for the first boot up, you can skip to the next
-section: <uri link="?part=1&amp;chap=11">Finalising your Gentoo
+PROM so that it boots <c>arcboot</c>/<c>arcload</c> off disk and loads Linux.
+This is not applicable to the setup of Cobalt servers.  In fact, all your work
+is done -- there is no configuration needed for the first boot up, you can skip
+to the next section: <uri link="?part=1&amp;chap=11">Finalising your Gentoo
 Installation</uri>
 </note>
 
@@ -408,14 +596,29 @@
 <section>
 <title>Tweaking the SGI PROM</title>
 <subsection>
+<title>Setting generic PROM settings</title>
 <body>
 
 <p>
+Now that you've installed the bootloader, you're ready to reboot the machine.
+</p>
+
+<pre caption="Rebooting">
+<comment>(Exit the chroot environment)</comment>
+# <i>exit</i>
+
+<comment>(Unmount the drives)</comment>
+# <i>umount /gentoo/boot</i>
+# <i>umount /gentoo</i>
+
+<comment>(Reboot)</comment>
+# <i>reboot</i>
+</pre>
+
+<p>
 When you are rebooted, go to the <e>System Maintenance Menu</e> and select 
-<e>Enter Command Monitor</e> (<c>5</c>). If you want to test your new Gentoo 
-installation, you can just run <c>boot -f &lt;kernel name&gt;</c>. To have your 
-system permanently boot into the Gentoo installation, you need to set some 
-variables in the SGI PROM: 
+<e>Enter Command Monitor</e> (<c>5</c>) like you did when you netbooted the
+machine.
 </p>
 
 <pre caption="Configuring the PROM to Boot Gentoo">
@@ -428,6 +631,46 @@
 Option? <i>5</i>
 Command Monitor.  Type "exit" to return to the menu.
 
+<comment>(Set some options which are common for both arcload and arcboot)</comment>
+
+<comment>(Provide the location of the Volume Header)</comment>
+&gt;&gt; <i>setenv SystemPartition scsi(0)disk(1)rdisk(0)partition(8)</i>
+
+<comment>(Automatically boot Gentoo)</comment>
+&gt;&gt; <i>setenv AutoLoad Yes</i>
+
+<comment>(Set the timezone)</comment>
+&gt;&gt; <i>setenv TimeZone EST5EDT</i>
+
+<comment>(Use the serial console - graphic adapter users should have "g" instead of "d1" (one))</comment>
+&gt;&gt; <i>setenv console d1</i>
+
+<comment>(Setting the serial console baud rate.  This is optional, 9600 is the           )
+(default setting, although one may use rates up to 38400 if that is desired.   )</comment>
+&gt;&gt; <i>setenv dbaud 9600</i>
+</pre>
+
+<p>
+Now, the next settings depend on how you are booting the system.
+</p>
+
+</body>
+</subsection>
+
+<subsection>
+<title>Settings for direct volume-header booting</title>
+<body>
+
+<p>
+This is covered here for completeness.  It's recommended that users look into
+installing <c>arcboot</c> or <c>arcload</c> instead.
+</p>
+
+<note>
+This only works on the Indy, Indigo2 (R4k) and Challenge S.
+</note>
+
+<pre caption="PROM settings for booting off the volume header">
 <comment>(&lt;root device&gt; = Gentoo's root partition, e.g. /dev/sda3)</comment>
 &gt;&gt; <i>setenv OSLoadPartition &lt;root device&gt;</i>
 
@@ -437,21 +680,91 @@
 
 <comment>(Declare the kernel parameters you want to pass)</comment>
 &gt;&gt; <i>setenv OSLoadOptions &lt;kernel parameters&gt;</i>
+</pre>
 
-<comment>(Provide the location of the Volume Header)</comment>
-&gt;&gt; <i>setenv SystemPartition scsi(0)disk(1)rdisk(0)partition(8)</i>
+<p>
+If you wish to try a kernel without messing with kernel parameters, you may do
+so using the <c>boot -f</c> PROM command:
+</p>
 
-<comment>(Automatically boot Gentoo)</comment>
-&gt;&gt; <i>setenv AutoLoad Yes</i>
+<pre caption="Booting without changing environment variables">
+<comment>(Booting a kernel, "new", with additional options)</comment>
+# <i>boot -f new root=/dev/sda3 ro</i>
+</pre>
 
-<comment>(Set the timezone)</comment>
-&gt;&gt; <i>setenv TimeZone EST5EDT</i>
+</body>
+</subsection>
 
-<comment>(Use the serial console - graphic adapter users should have "g" instead of "d1" (one))</comment>
-&gt;&gt; <i>setenv console d1</i>
+<subsection>
+<title>Settings for arcload</title>
+<body>
+
+<p>
+<c>arcload</c> uses the <c>OSLoadFilename</c> option to specify which options to
+set from <path>arc.cf</path>.  The configuration file is essentially a script,
+with the top-level blocks defining boot images for different systems, and inside
+that, optional settings.  Thus, setting <c>OSLoadFilename=mysys(serial)</c>
+pulls in the settings for the <c>mysys</c> block, then sets further options
+overridden in <c>serial</c>.
+</p>
+
+<p>
+In the example file above, we have one system block defined, <c>ip28</c> with
+<c>working</c>, <c>new</c> and <c>debug</c> options available.  We define our
+PROM variables as so:
+</p>
+
+<pre caption="PROM settings for using arcload">
+<comment>(Select arcload as the bootloader:- sash64 or sashARCS)</comment>
+&gt;&gt; setenv OSLoader sash64
+
+<comment>(Use the "working" kernel image, defined in "ip28" section of arc.cf)</comment>
+&gt;&gt; setenv OSLoadFilename ip28(working)
+</pre>
+
+</body>
+</subsection>
+
+<subsection>
+<title>Settings for arcboot</title>
+<body>
+
+<p>
+<c>arcboot</c> loads its configuration file and kernels from your
+<path>/boot</path> partition, which needs to be formatted either EXT2 or EXT3.
+Thus <c>OSLoadPartition</c> needs to point to that partition.  <c>OSLoader</c>
+should point to the <c>arcboot</c> binary in the volume header, and
+<c>OSLoadFilename</c> is the image name being used.
+</p>
+
+<pre caption="PROM settings for using arcboot">
+<comment>(Read configuration and kernels from SCSI ID# 1, partition 0 -- sda1)</comment>
+&gt;&gt; <i>setenv OSLoadPartition scsi(0)disk(1)rdisk(0)partition(0)</i>
+
+<comment>(Use arcboot as the bootloader)</comment>
+&gt;&gt; <i>setenv OSLoader arcload</i>
+
+<comment>(Which boot image in arcboot.conf to load)</comment>
+&gt;&gt; <i>setenv OSLoadFilename working</i>
 </pre>
 
 <p>
+When testing kernels via <c>arcboot</c> you can specify an alternate image like
+so (where <c>new</c> is the alternate image):
+</p>
+
+<pre caption="Specifying an alternate image">
+# <i>boot new</i>
+</pre>
+
+</body>
+</subsection>
+
+<subsection>
+<title>All Done</title>
+<body>
+
+<p>
 Now you're ready to enjoy Gentoo! Boot in your Gentoo installation and finish 
 up with <uri link="?part=1&amp;chap=11">Finalizing your Gentoo 
 Installation</uri>.



1.2       +12 -3     xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-mips-disk.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-mips-disk.xml?rev=1.2&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-mips-disk.xml?rev=1.2&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-mips-disk.xml.diff?r1=1.1&r2=1.2&cvsroot=gentoo

Index: hb-install-mips-disk.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-mips-disk.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- hb-install-mips-disk.xml	12 Feb 2006 13:54:32 -0000	1.1
+++ hb-install-mips-disk.xml	12 Feb 2006 14:31:58 -0000	1.2
@@ -4,12 +4,12 @@
 <!-- The content of this document is licensed under the CC-BY-SA license -->
 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
 
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-mips-disk.xml,v 1.1 2006/02/12 13:54:32 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-mips-disk.xml,v 1.2 2006/02/12 14:31:58 nightmorph Exp $ -->
 
 <sections>
 
-<version>1.11</version>
-<date>2005-10-02</date>
+<version>1.12</version>
+<date>2006-02-12</date>
 
 <section>
 <title>Introduction to Block Devices</title>
@@ -223,6 +223,15 @@
 with each image allowed eight-character names.
 </p>
 
+<note>
+On SGI systems, there are two bootloaders available: <c>arcboot</c> and
+<c>arcload</c>.  Currently, only the Indy, Indigo2 (R4k variety), Challenge S
+and O2 are capable of using <c>arcboot</c> as a bootloader, whereas
+<c>arcload</c> runs on all the Linux-supported SGI machines.  Unlike
+<c>arcboot</c> however, <c>arcload</c> cannot presently read EXT2/3 partitions,
+and thus, loads its kernels from the volume header.
+</note>
+
 <p>
 The process of making the volume header larger isn't exactly straight-forward;
 there's a bit of a trick to it. One cannot simply delete and re-add the volume



1.2       +215 -73   xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-mips-kernel.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-mips-kernel.xml?rev=1.2&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-mips-kernel.xml?rev=1.2&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-mips-kernel.xml.diff?r1=1.1&r2=1.2&cvsroot=gentoo

Index: hb-install-mips-kernel.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-mips-kernel.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- hb-install-mips-kernel.xml	12 Feb 2006 13:54:32 -0000	1.1
+++ hb-install-mips-kernel.xml	12 Feb 2006 14:31:58 -0000	1.2
@@ -4,12 +4,12 @@
 <!-- The content of this document is licensed under the CC-BY-SA license -->
 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
 
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-mips-kernel.xml,v 1.1 2006/02/12 13:54:32 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-mips-kernel.xml,v 1.2 2006/02/12 14:31:58 nightmorph Exp $ -->
 
 <sections>
 
 <version>1.15</version>
-<date>2006-01-06</date>
+<date>2006-02-12</date>
 
 <section>
 <title>Timezone</title>
@@ -44,34 +44,75 @@
 </p>
 
 <p>
-MIPS-based systems can choose from <c>mips-sources</c> (the default kernel
-source for the MIPS architecture) and <c>mips-prepatch-sources</c> (prerelease
-kernel tree).
+MIPS-based systems have just the one kernel tree to choose from, <c>mips-sources</c>.
+Special patches are needed to make certain systems work.  The table below
+displays the USE flags required to enable the patchsets.  Note that Indy,
+Indigo2 (R4k) and Challenge S systems do not require any additional patchsets.
 </p>
 
-<p>
-Choose your kernel source and install it using <c>emerge</c>.  Of course
-substitute with your choice of sources, this is merely an example.  The
-<c>USE="-doc"</c> is necessary to avoid installing xorg-x11 or other
-dependencies at this point. <c>USE="symlink"</c> is not necessary for a new
-install, but ensures proper creation of the <path>/usr/src/linux</path>
-symlink.
-</p>
+<table>
+<tr>
+  <th>USE flag</th>
+  <th>System</th>
+</tr>
+<tr>
+  <ti><c>cobalt</c></ti>
+  <ti>Cobalt Qube/RaQ support</ti>
+</tr>
+<tr>
+  <ti><c>ip27</c></ti>
+  <ti>SGI Origin 200/2000 support (1)</ti>
+</tr>
+<tr>
+  <ti><c>ip28</c></ti>
+  <ti>SGI Indigo2 Impact (R10000) support (1,2)</ti>
+</tr>
+<tr>
+  <ti><c>ip30</c></ti>
+  <ti>SGI Octane/Octane2 support (1)</ti>
+</tr>
+</table>
 
 <note>
-Special patches are needed to make a kernel work on Cobalt servers.  The
-<c>cobalt</c> USE flag must be defined in order to grab the necessary patches
-and apply them.
+The <c>USE="-doc"</c> disables the generation of kernel API documentation, which
+would otherwise pull in numerous dependancies not required for this step.
 </note>
 
-<pre caption="Installing a kernel source">
-<comment>(For SGI machines)</comment>
-# <i>USE="-doc symlink" emerge mips-sources</i>
-
-<comment>(For Cobalt machines)</comment>
-# <i>mkdir -p /etc/portage</i>
+<pre caption="Setting USE flags and merging kernel sources...">
+<comment>(Substitute cobalt with the appropriate USE flag for your system if required)</comment>
+# <i>mkdir /etc/portage</i>
 # <i>echo "sys-kernel/mips-sources cobalt" &gt;&gt; /etc/portage/package.use</i>
-# <i>USE="-doc symlink" emerge mips-sources</i>
+
+<comment>(Unpack &amp; install the kernel sources)</comment>
+# <i>USE="-doc" emerge mips-sources</i>
+</pre>
+
+<impo>
+(1) On the Origin 200/2000, Indigo2 Impact (R10000), Octane/Octane2 and O2, a
+64-bit kernel is required to boot these systems.  For these machines, you should
+switch to the <path>default-linux/mips/mips64/RELEASE</path>
+profile by altering the <path>/etc/make.profile</path> symlink.  Then you can
+<c>emerge gcc-mips64</c> to create a cross-compiler for building 64-bit kernels.
+</impo>
+
+<impo>
+(2) The Indigo2 Impact is a special case in that it requires special patch to
+be applied to <c>gcc</c> before it will build an IP28 kernel correctly.  This
+patch adds support for the <c>-mip28-cache-barriers</c> CFLAG, which is used 
+when building kernels to work around the inherent hardware bug brought on by
+speculative execution.  This USE flag can be set in
+<path>/etc/make.conf</path>.  This is done for you by setting your profile to
+<path>default-linux/mips/mips64/ip28/RELEASE</path>, which also
+takes care of (1).
+</impo>
+
+<pre caption="Changing Profiles and installing gcc-mips64...">
+<comment>(This assumes PORTDIR is in the usual location; /usr/portage)</comment>
+# <i>rm /etc/make.profile</i>
+# <i>ln -s /usr/portage/profiles/default-linux/mips/mips64/2005.0</i> <comment>(or .../mips64/ip28/2005.0)</comment>
+
+<comment>(Install the 64-bit kernel toolchain)</comment>
+# <i>emerge gcc-mips64</i>
 </pre>
 
 <p>
@@ -83,7 +124,18 @@
 
 <pre caption="Viewing the kernel source symlink">
 # <i>ls -l /usr/src/linux</i>
-lrwxrwxrwx    1 root     root           12 Oct 13 11:04 /usr/src/linux -&gt; linux-2.4.24
+lrwxrwxrwx    1 root     root           12 Oct 13 11:04 /usr/src/linux -&gt; linux-2.6.13.4
+</pre>
+
+<p>
+If this isn't the case (i.e. the symlink points to a different kernel source) 
+change the symlink before you continue:
+</p>
+
+<pre caption="Changing the kernel source symlink">
+# <i>rm /usr/src/linux</i>
+# <i>cd /usr/src</i>
+# <i>ln -s linux-2.6.13.4 linux</i>
 </pre>
 
 <p>
@@ -101,53 +153,107 @@
 
 <p>
 Previously, we went through the manual configuration of how to set up the kernel
-sources.  Instead, we have uploaded a number of sample configurations which you
-can base your configuration upon.  Simply click on the closest option that
-matches your system and kernel version.  You may also find other configuration
-samples at the URLs mentioned below.
+sources.  This has become impractical with the number of systems we now support.
+This section details various sources for sample kernel configurations.
+</p>
+
+</body>
+</subsection>
+<subsection>
+<title>Using sample configurations in the kernel source</title>
+<body>
+
+<p>
+Many of the systems supported have sample .configs hiding in amongst the kernel
+source.  Not all systems have configs distributed in this way.  Those that do,
+can be configured using the commands mentioned in the table below.
 </p>
 
 <table>
-  <tr>
-    <th>System</th>
-    <th>Kernel Version</th>
-  </tr>
-  <tr>
-    <ti>SGI IP22 (Indy, Indigo 2, Challenge S)</ti>
-    <ti>
-      <uri link="http://www.longlandclan.hopto.org/~stuartl/mips-linux/sgi/ip22/config/2.4.29-mipscvs-20050130.gz">2.4.29</uri>
-    </ti>
-  </tr>
-  <tr>
-    <ti>Cobalt Qube/Raq 2800</ti>
-    <ti>
-      <uri link="http://dev.gentoo.org/~kumba/mips/cobalt/kernel/cobalt-2605.config">2.6.5</uri>
-      <uri link="http://dev.gentoo.org/~kumba/mips/cobalt/kernel/cobalt-2606.config">2.6.6</uri>
-      <uri link="http://dev.gentoo.org/~kumba/mips/cobalt/kernel/cobalt-config-2609">2.6.9</uri>
-    </ti>
-  </tr>
+<tr>
+  <th>System</th>
+  <th>Configure command</th>
+</tr>
+<tr>
+  <ti>Cobalt Servers</ti>
+  <ti><c>make cobalt_defconfig</c></ti>
+</tr>
+<tr>
+  <ti>Indy, Indigo2 (R4k), Challenge S</ti>
+  <ti><c>make ip22_defconfig</c></ti>
+</tr>
+<tr>
+  <ti>Origin 200/2000</ti>
+  <ti><c>make ip27_defconfig</c></ti>
+</tr>
+<tr>
+  <ti>Indigo2 Impact (R10k)</ti>
+  <ti>
+    <c>make ip28_defconfig</c> (requires <c>mips-sources-2.6.14.5</c> or
+    later)
+  </ti>
+</tr>
+<tr>
+  <ti>O2</ti>
+  <ti><c>make ip32_defconfig</c></ti>
+</tr>
 </table>
 
-<ul>
-  <li>
-    IP22 (Indy, Indigo2, Challenge S) Configurations:
-    <uri link="http://www.longlandclan.hopto.org/~stuartl/mips-linux/sgi/ip22/config">
-      http://www.longlandclan.hopto.org/~stuartl/mips-linux/sgi/ip22/config
-    </uri>
-  </li>
-  <li>
-    Cobalt Server Configurations:
-    <uri link="http://dev.gentoo.org/~kumba/mips">
-      http://dev.gentoo.org/~kumba/mips
-    </uri>
-  </li>
-</ul>
+</body>
+</subsection>
 
-<note>
-More kernel configuration examples can be found on the Gentoo/MIPS Hardware
-Support Database, which is located at
+<subsection>
+<title>Using the running kernel config from the installation media</title>
+<body>
+
+<p>
+All of the Gentoo installation images provide a kernel config option as part of
+the image itself, accessible as <path>/proc/config.gz</path>.  This may be used
+in many cases.  It is best though if your kernel source matches closely, the
+kernel that is currently running.  To extract it, simply run it through
+<c>zcat</c> as shown below.
+</p>
+
+<pre caption="Extracting .config from /proc/config.gz">
+# <i>zcat /proc/config.gz > .config</i>
+</pre>
+
+<impo>
+This kernel config is set up for a netboot image.  That
+is, it will expect to find a root filesystem image somewhere nearby, either as a
+directory for initramfs, or a loopback device for initrd.  When you run <c>make
+menuconfig</c> below, don't forget to go into General Setup and disable the
+options for initramfs.
+</impo>
+
+</body>
+</subsection>
+
+<subsection>
+<title>The Hardware Compatability Database</title>
+<body>
+
+<p>
+As an aid to users in finding working settings, a hardware compatability
+database was set up.  This database lists the support for various MIPS devices,
+and allows users to contribute kernel configurations that are known to work.
+The address for this site is
 <uri>http://stuartl.longlandclan.hopto.org/gentoo/mips</uri>.
-</note>
+</p>
+
+<p>
+If you find this service useful, you're welcome to contribute your notes and
+.config files so that others may benefit from your experience.  It should be
+noted however that there is no guarantee that any of the configuration files
+downloaded from this site will work.
+</p>
+
+</body>
+</subsection>
+
+<subsection>
+<title>Customising the configuration for your needs.</title>
+<body>
 
 <p>
 Once you have found a configuration, download it into your kernel source
@@ -164,6 +270,15 @@
 # <i>make menuconfig</i>
 </pre>
 
+<impo>
+In the Kernel Hacking section, there is an option named "Are You Using A Cross
+Compiler?".  This tells the kernel Makefiles to prepend "<c>mips-linux-</c>" (or
+<c>mipsel-linux</c> ... etc) to <c>gcc</c> and <c>as</c> commands when compiling
+the kernel.  This should be turned off, even if cross-compiling.  Instead, if
+you do need to call a cross-compiler, specify the prefix using the
+<c>CROSS_COMPILE</c> variable as shown in the next section.
+</impo>
+
 </body>
 </subsection>
 <subsection id="compiling">
@@ -175,12 +290,40 @@
 the configuration and start the compilation process:
 </p>
 
+<note>
+On 64-bit machines, you need to specify
+<c>CROSS_COMPILE=mips64-unknown-linux-gnu-</c> (or <c>mips64el-...</c> if on
+a little-endian system) to use the 64-bit compiler.
+</note>
+
 <pre caption="Compiling the kernel">
-<comment>(For 2.4 kernel)</comment>
-# <i>make dep &amp;&amp; make vmlinux modules modules_install</i>
+<comment>(For 2.4 kernel only)</comment>
+# <i>make dep</i>
+
+<comment>(2.4 and 2.6 kernels -- compiling natively)</comment>
+# <i>make vmlinux modules modules_install</i>
 
-<comment>(For 2.6 kernel)</comment>
-# <i>make &amp;&amp; make modules_install</i>
+<comment>(2.4 and 2.6 kernels -- cross-compiling on target machine)</comment>
+<comment>(    Adjust the mips64-unknown-linux-gnu- accordingly    )</comment>
+# <i>make vmlinux modules modules_install CROSS_COMPILE=mips64-unknown-linux-gnu-</i>
+
+<comment>(When compiling on another machine, such as an x86 box... use the)</comment>
+<comment>( following commands to compile the kernel &amp; install modules into)</comment>
+<comment>(  a specific directory to be transferred to the target machine. )</comment>
+# <i>make vmlinux modules CROSS_COMPILE=mips64-unknown-linux-gnu-</i>
+# <i>make modules_install INSTALL_MOD_PATH=/somewhere</i>
+</pre>
+
+<impo>
+When compiling a 64-bit kernel for the Indy, Indigo2 (R4k), Challenge S and O2,
+use the <c>vmlinux.32</c> target instead of <c>vmlinux</c>.  Otherwise, your
+machine will not be able to boot.  This is to work around the PROM not
+understanding the ELF64 format.
+</impo>
+
+<pre caption="Using the vmlinux.32 target">
+# <i>make vmlinux.32</i>
+<comment>(This will create vmlinux.32 -- which is your final kernel)</comment>
 </pre>
 
 <p>
@@ -190,15 +333,14 @@
 
 <note>
 On Cobalt servers, the bootloader will expect to see a compressed kernel image.
-Remember to <c>gzip -9</c> the file once it is in <path>/boot</path>. In the
-following example, replace <path>&lt;kernel-version&gt;</path> with your kernel
-version.
+Remember to <c>gzip -9</c> the file once it is in <path>/boot</path>.
 </note>
 
 <pre caption="Installing the kernel">
-# <i>cp vmlinux /boot/&lt;kernel-version&lt;</i>
+# <i>cp vmlinux /boot/kernel-2.6.13.4</i>
+
 <comment>(Cobalt Servers -- Compressing the kernel image)</comment>
-# <i>gzip -9v /boot/&lt;kernel-version&lt;</i>
+# <i>gzip -9v /boot/kernel-2.6.13.4</i>
 </pre>
 
 <!--



1.2       +153 -257  xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-mips-medium.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-mips-medium.xml?rev=1.2&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-mips-medium.xml?rev=1.2&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-mips-medium.xml.diff?r1=1.1&r2=1.2&cvsroot=gentoo

Index: hb-install-mips-medium.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-mips-medium.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- hb-install-mips-medium.xml	12 Feb 2006 13:54:32 -0000	1.1
+++ hb-install-mips-medium.xml	12 Feb 2006 14:31:58 -0000	1.2
@@ -4,12 +4,12 @@
 <!-- The content of this document is licensed under the CC-BY-SA license -->
 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
 
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-mips-medium.xml,v 1.1 2006/02/12 13:54:32 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/hb-install-mips-medium.xml,v 1.2 2006/02/12 14:31:58 nightmorph Exp $ -->
 
 <sections>
 
-<version>1.11</version>
-<date>2005-11-11</date>
+<version>1.12</version>
+<date>2006-02-12</date>
 
 <section>
 <title>Hardware Requirements</title>
@@ -30,6 +30,14 @@
 
 <table>
 <tr>
+  <th>CPU <e>(Big Endian port)</e></th>
+  <ti>MIPS3, MIPS4, MIPS5 or MIPS64-class CPU</ti>
+</tr>
+<tr>
+  <th>CPU <e>(Little Endian port)</e></th>
+  <ti>MIPS4, MIPS5 or MIPS64-class CPU</ti>
+</tr>
+<tr>
   <th>Memory</th>
   <ti>64 MB</ti>
 </tr>
@@ -107,6 +115,7 @@
       <uri link="http://www.linux-mips.org/wiki/index.php/R5000">RM5000</uri>,
       <uri link="http://www.linux-mips.org/wiki/index.php/RM7000">RM7000</uri>
       <uri link="http://www.linux-mips.org/wiki/index.php/R8000">R8000</uri>,
+      R9000,
       <uri link="http://www.linux-mips.org/wiki/index.php/R10000">R10000</uri>,
       <uri link="http://www.linux-mips.org/wiki/index.php/R10000">R12000</uri>,
       <uri link="http://www.linux-mips.org/wiki/index.php/R10000">R14000</uri>,
@@ -120,8 +129,36 @@
       None As Yet
     </ti>
   </tr>
+  <tr>
+    <ti>MIPS32</ti>
+    <ti>32-bit</ti>
+    <ti>
+      AMD Alchemy series, 4kc, 4km, many others...
+    </ti>
+  </tr>
+  <tr>
+    <ti>MIPS64</ti>
+    <ti>64-bit</ti>
+    <ti>
+      Broadcom SiByte SB1, 5kc ... etc...
+    </ti>
+  </tr>
 </table>
 
+<note>
+The <c>MIPS5</c> ISA level was designed by Silicon Graphics back in 1994, but
+never actually got used in a real life CPU.  It lives on as part of the
+<c>MIPS64</c> ISA.
+</note>
+
+<note>
+The <c>MIPS32</c> and <c>MIPS64</c> ISAs are a common source of confusion.  The
+<c>MIPS64</c> ISA level is actually a superset of the <c>MIPS5</c> ISA, so it
+includes all instructions from <c>MIPS5</c> and earlier ISAs.  <c>MIPS32</c> is
+the 32-bit subset of <c>MIPS64</c>, it exists because most applications only
+require 32-bit processing.
+</note>
+
 <p>
 Also, another important concept to grasp is the concept of <b>endianness</b>.
 Endianness refers to the way that a CPU reads words from main memory.  A word
@@ -222,8 +259,8 @@
 <p>
 In this section, we'll cover what you need in order to successfully network boot
 a Silicon Graphics workstation or Cobalt Server appliance.  This is just a brief
-guide, it is not intended to be thorough, for more information, I recommend
-reading the <uri link="/doc/en/diskless-howto.xml">Diskless
+guide, it is not intended to be thorough, for more information, it is
+recommended that you read the <uri link="/doc/en/diskless-howto.xml">Diskless
 HOWTO</uri>.
 </p>
 
@@ -268,12 +305,9 @@
 SGI machines use a MiniDIN 8 connector for the serial ports.  Apparently Apple
 modem cables work just fine as serial cables, but with Apple machines being
 equipped with USB &amp; internal modems, these are getting harder to
-find.  A number of sites describe how to make these cables (Google is your
-friend).  The following site describes making such a cable.  It's in German,
-but has a reasonably good wiring diagram.
-<uri link="http://www.arbeitsplatzvernichtung-durch-outsourcing.de/marty44/sgihard.html">
-  http://www.arbeitsplatzvernichtung-durch-outsourcing.de/marty44/sgihard.html
-</uri>
+find.  One wiring diagram is available from the <uri
+link="http://www.linux-mips.org/wiki/Serial_Cable">Linux/MIPS Wiki</uri>, and
+most electronics stores should stock the plugs required.
 </note>
 
 <note>
@@ -302,7 +336,7 @@
 
 <p>
 Okay, so you've got your bits and pieces together, now to set everything up.  As
-I mentioned earlier -- this is not a complete guide, this is a bare-bones config
+mentioned earlier -- this is not a complete guide, this is a bare-bones config
 that will just get things rolling.  You can either use this when starting a
 setup from scratch, or use the suggestions to amend your existing setup to
 support netbooting.
@@ -315,6 +349,12 @@
 separate machine to the DHCP server if desired.
 </p>
 
+<warn>
+The Gentoo/MIPS Team cannot help you with setting up other operating
+systems as netboot servers.  If you choose a different OS, it is assumed you
+know what you're doing.
+</warn>
+
 <p>
 First Step -- configuring DHCP.  In order for the ISC DHCP daemon to respond
 to BOOTP requests (as required by the SGI &amp; Cobalt BOOTROM) you need to
@@ -361,10 +401,9 @@
 </p>
 
 <p>
-Next Step -- Setting up TFTP server.  For the purposes of this guide, I'll
-restrict this to the tftp-hpa TFTP daemon.  I use this myself on SGI machines,
-Cobalt servers and PXE clients alike without any hassle.  Installation and
-configuration is fairly straightforward:
+Next Step -- Setting up TFTP server.  It is recommended that you use
+<c>tftp-hpa</c> as it is the only TFTP daemon known to work correctly.  Proceed
+by installing it as shown below.
 </p>
 
 <pre caption="Installing tftp-hpa">
@@ -372,15 +411,9 @@
 </pre>
 
 <p>
-Now, I personally like to move my <path>/tftpboot</path> directory into
-<path>/home</path> where I have more space.  This is totally optional, and can
-be configured through the <path>/etc/conf.d/in.tftpd</path> file.  For the
-purposes of this guide, I'll assume you've left it in the default place.
-</p>
-
-<p>
-Now that everything is configured, we're ready to move onto the fun bit --
-tayloring our config to suit the machine we wish to netboot.
+This will create <path>/tftproot</path> for you to store the netboot images.
+You may move this elsewhere if you wish.  For the purposes of this guide, it is
+assumed that you have left it in the default location.
 </p>
 
 </body>
@@ -458,16 +491,12 @@
 <body>
 
 <p>
-Once you have downloaded the file, simply place it in your
-<path>/tftpboot</path> directory.  Then edit your
-<path>/etc/dhcp/dhcpd.conf</path> and add the entry for your SGI client.
+Once you have downloaded the file, place the decompressed image file in your
+<path>/tftproot</path> directory.  (Use <c>bzip2 -d</c> to decompress)
+Then edit your <path>/etc/dhcp/dhcpd.conf</path> and add the entry for your
+SGI client.
 </p>
 
-<note>
-You may need to create the <path>/tftpboot</path> directory if it isn't
-there already.
-</note>
-
 <pre caption="dhcpd.conf snippet for SGI Workstation">
 subnet xxx.xxx.xxx.xxx netmask xxx.xxx.xxx.xxx {
   <comment># ... usual stuff here ...</comment>
@@ -625,25 +654,18 @@
 
 <ul>
   <li>
-    dhcpd is giving the SGI Machine an IP Address.  You should see some
+    <c>dhcpd</c> is giving the SGI Machine an IP Address.  You should see some
     messages about a BOOTP request in the system logs.  <c>tcpdump</c> is also
     useful here.
   </li>
   <li>
     Permissions are set properly in your tftp folder (typically 
-    <path>/tftpboot</path> -- should be world readable)
+    <path>/tftproot</path> -- should be world readable)
   </li>
   <li>
     Check system logs to see what the tftp server is reporting (errors
     perhaps)
   </li>
-<!--
-  I really think this tip can go...
-  
-  <li>
-    Pray to a Tux plushie (this may or may not work, and is not an officially
-    supported troubleshooting technique)
-  </li>-->
 </ul>
 
 <p>
@@ -664,6 +686,82 @@
 </section>
 
 <section>
+<title>Alternative Method: Gentoo/MIPS SGI LiveCD</title>
+<subsection>
+<title>Overview</title>
+<body>
+
+<p>
+On Silicon Graphics machines, it is possible to boot from a CD in order to
+install operating systems.  (This is how one installs IRIX for instance)
+Recently, images for such bootable CDs to install Gentoo have been made
+possible.  These CDs are designed to work in the same way.
+</p>
+
+<p>
+At the moment the Gentoo/MIPS Live CD will only work on the SGI Indy,
+Indigo 2 and O2 workstations equipped with R4000 and R5000-series CPUs, however
+other platforms may be possible in future.
+</p>
+
+<p>
+You can find the Live CD images for download on your favourite Gentoo Mirror
+under the <path>experimental/mips/livecd</path> directory.
+</p>
+
+<warn>
+These CDs are highly experimental at this time.  They may or may not work at
+this time.  You can report success or failures either on
+<uri link="http://bugs.gentoo.org">Bugzilla</uri>,
+<uri link="http://forums.gentoo.org/viewtopic.php?t=242518">this forum
+thread</uri> or in the <c>#gentoo-mips</c>
+<uri link="http://www.gentoo.org/main/en/irc.xml">IRC channel</uri>.  We would
+love to hear from you.
+</warn>
+
+</body>
+
+</subsection>
+
+<subsection>
+<title>Burning a Live CD</title>
+<body>
+
+<p>
+An important thing to note, the SGI PROM does not understand the ISO9660 format,
+nor does it know anything about the El Torito boot standard.  These CD images
+are constructed as a SGI disklabel with the boot image in the volume header like
+a hard drive.  Therefore, care must be taken when burning the CD image.
+</p>
+
+<p>
+Below is an example command that assumes 24x burning speed on an IDE burner.  If
+you have a SCSI burner for instance, you may want to adjust the <c>dev</c>
+statement as appropriate.  Likewise with the <c>speed</c> option - if you
+strike troubles, you might want to try dropping the speed.
+</p>
+
+<pre caption="Burning using cdrecord">
+# <i>bzip2 -d mips-livecd-prototype-rc2-20041027.img.bz2</i>
+# <i>cdrecord -vv -pad speed=24 dev=ATAPI:0,0,0 -tao mips-livecd-prototype-rc2-20041027.img</i>
+</pre>
+
+<note>
+It may be possible to burn these CDs under Windows, assuming your burning
+program just blindly burns the image as is.  However, no one has succeeded in
+making a working CD this way to date.
+</note>
+
+<note>
+If you don't know what to put as your <c>dev</c> argument, run <c>cdrecord
+-scanbus</c> as root - this will tell you where your burner is located.
+</note>
+
+</body>
+</subsection>
+</section>
+
+<section>
 <title>Netbooting on Cobalt Servers</title>
 <subsection>
 <body>
@@ -681,17 +779,7 @@
 buttons whilst powering the unit on.  The machine will then attempt to obtain an
 IP number via BOOTP, mount the <path>/nfsroot</path> directory from the server via
 NFS, then try to download and boot the file <path>vmlinux_raq-2800.gz</path>
-which it assumes to be a standard ELF binary.
-</p>
-
-<p>
-Unfortunately, the Cobalt BOOTROM does not give us any say in this procedure,
-so the file HAS to reside in <path>/nfsroot</path> directory, and must be less
-than 675kB in size.  In this guide, we'll set up 
-<uri link="http://www.colonel-panic.org/cobalt-mips/">CoLo</uri> to allow us to
-boot larger kernels than this limit.  CoLo also supports embedded ramdisks,
-therefore ridding the need of a full root filesystem sitting in
-<path>/nfsroot</path>.
+(depending on the model) which it assumes to be a standard ELF binary.
 </p>
 
 </body>
@@ -703,52 +791,18 @@
 
 <p>
 Inside
-<uri link="http://dev.gentoo.org/~kumba/mips/cobalt/netboot/">
-http://dev.gentoo.org/~kumba/mips/cobalt/netboot/</uri>
+<uri link="http://dev.gentoo.org/~redhatter/mips/cobalt/netboots/">
+http://dev.gentoo.org/~redhatter/mips/cobalt/netboots/</uri>
 you'll find the necessary boot images for getting a Cobalt up
 and running.  The files you need will have the name
-<path>cobalt-netboot-YYYYMMDD.img.gz</path> -- select the most recent one and
-place it in your <path>/nfsroot</path> directory.  For convenience, rename the
-file to <path>gentoo-cobalt.img.gz</path> -- I'll assume that you have done
-this.
-</p>
-
-<p>
-Once that is done, head over to
-<uri link="http://www.colonel-panic.org/cobalt-mips/">
-http://www.colonel-panic.org/cobalt-mips/</uri> and
-download the latest release of the CoLo bootloader.  Untar this somewhere
-convenient.  Inside the <path>colo-1.XX/binaries</path> directory created,
-you should find under a file named <path>colo-chain.elf</path>.  Gzip this
-file up and place it in <path>/nfsroot</path> calling it
-<path>vmlinux_raq-2800.gz</path>. Also, in some cases, you will need to create a
-symbolic link called <path>boot</path> that points back to
-<path>/nfsroot</path>. You can do this in one hit using these commands:
+<path>nfsroot-KERNEL-COLO-DATE-cobalt.tar</path> -- select the most recent one and
+unpack it to <path>/</path> as shown below:
 </p>
 
-<note>
-Please note, the RaQ1 and Qube 2700 look for <path>vmlinux.gz</path> rather than
-<path>vmlinux_raq-2800.gz</path>.
-</note>
-
-<pre caption="Putting CoLo in the nfsroot">
-# <i>tar -xzvf colo-1.XX.tar.gz</i>
-# <i>cd colo-1.XX/binaries</i>
-
-<comment>(For Qube 2800, RaQ2, etc)</comment>
-# <i>gzip -9vc colo-chain.elf &gt; /nfsroot/vmlinux_raq-2800.gz</i>
-
-<comment>(For RaQ1, Qube 2700)</comment>
-# <i>gzip -9vc colo-chain.elf &gt; /nfsroot/vmlinux.gz</i>
-# <i>cd /nfsroot</i>
-# <i>ln . boot</i>
+<pre caption="Unpacking the nfsroot image">
+# <i>tar -C / -xvf nfsroot-2.6.13.4-1.19-20051122.tar</i>
 </pre>
 
-<note>
-If the latest CoLo release fails to boot, you may wish to try an earlier
-release. Version 1.16 and earlier are known to work.
-</note>
-
 </body>
 </subsection>
 
@@ -812,6 +866,7 @@
   host <i>qube</i> {
     <comment># Path to the nfsroot directory.</comment>
     <comment># This is mainly for when using the TFTP boot option on CoLo</comment>
+    <comment># You shouldn't need to change this.</comment>
     option root-path "/nfsroot";
 
     <comment># Cobalt server's ethernet MAC address</comment>
@@ -823,9 +878,9 @@
     <comment># IP address of cobalt server</comment>
     fixed-address <i>192.168.10.2</i>;
 
-    <comment># Image to download</comment>
-    <comment># Again, this has more to do with CoLo</comment>
-    filename "<i>gentoo-cobalt.img.gz</i>";
+    <comment># Location of the default.colo file relative to /nfsroot</comment>
+    <comment># You shouldn't need to change this.</comment>
+    filename "default.colo";
   }
 }
 </pre>
@@ -872,91 +927,11 @@
 <p>
 If all is well, the back panel should display "Net Booting", you should
 see some network activity, closely followed by CoLo kicking in.  On the rear
-panel, scroll down the menu until you see "Boot Shell" then press ENTER.  On the
-serial console, you should be dropped to a prompt as shown below.
-</p>
-
-<note>
-It has been reported that simply selecting the NFS boot option does all of this
-for you under modern versions of CoLo. If selecting this option does not work,
-then read on.
-</note>
-
-<pre caption="CoLo booting to a prompt">
-[ "CoLo" v1.13 ]
-stage2: 87fb0000-88000000
-pci: unit type &lt;Qube2&gt;
-tulip: {00:10:e0:00:86:3d}
-ide: resetting
-boot: running boot menu
-&gt;
-</pre>
-
-<p>
-First step, tell the machine to fetch an address via DHCP.  Type <c>dhcp</c> at
-the prompt.
-</p>
-
-<pre caption="Fetching an address via DHCP">
-&gt; <i>dhcp</i>
-net: interface up
-dhcp: DISCOVER
-dhcp: OFFER 10.0.0.1 &lt;-- 192.168.10.254
-dhcp: REQUEST
-arp: sent request for 192.168.10.254
-udp: no matching socket 192.168.5.1:67 --&gt; 10.0.0.1:68
-arp: resolved 192.168.10.254
-udp: no matching socket 192.168.5.1:67 --&gt; 10.0.0.1:68
-dhcp: DISCOVER
-dhcp: OFFER 10.0.0.1 &lt;-- 192.168.10.254
-dhcp: REQUEST
-udp: no matching socket 192.168.5.1:67 --&gt; 10.0.0.1:68
-dhcp: ACK
-net: interface down
-net: interface up
-  address     10.0.0.1
-  netmask     255.255.255.0
-  gateway     10.0.0.254
-  name server 192.168.5.1
-</pre>
-
-<p>
-NOTE: If you have a Windows network you may see messages along the lines of
-<c>udp: no matching socket</c>.  These are in response to network broadcasts on
-ports that CoLo doesn't recognise.  As annoying as they are, they are perfectly
-harmless.
-</p>
-
-<pre caption="'no matching socket' error messages">
-udp: no matching socket 10.0.0.254:138 --&gt; 10.0.0.255:138
-udp: no matching socket 10.0.0.254:138 --&gt; 10.0.0.255:138
-udp: no matching socket 10.0.0.253:1062 --&gt; 10.0.0.255:137
-udp: no matching socket 10.0.0.253:1062 --&gt; 10.0.0.255:137
-</pre>
-
-<p>
-Okay, the next step is to tell the Cobalt server to download its kernel.
-</p>
-
-<pre caption="Downloading the kernel">
-&gt; <i>nfs 10.0.0.254 /nfsroot gentoo.img.gz</i>
-arp: sent request for 10.0.0.254
-arp: resolved 10.0.0.254
-udp: no matching socket 10.0.0.253:1062 --&gt; 10.0.0.255:137
-nfs: mounted "/nfsroot"
-nfs: lookup "gentoo.img.gz"
-nfs: mode &lt;0100644&gt;
-4651KB loaded (1240KB/sec)
-0048ada0 4763040t
-</pre>
-
-<p>
-And that's it... it has now downloaded its kernel, we now can tell it to start
-booting.
+panel, scroll down the menu until you see "Network (NFS)" then press ENTER.
+You should notice the machine starts booting on the serial console.
 </p>
 
 <pre caption="Booting the kernel">
-&gt; <i>execute</i>
 elf: 80080000 &lt;-- 00001000 6586368t + 192624t
 elf: entry 80328040
 net: interface down
@@ -1040,84 +1015,5 @@
 </body>
 </subsection>
 </section>
-<!--
-
-  Commented Out Until Further Notice
 
-<section>
-<title>Gentoo/MIPS LiveCD</title>
-<subsection>
-<title>Overview</title>
-<body>
-
-<p>
-On Silicon Graphics machines, it is possible to boot from a CD in order to
-install operating systems.  (This is how one installs IRIX for instance)
-Recently, images for such bootable CDs to install Gentoo have been made
-possible.  These CDs are designed to work in the same way.
-</p>
-
-<p>
-At the moment the Gentoo/MIPS Live CD will only work on the SGI Indy,
-Indigo 2 and O2 workstations equipped with R4000 and R5000-series CPUs, however
-other platforms may be possible in future.
-</p>
-
-<p>
-You can find the Live CD images for download on your favourite Gentoo Mirror
-under the <path>experimental/mips/livecd</path> directory.
-</p>
-
-<warn>
-These CDs are highly experimental at this time.  They may or may not work at
-this time.  You can report success or failures either on
-<uri link="http://bugs.gentoo.org">Bugzilla</uri>,
-<uri link="http://forums.gentoo.org/viewtopic.php?t=242518">this forum
-thread</uri> or in the <c>#gentoo-mips</c>
-<uri link="http://www.gentoo.org/main/en/irc.xml">IRC channel</uri>.  We would
-love to hear from you.
-</warn>
-
-</body>
-
-</subsection>
-
-<subsection>
-<title>Burning a Live CD</title>
-<body>
-
-<p>
-An important thing to note, the SGI PROM does not understand the ISO9660 format,
-nor does it know anything about the El Torito boot standard.  These CD images
-are constructed as a SGI disklabel with the boot image in the volume header like
-a hard drive.  Therefore, care must be taken when burning the CD image.
-</p>
-
-<p>
-Below is an example command that assumes 24x burning speed on an IDE burner.  If
-you have a SCSI burner for instance, you may want to adjust the <c>dev</c>
-statement as appropriate.  Likewise with the <c>speed</c> option - if you
-strike troubles, you might want to try dropping the speed.
-</p>
-
-<pre caption="Burning using cdrecord">
-# <i>bzip2 -d mips-livecd-prototype-rc2-20041027.img.bz2</i>
-# <i>cdrecord -vv -pad speed=24 dev=ATAPI:0,0,0 -tao mips-livecd-prototype-rc2-20041027.img</i>
-</pre>
-
-<note>
-It may be possible to burn these CDs under Windows, assuming your burning
-program just blindly burns the image as is.  However, no one has succeeded in
-making a working CD this way to date.
-</note>
-
-<note>
-If you don't know what to put as your <c>dev</c> argument, run <c>cdrecord
--scanbus</c> as root - this will tell you where your burner is located.
-</note>
-
-</body>
-</subsection>
-</section>
--->
 </sections>



1.4       +6 -3      xml/htdocs/doc/en/handbook/draft/2006.0/index.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/index.xml?rev=1.4&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/index.xml?rev=1.4&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/2006.0/index.xml.diff?r1=1.3&r2=1.4&cvsroot=gentoo

Index: index.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/index.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- index.xml	9 Feb 2006 20:23:40 -0000	1.3
+++ index.xml	12 Feb 2006 14:31:58 -0000	1.4
@@ -1,7 +1,7 @@
 <?xml version='1.0' encoding="UTF-8"?>
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
 
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/index.xml,v 1.3 2006/02/09 20:23:40 fox2mike Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/2006.0/index.xml,v 1.4 2006/02/12 14:31:58 nightmorph Exp $ -->
 
 <guide link="/doc/en/handbook/2006.0/index.xml" disclaimer="draft">
 <title>Gentoo 2006.0 Handbook</title>
@@ -18,8 +18,8 @@
 
 <license/>
 
-<version>6.0</version>
-<date>2006-02-01</date>
+<version>6.1</version>
+<date>2006-02-12</date>
 
 <chapter>
 <title>The Gentoo Linux 2006.0 Handbooks</title>
@@ -89,6 +89,7 @@
     <uri link="handbook-sparc.xml">sparc</uri>,
     <uri link="handbook-alpha.xml">alpha</uri>,
     <uri link="handbook-amd64.xml">amd64</uri>, 
+    <uri link="handbook-mips.xml">mips</uri>, 
     <uri link="handbook-ppc.xml">ppc</uri>, 
     <uri link="handbook-ppc64.xml">ppc64</uri>, 
     <uri link="handbook-hppa.xml">hppa</uri>
@@ -102,6 +103,7 @@
     <uri link="handbook-sparc.xml?full=1">sparc</uri>,
     <uri link="handbook-alpha.xml?full=1">alpha</uri>,
     <uri link="handbook-amd64.xml?full=1">amd64</uri>, 
+    <uri link="handbook-mips.xml?full=1">mips</uri>, 
     <uri link="handbook-ppc.xml?full=1">ppc</uri>, 
     <uri link="handbook-ppc64.xml?full=1">ppc64</uri>, 
     <uri link="handbook-hppa.xml?full=1">hppa</uri>
@@ -115,6 +117,7 @@
     <uri link="handbook-sparc.xml?style=printable&amp;full=1">sparc</uri>,
     <uri link="handbook-alpha.xml?style=printable&amp;full=1">alpha</uri>,
     <uri link="handbook-amd64.xml?style=printable&amp;full=1">amd64</uri>, 
+    <uri link="handbook-mips.xml?style=printable&amp;full=1">mips</uri>, 
     <uri link="handbook-ppc.xml?style=printable&amp;full=1">ppc</uri>, 
     <uri link="handbook-ppc64.xml?style=printable&amp;full=1">ppc64</uri>, 
     <uri link="handbook-hppa.xml?style=printable&amp;full=1">hppa</uri>



-- 
gentoo-doc-cvs@g.o mailing list