From ca65cb8962e1de7ddec4e117c381c0a2182b99bc Mon Sep 17 00:00:00 2001
From: Cyril Brulebois <kibi@debian.org>
Date: Mon, 30 Jan 2023 05:31:33 +0100
Subject: Drop isenkram-cli section and reference.

It was a welcome band-aid for Debian 11 (even if it required some heavy
lifting to work correctly), but becomes unnecessary with Debian 12: we
do have modalias information (as we did for Debian 11) and official
installation images include non-free-firmware packages, so graphics
drivers shouldn't be an issue anymore.
---
 en/hardware/hardware-supported.xml |  5 ----
 en/using-d-i/loading-firmware.xml  | 58 --------------------------------------
 2 files changed, 63 deletions(-)

diff --git a/en/hardware/hardware-supported.xml b/en/hardware/hardware-supported.xml
index 5b16c20de..fa536dceb 100644
--- a/en/hardware/hardware-supported.xml
+++ b/en/hardware/hardware-supported.xml
@@ -349,11 +349,6 @@ 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
diff --git a/en/using-d-i/loading-firmware.xml b/en/using-d-i/loading-firmware.xml
index 485cba5c9..8a643ee3b 100644
--- a/en/using-d-i/loading-firmware.xml
+++ b/en/using-d-i/loading-firmware.xml
@@ -121,62 +121,4 @@ 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>
-
-<para>
-
-Once logged in into the installed system, it is possible to automate
-the detection of missing firmware, and to perform the required steps to
-enable them following this procedure:
-
-</para><orderedlist>
-  <listitem><para>Install the <classname>isenkram-cli</classname>
-  package.</para></listitem>
-
-  <listitem><para>Run the
-  <command>isenkram-autoinstall-firmware</command> command as the
-  <quote>root</quote> user.</para></listitem>
-</orderedlist><para>
-
-Usually, rebooting is the simplest way to make sure all kernel modules
-are properly initialized; that's particularly important when one has
-booted the system with the <code>nomodeset</code> option as an
-interim measure.
-
-</para><note><para>
-
-Installing firmware packages is very likely to require enabling the
-non-free section of the package archive. As of &debian-gnu; 11.0,
-running the <command>isenkram-autoinstall-firmware</command> command
-will do that automatically by creating a dedicated file
-(<filename>/etc/apt/sources.list.d/isenkram-autoinstall-firmware.list</filename>),
-pointing at a generic mirror.
-
-</para></note>
-
-  </sect2>
  </sect1>
-- 
cgit v1.2.3