blob: 10f07473895f6ba3115e4537af61c3b7b4619307 (
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
|
<!-- retain these comments for translator revision tracking -->
<!-- $Id$ -->
<sect1 id="memory-disk-requirements">
<title>Memory and Disk Space Requirements</title>
<para>
You must have at least &minimum-memory; of memory and &minimum-fs-size;
of hard disk space to perform a normal installation. Note that these are
fairly minimal numbers. For more realistic figures, see
<xref linkend="minimum-hardware-reqts"/>.
</para><para>
The installer normally automatically enables memory-saving tricks to be able to
run on such low-memory system, but on architectures that are less tested
it may miss doing so. It can however be enabled manually by appending the
<userinput>lowmem=1</userinput> or even <userinput>lowmem=2</userinput> boot
parameter (see also <xref linkend="lowmem"/> and
<xref linkend="installer-args"/>).
</para><warning condition="lowmem-unchecked"><para>
On &architecture; the lowmem levels have not been tested, so automatic detection
is probably outdated and you thus probably <emphasis>need</emphasis> to pass the
boot parameter if your system has little memory.
</para></warning><para>
Installation on systems with less memory<footnote condition="gtk">
<para>
Installation images that support the graphical installer require more
memory than images that support only the text-based installer and should
not be used on systems with less than &minimum-memory; of memory. If
there is a choice between booting the text-based and the graphical installer,
the former should be selected on such systems.
</para>
</footnote> or disk space available may be possible but is only advised for
experienced users.
</para>
</sect1>
|
