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
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
|
<!-- retain these comments for translator revision tracking -->
<!-- $Id$ -->
<sect2 arch="any-x86" condition="bootable-usb" id="usb-boot-x86">
<title>Booting from USB Memory Stick</title>
&boot-installer-intro-usb.xml;
</sect2>
<sect2 arch="any-x86"><title>Booting from optical disc (CD/DVD)</title>
&boot-installer-intro-cd.xml;
</sect2>
<sect2 arch="x86" id="boot-initrd">
<title>Booting from Linux using
<command>GRUB</command></title>
<para>
To boot the installer from hard disk, you must first download
and place the needed files as described in <xref linkend="boot-drive-files"/>.
</para>
<para>
For <command>GRUB2</command>, you will need to configure two
essential things in <filename>/boot/grub/grub.cfg</filename>:
<itemizedlist>
<listitem><para>
to load the <filename>initrd.gz</filename> installer at boot time;
</para></listitem>
<listitem><para>
have the <filename>vmlinuz</filename> kernel use a RAM disk as
its root partition.
</para></listitem>
</itemizedlist>
</para><para>
An entry for the installer would be for example:
<informalexample><screen>
menuentry 'New Install' {
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
linux /boot/newinstall/vmlinuz
initrd /boot/newinstall/initrd.gz
}
</screen></informalexample>
</para>
</sect2>
<sect2 arch="x86" id="boot-tftp-x86"><title>Booting with TFTP</title>
&boot-installer-intro-net.xml;
<para>
There are various ways to do a TFTP boot on i386.
</para>
<sect3><title>NIC or Motherboard that support PXE</title>
<para>
It could be that your Network Interface Card or Motherboard provides
PXE boot functionality.
This is a <trademark class="trade">Intel</trademark> re-implementation
of TFTP boot. If so, you may be able to configure your BIOS/UEFI to boot from the
network.
</para>
</sect3>
<sect3><title>NIC with Network BootROM</title>
<para>
It could be that your Network Interface Card provides
TFTP boot functionality.
</para><para condition="FIXME">
Let us (<email>&email-debian-boot-list;</email>) know how did you manage it.
Please refer to this document.
</para>
</sect3>
<sect3><title>Etherboot</title>
<para>
The <ulink url="http://www.etherboot.org">etherboot project</ulink>
provides bootdiskettes and even bootroms that do a TFTPboot.
</para>
</sect3>
</sect2>
<sect2 arch="x86" id="boot-screen">
<title>The Boot Screen</title>
<para>
When the installer boots, you should be presented with a friendly graphical
screen showing the &debian; logo and a menu:
<informalexample><screen>
&debian-gnu; installer boot menu
Graphical install
Install
Advanced options >
Accessible dark contrast installer menu >
Help
Install with speech synthesis
</screen></informalexample>
</para>
<note><para>
This graphical screen will look very slightly different depending on
how your computer has booted (BIOS or UEFI), but the same options will
be shown.
</para></note>
<para>
Depending on the installation method you are using, the <quote>Graphical
install</quote> option may not be available. Bi-arch images additionally have a
64 bit variant for each install option, right below it, thus almost doubling the
number of options.
</para><para>
For a normal installation, select either the <quote>Graphical install</quote> or
the <quote>Install</quote> entry — using either the
arrow keys on your keyboard or by typing the first (highlighted) letter —
and press &enterkey; to boot the installer. The
<quote>Graphical install</quote> entry is already selected by default.
</para><para>
The <quote>Advanced options</quote> entry gives access to a second menu
that allows to boot the installer in expert mode, in rescue mode and for
automated installs.
</para><para>
If you wish or need to add any boot parameters for either the
installer or the kernel, press &tabkey; (BIOS boot), or &ekey; then
&downkey; three times then &endkey; (UEFI boot).
This will bring the boot command for the selected menu entry
and allow you to edit it to suit your needs. Note that the keyboard layout at
this point is still QWERTY. The help screens (see
below) list some common possible options. Press &enterkey; (BIOS boot)
or &f10key; (UEFI boot) to boot the installer with your options;
pressing &escapekey; will return you to the boot menu and undo any
changes you made.
</para><para>
Choosing the <quote>Help</quote> entry will result in the first help screen
being displayed which gives an overview of all available help screens.
To return to the boot menu after the help screens have been
displayed, type <quote>menu</quote> at the boot prompt and press &enterkey;. All
help screens have a boot prompt at which the boot command can be typed:
<informalexample><screen>
Press F1 for the help index, or ENTER to boot:
</screen></informalexample>
At this boot prompt you can either just press &enterkey; to boot the
installer with default options or enter a specific boot command and,
optionally, boot parameters. A number of boot parameters which might be
useful can be found on the various help screens. If you do add any
parameters to the boot command line, be sure to first type the boot method
(the default is <userinput>install</userinput>) and a space before the
first parameter (e.g., <userinput>install fb=false</userinput>).
<note><para>
The keyboard is assumed to have a default American English layout at this
point. This means that if your keyboard has a different (language-specific)
layout, the characters that appear on the screen may be different from what
you'd expect when you type parameters. Wikipedia has a
<ulink url="&url-us-keymap;">schema of the US keyboard layout</ulink> which
can be used as a reference to find the correct keys to use.
</para></note>
<note><para>
If you are using a system that has the BIOS configured to use serial console,
you may not be able to see the initial graphical splash screen upon booting
the installer; you may even not see the boot menu. The same can happen if
you are installing the system via a remote management device that provides a
text interface to the VGA console. Examples of these devices include the text
console of Compaq's <quote>integrated Lights Out</quote> (iLO) and HP's
<quote>Integrated Remote Assistant</quote> (IRA).
</para><para>
To bypass the graphical boot screen you can either blindly press &escapekey;
to get a text boot prompt, or (equally blindly) press <quote>H</quote>
followed by &enterkey; to select the <quote>Help</quote> option described
above. After that your keystrokes should be echoed at the prompt.
To prevent the installer from using the framebuffer for the rest of the
installation, you will also want to add <userinput>vga=normal fb=false</userinput>
to the boot prompt, as described in the help text.
</para></note>
</para>
</sect2>
|
