release-notes/devel/en_US ArchSpecific.xml,1.29,1.30
Paul W. Frields (pfrields)
fedora-docs-commits at redhat.com
Tue Apr 8 21:21:01 UTC 2008
Author: pfrields
Update of /cvs/docs/release-notes/devel/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv4457
Modified Files:
ArchSpecific.xml
Log Message:
Resync with wiki for changes
Index: ArchSpecific.xml
===================================================================
RCS file: /cvs/docs/release-notes/devel/en_US/ArchSpecific.xml,v
retrieving revision 1.29
retrieving revision 1.30
diff -u -r1.29 -r1.30
--- ArchSpecific.xml 7 Apr 2008 22:17:30 -0000 1.29
+++ ArchSpecific.xml 8 Apr 2008 21:20:58 -0000 1.30
@@ -83,17 +83,17 @@
</listitem>
<listitem>
<para>
- Fedora 9 supports IBM RS/6000, pSeries, iSeries, and Cell Broadband Engine machines.
+ Fedora 9 supports IBM RS/6000, pSeries, iSeries, and Cell Broadband Engine machines.
</para>
</listitem>
<listitem>
<para>
- Fedora 9 also supports the Sony PlayStation 3 and Genesi Pegasos II and Efika.
+ Fedora 9 also supports the Sony PlayStation 3 and Genesi Pegasos II and Efika.
</para>
</listitem>
<listitem>
<para>
- Fedora 9 includes new hardware support for the P.A. Semiconductor 'Electra' machines.
+ Fedora 9 includes new hardware support for the P.A. Semiconductor 'Electra' machines.
</para>
</listitem>
<listitem>
@@ -226,21 +226,37 @@
<formalpara>
<title>Genesi Pegasos II / Efika 5200B</title>
<para>
- The Fedora kernel supports both Pegasos and Efika without the need to use the "Device Tree Supplement" from powerdeveloper.org. However, the lack of full support for ISO9660 in the firmware means that booting via yaboot from the CD is not possible. You must boot the 'netboot' image instead -- either from the CD or, as its name implies, over the network. Because of the size of the image, you must set the firmware's <option>load-base</option> variable to load files at a high address such as 32MiB instead of the default 4MiB:
+ The Fedora kernel supports both Pegasos and Efika without
+ the need to use the "Device Tree Supplement" from
+ powerdeveloper.org. However, the lack of full support for
+ ISO9660 in the firmware means that booting via yaboot from
+ the CD is not possible. Boot the 'netboot' image instead,
+ either from the CD or over the network. Because of the
+ size of the image, you must set the
+ firmware's <option>load-base</option> variable to load
+ files at a high address such as 32MiB instead of the
+ default 4MiB:
</para>
</formalpara>
-<screen><![CDATA[setenv load-base 0x2000000]]></screen>
-<para>
- At the OpenFirmware prompt, enter the following command to boot the netboot image from the CD:
-</para>
-<screen><![CDATA[boot cd: /images/netboot/ppc32.img]]></screen>
-<para>
- Or from the network:
-</para>
-<screen><![CDATA[boot eth ppc32.img]]></screen>
-<para>
- You must also manually configure OpenFirmware to make the installed Fedora system bootable. To do this, set the <option>boot-device</option> and <option>boot-file</option> environment variables appropriately, to load yaboot from the <filename>/boot</filename> partition. For example, a default installation might require the following:
-</para>
+ <screen><![CDATA[setenv load-base 0x2000000]]></screen>
+ <para>
+ At the OpenFirmware prompt, enter the following command to
+ boot the netboot image from the CD:
+ </para>
+ <screen><![CDATA[boot cd: /images/netboot/ppc32.img]]></screen>
+ <para>
+ Or from the network:
+ </para>
+ <screen><![CDATA[boot eth ppc32.img]]></screen>
+ <para>
+ You must also manually configure OpenFirmware to make the
+ installed Fedora system bootable. To do this, set
+ the <option>boot-device</option>
+ and <option>boot-file</option> environment variables
+ appropriately, to load yaboot from
+ the <filename>/boot</filename> partition. For example, a
+ default installation might require the following:
+ </para>
<screen><![CDATA[
setenv boot-device hd:0
setenv boot-file /yaboot/yaboot
@@ -248,12 +264,18 @@
</screen>
</listitem>
<listitem>
- <formalpara>
- <title>PA Semi Electra</title>
- <para>
- The Electra firmware does not yet support yaboot; to install on Electra, you can boot the <filename>ppc64.img</filename> netboot image. After the installation, you will need to manually configure the firmware to load the installed kernel and initrd from the <filename>/boot</filename> partition. Refer to the firmware documentation for further details.
- </para>
- </formalpara>
+ <formalpara>
+ <title>PA Semi Electra</title>
+ <para>
+ The Electra firmware does not yet support yaboot; to
+ install on Electra, you can boot
+ the <filename>ppc64.img</filename> netboot image. After
+ the installation, you will need to manually configure the
+ firmware to load the installed kernel and initrd from
+ the <filename>/boot</filename> partition. Refer to the
+ firmware documentation for further details.
+ </para>
+ </formalpara>
</listitem>
<listitem>
<formalpara>
@@ -274,14 +296,9 @@
</formalpara>
<para>
Once the boot loader is installed, the PlayStation 3 should
- be able to boot from the Fedora install media. Type
- <command>linux64 xdriver=fbdev</command> at the boot prompt,
- which will work around
- <ulink
- url='https://bugzilla.redhat.com/show_bug.cgi?id=370761'
- />.
- Please note that network installation works best with NFS,
- since that takes less memory than FTP or HTTP methods. Using
+ be able to boot from the Fedora install media. Please note
+ that network installation works best with NFS, since that
+ takes less memory than FTP or HTTP methods. Using
the <command>text</command> option also reduces the amount
of memory taken by the installer.
</para>
@@ -323,13 +340,14 @@
<title>PPC Specific Packages</title>
<para>
- <filename>ppc64-utils</filename> has been split out into
- individual packages reflecting upstream packaging
- (<filename>ps3pf-utils</filename>,
- <filename>powerpc-utils</filename>,
- <filename>powerpc-utils-papr</filename>). The
+ The <package>ppc64-utils</package> package has been split out
+ into individual packages reflecting upstream packaging
+ (<package>ps3pf-utils</package>,
+ <package>powerpc-utils</package>,
+ <package>powerpc-utils-papr</package>). Although the
<command>mkzimage</command> command is no longer supplied, you
- can use the wrapper script from kernel-bootwrapper package - eg:
+ can use the <command>wrapper</command> script from the
+ <package>kernel-bootwrapper</package> package:
</para>
<screen><![CDATA[wrapper -i initrd-${KERN_VERSION}.img -o zImage-${KERN_VERSION}.img vmlinuz-${KERN_VERSION} ]]></screen>
</section>
More information about the Fedora-docs-commits
mailing list