[gentoo-doc-cvs] cvs commit: hb-install-ppc-medium.xml

[Joseph Jezak]

josejx      06/02/26 17:44:44

  Modified:    xml/htdocs/doc/en/handbook/draft hb-install-ppc-medium.xml
  Log:
  Merged hb-install-ppc-medium.xml patches.

Revision  Changes    Path
1.30      +48 -37    xml/htdocs/doc/en/handbook/draft/hb-install-ppc-medium.xml

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

Index: hb-install-ppc-medium.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc-medium.xml,v
retrieving revision 1.29
retrieving revision 1.30
diff -u -r1.29 -r1.30
--- hb-install-ppc-medium.xml	26 Feb 2006 16:48:51 -0000	1.29
+++ hb-install-ppc-medium.xml	26 Feb 2006 17:44:44 -0000	1.30
@@ -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/hb-install-ppc-medium.xml,v 1.29 2006/02/26 16:48:51 fox2mike Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc-medium.xml,v 1.30 2006/02/26 17:44:44 josejx Exp $ -->
 
 <sections>
 
-<version>2.8</version>
-<date>2005-11-29</date>
+<version>2.9</version>
+<date>2006-02-18</date>
 
 <section>
 <title>Hardware Requirements</title>
@@ -71,8 +71,9 @@
 </table>
 
 <p>
-Be sure to read up on the <uri link="/doc/en/gentoo-ppc-faq.xml">Gentoo 
-PPC FAQ</uri> before you begin.
+Be sure to read the <uri link="/doc/en/gentoo-ppc-faq.xml">Gentoo PPC FAQ</uri>
+for help with some common installation related issues or if you're unsure as to
+just what's in that PowerPC machine you've got sitting on your desk right now.
 </p>
 
 </body>
@@ -322,15 +323,13 @@
 </p>
 
 <p>
-At this prompt you are able to select a kernel for the subarchitecture you use.
-We provide <c>G3</c>, <c>G4</c> and <c>G5</c>. All kernels are built with
-support for multiple CPUs, but they will boot on single processor machines as
-well.
+We provide one generic kernel, <e>ppc32</e>. This kernel is built with support
+for multiple CPUs, but it will boot on single processor machines as well.
 </p>
 
 <p>
-You are also able to tweak some kernel options at this prompt. The following
-table lists some of the available boot options you can add:
+You can tweak some kernel options at this prompt. The following table lists 
+some of the available boot options you can add:
 </p>
 
 <table>
@@ -342,10 +341,13 @@
   <ti><c>video</c></ti>
   <ti>
     This option takes one of the following vendor-specific tags:
-    <c>radeonfb</c>, <c>rivafb</c>, <c>atyfb</c>, <c>aty128</c> or
-    <c>ofonly</c>. You can follow this tag with the resolution and refreshrate
-    you want to use. For instance <c>video=radeonfb:1280x1024@75</c>. If you are
-    uncertain what to choose, <c>ofonly</c> will most certainly work.
+    <c>nvidiafb</c>, <c>radeonfb</c>, <c>rivafb</c>, <c>atyfb</c>, 
+    <c>aty128</c> or <c>ofonly</c>. You can follow this tag with the resolution 
+    refresh rate and color depth you want to use. For instance,
+    <c>video=radeonfb:1280x1024@75-32</c> will select the ATI Radeon frame buffer
+    at a resolution of 1280x1024 with a refresh rate of 75Hz and a color depth of
+    32 bits. If you are uncertain what to choose, and the default doesn't work,
+    <c>video=ofonly</c> will most certainly work.
   </ti>
 </tr>
 <tr>
@@ -385,11 +387,11 @@
 On the Pegasos simply insert the CD and at the SmartFirmware boot-prompt type
 <c>boot cd /boot/menu</c>. This will open a small bootmenu where you can choose
 between several preconfigured video configs. If you need any special boot
-options you can append them to the command-line. For instance <c>boot cd
-/boot/pegasos video=radeonfb:1280x1024@75 mem=256M</c>.  The complete list of
-kernel appends (in case something goes wrong and you need it) is preconfigured
-in the kernel with <c>console=ttyS0,115200 console=tty0 init=/linuxrc
-looptype=squashfs loop=/livecd.squashfs udev nodevfs cdroot root=/dev/ram0</c>.
+options you can append them to the command-line just like with Yaboot above. 
+For example: <c>boot cd /boot/pegasos video=radeonfb:1280x1024@75 mem=256M</c>.
+The default kernel options (in case something goes wrong and you need it) are 
+preconfigured with <c>console=ttyS0,115200 console=tty0 init=/linuxrc 
+looptype=squashfs loop=/image.squashfs udev nodevfs cdroot root=/dev/ram0</c>.
 </p>
 
 </body>
