diff options
Diffstat (limited to 'po/pot/hardware.pot')
| -rw-r--r-- | po/pot/hardware.pot | 84 |
1 files changed, 18 insertions, 66 deletions
diff --git a/po/pot/hardware.pot b/po/pot/hardware.pot index cf394da5b..d833e3fd2 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: 2006-12-29 10:24+0000\n" +"POT-Creation-Date: 2006-12-29 19:35+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" @@ -3158,149 +3158,101 @@ msgstr "" #. Tag: para #: hardware.xml:2489 #, no-c-format -msgid "The following network interface cards are supported directly by the installation images for Netwinder and CATS machines:" +msgid "##TODO## Something about NLSU needed." msgstr "" #. Tag: para -#: hardware.xml:2495 -#, no-c-format -msgid "PCI-based NE2000" -msgstr "" - -#. Tag: para -#: hardware.xml:2500 -#, no-c-format -msgid "DECchip Tulip" -msgstr "" - -#. Tag: para -#: hardware.xml:2507 -#, no-c-format -msgid "The following network interface cards are supported directly by the installation images for RiscPCs:" -msgstr "" - -#. Tag: para -#: hardware.xml:2513 -#, no-c-format -msgid "Ether1" -msgstr "" - -#. Tag: para -#: hardware.xml:2518 -#, no-c-format -msgid "Ether3" -msgstr "" - -#. Tag: para -#: hardware.xml:2523 -#, no-c-format -msgid "EtherH" -msgstr "" - -#. Tag: para -#: hardware.xml:2530 -#, no-c-format -msgid "If your card is mentioned in the lists above, the complete installation can be carried out from the network with no need for CD-ROMs or floppy disks." -msgstr "" - -#. Tag: para -#: hardware.xml:2536 -#, no-c-format -msgid "Any other network interface card (NIC) supported by the Linux kernel should also be supported by the boot disks. You may need to load your network driver as a module; this means that you will have to install the operating system kernel and modules using some other media." -msgstr "" - -#. Tag: para -#: hardware.xml:2543 +#: hardware.xml:2493 #, 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:2552 +#: hardware.xml:2502 #, no-c-format msgid "Drivers Requiring Firmware" msgstr "" #. Tag: para -#: hardware.xml:2553 +#: hardware.xml:2503 #, 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:2559 +#: hardware.xml:2509 #, 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:2570 +#: hardware.xml:2520 #, 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:2582 +#: hardware.xml:2532 #, no-c-format msgid "Wireless Network Cards" msgstr "" #. Tag: para -#: hardware.xml:2583 +#: hardware.xml:2533 #, 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:2590 +#: hardware.xml:2540 #, 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:2596 +#: hardware.xml:2546 #, 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:2610 +#: hardware.xml:2560 #, no-c-format msgid "Known Issues for &arch-title;" msgstr "" #. Tag: para -#: hardware.xml:2611 +#: hardware.xml:2561 #, no-c-format msgid "There are a couple of issues with specific network cards that are worth mentioning here." msgstr "" #. Tag: title -#: hardware.xml:2618 +#: hardware.xml:2568 #, no-c-format msgid "Conflict between tulip and dfme drivers" msgstr "" #. Tag: para -#: hardware.xml:2620 +#: hardware.xml:2570 #, 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:2630 +#: hardware.xml:2580 #, 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:2645 +#: hardware.xml:2595 #, no-c-format msgid "Sun B100 blade" msgstr "" #. Tag: para -#: hardware.xml:2647 +#: hardware.xml:2597 #, no-c-format msgid "The <literal>cassini</literal> network driver does not work with Sun B100 blade systems." msgstr "" |