From 8b9c3cbba247868a1e2dfd77baab2ffe7dc79df4 Mon Sep 17 00:00:00 2001
From: Philip Hands <phil@hands.com>
Date: Tue, 31 Jan 2023 11:17:12 +0100
Subject: Restore nomodeset & CtrlAltF2 tips

This reverts some of commit ca65cb8962e1de7ddec4e117c381c0a2182b99bc.
---
 en/using-d-i/loading-firmware.xml | 26 ++++++++++++++++++++++++++
 1 file changed, 26 insertions(+)

diff --git a/en/using-d-i/loading-firmware.xml b/en/using-d-i/loading-firmware.xml
index 8a643ee3b..5b96cf802 100644
--- a/en/using-d-i/loading-firmware.xml
+++ b/en/using-d-i/loading-firmware.xml
@@ -121,4 +121,30 @@ the installation is completed.
 
 </para></note>
   </sect2>
+
+  <sect2 id="completing-installed-system"><title>Completing the Installed System</title>
+<para>
+
+Depending on how the installation was performed, it might be that the
+need for some firmware was not detected during installation, that the
+relevant firmware was not available, or that one chose not to install
+some firmware at that time.
+
+In some cases, a successful installation can still end up in a black
+screen or a garbled display when rebooting into the installed
+system. When that happens, the following workarounds can be tried:
+
+</para>
+
+<itemizedlist>
+  <listitem><para>Pass the <code>nomodeset</code> option on the kernel
+  command line. This might help boot into a <quote>fallback
+  graphics</quote> mode.</para></listitem>
+
+  <listitem><para>Use the
+  <keycombo><keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>F2</keycap></keycombo>
+  key combination to switch to VT2, which might offer a functional
+  login prompt.</para></listitem>
+</itemizedlist>
+  </sect2>
  </sect1>
-- 
cgit v1.2.3