diff options
| author | Holger Wansing <hwansing@mailbox.org> | 2022-05-20 00:02:26 +0200 |
|---|---|---|
| committer | Holger Wansing <hwansing@mailbox.org> | 2022-05-20 00:02:26 +0200 |
| commit | c88fe18c8e799ebd957509a416683baecd537caa (patch) | |
| tree | f1bfedec4c1f616003b002b47f27311b962130b4 /en | |
| parent | cf31af36a58834f1dc445c72d7e30ad2614172e3 (diff) | |
| download | installation-guide-c88fe18c8e799ebd957509a416683baecd537caa.zip | |
Clean-up of outdated/no longer used content (remove docs for non-release archs)
Diffstat (limited to 'en')
57 files changed, 115 insertions, 2123 deletions
diff --git a/en/appendix/chroot-install.xml b/en/appendix/chroot-install.xml index a337c94cc..a7eb83d28 100644 --- a/en/appendix/chroot-install.xml +++ b/en/appendix/chroot-install.xml @@ -571,7 +571,10 @@ Note that this assumes that a <filename>/dev/sda</filename> device file has been created. There are alternative methods to install <command>grub2</command>, but those are outside the scope of this appendix. -</para><para arch="powerpc"> +</para> + +<!-- +<para arch="powerpc"> Check <userinput>man yaboot.conf</userinput> for instructions on setting up the bootloader. If you are keeping the system you used to @@ -600,6 +603,8 @@ On some machines, you may need to use <userinput>ide0:</userinput> instead of <userinput>hd:</userinput>. </para> +--> + </sect2> <sect2> diff --git a/en/appendix/files.xml b/en/appendix/files.xml index 248e1f8d2..63b44735c 100644 --- a/en/appendix/files.xml +++ b/en/appendix/files.xml @@ -140,8 +140,11 @@ To load a mouse driver module, you can use the <command>modconf</command> command (from the package with the same name) and look in the category <userinput>kernel/drivers/input/mouse</userinput>. -</para><para arch="powerpc"> -<!-- FJP 20070122: Unsure if this is still valid --> +</para> + +<!-- +<para arch="powerpc"> +### FJP 20070122: Unsure if this is still valid ### Modern kernels give you the capability to emulate a three-button mouse when your mouse only has one button. Just add the following lines to @@ -159,6 +162,8 @@ when your mouse only has one button. Just add the following lines to </screen></informalexample> </para> +--> + </sect2> </sect1> diff --git a/en/boot-installer/accessibility.xml b/en/boot-installer/accessibility.xml index 13c332da5..9fe810d76 100644 --- a/en/boot-installer/accessibility.xml +++ b/en/boot-installer/accessibility.xml @@ -7,10 +7,10 @@ Some users may need specific support because of e.g. some visual impairment. -<phrase arch="ia64;powerpc;ppc64el;x86">USB braille displays are detected +<phrase arch="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;mips64el;sparc">Most</phrase> +<phrase arch="arm;mipsel;mips64el">Most</phrase> accessibility features have to be enabled manually. <phrase arch="x86">On machines that support it, the boot menu emits beeps when it is ready to receive keystrokes. It beeps once on BIOS systems, @@ -56,7 +56,7 @@ selection of choices has to be made (e.g. during task selection), one can type </para> </sect2> - <sect2 arch="ia64;powerpc;ppc64el;x86"> + <sect2 arch="ppc64el;x86"> <title>USB Braille Displays</title> <para> @@ -72,7 +72,7 @@ url="&url-brltty-driver-help;"><classname>brltty</classname> website</ulink>. </para> </sect2> - <sect2 arch="ia64;powerpc;ppc64el;x86"> + <sect2 arch="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 aaf704786..e3dd9fd65 100644 --- a/en/boot-installer/boot-installer.xml +++ b/en/boot-installer/boot-installer.xml @@ -5,14 +5,13 @@ <!-- 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;mips64el;s390;powerpc;ppc64el;sparc"> + <sect1 arch="arm;any-x86;mipsel;mips64el;s390;ppc64el"> <title>Booting the Installer on &arch-title;</title> <!-- This info is so architecture dependent, that I have turned the --> <!-- structure inside out for this chapter. Each arch has a document. --> -<!-- Note: arch hppa is currently missing --> -<warning arch="any-x86;powerpc"><para> +<warning arch="any-x86"><para> If you have any other operating systems on your system that you wish to keep (dual boot setup), you should make sure that they have been properly @@ -31,13 +30,9 @@ For information on how to boot the graphical installer, see </para></note> &boot-installer-arm.xml; -<!-- &boot-installer-hppa.xml; --> &boot-installer-x86.xml; -&boot-installer-ia64.xml; -&boot-installer-mips.xml; &boot-installer-s390.xml; &boot-installer-powerpc.xml; -&boot-installer-sparc.xml; &boot-installer-graphical.xml; </sect1> diff --git a/en/boot-installer/graphical.xml b/en/boot-installer/graphical.xml index dd4e65b8e..2d0987c42 100644 --- a/en/boot-installer/graphical.xml +++ b/en/boot-installer/graphical.xml @@ -44,7 +44,10 @@ Look for <filename>netboot/gtk/mini.iso</filename>. </footnote>, which is mainly useful for testing. -</para><para arch="powerpc"> +</para> + +<!-- +<para arch="powerpc"> For &arch-title;, currently only an experimental <quote>mini</quote> ISO image is available<footnote id="gtk-miniiso-powerpc"> @@ -58,7 +61,10 @@ Look for <filename>netboot/gtk/mini.iso</filename>. </footnote>. It should work on almost all PowerPC systems that have an ATI graphical card, but is unlikely to work on other systems. -</para><para> +</para> +--> + +<para> Just as with the text-based installer it is possible to add boot parameters when starting the graphical installer. diff --git a/en/boot-installer/hppa.xml b/en/boot-installer/hppa.xml deleted file mode 100644 index 3bf892313..000000000 --- a/en/boot-installer/hppa.xml +++ /dev/null @@ -1,12 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- $Id$ --> - - <sect2 arch="hppa"> - <title></title> -<para> - -<!-- Placeholder document; please write and include in - boot-installer.xml and build/templates/docstruct.ent --> - -</para> - </sect2> diff --git a/en/boot-installer/ia64.xml b/en/boot-installer/ia64.xml deleted file mode 100644 index 30be38d30..000000000 --- a/en/boot-installer/ia64.xml +++ /dev/null @@ -1,464 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- $Id$ --> - - <sect2 arch="ia64"><title>Booting from a CD-ROM</title> - -&boot-installer-intro-cd.xml; - - <note> - <title>CD Contents</title> - -<para> - -There are three basic variations of &debian; Install CDs. -The <emphasis>Business Card</emphasis> CD has a minimal installation -that will fit on the small form factor CD media. -It requires a network connection in order to install the rest of the -base installation and make a usable system. -The <emphasis>Network Install</emphasis> CD has all of the packages -for a base install but requires a network connection to a &debian; -mirror site in order to install the -extra packages one would want for a complete system . -The set of &debian; CDs can install a complete system from the wide -range of packages without needing access to the network. -</para> - </note> - -<para> - -The IA-64 architecture uses the next generation Extensible Firmware Interface -(EFI) from Intel. -Unlike the traditional x86 BIOS which knows little about the boot -device other than the partition table and Master Boot Record (MBR), -EFI can read and write files from FAT16 or FAT32 formatted disk -partitions. -This simplifies the often arcane process of starting a system. -The system boot loader and the EFI firmware that supports it have -a full filesystem to store the files necessary for booting the -machine. -This means that the system disk on an IA-64 system has an additional -disk partition dedicated to EFI instead of the simple MBR or boot -block on more conventional systems. - -</para><para> - -The &debian; Installer CD contains a small EFI partition where the -<command>ELILO</command> bootloader, its configuration file, the installer's -kernel, and initial filesystem (initrd) are located. -The running system also contains an EFI partition where the necessary -files for booting the system reside. -These files are readable from the EFI Shell as described below. - -</para><para> - -Most of the details of how <command>ELILO</command> actually loads and -starts a system are transparent to the system installer. -However, the installer must set up an EFI partition prior to installing -the base system. Otherwise, the installation of <command>ELILO</command> -will fail, rendering the system un-bootable. -The EFI partition is allocated and formatted in the partitioning step -of the installation prior to loading any packages on the system disk. -The partitioning task also verifies that a suitable EFI partition is -present before allowing the installation to proceed. - -</para><para> - -The EFI Boot Manager is presented as the last step of the firmware -initialization. -It displays a menu list from which the user can select -an option. -Depending on the model of system and what other software has been -loaded on the system, this menu may be different from one system -to another. -There should be at least two menu items displayed, -<command>Boot Option Maintenance Menu</command> and -<command>EFI Shell (Built-in)</command>. -Using the first option is preferred, however, if that -option is not available or the CD for some reason does not -boot with it, use the second option. - -</para> - - <warning> - <title>IMPORTANT</title> -<para> -The EFI Boot Manager will select a default boot action, typically -the first menu choice, within a pre-set number of seconds. -This is indicated by a countdown at the bottom of the screen. -Once the timer expires and the systems starts the default action, -you may have to reboot the machine in order to continue the installation. -If the default action is the EFI Shell, you can return to the Boot Manager -by running <command>exit</command> at the shell prompt. -</para> - </warning> - - <sect3 arch="ia64" id="bootable-cd"> - <title>Option 1: Booting from the Boot Option Maintenance Menu</title> -<para> - -</para> - -<itemizedlist> - -<listitem><para> -Insert the CD in the DVD/CD drive and reboot the machine. -The firmware will display the EFI Boot Manager page and menu after -it completes its system initialization. -</para></listitem> - -<listitem><para> -Select <command>Boot Maintenance Menu</command> from the menu -with the arrow keys and press <command>ENTER</command>. -This will display a new menu. -</para></listitem> - -<listitem><para> -Select <command>Boot From a File</command> from the menu -with the arrow keys and press <command>ENTER</command>. -This will display a list of devices probed by the firmware. -You should see two menu lines containing either the label -<command>Debian Inst [Acpi ...</command> or -<command>Removable Media Boot</command>. -If you examine the rest of the menu line, you will notice that -the device and controller information should be the same. -</para></listitem> - -<listitem><para> -You can choose either of the entries that refer to the CD/DVD -drive. -Select your choice with the arrow keys and press <command>ENTER</command>. -If you choose <command>Removable Media Boot</command> the machine -will immediately start the boot load sequence. -If you choose <command>Debian Inst [Acpi ...</command> instead, it -will display a directory listing of the bootable portion of the -CD, requiring you to proceed to the next (additional) step. -</para></listitem> - -<listitem><para> -You will only need this step if you chose -<command>Debian Inst [Acpi ...</command>. -The directory listing will also show -<command>[Treat like Removable Media Boot]</command> on the next to -the last line. -Select this line with the arrow keys and press <command>ENTER</command>. -This will start the boot load sequence. -</para></listitem> - -</itemizedlist> - -<para> - -These steps start the &debian; boot loader which will display a -menu page for you to select a boot kernel and options. -Proceed to selecting the boot kernel and options. - -</para> - </sect3> - - <sect3 arch="ia64" id="boot-with-efi"> - <title>Option 2: Booting from the EFI Shell</title> -<para> - -If, for some reason, option 1 is not successful, reboot the machine -and when the EFI Boot Manager screen appears there should be -one option called <command>EFI Shell [Built-in]</command>. -Boot the &debian; Installer CD with the following steps: - -</para> - -<itemizedlist> - -<listitem><para> -Insert the CD in the DVD/CD drive and reboot the machine. -The firmware will display the EFI Boot Manager page and menu after -it completes system initialization. -</para></listitem> - -<listitem><para> -Select <command>EFI Shell</command> from the menu with the arrow keys -and press <command>ENTER</command>. -The EFI Shell will scan all of the bootable devices and display -them to the console before displaying its command prompt. -The recognized bootable partitions on devices will show a device name of -<filename>fs<replaceable>n</replaceable>:</filename>. -All other recognized partitions will be named -<filename>blk<replaceable>n</replaceable>:</filename>. -If you inserted the CD just before entering the shell, this may -take a few extra seconds as it initializes the CD drive. -</para> -</listitem> - -<listitem><para> -Examine the output from the shell looking for the CDROM drive. -It is most likely the <filename>fs0:</filename> device although -other devices with bootable partitions will also show up as -<filename>fs<replaceable>n</replaceable></filename>. -</para></listitem> - -<listitem><para> -Enter <command>fs<replaceable>n</replaceable>:</command> and press -<command>ENTER</command> to select that -device where <replaceable>n</replaceable> is the partition number for the -CDROM. The shell will now display the partition number as its prompt. -</para></listitem> - -<listitem><para> -Enter <command>elilo</command> and press <command>ENTER</command>. -This will start the boot load sequence. -</para></listitem> - -</itemizedlist> - -<para> - -As with option 1, these steps start the &debian; boot loader which will -display a menu page for you to select a boot kernel and options. -You can also enter the shorter -<command>fs<replaceable>n</replaceable>:elilo</command> command at -the shell prompt. -Proceed to selecting the boot kernel and options. - -</para> - - </sect3> - - <sect3 arch="ia64" id="serial-console"> - <title>Installing using a Serial Console</title> - -<para> - -You may choose to perform an install using a monitor and keyboard -or using a serial connection. To use a monitor/keyboard setup, -select an option containing the string [VGA console]. To install -over a serial connection, choose an option containing the string -[<replaceable>BAUD</replaceable> baud serial console], where -<replaceable>BAUD</replaceable> is the speed of your serial console. -Menu items for the most typical baud rate settings on the ttyS0 -device are preconfigured. - -</para><para> - -In most circumstances, you will want the installer to use the same -baud rate as your connection to the EFI console. If you aren't -sure what this setting is, you can obtain it using the command -<command>baud</command> at the EFI shell. - -</para><para> - -If there is not an option available that is configured for the serial -device or baud rate you would like to use, you may override the console setting -for one of the existing menu options. For example, to use a -57600 baud console over the ttyS1 device, enter -<command>console=ttyS1,57600n8</command> into -the <classname>Boot:</classname> text window. - -</para> - -<note><para> -Most IA-64 boxes ship with a default console setting of 9600 baud. -This setting is rather slow, and the normal installation process -will take a significant time to draw each screen. You should consider -either increasing the baud rate used for performing the installation, -or performing a Text Mode installation. See the <classname>Params</classname> -help menu for instructions on starting the installer in Text Mode. -</para></note> - -<warning><para> -If you select the wrong console type, you -will be able to select the kernel and enter parameters but both -the display and your input will go dead as soon as the kernel starts, -requiring you to reboot before you can begin the installation. -</para></warning> - </sect3> - - <sect3 arch="ia64" id="kernel-option-menu"> - <title>Selecting the Boot Kernel and Options</title> - -<para> - -The boot loader will display a form with a menu list and a text -window with a <classname>Boot:</classname> prompt. -The arrow keys select an item from the menu and any text typed -at the keyboard will appear in the text window. -There are also help screens which can be displayed by pressing -the appropriate function key. -The <classname>General</classname> help screen explains the menu -choices and the <classname>Params</classname> screen explains -the common command line options. - -</para><para> - -Consult the <classname>General</classname> help screen for the -description of the kernels and install modes most appropriate -for your installation. -You should also consult <xref linkend="boot-parms"/> below for any additional -parameters that you may want to set in the <classname>Boot:</classname> -text window. -The kernel version you choose selects the kernel version that will be -used for both the installation process and the installed system. -If you encounter kernel problems with the installation, you may also -have those same problems with the system you install. -The following two steps will select and start the install: - -</para> - -<itemizedlist> - -<listitem><para> -Select the kernel version and installation mode most -appropriate to your needs with the arrow keys. -</para></listitem> - -<listitem><para> -Enter any boot parameters by typing at the keyboard. -The text will be displayed directly in the text window. -This is where kernel parameters (such as serial console -settings) are specified. -</para></listitem> - -<listitem><para> -Press <command>ENTER</command>. This will load and start the -kernel. -The kernel will display its usual initialization messages followed -by the first screen of the &debian; Installer. -</para></listitem> - -</itemizedlist> - -<para> - -Proceed to the next chapter to continue the installation where you will -set up the language locale, network, and disk partitions. - -</para> - </sect3> - </sect2> - - <sect2 arch="ia64" id="boot-tftp-ia64"><title>Booting with TFTP</title> - -<para> -Booting an IA-64 system from the network is similar to a CD boot. -The only difference is how the installation kernel is loaded. -The EFI Boot Manager can load and start programs from a server on -the network. -Once the installation kernel is loaded and starts, the system install -will proceed through the same steps as the CD install with the exception -that the packages of the base install will be loaded from the network -rather than the CD drive. - -</para> - -&boot-installer-intro-net.xml; - -<para> - -Network booting an IA-64 system requires two architecture-specific actions. -On the boot server, DHCP and TFTP must be configured to deliver -<command>elilo</command>. -On the client a new boot option must be defined in the EFI boot manager -to enable loading over a network. - -</para> - - <sect3 arch="ia64" id="boot-tftp-server"> - <title>Configuring the Server</title> -<para> - -A suitable TFTP entry for network booting an IA-64 system looks something -like this: - -<informalexample><screen> -host mcmuffin { - hardware ethernet 00:30:6e:1e:0e:83; - fixed-address 10.0.0.21; - filename "debian-installer/ia64/elilo.efi"; -} -</screen></informalexample> - -Note that the goal is to get <command>elilo.efi</command> running on -the client. - -</para><para> - -Extract the <filename>netboot.tar.gz</filename> file into the directory used -as the root for your tftp server. Typical tftp root directories include -<filename>/var/lib/tftp</filename> and <filename>/tftpboot</filename>. -This will create a <filename>debian-installer</filename> directory -tree containing the boot files for an IA-64 system. - -</para><para> - -<informalexample><screen> -# cd /var/lib/tftp -# tar xvfz /home/user/netboot.tar.gz -./ -./debian-installer/ -./debian-installer/ia64/ -[...] -</screen></informalexample> - -The <filename>netboot.tar.gz</filename> contains an -<filename>elilo.conf</filename> file that should work for most configurations. -However, should you need to make changes to this file, you can find it in the -<filename>debian-installer/ia64/</filename> directory. - -It is possible to have different config files for different clients by naming -them using the client's IP address in hex with the suffix -<filename>.conf</filename> instead of <filename>elilo.conf</filename>. -See documentation provided in the <classname>elilo</classname> package -for details. - -</para> - </sect3> - - <sect3 arch="ia64" id="boot-tftp-client"> - <title>Configuring the Client</title> -<para> - -To configure the client to support TFTP booting, start by booting to -EFI and entering the <guimenu>Boot Option Maintenance Menu</guimenu>. - -<itemizedlist> -<listitem><para> - -Add a boot option. - -</para></listitem> -<listitem><para> - -You should see one or more lines with the text -<guimenuitem>Load File [Acpi()/.../Mac()]</guimenuitem>. If more -than one of these entries exist, choose the one containing the -MAC address of the interface from which you'll be booting. -Use the arrow keys to highlight your choice, then press enter. - -</para></listitem> -<listitem><para> - -Name the entry <userinput>Netboot</userinput> or something similar, -save, and exit back to the boot options menu. - -</para></listitem> -</itemizedlist> - -You should see the new boot option you just created, and selecting it -should initiate a DHCP query, leading to a TFTP load of -<filename>elilo.efi</filename> from the server. - -</para><para> - -The boot loader will display its prompt after it has downloaded and -processed its configuration file. -At this point, the installation proceeds with the same steps as a -CD install. Select a boot option as in above and when the kernel -has completed installing itself from the network, it will start the -&debian; Installer. - -</para><para> - -Proceed to the next chapter to continue the installation where -you will set up the language locale, network, and disk partitions. - -</para> - </sect3> - </sect2> diff --git a/en/boot-installer/intro-net.xml b/en/boot-installer/intro-net.xml index 1c7512165..a2d6a896d 100644 --- a/en/boot-installer/intro-net.xml +++ b/en/boot-installer/intro-net.xml @@ -7,12 +7,9 @@ Booting from the network requires that you have a network connection and a TFTP network boot server (and probably also a DHCP, RARP, or BOOTP server for automatic network configuration). -</para><para arch="hppa"> +</para> -Older systems such as the 715 might require the use of an RBOOT server -instead of a BOOTP server. - -</para><para> +<para> The server-side setup to support network booting is described in <xref linkend="install-tftp"/>. diff --git a/en/boot-installer/mips.xml b/en/boot-installer/mips.xml deleted file mode 100644 index 7781679dc..000000000 --- a/en/boot-installer/mips.xml +++ /dev/null @@ -1,9 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- $Id$ --> - - - <sect2 arch="mips;mips64el;mipsel" id="boot-tftp-mips"><title>Booting with TFTP</title> - -&boot-installer-intro-net.xml; - - </sect2>
\ No newline at end of file diff --git a/en/boot-installer/parameters.xml b/en/boot-installer/parameters.xml index bbc2837c1..91d981406 100644 --- a/en/boot-installer/parameters.xml +++ b/en/boot-installer/parameters.xml @@ -66,16 +66,6 @@ terminal type, which is very close to <literal>vt102</literal>. </para> -<para arch="sparc"> - -For &arch-title; the serial devices are <filename>ttya</filename> or -<filename>ttyb</filename>. -Alternatively, set the <envar>input-device</envar> and -<envar>output-device</envar> OpenPROM variables to -<filename>ttya</filename>. - -</para> - </sect2> <sect2 id="installer-args"><title>&debian; Installer Parameters</title> @@ -248,21 +238,7 @@ you can disable the feature using the parameter Problem symptoms are error messages about bterm or bogl, a blank screen, or a freeze within a few minutes after starting the install. -</para><para arch="hppa"> - -Such problems have been reported on hppa. - -</para><note arch="sparc"><para> - -Because of display problems on some systems, framebuffer support is -<emphasis>disabled by default</emphasis> for &arch-title;. This can result -in ugly display on systems that do properly support the framebuffer, like -those with ATI graphical cards. -If you see display problems in the installer, you can try booting with -parameter <userinput>debian-installer/framebuffer=true</userinput> or -<userinput>fb=true</userinput> for short. - -</para></note></listitem> +</para></listitem> </varlistentry> <varlistentry arch="not-s390"> @@ -433,7 +409,7 @@ disable that authentication. </para></listitem> </varlistentry> -<varlistentry arch="mips;mipsel;mips64el"> +<varlistentry arch="mipsel;mips64el"> <term>ramdisk_size</term> <listitem><para> diff --git a/en/boot-installer/sparc.xml b/en/boot-installer/sparc.xml deleted file mode 100644 index e5c39e742..000000000 --- a/en/boot-installer/sparc.xml +++ /dev/null @@ -1,46 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- $Id$ --> - - <sect2 arch="sparc" id="boot-tftp-sparc"><title>Booting with TFTP</title> - -&boot-installer-intro-net.xml; - -<para> - -On machines with OpenBoot, simply enter the boot monitor on the -machine which is being installed (see -<xref linkend="invoking-openboot"/>). -Use the command <userinput>boot net</userinput> to boot from a TFTP -and RARP server, or try <userinput>boot net:bootp</userinput> or -<userinput>boot net:dhcp</userinput> to boot from a TFTP and BOOTP -or DHCP server. You can pass extra boot parameters to &d-i; at the end -of the <userinput>boot</userinput> command. - -</para> - </sect2> - - - <sect2 arch="sparc"><title>Booting from a CD-ROM</title> - -&boot-installer-intro-cd.xml; - -<para> - -Most OpenBoot versions support the <userinput>boot cdrom</userinput> -command which is simply an alias to boot from the SCSI device on ID 6 -(or the secondary master for IDE based systems). - -</para> - </sect2> - - <sect2 arch="sparc"><title>IDPROM Messages</title> -<para> - -If you cannot boot because you get messages about a problem with -<quote>IDPROM</quote>, then it's possible that your NVRAM battery, which -holds configuration information for you firmware, has run out. See the -<ulink url="&url-sun-nvram-faq;">Sun NVRAM FAQ</ulink> for more -information. - -</para> - </sect2> diff --git a/en/boot-installer/trouble.xml b/en/boot-installer/trouble.xml index 4f6859e69..cbaae23a0 100644 --- a/en/boot-installer/trouble.xml +++ b/en/boot-installer/trouble.xml @@ -356,73 +356,6 @@ installer. </para> </sect3> -<!-- outdated - <sect3> - <title>System Freeze while Loading USB Modules</title> -<para> - -The kernel normally tries to install USB modules and the USB keyboard driver -in order to support some non-standard USB keyboards. However, there are some -broken USB systems where the driver hangs on loading. A possible workaround -may be disabling the USB controller in your mainboard BIOS setup. Another option -is passing the <userinput>nousb</userinput> parameter at the boot prompt. - -</para> - </sect3> ---> - - </sect2> - - <sect2 arch="sparc" id="sparc-boot-problems"> - <title>Common &arch-title; Installation Problems</title> -<para> - -There are some common installation problems that are worth mentioning. - -</para> - <sect3> - <title>Misdirected video output</title> -<para> - -It is fairly common for &arch-title; to have two video cards in one machine, -for example an ATI card and a Sun Creator 3D. In some cases, this may result -in the video output getting misdirected soon after the system boots. In -typical cases, the display will only show: - -<informalexample><screen> -Remapping the kernel... done -Booting Linux... -</screen></informalexample> - -To work around this, you can either pull out one of the video cards, or -disable the one not used during the OpenProm boot phase using a kernel -parameter. For example, to disable an ATI card, you should boot the -installer with <userinput>video=atyfb:off</userinput>. - -</para><para> - -Note that you may also have to manually add this parameter to the silo -configuration (edit <filename>/target/etc/silo.conf</filename> before -rebooting) and, if you installed X11, modify the video driver in -<filename>/etc/X11/xorg.conf</filename>. - -</para> - </sect3> - - <sect3> - <title>Failure to Boot or Install from CD-ROM</title> -<para> - -Some Sparc systems are notoriously difficult to boot from CD-ROM and -even if they do boot, there may be inexplicable failures during the -installation. Most problems have been reported with SunBlade systems. - -</para><para> - -We recommend to install such systems by netbooting the installer. - -</para> - </sect3> </sect2> <sect2 id="kernel-msgs"> diff --git a/en/boot-new/boot-new.xml b/en/boot-new/boot-new.xml index cb28aca37..6ef382a2a 100644 --- a/en/boot-new/boot-new.xml +++ b/en/boot-new/boot-new.xml @@ -53,6 +53,7 @@ or not detected correctly, please file an installation report. </para> +<!-- <sect2 arch="powerpc"><title>OldWorld PowerMacs</title> <para> @@ -91,8 +92,10 @@ e.g. <userinput>/dev/sda8</userinput>. </para> </sect2> +--> +<!-- <sect2 arch="powerpc"><title>NewWorld PowerMacs</title> <para> @@ -135,6 +138,8 @@ for more information. </para> </sect2> +--> + </sect1> &mount-encrypted.xml; diff --git a/en/hardware/accessibility.xml b/en/hardware/accessibility.xml index 428be96b2..0600e7481 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;ppc64el;x86"> + <sect2 id="braille-displays" arch="ppc64el;x86"> <title>Braille Displays</title> <para> diff --git a/en/hardware/hardware-supported.xml b/en/hardware/hardware-supported.xml index 3db1387e4..f1dddcc5e 100644 --- a/en/hardware/hardware-supported.xml +++ b/en/hardware/hardware-supported.xml @@ -79,18 +79,6 @@ variations of each architecture known as <quote>flavors</quote>. <entry></entry> </row> -<!-- -<row> - <entry morerows="1">32bit MIPS (big-endian)</entry> - <entry morerows="1">mips</entry> - <entry>MIPS Malta</entry> - <entry>4kc-malta</entry> -</row><row> - <entry>Cavium Octeon</entry> - <entry>octeon</entry> -</row> ---> - <row> <entry morerows="2">64bit MIPS (little-endian)</entry> <entry morerows="2">mips64el</entry> @@ -138,26 +126,6 @@ variations of each architecture known as <quote>flavors</quote>. <entry></entry> </row> -<!-- -<row> - <entry morerows="1">Sun SPARC</entry> - <entry morerows="1">sparc</entry> - <entry>sun4u</entry> - <entry morerows="1">sparc64</entry> -</row><row> - <entry>sun4v</entry> -</row> ---> - -<!-- -<row> - <entry>IBM S/390</entry> - <entry>s390</entry> - <entry>IPL from VM-reader and DASD</entry> - <entry>generic</entry> -</row> ---> - <row> <entry>64bit IBM S/390</entry> <entry>s390x</entry> @@ -200,10 +168,8 @@ as well. &supported-amd64.xml; &supported-arm.xml; &supported-i386.xml; -&supported-mips.xml; &supported-powerpc.xml; &supported-s390.xml; -&supported-sparc.xml; <sect2 arch="x86" id="laptops"><title>Laptops</title> <para> @@ -358,30 +324,6 @@ Details on supported graphics hardware and pointing devices can be found at <ulink url="&url-xorg;"></ulink>. &debian; &release; ships with X.Org version &x11ver;. -</para><para arch="sparc"> - -Most graphics options commonly found on Sparc-based machines are supported. -X.org graphics drivers are available for sunbw2, suncg14, suncg3, suncg6, -sunleo and suntcx framebuffers, Creator3D and Elite3D cards (sunffb driver), -PGX24/PGX64 ATI-based video cards (ati driver), and PermediaII-based cards -(glint driver). To use an Elite3D card with X.org you additionally need to -install the <classname>afbinit</classname> package, and read the documentation -included with it on how to activate the card. - -</para><para arch="sparc"> - -It is not uncommon for a Sparc machine to have two graphics cards in a -default configuration. In such a case there is a possibility that the -Linux kernel will not direct its output to the card initially used by the -firmware. The lack of output on the graphical console may then be mistaken -for a hang (usually the last message seen on console is 'Booting Linux...'). -One possible solution is to physically remove one of the video cards; -another option is to disable one of the cards using a kernel boot parameter. -Also, if graphical output is not required or desired, serial console may be -used as an alternative. On some systems use of serial console can be -activated automatically by disconnecting the keyboard before booting the -system. - </para> </sect2> diff --git a/en/hardware/installation-media.xml b/en/hardware/installation-media.xml index 742a09e09..00eba6c8a 100644 --- a/en/hardware/installation-media.xml +++ b/en/hardware/installation-media.xml @@ -73,7 +73,7 @@ deployment of a large number of machines. Setting up the necessary infrastructure requires a certain level of technical experience, so this is not recommended for novice users. -<phrase arch="mips;mipsel;mips64el">This is the preferred installation technique +<phrase arch="mipsel;mips64el">This is the preferred installation technique for &arch-title;.</phrase> </para><para condition="supports-nfsroot"> @@ -94,12 +94,8 @@ for many architectures. This will require some other operating system to load the installer onto the hard disk. This method is only recommended for special cases when no other installation method is available. -</para><para arch="sparc"> - -Although the &arch-title; does not allow booting from SunOS -(Solaris), you can install from a SunOS partition (UFS slices). - </para> + </sect2> @@ -141,38 +137,9 @@ SCSI disk controllers from many different manufacturers are supported. See the for more details. --> -</para><para arch="sparc"> - -Any storage system supported by the Linux kernel is also supported by -the boot system. The following SCSI drivers are supported in the default -kernel: - -<itemizedlist> -<listitem><para> - -Sparc ESP - -</para></listitem> -<listitem><para> - -PTI Qlogic,ISP +</para><para> -</para></listitem> -<listitem><para> - -Adaptec AIC7xxx - -</para></listitem> -<listitem><para> - -NCR and Symbios 53C8XX - -</para></listitem> -</itemizedlist> - -IDE systems (such as the UltraSPARC 5) are also supported. See -<ulink url="&url-sparc-linux-faq;">Linux for SPARC Processors FAQ</ulink> -for more information on SPARC hardware supported by the Linux kernel. +IDE systems are also supported. <!-- </para><para arch="powerpc"> @@ -180,13 +147,7 @@ Any storage system supported by the Linux kernel is also supported by the boot system. Note that the current Linux kernel does not support floppies on CHRP systems at all. --> -<!-- </para><para arch="hppa"> - -Any storage system supported by the Linux kernel is also supported by -the boot system. Note that the current Linux kernel does not support -the floppy drive. --> - -</para><para arch="mips;mipsel;mips64el"> +</para><para arch="mipsel;mips64el"> Any storage system supported by the Linux kernel is also supported by the boot system. diff --git a/en/hardware/network-cards.xml b/en/hardware/network-cards.xml index cd1b059ce..692d38202 100644 --- a/en/hardware/network-cards.xml +++ b/en/hardware/network-cards.xml @@ -13,40 +13,9 @@ should normally be loaded automatically. PCMCIA/Express Cards on laptops.</phrase> <phrase arch="i386">Many older ISA cards are supported as well.</phrase> -</para><para arch="sparc"> - -This includes a lot of generic PCI cards (for systems that have PCI) and -the following NICs from Sun: - -<itemizedlist> -<listitem><para> - -Sun LANCE - -</para></listitem> -<listitem><para> - -Sun Happy Meal - -</para></listitem> -<listitem><para> - -Sun BigMAC - -</para></listitem> -<listitem><para> - -Sun QuadEthernet - -</para></listitem> -<listitem><para> - -MyriCOM Gigabit Ethernet - -</para></listitem> -</itemizedlist> +</para> -</para><para arch="s390"> +<para arch="s390"> The list of supported network devices is: @@ -123,56 +92,4 @@ a Windows driver.</phrase> </para> </sect3> - <sect3 arch="sparc" id="nics-sparc-trouble"> - <title>Known Issues for &arch-title;</title> -<para> - -There are a couple of issues with specific network cards that are worth -mentioning here. - -</para> - - <sect4><title>Conflict between tulip and dfme drivers</title> -<!-- BTS: #334104; may also affect other arches, but most common on sparc --> -<para> - -<!-- BTS: #334104; may also affect other arches, but most common on sparc --> -There are various PCI network cards that have the same PCI identification, -but are supported by related, but different drivers. Some cards work with -the <literal>tulip</literal> driver, others with the <literal>dfme</literal> -driver. Because they have the same identification, the kernel cannot -distinguish between them and it is not certain which driver will be loaded. -If this happens to be the wrong one, the NIC may not work, or work badly. - -</para><para> - -This is a common problem on Netra systems with a Davicom (DEC-Tulip -compatible) NIC. In that case the <literal>tulip</literal> driver is -probably the correct one. -You can prevent this issue by blacklisting the wrong driver module as -described in <xref linkend="module-blacklist"/>. - -</para><para> - -An alternative solution during the installation is to switch to a shell -and unload the wrong driver module using -<userinput>modprobe -r <replaceable>module</replaceable></userinput> (or -both, if they are both loaded). After that you can load the correct module -using <userinput>modprobe <replaceable>module</replaceable></userinput>. -Note that the wrong module may then still be loaded when the system is -rebooted. - -</para> - </sect4> - - <sect4><title>Sun B100 blade</title> -<!-- BTS: #384549; should be checked for kernels >2.6.18 --> -<para> - -The <literal>cassini</literal> network driver does not work with Sun B100 -blade systems. - -</para> - </sect4> - </sect3> </sect2> diff --git a/en/hardware/supported/hppa.xml b/en/hardware/supported/hppa.xml deleted file mode 100644 index b2fdad4d1..000000000 --- a/en/hardware/supported/hppa.xml +++ /dev/null @@ -1,17 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- $Id$ --> - - - <sect2 arch="hppa"><title>CPU, Main Boards, and Video Support</title> -<para> - -There are two major support <emphasis>&architecture;</emphasis> flavors: -PA-RISC 1.1 and PA-RISC 2.0. The PA-RISC 1.1 architecture is targeted -at 32-bit processors whereas the 2.0 architecture is targeted to -the 64-bit processors. Some systems are able to run either kernel. -In both cases, the userland is 32-bit. There is the possibility of -a 64-bit userland in the future. - -</para> - </sect2> - diff --git a/en/hardware/supported/ia64.xml b/en/hardware/supported/ia64.xml deleted file mode 100644 index 53394db87..000000000 --- a/en/hardware/supported/ia64.xml +++ /dev/null @@ -1,3 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- $Id$ --> - diff --git a/en/hardware/supported/mips.xml b/en/hardware/supported/mips.xml deleted file mode 100644 index f8fd19a54..000000000 --- a/en/hardware/supported/mips.xml +++ /dev/null @@ -1,116 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- $Id$ --> - - - <sect2 arch="mips;mips64el;mipsel"><title>Platforms supported by the - &debian; &architecture; port</title> -<para> - -&debian; on &arch-title; supports the following platforms: - - <variablelist> - <varlistentry> - <term>Cavium Octeon</term> - <listitem> - <para> - Cavium designs a range of 64-bit MIPS Octeon processors which are - mainly used in networking devices. Devices with these processors - include the Ubiquiti EdgeRouter and the Rhino Labs UTM8. - </para> - </listitem> - </varlistentry> - - <varlistentry arch="mips64el;mipsel"> - <term>Loongson 3</term> - <listitem> - <para> - Devices based on the Loongson 3A and 3B processors are supported. - <!-- TODO list some actual devices here --> - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>MIPS Malta</term> - <listitem> - <para> - This platform is emulated by QEMU and is therefore a nice way - to test and run &debian; on MIPS if you don't have the hardware. - </para> - <para> - There are two Malta kernel flavours: 4kc-malta is built for 32-bit - processors, and 5kc-malta is built for 64-bit processors. - </para> - </listitem> - </varlistentry> - </variablelist> -</para> -<para> - - In addition, other boards which contain <phrase arch="mips;mipsel">MIPS32r2 - or</phrase> MIPS64r2 based processors should also be able to run &debian;, - however kernels for these processors are not built and the &debian; - installer does not directly support them. - -</para> -<para> - -Complete information regarding supported mips/mipsel/mips64el machines can be found -at the <ulink url="&url-linux-mips;">Linux-MIPS homepage</ulink>. In the -following, only the systems supported by the &debian; installer will be -covered. If you are looking for support for other subarchitectures, please -contact the <ulink url="&url-list-subscribe;"> -debian-&arch-listname; mailing list</ulink>. - -</para> - - <sect3><title>CPU</title> -<para> - - Some MIPS machines can be operated in both big and little endian mode. - <phrase arch="mips64el;mipsel"> - For little endian MIPS, please read the documentation for the mipsel and - mips64el architectures. - </phrase> - <phrase arch="mips"> - For big endian MIPS, please read the documentation for the mips architecture. - </phrase> - -</para> - </sect3> - </sect2> - - <sect2 arch="mips;mipsel"><title>Platforms no longer supported by the &debian; &architecture; port</title> -<para> - Since &debian; Stretch, support for all MIPS processors which do not - implement MIPS32 Release 2 have been dropped. Therefore the following - platforms supported in Jessie are no longer supported: - - <variablelist> - <varlistentry> - <term>Loongson 2E and 2F</term> - <listitem> - These are the older Loongson processors. Devices based on them - include the Fuloong Mini-PC and the Lemote Yeeloong laptop. - </listitem> - </varlistentry> - <varlistentry> - <term>SGI IP22</term> - <listitem> - This platform includes the SGI machines Indy, Indigo 2 and Challenge S. - </listitem> - </varlistentry> - <varlistentry> - <term>SGI IP32</term> - <listitem>This platform is generally known as SGI O2.</listitem> - </varlistentry> - <varlistentry> - <term>Broadcom BCM91250</term> - <listitem> - Development board for Broadcom's SiByte core. Also known by its - codename SWARM. - </listitem> - </varlistentry> - </variablelist> -</para> - </sect2> diff --git a/en/hardware/supported/powerpc.xml b/en/hardware/supported/powerpc.xml index 4b9ab56ad..414f82eb5 100644 --- a/en/hardware/supported/powerpc.xml +++ b/en/hardware/supported/powerpc.xml @@ -2,13 +2,13 @@ <!-- $Id$ --> +<!-- <sect2 arch="powerpc"><title>CPU, Main Boards, and Video Support</title> <para> For &debian-gnu; &release; only the PMac (Power-Macintosh or PowerMac) and PreP subarchitectures are supported. -<!-- There are four major supported <emphasis>&architecture;</emphasis> subarchitectures: PMac (Power-Macintosh or PowerMac), PReP, APUS (Amiga Power-UP System), and CHRP machines. Each subarchitecture has its own boot @@ -20,7 +20,6 @@ supporting different CPU variants. Ports to other <emphasis>&architecture;</emphasis> architectures, such as the Be-Box and MBX architecture, are underway but not yet supported by &debian;. We may have a 64-bit port in the future. ---> </para> @@ -82,7 +81,7 @@ Newer IBM systems using POWER5, POWER6, and POWER7 processors. </para></listitem> </varlistentry> -<!-- + <varlistentry> <term>prep</term> <listitem><para> @@ -101,7 +100,7 @@ currently disabled. </para></listitem> </varlistentry> ---> + </variablelist> </para> @@ -444,6 +443,7 @@ which is Nubus, please see the section above). </sect3> </sect2> +--> <sect2 arch="ppc64el"><title>CPU, Main Boards, and Video Support</title> <!-- Section for ppc64el --> diff --git a/en/hardware/supported/sparc.xml b/en/hardware/supported/sparc.xml deleted file mode 100644 index a8261e45f..000000000 --- a/en/hardware/supported/sparc.xml +++ /dev/null @@ -1,70 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- $Id$ --> - - <sect2 arch="sparc" id="sparc-cpus"> - <title>CPU and Main Boards Support</title> -<para> - -Sparc-based hardware is divided into a number of different subarchitectures, -identified by one of the following names: sun4, sun4c, sun4d, sun4m, sun4u -or sun4v. The following list describes what machines they include and what -level of support may be expected for each of them. - -</para> - -<variablelist> -<varlistentry> -<term>sun4, sun4c, sun4d, sun4m</term> - -<listitem><para> - -None of these 32-bit sparc subarchitectures (sparc32) is supported. For a -complete list of machines belonging to these subarchitectures, please consult -the <ulink url="http://en.wikipedia.org/wiki/SPARCstation">Wikipedia -SPARCstation page</ulink>. - -</para><para> - -The last &debian; release to support sparc32 was Etch, but even then only -for sun4m systems. Support for the other 32-bits subarchitectures had -already been discontinued after earlier releases. - -</para></listitem> -</varlistentry> - -<varlistentry> -<term>sun4u</term> - -<listitem><para> - -This subarchitecture includes all 64-bit machines (sparc64) based on -the UltraSparc processor and its clones. Most of the machines are well -supported, even though for some you may experience problems booting from -CD due to firmware or bootloader bugs (this problem may be worked around -by using netbooting). Use the sparc64 or sparc64-smp kernel in UP and SMP -configurations respectively. - -</para></listitem> -</varlistentry> - -<varlistentry> -<term>sun4v</term> - -<listitem><para> - -This is the newest addition to the Sparc family, which includes machines -based on the Niagara multi-core CPUs. At the moment such CPUs are only -available in T1000 and T2000 servers by Sun, and are well supported. Use -the sparc64-smp kernel. - -</para></listitem> -</varlistentry> -</variablelist> - -<para> - -Note that Fujitsu's SPARC64 CPUs used in PRIMEPOWER family of servers are not -supported due to lack of support in the Linux kernel. - -</para> - </sect2> diff --git a/en/howto/installation-howto.xml b/en/howto/installation-howto.xml index 09d2fdf34..6e79c5d10 100644 --- a/en/howto/installation-howto.xml +++ b/en/howto/installation-howto.xml @@ -131,12 +131,17 @@ selection menu should show <quote>removable drive</quote> or <quote>USB-HDD</quo to get it to boot from the USB device. For helpful hints and details, see <xref linkend="usb-boot-x86" />. -</para><para arch="powerpc"> +</para> + +<!-- +<para arch="powerpc"> Booting Macintosh systems from USB storage devices involves manual use of Open Firmware. For directions, see <xref linkend="usb-boot-powerpc" />. </para> +--> + </sect2> <sect2 id="howto-getting-images-netboot"> diff --git a/en/install-methods/boot-drive-files.xml b/en/install-methods/boot-drive-files.xml index 1cf0274d9..59741e5a6 100644 --- a/en/install-methods/boot-drive-files.xml +++ b/en/install-methods/boot-drive-files.xml @@ -17,7 +17,10 @@ A full, <quote>pure network</quote> installation can be achieved using this technique. This avoids all hassles of removable media, like finding and burning CD/DVD images. -</para><para arch="powerpc"> +</para> + +<!-- +<para arch="powerpc"> The installer cannot boot from files on an HFS+ file system. MacOS System 8.1 and above may use HFS+ file systems; NewWorld PowerMacs all @@ -35,6 +38,7 @@ depending on whether the system is a <quote>NewWorld</quote> or an <quote>OldWorld</quote> model. </para> +--> <sect2 arch="x86" id="files-grub"> <title>Hard disk installer booting from Linux using @@ -124,98 +128,4 @@ Copy the following directories from a &debian; installation image to <filename>c </para> </sect2> - -<!-- - <sect2 arch="powerpc" id="files-oldworld"> - <title>Hard Disk Installer Booting for OldWorld Macs</title> -<para> - -The <filename>boot-floppy-hfs</filename> floppy uses -<application>miBoot</application> to launch Linux installation, but -<application>miBoot</application> cannot easily be used for hard disk -booting. <application>BootX</application>, launched from MacOS, -supports booting from files placed on the hard -disk. <application>BootX</application> can also be used to dual-boot -MacOS and Linux after your &debian; installation is complete. For the -Performa 6360, it appears that <command>quik</command> cannot make the -hard disk bootable. So <application>BootX</application> is required -on that model. - -</para><para> - -Download and unstuff the <application>BootX</application> -distribution, available from <ulink url="&url-powerpc-bootx;"></ulink>, -or in the -<filename>dists/woody/main/disks-powerpc/current/powermac</filename> -directory on &debian; http/ftp mirrors and official &debian; CDs. Use -<application>Stuffit Expander</application> to extract it from its -archive. Within the package, there is an empty folder called -<filename>Linux Kernels</filename>. Download -<filename>linux.bin</filename> and -<filename>ramdisk.image.gz</filename> from the -<filename>disks-powerpc/current/powermac</filename> folder, and place -them in the <filename>Linux Kernels</filename> folder. Then place the -<filename>Linux Kernels</filename> folder in the active System Folder. - -</para> - </sect2> - - <sect2 arch="powerpc" id="files-newworld"> - <title>Hard Disk Installer Booting for NewWorld Macs</title> -<para> - -NewWorld PowerMacs support booting from a network or an ISO9660 -CD-ROM, as well as loading ELF binaries directly from the hard -disk. These machines will boot Linux directly via -<command>yaboot</command>, which supports loading a kernel and RAMdisk -directly from an ext2 partition, as well as dual-booting with -MacOS. Hard disk booting of the installer is particularly appropriate -for newer machines without floppy drives. <command>BootX</command> is -not supported and must not be used on NewWorld PowerMacs. - -</para><para> - -<emphasis>Copy</emphasis> (not move) the following four files which -you downloaded earlier from the &debian; archives, onto the root level -of your hard drive (this can be accomplished by -<keycap>option</keycap>-dragging each file to the hard drive icon). - -<itemizedlist> -<listitem><para> - -<filename>vmlinux</filename> - -</para></listitem> -<listitem><para> - -<filename>initrd.gz</filename> - -</para></listitem> -<listitem><para> - -<filename>yaboot</filename> - -</para></listitem> -<listitem><para> - -<filename>yaboot.conf</filename> - -</para></listitem> -</itemizedlist> - -</para><para> - -Make a note of the partition number of the MacOS partition where you -place these files. If you have the MacOS <command>pdisk</command> -program, you can use the <command>L</command> command to check for the -partition number. You will need this partition number for the command -you type at the Open Firmware prompt when you boot the installer. - -</para><para> - -To boot the installer, proceed to <xref linkend="boot-newworld"/>. - -</para> - </sect2> ---> </sect1> diff --git a/en/install-methods/boot-usb-files.xml b/en/install-methods/boot-usb-files.xml index 062aed26f..9815ac2eb 100644 --- a/en/install-methods/boot-usb-files.xml +++ b/en/install-methods/boot-usb-files.xml @@ -141,8 +141,6 @@ setups are possible using the files from netboot, following There is an all-in-one file &hdmedia-boot-img; which contains all the installer files (including the kernel)<phrase arch="x86"> as well as <classname>syslinux</classname> and its -configuration file</phrase><phrase arch="powerpc"> as well as -<classname>yaboot</classname> and its configuration file</phrase>. </para><note><para> @@ -161,7 +159,10 @@ Simply extract this image directly to your USB stick: # zcat boot.img.gz > /dev/<replaceable>sdX</replaceable> </screen></informalexample> -</para><para arch="powerpc"> +</para> + +<!-- +<para arch="powerpc"> Create a partition of type "Apple_Bootstrap" on your USB stick using <command>mac-fdisk</command>'s <userinput>C</userinput> command and @@ -171,7 +172,10 @@ extract the image directly to that: # zcat boot.img.gz > /dev/<replaceable>sdX2</replaceable> </screen></informalexample> -</para><para> +</para> +--> + +<para> After that, mount the USB memory stick <phrase arch="x86">(<userinput>mount diff --git a/en/install-methods/install-tftp.xml b/en/install-methods/install-tftp.xml index 3094cf769..d37ee87d3 100644 --- a/en/install-methods/install-tftp.xml +++ b/en/install-methods/install-tftp.xml @@ -32,18 +32,19 @@ The DHCP (Dynamic Host Configuration Protocol) is a more flexible, backwards-compatible extension of BOOTP. Some systems can only be configured via DHCP. -</para><para arch="powerpc"> +</para> + +<!-- +<para arch="powerpc"> For PowerPC, if you have a NewWorld Power Macintosh machine, it is a good idea to use DHCP instead of BOOTP. Some of the latest machines are unable to boot using BOOTP. -</para><para arch="hppa"> - -Some older HPPA machines (e.g. 715/75) use RBOOTD rather than BOOTP. -There is an <classname>rbootd</classname> package available in &debian;. +</para> +--> -</para><para> +<para> The Trivial File Transfer Protocol (TFTP) is used to serve the boot image to the client. Theoretically, any server, on any platform, @@ -100,28 +101,6 @@ log TFTP requests to the system logs by default. Some of them support a It is recommended to check these log messages in case of boot problems as they are a good starting point for diagnosing the cause of errors. -</para><para arch="mips"> - -If you intend to install &debian; on an SGI machine and your TFTP server is a -GNU/Linux box running Linux 2.4, you'll need to set the following on your -server: - -<informalexample><screen> -# echo 1 > /proc/sys/net/ipv4/ip_no_pmtu_disc -</screen></informalexample> - -to turn off Path MTU discovery, otherwise the SGI's PROM can't -download the kernel. Furthermore, make sure TFTP packets are sent from -a source port no greater than 32767, or the download will stall after -the first packet. Again, it's Linux 2.4.X tripping this bug in the -PROM, and you can avoid it by setting - -<informalexample><screen> -# echo "2048 32767" > /proc/sys/net/ipv4/ip_local_port_range -</screen></informalexample> - -to adjust the range of source ports the Linux TFTP server uses. - </para> </sect2> @@ -136,7 +115,10 @@ file to the file which <command>tftpd</command> will use for booting a particular client. Unfortunately, the file name is determined by the TFTP client, and there are no strong standards. -</para><para arch="powerpc"> +</para> + +<!-- +<para arch="powerpc"> On NewWorld Power Macintosh machines, you will need to set up the <command>yaboot</command> boot loader as the TFTP boot image. @@ -172,7 +154,10 @@ from the <filename>netboot/</filename> directory: </para></listitem> </itemizedlist> -</para><para arch="x86"> +</para> +--> + +<para arch="x86"> For PXE booting, everything you should need is set up in the <filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this @@ -182,162 +167,6 @@ to <command>tftpd</command> as the filename to boot. For UEFI machines, you will need to pass an appropriate EFI boot image name (such as <filename>/debian-installer/amd64/bootnetx64.efi</filename>). -</para><para arch="ia64"> - -For PXE booting, everything you should need is set up in the -<filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this -tarball into the <command>tftpd</command> boot image directory. Make sure -your dhcp server is configured to pass -<filename>/debian-installer/ia64/elilo.efi</filename> -to <command>tftpd</command> as the filename to boot. - </para> - - <sect3 arch="sparc"> - <title>SPARC TFTP Booting</title> -<para> - -Some SPARC architectures add the subarchitecture names, such as -<quote>SUN4M</quote> or <quote>SUN4C</quote>, to the filename. Thus, -if your system's subarchitecture is a SUN4C, and its IP is 192.168.1.3, -the filename would be <filename>C0A80103.SUN4C</filename>. However, -there are also subarchitectures where the file the client looks for is -just <filename>client-ip-in-hex</filename>. An easy way to determine the -hexadecimal code for the IP address is to enter the following command -in a shell (assuming the machine's intended IP is 10.0.0.4). - -<informalexample><screen> -$ printf '%.2x%.2x%.2x%.2x\n' 10 0 0 4 -</screen></informalexample> - -To get to the correct filename, you will need to change all letters to -uppercase and if necessary append the subarchitecture name. - -</para><para> - -If you've done all this correctly, giving the command <userinput>boot -net</userinput> from the OpenPROM should load the image. If the image -cannot be found, try checking the logs on your tftp server to see which -image name is being requested. - -</para><para> - -You can also force some sparc systems to look for a specific file name -by adding it to the end of the OpenPROM boot command, such as -<userinput>boot net my-sparc.image</userinput>. This must still reside -in the directory that the TFTP server looks in. - -</para> - </sect3> - - <sect3 arch="mips"> - <title>SGI TFTP Booting</title> -<para> - -On SGI machines you can rely on the <command>bootpd</command> to supply -the name of the TFTP file. It is given either as the -<userinput>bf=</userinput> in <filename>/etc/bootptab</filename> or as -the <userinput>filename=</userinput> option in -<filename>/etc/dhcpd.conf</filename>. - -</para> - </sect3> - - </sect2> - -<!-- FIXME: commented out since it seems too old to be usable and a current - way is not known - - <sect2 id="tftp-low-memory"> - <title>TFTP Installation for Low-Memory Systems</title> -<para> - -On some systems, the standard installation RAMdisk, combined with the -memory requirements of the TFTP boot image, cannot fit in memory. In -this case, you can still install using TFTP, you'll just have to go -through the additional step of NFS mounting your root directory over -the network as well. This type of setup is also appropriate for -diskless or dataless clients. - -</para><para> - -First, follow all the steps above in <xref linkend="install-tftp"/>. - -<orderedlist> -<listitem><para> - -Copy the Linux kernel image on your TFTP server using the -<userinput>a.out</userinput> image for the architecture you are -booting. - -</para></listitem> -<listitem><para> - -Untar the root archive on your NFS server (can be the same system as -your TFTP server): - -<informalexample><screen> -# cd /tftpboot -# tar xvzf root.tar.gz -</screen></informalexample> - -Be sure to use the GNU <command>tar</command> (other tar programs, like the -SunOS one, badly handle devices as plain files). - -</para></listitem> -<listitem><para> - -Export your <filename>/tftpboot/debian-sparc-root</filename> directory -with root access to your client. E.g., add the following line to -<filename>/etc/exports</filename> (GNU/Linux syntax, should be similar -for SunOS): - -<informalexample><screen> -/tftpboot/debian-sparc-root <replaceable>client</replaceable>(rw,no_root_squash) -</screen></informalexample> - -NOTE: <replaceable>client</replaceable> is the host name or IP address recognized -by the server for the system you are booting. - -</para></listitem> -<listitem><para> - -Create a symbolic link from your client IP address in dotted notation -to <filename>debian-sparc-root</filename> in the -<filename>/tftpboot</filename> directory. For example, if the client -IP address is 192.168.1.3, do - -<informalexample><screen> -# ln -s debian-sparc-root 192.168.1.3 -</screen></informalexample> - -</para></listitem> -</orderedlist> - -</para> - - </sect2> - - <sect2 condition="supports-nfsroot"> - <title>Installing with TFTP and NFS Root</title> -<para> - -Installing with TFTP and NFS Root is similar to -<xref linkend="tftp-low-memory"/> because you don't want to -load the RAMdisk anymore but boot from the newly created NFS-root file -system. You then need to replace the symlink to the tftpboot image by -a symlink to the kernel image (for example, -<filename>linux-a.out</filename>). - -</para><para> - -RARP/TFTP requires all daemons to be running on the same server (the -workstation is sending a TFTP request back to the server that replied -to its previous RARP request). - -</para> - - </sect2> -END FIXME --> </sect1> diff --git a/en/install-methods/tftp/bootp.xml b/en/install-methods/tftp/bootp.xml index 4e89b8622..678e1cb3a 100644 --- a/en/install-methods/tftp/bootp.xml +++ b/en/install-methods/tftp/bootp.xml @@ -49,12 +49,6 @@ specifies the hardware address of the client. The <quote>bf</quote> option specifies the file a client should retrieve via TFTP; see <xref linkend="tftp-images"/> for more details. -<phrase arch="mips"> -On SGI machines you can just enter the command monitor and type -<userinput>printenv</userinput>. The value of the -<userinput>eaddr</userinput> variable is the machine's MAC address. -</phrase> - </para><para> By contrast, setting up BOOTP with ISC <command>dhcpd</command> is diff --git a/en/install-methods/tftp/rarp.xml b/en/install-methods/tftp/rarp.xml index 289d3a5c0..dc6b1f4d7 100644 --- a/en/install-methods/tftp/rarp.xml +++ b/en/install-methods/tftp/rarp.xml @@ -9,9 +9,6 @@ To set up RARP, you need to know the Ethernet address (a.k.a. the MAC address) of the client computers to be installed. If you don't know this information, you can -<phrase arch="sparc"> pick it off the initial OpenPROM boot messages, use the -OpenBoot <userinput>.enet-addr</userinput> command, or </phrase> - boot into <quote>Rescue</quote> mode and use the command <userinput>ip addr show dev eth0</userinput>. diff --git a/en/install-methods/usb-setup/powerpc.xml b/en/install-methods/usb-setup/powerpc.xml index 9e22dc6a7..078d37d2e 100644 --- a/en/install-methods/usb-setup/powerpc.xml +++ b/en/install-methods/usb-setup/powerpc.xml @@ -1,6 +1,7 @@ <!-- retain these comments for translator revision tracking --> <!-- $Id$ --> +<!-- <sect3 arch="powerpc"> <title>Partitioning the USB stick</title> <para> @@ -125,3 +126,4 @@ stick (<userinput>umount /mnt</userinput>). </para> </sect3> +-->
\ No newline at end of file diff --git a/en/partitioning/device-names.xml b/en/partitioning/device-names.xml index 9c68ff013..308b75a16 100644 --- a/en/partitioning/device-names.xml +++ b/en/partitioning/device-names.xml @@ -81,14 +81,9 @@ drive is <filename>/dev/sda5</filename>. Remember that the extended partition, that is, the primary partition holding the logical partitions, is not usable by itself. -</para><para arch="sparc"> - -Sun disk partitions allow for 8 separate partitions (or slices). The -third partition is usually (and is preferred to have) the <quote>Whole -Disk</quote> partition. This partition references all of the sectors of the -disk, and is used by the boot loader (either SILO, or Sun's). +</para> -</para><para arch="s390"> +<para arch="s390"> The partitions on each disk are represented by appending a decimal number to the disk name: <filename>dasda1</filename> and diff --git a/en/partitioning/partition-programs.xml b/en/partitioning/partition-programs.xml index cb63a3489..dad9a4307 100644 --- a/en/partitioning/partition-programs.xml +++ b/en/partitioning/partition-programs.xml @@ -128,11 +128,7 @@ includes steps you should take if you are sharing your disk with MacOS. </para> -&partition-hppa.xml; &partition-x86.xml; -&partition-ia64.xml; -&partition-mips.xml; &partition-powerpc.xml; -&partition-sparc.xml; </sect1> diff --git a/en/partitioning/partition/hppa.xml b/en/partitioning/partition/hppa.xml deleted file mode 100644 index 9f4443312..000000000 --- a/en/partitioning/partition/hppa.xml +++ /dev/null @@ -1,22 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- $Id$ --> - - - <sect2 arch="hppa"><title>Partitioning for &arch-title;</title> -<para> - -PALO, the HPPA boot loader, requires a partition of type <quote>F0</quote> somewhere -in the first 2GB. This is where the boot loader and an optional kernel -and RAMdisk will be stored, so make it big enough for that — at least -4Mb (I like 8–16MB). An additional requirement of the firmware is that -the Linux kernel must reside within the first 2GB of the disk. This -is typically achieved by making the root ext2 partition fit entirely -within the first 2GB of the disk. Alternatively you can create a small -ext2 partition near the start of the disk and mount that on -<filename>/boot</filename>, since that is the directory where the Linux -kernel(s) will be stored. <filename>/boot</filename> needs to be big enough -to hold whatever kernels (and backups) you might wish to load; 25–50MB -is generally sufficient. - -</para> - </sect2> diff --git a/en/partitioning/partition/ia64.xml b/en/partitioning/partition/ia64.xml deleted file mode 100644 index c4b3b6a3a..000000000 --- a/en/partitioning/partition/ia64.xml +++ /dev/null @@ -1,120 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- $Id$ --> - - - <sect2 arch="ia64"><title>Partitioning for &arch-title;</title> -<para> - -The <command>partman</command> disk partitioner is the default -partitioning tool for the installer. -It manages the set of partitions and their mount points to ensure -that the disks and filesystems are properly configured for a successful -installation. It actually uses <command>parted</command> to do the -on-disk partitioning. - -</para> - - <note> - <title>EFI Recognized Formats</title> -<para> - -The IA-64 EFI firmware supports two partition table (or disk label) -formats, GPT and MS-DOS. MS-DOS, the format typically used on i386 -PCs, is no longer recommended for IA-64 systems. Although -the installer also provides <command>cfdisk</command>, -you should only use <ulink url="parted.txt"> -<command>parted</command></ulink> because only it can manage both GPT -and MS-DOS tables correctly. - -</para></note> - -<para> - -The automatic partitioning recipes for <command>partman</command> -allocate an EFI partition as the first partition on the disk. -You can also set up the partition under the <guimenuitem>Guided -partitioning</guimenuitem> from the main menu in a manner similar to -setting up a <emphasis>swap</emphasis> partition. - -</para><para> - -The <command>partman</command> partitioner will handle most disk -layouts. -For those rare cases where it is necessary to manually set up a disk, -you can use the shell as described above and run the -<command>parted</command> utility directly using its command line interface. -Assuming that you want to erase your whole disk and create a GPT table -and some partitions, then something similar to the following command -sequence could be used: - -<informalexample><screen> - mklabel gpt - mkpartfs primary fat 0 50 - mkpartfs primary linux-swap 51 1000 - mkpartfs primary ext2 1001 3000 - set 1 boot on - print - quit -</screen></informalexample> - -This creates a new partition table, and three partitions to be used as -an EFI boot partition, swap space, and a root file system. Finally it -sets the boot flag on the EFI partition. Partitions are specified in -Megabytes, with start and end offsets from the beginning of the disk. -So, for example, above we created a 1999MB ext2 file system starting -at offset 1001MB from the start of the disk. Note that formatting swap -space with <command>parted</command> can take a few minutes to -complete, as it scans the partition for bad blocks. - -</para> - </sect2> - - <sect2 arch="ia64"><title>Boot Loader Partition Requirements</title> -<para> - -ELILO, the IA-64 boot loader, requires a partition containing a FAT -file system with the <userinput>boot</userinput> flag set. -The partition must be big enough to hold the boot loader and any -kernels or RAMdisks you may wish to boot. A minimum size would be -about 20MB, but if you expect to run with multiple kernels, then -128MB might be a better size. - -</para><para> - -The EFI Boot Manager and the EFI Shell fully support the GPT table -so the boot partition does not necessarily have to be the first -partition or even on the same disk. -This is convenient if you should forget to allocate the partition and -only find out after you have formatted the other partitions on your disk(s). -The <command>partman</command> partitioner checks for an EFI partition -at the same time it checks for a properly set up <emphasis>root</emphasis> -partition. -This gives you an opportunity to correct the disk layout before the -package install begins. -The easiest way to correct this omission is to shrink the last partition -of the disk to make enough free space for adding an EFI partition. - -</para><para> - -It is strongly recommended that you allocate the EFI boot partition -on the same disk as the <emphasis>root</emphasis> filesystem. - -</para> - </sect2> - - <sect2 arch="ia64"><title>EFI Diagnostic Partitions</title> -<para> - -The EFI firmware is significantly more sophisticated than the usual -BIOS seen on most x86 PCs. -Some system vendors take advantage of the ability of the EFI to -access files and run programs from a hard disk filesystem to store diagnostics -and EFI based system management utilities on the hard disk. -This is a separate FAT format filesystem on the system disk. -Consult the system documentation and accessories that come with the -system for details. -The easiest time to set up a diagnostics partition is at the same time you -set up the EFI boot partition. - -</para> - </sect2> diff --git a/en/partitioning/partition/mips.xml b/en/partitioning/partition/mips.xml deleted file mode 100644 index fa1f01fc5..000000000 --- a/en/partitioning/partition/mips.xml +++ /dev/null @@ -1,16 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- $Id$ --> - - - <sect2 arch="mips"><title>Partitioning for &arch-title;</title> -<para> - -SGI machines require an SGI disk label in order to make the system bootable -from hard disk. It can be created in the fdisk expert menu. The thereby -created volume header (partition number 9) should be at least 3MB large. -If the volume header created is too small, you can simply delete -partition number 9 and re-add it with a different size. Note that the -volume header must start at sector 0. - -</para> - </sect2> diff --git a/en/partitioning/partition/powerpc.xml b/en/partitioning/partition/powerpc.xml index ae28f24c7..ebeda02c1 100644 --- a/en/partitioning/partition/powerpc.xml +++ b/en/partitioning/partition/powerpc.xml @@ -2,6 +2,7 @@ <!-- $Id$ --> +<!-- <sect2 arch="powerpc"><title>Partitioning Newer PowerMacs</title> <para> @@ -55,3 +56,4 @@ not have active MacOS partitions and driver partitions. </para> </sect2> +--> diff --git a/en/partitioning/partition/sparc.xml b/en/partitioning/partition/sparc.xml deleted file mode 100644 index 8e861025e..000000000 --- a/en/partitioning/partition/sparc.xml +++ /dev/null @@ -1,33 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- $Id$ --> - - - <sect2 arch="sparc"><title>Partitioning for &arch-title;</title> -<para> - -Make sure you create a <quote>Sun disk label</quote> on your boot disk. This is -the only kind of partition scheme that the OpenBoot PROM understands, -and so it's the only scheme from which you can boot. The -<keycap>s</keycap> key is used in <command>fdisk</command> to -create Sun disk labels. - -</para><para> - -Furthermore, on &arch-title; disks, make sure your first partition on -your boot disk starts at cylinder 0. While this is required, it also -means that the first partition will contain the partition table and -the boot block, which are the first two sectors of the disk. You must -<emphasis>not</emphasis> put swap on the first partition of the boot -drive, since swap partitions do not preserve the first few sectors of -the partition. You can put Ext2 or UFS partitions there; these will -leave the partition table and the boot block alone. - -</para><para> - -It is also advised that the third partition should be of type <quote>Whole -disk</quote> (type 5), and contain the entire disk (from the first cylinder -to the last). This is simply a convention of Sun disk labels, and -helps the <command>SILO</command> boot loader keep its bearings. - -</para> - </sect2>
\ No newline at end of file diff --git a/en/preparing/bios-setup/powerpc.xml b/en/preparing/bios-setup/powerpc.xml index f03f3d23c..5b83af691 100644 --- a/en/preparing/bios-setup/powerpc.xml +++ b/en/preparing/bios-setup/powerpc.xml @@ -2,6 +2,7 @@ <!-- $Id$ --> +<!-- <sect2 arch="powerpc" id="invoking-openfirmware"> <title>Invoking OpenFirmware</title> <para> @@ -50,6 +51,7 @@ installed to nvram. </para> </sect2> +--> <sect2 arch="ppc64el;powerpc" id="update-firmware"> <title>How to update bare metal ppc64el firmware</title> diff --git a/en/preparing/bios-setup/sparc.xml b/en/preparing/bios-setup/sparc.xml deleted file mode 100644 index a88c9fe1a..000000000 --- a/en/preparing/bios-setup/sparc.xml +++ /dev/null @@ -1,105 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- $Id$ --> - - - <sect2 arch="sparc" id="invoking-openboot"><title>Invoking OpenBoot</title> - -<para> - -OpenBoot provides the basic functions needed to boot the &arch-title; -architecture. This is rather similar in function to the BIOS in the -x86 architecture, although much nicer. The Sun boot PROMs have a -built-in forth interpreter which lets you do quite a number of things -with your machine, such as diagnostics and simple scripts. - -</para><para> - -To get to the boot prompt you need to hold down the -<keycap>Stop</keycap> key (on older type 4 keyboards, use the -<keycap>L1</keycap> key, if you have a PC keyboard adapter, use -the <keycap>Break</keycap> key) and press the -<keycap>A</keycap> key. The boot PROM will give you a prompt, -either <userinput>ok</userinput> or <userinput>></userinput>. It is -preferred to have the <userinput>ok</userinput> prompt. So if you get -the old style prompt, hit the <keycap>n</keycap> key to get the new -style prompt. - -</para><para> - -If you are using a serial console, send a break to the machine. With Minicom, -use <keycap>Ctrl-A F</keycap>, with cu, hit <keycap>Enter</keycap>, then type -<userinput>%~break</userinput>. Consult the documentation of your terminal -emulator if you are using a different program. - -</para> - </sect2> - - <sect2 arch="sparc" id="boot-dev-select-sun"> - <title>Boot Device Selection</title> - -<para> - -You can use OpenBoot to boot from specific devices, and also to change -your default boot device. However, you need to know some details -about how OpenBoot names devices; it's considerably different from Linux -device naming, described in <xref linkend="device-names"/>. -Also, the command will vary a bit, depending on what version of -OpenBoot you have. More information about OpenBoot can be found in -the <ulink url="&url-openboot;">Sun OpenBoot Reference</ulink>. - -</para><para> - -<!-- -Typically, with newer revisions, you can use OpenBoot devices such as -<quote>floppy</quote>, <quote>cdrom</quote>, <quote>net</quote>, -<quote>disk</quote>, or <quote>disk2</quote>. These have the obvious -meanings; the <quote>net</quote> device is for booting from the network. -Additionally, the device name can specify a particular partition of a disk, -such as <quote>disk2:a</quote> to boot disk2, first partition. Full -OpenBoot device names have the form: - -<informalexample> -<screen> -<replaceable>driver-name</replaceable>@ -<replaceable>unit-address</replaceable>: -<replaceable>device-arguments</replaceable> -</screen></informalexample> - -In older revisions of OpenBoot, device naming is a bit different: the -floppy device is called <quote>/fd</quote>, and SCSI disk devices are of -the form <quote>sd(<replaceable>controller</replaceable>, -<replaceable>disk-target-id</replaceable>, -<replaceable>disk-lun</replaceable>)</quote>. The command -<userinput>show-devs</userinput> in newer OpenBoot revisions is useful -for viewing the currently configured devices. For full information, -whatever your revision, see the -<ulink url="&url-openboot;">Sun OpenBoot Reference</ulink>. - -</para><para> ---> - -To boot from a specific device, use the command <userinput>boot -<replaceable>device</replaceable></userinput>. You can set this -behavior as the default using the <userinput>setenv</userinput> -command. However, the name of the variable to set changed between -OpenBoot revisions. In OpenBoot 1.x, use the command -<userinput>setenv boot-from -<replaceable>device</replaceable></userinput>. In later revisions of -OpenBoot, use the command <userinput>setenv boot-device -<replaceable>device</replaceable></userinput>. Note, this is also -configurable using the <command>eeprom</command> command on Solaris, -or modifying the appropriate files in -<filename>/proc/openprom/options/</filename>, for example under Linux: - -<informalexample><screen> -# echo disk1:1 > /proc/openprom/options/boot-device -</screen></informalexample> - -and under Solaris: - -<informalexample><screen> -eeprom boot-device=disk1:1 -</screen></informalexample> - -</para> - </sect2> diff --git a/en/preparing/minimum-hardware-reqts.xml b/en/preparing/minimum-hardware-reqts.xml index c5e373ec1..84f8c7352 100644 --- a/en/preparing/minimum-hardware-reqts.xml +++ b/en/preparing/minimum-hardware-reqts.xml @@ -20,11 +20,15 @@ risk being frustrated if they ignore these suggestions. A Pentium 4, 1GHz system is the minimum recommended for a desktop system. -</para><para arch="powerpc"> +</para> + +<!-- +<para arch="powerpc"> Any OldWorld or NewWorld PowerPC can serve well as a desktop system. </para> +--> <table> <title>Recommended Minimum System Requirements</title> diff --git a/en/preparing/needed-info.xml b/en/preparing/needed-info.xml index b9e6e220d..2db3a4d23 100644 --- a/en/preparing/needed-info.xml +++ b/en/preparing/needed-info.xml @@ -52,20 +52,14 @@ Often contains useful information on configuring or using your hardware. <!-- We need the arch dependence for the whole list to ensure proper xml as long as not architectures have a paragraph --> - <itemizedlist arch="x86;sparc;mips;mipsel;mips64el"> + <itemizedlist arch="x86;mipsel;mips64el"> <listitem arch="x86"><para> <ulink url="&url-debian-wiki-hardware;">The Debian Wiki hardware page</ulink> </para></listitem> -<listitem arch="sparc"><para> - -<ulink url="&url-sparc-linux-faq;">Linux for SPARC Processors FAQ</ulink> - -</para></listitem> - -<listitem arch="mips;mipsel;mips64el"><para> +<listitem arch="mipsel;mips64el"><para> <ulink url="&url-linux-mips;">Linux/MIPS website</ulink> diff --git a/en/preparing/non-debian-partitioning.xml b/en/preparing/non-debian-partitioning.xml index c634c17d5..9f53f611a 100644 --- a/en/preparing/non-debian-partitioning.xml +++ b/en/preparing/non-debian-partitioning.xml @@ -74,37 +74,8 @@ to the partitioning step, select the option for manual partitioning, select the partition to resize, and simply specify its new size. </para> -<para arch="hppa" condition="FIXME"> - -<emphasis>FIXME: write about HP-UX disks?</emphasis> - -</para><para> - -Creating and deleting partitions can be done from within &d-i; as -well as from an existing operating system. As a rule of thumb, -partitions should be created by the system for which they are to -be used, i.e. partitions to be used by &debian-gnu; should be -created from within &d-i; and partitions to be used from another -operating system should be created from there. &d-i; is -capable of creating non-&arch-kernel; partitions, and partitions created -this way usually work without problems when used in other operating -systems, but there are a few rare corner cases in which this could -cause problems, so if you want to be sure, use the native partitioning -tools to create partitions for use by other operating systems. -</para><para> - -If you are going to install more than one operating system on the same -machine, you should install all other system(s) before proceeding with -the &debian; installation. Windows and other OS installations may destroy -your ability to start &debian;, or encourage you to reformat non-native -partitions. - -</para><para> - -You can recover from these actions or avoid them, but installing -the native system first saves you trouble. - -</para><para arch="powerpc"> +<!-- +<para arch="powerpc"> In order for OpenFirmware to automatically boot &debian-gnu; the &arch-parttype; partitions should appear before all other partitions on the disk, @@ -117,66 +88,8 @@ tools later during the actual install, and replace it with &arch-parttype; partitions. </para> - -<!-- paragraph scheduled for removal -<para> - -If you currently have one hard disk with one partition (a common setup -for desktop computers), and you want to multi-boot the native -operating system and &debian;, you will need to: - - <orderedlist> -<listitem><para> - -Back up everything on the computer. - -</para></listitem> -<listitem><para> - -Boot from the native operating system installer media such as CD-ROM -or tapes. - -<phrase arch="powerpc">When booting from a MacOS CD, hold the -<keycap>c</keycap> key while -booting to force the CD to become the active MacOS system.</phrase> - -</para></listitem> -<listitem><para> - -Use the native partitioning tools to create native system -partition(s). Leave either a place holder partition or free space for -&debian-gnu;. - -</para></listitem> -<listitem><para> - -Install the native operating system on its new partition. - -</para></listitem> -<listitem><para> - -Boot back into the native system to verify everything's OK, - and to download the &debian; installer boot files. - -</para></listitem> -<listitem><para> - -Boot the &debian; installer to continue installing &debian;. - -</para></listitem> -</orderedlist> - -</para> ---> - -<!-- &nondeb-part-x86.xml; currently includes only outdated information; - don't use it for building the manual. - -&nondeb-part-x86.xml; - --> -&nondeb-part-sparc.xml; &nondeb-part-powerpc.xml; </sect1> diff --git a/en/preparing/nondeb-part/powerpc.xml b/en/preparing/nondeb-part/powerpc.xml index 6681589f4..c88b75c91 100644 --- a/en/preparing/nondeb-part/powerpc.xml +++ b/en/preparing/nondeb-part/powerpc.xml @@ -2,6 +2,7 @@ <!-- $Id$ --> +<!-- <sect2 arch="powerpc"><title>Mac OS X Partitioning</title> <para> @@ -37,3 +38,4 @@ file systems are supported by MacOS 9, Mac OS X and GNU/Linux. </para> </sect2> +--> diff --git a/en/preparing/nondeb-part/sparc.xml b/en/preparing/nondeb-part/sparc.xml deleted file mode 100644 index 040feb008..000000000 --- a/en/preparing/nondeb-part/sparc.xml +++ /dev/null @@ -1,41 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- $Id$ --> - - - <sect2 arch="sparc"><title>Partitioning from SunOS</title> - -<para> - -It's perfectly fine to partition from SunOS; in fact, if you intend to -run both SunOS and &debian; on the same machine, it is recommended that -you partition using SunOS prior to installing &debian;. The Linux -kernel understands Sun disk labels, so there are no problems there. -SILO supports booting Linux and SunOS from any of EXT2 (Linux), UFS -(SunOS), romfs or iso9660 (CDROM) partitions. - -</para> - </sect2> - - <sect2 arch="sparc"><title>Partitioning from Linux or another OS</title> - -<para> - -Whatever system you are using to partition, make sure you create a -<quote>Sun disk label</quote> on your boot disk. This is the only kind of -partition scheme that the OpenBoot PROM understands, and so it's the -only scheme from which you can boot. In <command>fdisk</command>, the -<keycap>s</keycap> key is used to create Sun disk labels. You only need to do this -on drives that do not already have a Sun disk label. If you are using a -drive that was previously formatted using a PC (or other architecture) you -must create a new disk label, or problems with the disk geometry will most -likely occur. - -</para><para> - -You will probably be using <command>SILO</command> as your boot loader (the -small program which runs the operating system kernel). -<command>SILO</command> has certain requirements for partition sizes and -location; see <xref linkend="partitioning"/>. - -</para> - </sect2> diff --git a/en/preparing/pre-install-bios-setup.xml b/en/preparing/pre-install-bios-setup.xml index aa80fff54..13ba18ec8 100644 --- a/en/preparing/pre-install-bios-setup.xml +++ b/en/preparing/pre-install-bios-setup.xml @@ -16,7 +16,6 @@ hardware; it is most critically invoked during the bootstrap process &bios-setup-i386.xml; &bios-setup-powerpc.xml; -&bios-setup-sparc.xml; &bios-setup-s390.xml; &bios-setup-arm.xml; @@ -127,7 +126,7 @@ hardware; it is most critically invoked during the bootstrap process </para> </sect2> - <sect2 arch="x86;powerpc" id="hardware-issues"> + <sect2 arch="x86" id="hardware-issues"> <title>Hardware Issues to Watch Out For</title> <formalpara arch="x86"> @@ -144,6 +143,7 @@ keyboard emulation</quote> or <quote>USB keyboard support</quote> options. </para> </formalpara> +<!-- <formalpara arch="powerpc"> <title>Display-visibility on OldWorld Powermacs</title> @@ -159,5 +159,7 @@ colors instead of <quote>thousands</quote> or <quote>millions</quote>. </para> </formalpara> +--> + </sect2> </sect1> diff --git a/en/using-d-i/components.xml b/en/using-d-i/components.xml index 702185e97..f2a627cae 100644 --- a/en/using-d-i/components.xml +++ b/en/using-d-i/components.xml @@ -94,9 +94,6 @@ like RAID, LVM or encrypted devices. &module-s390-dasd.xml; &module-partman.xml; -&module-autopartkit.xml; -&module-partitioner.xml; -&module-partconf.xml; &module-partman-md.xml; &module-partman-lvm.xml; &module-partman-crypto.xml; @@ -139,22 +136,13 @@ network connection. If you are installing a diskless workstation, obviously, booting off the local disk isn't a meaningful option, and this step will be -skipped. <phrase arch="sparc">You may wish to set OpenBoot to boot -from the network by default; see <xref -linkend="boot-dev-select-sun"/>.</phrase> +skipped. </para> &module-os-prober.xml; -&module-hppa-palo-installer.xml; &module-x86-grub-installer.xml; -&module-ia64-elilo-installer.xml; -&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; &module-nobootloader.xml; </sect2> diff --git a/en/using-d-i/modules/autopartkit.xml b/en/using-d-i/modules/autopartkit.xml deleted file mode 100644 index 67c575a36..000000000 --- a/en/using-d-i/modules/autopartkit.xml +++ /dev/null @@ -1,2 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- $Id$ --> diff --git a/en/using-d-i/modules/hppa/palo-installer.xml b/en/using-d-i/modules/hppa/palo-installer.xml deleted file mode 100644 index eb5398812..000000000 --- a/en/using-d-i/modules/hppa/palo-installer.xml +++ /dev/null @@ -1,20 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- $Id$ --> - - <sect3 arch="hppa"> - <title><command>palo</command>-installer</title> -<para> - -The bootloader on PA-RISC is <quote>palo</quote>. -<command>PALO</command> is similar in configuration and usage to -<command>LILO</command>, with a few exceptions. First of all, -<command>PALO</command> allows you to boot any kernel image on your -boot partition. This is because <command>PALO</command> can actually -read Linux partitions. - -</para><para condition="FIXME"> - -hppa FIXME ( need more info ) - -</para> - </sect3> diff --git a/en/using-d-i/modules/ia64/elilo-installer.xml b/en/using-d-i/modules/ia64/elilo-installer.xml deleted file mode 100644 index ff117d5c1..000000000 --- a/en/using-d-i/modules/ia64/elilo-installer.xml +++ /dev/null @@ -1,135 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- $Id$ --> - - <sect3 arch="ia64"> - <title>Install the <command>ELILO</command> Boot Loader - on a Hard Disk</title> -<para> - -The &architecture; boot loader is called <quote>elilo</quote>. -It is modeled on the <quote>lilo</quote> boot loader for the -x86 architecture and uses a similar configuration file. -However, instead of writing an MBR or partition boot record to -the disk, it copies the necessary files to a separate FAT formatted -disk partition and modifies the <guimenuitem>EFI Boot Manager</guimenuitem> -menu in the firmware to point to the files in the EFI partition. -The <command>elilo</command> boot loader is really in two parts. -The <filename>/usr/sbin/elilo</filename> command manages the partition and -copies files into it. -The <filename>elilo.efi</filename> program is copied into the EFI -partition and then run by the <quote>EFI Boot Manager</quote> to -do the actual work of loading and starting the Linux kernel. - -</para><para> - -The <quote>elilo</quote> configuration and installation is done as the -last step of installing the packages of the base installation. -&d-i; will present you with a list of potential disk partitions that it -has found suitable for an EFI partition. -Select the partition you set up earlier in the installation, typically -a partition on the same disk that contains your -<emphasis>root</emphasis> filesystem. - -</para> - - <warning><title>Choose the correct partition!</title> - -<para> - -The criterion for selecting a partition is that it must be a FAT format -filesystem with its <emphasis>boot</emphasis> flag set. -&d-i; may show multiple choices depending on what it finds from scanning -all of the disks of the system including EFI partitions of other system -disks and EFI diagnostic partitions. -Remember, <command>elilo</command> may format the partition during -the installation, erasing any previous contents! - -</para></warning> - - </sect3> - - <sect3 arch="ia64"> - <title>EFI Partition Contents</title> - -<para> - -The EFI partition is a FAT filesystem format partition on one of the -hard disks of the system, usually the same disk that contains the -<emphasis>root</emphasis> filesystem. -It is normally not mounted on a running system as it is only needed -by the <quote>EFI Boot Manager</quote> to load the system and the -installer part of the <command>elilo</command> writes to the filesystem -directly. -The <command>/usr/sbin/elilo</command> utility writes the following files -into the <filename>efi/debian</filename> directory of the EFI -partition during the installation. -Note that the <quote>EFI Boot Manager</quote> would find these files -using the path <filename>fs<replaceable>n</replaceable>:\efi\debian</filename>. -There may be other files in this filesystem as well over time as -the system is updated or re-configured. - -</para> - -<variablelist> - -<varlistentry> -<term><filename>elilo.conf</filename></term> -<listitem><para> - -This is the configuration file read by the boot loader when it starts. -It is a copy of the <filename>/etc/elilo.conf</filename> with -the filenames re-written to refer to files in the EFI partition. - -</para></listitem></varlistentry> - -<varlistentry> -<term><filename>elilo.efi</filename></term> -<listitem><para> - -This is the boot loader program that the <quote>EFI Boot Manager</quote> -runs to boot the system. -It is the program behind the <guimenuitem>&debian; GNU/Linux</guimenuitem> -menu item of the <quote>EFI Boot Manager</quote> command menu. - -</para></listitem></varlistentry> - -<varlistentry> -<term><filename>initrd.img</filename></term> -<listitem><para> - -This is the initial root filesystem used to boot the kernel. -It is a copy of the file referenced in the -<filename>/etc/elilo.conf</filename>. -In a standard &debian; installation it would be the file in -<filename>/boot</filename> pointed to by the symbolic link -<filename>/initrd.img</filename>. - -</para></listitem></varlistentry> - -<varlistentry> -<term><filename>readme.txt</filename></term> -<listitem><para> - -This is a small text file warning you that the contents of the -directory are managed by the <command>elilo</command> and that -any local changes would be lost at the next time -<filename>/usr/sbin/elilo</filename> is run. - -</para></listitem></varlistentry> - -<varlistentry> -<term><filename>vmlinuz</filename></term> -<listitem><para> - -This is the compressed kernel itself. -It is a copy of the file referenced in the -<filename>/etc/elilo.conf</filename>. -In a standard &debian; installation it would be the file in -<filename>/boot</filename> pointed to by the symbolic link -<filename>/vmlinuz</filename>. - -</para></listitem></varlistentry> - -</variablelist> - - </sect3> diff --git a/en/using-d-i/modules/mipsel/colo-installer.xml b/en/using-d-i/modules/mipsel/colo-installer.xml deleted file mode 100644 index 67c575a36..000000000 --- a/en/using-d-i/modules/mipsel/colo-installer.xml +++ /dev/null @@ -1,2 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- $Id$ --> diff --git a/en/using-d-i/modules/partconf.xml b/en/using-d-i/modules/partconf.xml deleted file mode 100644 index 67c575a36..000000000 --- a/en/using-d-i/modules/partconf.xml +++ /dev/null @@ -1,2 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- $Id$ --> diff --git a/en/using-d-i/modules/partitioner.xml b/en/using-d-i/modules/partitioner.xml deleted file mode 100644 index 53394db87..000000000 --- a/en/using-d-i/modules/partitioner.xml +++ /dev/null @@ -1,3 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- $Id$ --> - diff --git a/en/using-d-i/modules/partman.xml b/en/using-d-i/modules/partman.xml index e880d4800..bb56e017f 100644 --- a/en/using-d-i/modules/partman.xml +++ b/en/using-d-i/modules/partman.xml @@ -7,21 +7,7 @@ If you are uncomfortable with partitioning, or just want to know more details, see <xref linkend="partitioning"/>. </para> -<warning arch="sparc"><para> -<!-- BTS: #384653 --> -If a hard disk has previously used under Solaris, the partitioner may not -detect the size of the drive correctly. Creating a new partition table -does not fix this issue. What does help, is to <quote>zero</quote> the -first few sectors of the drive: - -<informalexample><screen> -# dd if=/dev/zero of=/dev/sd<replaceable>X</replaceable> bs=512 count=2; sync -</screen></informalexample> - -Note that this will make any existing data on that disk inaccessible. - -</para></warning> <para> First you will be given the opportunity to automatically partition @@ -162,7 +148,7 @@ The following file systems are supported. <listitem><para> <emphasis>FAT16</emphasis>, <emphasis>FAT32</emphasis> </para></listitem> - <listitem arch="x86;ia64"><para> + <listitem arch="x86"><para> <emphasis>NTFS</emphasis> (read-only) </para><para> Existing NTFS partitions can be resized and it is possible to assign diff --git a/en/using-d-i/modules/powerpc/quik-installer.xml b/en/using-d-i/modules/powerpc/quik-installer.xml deleted file mode 100644 index 07ba1e66b..000000000 --- a/en/using-d-i/modules/powerpc/quik-installer.xml +++ /dev/null @@ -1,15 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- $Id$ --> - - <sect3 arch="powerpc"> - <title>Install <command>Quik</command> on a Hard Disk</title> -<para> - -The boot loader for OldWorld Power Macintosh machines is -<command>quik</command>. You can also use it on CHRP. The installer -will attempt to set up <command>quik</command> automatically. The -setup has been known to work on 7200, 7300, and 7600 Powermacs, and on -some Power Computing clones. - -</para> - </sect3> diff --git a/en/using-d-i/modules/powerpc/yaboot-installer.xml b/en/using-d-i/modules/powerpc/yaboot-installer.xml deleted file mode 100644 index 29383ae5d..000000000 --- a/en/using-d-i/modules/powerpc/yaboot-installer.xml +++ /dev/null @@ -1,17 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- $Id$ --> - - <sect3 arch="powerpc"> - <title>Install <command>Yaboot</command> on a Hard Disk</title> -<para> - -Newer (mid 1998 and on) PowerMacs use <command>yaboot</command> as -their boot loader. The installer will set up <command>yaboot</command> -automatically, so all you need is a small 820k partition named -<quote>bootstrap</quote> with type -<emphasis>Apple_Bootstrap</emphasis> created back in the partitioning -component. If this step completes successfully then your disk should -now be bootable and OpenFirmware will be set to boot &debian-gnu;. - -</para> - </sect3> diff --git a/en/using-d-i/modules/sparc/silo-installer.xml b/en/using-d-i/modules/sparc/silo-installer.xml deleted file mode 100644 index fe6d0f607..000000000 --- a/en/using-d-i/modules/sparc/silo-installer.xml +++ /dev/null @@ -1,25 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- $Id$ --> - - <sect3 arch="sparc"> - <title>Install the <command>SILO</command> Boot Loader - on a Hard Disk</title> -<para> - -The standard &architecture; boot loader is called <quote>silo</quote>. -It is documented in -<filename>/usr/share/doc/silo/</filename>. <command>SILO</command> is -similar in configuration and usage to <command>LILO</command>, with -a few exceptions. First of all, <command>SILO</command> allows you to -boot any kernel image on your drive, even if it is not listed in -<filename>/etc/silo.conf</filename>. This is because -<command>SILO</command> can actually read Linux partitions. Also, -<filename>/etc/silo.conf</filename> is read at boot time, so there is -no need to rerun <command>silo</command> after installing a new kernel -like you would with <command>LILO</command>. <command>SILO</command> -can also read UFS partitions, which means it can boot SunOS/Solaris -partitions as well. This is useful if you want to install GNU/Linux -alongside an existing SunOS/Solaris install. - -</para> - </sect3> diff --git a/en/using-d-i/modules/x86/lilo-installer.xml b/en/using-d-i/modules/x86/lilo-installer.xml deleted file mode 100644 index cc22d1e0f..000000000 --- a/en/using-d-i/modules/x86/lilo-installer.xml +++ /dev/null @@ -1,67 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- $Id$ --> - - <sect3 arch="x86"> - <title>Install the <command>LILO</command> Boot Loader - on a Hard Disk</title> -<para> - -The second &architecture; boot loader is called <quote>LILO</quote>. -It is an old complex program which offers lots of functionality, -including DOS, Windows, and OS/2 boot management. Please carefully -read the instructions in the directory -<filename>/usr/share/doc/lilo/</filename> if you have special needs; -also see the <ulink url="&url-lilo-howto;">LILO mini-HOWTO</ulink>. - -</para> -<note><para> - -Currently the LILO installation will only create menu entries for other -operating systems if these can be <firstterm>chainloaded</firstterm>. -This means you may have to manually add a menu entry for operating -systems like GNU/Linux and GNU/Hurd after the installation. - -</para></note> -<para> - -&d-i; offers you three choices on where to install the -<command>LILO</command> boot loader: - -<variablelist> -<varlistentry> -<term>Master Boot Record (MBR)</term><listitem><para> - -This way the <command>LILO</command> will take complete control of the -boot process. - -</para></listitem></varlistentry> -<varlistentry> -<term>new &debian; partition</term><listitem><para> - -Choose this if you want to use another boot -manager. <command>LILO</command> will install itself at the beginning -of the new &debian; partition and it will serve as a secondary boot -loader. - -</para></listitem></varlistentry> -<varlistentry> -<term>Other choice</term><listitem><para> - -Useful for advanced users who want to install <command>LILO</command> -somewhere else. In this case you will be asked for desired -location. You can use traditional device names such as -<filename>/dev/sda</filename>. - -</para></listitem></varlistentry> -</variablelist> - -</para><para> - -If you can no longer boot into Windows 9x (or DOS) after this step, -you'll need to use a Windows 9x (MS-DOS) boot disk and use the -<userinput>fdisk /mbr</userinput> command to reinstall the MS-DOS -master boot record — however, this means that you'll need to use -some other way to get back into &debian;! - -</para> - </sect3> diff --git a/en/using-d-i/using-d-i.xml b/en/using-d-i/using-d-i.xml index a8da81983..e4f3cc59a 100644 --- a/en/using-d-i/using-d-i.xml +++ b/en/using-d-i/using-d-i.xml @@ -22,7 +22,10 @@ used by default unless you select an <quote>Graphical install</quote> option in the boot menu. For more information about booting the graphical installer, please refer to <xref linkend="graphical"/>. -</para><para arch="powerpc"> +</para> + +<!-- +<para arch="powerpc"> For this architecture the &d-i; supports two different user interfaces: a text-based one and a graphical one. The text-based interface is @@ -30,7 +33,10 @@ used by default unless you select an <quote>Graphical install</quote> option in the boot menu. For more information about booting the graphical installer, please refer to <xref linkend="graphical"/>. -</para><para condition="not-gtk"> +</para> +--> + +<para condition="not-gtk"> For this architecture the installer uses a text-based user interface. A graphical user interface is currently not available. @@ -335,25 +341,6 @@ in &debian;. </varlistentry> <varlistentry> -<term>partitioner</term><listitem><para> - -Allows the user to partition disks attached to the system. A -partitioning program appropriate to your computer's architecture -is chosen. - -</para></listitem> -</varlistentry> -<varlistentry> - -<term>partconf</term><listitem><para> - -Displays a list of partitions, and creates file systems on -the selected partitions according to user instructions. - -</para></listitem> -</varlistentry> -<varlistentry> - <term>partman-lvm</term><listitem><para> Helps the user with the configuration of the |