@@ -402,8 +404,7 @@
 <p>
 If you have an OldWorld Mac the bootable portion of the livecd can't be used.
 The most simple solution is to use MacOS to bootstrap into a Linux environment
-with a tool called BootX.  Boot floppies are being prepared for Macs without
-MacOS, but they are not available at this time.
+with a tool called BootX.  
 </p>
 
 <p>
@@ -412,33 +413,34 @@
 archive into <c>Extensions Folder</c> and the BootX App Control Panel into
 <c>Control Panels</c>, both of which are located in your MacOS System Folder.
 Next, create a folder called "Linux Kernels" in your System folder and copy the
-<c>G3G4</c> kernel from the CD to this folder.  Finally, copy <c>G3G4.igz</c> 
+<c>ppc32</c> kernel from the CD to this folder.  Finally, copy <c>ppc32.igz</c> 
 from the Installation CD <path>boot</path> folder into the MacOS 
 <c>System Folder</c>.
 </p>
 
 <p>
 To prepare BootX, start the BootX App Control Panel.  First select the Options
-dialog and check <c>Use Specified RAM Disk</c> and select <c>G3G4.igz</c> from
+dialog and check <c>Use Specified RAM Disk</c> and select <c>ppc32.igz</c> from
 your System Folder.  Continue back to the initial screen and ensure that the
 ramdisk size is at least <c>32000</c>.  Finally, set the kernel arguments as
 shown below:
 </p>
 
 <pre caption="BootX kernel arguments">
-cdroot root=/dev/ram0 init=linuxrc loop=livecd.squashfs looptype=squashfs console=tty0 nodevfs udev
+cdroot root=/dev/ram0 init=linuxrc loop=image.squashfs looptype=squashfs console=tty0 nodevfs udev
 </pre>
 
 <note>
-The kernel parameters in the yaboot section above are also applicable here.
+The kernel parameters in the yaboot section above are also applicable here. You
+can append any of those options to the kernel arguments above.
 </note>
 
 <p>
 Check once more to make sure the settings are correct and then save the 
 configuration.  This saves typing just in case it doesn't boot or something is
-missing.  Press the Linux button at the top of the window to boot into the 
-Installation CD and continue with <uri link="#booted">And When 
-You're Booted...</uri>
+missing.  Press the Linux button at the top of the window.  If everything goes
+correctly, it should boot into the Installation CD. Continue with 
+<uri link="#booted">And When You're Booted...</uri>
 </p>
 
 </body>
@@ -451,8 +453,8 @@
 <p>
 You will be greeted by a root ("#") prompt on the current console. You can also 
 switch to other consoles by pressing Alt-F2, Alt-F3 and Alt-F4. Get 
-back to the one you started on by pressing Alt-F1. Probably you have to hit
-Alt-fn-Fx on Apple machines.
+back to the one you started on by pressing Alt-F1.  Due to the keyboard layout,
+you may need to press Alt-fn-Fx on Apple machines.
 </p>
 
 <p>
@@ -496,16 +498,25 @@
 of your system's hardware, you will have to load the appropriate kernel modules
 manually. 
 </p>
-
+  
 <p>
-In the next example we try to load the <c>airport</c> module. This module
-supports only the old Airport cards (b-net). AirportExtreme is currently not
-supported under Linux:
+In the next example we try to load the <c>airport</c> module.  This module
+supports only the old Airport cards (802.11b).  Airport Extreme (802.11g) is not
+supported on the InstallCD due to restrictions on firmware distribution.
 </p>
-
-<pre caption="Loading kernel modules">
+  
+<pre caption="Loading the airport module">
 # <i>modprobe airport</i>
 </pre>
+  
+<p>
+On older iMacs, sometimes the network card is not detected properly.  These use
+the BMAC driver:
+</p>
+
+<pre caption="Loading the bmac module">
+# <i>modprobe bmac</i>
+</pre>
 
 </body>
 </subsection>



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