This is Gentoo's testing wiki. It is a non-operational environment and its textual content is outdated.
Please visit our production wiki at https://wiki.gentoo.org
Handbook:PPC/Installation/Media
Hardware requirements
Before we start, we first list what hardware requirements are needed to successfully install Gentoo on a ppc box.
| System overview | |
|---|---|
| Apple NewWorld Machines | Power/PowerPC microprocessors (G3, G4, G5) such as iMac, eMac, iBook PowerBook, Xserver, PowerMac |
| Apple OldWorld machines | Apple Machines with an Open Firmware revision less than 3, such as the Beige G3s, PCI PowerMacs and PCI PowerBooks. PCI-based Apple Clones should also be supported. |
| Genesi | Pegasos I/II, Open Desktop Workstation, Efika |
| IBM | RS/6000, iSeries, pSeries |
| Requirements | |
| Memory | At least 64 MB |
| Diskspace | 1.5 GB (excluding swap space) |
| Swap space | At least 256 MB |
Be sure to read the Gentoo PPC FAQ for help with some common installation related issues or to know just what's in that PowerPC machine.
Media instalacyjne Gentoo Linux
Minimal installation CD
As of August 23, 2018 the official Minimal CDs are capable of booting in UEFI mode. Previous versions boot in BIOS (MBR) mode only. Readers looking to make their system UEFI bootable must download the latest ISO.
The Gentoo minimal installation CD is a bootable image which contains a self-sustained Gentoo environment. It allows the user to boot Linux from the CD or other installation media. During the boot process the hardware is detected and the appropriate drivers are loaded. The image is maintained by Gentoo developers and allows anyone to install Gentoo if an active Internet connection is available.
The Minimal Installation CD is called install-ppc-minimal-<release>.iso.
The occasional Gentoo LiveDVD
Occasionally, a special DVD is crafted by the Gentoo Ten project which can be used to install Gentoo. The instructions further down this chapter target the Minimal Installation CD so might be a bit different. However, the LiveDVD (or any other bootable Linux environment) supports getting a root prompt by just invoking sudo su - or sudo -i in a terminal.
What are stages then?
A stage3 tarball is an archive containing a minimal Gentoo environment, suitable to continue the Gentoo installation using the instructions in this manual. Previously, the Gentoo Handbook described the installation using one of three stage tarballs. While Gentoo still offers stage1 and stage2 tarballs, the official installation method uses the stage3 tarball. If you are interested in performing a Gentoo installation using a stage1 or stage2 tarball, please read the Gentoo FAQ on How do I install Gentoo using a stage1 or stage2 tarball?
Stage3 tarballs can be downloaded from releases/ppc/autobuilds/ on any of the official Gentoo mirrors. Stage files update frequently and are not included on the installation images.
Downloading
Obtain the media
The default installation media that Gentoo Linux uses are the minimal installation CDs, which host a bootable, very small Gentoo Linux environment. This environment contains all the right tools to install Gentoo. The CD images themselves can be downloaded from the downloads page (recommended) or by manually browsing to the ISO location on one of the many available mirrors.
If downloading from a mirror, the minimal installation CDs can be found as follows:
- Go to the releases/ directory.
- Select the directory for the relevant target architecture (such as ppc/).
- Select the autobuilds/ directory.
- For amd64 and x86 architectures select either the current-install-amd64-minimal/ or current-install-x86-minimal/ directory (respectively). For all other architectures navigate to the current-iso/ directory.
Some target architectures such as arm, mips, and s390 will not have minimal install CDs. At this time the Gentoo Release Engineering project does not support building .iso files for these targets.
Inside this location, the installation media file is the file with the .iso suffix. For instance, take a look at the following listing:
[DIR] hardened/ 05-Dec-2014 01:42 - [ ] install-ppc-minimal-20141204.iso 04-Dec-2014 21:04 208M [ ] install-ppc-minimal-20141204.iso.CONTENTS 04-Dec-2014 21:04 3.0K [ ] install-ppc-minimal-20141204.iso.DIGESTS 04-Dec-2014 21:04 740 [TXT] install-ppc-minimal-20141204.iso.DIGESTS.asc 05-Dec-2014 01:42 1.6K [ ] stage3-ppc-20141204.tar.bz2 04-Dec-2014 21:04 198M [ ] stage3-ppc-20141204.tar.bz2.CONTENTS 04-Dec-2014 21:04 4.6M [ ] stage3-ppc-20141204.tar.bz2.DIGESTS 04-Dec-2014 21:04 720 [TXT] stage3-ppc-20141204.tar.bz2.DIGESTS.asc 05-Dec-2014 01:42 1.5K
In the above example, the install-ppc-minimal-20141204.iso file is the minimal installation CD itself. But as can be seen, other related files exist as well:
- A .CONTENTS file which is a text file listing all files available on the installation media. This file can be useful to verify if particular firmware or drivers are available on the installation media before downloading it.
- A .DIGESTS file which contains the hash of the ISO file itself, in various hashing formats/algorithms. This file can be used to verify if the downloaded ISO file is corrupt or not.
- A .DIGESTS.asc file which not only contains the hash of the ISO file (like the .DIGESTS file), but also a cryptographic signature of that file. This can be used to both verify if the downloaded ISO file is corrupt or not, as well as verify that the download is indeed provided by the Gentoo Release Engineering team and has not been tampered with.
Ignore the other files available at this location for now - those will come back when the installation has proceeded further. Download the .iso file and, if verification of the download is wanted, download the .DIGESTS.asc file for the .iso file as well. The .CONTENTS file does not need to be downloaded as the installation instructions will not refer to this file anymore, and the .DIGESTS file should contain the same information as the .DIGESTS.asc file, except that the latter also contains a signature on top of it.
Verifying the downloaded files
This is an optional step and not necessary to install Gentoo Linux. However, it is recommended as it ensures that the downloaded file is not corrupt and has indeed been provided by the Gentoo Infrastructure team.
Through the .DIGESTS and .DIGESTS.asc files, the validity of the ISO file can be confirmed using the right set of tools. This verification is usually done in two steps:
- First, the cryptographic signature is validated to make sure that the installation file is provided by the Gentoo Release Engineering team
- If the cryptographic signature validates, then the checksum is verified to make sure that the downloaded file itself is not corrupted
Microsoft Windows based verification
On a Microsoft Windows system, chances are low that the right set of tools to verify checksums and cryptographic signatures are in place.
To first verify the cryptographic signature, tools such as GPG4Win can be used. After installation, the public keys of the Gentoo Release Engineering team need to be imported. The list of keys is available on the signatures page. Once imported, the user can then verify the signature of the .DIGESTS.asc file.
This does not verify that the .DIGESTS file is correct, only that the .DIGESTS.asc file is. That also implies that the checksum should be verified against the values in the .DIGESTS.asc file, which is why the instructions above only refer to downloading the .DIGESTS.asc file.
The checksum itself can be verified using the Hashcalc application, although many others exist as well. Most of the time, these tools will show the user the calculated checksum, and the user is requested to verify this checksum with the value that is inside the .DIGESTS.asc file.
Linux based verification
On a Linux system, the most common method for verifying the cryptographic signature is to use the app-crypt/gnupg software. With this package installed, the following commands can be used to verify the cryptographic signature of the .DIGESTS.asc file.
First, download the right set of keys as made available on the signatures page:
user $gpg --keyserver hkp://keys.gnupg.net --recv-keys 0xBB572E0E2D182910gpg: requesting key 0xBB572E0E2D182910 from hkp server pool.sks-keyservers.net gpg: key 0xBB572E0E2D182910: "Gentoo Linux Release Engineering (Automated Weekly Release Key) <releng@gentoo.org>" 1 new signature gpg: 3 marginal(s) needed, 1 complete(s) needed, classic trust model gpg: depth: 0 valid: 3 signed: 20 trust: 0-, 0q, 0n, 0m, 0f, 3u gpg: depth: 1 valid: 20 signed: 12 trust: 9-, 0q, 0n, 9m, 2f, 0u gpg: next trustdb check due at 2018-09-15 gpg: Total number processed: 1 gpg: new signatures: 1
Next verify the cryptographic signature of the .DIGESTS.asc file:
user $gpg --verify install-ppc-minimal-20141204.iso.DIGESTS.ascgpg: Signature made Fri 05 Dec 2014 02:42:44 AM CET gpg: using RSA key 0xBB572E0E2D182910 gpg: Good signature from "Gentoo Linux Release Engineering (Automated Weekly Release Key) <releng@gentoo.org>" [unknown] gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: 13EB BDBE DE7A 1277 5DFD B1BA BB57 2E0E 2D18 2910
To be absolutely certain that everything is valid, verify the fingerprint shown with the fingerprint on the Gentoo signatures page.
With the cryptographic signature validated, next verify the checksum to make sure the downloaded ISO file is not corrupted. The .DIGESTS.asc file contains multiple hashing algorithms, so one of the methods to validate the right one is to first look at the checksum registered in the .DIGESTS.asc file. For instance, to get the SHA512 checksum:
user $grep -A 1 -i sha512 install-ppc-minimal-20141204.iso.DIGESTS.asc# SHA512 HASH 364d32c4f8420605f8a9fa3a0fc55864d5b0d1af11aa62b7a4d4699a427e5144b2d918225dfb7c5dec8d3f0fe2cddb7cc306da6f0cef4f01abec33eec74f3024 install-ppc-minimal-20141204.iso -- # SHA512 HASH 0719a8954dc7432750de2e3076c8b843a2c79f5e60defe43fcca8c32ab26681dfb9898b102e211174a895ff4c8c41ddd9e9a00ad6434d36c68d74bd02f19b57f install-ppc-minimal-20141204.iso.CONTENTS
In the above output, two SHA512 checksums are shown - one for the install-ppc-minimal-20141204.iso file and one for its accompanying .CONTENTS file. Only the first checksum is of interest, as it needs to be compared with the calculated SHA512 checksum which can be generated as follows:
user $sha512sum install-ppc-minimal-20141204.iso364d32c4f8420605f8a9fa3a0fc55864d5b0d1af11aa62b7a4d4699a427e5144b2d918225dfb7c5dec8d3f0fe2cddb7cc306da6f0cef4f01abec33eec74f3024 install-ppc-minimal-20141204.iso
As both checksums match, the file is not corrupted and the installation can continue.
Burning a disk
Of course, with just an ISO file downloaded, the Gentoo Linux installation cannot be started. The ISO file needs to be burned on a CD to boot from, and in such a way that its content is burned on the CD, not just the file itself. Below a few common methods are described - a more elaborate set of instructions can be found in Our FAQ on burning an ISO file.
Burning with Microsoft Windows
On Microsoft Windows, a number of tools exist that support burning ISOs on CDs.
- With EasyCD Creator, select File, Record CD from CD image. Then change the Files of type to ISO image file. Then locate the ISO file and click Open. After clicking on Start recording the ISO image will be burned correctly onto the CD-R.
- With Nero Burning ROM, cancel the wizard which automatically pops up and select Burn Image from the File menu. Select the image to burn and click Open. Now hit the Burn button and watch the brand new CD being burnt.
Burning with Linux
On Linux, the ISO file can be burned on a CD using the cdrecord command, part of the app-cdr/cdrtools package.
For instance, to burn the ISO file on the CD in the /dev/sr0 device (this is the first CD device on the system - substitute with the right device file if necessary):
user $cdrecord dev=/dev/sr0 install-ppc-minimal-20141204.isoUsers that prefer a graphical user interface can use K3B, part of the kde-apps/k3b package. In K3B, go to Tools and use Burn CD Image. Then follow the instructions provided by K3B.
Booting
Default: Booting the installation CD with yaboot
On NewWorld machines place the Installation CD in the CD-ROM and reboot the system. When the system-start-bell sounds, simply hold down the C until the CD loads.
After the installation CD loaded, a boot prompt will show up at the bottom of the screen.
We provide one generic kernel, ppc32. This kernel is built with support for multiple CPUs, but it will boot on single processor machines as well.
It is possible to tweak some kernel options at this prompt. The following table lists some of the available boot options you can add:
| Boot Option | Description |
|---|---|
| video | This option takes one of the following vendor-specific tags: nvidiafb, radeonfb, rivafb, atyfb, aty128 or ofonly. Follow this tag with the resolution refresh rate and color depth to use. For instance, video=radeonfb:1280x1024@75-32 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. When uncertain about what to choose, and the default doesn't work, video=ofonly will most certainly work. |
| nol3 | Disables level 3 cache on some PowerBooks (needed for at least the 17") |
| dofirewire | Enables support for IEEE1394 (FireWire) devices, like external harddisks. |
| dopcmcia | To use PCMCIA devices during the installation (like PCMCIA network cards) this options needs to be enabled. |
| dosshd | Starts sshd. Useful for unattended installs. |
| passwd=foo | Sets whatever is after the = as the root password. Use with dosshd for remote installs. |
To use the above options, at the boot prompt, type ppc32 followed by the desired option. In the example below, we'll force the kernel to use the Open Firmware framebuffer instead of the device specific driver.
boot:ppc32 video=ofonlyIf no options are needed, just type ppc32 at this prompt, and a complete Gentoo Linux environment will be loaded from the CD.
Alternative: Booting the installation CD on a Pegasos system
On the Pegasos simply insert the CD and at the SmartFirmware boot-prompt type cd /boot/menu.
bootcd /boot/menuThis will open a small bootmenu that allows users to choose between several preconfigured video configs. Any special boot options can be appended to the command-line just like with Yaboot above. For example:
bootcd /boot/pegasos video=radeonfb:1280x1024@75 mem=256MThe default kernel options (in case something goes wrong) are preconfigured with console=ttyS0,115200 console=tty0 init=/linuxrc looptype=squashfs loop=/image.squashfs cdroot root=/dev/ram0.
Alternative: Booting the installation CD with BootX
With an OldWorld Mac the bootable portion of the livecd can't be used. The most simple solution is to use MacOS 9 or earlier to bootstrap into a Linux environment with a tool called BootX.
First, download BootX and unpack the archive. Copy the the BootX Extension from the unpacked archive into Extensions Folder and the BootX App Control Panel into Control Panels, both of which are located in the MacOS System Folder. Next, create a folder called "Linux Kernels" in the System folder and copy the ppc32 kernel from the CD to this folder. Finally, copy ppc32.igz from the Installation CD boot folder into the MacOS System Folder.
To prepare BootX, start the BootX App Control Panel. First select the Options dialog and check Use Specified RAM Disk and select ppc32.igz from the System Folder. Continue back to the initial screen and ensure that the ramdisk size is at least 32000. Finally, set the kernel arguments as shown below:
'"`UNIQ--pre-00000005-QINU`"'
This is a deprecated template. Help us update this template!
The kernel parameters in the yaboot section above are also applicable here. Append any of those options to the kernel arguments above.
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. If everything goes correctly, it should boot into the Installation CD.
Setting the keyboard map
After boot, a root ("#") prompt appears on the current console. It is possible to switch to other consoles by pressing Alt + F2, Alt + F3 and Alt + F4. Get back to the first one by pressing Alt + F1. Due to the keyboard layout, it may be necessary to press Alt + fn + F# on Apple machines.
When installing Gentoo on a system with a non-US keyboard, use loadkeys to load the keymap for the keyboard. To list the available keymaps, execute ls /usr/share/keymaps/i386.
root #ls /usr/share/keymaps/i386Now load the keymap of choice:
root #loadkeys be-latin1
Extra hardware configuration
When the Installation medium boots, it tries to detect all the hardware devices and loads the appropriate kernel modules to support the hardware. In the vast majority of cases, it does a very good job. However, in some cases it may not auto-load the kernel modules needed by the system. If the PCI auto-detection missed some of the system's hardware, the appropriate kernel modules have to be loaded manually.
In the next example the 8139too module (which supports certain kinds of network interfaces) is loaded:
root #modprobe 8139tooOptional: User accounts
If other people need access to the installation environment, or there is need to run commands as a non-root user on the installation medium (such as to chat using irssi without root privileges for security reasons), then an additional user account needs to be created and the root password set to a strong password.
To change the root password, use the passwd utility:
root #passwdNew password: (Enter the new password) Re-enter password: (Re-enter the password)
To create a user account, first enter their credentials, followed by the account's password. The useradd and passwd commands are used for these tasks.
In the next example, a user called john is created:
root #useradd -m -G users john
root #passwd johnNew password: (Enter john's password) Re-enter password: (Re-enter john's password)
To switch from the (current) root user to the newly created user account, use the su command:
root #su - johnOptional: Viewing documentation while installing
TTYs
To view the Gentoo handbook during the installation, first create a user account as described above. Then press Alt+F2 to go to a new terminal.
During the installation, the links command can be used to browse the Gentoo handbook - of course only from the moment that the Internet connection is working.
user $links https://wiki.gentoo.org/wiki/Handbook:PPCTo go back to the original terminal, press Alt+F1.
GNU Screen
The GNU Screen utility is installed by default on official Gentoo installation media. It may be more efficient for the seasoned Linux enthusiast to use screen to view installation instructions via split panes rather than the multiple TTY method mentioned above.
Optional: Starting the SSH daemon
To allow other users to access the system during the installation (perhaps to support during an installation, or even do it remotely), a user account needs to be created (as was documented earlier on) and the SSH daemon needs to be started.
To fire up the SSH daemon on an OpenRC init, execute the following command:
root #rc-service sshd startIf users log on to the system, they will see a message that the host key for this system needs to be confirmed (through what is called a fingerprint). This behavior is typical and can be expected for initial connections to an SSH server. However, later when the system is set up and someone logs on to the newly created system, the SSH client will warn that the host key has been changed. This is because the user now logs on to - for SSH - a different server (namely the freshly installed Gentoo system rather than the live environment that the installation is currently using). Follow the instructions given on the screen then to replace the host key on the client system.
To be able to use sshd, the network needs to function properly. Continue with the chapter on Configuring the network.