summaryrefslogtreecommitdiff
path: root/po/pot/using-d-i.pot
diff options
context:
space:
mode:
Diffstat (limited to 'po/pot/using-d-i.pot')
-rw-r--r--po/pot/using-d-i.pot28
1 files changed, 17 insertions, 11 deletions
diff --git a/po/pot/using-d-i.pot b/po/pot/using-d-i.pot
index 718c06922..626149688 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: 2012-10-24 19:53+0000\n"
+"POT-Creation-Date: 2012-12-29 10:09+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"
@@ -2757,62 +2757,68 @@ msgstr ""
msgid "Note that it is possible to skip loading the firmware if you know the device will also function without it, or if the device is not needed during the installation."
msgstr ""
+#. Tag: para
+#: using-d-i.xml:3504
+#, no-c-format
+msgid "&d-i; only prompts for firmware needed by kernel modules loaded during the installation. Not all drivers are included in &d-i;, in particular radeon is not, so this implies that the capabilities of some devices may be no different at the end of the installation from what they were at the beginning. Consequently, some of your hardware may not be being used to its full potential. If you suspect this is the case, or are just curious, it is not a bad idea to check the output of the <command>dmesg</command> command on the newly booted system and search for <quote>firmware</quote>."
+msgstr ""
+
#. Tag: title
-#: using-d-i.xml:3506
+#: using-d-i.xml:3518
#, no-c-format
msgid "Preparing a medium"
msgstr ""
#. Tag: para
-#: using-d-i.xml:3507
+#: using-d-i.xml:3519
#, no-c-format
msgid "Official CD images do not include non-free firmware. The most common method to load such firmware is from some removable medium such as a USB stick. Alternatively, unofficial CD builds containing non-free firmware can be found at <ulink url=\"&url-firmware-cds;\"></ulink>. To prepare a USB stick (or other medium like a hard drive partition, or floppy disk), the firmware files or packages must be placed in either the root directory or a directory named <filename>/firmware</filename> of the file system on the medium. The recommended file system to use is FAT as that is most certain to be supported during the early stages of the installation."
msgstr ""
#. Tag: para
-#: using-d-i.xml:3520
+#: using-d-i.xml:3532
#, no-c-format
msgid "Tarballs and zip files containing current packages for the most common firmware are available from: <itemizedlist> <listitem><para> <ulink url=\"&url-firmware-tarballs;\"></ulink> </para></listitem> </itemizedlist> Just download the tarball or zip file for the correct release and unpack it to the file system on the medium."
msgstr ""
#. Tag: para
-#: using-d-i.xml:3534
+#: using-d-i.xml:3546
#, no-c-format
msgid "If the firmware you need is not included in the tarball, you can also download specific firmware packages from the (non-free section of the) archive. The following overview should list most available firmware packages but is not guaranteed to be complete and may also contain non-firmware packages:"
msgstr ""
#. Tag: para
-#: using-d-i.xml:3548
+#: using-d-i.xml:3560
#, no-c-format
msgid "It is also possible to copy individual firmware files to the medium. Loose firmware could be obtained for example from an already installed system or from a hardware vendor."
msgstr ""
#. Tag: title
-#: using-d-i.xml:3557
+#: using-d-i.xml:3569
#, no-c-format
msgid "Firmware and the Installed System"
msgstr ""
#. Tag: para
-#: using-d-i.xml:3558
+#: using-d-i.xml:3570
#, no-c-format
msgid "Any firmware loaded during the installation will be copied automatically to the installed system. In most cases this will ensure that the device that requires the firmware will also work correctly after the system is rebooted into the installed system. However, if the installed system runs a different kernel version from the installer there is a slight chance that the firmware cannot be loaded due to version skew."
msgstr ""
#. Tag: para
-#: using-d-i.xml:3567
+#: using-d-i.xml:3579
#, no-c-format
msgid "If the firmware was loaded from a firmware package, &d-i; will also install this package for the installed system and will automatically add the non-free section of the package archive in APT's <filename>sources.list</filename>. This has the advantage that the firmware should be updated automatically if a new version becomes available."
msgstr ""
#. Tag: para
-#: using-d-i.xml:3575
+#: using-d-i.xml:3587
#, no-c-format
msgid "If loading the firmware was skipped during the installation, the relevant device will probably not work with the installed system until the firmware (package) is installed manually."
msgstr ""
#. Tag: para
-#: using-d-i.xml:3582
+#: using-d-i.xml:3594
#, no-c-format
msgid "If the firmware was loaded from loose firmware files, the firmware copied to the installed system will <emphasis>not</emphasis> be automatically updated unless the corresponding firmware package (if available) is installed after the installation is completed."
msgstr ""