diff options
| author | Felipe Augusto van de Wiel <faw@debian.org> | 2007-07-26 04:05:43 +0000 |
|---|---|---|
| committer | Felipe Augusto van de Wiel <faw@debian.org> | 2007-07-26 04:05:43 +0000 |
| commit | 2ceebfd3c833bf3e65f537cfbc9693b8a94106e5 (patch) | |
| tree | c2ba242c9547a8c23de5c63e5b2574380a998558 /po/pot | |
| parent | 7afb7da18c66015e9f428dd67f75b16cb6aeb91f (diff) | |
| download | installation-guide-2ceebfd3c833bf3e65f537cfbc9693b8a94106e5.zip | |
[SILENT_COMMIT] Update of POT and PO files for the manual
Diffstat (limited to 'po/pot')
| -rw-r--r-- | po/pot/boot-installer.pot | 341 | ||||
| -rw-r--r-- | po/pot/hardware.pot | 958 | ||||
| -rw-r--r-- | po/pot/preparing.pot | 6 | ||||
| -rw-r--r-- | po/pot/preseed.pot | 18 | ||||
| -rw-r--r-- | po/pot/using-d-i.pot | 160 |
5 files changed, 740 insertions, 743 deletions
diff --git a/po/pot/boot-installer.pot b/po/pot/boot-installer.pot index 7482d0192..6d7af2a84 100644 --- a/po/pot/boot-installer.pot +++ b/po/pot/boot-installer.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2007-07-19 05:14+0000\n" +"POT-Creation-Date: 2007-07-26 04:00+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <LL@li.org>\n" @@ -753,7 +753,7 @@ msgid "Let's assume you have prepared everything from <xref linkend=\"boot-dev-s msgstr "" #. Tag: title -#: boot-installer.xml:957 boot-installer.xml:2066 boot-installer.xml:2569 boot-installer.xml:2712 +#: boot-installer.xml:957 boot-installer.xml:2066 boot-installer.xml:2569 #, no-c-format msgid "Booting from Floppies" msgstr "" @@ -1493,7 +1493,7 @@ msgid "" msgstr "" #. Tag: title -#: boot-installer.xml:2132 boot-installer.xml:2236 boot-installer.xml:2770 +#: boot-installer.xml:2132 boot-installer.xml:2236 boot-installer.xml:2729 #, no-c-format msgid "Boot Parameters" msgstr "" @@ -1761,69 +1761,38 @@ msgstr "" msgid "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)." msgstr "" -#. Tag: para -#: boot-installer.xml:2713 -#, no-c-format -msgid "Floppy images are currently only available for sparc32, but, for technical reasons, not for official releases. (The reason is that they can only be built as root, which is not supported by our build daemons.) Look under <quote>daily built images</quote> on the <ulink url=\"&url-d-i;\">Debian Installer project website</ulink> for links to floppy images for sparc32." -msgstr "" - -#. Tag: para -#: boot-installer.xml:2722 -#, no-c-format -msgid "" - "To boot from floppy on a Sparc, use <informalexample><screen>\n" - "Stop-A -> OpenBoot: \"boot floppy\"\n" - "</screen></informalexample> Be warned that the newer Sun4u (ultra) architecture does not support floppy booting. A typical error message is <computeroutput>Bad magic number in disk label - Can't open disk label package</computeroutput>." -msgstr "" - -#. Tag: para -#: boot-installer.xml:2732 -#, no-c-format -msgid "Several Sparcs (e.g. Ultra 10) have an OBP bug that prevents them from booting (instead of not supporting booting at all). The appropriate OBP update can be downloaded as product ID 106121 from <ulink url=\"http://sunsolve.sun.com\"></ulink>." -msgstr "" - -#. Tag: para -#: boot-installer.xml:2739 -#, no-c-format -msgid "" - "If you are booting from the floppy, and you see messages such as <informalexample><screen>\n" - "Fatal error: Cannot read partition\n" - "Illegal or malformed device name\n" - "</screen></informalexample> then it is possible that floppy booting is simply not supported on your machine." -msgstr "" - #. Tag: title -#: boot-installer.xml:2751 +#: boot-installer.xml:2710 #, no-c-format msgid "IDPROM Messages" msgstr "" #. Tag: para -#: boot-installer.xml:2752 +#: boot-installer.xml:2711 #, no-c-format msgid "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." msgstr "" #. Tag: para -#: boot-installer.xml:2771 +#: boot-installer.xml:2730 #, no-c-format msgid "Boot parameters are Linux kernel parameters which are generally used to make sure that peripherals are dealt with properly. For the most part, the kernel can auto-detect information about your peripherals. However, in some cases you'll have to help the kernel a bit." msgstr "" #. Tag: para -#: boot-installer.xml:2778 +#: boot-installer.xml:2737 #, no-c-format msgid "If this is the first time you're booting the system, try the default boot parameters (i.e., don't try setting parameters) and see if it works correctly. It probably will. If not, you can reboot later and look for any special parameters that inform the system about your hardware." msgstr "" #. Tag: para -#: boot-installer.xml:2785 +#: boot-installer.xml:2744 #, no-c-format msgid "Information on many boot parameters can be found in the <ulink url=\"http://www.tldp.org/HOWTO/BootPrompt-HOWTO.html\"> Linux BootPrompt HOWTO</ulink>, including tips for obscure hardware. This section contains only a sketch of the most salient parameters. Some common gotchas are included below in <xref linkend=\"boot-troubleshooting\"/>." msgstr "" #. Tag: para -#: boot-installer.xml:2794 +#: boot-installer.xml:2753 #, no-c-format msgid "" "When the kernel boots, a message <informalexample><screen>\n" @@ -1832,463 +1801,463 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:2810 +#: boot-installer.xml:2769 #, no-c-format msgid "If you are booting with a serial console, generally the kernel will autodetect this<phrase arch=\"mipsel\"> (although not on DECstations)</phrase>. If you have a videocard (framebuffer) and a keyboard also attached to the computer which you wish to boot via serial console, you may have to pass the <userinput>console=<replaceable>device</replaceable></userinput> argument to the kernel, where <replaceable>device</replaceable> is your serial device, which is usually something like <filename>ttyS0</filename>." msgstr "" #. Tag: para -#: boot-installer.xml:2823 +#: boot-installer.xml:2782 #, no-c-format msgid "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>." msgstr "" #. Tag: title -#: boot-installer.xml:2834 +#: boot-installer.xml:2793 #, no-c-format msgid "Debian Installer Parameters" msgstr "" #. Tag: para -#: boot-installer.xml:2835 +#: boot-installer.xml:2794 #, no-c-format msgid "The installation system recognizes a few additional boot parameters<footnote> <para> With current kernels (2.6.9 or newer) you can use 32 command line options and 32 environment options. If these numbers are exceeded, the kernel will panic. </para> </footnote> which may be useful." msgstr "" #. Tag: para -#: boot-installer.xml:2848 +#: boot-installer.xml:2807 #, no-c-format msgid "A number of parameters have a <quote>short form</quote> that helps avoid the limitations of the kernel command line options and makes entering the parameters easier. If a parameter has a short form, it will be listed in brackets behind the (normal) long form. Examples in this manual will normally use the short form too." msgstr "" #. Tag: term -#: boot-installer.xml:2860 +#: boot-installer.xml:2819 #, no-c-format msgid "debconf/priority (priority)" msgstr "" #. Tag: para -#: boot-installer.xml:2861 +#: boot-installer.xml:2820 #, no-c-format msgid "This parameter sets the lowest priority of messages to be displayed." msgstr "" #. Tag: para -#: boot-installer.xml:2865 +#: boot-installer.xml:2824 #, no-c-format msgid "The default installation uses <userinput>priority=high</userinput>. This means that both high and critical priority messages are shown, but medium and low priority messages are skipped. If problems are encountered, the installer adjusts the priority as needed." msgstr "" #. Tag: para -#: boot-installer.xml:2872 +#: boot-installer.xml:2831 #, no-c-format msgid "If you add <userinput>priority=medium</userinput> as boot parameter, you will be shown the installation menu and gain more control over the installation. When <userinput>priority=low</userinput> is used, all messages are shown (this is equivalent to the <emphasis>expert</emphasis> boot method). With <userinput>priority=critical</userinput>, the installation system will display only critical messages and try to do the right thing without fuss." msgstr "" #. Tag: term -#: boot-installer.xml:2886 +#: boot-installer.xml:2845 #, no-c-format msgid "DEBIAN_FRONTEND" msgstr "" #. Tag: para -#: boot-installer.xml:2887 +#: boot-installer.xml:2846 #, no-c-format msgid "This boot parameter controls the type of user interface used for the installer. The current possible parameter settings are: <itemizedlist> <listitem> <para><userinput>DEBIAN_FRONTEND=noninteractive</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=text</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=newt</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=gtk</userinput></para> </listitem> </itemizedlist> The default frontend is <userinput>DEBIAN_FRONTEND=newt</userinput>. <userinput>DEBIAN_FRONTEND=text</userinput> may be preferable for serial console installs. Generally, only the <userinput>newt</userinput> frontend is available on default install media. On architectures that support it, the graphical installer uses the <userinput>gtk</userinput> frontend." msgstr "" #. Tag: term -#: boot-installer.xml:2916 +#: boot-installer.xml:2875 #, no-c-format msgid "BOOT_DEBUG" msgstr "" #. Tag: para -#: boot-installer.xml:2917 +#: boot-installer.xml:2876 #, no-c-format msgid "Setting this boot parameter to 2 will cause the installer's boot process to be verbosely logged. Setting it to 3 makes debug shells available at strategic points in the boot process. (Exit the shells to continue the boot process.)" msgstr "" #. Tag: userinput -#: boot-installer.xml:2926 +#: boot-installer.xml:2885 #, no-c-format msgid "BOOT_DEBUG=0" msgstr "" #. Tag: para -#: boot-installer.xml:2927 +#: boot-installer.xml:2886 #, no-c-format msgid "This is the default." msgstr "" #. Tag: userinput -#: boot-installer.xml:2931 +#: boot-installer.xml:2890 #, no-c-format msgid "BOOT_DEBUG=1" msgstr "" #. Tag: para -#: boot-installer.xml:2932 +#: boot-installer.xml:2891 #, no-c-format msgid "More verbose than usual." msgstr "" #. Tag: userinput -#: boot-installer.xml:2936 +#: boot-installer.xml:2895 #, no-c-format msgid "BOOT_DEBUG=2" msgstr "" #. Tag: para -#: boot-installer.xml:2937 +#: boot-installer.xml:2896 #, no-c-format msgid "Lots of debugging information." msgstr "" #. Tag: userinput -#: boot-installer.xml:2941 +#: boot-installer.xml:2900 #, no-c-format msgid "BOOT_DEBUG=3" msgstr "" #. Tag: para -#: boot-installer.xml:2942 +#: boot-installer.xml:2901 #, no-c-format msgid "Shells are run at various points in the boot process to allow detailed debugging. Exit the shell to continue the boot." msgstr "" #. Tag: term -#: boot-installer.xml:2956 +#: boot-installer.xml:2915 #, no-c-format msgid "INSTALL_MEDIA_DEV" msgstr "" #. Tag: para -#: boot-installer.xml:2957 +#: boot-installer.xml:2916 #, no-c-format msgid "The value of the parameter is the path to the device to load the Debian installer from. For example, <userinput>INSTALL_MEDIA_DEV=/dev/floppy/0</userinput>" msgstr "" #. Tag: para -#: boot-installer.xml:2963 +#: boot-installer.xml:2922 #, no-c-format msgid "The boot floppy, which normally scans all floppies it can to find the root floppy, can be overridden by this parameter to only look at the one device." msgstr "" #. Tag: term -#: boot-installer.xml:2973 +#: boot-installer.xml:2932 #, no-c-format msgid "lowmem" msgstr "" #. Tag: para -#: boot-installer.xml:2974 +#: boot-installer.xml:2933 #, no-c-format msgid "Can be used to force the installer to a lowmem level higher than the one the installer sets by default based on available memory. Possible values are 1 and 2. See also <xref linkend=\"lowmem\"/>." msgstr "" #. Tag: term -#: boot-installer.xml:2984 +#: boot-installer.xml:2943 #, no-c-format msgid "debian-installer/framebuffer (fb)" msgstr "" #. Tag: para -#: boot-installer.xml:2985 +#: boot-installer.xml:2944 #, no-c-format msgid "Some architectures use the kernel framebuffer to offer installation in a number of languages. If framebuffer causes a problem on your system you can disable the feature by the parameter <userinput>fb=false</userinput>. Problem symptoms are error messages about bterm or bogl, a blank screen, or a freeze within a few minutes after starting the install." msgstr "" #. Tag: para -#: boot-installer.xml:2994 +#: boot-installer.xml:2953 #, no-c-format msgid "The <userinput>video=vga16:off</userinput> argument may also be used to disable the kernel's use of the framebuffer. Such problems have been reported on a Dell Inspiron with Mobile Radeon card." msgstr "" #. Tag: para -#: boot-installer.xml:3000 +#: boot-installer.xml:2959 #, no-c-format msgid "Such problems have been reported on the Amiga 1200 and SE/30." msgstr "" #. Tag: para -#: boot-installer.xml:3004 +#: boot-installer.xml:2963 #, no-c-format msgid "Such problems have been reported on hppa." msgstr "" #. Tag: para -#: boot-installer.xml:3008 +#: boot-installer.xml:2967 #, no-c-format msgid "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." msgstr "" #. Tag: term -#: boot-installer.xml:3022 +#: boot-installer.xml:2981 #, no-c-format msgid "debian-installer/theme (theme)" msgstr "" #. Tag: para -#: boot-installer.xml:3023 +#: boot-installer.xml:2982 #, no-c-format msgid "A theme determines how the user interface of the installer looks (colors, icons, etc.). What themes are available differs per frontend. Currently both the newt and gtk frontends only have a <quote>dark</quote> theme that was designed for visually impaired users. Set the theme by booting with <userinput>theme=<replaceable>dark</replaceable></userinput>." msgstr "" #. Tag: term -#: boot-installer.xml:3035 boot-installer.xml:3238 +#: boot-installer.xml:2994 boot-installer.xml:3197 #, no-c-format msgid "netcfg/disable_dhcp" msgstr "" #. Tag: para -#: boot-installer.xml:3036 +#: boot-installer.xml:2995 #, no-c-format msgid "By default, the &d-i; automatically probes for network configuration via DHCP. If the probe succeeds, you won't have a chance to review and change the obtained settings. You can get to the manual network setup only in case the DHCP probe fails." msgstr "" #. Tag: para -#: boot-installer.xml:3043 +#: boot-installer.xml:3002 #, no-c-format msgid "If you have a DHCP server on your local network, but want to avoid it because e.g. it gives wrong answers, you can use the parameter <userinput>netcfg/disable_dhcp=true</userinput> to prevent configuring the network with DHCP and to enter the information manually." msgstr "" #. Tag: term -#: boot-installer.xml:3054 +#: boot-installer.xml:3013 #, no-c-format msgid "hw-detect/start_pcmcia" msgstr "" #. Tag: para -#: boot-installer.xml:3055 +#: boot-installer.xml:3014 #, no-c-format msgid "Set to <userinput>false</userinput> to prevent starting PCMCIA services, if that causes problems. Some laptops are well known for this misbehavior." msgstr "" #. Tag: term -#: boot-installer.xml:3065 +#: boot-installer.xml:3024 #, no-c-format msgid "disk-detect/dmraid/enable (dmraid)" msgstr "" #. Tag: para -#: boot-installer.xml:3066 +#: boot-installer.xml:3025 #, no-c-format msgid "Set to <userinput>true</userinput> to enable support for Serial ATA RAID (also called ATA RAID, BIOS RAID or fake RAID) disks in the installer. Note that this support is currently experimental. Additional information can be found on the <ulink url=\"&url-d-i-wiki;\">Debian Installer Wiki</ulink>." msgstr "" #. Tag: term -#: boot-installer.xml:3077 +#: boot-installer.xml:3036 #, no-c-format msgid "preseed/url (url)" msgstr "" #. Tag: para -#: boot-installer.xml:3078 +#: boot-installer.xml:3037 #, no-c-format msgid "Specify the url to a preconfiguration file to download and use for automating the install. See <xref linkend=\"automatic-install\"/>." msgstr "" #. Tag: term -#: boot-installer.xml:3087 +#: boot-installer.xml:3046 #, no-c-format msgid "preseed/file (file)" msgstr "" #. Tag: para -#: boot-installer.xml:3088 +#: boot-installer.xml:3047 #, no-c-format msgid "Specify the path to a preconfiguration file to load for automating the install. See <xref linkend=\"automatic-install\"/>." msgstr "" #. Tag: term -#: boot-installer.xml:3097 +#: boot-installer.xml:3056 #, no-c-format msgid "preseed/interactive" msgstr "" #. Tag: para -#: boot-installer.xml:3098 +#: boot-installer.xml:3057 #, no-c-format msgid "Set to <userinput>true</userinput> to display questions even if they have been preseeded. Can be useful for testing or debugging a preconfiguration file. Note that this will have no effect on parameters that are passed as boot parameters, but for those a special syntax can be used. See <xref linkend=\"preseed-seenflag\"/> for details." msgstr "" #. Tag: term -#: boot-installer.xml:3110 +#: boot-installer.xml:3069 #, no-c-format msgid "auto-install/enable (auto)" msgstr "" #. Tag: para -#: boot-installer.xml:3111 +#: boot-installer.xml:3070 #, no-c-format msgid "Delay questions that are normally asked before preseeding is possible until after the network is configured. See <xref linkend=\"preseed-auto\"/> for details about using this to automate installs." msgstr "" #. Tag: term -#: boot-installer.xml:3122 +#: boot-installer.xml:3081 #, no-c-format msgid "cdrom-detect/eject" msgstr "" #. Tag: para -#: boot-installer.xml:3123 +#: boot-installer.xml:3082 #, no-c-format msgid "By default, before rebooting, &d-i; automatically ejects the optical media used during the installation. This can be unnecessary if the system does not automatically boot off the CD. In some cases it may even be undesirable, for example if the optical drive cannot reinsert the media itself and the user is not there to do it manually. Many slot loading, slim-line, and caddy style drives cannot reload media automatically." msgstr "" #. Tag: para -#: boot-installer.xml:3132 +#: boot-installer.xml:3091 #, no-c-format msgid "Set to <userinput>false</userinput> to disable automatic ejection, and be aware that you may need to ensure that the system does not automatically boot from the optical drive after the initial installation." msgstr "" #. Tag: term -#: boot-installer.xml:3143 +#: boot-installer.xml:3102 #, no-c-format msgid "debian-installer/allow_unauthenticated" msgstr "" #. Tag: para -#: boot-installer.xml:3144 +#: boot-installer.xml:3103 #, no-c-format msgid "By default the installer requires that repositories be authenticated using a known gpg key. Set to <userinput>true</userinput> to disable that authentication. <emphasis role=\"bold\">Warning: insecure, not recommended.</emphasis>" msgstr "" #. Tag: term -#: boot-installer.xml:3155 +#: boot-installer.xml:3114 #, no-c-format msgid "ramdisk_size" msgstr "" #. Tag: para -#: boot-installer.xml:3156 +#: boot-installer.xml:3115 #, no-c-format msgid "This parameter should already be set to a correct value where needed; set it only it you see errors during the boot that indicate the ramdisk could not be loaded completely. The value is in kB." msgstr "" #. Tag: term -#: boot-installer.xml:3166 +#: boot-installer.xml:3125 #, no-c-format msgid "mouse/left" msgstr "" #. Tag: para -#: boot-installer.xml:3167 +#: boot-installer.xml:3126 #, no-c-format msgid "For the gtk frontend (graphical installer), users can switch the mouse to left-handed operation by setting this parameter to <userinput>true</userinput>." msgstr "" #. Tag: term -#: boot-installer.xml:3176 +#: boot-installer.xml:3135 #, no-c-format msgid "directfb/hw-accel" msgstr "" #. Tag: para -#: boot-installer.xml:3177 +#: boot-installer.xml:3136 #, no-c-format msgid "For the gtk frontend (graphical installer), hardware acceleration in directfb is disabled by default. Set this parameter to <userinput>true</userinput> to enable it." msgstr "" #. Tag: term -#: boot-installer.xml:3187 +#: boot-installer.xml:3146 #, no-c-format msgid "rescue/enable" msgstr "" #. Tag: para -#: boot-installer.xml:3188 +#: boot-installer.xml:3147 #, no-c-format msgid "Set to <userinput>true</userinput> to enter rescue mode rather than performing a normal installation. See <xref linkend=\"rescue\"/>." msgstr "" #. Tag: title -#: boot-installer.xml:3199 +#: boot-installer.xml:3158 #, no-c-format msgid "Using boot parameters to answer questions" msgstr "" #. Tag: para -#: boot-installer.xml:3200 +#: boot-installer.xml:3159 #, no-c-format msgid "With some exceptions, a value can be set at the boot prompt for any question asked during the installation, though this is only really useful in specific cases. General instructions how to do this can be found in <xref linkend=\"preseed-bootparms\"/>. Some specific examples are listed below." msgstr "" #. Tag: term -#: boot-installer.xml:3212 +#: boot-installer.xml:3171 #, no-c-format msgid "debian-installer/locale (locale)" msgstr "" #. Tag: para -#: boot-installer.xml:3213 +#: boot-installer.xml:3172 #, no-c-format msgid "Can be used to set both the language and country for the installation. This will only work if the locale is supported in Debian. For example, use <userinput>locale=de_CH</userinput> to select German as language and Switzerland as country." msgstr "" #. Tag: term -#: boot-installer.xml:3224 +#: boot-installer.xml:3183 #, no-c-format msgid "anna/choose_modules (modules)" msgstr "" #. Tag: para -#: boot-installer.xml:3225 +#: boot-installer.xml:3184 #, no-c-format msgid "Can be used to automatically load installer components that are not loaded by default. Examples of optional components that may be useful are <classname>openssh-client-udeb</classname> (so you can use <command>scp</command> during the installation)<phrase arch=\"not-s390\"> and <classname>ppp-udeb</classname> (see <xref linkend=\"pppoe\"/>)</phrase>." msgstr "" #. Tag: para -#: boot-installer.xml:3239 +#: boot-installer.xml:3198 #, no-c-format msgid "Set to <userinput>true</userinput> if you want to disable DHCP and instead force static network configuration." msgstr "" #. Tag: term -#: boot-installer.xml:3248 +#: boot-installer.xml:3207 #, no-c-format msgid "mirror/protocol (protocol)" msgstr "" #. Tag: para -#: boot-installer.xml:3249 +#: boot-installer.xml:3208 #, no-c-format msgid "By default the installer will use the http protocol to download files from Debian mirrors and changing that to ftp is not possible during installations at normal priority. By setting this parameter to <userinput>ftp</userinput>, you can force the installer to use that protocol instead. Note that you cannot select an ftp mirror from a list, you have to enter the hostname manually." msgstr "" #. Tag: term -#: boot-installer.xml:3262 +#: boot-installer.xml:3221 #, no-c-format msgid "tasksel:tasksel/first (tasks)" msgstr "" #. Tag: para -#: boot-installer.xml:3263 +#: boot-installer.xml:3222 #, no-c-format msgid "Can be used to select tasks that are not available from the interactive task list, such as the <literal>kde-desktop</literal> task. See <xref linkend=\"pkgsel\"/> for additional information." msgstr "" #. Tag: title -#: boot-installer.xml:3277 +#: boot-installer.xml:3236 #, no-c-format msgid "Passing parameters to kernel modules" msgstr "" #. Tag: para -#: boot-installer.xml:3278 +#: boot-installer.xml:3237 #, no-c-format msgid "If drivers are compiled into the kernel, you can pass parameters to them as described in the kernel documentation. However, if drivers are compiled as modules and because kernel modules are loaded a bit differently during an installation than when booting an installed system, it is not possible to pass parameters to modules as you would normally do. Instead, you need to use a special syntax recognized by the installer which will then make sure that the parameters are saved in the proper configuration files and will thus be used when the modules are actually loaded. The parameters will also be propagated automatically to the configuration for the installed system." msgstr "" #. Tag: para -#: boot-installer.xml:3291 +#: boot-installer.xml:3250 #, no-c-format msgid "Note that it is now quite rare that parameters need to be passed to modules. In most cases the kernel will be able to probe the hardware present in a system and set good defaults that way. However, in some situations it may still be needed to set parameters manually." msgstr "" #. Tag: para -#: boot-installer.xml:3298 +#: boot-installer.xml:3257 #, no-c-format msgid "" "The syntax to use to set parameters for modules is: <informalexample><screen>\n" @@ -2297,133 +2266,133 @@ msgid "" msgstr "" #. Tag: screen -#: boot-installer.xml:3308 +#: boot-installer.xml:3267 #, no-c-format msgid "3c509.xcvr=3 3c509.irq=10" msgstr "" #. Tag: title -#: boot-installer.xml:3314 +#: boot-installer.xml:3273 #, no-c-format msgid "Blacklisting kernel modules" msgstr "" #. Tag: para -#: boot-installer.xml:3315 +#: boot-installer.xml:3274 #, no-c-format msgid "Sometimes it may be necessary to blacklist a module to prevent it from being loaded automatically by the kernel and udev. One reason could be that a particular module causes problems with your hardware. The kernel also sometimes lists two different drivers for the same device. This can cause the device to not work correctly if the drivers conflict or if the wrong driver is loaded first." msgstr "" #. Tag: para -#: boot-installer.xml:3324 +#: boot-installer.xml:3283 #, no-c-format msgid "You can blacklist a module using the following syntax: <userinput><replaceable>module_name</replaceable>.blacklist=yes</userinput>. This will cause the module to be blacklisted in <filename>/etc/modprobe.d/blacklist.local</filename> both during the installation and for the installed system." msgstr "" #. Tag: para -#: boot-installer.xml:3332 +#: boot-installer.xml:3291 #, no-c-format msgid "Note that a module may still be loaded by the installation system itself. You can prevent that from happening by running the installation in expert mode and unselecting the module from the list of modules displayed during the hardware detection phases." msgstr "" #. Tag: title -#: boot-installer.xml:3349 +#: boot-installer.xml:3308 #, no-c-format msgid "Troubleshooting the Installation Process" msgstr "" #. Tag: title -#: boot-installer.xml:3354 +#: boot-installer.xml:3313 #, no-c-format msgid "CD-ROM Reliability" msgstr "" #. Tag: para -#: boot-installer.xml:3355 +#: boot-installer.xml:3314 #, no-c-format msgid "Sometimes, especially with older CD-ROM drives, the installer may fail to boot from a CD-ROM. The installer may also — even after booting successfully from CD-ROM — fail to recognize the CD-ROM or return errors while reading from it during the installation." msgstr "" #. Tag: para -#: boot-installer.xml:3362 +#: boot-installer.xml:3321 #, no-c-format msgid "There are a many different possible causes for these problems. We can only list some common issues and provide general suggestions on how to deal with them. The rest is up to you." msgstr "" #. Tag: para -#: boot-installer.xml:3368 +#: boot-installer.xml:3327 #, no-c-format msgid "There are two very simple things that you should try first." msgstr "" #. Tag: para -#: boot-installer.xml:3373 +#: boot-installer.xml:3332 #, no-c-format msgid "If the CD-ROM does not boot, check that it was inserted correctly and that it is not dirty." msgstr "" #. Tag: para -#: boot-installer.xml:3379 +#: boot-installer.xml:3338 #, no-c-format msgid "If the installer fails to recognize a CD-ROM, try just running the option <menuchoice> <guimenuitem>Detect and mount CD-ROM</guimenuitem> </menuchoice> a second time. Some DMA related issues with older CD-ROM drives are known to be resolved in this way." msgstr "" #. Tag: para -#: boot-installer.xml:3389 +#: boot-installer.xml:3348 #, no-c-format msgid "If this does not work, then try the suggestions in the subsections below. Most, but not all, suggestions discussed there are valid for both CD-ROM and DVD, but we'll use the term CD-ROM for simplicity." msgstr "" #. Tag: para -#: boot-installer.xml:3395 +#: boot-installer.xml:3354 #, no-c-format msgid "If you cannot get the installation working from CD-ROM, try one of the other installation methods that are available." msgstr "" #. Tag: title -#: boot-installer.xml:3403 +#: boot-installer.xml:3362 #, no-c-format msgid "Common issues" msgstr "" #. Tag: para -#: boot-installer.xml:3406 +#: boot-installer.xml:3365 #, no-c-format msgid "Some older CD-ROM drives do not support reading from discs that were burned at high speeds using a modern CD writer." msgstr "" #. Tag: para -#: boot-installer.xml:3412 +#: boot-installer.xml:3371 #, no-c-format msgid "If your system boots correctly from the CD-ROM, it does not necessarily mean that Linux also supports the CD-ROM (or, more correctly, the controller that your CD-ROM drive is connected to)." msgstr "" #. Tag: para -#: boot-installer.xml:3419 +#: boot-installer.xml:3378 #, no-c-format msgid "Some older CD-ROM drives do not work correctly if <quote>direct memory access</quote> (DMA) is enabled." msgstr "" #. Tag: title -#: boot-installer.xml:3430 +#: boot-installer.xml:3389 #, no-c-format msgid "How to investigate and maybe solve issues" msgstr "" #. Tag: para -#: boot-installer.xml:3431 +#: boot-installer.xml:3390 #, no-c-format msgid "If the CD-ROM fails to boot, try the suggestions listed below." msgstr "" #. Tag: para -#: boot-installer.xml:3436 +#: boot-installer.xml:3395 #, no-c-format msgid "Check that your BIOS actually supports booting from CD-ROM (older systems possibly don't) and that your CD-ROM drive supports the media you are using." msgstr "" #. Tag: para -#: boot-installer.xml:3442 +#: boot-installer.xml:3401 #, no-c-format msgid "" "If you downloaded an iso image, check that the md5sum of that image matches the one listed for the image in the <filename>MD5SUMS</filename> file that should be present in the same location as where you downloaded the image from. <informalexample><screen>\n" @@ -2433,7 +2402,7 @@ msgid "" msgstr "" #. Tag: screen -#: boot-installer.xml:3455 +#: boot-installer.xml:3414 #, no-c-format msgid "" "$ dd if=/dev/cdrom | \\\n" @@ -2446,19 +2415,19 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:3460 +#: boot-installer.xml:3419 #, no-c-format msgid "If, after the installer has been booted successfully, the CD-ROM is not detected, sometimes simply trying again may solve the problem. If you have more than one CD-ROM drive, try changing the CD-ROM to the other drive. If that does not work or if the CD-ROM is recognized but there are errors when reading from it, try the suggestions listed below. Some basic knowledge of Linux is required for this. To execute any of the commands, you should first switch to the second virtual console (VT2) and activate the shell there." msgstr "" #. Tag: para -#: boot-installer.xml:3472 +#: boot-installer.xml:3431 #, no-c-format msgid "Switch to VT4 or view the contents of <filename>/var/log/syslog</filename> (use <command>nano</command> as editor) to check for any specific error messages. After that, also check the output of <command>dmesg</command>." msgstr "" #. Tag: para -#: boot-installer.xml:3479 +#: boot-installer.xml:3438 #, no-c-format msgid "" "Check in the output of <command>dmesg</command> if your CD-ROM drive was recognized. You should see something like (the lines do not necessarily have to be consecutive): <informalexample><screen>\n" @@ -2471,13 +2440,13 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:3493 +#: boot-installer.xml:3452 #, no-c-format msgid "Check that there is a device node for your CD-ROM drive under <filename>/dev/</filename>. In the example above, this would be <filename>/dev/hdc</filename>. There should also be a <filename>/dev/cdroms/cdrom0</filename>." msgstr "" #. Tag: para -#: boot-installer.xml:3501 +#: boot-installer.xml:3460 #, no-c-format msgid "" "Use the <command>mount</command> command to check if the CD-ROM is already mounted; if not, try mounting it manually: <informalexample><screen>\n" @@ -2486,7 +2455,7 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:3511 +#: boot-installer.xml:3470 #, no-c-format msgid "" "Check if DMA is currently enabled: <informalexample><screen>\n" @@ -2499,157 +2468,157 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:3526 +#: boot-installer.xml:3485 #, no-c-format msgid "If there are any problems during the installation, try checking the integrity of the CD-ROM using the option near the bottom of the installer's main menu. This option can also be used as a general test if the CD-ROM can be read reliably." msgstr "" #. Tag: title -#: boot-installer.xml:3541 +#: boot-installer.xml:3500 #, no-c-format msgid "Floppy Disk Reliability" msgstr "" #. Tag: para -#: boot-installer.xml:3543 +#: boot-installer.xml:3502 #, no-c-format msgid "The biggest problem for people using floppy disks to install Debian seems to be floppy disk reliability." msgstr "" #. Tag: para -#: boot-installer.xml:3548 +#: boot-installer.xml:3507 #, no-c-format msgid "The boot floppy is the floppy with the worst problems, because it is read by the hardware directly, before Linux boots. Often, the hardware doesn't read as reliably as the Linux floppy disk driver, and may just stop without printing an error message if it reads incorrect data. There can also be failures in the driver floppies, most of which indicate themselves with a flood of messages about disk I/O errors." msgstr "" #. Tag: para -#: boot-installer.xml:3557 +#: boot-installer.xml:3516 #, no-c-format msgid "If you are having the installation stall at a particular floppy, the first thing you should do is write the image to a <emphasis>different</emphasis> floppy and see if that solves the problem. Simply reformatting the old floppy may not be sufficient, even if it appears that the floppy was reformatted and written with no errors. It is sometimes useful to try writing the floppy on a different system." msgstr "" #. Tag: para -#: boot-installer.xml:3566 +#: boot-installer.xml:3525 #, no-c-format msgid "One user reports he had to write the images to floppy <emphasis>three</emphasis> times before one worked, and then everything was fine with the third floppy." msgstr "" #. Tag: para -#: boot-installer.xml:3572 +#: boot-installer.xml:3531 #, no-c-format msgid "Normally you should not have to download a floppy image again, but if you are experiencing problems it is always useful to verify that the images were downloaded correctly by verifying their md5sums." msgstr "" #. Tag: para -#: boot-installer.xml:3578 +#: boot-installer.xml:3537 #, no-c-format msgid "Other users have reported that simply rebooting a few times with the same floppy in the floppy drive can lead to a successful boot. This is all due to buggy hardware or firmware floppy drivers." msgstr "" #. Tag: title -#: boot-installer.xml:3587 +#: boot-installer.xml:3546 #, no-c-format msgid "Boot Configuration" msgstr "" #. Tag: para -#: boot-installer.xml:3589 +#: boot-installer.xml:3548 #, no-c-format msgid "If you have problems and the kernel hangs during the boot process, doesn't recognize peripherals you actually have, or drives are not recognized properly, the first thing to check is the boot parameters, as discussed in <xref linkend=\"boot-parms\"/>." msgstr "" #. Tag: para -#: boot-installer.xml:3596 +#: boot-installer.xml:3555 #, no-c-format msgid "Often, problems can be solved by removing add-ons and peripherals, and then trying booting again. <phrase arch=\"x86\">Internal modems, sound cards, and Plug-n-Play devices can be especially problematic.</phrase>" msgstr "" #. Tag: para -#: boot-installer.xml:3602 +#: boot-installer.xml:3561 #, no-c-format msgid "If you have a large amount of memory installed in your machine, more than 512M, and the installer hangs when booting the kernel, you may need to include a boot argument to limit the amount of memory the kernel sees, such as <userinput>mem=512m</userinput>." msgstr "" #. Tag: title -#: boot-installer.xml:3613 boot-installer.xml:3697 +#: boot-installer.xml:3572 boot-installer.xml:3656 #, no-c-format msgid "Common &arch-title; Installation Problems" msgstr "" #. Tag: para -#: boot-installer.xml:3614 +#: boot-installer.xml:3573 #, no-c-format msgid "There are some common installation problems that can be solved or avoided by passing certain boot parameters to the installer." msgstr "" #. Tag: para -#: boot-installer.xml:3619 +#: boot-installer.xml:3578 #, no-c-format msgid "Some systems have floppies with <quote>inverted DCLs</quote>. If you receive errors reading from the floppy, even when you know the floppy is good, try the parameter <userinput>floppy=thinkpad</userinput>." msgstr "" #. Tag: para -#: boot-installer.xml:3625 +#: boot-installer.xml:3584 #, no-c-format msgid "On some systems, such as the IBM PS/1 or ValuePoint (which have ST-506 disk drivers), the IDE drive may not be properly recognized. Again, try it first without the parameters and see if the IDE drive is recognized properly. If not, determine your drive geometry (cylinders, heads, and sectors), and use the parameter <userinput>hd=<replaceable>cylinders</replaceable>,<replaceable>heads</replaceable>,<replaceable>sectors</replaceable></userinput>." msgstr "" #. Tag: para -#: boot-installer.xml:3634 +#: boot-installer.xml:3593 #, no-c-format msgid "If you have a very old machine, and the kernel hangs after saying <computeroutput>Checking 'hlt' instruction...</computeroutput>, then you should try the <userinput>no-hlt</userinput> boot argument, which disables this test." msgstr "" #. Tag: para -#: boot-installer.xml:3641 +#: boot-installer.xml:3600 #, no-c-format msgid "If your screen begins to show a weird picture while the kernel boots, eg. pure white, pure black or colored pixel garbage, your system may contain a problematic video card which does not switch to the framebuffer mode properly. Then you can use the boot parameter <userinput>fb=false video=vga16:off</userinput> to disable the framebuffer console. Only a reduced set of languages will be available during the installation due to limited console features. See <xref linkend=\"boot-parms\"/> for details." msgstr "" #. Tag: title -#: boot-installer.xml:3655 +#: boot-installer.xml:3614 #, no-c-format msgid "System Freeze During the PCMCIA Configuration Phase" msgstr "" #. Tag: para -#: boot-installer.xml:3656 +#: boot-installer.xml:3615 #, no-c-format msgid "Some laptop models produced by Dell are known to crash when PCMCIA device detection tries to access some hardware addresses. Other laptops may display similar problems. If you experience such a problem and you don't need PCMCIA support during the installation, you can disable PCMCIA using the <userinput>hw-detect/start_pcmcia=false</userinput> boot parameter. You can then configure PCMCIA after the installation is completed and exclude the resource range causing the problems." msgstr "" #. Tag: para -#: boot-installer.xml:3666 +#: boot-installer.xml:3625 #, no-c-format msgid "Alternatively, you can boot the installer in expert mode. You will then be asked to enter the resource range options your hardware needs. For example, if you have one of the Dell laptops mentioned above, you should enter <userinput>exclude port 0x800-0x8ff</userinput> here. There is also a list of some common resource range options in the <ulink url=\"http://pcmcia-cs.sourceforge.net/ftp/doc/PCMCIA-HOWTO-1.html#ss1.12\">System resource settings section of the PCMCIA HOWTO</ulink>. Note that you have to omit the commas, if any, when you enter this value in the installer." msgstr "" #. Tag: title -#: boot-installer.xml:3683 +#: boot-installer.xml:3642 #, no-c-format msgid "System Freeze while Loading USB Modules" msgstr "" #. Tag: para -#: boot-installer.xml:3684 +#: boot-installer.xml:3643 #, no-c-format msgid "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." msgstr "" #. Tag: para -#: boot-installer.xml:3698 +#: boot-installer.xml:3657 #, no-c-format msgid "There are some common installation problems that are worth mentioning." msgstr "" #. Tag: title -#: boot-installer.xml:3704 +#: boot-installer.xml:3663 #, no-c-format msgid "Misdirected video output" msgstr "" #. Tag: para -#: boot-installer.xml:3705 +#: boot-installer.xml:3664 #, no-c-format msgid "" "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>\n" @@ -2659,85 +2628,85 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:3719 +#: boot-installer.xml:3678 #, no-c-format msgid "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>." msgstr "" #. Tag: title -#: boot-installer.xml:3730 +#: boot-installer.xml:3689 #, no-c-format msgid "Failure to Boot or Install from CD-ROM" msgstr "" #. Tag: para -#: boot-installer.xml:3731 +#: boot-installer.xml:3690 #, no-c-format msgid "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." msgstr "" #. Tag: para -#: boot-installer.xml:3737 +#: boot-installer.xml:3696 #, no-c-format msgid "We recommend to install such systems by netbooting the installer." msgstr "" #. Tag: title -#: boot-installer.xml:3746 +#: boot-installer.xml:3705 #, no-c-format msgid "Interpreting the Kernel Startup Messages" msgstr "" #. Tag: para -#: boot-installer.xml:3748 +#: boot-installer.xml:3707 #, no-c-format msgid "During the boot sequence, you may see many messages in the form <computeroutput>can't find <replaceable>something</replaceable></computeroutput>, or <computeroutput><replaceable>something</replaceable> not present</computeroutput>, <computeroutput>can't initialize <replaceable>something</replaceable></computeroutput>, or even <computeroutput>this driver release depends on <replaceable>something</replaceable></computeroutput>. Most of these messages are harmless. You see them because the kernel for the installation system is built to run on computers with many different peripheral devices. Obviously, no one computer will have every possible peripheral device, so the operating system may emit a few complaints while it looks for peripherals you don't own. You may also see the system pause for a while. This happens when it is waiting for a device to respond, and that device is not present on your system. If you find the time it takes to boot the system unacceptably long, you can create a custom kernel later (see <xref linkend=\"kernel-baking\"/>)." msgstr "" #. Tag: title -#: boot-installer.xml:3773 +#: boot-installer.xml:3732 #, no-c-format msgid "Reporting Installation Problems" msgstr "" #. Tag: para -#: boot-installer.xml:3774 +#: boot-installer.xml:3733 #, no-c-format msgid "If you get through the initial boot phase but cannot complete the install, the menu option <guimenuitem>Save debug logs</guimenuitem> may be helpful. It lets you store system error logs and configuration information from the installer to a floppy, or download them using a web browser. This information may provide clues as to what went wrong and how to fix it. If you are submitting a bug report, you may want to attach this information to the bug report." msgstr "" #. Tag: para -#: boot-installer.xml:3785 +#: boot-installer.xml:3744 #, no-c-format msgid "Other pertinent installation messages may be found in <filename>/var/log/</filename> during the installation, and <filename>/var/log/installer/</filename> after the computer has been booted into the installed system." msgstr "" #. Tag: title -#: boot-installer.xml:3796 +#: boot-installer.xml:3755 #, no-c-format msgid "Submitting Installation Reports" msgstr "" #. Tag: para -#: boot-installer.xml:3797 +#: boot-installer.xml:3756 #, no-c-format msgid "If you still have problems, please submit an installation report. We also encourage installation reports to be sent even if the installation is successful, so that we can get as much information as possible on the largest number of hardware configurations." msgstr "" #. Tag: para -#: boot-installer.xml:3804 +#: boot-installer.xml:3763 #, no-c-format msgid "Note that your installation report will be published in the Debian Bug Tracking System (BTS) and forwarded to a public mailing list. Make sure that you use an e-mail address that you do not mind being made public." msgstr "" #. Tag: para -#: boot-installer.xml:3810 +#: boot-installer.xml:3769 #, no-c-format msgid "If you have a working Debian system, the easiest way to send an installation report is to install the <classname>installation-report</classname> and <classname>reportbug</classname> packages (<command>aptitude install installation-report reportbug</command>), configure <classname>reportbug</classname> as explained in <xref linkend=\"mail-outgoing\"/>, and run the command <command>reportbug installation-reports</command>." msgstr "" #. Tag: para -#: boot-installer.xml:3820 +#: boot-installer.xml:3779 #, no-c-format msgid "" "Alternatively you can use this template when filling out installation reports, and file the report as a bug report against the <classname>installation-reports</classname> pseudo package, by sending it to <email>submit@bugs.debian.org</email>. <informalexample><screen>\n" diff --git a/po/pot/hardware.pot b/po/pot/hardware.pot index d4fde4d06..f8baad717 100644 --- a/po/pot/hardware.pot +++ b/po/pot/hardware.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2007-05-05 22:00+0000\n" +"POT-Creation-Date: 2007-07-26 04:00+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <LL@li.org>\n" @@ -315,13 +315,13 @@ msgid "DECstation" msgstr "" #. Tag: entry -#: hardware.xml:138 hardware.xml:1111 hardware.xml:1126 hardware.xml:1136 +#: hardware.xml:138 hardware.xml:1113 hardware.xml:1128 hardware.xml:1138 #, no-c-format msgid "r4k-kn04" msgstr "" #. Tag: entry -#: hardware.xml:140 hardware.xml:1106 hardware.xml:1116 hardware.xml:1121 hardware.xml:1131 +#: hardware.xml:140 hardware.xml:1108 hardware.xml:1118 hardware.xml:1123 hardware.xml:1133 #, no-c-format msgid "r3k-kn02" msgstr "" @@ -447,13 +447,13 @@ msgid "<entry>prep</entry>" msgstr "" #. Tag: entry -#: hardware.xml:183 +#: hardware.xml:183 hardware.xml:188 #, no-c-format msgid "Sun SPARC" msgstr "" #. Tag: entry -#: hardware.xml:184 +#: hardware.xml:184 hardware.xml:189 #, no-c-format msgid "sparc" msgstr "" @@ -471,1495 +471,1495 @@ msgid "sparc32" msgstr "" #. Tag: entry -#: hardware.xml:188 +#: hardware.xml:190 #, no-c-format msgid "<entry>sun4u</entry>" msgstr "" #. Tag: entry -#: hardware.xml:189 +#: hardware.xml:191 #, no-c-format msgid "sparc64" msgstr "" #. Tag: entry -#: hardware.xml:191 +#: hardware.xml:193 #, no-c-format msgid "<entry>sun4v</entry>" msgstr "" #. Tag: entry -#: hardware.xml:195 +#: hardware.xml:197 #, no-c-format msgid "IBM S/390" msgstr "" #. Tag: entry -#: hardware.xml:196 +#: hardware.xml:198 #, no-c-format msgid "s390" msgstr "" #. Tag: entry -#: hardware.xml:197 +#: hardware.xml:199 #, no-c-format msgid "IPL from VM-reader and DASD" msgstr "" #. Tag: entry -#: hardware.xml:198 +#: hardware.xml:200 #, no-c-format msgid "generic" msgstr "" #. Tag: entry -#: hardware.xml:200 +#: hardware.xml:202 #, no-c-format msgid "IPL from tape" msgstr "" #. Tag: entry -#: hardware.xml:201 +#: hardware.xml:203 #, no-c-format msgid "tape" msgstr "" #. Tag: para -#: hardware.xml:206 +#: hardware.xml:208 #, no-c-format msgid "This document covers installation for the <emphasis>&arch-title;</emphasis> architecture. If you are looking for information on any of the other Debian-supported architectures take a look at the <ulink url=\"http://www.debian.org/ports/\">Debian-Ports</ulink> pages." msgstr "" #. Tag: para -#: hardware.xml:214 +#: hardware.xml:216 #, no-c-format msgid "This is the first official release of &debian; for the &arch-title; architecture. We feel that it has proven itself sufficiently to be released. However, because it has not had the exposure (and hence testing by users) that some other architectures have had, you may encounter a few bugs. Use our <ulink url=\"&url-bts;\">Bug Tracking System</ulink> to report any problems; make sure to mention the fact that the bug is on the &arch-title; platform. It can be necessary to use the <ulink url=\"&url-list-subscribe;\">debian-&arch-listname; mailing list</ulink> as well." msgstr "" #. Tag: title -#: hardware.xml:236 hardware.xml:695 hardware.xml:731 hardware.xml:826 hardware.xml:845 hardware.xml:931 hardware.xml:973 hardware.xml:1041 hardware.xml:1200 +#: hardware.xml:238 hardware.xml:697 hardware.xml:733 hardware.xml:828 hardware.xml:847 hardware.xml:933 hardware.xml:975 hardware.xml:1043 hardware.xml:1202 #, no-c-format msgid "CPU, Main Boards, and Video Support" msgstr "" #. Tag: para -#: hardware.xml:237 +#: hardware.xml:239 #, no-c-format msgid "Complete information regarding supported DEC Alphas can be found at <ulink url=\"&url-alpha-howto;\">Linux Alpha HOWTO</ulink>. The purpose of this section is to describe the systems supported by the boot disks." msgstr "" #. Tag: para -#: hardware.xml:244 +#: hardware.xml:246 #, no-c-format msgid "Alpha machines are subdivided into different system types because there are a number of generations of motherboard and supporting chipsets. Different systems (<quote>sub-architectures</quote>) often have radically different engineering and capabilities. Therefore, the process of installing and, more to the point, booting, can vary from system to system." msgstr "" #. Tag: para -#: hardware.xml:252 +#: hardware.xml:254 #, no-c-format msgid "The following table lists the system types supported by the Debian installation system. The table also indicates the <emphasis>code name</emphasis> for these system types. You'll need to know this code name when you actually begin the installation process:" msgstr "" #. Tag: entry -#: hardware.xml:269 +#: hardware.xml:271 #, no-c-format msgid "Hardware Type" msgstr "" #. Tag: entry -#: hardware.xml:270 +#: hardware.xml:272 #, no-c-format msgid "Aliases" msgstr "" #. Tag: entry -#: hardware.xml:270 +#: hardware.xml:272 #, no-c-format msgid "MILO image" msgstr "" #. Tag: entry -#: hardware.xml:276 +#: hardware.xml:278 #, no-c-format msgid "ALCOR" msgstr "" #. Tag: entry -#: hardware.xml:277 +#: hardware.xml:279 #, no-c-format msgid "AlphaStation 500 5/266.300" msgstr "" #. Tag: entry -#: hardware.xml:278 +#: hardware.xml:280 #, no-c-format msgid "Maverick" msgstr "" #. Tag: entry -#: hardware.xml:279 hardware.xml:283 hardware.xml:287 +#: hardware.xml:281 hardware.xml:285 hardware.xml:289 #, no-c-format msgid "alcor" msgstr "" #. Tag: entry -#: hardware.xml:281 +#: hardware.xml:283 #, no-c-format msgid "AlphaStation 500 5/333...500" msgstr "" #. Tag: entry -#: hardware.xml:282 +#: hardware.xml:284 #, no-c-format msgid "Bret" msgstr "" #. Tag: entry -#: hardware.xml:285 +#: hardware.xml:287 #, no-c-format msgid "AlphaStation 600/266...300" msgstr "" #. Tag: entry -#: hardware.xml:286 +#: hardware.xml:288 #, no-c-format msgid "Alcor" msgstr "" #. Tag: entry -#: hardware.xml:289 +#: hardware.xml:291 #, no-c-format msgid "AlphaStation 600/300...433" msgstr "" #. Tag: entry -#: hardware.xml:290 +#: hardware.xml:292 #, no-c-format msgid "<entry>XLT</entry>" msgstr "" #. Tag: entry -#: hardware.xml:291 +#: hardware.xml:293 #, no-c-format msgid "<entry>xlt</entry>" msgstr "" #. Tag: entry -#: hardware.xml:295 +#: hardware.xml:297 #, no-c-format msgid "BOOK1" msgstr "" #. Tag: entry -#: hardware.xml:296 +#: hardware.xml:298 #, no-c-format msgid "AlphaBook1 (laptop)" msgstr "" #. Tag: entry -#: hardware.xml:297 +#: hardware.xml:299 #, no-c-format msgid "Alphabook1/Burns" msgstr "" #. Tag: entry -#: hardware.xml:298 +#: hardware.xml:300 #, no-c-format msgid "book1" msgstr "" #. Tag: entry -#: hardware.xml:302 +#: hardware.xml:304 #, no-c-format msgid "AVANTI" msgstr "" #. Tag: entry -#: hardware.xml:303 +#: hardware.xml:305 #, no-c-format msgid "AlphaStation 200 4/100...166" msgstr "" #. Tag: entry -#: hardware.xml:304 +#: hardware.xml:306 #, no-c-format msgid "Mustang" msgstr "" #. Tag: entry -#: hardware.xml:305 hardware.xml:309 hardware.xml:313 hardware.xml:317 hardware.xml:321 hardware.xml:325 hardware.xml:329 hardware.xml:333 +#: hardware.xml:307 hardware.xml:311 hardware.xml:315 hardware.xml:319 hardware.xml:323 hardware.xml:327 hardware.xml:331 hardware.xml:335 #, no-c-format msgid "avanti" msgstr "" #. Tag: entry -#: hardware.xml:307 +#: hardware.xml:309 #, no-c-format msgid "AlphaStation 200 4/233" msgstr "" #. Tag: entry -#: hardware.xml:308 +#: hardware.xml:310 #, no-c-format msgid "Mustang+" msgstr "" #. Tag: entry -#: hardware.xml:311 +#: hardware.xml:313 #, no-c-format msgid "AlphaStation 205 4/133...333" msgstr "" #. Tag: entry -#: hardware.xml:312 +#: hardware.xml:314 #, no-c-format msgid "<entry>LX3</entry>" msgstr "" #. Tag: entry -#: hardware.xml:315 +#: hardware.xml:317 #, no-c-format msgid "AlphaStation 250 4/300" msgstr "" #. Tag: entry -#: hardware.xml:316 +#: hardware.xml:318 #, no-c-format msgid "<entry>M3+</entry>" msgstr "" #. Tag: entry -#: hardware.xml:319 +#: hardware.xml:321 #, no-c-format msgid "AlphaStation 255 4/133...333" msgstr "" #. Tag: entry -#: hardware.xml:320 +#: hardware.xml:322 #, no-c-format msgid "LX3+" msgstr "" #. Tag: entry -#: hardware.xml:323 +#: hardware.xml:325 #, no-c-format msgid "AlphaStation 300 4/266" msgstr "" #. Tag: entry -#: hardware.xml:324 +#: hardware.xml:326 #, no-c-format msgid "Melmac" msgstr "" #. Tag: entry -#: hardware.xml:327 +#: hardware.xml:329 #, no-c-format msgid "AlphaStation 400 4/166" msgstr "" #. Tag: entry -#: hardware.xml:328 +#: hardware.xml:330 #, no-c-format msgid "Chinet" msgstr "" #. Tag: entry -#: hardware.xml:331 +#: hardware.xml:333 #, no-c-format msgid "AlphaStation 400 4/233...300" msgstr "" #. Tag: entry -#: hardware.xml:332 +#: hardware.xml:334 #, no-c-format msgid "Avanti" msgstr "" #. Tag: entry -#: hardware.xml:337 hardware.xml:350 hardware.xml:351 +#: hardware.xml:339 hardware.xml:352 hardware.xml:353 #, no-c-format msgid "EB164" msgstr "" #. Tag: entry -#: hardware.xml:338 +#: hardware.xml:340 #, no-c-format msgid "AlphaPC164" msgstr "" #. Tag: entry -#: hardware.xml:339 +#: hardware.xml:341 #, no-c-format msgid "PC164" msgstr "" #. Tag: entry -#: hardware.xml:340 +#: hardware.xml:342 #, no-c-format msgid "pc164" msgstr "" #. Tag: entry -#: hardware.xml:342 +#: hardware.xml:344 #, no-c-format msgid "AlphaPC164-LX" msgstr "" #. Tag: entry -#: hardware.xml:343 +#: hardware.xml:345 #, no-c-format msgid "LX164" msgstr "" #. Tag: entry -#: hardware.xml:344 +#: hardware.xml:346 #, no-c-format msgid "lx164" msgstr "" #. Tag: entry -#: hardware.xml:346 +#: hardware.xml:348 #, no-c-format msgid "AlphaPC164-SX" msgstr "" #. Tag: entry -#: hardware.xml:347 +#: hardware.xml:349 #, no-c-format msgid "SX164" msgstr "" #. Tag: entry -#: hardware.xml:348 +#: hardware.xml:350 #, no-c-format msgid "sx164" msgstr "" #. Tag: entry -#: hardware.xml:352 +#: hardware.xml:354 #, no-c-format msgid "eb164" msgstr "" #. Tag: entry -#: hardware.xml:356 hardware.xml:365 hardware.xml:366 +#: hardware.xml:358 hardware.xml:367 hardware.xml:368 #, no-c-format msgid "EB64+" msgstr "" #. Tag: entry -#: hardware.xml:357 +#: hardware.xml:359 #, no-c-format msgid "AlphaPC64" msgstr "" #. Tag: entry -#: hardware.xml:358 hardware.xml:362 +#: hardware.xml:360 hardware.xml:364 #, no-c-format msgid "Cabriolet" msgstr "" #. Tag: entry -#: hardware.xml:359 hardware.xml:363 +#: hardware.xml:361 hardware.xml:365 #, no-c-format msgid "cabriolet" msgstr "" #. Tag: entry -#: hardware.xml:361 +#: hardware.xml:363 #, no-c-format msgid "AlphaPCI64" msgstr "" #. Tag: entry -#: hardware.xml:367 +#: hardware.xml:369 #, no-c-format msgid "eb64p" msgstr "" #. Tag: entry -#: hardware.xml:371 hardware.xml:372 hardware.xml:373 +#: hardware.xml:373 hardware.xml:374 hardware.xml:375 #, no-c-format msgid "EB66" msgstr "" #. Tag: entry -#: hardware.xml:374 +#: hardware.xml:376 #, no-c-format msgid "eb66" msgstr "" #. Tag: entry -#: hardware.xml:376 hardware.xml:377 +#: hardware.xml:378 hardware.xml:379 #, no-c-format msgid "EB66+" msgstr "" #. Tag: entry -#: hardware.xml:378 +#: hardware.xml:380 #, no-c-format msgid "eb66p" msgstr "" #. Tag: entry -#: hardware.xml:382 +#: hardware.xml:384 #, no-c-format msgid "JENSEN" msgstr "" #. Tag: entry -#: hardware.xml:383 +#: hardware.xml:385 #, no-c-format msgid "DEC 2000 Model 300(S)" msgstr "" #. Tag: entry -#: hardware.xml:384 hardware.xml:392 +#: hardware.xml:386 hardware.xml:394 #, no-c-format msgid "Jensen" msgstr "" #. Tag: entry -#: hardware.xml:385 hardware.xml:389 hardware.xml:393 hardware.xml:454 hardware.xml:458 hardware.xml:476 hardware.xml:480 hardware.xml:484 hardware.xml:488 hardware.xml:492 hardware.xml:496 hardware.xml:500 hardware.xml:514 hardware.xml:518 hardware.xml:522 hardware.xml:526 hardware.xml:530 hardware.xml:564 hardware.xml:568 hardware.xml:572 hardware.xml:576 hardware.xml:590 hardware.xml:594 hardware.xml:598 hardware.xml:602 hardware.xml:609 hardware.xml:613 hardware.xml:617 hardware.xml:621 hardware.xml:625 hardware.xml:629 hardware.xml:633 hardware.xml:637 hardware.xml:641 hardware.xml:645 hardware.xml:649 hardware.xml:653 hardware.xml:657 hardware.xml:664 hardware.xml:668 +#: hardware.xml:387 hardware.xml:391 hardware.xml:395 hardware.xml:456 hardware.xml:460 hardware.xml:478 hardware.xml:482 hardware.xml:486 hardware.xml:490 hardware.xml:494 hardware.xml:498 hardware.xml:502 hardware.xml:516 hardware.xml:520 hardware.xml:524 hardware.xml:528 hardware.xml:532 hardware.xml:566 hardware.xml:570 hardware.xml:574 hardware.xml:578 hardware.xml:592 hardware.xml:596 hardware.xml:600 hardware.xml:604 hardware.xml:611 hardware.xml:615 hardware.xml:619 hardware.xml:623 hardware.xml:627 hardware.xml:631 hardware.xml:635 hardware.xml:639 hardware.xml:643 hardware.xml:647 hardware.xml:651 hardware.xml:655 hardware.xml:659 hardware.xml:666 hardware.xml:670 #, no-c-format msgid "<entry>N/A</entry>" msgstr "" #. Tag: entry -#: hardware.xml:387 +#: hardware.xml:389 #, no-c-format msgid "DEC 2000 Model 500" msgstr "" #. Tag: entry -#: hardware.xml:388 +#: hardware.xml:390 #, no-c-format msgid "Culzen" msgstr "" #. Tag: entry -#: hardware.xml:391 +#: hardware.xml:393 #, no-c-format msgid "DECpc 150" msgstr "" #. Tag: entry -#: hardware.xml:397 +#: hardware.xml:399 #, no-c-format msgid "MIATA" msgstr "" #. Tag: entry -#: hardware.xml:398 +#: hardware.xml:400 #, no-c-format msgid "Personal WorkStation 433a" msgstr "" #. Tag: entry -#: hardware.xml:399 hardware.xml:403 hardware.xml:407 hardware.xml:411 hardware.xml:415 hardware.xml:419 hardware.xml:423 hardware.xml:427 +#: hardware.xml:401 hardware.xml:405 hardware.xml:409 hardware.xml:413 hardware.xml:417 hardware.xml:421 hardware.xml:425 hardware.xml:429 #, no-c-format msgid "Miata" msgstr "" #. Tag: entry -#: hardware.xml:400 hardware.xml:404 hardware.xml:408 hardware.xml:412 hardware.xml:416 hardware.xml:420 hardware.xml:424 hardware.xml:428 +#: hardware.xml:402 hardware.xml:406 hardware.xml:410 hardware.xml:414 hardware.xml:418 hardware.xml:422 hardware.xml:426 hardware.xml:430 #, no-c-format msgid "miata" msgstr "" #. Tag: entry -#: hardware.xml:402 +#: hardware.xml:404 #, no-c-format msgid "Personal WorkStation 433au" msgstr "" #. Tag: entry -#: hardware.xml:406 +#: hardware.xml:408 #, no-c-format msgid "Personal WorkStation 466au" msgstr "" #. Tag: entry -#: hardware.xml:410 +#: hardware.xml:412 #, no-c-format msgid "Personal WorkStation 500a" msgstr "" #. Tag: entry -#: hardware.xml:414 +#: hardware.xml:416 #, no-c-format msgid "Personal WorkStation 500au" msgstr "" #. Tag: entry -#: hardware.xml:418 +#: hardware.xml:420 #, no-c-format msgid "Personal WorkStation 550au" msgstr "" #. Tag: entry -#: hardware.xml:422 +#: hardware.xml:424 #, no-c-format msgid "Personal WorkStation 600a" msgstr "" #. Tag: entry -#: hardware.xml:426 +#: hardware.xml:428 #, no-c-format msgid "Personal WorkStation 600au" msgstr "" #. Tag: entry -#: hardware.xml:432 +#: hardware.xml:434 #, no-c-format msgid "MIKASA" msgstr "" #. Tag: entry -#: hardware.xml:433 +#: hardware.xml:435 #, no-c-format msgid "AlphaServer 1000 4/200" msgstr "" #. Tag: entry -#: hardware.xml:434 +#: hardware.xml:436 #, no-c-format msgid "Mikasa" msgstr "" #. Tag: entry -#: hardware.xml:435 hardware.xml:439 hardware.xml:443 hardware.xml:447 +#: hardware.xml:437 hardware.xml:441 hardware.xml:445 hardware.xml:449 #, no-c-format msgid "mikasa" msgstr "" #. Tag: entry -#: hardware.xml:437 +#: hardware.xml:439 #, no-c-format msgid "AlphaServer 1000 4/233..266" msgstr "" #. Tag: entry -#: hardware.xml:438 +#: hardware.xml:440 #, no-c-format msgid "Mikasa+" msgstr "" #. Tag: entry -#: hardware.xml:441 hardware.xml:445 +#: hardware.xml:443 hardware.xml:447 #, no-c-format msgid "AlphaServer 1000 5/300" msgstr "" #. Tag: entry -#: hardware.xml:442 +#: hardware.xml:444 #, no-c-format msgid "Mikasa-Pinnacle" msgstr "" #. Tag: entry -#: hardware.xml:446 +#: hardware.xml:448 #, no-c-format msgid "Mikasa-Primo" msgstr "" #. Tag: entry -#: hardware.xml:451 +#: hardware.xml:453 #, no-c-format msgid "NAUTILUS" msgstr "" #. Tag: entry -#: hardware.xml:452 +#: hardware.xml:454 #, no-c-format msgid "UP1000" msgstr "" #. Tag: entry -#: hardware.xml:453 +#: hardware.xml:455 #, no-c-format msgid "Nautilus" msgstr "" #. Tag: entry -#: hardware.xml:456 +#: hardware.xml:458 #, no-c-format msgid "UP1100" msgstr "" #. Tag: entry -#: hardware.xml:457 +#: hardware.xml:459 #, no-c-format msgid "Galaxy-Train/Nautilus Jr." msgstr "" #. Tag: entry -#: hardware.xml:462 +#: hardware.xml:464 #, no-c-format msgid "NONAME" msgstr "" #. Tag: entry -#: hardware.xml:463 +#: hardware.xml:465 #, no-c-format msgid "AXPpci33" msgstr "" #. Tag: entry -#: hardware.xml:464 +#: hardware.xml:466 #, no-c-format msgid "Noname" msgstr "" #. Tag: entry -#: hardware.xml:465 hardware.xml:469 +#: hardware.xml:467 hardware.xml:471 #, no-c-format msgid "noname" msgstr "" #. Tag: entry -#: hardware.xml:467 +#: hardware.xml:469 #, no-c-format msgid "<entry>UDB</entry>" msgstr "" #. Tag: entry -#: hardware.xml:468 +#: hardware.xml:470 #, no-c-format msgid "Multia" msgstr "" #. Tag: entry -#: hardware.xml:473 +#: hardware.xml:475 #, no-c-format msgid "NORITAKE" msgstr "" #. Tag: entry -#: hardware.xml:474 +#: hardware.xml:476 #, no-c-format msgid "AlphaServer 1000A 4/233...266" msgstr "" #. Tag: entry -#: hardware.xml:475 +#: hardware.xml:477 #, no-c-format msgid "Noritake" msgstr "" #. Tag: entry -#: hardware.xml:478 +#: hardware.xml:480 #, no-c-format msgid "AlphaServer 1000A 5/300" msgstr "" #. Tag: entry -#: hardware.xml:479 +#: hardware.xml:481 #, no-c-format msgid "Noritake-Pinnacle" msgstr "" #. Tag: entry -#: hardware.xml:482 +#: hardware.xml:484 #, no-c-format msgid "AlphaServer 1000A 5/333...500" msgstr "" #. Tag: entry -#: hardware.xml:483 +#: hardware.xml:485 #, no-c-format msgid "Noritake-Primo" msgstr "" #. Tag: entry -#: hardware.xml:486 +#: hardware.xml:488 #, no-c-format msgid "AlphaServer 800 5/333...500" msgstr "" #. Tag: entry -#: hardware.xml:487 hardware.xml:495 hardware.xml:499 +#: hardware.xml:489 hardware.xml:497 hardware.xml:501 #, no-c-format msgid "Corelle" msgstr "" #. Tag: entry -#: hardware.xml:490 +#: hardware.xml:492 #, no-c-format msgid "AlphaStation 600 A" msgstr "" #. Tag: entry -#: hardware.xml:491 +#: hardware.xml:493 #, no-c-format msgid "Alcor-Primo" msgstr "" #. Tag: entry -#: hardware.xml:494 +#: hardware.xml:496 #, no-c-format msgid "Digital Server 3300" msgstr "" #. Tag: entry -#: hardware.xml:498 +#: hardware.xml:500 #, no-c-format msgid "Digital Server 3300R" msgstr "" #. Tag: entry -#: hardware.xml:504 +#: hardware.xml:506 #, no-c-format msgid "PLATFORM 2000" msgstr "" #. Tag: entry -#: hardware.xml:505 hardware.xml:506 +#: hardware.xml:507 hardware.xml:508 #, no-c-format msgid "<entry>P2K</entry>" msgstr "" #. Tag: entry -#: hardware.xml:507 +#: hardware.xml:509 #, no-c-format msgid "<entry>p2k</entry>" msgstr "" #. Tag: entry -#: hardware.xml:511 +#: hardware.xml:513 #, no-c-format msgid "RAWHIDE" msgstr "" #. Tag: entry -#: hardware.xml:512 +#: hardware.xml:514 #, no-c-format msgid "AlphaServer 1200 5/xxx" msgstr "" #. Tag: entry -#: hardware.xml:513 hardware.xml:525 +#: hardware.xml:515 hardware.xml:527 #, no-c-format msgid "Tincup/DaVinci" msgstr "" #. Tag: entry -#: hardware.xml:516 +#: hardware.xml:518 #, no-c-format msgid "AlphaServer 4000 5/xxx" msgstr "" #. Tag: entry -#: hardware.xml:517 +#: hardware.xml:519 #, no-c-format msgid "Wrangler/Durango" msgstr "" #. Tag: entry -#: hardware.xml:520 +#: hardware.xml:522 #, no-c-format msgid "AlphaServer 4100 5/xxx" msgstr "" #. Tag: entry -#: hardware.xml:521 hardware.xml:529 +#: hardware.xml:523 hardware.xml:531 #, no-c-format msgid "Dodge" msgstr "" #. Tag: entry -#: hardware.xml:524 +#: hardware.xml:526 #, no-c-format msgid "Digital Server 5300" msgstr "" #. Tag: entry -#: hardware.xml:528 +#: hardware.xml:530 #, no-c-format msgid "Digital Server 7300" msgstr "" #. Tag: entry -#: hardware.xml:534 +#: hardware.xml:536 #, no-c-format msgid "RUFFIAN" msgstr "" #. Tag: entry -#: hardware.xml:535 +#: hardware.xml:537 #, no-c-format msgid "DeskStation AlphaPC164-UX" msgstr "" #. Tag: entry -#: hardware.xml:536 hardware.xml:540 hardware.xml:544 hardware.xml:548 hardware.xml:552 hardware.xml:556 +#: hardware.xml:538 hardware.xml:542 hardware.xml:546 hardware.xml:550 hardware.xml:554 hardware.xml:558 #, no-c-format msgid "Ruffian" msgstr "" #. Tag: entry -#: hardware.xml:537 hardware.xml:541 hardware.xml:545 hardware.xml:549 hardware.xml:553 hardware.xml:557 +#: hardware.xml:539 hardware.xml:543 hardware.xml:547 hardware.xml:551 hardware.xml:555 hardware.xml:559 #, no-c-format msgid "ruffian" msgstr "" #. Tag: entry -#: hardware.xml:539 +#: hardware.xml:541 #, no-c-format msgid "DeskStation RPL164-2" msgstr "" #. Tag: entry -#: hardware.xml:543 +#: hardware.xml:545 #, no-c-format msgid "DeskStation RPL164-4" msgstr "" #. Tag: entry -#: hardware.xml:547 +#: hardware.xml:549 #, no-c-format msgid "DeskStation RPX164-2" msgstr "" #. Tag: entry -#: hardware.xml:551 +#: hardware.xml:553 #, no-c-format msgid "DeskStation RPX164-4" msgstr "" #. Tag: entry -#: hardware.xml:555 +#: hardware.xml:557 #, no-c-format msgid "Samsung AlphaPC164-BX" msgstr "" #. Tag: entry -#: hardware.xml:561 +#: hardware.xml:563 #, no-c-format msgid "SABLE" msgstr "" #. Tag: entry -#: hardware.xml:562 +#: hardware.xml:564 #, no-c-format msgid "AlphaServer 2000 4/xxx" msgstr "" #. Tag: entry -#: hardware.xml:563 +#: hardware.xml:565 #, no-c-format msgid "Demi-Sable" msgstr "" #. Tag: entry -#: hardware.xml:566 +#: hardware.xml:568 #, no-c-format msgid "AlphaServer 2000 5/xxx" msgstr "" #. Tag: entry -#: hardware.xml:567 +#: hardware.xml:569 #, no-c-format msgid "Demi-Gamma-Sable" msgstr "" #. Tag: entry -#: hardware.xml:570 +#: hardware.xml:572 #, no-c-format msgid "AlphaServer 2100 4/xxx" msgstr "" #. Tag: entry -#: hardware.xml:571 +#: hardware.xml:573 #, no-c-format msgid "Sable" msgstr "" #. Tag: entry -#: hardware.xml:574 +#: hardware.xml:576 #, no-c-format msgid "AlphaServer 2100 5/xxx" msgstr "" #. Tag: entry -#: hardware.xml:575 +#: hardware.xml:577 #, no-c-format msgid "Gamma-Sable" msgstr "" #. Tag: entry -#: hardware.xml:580 +#: hardware.xml:582 #, no-c-format msgid "TAKARA" msgstr "" #. Tag: entry -#: hardware.xml:581 +#: hardware.xml:583 #, no-c-format msgid "21164 PICMG SBC" msgstr "" #. Tag: entry -#: hardware.xml:582 +#: hardware.xml:584 #, no-c-format msgid "Takara" msgstr "" #. Tag: entry -#: hardware.xml:583 +#: hardware.xml:585 #, no-c-format msgid "takara" msgstr "" #. Tag: entry -#: hardware.xml:587 +#: hardware.xml:589 #, no-c-format msgid "TITAN" msgstr "" #. Tag: entry -#: hardware.xml:588 +#: hardware.xml:590 #, no-c-format msgid "AlphaServer DS15" msgstr "" #. Tag: entry -#: hardware.xml:589 +#: hardware.xml:591 #, no-c-format msgid "HyperBrick2" msgstr "" #. Tag: entry -#: hardware.xml:592 +#: hardware.xml:594 #, no-c-format msgid "AlphaServer DS25" msgstr "" #. Tag: entry -#: hardware.xml:593 +#: hardware.xml:595 #, no-c-format msgid "Granite" msgstr "" #. Tag: entry -#: hardware.xml:596 +#: hardware.xml:598 #, no-c-format msgid "AlphaServer ES45" msgstr "" #. Tag: entry -#: hardware.xml:597 +#: hardware.xml:599 #, no-c-format msgid "Privateer" msgstr "" #. Tag: entry -#: hardware.xml:600 hardware.xml:639 hardware.xml:643 +#: hardware.xml:602 hardware.xml:641 hardware.xml:645 #, no-c-format msgid "UNKNOWN" msgstr "" #. Tag: entry -#: hardware.xml:601 +#: hardware.xml:603 #, no-c-format msgid "Yukon" msgstr "" #. Tag: entry -#: hardware.xml:606 +#: hardware.xml:608 #, no-c-format msgid "TSUNAMI" msgstr "" #. Tag: entry -#: hardware.xml:607 +#: hardware.xml:609 #, no-c-format msgid "AlphaServer DS10" msgstr "" #. Tag: entry -#: hardware.xml:608 hardware.xml:656 +#: hardware.xml:610 hardware.xml:658 #, no-c-format msgid "Webbrick" msgstr "" #. Tag: entry -#: hardware.xml:611 +#: hardware.xml:613 #, no-c-format msgid "AlphaServer DS10L" msgstr "" #. Tag: entry -#: hardware.xml:612 +#: hardware.xml:614 #, no-c-format msgid "Slate" msgstr "" #. Tag: entry -#: hardware.xml:615 +#: hardware.xml:617 #, no-c-format msgid "AlphaServer DS20" msgstr "" #. Tag: entry -#: hardware.xml:616 +#: hardware.xml:618 #, no-c-format msgid "Catamaran/Goldrush" msgstr "" #. Tag: entry -#: hardware.xml:619 +#: hardware.xml:621 #, no-c-format msgid "AlphaServer DS20E" msgstr "" #. Tag: entry -#: hardware.xml:620 +#: hardware.xml:622 #, no-c-format msgid "Goldrack" msgstr "" #. Tag: entry -#: hardware.xml:623 +#: hardware.xml:625 #, no-c-format msgid "AlphaServer DS20L" msgstr "" #. Tag: entry -#: hardware.xml:624 +#: hardware.xml:626 #, no-c-format msgid "Shark" msgstr "" #. Tag: entry -#: hardware.xml:627 +#: hardware.xml:629 #, no-c-format msgid "AlphaServer ES40" msgstr "" #. Tag: entry -#: hardware.xml:628 +#: hardware.xml:630 #, no-c-format msgid "Clipper" msgstr "" #. Tag: entry -#: hardware.xml:631 hardware.xml:632 +#: hardware.xml:633 hardware.xml:634 #, no-c-format msgid "DP264" msgstr "" #. Tag: entry -#: hardware.xml:635 +#: hardware.xml:637 #, no-c-format msgid "SMARTengine 21264 PCI/ISA SBC" msgstr "" #. Tag: entry -#: hardware.xml:636 +#: hardware.xml:638 #, no-c-format msgid "Eiger" msgstr "" #. Tag: entry -#: hardware.xml:640 +#: hardware.xml:642 #, no-c-format msgid "Warhol" msgstr "" #. Tag: entry -#: hardware.xml:644 +#: hardware.xml:646 #, no-c-format msgid "Windjammer" msgstr "" #. Tag: entry -#: hardware.xml:647 +#: hardware.xml:649 #, no-c-format msgid "UP2000" msgstr "" #. Tag: entry -#: hardware.xml:648 +#: hardware.xml:650 #, no-c-format msgid "Swordfish" msgstr "" #. Tag: entry -#: hardware.xml:651 +#: hardware.xml:653 #, no-c-format msgid "XP1000" msgstr "" #. Tag: entry -#: hardware.xml:652 +#: hardware.xml:654 #, no-c-format msgid "Monet/Brisbane" msgstr "" #. Tag: entry -#: hardware.xml:655 +#: hardware.xml:657 #, no-c-format msgid "XP900" msgstr "" #. Tag: entry -#: hardware.xml:661 +#: hardware.xml:663 #, no-c-format msgid "WILDFIRE" msgstr "" #. Tag: entry -#: hardware.xml:662 +#: hardware.xml:664 #, no-c-format msgid "AlphaServer GS160" msgstr "" #. Tag: entry -#: hardware.xml:663 hardware.xml:667 +#: hardware.xml:665 hardware.xml:669 #, no-c-format msgid "Wildfire" msgstr "" #. Tag: entry -#: hardware.xml:666 +#: hardware.xml:668 #, no-c-format msgid "AlphaServer GS320" msgstr "" #. Tag: entry -#: hardware.xml:672 hardware.xml:674 +#: hardware.xml:674 hardware.xml:676 #, no-c-format msgid "<entry>XL</entry>" msgstr "" #. Tag: entry -#: hardware.xml:673 +#: hardware.xml:675 #, no-c-format msgid "XL-233...266" msgstr "" #. Tag: entry -#: hardware.xml:675 +#: hardware.xml:677 #, no-c-format msgid "<entry>xl</entry>" msgstr "" #. Tag: para -#: hardware.xml:680 +#: hardware.xml:682 #, no-c-format msgid "It is believed that Debian &releasename; supports installing on all alpha sub-architectures with the exception of the ARC-only Ruffian and XL sub-architectures and the Titan subarchitecture, which requires a change to the kernel compile options." msgstr "" #. Tag: para -#: hardware.xml:696 hardware.xml:846 +#: hardware.xml:698 hardware.xml:848 #, no-c-format msgid "Complete information concerning supported peripherals can be found at <ulink url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink>. This section merely outlines the basics." msgstr "" #. Tag: title -#: hardware.xml:704 hardware.xml:854 hardware.xml:1014 +#: hardware.xml:706 hardware.xml:856 hardware.xml:1016 #, no-c-format msgid "<title>CPU</title>" msgstr "" #. Tag: para -#: hardware.xml:705 +#: hardware.xml:707 #, no-c-format msgid "Both AMD64 and Intel EM64T processors are supported." msgstr "" #. Tag: para -#: hardware.xml:733 +#: hardware.xml:735 #, no-c-format msgid "Each distinct ARM architecture requires its own kernel. Because of this the standard Debian distribution only supports installation on a number of the most common platforms. The Debian userland however may be used by <emphasis>any</emphasis> ARM CPU." msgstr "" #. Tag: para -#: hardware.xml:742 +#: hardware.xml:744 #, no-c-format msgid "Most ARM CPUs may be run in either endian mode (big or little). However, the majority of current system implementation uses little-endian mode. Debian currently only supports little-endian ARM systems." msgstr "" #. Tag: para -#: hardware.xml:750 +#: hardware.xml:752 #, no-c-format msgid "The supported platforms are:" msgstr "" #. Tag: term -#: hardware.xml:757 +#: hardware.xml:759 #, no-c-format msgid "Netwinder" msgstr "" #. Tag: para -#: hardware.xml:758 +#: hardware.xml:760 #, no-c-format msgid "This is actually the name for the group of machines based upon the StrongARM 110 CPU and Intel 21285 Northbridge (also known as Footbridge). It comprises of machines like: Netwinder (possibly one of the most common ARM boxes), CATS (also known as the EB110ATX), EBSA 285 and Compaq personal server (cps, aka skiff)." msgstr "" #. Tag: term -#: hardware.xml:771 +#: hardware.xml:773 #, no-c-format msgid "IOP32x" msgstr "" #. Tag: para -#: hardware.xml:772 +#: hardware.xml:774 #, no-c-format msgid "Intel's I/O Processor (IOP) line is found in a number of products related to data storage and processing. Debian currently supports the IOP32x platform, featuring the IOP 80219 and 32x chips commonly found in Network Attached Storage (NAS) devices. Debian explicitly supports two such devices: the <ulink url=\"&url-arm-cyrius-glantank;\">GLAN Tank</ulink> from IO-Data and the <ulink url=\"&url-arm-cyrius-n2100;\">Thecus N2100</ulink>." msgstr "" #. Tag: term -#: hardware.xml:785 +#: hardware.xml:787 #, no-c-format msgid "IXP4xx" msgstr "" #. Tag: para -#: hardware.xml:786 +#: hardware.xml:788 #, no-c-format msgid "The IXP4xx platform is based on Intel's XScale ARM core. Currently, only one IXP4xx based system is supported, the Linksys NSLU2. The Linksys NSLU2 (Network Storage Link for USB 2.0 Disk Drives) is a small device which allows you to easily provide storage via the network. It comes with an Ethernet connection and two USB ports to which hard drives can be connected. There is an external site with <ulink url=\"&url-arm-cyrius-nslu2;\">installation instructions</ulink>." msgstr "" #. Tag: term -#: hardware.xml:800 +#: hardware.xml:802 #, no-c-format msgid "<term>RiscPC</term>" msgstr "" #. Tag: para -#: hardware.xml:801 +#: hardware.xml:803 #, no-c-format msgid "This machine is the oldest supported hardware but support for it in our new installer is incomplete. It has RISC OS in ROM, Linux can be booted from that OS using linloader. The RiscPC has a modular CPU card and typically has a 30MHz 610, 40MHz 710 or 233MHz Strongarm 110 CPU fitted. The mainboard has integrated IDE, SVGA video, parallel port, single serial port, PS/2 keyboard and proprietary mouse port. The proprietary module expansion bus allows for up to eight expansion cards to be fitted depending on configuration, several of these modules have Linux drivers." msgstr "" #. Tag: para -#: hardware.xml:827 +#: hardware.xml:829 #, no-c-format msgid "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." msgstr "" #. Tag: para -#: hardware.xml:855 +#: hardware.xml:857 #, no-c-format msgid "Nearly all x86-based (IA-32) processors still in use in personal computers are supported, including all varieties of Intel's \"Pentium\" series. This also includes 32-bit AMD and VIA (former Cyrix) processors, and processors like the Athlon XP and Intel P4 Xeon." msgstr "" #. Tag: para -#: hardware.xml:863 +#: hardware.xml:865 #, no-c-format msgid "If your system has a 64-bit processor from the AMD64 or Intel EM64T families, you will probably want to use the installer for the amd64 architecture instead of the installer for the (32-bit) i386 architecture." msgstr "" #. Tag: para -#: hardware.xml:870 +#: hardware.xml:872 #, no-c-format msgid "However, Debian GNU/Linux &releasename; will <emphasis>not</emphasis> run on 386 or earlier processors. Despite the architecture name \"i386\", support for actual 80386 processors (and their clones) was dropped with the Sarge (r3.1) release of Debian<footnote> <para> We have long tried to avoid this, but in the end it was necessary due a unfortunate series of issues with the compiler and the kernel, starting with an bug in the C++ ABI provided by GCC. You should still be able to run Debian GNU/Linux on actual 80386 processors if you compile your own kernel and compile all packages from source, but that is beyond the scope of this manual. </para> </footnote>. (No version of Linux has ever supported the 286 or earlier chips in the series.) All i486 and later processors are still supported<footnote> <para> Many Debian packages will actually run slightly faster on modern computers as a positive side effect of dropping support for these old chips. The i486, introduced in 1989, has three opcodes (bswap, cmpxchg, and xadd) which the i386, introduced in 1986, did not have. Previously, these could not be easily used by most Debian packages; now they can. </para> </footnote>." msgstr "" #. Tag: title -#: hardware.xml:907 +#: hardware.xml:909 #, no-c-format msgid "I/O Bus" msgstr "" #. Tag: para -#: hardware.xml:908 +#: hardware.xml:910 #, no-c-format msgid "The system bus is the part of the motherboard which allows the CPU to communicate with peripherals such as storage devices. Your computer must use the ISA, EISA, PCI, the Microchannel Architecture (MCA, used in IBM's PS/2 line), or VESA Local Bus (VLB, sometimes called the VL bus). Essentially all personal computers sold in recent years use one of these." msgstr "" #. Tag: para -#: hardware.xml:932 +#: hardware.xml:934 #, no-c-format msgid "Complete information concerning supported M68000 based (<emphasis>&architecture;</emphasis>) systems can be found at the <ulink url=\"&url-m68k-faq;\">Linux/m68k FAQ</ulink>. This section merely outlines the basics." msgstr "" #. Tag: para -#: hardware.xml:939 +#: hardware.xml:941 #, no-c-format msgid "The &architecture; port of Linux runs on any 680x0 with a PMMU (Paged Memory Management Unit) and a FPU (floating-point unit). This includes the 68020 with an external 68851 PMMU, the 68030, and better, and excludes the <quote>EC</quote> line of 680x0 processors. See the <ulink url=\"&url-m68k-faq;\">Linux/m68k FAQ</ulink> for complete details." msgstr "" #. Tag: para -#: hardware.xml:947 +#: hardware.xml:949 #, no-c-format msgid "There are four major supported <emphasis>&architecture;</emphasis> flavors: Amiga, Atari, Macintosh and VME machines. Amiga and Atari were the first two systems to which Linux was ported; in keeping, they are also the two most well-supported Debian ports. The Macintosh line is supported incompletely, both by Debian and by the Linux kernel; see <ulink url=\"&url-m68k-mac;\">Linux m68k for Macintosh</ulink> for project status and supported hardware. The BVM and Motorola single board VMEbus computers are the most recent addition to the list of machines supported by Debian. Ports to other &architecture; architectures, such as the Sun3 architecture and NeXT black box, are underway but not yet supported by Debian." msgstr "" #. Tag: para -#: hardware.xml:974 +#: hardware.xml:976 #, no-c-format msgid "Debian on &arch-title; supports the following platforms: <itemizedlist> <listitem><para> SGI IP22: this platform includes the SGI machines Indy, Indigo 2 and Challenge S. Since these machines are very similar, whenever this document refers to the SGI Indy, the Indigo 2 and Challenge S are meant as well. </para></listitem> <listitem><para> SGI IP32: this platform is generally known as SGI O2. </para></listitem> <listitem><para> Broadcom BCM91250A (SWARM): this is an ATX form factor evaluation board from Broadcom based on the dual-core SB1 1250 CPU. </para></listitem> <listitem><para> Broadcom BCM91480B (BigSur): this is an ATX form factor evaluation board from Broadcom based on the quad-core SB1A 1480 CPU. </para></listitem> </itemizedlist> Complete information regarding supported mips/mipsel 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>." msgstr "" #. Tag: para -#: hardware.xml:1015 +#: hardware.xml:1017 #, no-c-format msgid "On SGI IP22, SGI Indy, Indigo 2 and Challenge S with R4000, R4400, R4600 and R5000 processors are supported by the Debian installation system on big endian MIPS. On SGI IP32, currently only systems based on the R5000 are supported. The Broadcom BCM91250A evaluation board comes with an SB1 1250 chip with two cores which are supported in SMP mode by this installer. Similarly, the BCM91480B evaluation board contains an SB1A 1480 chip with four cores which are supported in SMP mode." msgstr "" #. Tag: para -#: hardware.xml:1025 +#: hardware.xml:1027 #, no-c-format msgid "Some MIPS machines can be operated in both big and little endian mode. For little endian MIPS, please read the documentation for the mipsel architecture." msgstr "" #. Tag: para -#: hardware.xml:1042 +#: hardware.xml:1044 #, no-c-format msgid "Debian on &arch-title; supports the following platforms: <itemizedlist> <listitem><para> DECstation: various models of the DECstation are supported. </para></listitem> <listitem><para> Cobalt Microserver: only MIPS based Cobalt machines are covered here. This includes the Cobalt Qube 2700 (Qube1), RaQ, Qube2 and RaQ2, and the Gateway Microserver. </para></listitem> <listitem><para> Broadcom BCM91250A (SWARM): this is an ATX form factor evaluation board from Broadcom based on the dual-core SB1 1250 CPU. </para></listitem> <listitem><para> Broadcom BCM91480B (BigSur): this is an ATX form factor evaluation board from Broadcom based on the quad-core SB1A 1480 CPU. </para></listitem> </itemizedlist> Complete information regarding supported mips/mipsel 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>." msgstr "" #. Tag: title -#: hardware.xml:1082 +#: hardware.xml:1084 #, no-c-format msgid "CPU/Machine types" msgstr "" #. Tag: para -#: hardware.xml:1084 +#: hardware.xml:1086 #, no-c-format msgid "Currently only DECstations with R3000 and R4000/R4400 CPUs are supported by the Debian installation system on little endian MIPS. The Debian installation system works on the following machines:" msgstr "" #. Tag: entry -#: hardware.xml:1096 +#: hardware.xml:1098 #, no-c-format msgid "System Type" msgstr "" #. Tag: entry -#: hardware.xml:1096 +#: hardware.xml:1098 #, no-c-format msgid "<entry>CPU</entry>" msgstr "" #. Tag: entry -#: hardware.xml:1096 +#: hardware.xml:1098 #, no-c-format msgid "Code-name" msgstr "" #. Tag: entry -#: hardware.xml:1097 +#: hardware.xml:1099 #, no-c-format msgid "Debian subarchitecture" msgstr "" #. Tag: entry -#: hardware.xml:1103 +#: hardware.xml:1105 #, no-c-format msgid "DECstation 5000/1xx" msgstr "" #. Tag: entry -#: hardware.xml:1104 hardware.xml:1114 hardware.xml:1119 hardware.xml:1129 +#: hardware.xml:1106 hardware.xml:1116 hardware.xml:1121 hardware.xml:1131 #, no-c-format msgid "R3000" msgstr "" #. Tag: entry -#: hardware.xml:1105 hardware.xml:1110 +#: hardware.xml:1107 hardware.xml:1112 #, no-c-format msgid "3MIN" msgstr "" #. Tag: entry -#: hardware.xml:1108 +#: hardware.xml:1110 #, no-c-format msgid "DECstation 5000/150" msgstr "" #. Tag: entry -#: hardware.xml:1109 hardware.xml:1134 +#: hardware.xml:1111 hardware.xml:1136 #, no-c-format msgid "R4000" msgstr "" #. Tag: entry -#: hardware.xml:1113 +#: hardware.xml:1115 #, no-c-format msgid "DECstation 5000/200" msgstr "" #. Tag: entry -#: hardware.xml:1115 +#: hardware.xml:1117 #, no-c-format msgid "3MAX" msgstr "" #. Tag: entry -#: hardware.xml:1118 +#: hardware.xml:1120 #, no-c-format msgid "DECstation 5000/240" msgstr "" #. Tag: entry -#: hardware.xml:1120 hardware.xml:1125 +#: hardware.xml:1122 hardware.xml:1127 #, no-c-format msgid "3MAX+" msgstr "" #. Tag: entry -#: hardware.xml:1123 +#: hardware.xml:1125 #, no-c-format msgid "DECstation 5000/260" msgstr "" #. Tag: entry -#: hardware.xml:1124 +#: hardware.xml:1126 #, no-c-format msgid "R4400" msgstr "" #. Tag: entry -#: hardware.xml:1128 +#: hardware.xml:1130 #, no-c-format msgid "Personal DECstation 5000/xx" msgstr "" #. Tag: entry -#: hardware.xml:1130 hardware.xml:1135 +#: hardware.xml:1132 hardware.xml:1137 #, no-c-format msgid "Maxine" msgstr "" #. Tag: entry -#: hardware.xml:1133 +#: hardware.xml:1135 #, no-c-format msgid "Personal DECstation 5000/50" msgstr "" #. Tag: para -#: hardware.xml:1140 +#: hardware.xml:1142 #, no-c-format msgid "All Cobalt machines are supported. In the past, only machines with a serial console were supported (that is, all machines except for the Qube 2700, aka Qube1). However, installations are now also possible through SSH." msgstr "" #. Tag: para -#: hardware.xml:1147 +#: hardware.xml:1149 #, no-c-format msgid "The Broadcom BCM91250A evaluation board comes with an SB1 1250 chip with two cores which are supported in SMP mode by this installer. Similarly, the BCM91480B evaluation board contains an SB1A 1480 chip with four cores which are supported in SMP mode." msgstr "" #. Tag: title -#: hardware.xml:1157 +#: hardware.xml:1159 #, no-c-format msgid "Supported console options" msgstr "" #. Tag: para -#: hardware.xml:1158 +#: hardware.xml:1160 #, no-c-format msgid "A serial console is available on all supported DECstations (9600 bps, 8N1). To use the serial console, you have to boot the installer image with the <literal>console=ttyS</literal><replaceable>x</replaceable> kernel parameter (with <replaceable>x</replaceable> being the number of the serial port you have your terminal connected to — usually <literal>2</literal>, but <literal>0</literal> for the Personal DECstations). On 3MIN and 3MAX+ (DECstation 5000/1xx, 5000/240 and 5000/260) a local console is available with the PMAG-BA and the PMAGB-B graphics options." msgstr "" #. Tag: para -#: hardware.xml:1169 +#: hardware.xml:1171 #, no-c-format msgid "" "If you have a Linux system to use as serial terminal, an easy way is to run <command>cu</command><footnote> <para> In Woody this command was part of the <classname>uucp</classname> package, but in later releases it is available as a separate package. </para> </footnote> on it. Example: <informalexample><screen>\n" @@ -1968,1297 +1968,1315 @@ msgid "" msgstr "" #. Tag: para -#: hardware.xml:1187 +#: hardware.xml:1189 #, no-c-format msgid "Both Cobalt and Broadcom BCM91250A/BCM91480B use 115200 bps." msgstr "" #. Tag: para -#: hardware.xml:1201 +#: hardware.xml:1203 #, no-c-format msgid "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 methods. In addition, there are four different kernel flavours, supporting different CPU variants." msgstr "" #. Tag: para -#: hardware.xml:1209 +#: hardware.xml:1211 #, no-c-format msgid "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." msgstr "" #. Tag: title -#: hardware.xml:1217 +#: hardware.xml:1219 #, no-c-format msgid "Kernel Flavours" msgstr "" #. Tag: para -#: hardware.xml:1219 +#: hardware.xml:1221 #, no-c-format msgid "There are four flavours of the powerpc kernel in Debian, based on the CPU type:" msgstr "" #. Tag: term -#: hardware.xml:1226 +#: hardware.xml:1228 #, no-c-format msgid "<term>powerpc</term>" msgstr "" #. Tag: para -#: hardware.xml:1227 +#: hardware.xml:1229 #, no-c-format msgid "Most systems use this kernel flavour, which supports the PowerPC 601, 603, 604, 740, 750, and 7400 processors. All Apple PowerMac machines up to and including the one marketed as G4 use one of these processors." msgstr "" #. Tag: term -#: hardware.xml:1237 +#: hardware.xml:1239 #, no-c-format msgid "power64" msgstr "" #. Tag: para -#: hardware.xml:1238 +#: hardware.xml:1240 #, no-c-format msgid "The power64 kernel flavour supports the following CPUs:" msgstr "" #. Tag: para -#: hardware.xml:1242 +#: hardware.xml:1244 #, no-c-format msgid "The POWER3 processor is used in older IBM 64-bit server systems: known models include the IntelliStation POWER Model 265, the pSeries 610 and 640, and the RS/6000 7044-170, 7043-260, and 7044-270." msgstr "" #. Tag: para -#: hardware.xml:1248 +#: hardware.xml:1250 #, no-c-format msgid "The POWER4 processor is used in more recent IBM 64-bit server systems: known models include the pSeries 615, 630, 650, 655, 670, and 690." msgstr "" #. Tag: para -#: hardware.xml:1253 +#: hardware.xml:1255 #, no-c-format msgid "Systems using the Apple G5 (PPC970FX processor) are also based on the POWER4 architecture, and use this kernel flavour." msgstr "" #. Tag: term -#: hardware.xml:1262 +#: hardware.xml:1264 #, no-c-format msgid "<term>prep</term>" msgstr "" #. Tag: para -#: hardware.xml:1263 +#: hardware.xml:1265 #, no-c-format msgid "This kernel flavour supports the PReP subarchitecture." msgstr "" #. Tag: term -#: hardware.xml:1271 +#: hardware.xml:1273 #, no-c-format msgid "apus" msgstr "" #. Tag: para -#: hardware.xml:1272 +#: hardware.xml:1274 #, no-c-format msgid "This kernel flavour supports the Amiga Power-UP System, though it is currently disabled." msgstr "" #. Tag: title -#: hardware.xml:1285 +#: hardware.xml:1287 #, no-c-format msgid "Power Macintosh (pmac) subarchitecture" msgstr "" #. Tag: para -#: hardware.xml:1287 +#: hardware.xml:1289 #, no-c-format msgid "Apple (and briefly a few other manufacturers — Power Computing, for example) made a series of Macintosh computers based on the PowerPC processor. For purposes of architecture support, they are categorized as NuBus (not supported by Debian), OldWorld, and NewWorld." msgstr "" #. Tag: para -#: hardware.xml:1294 +#: hardware.xml:1296 #, no-c-format msgid "OldWorld systems are most Power Macintoshes with a floppy drive and a PCI bus. Most 603, 603e, 604, and 604e based Power Macintoshes are OldWorld machines. Those pre-iMac PowerPC models from Apple use a four digit naming scheme, except for the beige colored G3 systems, which are also OldWorld." msgstr "" #. Tag: para -#: hardware.xml:1302 +#: hardware.xml:1304 #, no-c-format msgid "The so called NewWorld PowerMacs are any PowerMacs in translucent colored plastic cases and later models. That includes all iMacs, iBooks, G4 systems, blue colored G3 systems, and most PowerBooks manufactured in and after 1999. The NewWorld PowerMacs are also known for using the <quote>ROM in RAM</quote> system for MacOS, and were manufactured from mid-1998 onwards." msgstr "" #. Tag: para -#: hardware.xml:1310 +#: hardware.xml:1312 #, no-c-format msgid "Specifications for Apple hardware are available at <ulink url=\"http://www.info.apple.com/support/applespec.html\">AppleSpec</ulink>, and, for older hardware, <ulink url=\"http://www.info.apple.com/support/applespec.legacy/index.html\">AppleSpec Legacy</ulink>." msgstr "" #. Tag: entry -#: hardware.xml:1326 hardware.xml:1461 hardware.xml:1505 hardware.xml:1534 +#: hardware.xml:1328 hardware.xml:1463 hardware.xml:1507 hardware.xml:1536 #, no-c-format msgid "Model Name/Number" msgstr "" #. Tag: entry -#: hardware.xml:1327 +#: hardware.xml:1329 #, no-c-format msgid "Generation" msgstr "" #. Tag: entry -#: hardware.xml:1333 +#: hardware.xml:1335 #, no-c-format msgid "Apple" msgstr "" #. Tag: entry -#: hardware.xml:1334 +#: hardware.xml:1336 #, no-c-format msgid "iMac Bondi Blue, 5 Flavors, Slot Loading" msgstr "" #. Tag: entry -#: hardware.xml:1335 hardware.xml:1338 hardware.xml:1341 hardware.xml:1344 hardware.xml:1347 hardware.xml:1350 hardware.xml:1353 hardware.xml:1356 hardware.xml:1359 hardware.xml:1362 hardware.xml:1365 hardware.xml:1368 hardware.xml:1371 hardware.xml:1374 hardware.xml:1377 hardware.xml:1380 +#: hardware.xml:1337 hardware.xml:1340 hardware.xml:1343 hardware.xml:1346 hardware.xml:1349 hardware.xml:1352 hardware.xml:1355 hardware.xml:1358 hardware.xml:1361 hardware.xml:1364 hardware.xml:1367 hardware.xml:1370 hardware.xml:1373 hardware.xml:1376 hardware.xml:1379 hardware.xml:1382 #, no-c-format msgid "NewWorld" msgstr "" #. Tag: entry -#: hardware.xml:1337 +#: hardware.xml:1339 #, no-c-format msgid "iMac Summer 2000, Early 2001" msgstr "" #. Tag: entry -#: hardware.xml:1340 +#: hardware.xml:1342 #, no-c-format msgid "iMac G5" msgstr "" #. Tag: entry -#: hardware.xml:1343 +#: hardware.xml:1345 #, no-c-format msgid "iBook, iBook SE, iBook Dual USB" msgstr "" #. Tag: entry -#: hardware.xml:1346 +#: hardware.xml:1348 #, no-c-format msgid "iBook2" msgstr "" #. Tag: entry -#: hardware.xml:1349 +#: hardware.xml:1351 #, no-c-format msgid "iBook G4" msgstr "" #. Tag: entry -#: hardware.xml:1352 +#: hardware.xml:1354 #, no-c-format msgid "Power Macintosh Blue and White (B&W) G3" msgstr "" #. Tag: entry -#: hardware.xml:1355 +#: hardware.xml:1357 #, no-c-format msgid "Power Macintosh G4 PCI, AGP, Cube" msgstr "" #. Tag: entry -#: hardware.xml:1358 +#: hardware.xml:1360 #, no-c-format msgid "Power Macintosh G4 Gigabit Ethernet" msgstr "" #. Tag: entry -#: hardware.xml:1361 +#: hardware.xml:1363 #, no-c-format msgid "Power Macintosh G4 Digital Audio, Quicksilver" msgstr "" #. Tag: entry -#: hardware.xml:1364 +#: hardware.xml:1366 #, no-c-format msgid "Power Macintosh G5" msgstr "" #. Tag: entry -#: hardware.xml:1367 +#: hardware.xml:1369 #, no-c-format msgid "PowerBook G3 FireWire Pismo (2000)" msgstr "" #. Tag: entry -#: hardware.xml:1370 +#: hardware.xml:1372 #, no-c-format msgid "PowerBook G3 Lombard (1999)" msgstr "" #. Tag: entry -#: hardware.xml:1373 +#: hardware.xml:1375 #, no-c-format msgid "PowerBook G4 Titanium" msgstr "" #. Tag: entry -#: hardware.xml:1376 +#: hardware.xml:1378 #, no-c-format msgid "PowerBook G4 Aluminum" msgstr "" #. Tag: entry -#: hardware.xml:1379 +#: hardware.xml:1381 #, no-c-format msgid "Xserve G5" msgstr "" #. Tag: entry -#: hardware.xml:1382 +#: hardware.xml:1384 #, no-c-format msgid "Performa 4400, 54xx, 5500" msgstr "" #. Tag: entry -#: hardware.xml:1383 hardware.xml:1386 hardware.xml:1389 hardware.xml:1392 hardware.xml:1395 hardware.xml:1398 hardware.xml:1401 hardware.xml:1404 hardware.xml:1407 hardware.xml:1410 hardware.xml:1413 hardware.xml:1416 hardware.xml:1422 hardware.xml:1425 hardware.xml:1431 hardware.xml:1437 hardware.xml:1443 +#: hardware.xml:1385 hardware.xml:1388 hardware.xml:1391 hardware.xml:1394 hardware.xml:1397 hardware.xml:1400 hardware.xml:1403 hardware.xml:1406 hardware.xml:1409 hardware.xml:1412 hardware.xml:1415 hardware.xml:1418 hardware.xml:1424 hardware.xml:1427 hardware.xml:1433 hardware.xml:1439 hardware.xml:1445 #, no-c-format msgid "OldWorld" msgstr "" #. Tag: entry -#: hardware.xml:1385 +#: hardware.xml:1387 #, no-c-format msgid "Performa 6360, 6400, 6500" msgstr "" #. Tag: entry -#: hardware.xml:1388 +#: hardware.xml:1390 #, no-c-format msgid "Power Macintosh 4400, 5400" msgstr "" #. Tag: entry -#: hardware.xml:1391 +#: hardware.xml:1393 #, no-c-format msgid "Power Macintosh 7200, 7300, 7500, 7600" msgstr "" #. Tag: entry -#: hardware.xml:1394 +#: hardware.xml:1396 #, no-c-format msgid "Power Macintosh 8200, 8500, 8600" msgstr "" #. Tag: entry -#: hardware.xml:1397 +#: hardware.xml:1399 #, no-c-format msgid "Power Macintosh 9500, 9600" msgstr "" #. Tag: entry -#: hardware.xml:1400 +#: hardware.xml:1402 #, no-c-format msgid "Power Macintosh (Beige) G3 Minitower" msgstr "" #. Tag: entry -#: hardware.xml:1403 +#: hardware.xml:1405 #, no-c-format msgid "Power Macintosh (Beige) Desktop, All-in-One" msgstr "" #. Tag: entry -#: hardware.xml:1406 +#: hardware.xml:1408 #, no-c-format msgid "PowerBook 2400, 3400, 3500" msgstr "" #. Tag: entry -#: hardware.xml:1409 +#: hardware.xml:1411 #, no-c-format msgid "PowerBook G3 Wallstreet (1998)" msgstr "" #. Tag: entry -#: hardware.xml:1412 +#: hardware.xml:1414 #, no-c-format msgid "Twentieth Anniversary Macintosh" msgstr "" #. Tag: entry -#: hardware.xml:1415 +#: hardware.xml:1417 #, no-c-format msgid "Workgroup Server 7250, 7350, 8550, 9650, G3" msgstr "" #. Tag: entry -#: hardware.xml:1420 +#: hardware.xml:1422 #, no-c-format msgid "Power Computing" msgstr "" #. Tag: entry -#: hardware.xml:1421 +#: hardware.xml:1423 #, no-c-format msgid "PowerBase, PowerTower / Pro, PowerWave" msgstr "" #. Tag: entry -#: hardware.xml:1424 +#: hardware.xml:1426 #, no-c-format msgid "PowerCenter / Pro, PowerCurve" msgstr "" #. Tag: entry -#: hardware.xml:1429 +#: hardware.xml:1431 #, no-c-format msgid "UMAX" msgstr "" #. Tag: entry -#: hardware.xml:1430 +#: hardware.xml:1432 #, no-c-format msgid "C500, C600, J700, S900" msgstr "" #. Tag: entry -#: hardware.xml:1435 +#: hardware.xml:1437 #, no-c-format msgid "<entry>APS</entry>" msgstr "" #. Tag: entry -#: hardware.xml:1436 +#: hardware.xml:1438 #, no-c-format msgid "APS Tech M*Power 604e/2000" msgstr "" #. Tag: entry -#: hardware.xml:1441 hardware.xml:1467 +#: hardware.xml:1443 hardware.xml:1469 #, no-c-format msgid "Motorola" msgstr "" #. Tag: entry -#: hardware.xml:1442 +#: hardware.xml:1444 #, no-c-format msgid "Starmax 3000, 4000, 5000, 5500" msgstr "" #. Tag: title -#: hardware.xml:1451 +#: hardware.xml:1453 #, no-c-format msgid "PReP subarchitecture" msgstr "" #. Tag: entry -#: hardware.xml:1468 +#: hardware.xml:1470 #, no-c-format msgid "Firepower, PowerStack Series E, PowerStack II" msgstr "" #. Tag: entry -#: hardware.xml:1470 +#: hardware.xml:1472 #, no-c-format msgid "MPC 7xx, 8xx" msgstr "" #. Tag: entry -#: hardware.xml:1472 +#: hardware.xml:1474 #, no-c-format msgid "MTX, MTX+" msgstr "" #. Tag: entry -#: hardware.xml:1474 +#: hardware.xml:1476 #, no-c-format msgid "MVME2300(SC)/24xx/26xx/27xx/36xx/46xx" msgstr "" #. Tag: entry -#: hardware.xml:1476 +#: hardware.xml:1478 #, no-c-format msgid "MCP(N)750" msgstr "" #. Tag: entry -#: hardware.xml:1480 hardware.xml:1511 +#: hardware.xml:1482 hardware.xml:1513 #, no-c-format msgid "IBM RS/6000" msgstr "" #. Tag: entry -#: hardware.xml:1481 +#: hardware.xml:1483 #, no-c-format msgid "40P, 43P" msgstr "" #. Tag: entry -#: hardware.xml:1483 +#: hardware.xml:1485 #, no-c-format msgid "Power 830/850/860 (6070, 6050)" msgstr "" #. Tag: entry -#: hardware.xml:1485 +#: hardware.xml:1487 #, no-c-format msgid "6030, 7025, 7043" msgstr "" #. Tag: entry -#: hardware.xml:1487 +#: hardware.xml:1489 #, no-c-format msgid "p640" msgstr "" #. Tag: title -#: hardware.xml:1495 +#: hardware.xml:1497 #, no-c-format msgid "CHRP subarchitecture" msgstr "" #. Tag: entry -#: hardware.xml:1512 +#: hardware.xml:1514 #, no-c-format msgid "B50, 43P-150, 44P" msgstr "" #. Tag: entry -#: hardware.xml:1515 +#: hardware.xml:1517 #, no-c-format msgid "Genesi" msgstr "" #. Tag: entry -#: hardware.xml:1516 +#: hardware.xml:1518 #, no-c-format msgid "Pegasos I, Pegasos II" msgstr "" #. Tag: title -#: hardware.xml:1524 +#: hardware.xml:1526 #, no-c-format msgid "APUS subarchitecture" msgstr "" #. Tag: entry -#: hardware.xml:1540 +#: hardware.xml:1542 #, no-c-format msgid "Amiga Power-UP Systems (APUS)" msgstr "" #. Tag: entry -#: hardware.xml:1541 +#: hardware.xml:1543 #, no-c-format msgid "A1200, A3000, A4000" msgstr "" #. Tag: title -#: hardware.xml:1549 +#: hardware.xml:1551 #, no-c-format msgid "Nubus PowerMac subarchitecture (unsupported)" msgstr "" #. Tag: para -#: hardware.xml:1551 +#: hardware.xml:1553 #, no-c-format msgid "NuBus systems are not currently supported by Debian/powerpc. The monolithic Linux/PPC kernel architecture does not have support for these machines; instead, one must use the MkLinux Mach microkernel, which Debian does not yet support. These include the following: <itemizedlist> <listitem><para> Power Macintosh 6100, 7100, 8100 </para></listitem> <listitem><para> Performa 5200, 6200, 6300 </para></listitem> <listitem><para> Powerbook 1400, 2300, and 5300 </para></listitem> <listitem><para> Workgroup Server 6150, 8150, 9150 </para></listitem> </itemizedlist> A linux kernel for these machines and limited support is available at <ulink url=\"http://nubus-pmac.sourceforge.net/\"></ulink>." msgstr "" #. Tag: title -#: hardware.xml:1588 +#: hardware.xml:1590 #, no-c-format msgid "Non-PowerPC Macs" msgstr "" #. Tag: para -#: hardware.xml:1590 +#: hardware.xml:1592 #, no-c-format msgid "Macintosh computers using the 680x0 series of processors are <emphasis>not</emphasis> in the PowerPC family but are instead m68k machines. Those models start with <quote>Mac II</quote> series, go on to the <quote>LC</quote> family, then the Centris series, and culminate in the Quadras and Performas. These models usually have a Roman numeral or 3-digit model number such as Mac IIcx, LCIII or Quadra 950." msgstr "" #. Tag: para -#: hardware.xml:1599 +#: hardware.xml:1601 #, no-c-format msgid "This model range started with the Mac II (Mac II, IIx, IIcx, IIci, IIsi, IIvi, IIvx, IIfx), then the LC (LC, LCII, III, III+, 475, 520, 550, 575, 580, 630), then the Mac TV, then the Centris (610, 650, 660AV), the Quadra (605, 610, 630, 650, 660AV, 700, 800, 840AV, 900, 950), and finally the Performa 200-640CD." msgstr "" #. Tag: para -#: hardware.xml:1607 +#: hardware.xml:1609 #, no-c-format msgid "In laptops, it started with the Mac Portable, then the PowerBook 100-190cs and the PowerBook Duo 210-550c (excluding PowerBook 500 which is Nubus, please see the section above)." msgstr "" #. Tag: title -#: hardware.xml:1623 +#: hardware.xml:1625 #, no-c-format msgid "S/390 and zSeries machine types" msgstr "" #. Tag: para -#: hardware.xml:1624 +#: hardware.xml:1626 #, no-c-format msgid "Complete information regarding supported S/390 and zSeries machines can be found in IBM's Redbook <ulink url=\"http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246264.pdf\"> Linux for IBM eServer zSeries and S/390: Distributions</ulink> in chapter 2.1 or at the <ulink url=\"http://www-128.ibm.com/developerworks/linux/linux390/index.html\">zSeries page at the developerWorks</ulink>. In short, G5, Multiprise 3000, G6 and all zSeries are fully supported; Multiprise 2000, G3 and G4 machines are supported with IEEE floating point emulation and thus degraded performance." msgstr "" #. Tag: title -#: hardware.xml:1646 +#: hardware.xml:1648 #, no-c-format msgid "CPU and Main Boards Support" msgstr "" #. Tag: para -#: hardware.xml:1647 +#: hardware.xml:1649 #, no-c-format msgid "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." msgstr "" #. Tag: term -#: hardware.xml:1658 +#: hardware.xml:1660 #, no-c-format msgid "sun4, sun4c, sun4d" msgstr "" #. Tag: para -#: hardware.xml:1660 +#: hardware.xml:1662 #, no-c-format msgid "These subarchitectures include some very old 32-bit machines, which are no longer supported. For a complete list please consult the <ulink url=\"http://en.wikipedia.org/wiki/SPARCstation\">Wikipedia SPARCstation page</ulink>." msgstr "" #. Tag: term -#: hardware.xml:1671 +#: hardware.xml:1673 #, no-c-format msgid "<term>sun4m</term>" msgstr "" #. Tag: para -#: hardware.xml:1673 +#: hardware.xml:1675 #, no-c-format msgid "sun4m is the only 32-bit subarchitecture (sparc32) that is currently supported. The most popular machines belonging to this class are Sparcstation 4, 5, 10 and 20." msgstr "" #. Tag: para -#: hardware.xml:1679 +#: hardware.xml:1681 #, no-c-format msgid "Note that symmetric multiprocessing (SMP) — the ability to run processes on multiple processors — is not supported on this hardware, due to stability problems with such configurations. The available uniprocessor (UP) sparc32 kernel will boot fine on multiprocessor machines, although it will activate and use only the first CPU." msgstr "" #. Tag: term -#: hardware.xml:1691 +#: hardware.xml:1693 +#, no-c-format +msgid "sun4, sun4c, sun4d, sun4m" +msgstr "" + +#. Tag: para +#: hardware.xml:1695 +#, no-c-format +msgid "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>." +msgstr "" + +#. Tag: para +#: hardware.xml:1702 +#, no-c-format +msgid "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." +msgstr "" + +#. Tag: term +#: hardware.xml:1712 #, no-c-format msgid "<term>sun4u</term>" msgstr "" #. Tag: para -#: hardware.xml:1693 +#: hardware.xml:1714 #, no-c-format msgid "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." msgstr "" #. Tag: term -#: hardware.xml:1706 +#: hardware.xml:1727 #, no-c-format msgid "<term>sun4v</term>" msgstr "" #. Tag: para -#: hardware.xml:1708 +#: hardware.xml:1729 #, no-c-format msgid "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." msgstr "" #. Tag: para -#: hardware.xml:1719 +#: hardware.xml:1740 #, no-c-format msgid "Note that Fujitsu's SPARC64 CPUs used in PRIMEPOWER family of servers are not supported due to lack of support in the Linux kernel." msgstr "" #. Tag: title -#: hardware.xml:1728 +#: hardware.xml:1749 #, no-c-format msgid "Graphics Card Support" msgstr "" #. Tag: para -#: hardware.xml:1729 +#: hardware.xml:1750 #, no-c-format msgid "You should be using a VGA-compatible display interface for the console terminal. Nearly every modern display card is compatible with VGA. Ancient standards such CGA, MDA, or HGA should also work, assuming you do not require X11 support. Note that X11 is not used during the installation process described in this document." msgstr "" #. Tag: para -#: hardware.xml:1737 +#: hardware.xml:1758 #, no-c-format msgid "Debian's support for graphical interfaces is determined by the underlying support found in X.Org's X11 system. Most AGP, PCI and PCIe video cards work under X.Org. Details on supported graphics buses, cards, monitors, and pointing devices can be found at <ulink url=\"&url-xorg;\"></ulink>. Debian &release; ships with X.Org version &x11ver;." msgstr "" #. Tag: para -#: hardware.xml:1746 +#: hardware.xml:1767 #, no-c-format msgid "The X.Org X Window System is only supported on the SGI Indy and the O2. The Broadcom BCM91250A and BCM91480B evaluation boards have standard 3.3v PCI slots and support VGA emulation or Linux framebuffer on a selected range of graphics cards. A <ulink url=\"&url-bcm91250a-hardware;\">compatibility listing</ulink> for Broadcom evaluation boards is available." msgstr "" #. Tag: para -#: hardware.xml:1755 +#: hardware.xml:1776 #, no-c-format msgid "The X.Org X Window System is supported on some DECstation models. The Broadcom BCM91250A and BCM91480B evaluation boards have standard 3.3v PCI slots and support VGA emulation or Linux framebuffer on a selected range of graphics cards. A <ulink url=\"&url-bcm91250a-hardware;\">compatibility listing</ulink> for Broadcom evaluation boards is available." msgstr "" #. Tag: para -#: hardware.xml:1763 +#: hardware.xml:1784 #, no-c-format msgid "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." msgstr "" #. Tag: para -#: hardware.xml:1773 +#: hardware.xml:1794 #, no-c-format msgid "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." msgstr "" #. Tag: title -#: hardware.xml:1790 +#: hardware.xml:1811 #, no-c-format msgid "Laptops" msgstr "" #. Tag: para -#: hardware.xml:1791 +#: hardware.xml:1812 #, no-c-format msgid "Laptops are also supported. Laptops are often specialized or contain proprietary hardware. To see if your particular laptop works well with GNU/Linux, see the <ulink url=\"&url-x86-laptop;\">Linux Laptop pages</ulink>" msgstr "" #. Tag: title -#: hardware.xml:1802 hardware.xml:1824 hardware.xml:1844 hardware.xml:1867 +#: hardware.xml:1823 hardware.xml:1845 hardware.xml:1865 hardware.xml:1888 #, no-c-format msgid "Multiple Processors" msgstr "" #. Tag: para -#: hardware.xml:1803 +#: hardware.xml:1824 #, no-c-format msgid "Multiprocessor support — also called <quote>symmetric multiprocessing</quote> or SMP — is available for this architecture. The standard Debian &release; kernel image was compiled with SMP support. This should not prevent installation, since the SMP kernel should boot on non-SMP systems; the kernel will simply cause a bit more overhead." msgstr "" #. Tag: para -#: hardware.xml:1811 +#: hardware.xml:1832 #, no-c-format msgid "In order to optimize the kernel for single CPU systems, you'll have to replace the standard Debian kernel. You can find a discussion of how to do this in <xref linkend=\"kernel-baking\"/>. At this time (kernel version &kernelversion;) the way you disable SMP is to deselect <quote>&smp-config-option;</quote> in the <quote>&smp-config-section;</quote> section of the kernel config." msgstr "" #. Tag: para -#: hardware.xml:1826 +#: hardware.xml:1847 #, no-c-format msgid "Multiprocessor support — also called <quote>symmetric multiprocessing</quote> or SMP — is available for this architecture. The standard Debian &release; kernel image was compiled with <firstterm>SMP-alternatives</firstterm> support. This means that the kernel will detect the number of processors (or processor cores) and will automatically deactivate SMP on uniprocessor systems." msgstr "" #. Tag: para -#: hardware.xml:1835 +#: hardware.xml:1856 #, no-c-format msgid "The 486 flavour of the Debian kernel image packages for &arch-title; is not compiled with SMP support." msgstr "" #. Tag: para -#: hardware.xml:1845 +#: hardware.xml:1866 #, no-c-format msgid "Multiprocessor support — also called <quote>symmetric multiprocessing</quote> or SMP — is available for this architecture. However, the standard Debian &release; kernel image does not support SMP. This should not prevent installation, since the standard, non-SMP kernel should boot on SMP systems; the kernel will simply use the first CPU." msgstr "" #. Tag: para -#: hardware.xml:1854 +#: hardware.xml:1875 #, no-c-format msgid "In order to take advantage of multiple processors, you'll have to replace the standard Debian kernel. You can find a discussion of how to do this in <xref linkend=\"kernel-baking\"/>. At this time (kernel version &kernelversion;) the way you enable SMP is to select <quote>&smp-config-option;</quote> in the <quote>&smp-config-section;</quote> section of the kernel config." msgstr "" #. Tag: para -#: hardware.xml:1868 +#: hardware.xml:1889 #, no-c-format msgid "Multiprocessor support — also called <quote>symmetric multiprocessing</quote> or SMP — is available for this architecture, and is supported by a precompiled Debian kernel image. Depending on your install media, this SMP-capable kernel may or may not be installed by default. This should not prevent installation, since the standard, non-SMP kernel should boot on SMP systems; the kernel will simply use the first CPU." msgstr "" #. Tag: para -#: hardware.xml:1878 +#: hardware.xml:1899 #, no-c-format msgid "In order to take advantage of multiple processors, you should check to see if a kernel package that supports SMP is installed, and if not, choose an appropriate kernel package." msgstr "" #. Tag: para -#: hardware.xml:1884 +#: hardware.xml:1905 #, no-c-format msgid "You can also build your own customized kernel to support SMP. You can find a discussion of how to do this in <xref linkend=\"kernel-baking\"/>. At this time (kernel version &kernelversion;) the way you enable SMP is to select <quote>&smp-config-option;</quote> in the <quote>&smp-config-section;</quote> section of the kernel config." msgstr "" #. Tag: title -#: hardware.xml:1901 +#: hardware.xml:1922 #, no-c-format msgid "Installation Media" msgstr "" #. Tag: para -#: hardware.xml:1903 +#: hardware.xml:1924 #, no-c-format msgid "This section will help you determine which different media types you can use to install Debian. For example, if you have a floppy disk drive on your machine, it can be used to install Debian. There is a whole chapter devoted to media, <xref linkend=\"install-methods\"/>, which lists the advantages and disadvantages of each media type. You may want to refer back to this page once you reach that section." msgstr "" #. Tag: title -#: hardware.xml:1914 +#: hardware.xml:1935 #, no-c-format msgid "Floppies" msgstr "" #. Tag: para -#: hardware.xml:1915 +#: hardware.xml:1936 #, no-c-format msgid "In some cases, you'll have to do your first boot from floppy disks. Generally, all you will need is a high-density (1440 kilobytes) 3.5 inch floppy drive." msgstr "" #. Tag: para -#: hardware.xml:1921 +#: hardware.xml:1942 #, no-c-format msgid "For CHRP, floppy support is currently broken." msgstr "" #. Tag: title -#: hardware.xml:1928 +#: hardware.xml:1949 #, no-c-format msgid "CD-ROM/DVD-ROM" msgstr "" #. Tag: para -#: hardware.xml:1930 +#: hardware.xml:1951 #, no-c-format msgid "Whenever you see <quote>CD-ROM</quote> in this manual, it applies to both CD-ROMs and DVD-ROMs, because both technologies are really the same from the operating system's point of view, except for some very old nonstandard CD-ROM drives which are neither SCSI nor IDE/ATAPI." msgstr "" #. Tag: para -#: hardware.xml:1937 +#: hardware.xml:1958 #, no-c-format msgid "CD-ROM based installation is supported for some architectures. On machines which support bootable CD-ROMs, you should be able to do a completely <phrase arch=\"not-s390\">floppy-less</phrase> <phrase arch=\"s390\">tape-less</phrase> installation. Even if your system doesn't support booting from a CD-ROM, you can use the CD-ROM in conjunction with the other techniques to install your system, once you've booted up by other means; see <xref linkend=\"boot-installer\"/>." msgstr "" #. Tag: para -#: hardware.xml:1949 +#: hardware.xml:1970 #, no-c-format msgid "Both SCSI and IDE/ATAPI CD-ROMs are supported. In addition, all non-standard CD interfaces supported by Linux are supported by the boot disks (such as Mitsumi and Matsushita drives). However, these models might require special boot parameters or other massaging to get them to work, and booting off these non-standard interfaces is unlikely. The <ulink url=\"&url-cd-howto;\">Linux CD-ROM HOWTO</ulink> contains in-depth information on using CD-ROMs with Linux." msgstr "" #. Tag: para -#: hardware.xml:1959 +#: hardware.xml:1980 #, no-c-format msgid "USB CD-ROM drives are also supported, as are FireWire devices that are supported by the ohci1394 and sbp2 drivers." msgstr "" #. Tag: para -#: hardware.xml:1964 +#: hardware.xml:1985 #, no-c-format msgid "Both SCSI and IDE/ATAPI CD-ROMs are supported on &arch-title;, as long as the controller is supported by the SRM console. This rules out many add-on controller cards, but most integrated IDE and SCSI chips and controller cards that were provided by the manufacturer can be expected to work. To find out whether your device is supported from the SRM console, see the <ulink url=\"&url-srm-howto;\">SRM HOWTO</ulink>." msgstr "" #. Tag: para -#: hardware.xml:1973 +#: hardware.xml:1994 #, no-c-format msgid "IDE/ATAPI CD-ROMs are supported on all ARM machines. <phrase condition=\"etch\">On RiscPCs, SCSI CD-ROMs are also supported.</phrase>" msgstr "" #. Tag: para -#: hardware.xml:1978 +#: hardware.xml:1999 #, no-c-format msgid "On SGI machines, booting from CD-ROM requires a SCSI CD-ROM drive capable of working with a logical blocksize of 512 bytes. Many of the SCSI CD-ROM drives sold on the PC market do not have this capability. If your CD-ROM drive has a jumper labeled <quote>Unix/PC</quote> or <quote>512/2048</quote>, place it in the <quote>Unix</quote> or <quote>512</quote> position. To start the install, simply choose the <quote>System installation</quote> entry in the firmware. The Broadcom BCM91250A supports standard IDE devices, including CD-ROM drives, but CD images for this platform are currently not provided because the firmware doesn't recognize CD drives. In order to install Debian on an Broadcom BCM91480B evaluation board, you need an PCI IDE, SATA or SCSI card." msgstr "" #. Tag: para -#: hardware.xml:1993 +#: hardware.xml:2014 #, no-c-format msgid "On DECstations, booting from CD-ROM requires a SCSI CD-ROM drive capable of working with a logical blocksize of 512 bytes. Many of the SCSI CD-ROM drives sold on the PC market do not have this capability. If your CD-ROM drive has a jumper labeled <quote>Unix/PC</quote> or <quote>512/2048</quote>, place it in the <quote>Unix</quote> or <quote>512</quote> position." msgstr "" #. Tag: para -#: hardware.xml:2002 +#: hardware.xml:2023 #, no-c-format msgid "CD 1 contains the installer for the r3k-kn02 subarchitecture (the R3000-based DECstations 5000/1xx and 5000/240 as well as the R3000-based Personal DECstation models), CD 2 the installer for the r4k-kn04 subarchitecture (the R4x00-based DECstations 5000/150 and 5000/260 as well as the Personal DECstation 5000/50)." msgstr "" #. Tag: para -#: hardware.xml:2011 +#: hardware.xml:2032 #, no-c-format msgid "To boot from CD, issue the command <userinput>boot <replaceable>#</replaceable>/rz<replaceable>id</replaceable></userinput> on the firmware prompt, where <replaceable>#</replaceable> is the number of the TurboChannel device from which to boot (3 on most DECstations) and <replaceable>id</replaceable> is the SCSI ID of the CD-ROM drive. If you need to pass additional parameters, they can optionally be appended with the following syntax:" msgstr "" #. Tag: userinput -#: hardware.xml:2023 +#: hardware.xml:2044 #, no-c-format msgid "boot <replaceable>#</replaceable>/rz<replaceable>id</replaceable> param1=value1 param2=value2 ..." msgstr "" #. Tag: title -#: hardware.xml:2030 +#: hardware.xml:2051 #, no-c-format msgid "Hard Disk" msgstr "" #. Tag: para -#: hardware.xml:2032 +#: hardware.xml:2053 #, no-c-format msgid "Booting the installation system directly from a hard disk is another option for many architectures. This will require some other operating system to load the installer onto the hard disk." msgstr "" #. Tag: para -#: hardware.xml:2038 +#: hardware.xml:2059 #, no-c-format msgid "In fact, installation from your local disk is the preferred installation technique for most &architecture; machines." msgstr "" #. Tag: para -#: hardware.xml:2043 +#: hardware.xml:2064 #, no-c-format msgid "Although the &arch-title; does not allow booting from SunOS (Solaris), you can install from a SunOS partition (UFS slices)." msgstr "" #. Tag: title -#: hardware.xml:2051 +#: hardware.xml:2072 #, no-c-format msgid "USB Memory Stick" msgstr "" #. Tag: para -#: hardware.xml:2053 +#: hardware.xml:2074 #, no-c-format msgid "Many Debian boxes need their floppy and/or CD-ROM drives only for setting up the system and for rescue purposes. If you operate some servers, you will probably already have thought about omitting those drives and using an USB memory stick for installing and (when necessary) for recovering the system. This is also useful for small systems which have no room for unnecessary drives." msgstr "" #. Tag: title -#: hardware.xml:2065 +#: hardware.xml:2086 #, no-c-format msgid "Network" msgstr "" #. Tag: para -#: hardware.xml:2067 +#: hardware.xml:2088 #, no-c-format msgid "The network can be used during the installation to retrieve files needed for the installation. Whether the network is used or not depends on the installation method you choose and your answers to certain questions that will be asked during the installation. The installation system supports most types of network connections (including PPPoE, but not ISDN or PPP), via either HTTP or FTP. After the installation is completed, you can also configure your system to use ISDN and PPP." msgstr "" #. Tag: para -#: hardware.xml:2077 +#: hardware.xml:2098 #, no-c-format msgid "You can also <emphasis>boot</emphasis> the installation system over the network. <phrase arch=\"mips\">This is the preferred installation technique for &arch-title;.</phrase>" msgstr "" #. Tag: para -#: hardware.xml:2083 +#: hardware.xml:2104 #, no-c-format msgid "Diskless installation, using network booting from a local area network and NFS-mounting of all local filesystems, is another option." msgstr "" #. Tag: title -#: hardware.xml:2091 +#: hardware.xml:2112 #, no-c-format msgid "Un*x or GNU system" msgstr "" #. Tag: para -#: hardware.xml:2093 +#: hardware.xml:2114 #, no-c-format msgid "If you are running another Unix-like system, you could use it to install &debian; without using the &d-i; described in the rest of this manual. This kind of install may be useful for users with otherwise unsupported hardware or on hosts which can't afford downtime. If you are interested in this technique, skip to the <xref linkend=\"linux-upgrade\"/>." msgstr "" #. Tag: title -#: hardware.xml:2105 +#: hardware.xml:2126 #, no-c-format msgid "Supported Storage Systems" msgstr "" #. Tag: para -#: hardware.xml:2107 +#: hardware.xml:2128 #, no-c-format msgid "The Debian boot disks contain a kernel which is built to maximize the number of systems it runs on. Unfortunately, this makes for a larger kernel, which includes many drivers that won't be used for your machine (see <xref linkend=\"kernel-baking\"/> to learn how to build your own kernel). Support for the widest possible range of devices is desirable in general, to ensure that Debian can be installed on the widest array of hardware." msgstr "" #. Tag: para -#: hardware.xml:2117 +#: hardware.xml:2138 #, no-c-format msgid "Generally, the Debian installation system includes support for floppies, IDE drives, IDE floppies, parallel port IDE devices, SCSI controllers and drives, USB, and FireWire. The supported file systems include FAT, Win-32 FAT extensions (VFAT) and NTFS." msgstr "" #. Tag: para -#: hardware.xml:2124 +#: hardware.xml:2145 #, no-c-format msgid "Disk interfaces that emulate the <quote>AT</quote> hard disk interface — often called MFM, RLL, IDE, or ATA — are supported. Very old 8–bit hard disk controllers used in the IBM XT computer are supported only as a module. SCSI disk controllers from many different manufacturers are supported. See the <ulink url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink> for more details." msgstr "" #. Tag: para -#: hardware.xml:2134 +#: hardware.xml:2155 #, no-c-format msgid "Pretty much all storage systems supported by the Linux kernel are supported by the Debian installation system. Note that the current Linux kernel does not support floppies on the Macintosh at all, and the Debian installation system doesn't support floppies for Amigas. Also supported on the Atari is the Macintosh HFS system, and AFFS as a module. Macs support the Atari (FAT) file system. Amigas support the FAT file system, and HFS as a module." msgstr "" #. Tag: para -#: hardware.xml:2144 +#: hardware.xml:2165 #, no-c-format msgid "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></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." msgstr "" #. Tag: para -#: hardware.xml:2177 +#: hardware.xml:2198 #, no-c-format msgid "Any storage system supported by the Linux kernel is also supported by the boot system. This includes both SCSI and IDE disks. Note, however, that on many systems, the SRM console is unable to boot from IDE drives, and the Jensen is unable to boot from floppies. (see <ulink url=\"&url-jensen-howto;\"></ulink> for more information on booting the Jensen)" msgstr "" #. Tag: para -#: hardware.xml:2186 +#: hardware.xml:2207 #, no-c-format msgid "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." msgstr "" #. Tag: para -#: hardware.xml:2192 +#: hardware.xml:2213 #, no-c-format msgid "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." msgstr "" #. Tag: para -#: hardware.xml:2198 +#: hardware.xml:2219 #, no-c-format msgid "Any storage system supported by the Linux kernel is also supported by the boot system." msgstr "" #. Tag: para -#: hardware.xml:2203 +#: hardware.xml:2224 #, no-c-format msgid "Any storage system supported by the Linux kernel is also supported by the boot system. This means that FBA and ECKD DASDs are supported with the old Linux disk layout (ldl) and the new common S/390 disk layout (cdl)." msgstr "" #. Tag: title -#: hardware.xml:2220 +#: hardware.xml:2241 #, no-c-format msgid "Peripherals and Other Hardware" msgstr "" #. Tag: para -#: hardware.xml:2221 +#: hardware.xml:2242 #, no-c-format msgid "Linux supports a large variety of hardware devices such as mice, printers, scanners, PCMCIA and USB devices. However, most of these devices are not required while installing the system." msgstr "" #. Tag: para -#: hardware.xml:2227 +#: hardware.xml:2248 #, no-c-format msgid "USB hardware generally works fine, only some USB keyboards may require additional configuration (see <xref linkend=\"hardware-issues\"/>)." msgstr "" #. Tag: para -#: hardware.xml:2233 +#: hardware.xml:2254 #, no-c-format msgid "Again, see the <ulink url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink> to determine whether your specific hardware is supported by Linux." msgstr "" #. Tag: para -#: hardware.xml:2239 +#: hardware.xml:2260 #, no-c-format msgid "Package installations from XPRAM and tape are not supported by this system. All packages that you want to install need to be available on a DASD or over the network using NFS, HTTP or FTP." msgstr "" #. Tag: para -#: hardware.xml:2245 +#: hardware.xml:2266 #, no-c-format msgid "The Broadcom BCM91250A evaluation board offers standard 3.3v 32 bit and 64 bit PCI slots as well as USB connectors. The Broadcom BCM91480B evaluation board features four 64 bit PCI slots." msgstr "" #. Tag: para -#: hardware.xml:2251 +#: hardware.xml:2272 #, no-c-format msgid "The Broadcom BCM91250A evaluation board offers standard 3.3v 32 bit and 64 bit PCI slots as well as USB connectors. The Broadcom BCM91480B evaluation board features four 64 bit PCI slots. The Cobalt RaQ has no support for additional devices but the Qube has one PCI slot." msgstr "" #. Tag: title -#: hardware.xml:2261 +#: hardware.xml:2282 #, no-c-format msgid "Purchasing Hardware Specifically for GNU/Linux" msgstr "" #. Tag: para -#: hardware.xml:2263 +#: hardware.xml:2284 #, no-c-format msgid "There are several vendors, who ship systems with Debian or other distributions of GNU/Linux <ulink url=\"&url-pre-installed;\">pre-installed</ulink>. You might pay more for the privilege, but it does buy a level of peace of mind, since you can be sure that the hardware is well-supported by GNU/Linux." msgstr "" #. Tag: para -#: hardware.xml:2271 +#: hardware.xml:2292 #, no-c-format msgid "Unfortunately, it's quite rare to find any vendor shipping new &arch-title; machines at all." msgstr "" #. Tag: para -#: hardware.xml:2276 +#: hardware.xml:2297 #, no-c-format msgid "If you do have to buy a machine with Windows bundled, carefully read the software license that comes with Windows; you may be able to reject the license and obtain a rebate from your vendor. Searching the Internet for <quote>windows refund</quote> may get you some useful information to help with that." msgstr "" #. Tag: para -#: hardware.xml:2284 +#: hardware.xml:2305 #, no-c-format msgid "Whether or not you are purchasing a system with Linux bundled, or even a used system, it is still important to check that your hardware is supported by the Linux kernel. Check if your hardware is listed in the references found above. Let your salesperson (if any) know that you're shopping for a Linux system. Support Linux-friendly hardware vendors." msgstr "" #. Tag: title -#: hardware.xml:2295 +#: hardware.xml:2316 #, no-c-format msgid "Avoid Proprietary or Closed Hardware" msgstr "" #. Tag: para -#: hardware.xml:2296 +#: hardware.xml:2317 #, no-c-format msgid "Some hardware manufacturers simply won't tell us how to write drivers for their hardware. Others won't allow us access to the documentation without a non-disclosure agreement that would prevent us from releasing the Linux source code." msgstr "" #. Tag: para -#: hardware.xml:2303 +#: hardware.xml:2324 #, no-c-format msgid "Another example is the proprietary hardware in the older Macintosh line. In fact, no specifications or documentation have ever been released for any Macintosh hardware, most notably the ADB controller (used by the mouse and keyboard), the floppy controller, and all acceleration and CLUT manipulation of the video hardware (though we do now support CLUT manipulation on nearly all internal video chips). In a nutshell, this explains why the Macintosh Linux port lags behind other Linux ports." msgstr "" #. Tag: para -#: hardware.xml:2314 +#: hardware.xml:2335 #, no-c-format msgid "Since we haven't been granted access to the documentation on these devices, they simply won't work under Linux. You can help by asking the manufacturers of such hardware to release the documentation. If enough people ask, they will realize that the free software community is an important market." msgstr "" #. Tag: title -#: hardware.xml:2326 +#: hardware.xml:2347 #, no-c-format msgid "Windows-specific Hardware" msgstr "" #. Tag: para -#: hardware.xml:2327 +#: hardware.xml:2348 #, no-c-format msgid "A disturbing trend is the proliferation of Windows-specific modems and printers. In some cases these are specially designed to be operated by the Microsoft Windows operating system and bear the legend <quote>WinModem</quote> or <quote>Made especially for Windows-based computers</quote>. This is generally done by removing the embedded processors of the hardware and shifting the work they do over to a Windows driver that is run by your computer's main CPU. This strategy makes the hardware less expensive, but the savings are often <emphasis>not</emphasis> passed on to the user and this hardware may even be more expensive than equivalent devices that retain their embedded intelligence." msgstr "" #. Tag: para -#: hardware.xml:2340 +#: hardware.xml:2361 #, no-c-format msgid "You should avoid Windows-specific hardware for two reasons. The first is that the manufacturers do not generally make the resources available to write a Linux driver. Generally, the hardware and software interface to the device is proprietary, and documentation is not available without a non-disclosure agreement, if it is available at all. This precludes it being used for free software, since free software writers disclose the source code of their programs. The second reason is that when devices like these have had their embedded processors removed, the operating system must perform the work of the embedded processors, often at <emphasis>real-time</emphasis> priority, and thus the CPU is not available to run your programs while it is driving these devices. Since the typical Windows user does not multi-process as intensively as a Linux user, the manufacturers hope that the Windows user simply won't notice the burden this hardware places on their CPU. However, any multi-processing operating system, even Windows 2000 or XP, suffers from degraded performance when peripheral manufacturers skimp on the embedded processing power of their hardware." msgstr "" #. Tag: para -#: hardware.xml:2361 +#: hardware.xml:2382 #, no-c-format msgid "You can help improve this situation by encouraging these manufacturers to release the documentation and other resources necessary for us to program their hardware, but the best strategy is simply to avoid this sort of hardware until it is listed as working in the <ulink url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink>." msgstr "" #. Tag: title -#: hardware.xml:2378 +#: hardware.xml:2399 #, no-c-format msgid "Memory and Disk Space Requirements" msgstr "" #. Tag: para -#: hardware.xml:2380 +#: hardware.xml:2401 #, no-c-format msgid "You must have at least &minimum-memory; of memory and &minimum-fs-size; of hard disk space. Note that these are really bare-minimum numbers. For more realistic figures, see <xref linkend=\"minimum-hardware-reqts\"/>." msgstr "" #. Tag: para -#: hardware.xml:2386 +#: hardware.xml:2407 #, no-c-format msgid "On the Amiga the size of FastRAM is relevant towards the total memory requirements. Also, using Zorro cards with 16-bit RAM is not supported; you'll need 32-bit RAM. The <command>amiboot</command> program can be used to disable 16-bit RAM; see the <ulink url=\"&url-m68k-faq;\">Linux/m68k FAQ</ulink>. Recent kernels should disable 16-bit RAM automatically." msgstr "" #. Tag: para -#: hardware.xml:2395 +#: hardware.xml:2416 #, no-c-format msgid "On the Atari, both ST-RAM and Fast RAM (TT-RAM) are used by Linux. Many users have reported problems running the kernel itself in Fast RAM, so the Atari bootstrap will place the kernel in ST-RAM. The minimum requirement for ST-RAM is 2 MB. You will need an additional 12 MB or more of TT-RAM." msgstr "" #. Tag: para -#: hardware.xml:2403 +#: hardware.xml:2424 #, no-c-format msgid "On the Macintosh, care should be taken on machines with RAM-based video (RBV). The RAM segment at physical address 0 is used as screen memory, making the default load position for the kernel unavailable. The alternate RAM segment used for kernel and RAMdisk must be at least 4 MB." msgstr "" #. Tag: emphasis -#: hardware.xml:2413 +#: hardware.xml:2434 #, no-c-format msgid "FIXME: is this still true?" msgstr "" #. Tag: title -#: hardware.xml:2424 +#: hardware.xml:2445 #, no-c-format msgid "Network Connectivity Hardware" msgstr "" #. Tag: para -#: hardware.xml:2425 +#: hardware.xml:2446 #, no-c-format msgid "Almost any network interface card (NIC) supported by the Linux kernel should also be supported by the installation system; modular drivers should normally be loaded automatically. <phrase arch=\"x86\">This includes most PCI and PCMCIA cards.</phrase> <phrase arch=\"i386\">Many older ISA cards are supported as well.</phrase> <phrase arch=\"m68k\">Again, see <ulink url=\"&url-m68k-faq;\"></ulink> for complete details.</phrase>" msgstr "" #. Tag: para -#: hardware.xml:2437 +#: hardware.xml:2458 #, no-c-format msgid "This includes a lot of generic PCI cards (for systems that have PCI) and the following NICs from Sun:" msgstr "" #. Tag: para -#: hardware.xml:2443 +#: hardware.xml:2464 #, no-c-format msgid "Sun LANCE" msgstr "" #. Tag: para -#: hardware.xml:2448 +#: hardware.xml:2469 #, no-c-format msgid "Sun Happy Meal" msgstr "" #. Tag: para -#: hardware.xml:2453 +#: hardware.xml:2474 #, no-c-format msgid "Sun BigMAC" msgstr "" #. Tag: para -#: hardware.xml:2458 +#: hardware.xml:2479 #, no-c-format msgid "Sun QuadEthernet" msgstr "" #. Tag: para -#: hardware.xml:2463 +#: hardware.xml:2484 #, no-c-format msgid "MyriCOM Gigabit Ethernet" msgstr "" #. Tag: para -#: hardware.xml:2470 +#: hardware.xml:2491 #, no-c-format msgid "Due to kernel limitations only the onboard network interfaces on DECstations are supported, TurboChannel option network cards currently do not work." msgstr "" #. Tag: para -#: hardware.xml:2476 +#: hardware.xml:2497 #, no-c-format msgid "The list of supported network devices is:" msgstr "" #. Tag: para -#: hardware.xml:2481 +#: hardware.xml:2502 #, no-c-format msgid "Channel to Channel (CTC) and ESCON connection (real or emulated)" msgstr "" #. Tag: para -#: hardware.xml:2486 +#: hardware.xml:2507 #, no-c-format msgid "OSA-2 Token Ring/Ethernet and OSA-Express Fast Ethernet (non-QDIO)" msgstr "" #. Tag: para -#: hardware.xml:2491 +#: hardware.xml:2512 #, no-c-format msgid "OSA-Express in QDIO mode, HiperSockets and Guest-LANs" msgstr "" #. Tag: para -#: hardware.xml:2500 +#: hardware.xml:2521 #, no-c-format msgid "On &arch-title;, most built-in Ethernet devices are supported and modules for additional PCI and USB devices are provided. The major exception is the IXP4xx platform (featuring devices such as the Linksys NSLU2) which needs a proprietary microcode for the operation of its built-in Ethernet device. Unofficial images for Linksys NSLU2 with this proprietary microcode can be obtained from the <ulink url=\"&url-slug-firmware;\">Slug-Firmware site</ulink>." msgstr "" #. Tag: para -#: hardware.xml:2510 +#: hardware.xml:2531 #, no-c-format msgid "As for ISDN, the D-channel protocol for the (old) German 1TR6 is not supported; Spellcaster BRI ISDN boards are also not supported by the &d-i;. Using ISDN during the installation is not supported." msgstr "" #. Tag: title -#: hardware.xml:2519 +#: hardware.xml:2540 #, no-c-format msgid "Drivers Requiring Firmware" msgstr "" #. Tag: para -#: hardware.xml:2520 +#: hardware.xml:2541 #, no-c-format msgid "The installation system currently does not support retrieving firmware. This means that any network cards that use a driver that requires firmware to be loaded, is not supported by default." msgstr "" #. Tag: para -#: hardware.xml:2526 +#: hardware.xml:2547 #, no-c-format msgid "If there is no other NIC you can use during the installation, it is still possible to install &debian; using a full CD-ROM or DVD image. Select the option to not configure a network and install using only the packages available from the CD/DVD. You can then install the driver and firmware you need after the installation is completed (after the reboot) and configure your network manually. Note that the firmware may be packaged separately from the driver and may not be available in the <quote>main</quote> section of the &debian; archive." msgstr "" #. Tag: para -#: hardware.xml:2537 +#: hardware.xml:2558 #, no-c-format msgid "If the driver itself <emphasis>is</emphasis> supported, you may also be able to use the NIC during installation by copying the firmware from some medium to <filename>/usr/lib/hotplug/firmware</filename>. Don't forget to also copy the firmware to that location for the installed system before the reboot at the end of the installation." msgstr "" #. Tag: title -#: hardware.xml:2549 +#: hardware.xml:2570 #, no-c-format msgid "Wireless Network Cards" msgstr "" #. Tag: para -#: hardware.xml:2550 +#: hardware.xml:2571 #, no-c-format msgid "Wireless NICs are in general supported as well, with one big proviso. A lot of wireless adapters require drivers that are either non-free or have not been accepted into the official Linux kernel. These NICs can generally be made to work under &debian;, but are not supported during the installation." msgstr "" #. Tag: para -#: hardware.xml:2557 +#: hardware.xml:2578 #, no-c-format msgid "If there is no other NIC you can use during the installation, it is still possible to install &debian; using a full CD-ROM or DVD image. Use the same procedure as described above for NICs that require firmware." msgstr "" #. Tag: para -#: hardware.xml:2563 +#: hardware.xml:2584 #, no-c-format msgid "In some cases the driver you need may not be available as a Debian package. You will then have to look if there is source code available in the internet and compile the driver yourself. How to do this is outside the scope of this manual. <phrase arch=\"x86\">If no Linux driver is available, your last resort is to use the <classname>ndiswrapper</classname> package, which allows you to use a Windows driver.</phrase>" msgstr "" #. Tag: title -#: hardware.xml:2577 +#: hardware.xml:2598 #, no-c-format msgid "Known Issues for &arch-title;" msgstr "" #. Tag: para -#: hardware.xml:2578 +#: hardware.xml:2599 #, no-c-format msgid "There are a couple of issues with specific network cards that are worth mentioning here." msgstr "" #. Tag: title -#: hardware.xml:2585 +#: hardware.xml:2606 #, no-c-format msgid "Conflict between tulip and dfme drivers" msgstr "" #. Tag: para -#: hardware.xml:2587 +#: hardware.xml:2608 #, no-c-format msgid "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." msgstr "" #. Tag: para -#: hardware.xml:2597 +#: hardware.xml:2618 #, no-c-format msgid "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. During the installation the solution 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>." msgstr "" #. Tag: title -#: hardware.xml:2612 +#: hardware.xml:2633 #, no-c-format msgid "Sun B100 blade" msgstr "" #. Tag: para -#: hardware.xml:2614 +#: hardware.xml:2635 #, no-c-format msgid "The <literal>cassini</literal> network driver does not work with Sun B100 blade systems." msgstr "" diff --git a/po/pot/preparing.pot b/po/pot/preparing.pot index 518798209..5f49a63c6 100644 --- a/po/pot/preparing.pot +++ b/po/pot/preparing.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2007-05-10 19:09+0000\n" +"POT-Creation-Date: 2007-07-26 04:01+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <LL@li.org>\n" @@ -743,7 +743,7 @@ msgstr "" #. Tag: para #: preparing.xml:678 #, no-c-format -msgid "A Pentium 4, 1GHz system is the minimum recommended for a desktop systems." +msgid "A Pentium 4, 1GHz system is the minimum recommended for a desktop system." msgstr "" #. Tag: para @@ -827,7 +827,7 @@ msgstr "" #. Tag: entry #: preparing.xml:716 #, no-c-format -msgid "5 gigabyte" +msgid "5 gigabytes" msgstr "" #. Tag: para diff --git a/po/pot/preseed.pot b/po/pot/preseed.pot index a40da36d7..f603b559c 100644 --- a/po/pot/preseed.pot +++ b/po/pot/preseed.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2007-07-20 17:30+0000\n" +"POT-Creation-Date: 2007-07-26 04:00+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <LL@li.org>\n" @@ -877,10 +877,14 @@ msgid "" "#d-i partman-auto/init_automatically_partition \\\n" "# select Guided - use the largest continuous free space\n" "\n" - "# Alternatively, you can specify a disk to partition. The device name\n" + "<phrase condition=\"etch\"># Alternatively, you can specify a disk to partition. The device name\n" "# can be given in either devfs or traditional non-devfs format.\n" "# For example, to use the first disk:\n" - "d-i partman-auto/disk string /dev/discs/disc0/disc\n" + "d-i partman-auto/disk string /dev/discs/disc0/disc</phrase><phrase condition=\"lenny\">\n" + "# Alternatively, you can specify a disk to partition. The device name must\n" + "# be given in traditional non-devfs format.\n" + "# For example, to use the first SCSI/SATA hard disk:\n" + "d-i partman-auto/disk string /dev/sda</phrase>\n" "# In addition, you'll need to specify the method to use.\n" "# The presently available methods are: \"regular\", \"lvm\" and \"crypto\"\n" "d-i partman-auto/method string lvm\n" @@ -1024,7 +1028,13 @@ msgid "" "\n" "# You may set this to any valid setting for $TZ; see the contents of\n" "# /usr/share/zoneinfo/ for valid values.\n" - "d-i time/zone string US/Eastern" + "d-i time/zone string US/Eastern<phrase condition=\"lenny\">\n" + "\n" + "# Controls whether to use NTP to set the clock during the install\n" + "d-i clock-setup/ntp boolean true\n" + "# NTP server to use. The default is almost always fine here.\n" + "#d-i clock-setup/ntp-server ntp.example.com\n" + "</phrase>" msgstr "" #. Tag: title diff --git a/po/pot/using-d-i.pot b/po/pot/using-d-i.pot index 0b7aedac2..31dbf6fa8 100644 --- a/po/pot/using-d-i.pot +++ b/po/pot/using-d-i.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2007-06-10 22:49+0000\n" +"POT-Creation-Date: 2007-07-26 04:01+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <LL@li.org>\n" @@ -1796,125 +1796,125 @@ msgstr "" #. Tag: para #: using-d-i.xml:2276 #, no-c-format -msgid "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 devfs style names, such as those that start with <filename>/dev/ide</filename>, <filename>/dev/scsi</filename>, and <filename>/dev/discs</filename>, as well as traditional names, such as <filename>/dev/hda</filename> or <filename>/dev/sda</filename>." +msgid "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 <phrase condition=\"etch\">devfs style names, such as those that start with <filename>/dev/ide</filename>, <filename>/dev/scsi</filename>, and <filename>/dev/discs</filename>, as well as traditional names,</phrase> <phrase condition=\"lenny\">traditional device names</phrase> such as <filename>/dev/hda</filename> or <filename>/dev/sda</filename>." msgstr "" #. Tag: para -#: using-d-i.xml:2288 +#: using-d-i.xml:2290 #, no-c-format msgid "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!" msgstr "" #. Tag: title -#: using-d-i.xml:2304 +#: using-d-i.xml:2306 #, no-c-format msgid "Install the <command>ELILO</command> Boot Loader on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2306 +#: using-d-i.xml:2308 #, no-c-format msgid "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." msgstr "" #. Tag: para -#: using-d-i.xml:2322 +#: using-d-i.xml:2324 #, no-c-format msgid "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." msgstr "" #. Tag: title -#: using-d-i.xml:2334 +#: using-d-i.xml:2336 #, no-c-format msgid "Choose the correct partition!" msgstr "" #. Tag: para -#: using-d-i.xml:2336 +#: using-d-i.xml:2338 #, no-c-format msgid "The criteria for selecting a partition is that it is 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!" msgstr "" #. Tag: title -#: using-d-i.xml:2351 +#: using-d-i.xml:2353 #, no-c-format msgid "EFI Partition Contents" msgstr "" #. Tag: para -#: using-d-i.xml:2353 +#: using-d-i.xml:2355 #, no-c-format msgid "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." msgstr "" #. Tag: filename -#: using-d-i.xml:2375 +#: using-d-i.xml:2377 #, no-c-format msgid "elilo.conf" msgstr "" #. Tag: para -#: using-d-i.xml:2376 +#: using-d-i.xml:2378 #, no-c-format msgid "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." msgstr "" #. Tag: filename -#: using-d-i.xml:2385 +#: using-d-i.xml:2387 #, no-c-format msgid "elilo.efi" msgstr "" #. Tag: para -#: using-d-i.xml:2386 +#: using-d-i.xml:2388 #, no-c-format msgid "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." msgstr "" #. Tag: filename -#: using-d-i.xml:2396 +#: using-d-i.xml:2398 #, no-c-format msgid "initrd.img" msgstr "" #. Tag: para -#: using-d-i.xml:2397 +#: using-d-i.xml:2399 #, no-c-format msgid "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>." msgstr "" #. Tag: filename -#: using-d-i.xml:2409 +#: using-d-i.xml:2411 #, no-c-format msgid "readme.txt" msgstr "" #. Tag: para -#: using-d-i.xml:2410 +#: using-d-i.xml:2412 #, no-c-format msgid "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." msgstr "" #. Tag: filename -#: using-d-i.xml:2420 +#: using-d-i.xml:2422 #, no-c-format msgid "vmlinuz" msgstr "" #. Tag: para -#: using-d-i.xml:2421 +#: using-d-i.xml:2423 #, no-c-format msgid "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>." msgstr "" #. Tag: title -#: using-d-i.xml:2441 +#: using-d-i.xml:2443 #, no-c-format msgid "<command>arcboot</command>-installer" msgstr "" #. Tag: para -#: using-d-i.xml:2442 +#: using-d-i.xml:2444 #, no-c-format msgid "" "The boot loader on SGI machines is <command>arcboot</command>. It has to be installed on the same hard disk as the kernel (this is done automatically by the installer). Arcboot supports different configurations which are set up in <filename>/etc/arcboot.conf</filename>. Each configuration has a unique name, the default setup as created by the installer is <quote>linux</quote>. After arcboot has been installed, the system can be booted from hard disk by setting some firmware environment variables entering <informalexample><screen>\n" @@ -1927,61 +1927,61 @@ msgid "" msgstr "" #. Tag: replaceable -#: using-d-i.xml:2461 +#: using-d-i.xml:2463 #, no-c-format msgid "scsi" msgstr "" #. Tag: para -#: using-d-i.xml:2462 +#: using-d-i.xml:2464 #, no-c-format msgid "is the SCSI bus to be booted from, this is <userinput>0</userinput> for the onboard controllers" msgstr "" #. Tag: replaceable -#: using-d-i.xml:2470 +#: using-d-i.xml:2472 #, no-c-format msgid "disk" msgstr "" #. Tag: para -#: using-d-i.xml:2471 +#: using-d-i.xml:2473 #, no-c-format msgid "is the SCSI ID of the hard disk on which <command>arcboot</command> is installed" msgstr "" #. Tag: replaceable -#: using-d-i.xml:2479 using-d-i.xml:2548 +#: using-d-i.xml:2481 using-d-i.xml:2550 #, no-c-format msgid "partnr" msgstr "" #. Tag: para -#: using-d-i.xml:2480 +#: using-d-i.xml:2482 #, no-c-format msgid "is the number of the partition on which <filename>/etc/arcboot.conf</filename> resides" msgstr "" #. Tag: replaceable -#: using-d-i.xml:2488 +#: using-d-i.xml:2490 #, no-c-format msgid "config" msgstr "" #. Tag: para -#: using-d-i.xml:2489 +#: using-d-i.xml:2491 #, no-c-format msgid "is the name of the configuration entry in <filename>/etc/arcboot.conf</filename>, which is <quote>linux</quote> by default." msgstr "" #. Tag: title -#: using-d-i.xml:2510 +#: using-d-i.xml:2512 #, no-c-format msgid "<command>delo</command>-installer" msgstr "" #. Tag: para -#: using-d-i.xml:2511 +#: using-d-i.xml:2513 #, no-c-format msgid "" "The boot loader on DECstations is <command>DELO</command>. It has to be installed on the same hard disk as the kernel (this is done automatically by the installer). DELO supports different configurations which are set up in <filename>/etc/delo.conf</filename>. Each configuration has a unique name, the default setup as created by the installer is <quote>linux</quote>. After DELO has been installed, the system can be booted from hard disk by entering <informalexample><screen>\n" @@ -1990,265 +1990,265 @@ msgid "" msgstr "" #. Tag: replaceable -#: using-d-i.xml:2530 +#: using-d-i.xml:2532 #, no-c-format msgid "<replaceable>#</replaceable>" msgstr "" #. Tag: para -#: using-d-i.xml:2531 +#: using-d-i.xml:2533 #, no-c-format msgid "is the TurboChannel device to be booted from, on most DECstations this is <userinput>3</userinput> for the onboard controllers" msgstr "" #. Tag: replaceable -#: using-d-i.xml:2539 +#: using-d-i.xml:2541 #, no-c-format msgid "<replaceable>id</replaceable>" msgstr "" #. Tag: para -#: using-d-i.xml:2540 +#: using-d-i.xml:2542 #, no-c-format msgid "is the SCSI ID of the hard disk on which <command>DELO</command> is installed" msgstr "" #. Tag: para -#: using-d-i.xml:2549 +#: using-d-i.xml:2551 #, no-c-format msgid "is the number of the partition on which <filename>/etc/delo.conf</filename> resides" msgstr "" #. Tag: replaceable -#: using-d-i.xml:2557 +#: using-d-i.xml:2559 #, no-c-format msgid "name" msgstr "" #. Tag: para -#: using-d-i.xml:2558 +#: using-d-i.xml:2560 #, no-c-format msgid "is the name of the configuration entry in <filename>/etc/delo.conf</filename>, which is <quote>linux</quote> by default." msgstr "" #. Tag: para -#: using-d-i.xml:2568 +#: using-d-i.xml:2570 #, no-c-format msgid "In case <filename>/etc/delo.conf</filename> is on the first partition on the disk and the default configuration shall be booted, it is sufficient to use" msgstr "" #. Tag: screen -#: using-d-i.xml:2574 +#: using-d-i.xml:2576 #, no-c-format msgid "<userinput>boot #/rz<replaceable>id</replaceable></userinput>" msgstr "" #. Tag: title -#: using-d-i.xml:2584 +#: using-d-i.xml:2586 #, no-c-format msgid "Install <command>Yaboot</command> on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2585 +#: using-d-i.xml:2587 #, no-c-format msgid "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;." msgstr "" #. Tag: title -#: using-d-i.xml:2603 +#: using-d-i.xml:2605 #, no-c-format msgid "Install <command>Quik</command> on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2604 +#: using-d-i.xml:2606 #, no-c-format msgid "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." msgstr "" #. Tag: title -#: using-d-i.xml:2620 +#: using-d-i.xml:2622 #, no-c-format msgid "<command>zipl</command>-installer" msgstr "" #. Tag: para -#: using-d-i.xml:2621 +#: using-d-i.xml:2623 #, no-c-format msgid "The boot loader on &arch-title; is <quote>zipl</quote>. <command>ZIPL</command> is similar in configuration and usage to <command>LILO</command>, with a few exceptions. Please take a look at <quote>LINUX for &arch-title; Device Drivers and Installation Commands</quote> from IBM's developerWorks web site if you want to know more about <command>ZIPL</command>." msgstr "" #. Tag: title -#: using-d-i.xml:2638 +#: using-d-i.xml:2640 #, no-c-format msgid "Install the <command>SILO</command> Boot Loader on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2640 +#: using-d-i.xml:2642 #, no-c-format msgid "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." msgstr "" #. Tag: title -#: using-d-i.xml:2665 +#: using-d-i.xml:2667 #, no-c-format msgid "Continue Without Boot Loader" msgstr "" #. Tag: para -#: using-d-i.xml:2667 +#: using-d-i.xml:2669 #, no-c-format msgid "This option can be used to complete the installation even when no boot loader is to be installed, either because the arch/subarch doesn't provide one, or because none is desired (e.g. you will use existing boot loader). <phrase arch=\"m68k\">This option is especially useful for Macintosh, Atari, and Amiga systems, where the original operating system must be maintained on the box and used to boot GNU/Linux.</phrase>" msgstr "" #. Tag: para -#: using-d-i.xml:2676 +#: using-d-i.xml:2678 #, no-c-format msgid "If you plan to manually configure your bootloader, you should check the name of the installed kernel in <filename>/target/boot</filename>. You should also check that directory for the presence of an <firstterm>initrd</firstterm>; if one is present, you will probably have to instruct your bootloader to use it. Other information you will need are the disk and partition you selected for your <filename>/</filename> filesystem and, if you chose to install <filename>/boot</filename> on a separate partition, also your <filename>/boot</filename> filesystem." msgstr "" #. Tag: title -#: using-d-i.xml:2693 +#: using-d-i.xml:2695 #, no-c-format msgid "Finishing the Installation" msgstr "" #. Tag: para -#: using-d-i.xml:2694 +#: using-d-i.xml:2696 #, no-c-format msgid "These are the last bits to do before rebooting to your new system. It mostly consists of tidying up after the &d-i;." msgstr "" #. Tag: title -#: using-d-i.xml:2706 +#: using-d-i.xml:2708 #, no-c-format msgid "Finish the Installation and Reboot" msgstr "" #. Tag: para -#: using-d-i.xml:2708 +#: using-d-i.xml:2710 #, no-c-format msgid "This is the last step in the initial Debian installation process. You will be prompted to remove the boot media (CD, floppy, etc) that you used to boot the installer. The installer will do any last minute tasks, and then reboot into your new Debian system." msgstr "" #. Tag: para -#: using-d-i.xml:2715 +#: using-d-i.xml:2717 #, no-c-format msgid "Select the <guimenuitem>Finish the installation</guimenuitem> menu item which will halt the system because rebooting is not supported on &arch-title; in this case. You then need to IPL GNU/Linux from the DASD which you selected for the root filesystem during the first steps of the installation." msgstr "" #. Tag: title -#: using-d-i.xml:2729 +#: using-d-i.xml:2731 #, no-c-format msgid "Miscellaneous" msgstr "" #. Tag: para -#: using-d-i.xml:2730 +#: using-d-i.xml:2732 #, no-c-format msgid "The components listed in this section are usually not involved in the installation process, but are waiting in the background to help the user in case something goes wrong." msgstr "" #. Tag: title -#: using-d-i.xml:2743 +#: using-d-i.xml:2745 #, no-c-format msgid "Saving the installation logs" msgstr "" #. Tag: para -#: using-d-i.xml:2745 +#: using-d-i.xml:2747 #, no-c-format msgid "If the installation is successful, the logfiles created during the installation process will be automatically saved to <filename>/var/log/installer/</filename> on your new Debian system." msgstr "" #. Tag: para -#: using-d-i.xml:2752 +#: using-d-i.xml:2754 #, no-c-format msgid "Choosing <guimenuitem>Save debug logs</guimenuitem> from the main menu allows you to save the log files to a floppy disk, network, hard disk, or other media. This can be useful if you encounter fatal problems during the installation and wish to study the logs on another system or attach them to an installation report." msgstr "" #. Tag: title -#: using-d-i.xml:2772 +#: using-d-i.xml:2774 #, no-c-format msgid "Using the Shell and Viewing the Logs" msgstr "" #. Tag: para -#: using-d-i.xml:2774 +#: using-d-i.xml:2776 #, no-c-format msgid "There are several methods you can use to get a shell while running an installation. On most systems, and if you are not installing over serial console, the easiest method is to switch to the second <emphasis>virtual console</emphasis> by pressing <keycombo><keycap>Left Alt</keycap> <keycap>F2</keycap></keycombo><footnote> <para> That is: press the <keycap>Alt</keycap> key on the left-hand side of the <keycap>space bar</keycap> and the <keycap>F2</keycap> function key at the same time. </para> </footnote> (on a Mac keyboard, <keycombo><keycap>Option</keycap> <keycap>F2</keycap></keycombo>). Use <keycombo><keycap>Left Alt</keycap> <keycap>F1</keycap></keycombo> to switch back to installer itself." msgstr "" #. Tag: para -#: using-d-i.xml:2792 +#: using-d-i.xml:2794 #, no-c-format msgid "If you cannot switch consoles, there is also an <guimenuitem>Execute a Shell</guimenuitem> item on the main menu that can be used to start a shell. You can get to the main menu from most dialogs by using the &BTN-GOBACK; button one or more times. Type <userinput>exit</userinput> to close the shell and return to the installer." msgstr "" #. Tag: para -#: using-d-i.xml:2800 +#: using-d-i.xml:2802 #, no-c-format msgid "At this point you are booted from the RAM disk, and there is a limited set of Unix utilities available for your use. You can see what programs are available with the command <command>ls /bin /sbin /usr/bin /usr/sbin</command> and by typing <command>help</command>. The shell is a Bourne shell clone called <command>ash</command> and has some nice features like autocompletion and history." msgstr "" #. Tag: para -#: using-d-i.xml:2809 +#: using-d-i.xml:2811 #, no-c-format msgid "To edit and view files, use the text editor <command>nano</command>. Log files for the installation system can be found in the <filename>/var/log</filename> directory." msgstr "" #. Tag: para -#: using-d-i.xml:2816 +#: using-d-i.xml:2818 #, no-c-format msgid "Although you can do basically anything in a shell that the available commands allow you to do, the option to use a shell is really only there in case something goes wrong and for debugging." msgstr "" #. Tag: para -#: using-d-i.xml:2822 +#: using-d-i.xml:2824 #, no-c-format msgid "Doing things manually from the shell may interfere with the installation process and result in errors or an incomplete installation. In particular, you should always use let the installer activate your swap partition and not do this yourself from a shell." msgstr "" #. Tag: title -#: using-d-i.xml:2837 +#: using-d-i.xml:2839 #, no-c-format msgid "Installation Over the Network" msgstr "" #. Tag: para -#: using-d-i.xml:2839 +#: using-d-i.xml:2841 #, no-c-format msgid "One of the more interesting components is <firstterm>network-console</firstterm>. It allows you to do a large part of the installation over the network via SSH. The use of the network implies you will have to perform the first steps of the installation from the console, at least to the point of setting up the networking. (Although you can automate that part with <xref linkend=\"automatic-install\"/>.)" msgstr "" #. Tag: para -#: using-d-i.xml:2849 +#: using-d-i.xml:2851 #, no-c-format msgid "This component is not loaded into the main installation menu by default, so you have to explicitly ask for it. If you are installing from CD, you need to boot with medium priority or otherwise invoke the main installation menu and choose <guimenuitem>Load installer components from CD</guimenuitem> and from the list of additional components select <guimenuitem>network-console: Continue installation remotely using SSH</guimenuitem>. Successful load is indicated by a new menu entry called <guimenuitem>Continue installation remotely using SSH</guimenuitem>." msgstr "" #. Tag: para -#: using-d-i.xml:2862 +#: using-d-i.xml:2864 #, no-c-format msgid "For installations on &arch-title;, this is the default method after setting up the network." msgstr "" #. Tag: para -#: using-d-i.xml:2867 +#: using-d-i.xml:2869 #, no-c-format msgid "<phrase arch=\"not-s390\">After selecting this new entry, you</phrase> <phrase arch=\"s390\">You</phrase> will be asked for a new password to be used for connecting to the installation system and for its confirmation. That's all. Now you should see a screen which instructs you to login remotely as the user <emphasis>installer</emphasis> with the password you just provided. Another important detail to notice on this screen is the fingerprint of this system. You need to transfer the fingerprint securely to the <quote>person who will continue the installation remotely</quote>." msgstr "" #. Tag: para -#: using-d-i.xml:2879 +#: using-d-i.xml:2881 #, no-c-format msgid "Should you decide to continue with the installation locally, you can always press &enterkey;, which will bring you back to the main menu, where you can select another component." msgstr "" #. Tag: para -#: using-d-i.xml:2885 +#: using-d-i.xml:2887 #, no-c-format msgid "" "Now let's switch to the other side of the wire. As a prerequisite, you need to configure your terminal for UTF-8 encoding, because that is what the installation system uses. If you do not, remote installation will be still possible, but you may encounter strange display artefacts like destroyed dialog borders or unreadable non-ascii characters. Establishing a connection with the installation system is as simple as typing: <informalexample><screen>\n" @@ -2257,25 +2257,25 @@ msgid "" msgstr "" #. Tag: para -#: using-d-i.xml:2902 +#: using-d-i.xml:2904 #, no-c-format msgid "If you install several computers in turn and they happen to have the same IP address or hostname, <command>ssh</command> will refuse to connect to such host. The reason is that it will have different fingerprint, which is usually a sign of a spoofing attack. If you are sure this is not the case, you will need to delete the relevant line from <filename>~/.ssh/known_hosts</filename> and try again." msgstr "" #. Tag: para -#: using-d-i.xml:2911 +#: using-d-i.xml:2913 #, no-c-format msgid "After the login you will be presented with an initial screen where you have two possibilities called <guimenuitem>Start menu</guimenuitem> and <guimenuitem>Start shell</guimenuitem>. The former brings you to the main installer menu, where you can continue with the installation as usual. The latter starts a shell from which you can examine and possibly fix the remote system. You should only start one SSH session for the installation menu, but may start multiple sessions for shells." msgstr "" #. Tag: para -#: using-d-i.xml:2921 +#: using-d-i.xml:2923 #, no-c-format msgid "After you have started the installation remotely over SSH, you should not go back to the installation session running on the local console. Doing so may corrupt the database that holds the configuration of the new system. This in turn may result in a failed installation or problems with the installed system." msgstr "" #. Tag: para -#: using-d-i.xml:2929 +#: using-d-i.xml:2931 #, no-c-format msgid "Also, if you are running the SSH session from an X terminal, you should not resize the window as that will result in the connection being terminated." msgstr "" |