summaryrefslogtreecommitdiff
path: root/en/using-d-i
diff options
context:
space:
mode:
authorCyril Brulebois <kibi@debian.org>2012-12-26 15:39:58 +0000
committerCyril Brulebois <kibi@debian.org>2012-12-26 15:39:58 +0000
commit0deacaf97cea713858bb0f47f252b7af3d14cd5f (patch)
tree81a673b4a84cdb9ab497c9ef6b5d0e4e9fca843d /en/using-d-i
parent6e384752cb5248027df4c0a4775f52893f724134 (diff)
downloadinstallation-guide-0deacaf97cea713858bb0f47f252b7af3d14cd5f.zip
Improvement documentation about kernel modules needing firmwares,
including how to look for “firmware” in dmesg's output. Closes: #695403.
Diffstat (limited to 'en/using-d-i')
-rw-r--r--en/using-d-i/loading-firmware.xml12
1 files changed, 12 insertions, 0 deletions
diff --git a/en/using-d-i/loading-firmware.xml b/en/using-d-i/loading-firmware.xml
index 95a13496e..640611a79 100644
--- a/en/using-d-i/loading-firmware.xml
+++ b/en/using-d-i/loading-firmware.xml
@@ -37,6 +37,18 @@ 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.
+</para><para>
+
+&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 "firmware".
+
</para>
<sect2><title>Preparing a medium</title>