From 5330abfe2785291648dca87312e1cd860300c09a Mon Sep 17 00:00:00 2001 From: Frans Pop Date: Fri, 3 Oct 2008 19:11:55 +0000 Subject: Update of untranslated documents --- en/using-d-i/components.xml | 8 +++ en/using-d-i/loading-firmware.xml | 131 ++++++++++++++++++++++++++++++++++++++ en/using-d-i/using-d-i.xml | 1 + 3 files changed, 140 insertions(+) create mode 100644 en/using-d-i/loading-firmware.xml (limited to 'en/using-d-i') diff --git a/en/using-d-i/components.xml b/en/using-d-i/components.xml index 58bd8331b..05e99b4ee 100644 --- a/en/using-d-i/components.xml +++ b/en/using-d-i/components.xml @@ -37,6 +37,14 @@ at the hardware needed to load installer components (e.g. your CD-ROM or network card). As not all drivers may be available during this first run, hardware detection needs to be repeated later in the process. + + +During hardware detection &d-i; checks if any of the drivers for the hardware +devices in your system requires firmware to be loaded. If any firmware is +requested but unavailable, a dialog will be displayed that allows to load the +missing firmware from a removable medium. +See for further details. + &module-lowmem.xml; diff --git a/en/using-d-i/loading-firmware.xml b/en/using-d-i/loading-firmware.xml new file mode 100644 index 000000000..fcced447a --- /dev/null +++ b/en/using-d-i/loading-firmware.xml @@ -0,0 +1,131 @@ + + + + + Loading Missing Firmware + + +As described in some devices require +firmware to be loaded. In most cases the device will not work at all +if the firmware is not available; sometimes basic functionality is not +impaired if it is missing and the firmware is only needed to enable +additional features. + + + +If a device driver requests firmware that is not available, &d-i; will +display a dialog offering to load the missing firmware. If that question +is confirmed, &d-i; will scan available devices for either loose firmware +files or packages containing firmware. If found, the firmware will be +copied to the correct location (/lib/firmware) and +the driver module will be reloaded. + + + + +Which devices are scanned and which file systems are supported depends on +the architecture, the installation method and the stage of the installation. +Especially during the early stages of the installation, loading the firmware +is most likely to succeed from a FAT-formatted floppy disk or USB stick. +On i386 and amd64 firmware can also be loaded from an +MMC or SD card. + + + + +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. + + + + +Support for loading firmware is still relatively basic and is likely to +be improved in future releases of the installer. Please report any issues +you encounter. + + + + Preparing a medium + + +Although in some cases the firmware can also be loaded from a partition on +a hard disk, the most common method to load firmware will be from some +removable medium such as a floppy disk or a USB stick. +The firmware files or packages must be placed in either the root directory +or a directory named /firmware 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. + + + +Tarballs containing current packages for the most common firmware are +available from: + + + + + + + +Just download the tarball for the correct release and unpack it to the file +system on the medium. + + + +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: + + + + + + + + + +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. + + + + + Firmware and the Installed System + + +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. + + + +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 sources.list. +This has the advantage that the firmware should be updated automatically if +new a version becomes available. + + + +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. + + + + +If the firmware was loaded from loose firmware files, the firmware copied to +the installed system will not be automatically updated +unless the corresponding firmware package (if available) is installed after +the installation is completed. + + + + diff --git a/en/using-d-i/using-d-i.xml b/en/using-d-i/using-d-i.xml index 83db3f03c..03ac89cfe 100644 --- a/en/using-d-i/using-d-i.xml +++ b/en/using-d-i/using-d-i.xml @@ -387,6 +387,7 @@ report installer software problems to Debian developers later. &using-d-i-components.xml; +&loading-firmware.xml; -- cgit v1.2.3