josejx 07/04/02 02:40:59 Modified: hb-install-ppc-kernel.xml Log: Sync'd to draft version.
Revision Changes Path 1.3 xml/htdocs/doc/en/handbook/2007.0/hb-install-ppc-kernel.xml file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-ppc-kernel.xml?rev=1.3&view=markup plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-ppc-kernel.xml?rev=1.3&content-type=text/plain diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-ppc-kernel.xml?r1=1.2&r2=1.3 Index: hb-install-ppc-kernel.xml =================================================================== RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-ppc-kernel.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- hb-install-ppc-kernel.xml 2 Apr 2007 00:49:18 -0000 1.2 +++ hb-install-ppc-kernel.xml 2 Apr 2007 02:40:59 -0000 1.3 @@ -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/2007.0/hb-install-ppc-kernel.xml,v 1.2 2007/04/02 00:49:18 nightmorph Exp $ --> +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2007.0/hb-install-ppc-kernel.xml,v 1.3 2007/04/02 02:40:59 josejx Exp $ --> <sections> <version>8.0</version> -<date>2007-03-12</date> +<date>2007-04-01</date> <section> <title>Timezone</title> @@ -33,7 +33,7 @@ </body> </section> <section> -<title>Installing the Sources</title> +<title>Installing the Kernel Sources</title> <subsection> <title>Choosing a Kernel</title> <body> @@ -41,17 +41,17 @@ <p> The core around which all distributions are built is the Linux kernel. It is the layer between the user programs and your system hardware. Gentoo provides its -users several possible kernel sources. A full listing with description is -available at the <uri link="/doc/en/gentoo-kernel.xml">Gentoo Kernel -Guide</uri>. +users several possible kernels to choose from. A full listing with description +is available at the +<uri link="/doc/en/gentoo-kernel.xml">Gentoo Kernel Guide</uri>. </p> <p> -We suggest using <c>gentoo-sources</c> on PPC, which is a 2.6 kernel. +We suggest using <c>gentoo-sources</c> on PPC, which is a recent 2.6 kernel. </p> <pre caption="Installing a kernel source"> -# <i>emerge gentoo-sources</i> +# <i>emerge --usepkg gentoo-sources</i> </pre> <p> @@ -67,10 +67,10 @@ </pre> <p> -Now it is time to configure and compile your kernel source. You -can use <c>genkernel</c> for this, which will build a generic kernel as used -by the Installation CD. We explain the "manual" configuration first though, as -it is the best way to optimize your environment. +Now it is time to configure and compile your kernel source. You can use +<c>genkernel</c> for this, which will build a generic kernel as used by the +Installation CD. We explain the "manual" configuration first though, as it is +a more efficient configuration. </p> <p> @@ -92,29 +92,29 @@ <p> Manually configuring a kernel is often seen as the most difficult procedure a Linux user ever has to perform. Nothing is less true -- after configuring a -couple of kernels you don't even remember that it was difficult ;) +few kernels you won't even remember that it was difficult ;) </p> <p> However, one thing <e>is</e> true: you must know your system when you start configuring a kernel manually. Most information can be gathered by emerging -pciutils (<c>emerge pciutils</c>) which contains <c>lspci</c>. You will now -be able to use <c>lspci</c> within the chrooted environment. You may safely -ignore any <e>pcilib</e> warnings (like pcilib: cannot open -/sys/bus/pci/devices) that <c>lspci</c> throws out. Alternatively, you can run -<c>lspci</c> from a <e>non-chrooted</e> environment. The results are the same. -You can also run <c>lsmod</c> to see what kernel modules the Installation CD -uses (it might provide you with a nice hint on what to enable). Another place -to look for clues as to what components to enable is to check the kernel -message logs from the successful boot that got you this far. Type <c>dmesg</c> -to see the kernel messages. +pciutils (<c>emerge --usepkg pciutils</c>) which contains the program +<c>lspci</c>. You will now be able to use <c>lspci</c> within the chrooted +environment. You may safely ignore any <e>pcilib</e> warnings (such as pcilib: +cannot open /sys/bus/pci/devices) that <c>lspci</c> throws out. Alternatively, +you can run <c>lspci</c> from a <e>non-chrooted</e> environment. The results +are the same. You can also run <c>lsmod</c> to see what kernel modules the +Installation CD uses (it might provide you with a nice hint on what to enable). +Another place to look for clues as to what components to enable is to check the +kernel message logs from the successful boot that got you this far. Type +<c>dmesg</c> to see these kernel messages. </p> <p> Now, go to your kernel source directory, it's time to configure your kernel. -It is recommended that you add the default settings to your configuration by -first running <c>make pmac32_defconfig</c>. After the default configuration has -been generated, run <c>make menuconfig</c> which will fire up an ncurses-based +Start by configuring a kernel that will boot on most 32 Bit PowerPC machines +by first running <c>make pmac32_defconfig</c>. After the default configuration +has been generated, run <c>make menuconfig</c> to start an ncurses-based configuration menu. </p> @@ -158,6 +158,7 @@ <pre caption="Selecting necessary file systems"> File systems ---> Pseudo Filesystems ---> +<comment>(/proc may already be forced on by your configuration, if so, you'll see --- instead)</comment> [*] /proc file system support [*] Virtual memory file system support (former shm fs) Partition Types ---> @@ -179,7 +180,9 @@ <pre caption="Activating HFS support"> File Systems ---> - [*] HFS Support + Miscellaneous filesystems ---> + <*> Apple Macintosh file system support + <*> Apple Extended HFS file system support </pre> <p> @@ -189,16 +192,16 @@ <pre caption="Selecting PPPoE necessary drivers"> Device Drivers ---> - Networking support ---> + Network device support ---> <*> PPP (point-to-point protocol) support <*> PPP support for async serial ports <*> PPP support for sync tty ports </pre> <p> -The two compression options won't harm but are not definitely needed, neither -does the <c>PPP over Ethernet</c> option, that might only be used by -<c>rp-pppoe</c> when configured to do kernel mode PPPoE. +The two compression options won't harm but are not always needed. The +<c>PPP over Ethernet</c> option might only be used by <c>rp-pppoe</c> when +configured to perform kernel mode PPPoE. </p> <p> @@ -207,15 +210,30 @@ the BMAC driver. </p> +<pre caption="Selecting the network driver"> +Device Drivers ---> + Network device support ---> + Ethernet (10 or 100Mbit) ---> + [*] Ethernet (10 or 100Mbit) + <*> Generic Media Independent Interface device support + <*> MACE (Power Mac ethernet) support + <*> BMAC (G3 ethernet) support + <*> Sun GEM support +</pre> + <p> -At this time, kernel preemption is still unstable on PPC and may cause +At this time, full kernel preemption may still be unstable on PPC and may cause compilation failures and random segfaults. It is <e>strongly</e> suggested -that you do not use this feature. +that you do not use this featurea. Both <e>Voluntary Preemption</e> and +<e>No Forced Preemption</e> should be safe. </p> <pre caption="Ensure the Preemptible Kernel Option is Off"> Kernel options ---> - Preemption Model (No Forced Preemption (Server)) +<comment>(Select One)</comment> + Preemption Model + (X) No Forced Preemption (Server) + (X) Voluntary Kernel Preemption (Desktop) </pre> <p> @@ -268,8 +286,8 @@ <note> If you select more than one framebuffer device, it may default to a less than optimal driver. Either use only one framebuffer device or specify which -to use by passing the driver to use to the kernel on boot such as -<c>video=radeonfb</c>. +to use by passing the driver to use to the kernel on boot by appending a video +line such as: <c>video=radeonfb</c>. </note> <p> @@ -285,7 +303,7 @@ <p> Now that your kernel is configured, it is time to compile and install it. Exit -the configuration and run the commands which will compile the kernel: +the configuration menu and run the following commands: </p> <pre caption="Compiling the kernel"> @@ -301,11 +319,11 @@ <p> Yaboot and BootX expect to use an uncompressed kernel unlike many other -bootloaders. The uncompressed kernel is called vmlinux and it is placed in -<path>/usr/src/linux</path> after the kernel has finished compiling. If you are +bootloaders. The uncompressed kernel is called vmlinux and it is placed in +<path>/usr/src/linux</path> after the kernel has finished compiling. If you are using a Pegasos machine, the Pegasos firmware requires a compressed kernel -called zImage.chrp which can be found in -<path>/usr/src/linux/arch/ppc/boot/images</path>. +called zImage which can be found in +<path>/usr/src/linux/arch/powerpc/boot/images</path>. </p> <pre caption="Installing the kernel"> @@ -314,7 +332,7 @@ <comment>(Apple/IBM)</comment> # <i>cp vmlinux /boot/<kernel-version></i> <comment>(Pegasos)</comment> -# <i>cp arch/ppc/boot/images/zImage.chrp /boot/<kernel-version></i> +# <i>cp arch/powerpc/boot/images/zImage /boot/<keyval id="kernel-name"/></i> </pre> <p> @@ -333,8 +351,8 @@ <p> You should list the modules you want automatically loaded in -<path>/etc/modules.autoload.d/kernel-2.6</path>. You can add extra options to -the modules too if you want. +<path>/etc/modules.autoload.d/kernel-2.6</path>. You can add extra options to +the modules if required. </p> <p> @@ -348,8 +366,8 @@ </pre> <p> -For instance, to automatically load the <c>3c59x.o</c> module, edit the -<path>kernel-2.6</path> file and enter the module name in it. +For instance, to automatically load the <c>3c59x</c> module, edit the +<path>kernel-2.6</path> file and add the module to it, one module on a line. </p> <pre caption="Editing /etc/modules.autoload.d/kernel-2.6"> @@ -410,10 +428,10 @@ <p> Before compiling your sources, the fstab needs a slight adjustment. The rest of -the fstab will be completed during a later step, so don't worry about the +the fstab will be completed during a later step, so don't worry about the details now. If you did not create a separate boot partition (NOT bootstrap, -that's different), remove the line referencing /boot from -<path>/etc/fstab</path>. This will need to be done on most Apple computers. +that's different), remove the line referencing <path>/boot</path> from +<path>/etc/fstab</path>. This will need to be done on most Apple computers. </p> <pre caption="Removing /boot from /etc/fstab on machines without a boot partition"> @@ -435,7 +453,7 @@ or ext3 as filesystem you might need to manually configure your kernel using <c>genkernel --menuconfig all</c> and add support for your filesystem <e>in</e> the kernel (i.e. <e>not</e> as a module). Users of EVMS2 or -LVM2 will probably want to add <c>--evms2</c> or <c>--lvm2</c> as arguments as +LVM2 will probably want to add <c>--evms2</c> or <c>--lvm2</c> as an argument as well. </p> @@ -451,7 +469,7 @@ Once <c>genkernel</c> completes, a kernel, full set of modules and <e>initial root disk</e> (initrd) will be created. We will use the kernel and initrd when configuring a boot loader later in this document. Write -down the names of the kernel and initrd as you will need it when writing +down the names of the kernel and initrd as you will need them when writing the bootloader configuration file. The initrd will be started immediately after booting to perform hardware autodetection (just like on the Installation CD) before your "real" system starts up. Be sure to also copy down the required @@ -468,6 +486,5 @@ </body> </section> - </sections> -- [email protected] mailing list
