summaryrefslogtreecommitdiff
path: root/eu/preparing/bios-setup/i386.xml
blob: b7749022c3c99c7de2142e9d5e6e77bb1e062a81 (plain)
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
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
<!-- retain these comments for translator revision tracking -->
<!-- original version: 11648 untranslated -->


  <sect2 arch="x86"><title>Invoking the BIOS Set-Up Menu</title>

<para>

BIOS provides the basic functions needed to boot your machine to allow
your operating system to access your hardware.  Your system probably
provides a BIOS setup menu, which is used to configure the BIOS.
Before installing, you <emphasis>must</emphasis> ensure that your BIOS
is set up correctly; not doing so can lead to intermittent crashes or
an inability to install Debian.

</para><para>

The rest of this section is lifted from the 
<ulink url="&url-pc-hw-faq;"></ulink>, answering the question, "How do I
enter the CMOS configuration menu?".  How you access the BIOS (or
``CMOS'') configuration menu depends on who wrote your BIOS software:

</para>

<!-- From: burnesa@cat.com (Shaun Burnet) -->
<variablelist>

<varlistentry>
 <term>AMI BIOS</term>
 <listitem><para>

<keycap>Delete</keycap> key during the POST (power on self test)

</para></listitem>
</varlistentry>

<varlistentry>
 <term>Award BIOS</term>
 <listitem><para>

<keycombo>
  <keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Esc</keycap>
</keycombo>, or <keycap>Delete</keycap> key during the POST

</para></listitem>
</varlistentry>

<varlistentry><term>DTK BIOS</term>
 <listitem><para>

<keycap>Esc</keycap> key during the POST

</para></listitem>
</varlistentry>

<varlistentry><term>IBM PS/2 BIOS</term>
 <listitem><para>

<keycombo>
  <keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Insert</keycap>
</keycombo>
after
<keycombo>
  <keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Delete</keycap>
</keycombo>

</para></listitem>
</varlistentry>

<varlistentry>
 <term>Phoenix BIOS</term>
 <listitem><para>

<keycombo>
  <keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Esc</keycap>
</keycombo>
or
<keycombo>
  <keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>S</keycap>
</keycombo>
or
<keycap>F1</keycap>

</para></listitem>
</varlistentry>
</variablelist>

<para>

Information on invoking other BIOS routines can be found in 
<ulink url="&url-invoking-bios-info;"></ulink>.

</para><para>

Some &arch-title; machines don't have a CMOS configuration menu in the
BIOS.  They require a software CMOS setup program.  If you don't have
the Installation and/or Diagnostics diskette for your machine, you can
try using a shareware/freeware program.  Try looking in 
<ulink url="&url-simtel;"></ulink>.

</para>
  </sect2>

  <sect2 arch="x86" id="boot-dev-select"><title>Boot Device Selection</title>

<para>

Many BIOS setup menus allow you to select the devices that will be
used to bootstrap the system. Set this to look for a bootable
operating system on <filename>A:</filename> (the first floppy disk),
then optionally the first CD-ROM device (possibly appearing as
<filename>D:</filename> or <filename>E:</filename>), and then from
<filename>C:</filename> (the first hard disk).  This setting enables
you to boot from either a floppy disk or a CD-ROM, which are the two
most common boot devices used to install Debian.

</para><para>

If you have a newer SCSI controller and you have a CD-ROM device
attached to it, you are usually able to boot from the CD-ROM.  All you
have to do is enable booting from a CD-ROM in the SCSI-BIOS of your
controller. 

</para><para>

Other popular option is to boot from a USB storage (also called USB
memory stick or USB key).  Some BIOSes can boot USB storage directly,
and some cannot. You may need to configure your BIOS to boot from
a <quote>Removable drive</quote> or even a <quote>USB-ZIP</quote> to
get it to boot from the USB device.

</para><para>

Here are some details about how to set the boot order. Remember to
reset the boot order after Linux is installed, so that you restart
your machine from the hard drive.

</para>

   <sect3 id="ctbooi">
   <title>Changing the Boot Order on IDE Computers</title>

<orderedlist>
<listitem><para>

As your computer starts, press the keys to enter the BIOS 
utility. Often, it is the <keycap>Delete</keycap> key. However,
consult the hardware documentation for the exact keystrokes.

</para></listitem>
<listitem><para>

Find the boot sequence in the setup utility. Its location depends on
your BIOS, but you are looking for a field that lists drives.

</para><para>

   
Common entries on IDE machines are C, A, cdrom or A, C, cdrom.

</para><para>

   
C is the hard drive, and A is the floppy drive.

</para></listitem>   
<listitem><para>

Change the boot sequence setting so that the CD-ROM or the
floppy is first. Usually, the <keycap>Page Up</keycap> or
<keycap>Page Down</keycap> keys cycle 
through the possible choices.

