1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
|
<!-- retain these comments for translator revision tracking -->
<!-- $Id$ -->
<sect1 id="loading-firmware" arch="not-s390">
<title>Loading Missing Firmware</title>
<para>
As described in <xref linkend="hardware-firmware"/>, some devices require
firmware to be loaded. In most cases the device will not work at all
if the firmware is not available; sometimes basic functionality is not
impaired if it is missing and the firmware is only needed to enable
additional features.
</para><para>
Starting with &debian-gnu; 12.0, following the <ulink
url="https://www.debian.org/vote/2022/vote_003">2022 General
Resolution about non-free firmware</ulink>, official installation
images (like netinst) can include non-free firmware packages.
Even with those firmware packages available, some firmware files might
still be missing. Or one might be using netboot files, which don't
include firmware packages.
</para><para>
If a device driver requests firmware that is not available, &d-i; will
display a dialog offering to load the missing firmware. If this option
is selected, &d-i; will scan available devices for either loose firmware
files or packages containing firmware. If found, the firmware will be
copied to the correct location (<filename>/lib/firmware</filename>) and
the driver module will be reloaded.
</para>
<note><para>
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 USB stick.
<phrase arch="x86">On i386 and amd64 firmware can also be loaded from an
MMC or SD card.</phrase>
</para></note>
<para>
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>
<sect2><title>Preparing a medium</title>
<para>
The most common
method to load such firmware is from some removable medium such as a USB
stick.
To prepare a USB stick (or other medium like a hard drive partition),
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.
</para><para>
Tarballs and zip files containing current packages for the most common
firmware, and the associated metadata to ensure a proper detection by
the installer (<filename>dep11</filename> directory), are available from:
<itemizedlist>
<listitem><para>
<ulink url="&url-firmware-tarballs;"/>
</para></listitem>
</itemizedlist>
Just download the tarball or zip file for the correct release and unpack it to
the file system on the medium.
</para><para>
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.
</para>
</sect2>
<sect2><title>Firmware and the Installed System</title>
<para>
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.
</para><para>
If the firmware was loaded from a firmware package, &d-i; will also install
this package for the installed system and will automatically add the non-free-firmware
section of the package archive in APT's <filename>sources.list</filename>.
This has the advantage that the firmware should be updated automatically if
a new version becomes available.
</para><para>
If loading the firmware was skipped during the installation, the relevant
device will probably not work with the installed system until the firmware
(package) is installed manually.
</para>
<note><para>
If the firmware was loaded from loose firmware files, the firmware copied to
the installed system will <emphasis>not</emphasis> be automatically updated
unless the corresponding firmware package (if available) is installed after
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>
|
