summaryrefslogtreecommitdiff
path: root/en
diff options
context:
space:
mode:
authorCyril Brulebois <kibi@debian.org>2021-07-29 07:22:35 +0200
committerCyril Brulebois <kibi@debian.org>2021-07-30 12:52:15 +0200
commit272245c0b08c2c2f357f4fea0cec0ab7f09cc6cb (patch)
tree9c5bc2ac1caa2382c39ea665bc3df73ce65af642 /en
parente1516e08049431b2fc5a1c27eab13cb0198a7b15 (diff)
downloadinstallation-guide-272245c0b08c2c2f357f4fea0cec0ab7f09cc6cb.zip
Mention the black screen possibility (See: #989863, #991627).
And use an xref pointing at the section added in the previous commit. v2: Apply suggestion by Holger Wansing, thanks!
Diffstat (limited to 'en')
-rw-r--r--en/hardware/hardware-supported.xml8
1 files changed, 8 insertions, 0 deletions
diff --git a/en/hardware/hardware-supported.xml b/en/hardware/hardware-supported.xml
index bd2193046..04411b800 100644
--- a/en/hardware/hardware-supported.xml
+++ b/en/hardware/hardware-supported.xml
@@ -401,10 +401,18 @@ so-called <firstterm>firmware</firstterm> or <firstterm>microcode</firstterm>
to be loaded into the device before it can become operational. This is most
common for network interface cards (especially wireless NICs), but for example
some USB devices and even some hard disk controllers also require firmware.
+
+</para><para>
+
With many graphics cards, basic functionality is available without
additional firmware, but the use of advanced features requires an
appropriate firmware file to be installed in the system.
+In some cases, a successful installation can still end up in a black
+screen or garbled display when rebooting into the installed system. If
+that happens, some workarounds can be tried to log in anyway (see
+<xref linkend="completing-installed-system"/>).
+
</para><para>
On many older devices which require firmware to work, the firmware file was