|
401.
|
|
|
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. <phrase arch="x86">On i386 and amd64 firmware can also be loaded from an MMC or SD card.</phrase>
|
|
|
Tag: para
|
|
|
|
(no translation yet)
|
|
|
|
Located in
using-d-i.xml:3218
|
|
402.
|
|
|
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.
|
|
|
Tag: para
|
|
|
|
(no translation yet)
|
|
|
|
Located in
using-d-i.xml:3228
|
|
403.
|
|
|
Support for loading firmware is still relatively basic and is likely to be improved in future releases of the installer. Currently &d-i; will for example not display any warning if you choose to load missing firmware, but the requested firmware is not found. Please report any issues you encounter by filing an installation report (see <xref linkend="submit-bug"/>).
|
|
|
Tag: para
|
|
|
|
(no translation yet)
|
|
|
|
Located in
using-d-i.xml:3235
|
|
404.
|
|
|
Preparing a medium
|
|
|
Tag: title
|
|
|
|
(no translation yet)
|
|
|
|
Located in
using-d-i.xml:3246
|
|
405.
|
|
|
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 <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.
|
|
|
Tag: para
|
|
|
|
(no translation yet)
|
|
|
|
Located in
using-d-i.xml:3247
|
|
406.
|
|
|
Tarballs 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 for the correct release and unpack it to the file system on the medium.
|
|
|
Tag: para
|
|
|
|
(no translation yet)
|
|
|
|
Located in
using-d-i.xml:3257
|
|
407.
|
|
|
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:
|
|
|
Tag: para
|
|
|
|
(no translation yet)
|
|
|
|
Located in
using-d-i.xml:3271
|
|
408.
|
|
|
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.
|
|
|
Tag: para
|
|
|
|
(no translation yet)
|
|
|
|
Located in
using-d-i.xml:3285
|
|
409.
|
|
|
Firmware and the Installed System
|
|
|
Tag: title
|
|
|
|
(no translation yet)
|
|
|
|
Located in
using-d-i.xml:3294
|
|
410.
|
|
|
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.
|
|
|
Tag: para
|
|
|
|
(no translation yet)
|
|
|
|
Located in
using-d-i.xml:3295
|