diff options
Diffstat (limited to 'en')
| -rw-r--r-- | en/boot-installer/accessibility.xml | 6 | ||||
| -rw-r--r-- | en/boot-installer/boot-installer.xml | 2 | ||||
| -rw-r--r-- | en/boot-installer/powerpc.xml | 38 | ||||
| -rw-r--r-- | en/hardware/accessibility.xml | 2 | ||||
| -rw-r--r-- | en/hardware/hardware-supported.xml | 4 | ||||
| -rw-r--r-- | en/hardware/supported/powerpc.xml | 36 | ||||
| -rw-r--r-- | en/preparing/bios-setup/powerpc.xml | 224 | ||||
| -rw-r--r-- | en/using-d-i/components.xml | 1 | ||||
| -rw-r--r-- | en/using-d-i/modules/powerpc/grub-installer.xml | 13 |
9 files changed, 319 insertions, 7 deletions
diff --git a/en/boot-installer/accessibility.xml b/en/boot-installer/accessibility.xml index fcd833c64..976f4903a 100644 --- a/en/boot-installer/accessibility.xml +++ b/en/boot-installer/accessibility.xml @@ -7,7 +7,7 @@ Some users may need specific support because of e.g. some visual impairment. -<phrase arch="ia64;powerpc;x86">USB braille displays are detected +<phrase arch="ia64;powerpc;ppc64el;x86">USB braille displays are detected automatically (not serial displays connected via a serial-to-USB converter), but most other</phrase> <phrase arch="arm;hppa;mips;mipsel;sparc">Most</phrase> @@ -35,7 +35,7 @@ boxes. The choice can be made at the boot prompt, see the documentation for </para> </sect2> - <sect2 arch="ia64;powerpc;x86"> + <sect2 arch="ia64;powerpc;ppc64el;x86"> <title>USB Braille Displays</title> <para> @@ -51,7 +51,7 @@ url="&url-brltty-driver-help;"><classname>brltty</classname> website</ulink>. </para> </sect2> - <sect2 arch="ia64;powerpc;x86"> + <sect2 arch="ia64;powerpc;ppc64el;x86"> <title>Serial Braille Displays</title> <para> diff --git a/en/boot-installer/boot-installer.xml b/en/boot-installer/boot-installer.xml index f8a81078b..29e8e3a4a 100644 --- a/en/boot-installer/boot-installer.xml +++ b/en/boot-installer/boot-installer.xml @@ -5,7 +5,7 @@ <!-- Include only archs that are documented to avoid build-errors --> <!-- The arch="..." condition can be deleted when al archs are present --> - <sect1 arch="arm;any-x86;ia64;mips;mipsel;s390;powerpc;sparc"> + <sect1 arch="arm;any-x86;ia64;mips;mipsel;s390;powerpc;ppc64el;sparc"> <title>Booting the Installer on &arch-title;</title> <!-- This info is so architecture dependent, that I have turned the --> diff --git a/en/boot-installer/powerpc.xml b/en/boot-installer/powerpc.xml index 642a8d460..5351bf9f0 100644 --- a/en/boot-installer/powerpc.xml +++ b/en/boot-installer/powerpc.xml @@ -283,3 +283,41 @@ hardware, this changes to </para> </sect2> + + <sect2 arch="ppc64el"> <title>Booting a ppc64el machine</title> +<para> + +How to boot a ppc64el machine: + +</para> + + <sect3> <title>Petitboot</title> +<para> + +Petitboot is a platform independent bootloader based on the Linux kexec. +Petitboot supports loading kernel, initrd and device tree files from +any Linux mountable filesystem, plus can load files from the network +using the FTP, SFTP, TFTP, NFS, HTTP and HTTPS protocols. Petitboot can +boot any operating system that includes kexec boot support. + +</para><para> + +Petitboot looks for bootloader configuration files on mountable devices +in the system, and can also be configured to use boot information from a +DHCP server. + +</para> + </sect3> + +<!-- comment this out for now, since there is no content + <sect3> <title>Boot parameters</title> +<para> + Boot parameters for ppc64el + +FIXME: add some useful content here + +</para> + </sect3> +--> + + </sect2> diff --git a/en/hardware/accessibility.xml b/en/hardware/accessibility.xml index 9c218f669..428be96b2 100644 --- a/en/hardware/accessibility.xml +++ b/en/hardware/accessibility.xml @@ -1,7 +1,7 @@ <!-- retain these comments for translator revision tracking --> <!-- $Id$ --> - <sect2 id="braille-displays" arch="ia64;powerpc;x86"> + <sect2 id="braille-displays" arch="ia64;powerpc;ppc64el;x86"> <title>Braille Displays</title> <para> diff --git a/en/hardware/hardware-supported.xml b/en/hardware/hardware-supported.xml index 2e491e0ed..d1a2cf08d 100644 --- a/en/hardware/hardware-supported.xml +++ b/en/hardware/hardware-supported.xml @@ -134,9 +134,9 @@ variations of each architecture known as <quote>flavors</quote>. </row> <row> - <entry>IBM PowerPC (little endian)</entry> + <entry>Power Systems</entry> <entry>ppc64el</entry> - <entry></entry> + <entry>IBM POWER8 or newer machines</entry> <entry></entry> </row> diff --git a/en/hardware/supported/powerpc.xml b/en/hardware/supported/powerpc.xml index ebb0ad4d2..4b9ab56ad 100644 --- a/en/hardware/supported/powerpc.xml +++ b/en/hardware/supported/powerpc.xml @@ -444,3 +444,39 @@ which is Nubus, please see the section above). </sect3> </sect2> + + <sect2 arch="ppc64el"><title>CPU, Main Boards, and Video Support</title> +<!-- Section for ppc64el --> + + <sect3> <title>Machines</title> + +<itemizedlist> +<listitem><para> + +S822L + +</para></listitem> +<listitem><para> + +S821L + +</para></listitem> +<listitem><para> + +S822 + +</para></listitem> +<listitem><para> + +S821 + +</para></listitem> +<listitem><para> + +TYAN GN70-BP010 + +</para></listitem> +</itemizedlist> + + </sect3> + </sect2> diff --git a/en/preparing/bios-setup/powerpc.xml b/en/preparing/bios-setup/powerpc.xml index 01aac900e..a3824d046 100644 --- a/en/preparing/bios-setup/powerpc.xml +++ b/en/preparing/bios-setup/powerpc.xml @@ -50,3 +50,227 @@ installed to nvram. </para> </sect2> + + <sect2 arch="ppc64el;powerpc" id="update-firmware"> + <title>How to update bare metal ppc64el firmware</title> +<para> + +This is an excerpt from +<ulink url="&url-ibm-powerkvm;">IBM PowerKVM on IBM POWER8</ulink> + +</para><para> + +Open Power Abstraction Layer (OPAL) is the system firmware in the stack +of POWER processor-based server. + +</para><para> + +There may be instances when the user might have to upgrade the Power +Systems firmware to a more recent level to acquire new features or +additional support for devices. + +</para><para> + +Make sure that the following requirements are met: + +<itemizedlist> +<listitem><para> + an OS to be running on the system; +</para></listitem><listitem><para> + the .img file of the OPAL level that the user needs to update to; +</para></listitem><listitem><para> + the machine isn't under HMC control. +</para></listitem> +</itemizedlist> +</para><para> + +Power Systems has two sides of flash to boot firmware from, namely +permanent and temporary. This provides a way to test firmware updates on +the temporary side of the flash before committing the tested changes to +the permanent side, thereby committing the new updates. + +</para><para> + +Perform the following steps for the update: + +<orderedlist> +<listitem><para> + Save the level of the existing firmware before really updating. In + ASM, in the system menu, click <command>Service Aids ??? Service Processor + Command Line</command>, and run the following command: +<informalexample><screen> + cupdcmd -f +</screen></informalexample> +</para></listitem><listitem><para> + Download the .img file of the level of firmware to be updated to a + location in the host filesystem. Refer to IBM Fix Central for downloading + the image file. +</para><para> + Verify the image downloaded by running the following command and + save the output. +<informalexample><screen> + $update_flash -v -f <file_name.img> +</screen></informalexample> +</para></listitem> +<listitem><para> + Update the firmware by running the following command. +<informalexample><screen> + $update_flash -f <file_name.img> +</screen></informalexample> +</para> + +<note><para> + + <itemizedlist> + <listitem><para> + The command reboots the system and therefore, sessions if any, + would be lost. + </para></listitem><listitem><para> + Do not reboot or switch off the system until it is back. + </para></listitem> + </itemizedlist> + +</para></note> + +</listitem><listitem><para> + Verify the updated firmware level of the temporary side of the flash + as in step 1. +</para></listitem><listitem><para> + In case the update has to be reverted, the user can do so by running + this command: +<informalexample><screen> + $update_flash -r +</screen></informalexample> + Rejection would reject only the temporary side of the flash. + Therefore, the new level should be committed to the permanent side only + after thorough testing of the new firmware. +</para><para> + The new updated level can be committed to the permanent side of the + flash by running the following command. +<informalexample><screen> + $update_flash -c +</screen></informalexample> +</para></listitem> +</orderedlist> + +</para> + </sect2> + + <sect2 arch="ppc64el;powerpc"> + <title>Updating KVM guest firmware (SLOF)</title> +<para> + +Slimline Open Firmware (SLOF) is an implementation of the IEEE 1275 +standard. +It can be used as partition firmware for pSeries machines running on +QEMU or KVM. + +</para><para> + +The package qemu-slof is, in fact, a dependency of package +qemu-system-ppc (which also provides the virtual package +qemu-system-ppc64), and can be installed or updated via +<command>apt-get</command> tool on Debian-based distros. +Like so: + +<informalexample><screen> +# apt-get install qemu-slof +</screen></informalexample> + +SLOF can also be installed into rpm-based distribution systems, given +the proper repository or rpm package. Additionally, the upstream source +code is available at http://github.com/leilihh/SLOF. + +</para><para> + +Thus, one can use a different SLOF file rather than the default, when +running <command>qemu-system</command>, by adding the command line +argument <userinput>-bios <slof_file> </userinput> when starting +qemu. + +</para> + </sect2> + + <sect2 arch="ppc64el"> <title>Updating PowerKVM hypervisor</title> + <sect3 arch="ppc64el"> <title>Instructions for Netboot installation</title> +<para> + +You will need a DHCP/TFTP (BOOTP) server, as well as a web server. +After downloading ibm-powerkvm-*-ppc64-service-*.iso, mount loop it and +unpack it into some directory within your HTTP server www root +structure (say wwwroot): + +<informalexample><screen> +# cd <directory-where-the-iso-is> +# mkdir ./iso +# sudo mount -o loop ibm-powerkvm-*-ppc64-service-*.iso ./iso +# cp -a ./iso/* <path-to-wwwroot> +</screen></informalexample> + +Create the petitboot.conf file in a directory under your tftproot, say +/tftproot/powerkvm, with the following contents: + +<informalexample><screen> +label PowerKVM Automated Install +kernel http://YOUR-SERVER-IP/SOME-PATH-TO-wwwroot/ppc/ppc64/vmlinuz +initrd http://YOUR-SERVER-IP/SOME-PATH-TO-wwwroot/ppc/ppc64/initrd.img +append root=live:http://YOUR-SERVER-IP/SOME-PATH-TO-wwwroot/LiveOS/squashfs.img repo=http://YOUR-SERVER-IP/SOME-PATH-TO-wwwroot/packages rd.dm=0 rd.md=0 console=hvc0 console=tty0 +</screen></informalexample> + +Editing your dhcpd.conf, set this directive at the beginning: + +<informalexample><screen> +option conf-file code 209 = text; +</screen></informalexample> + +Add the system directive: + +<informalexample><screen> +host <your-system> { + hardware ethernet <system macaddr> + fixed-address <system ip>; + option host-name "<system hostname>"; + option conf-file "<powerkvm/petitboot.conf>"; + } +</screen></informalexample> + +Reboot the dhcp server. + +</para><para> + +Boot your PowerLinux machine. + +</para><para> + +There should be the following option at petitboot (select it): + +<informalexample><screen> +"Power KVM Automated Install" +</screen></informalexample> + +The installer menu should appear automatically. + +</para> + </sect3> + + <sect3 arch="ppc64el"> <title>Instructions for DVD</title> +<para> +Boot the ISO ibm-powerkvm-*-ppc64-service-*.iso (either burn a DVD or +make it virtual if using QEMU) and simply wait for the boot. +</para><para> +There should be the following option at petitboot (select it): +<informalexample><screen> +"POWERKVM_LIVECD" +</screen></informalexample> +The installer menu should appear automatically. +</para> + </sect3> + </sect2> + +<!-- commented out for now, since there is no content + <sect2 arch="ppc64el"> <title>Updating PowerVM hypervisor</title> +<para> +FIXME: add some useful content here +</para> + </sect2> +--> diff --git a/en/using-d-i/components.xml b/en/using-d-i/components.xml index 4420a01da..297341745 100644 --- a/en/using-d-i/components.xml +++ b/en/using-d-i/components.xml @@ -153,6 +153,7 @@ linkend="boot-dev-select-sun"/>.</phrase> &module-mipsel-colo-installer.xml; &module-powerpc-yaboot-installer.xml; &module-powerpc-quik-installer.xml; +&module-powerpc-grub-installer.xml; &module-s390-zipl-installer.xml; &module-sparc-silo-installer.xml; &module-arm-flash-kernel-installer.xml; diff --git a/en/using-d-i/modules/powerpc/grub-installer.xml b/en/using-d-i/modules/powerpc/grub-installer.xml new file mode 100644 index 000000000..5cbc92632 --- /dev/null +++ b/en/using-d-i/modules/powerpc/grub-installer.xml @@ -0,0 +1,13 @@ + <sect3 arch="ppc64el"> + <title>Install <command>GRUB2</command> on a Hard Disk</title> +<para> + +The boot loader for ppc64el machines is +<command>GRUB2</command>. + +<!-- +FIXME: add some useful content here +--> + +</para> + </sect3> |