</para></listitem>
<listitem><para>

Save your changes. Instructions on the screen tell you how to
save the changes on your computer.

</para></listitem>
</orderedlist>
   </sect3>

   <sect3 id="ctboos">
   <title>Changing the Boot Order on SCSI Computers</title>
<para>

<orderedlist>
<listitem><para>

As your computer starts, press the keys to enter the SCSI setup
utility.

</para><para>

You can start the SCSI setup utility after the memory check and
the message about how to start the BIOS utility displays when you
start your computer.

</para><para>

The keystrokes you need depend on the utility. Often, it is
<keycombo><keycap>Ctrl</keycap><keycap>F2</keycap></keycombo>.
However, consult your hardware documentation for the
exact keystrokes.

</para></listitem>
<listitem><para>

Find the utility for changing the boot order.

</para></listitem>
<listitem><para>

Set the utility so that the SCSI ID of the CD drive is first on
the list.

</para></listitem>
<listitem><para>

Save your changes. Instructions on the screen tell you how to
save the changes on your computer. Often, you must press
<keycap>F10</keycap>.

</para></listitem>
</orderedlist>

</para>
   </sect3>
  </sect2>

  <sect2 arch="x86">
  <title>Miscellaneous BIOS Settings</title>

   <sect3 id="cd-settings"><title>CD-ROM Settings</title>
<para>

Some BIOS systems (such as Award BIOS) allow you to automatically set
the CD speed.  You should avoid that, and instead set it to, say, the
lowest speed.  If you get <userinput>seek failed</userinput> error
messages, this may be your problem.

</para>
   </sect3>

   <sect3><title>Extended vs. Expanded Memory</title>
<para>

If your system provides both ex<emphasis>ten</emphasis>ded and
ex<emphasis>pan</emphasis>ded memory, set it so that there is as much
extended and as little expanded memory as possible. Linux requires
extended memory and cannot use expanded memory.

</para>
   </sect3>

   <sect3><title>Virus Protection</title>
<para>

Disable any virus-warning features your BIOS may provide. If you have
a virus-protection board or other special hardware, make sure it is
disabled or physically removed while running GNU/Linux. These aren't
compatible with GNU/Linux; moreover, due to the file system
permissions and protected memory of the Linux kernel, viruses are
almost unheard of.

<footnote>
<para>

After installation you can enable Boot Sector protection if you
want. This offers no additional security in Linux but if you also run
Windows it may prevent a catastrophe. There is no need to tamper with
the Master Boot Record (MBR) after the boot manager has been set up.

</para>
</footnote>

</para>
   </sect3>

   <sect3><title>Shadow RAM</title>
<para>

Your motherboard may provide <emphasis>shadow RAM</emphasis> or BIOS
caching. You may see settings for ``Video BIOS Shadow'', ``C800-CBFF
Shadow'', etc. <emphasis>Disable</emphasis> all shadow RAM.  Shadow
RAM is used to accelerate access to the ROMs on your motherboard and
on some of the controller cards. Linux does not use these ROMs once it
has booted because it provides its own faster 32-bit software in place
of the 16-bit programs in the ROMs. Disabling the shadow RAM may make
some of it available for programs to use as normal memory.  Leaving
the shadow RAM enabled may interfere with Linux access to hardware
devices.

</para>
   </sect3>

   <sect3><title>Memory Hole</title>
<para>

If your BIOS offers something like ``15-16 MB Memory Hole'', please
disable that. Linux expects to find memory there if you have that much
RAM.

</para><para>

We have a report of an Intel Endeavor motherboard on which there is an
option called ``LFB'' or ``Linear Frame Buffer''. This had two
settings: ``Disabled'' and ``1 Megabyte''. Set it to ``1 Megabyte''.
When disabled, the installation floppy was not read correctly, and the
system eventually crashed. At this writing we don't understand what's
going on with this particular device &mdash; it just worked with that
setting and not without it.

</para>
   </sect3>

<!-- no other platforms other than x86 provide this sort of thing, AFAIK -->

   <sect3><title>Advanced Power Management</title>
<para>

If your motherboard provides Advanced Power Management (APM),
configure it so that power management is controlled by APM. Disable
the doze, standby, suspend, nap, and sleep modes, and disable the hard
disk's power-down timer.  Linux can take over control of these modes,
and can do a better job of power-management than the BIOS. The version
of the operating system kernel on the installation floppies does not,
however, use APM, because we've had reports of one laptop system
crashing when the Linux APM driver is configured. Once you've
installed Linux, you can build a custom-configured version of the
Linux kernel; see <xref linkend="kernel-baking"/> for
instructions.

</para>
   </sect3>
  </sect2>