14
14
When downloading files from a Debian mirror, be sure to download the
15
15
files in <emphasis>binary</emphasis> mode, not text or automatic
16
mode. It's important to replicate the directory structure you find on
17
the mirror to create a local `sub-mirror'.
19
<phrase arch="not-s390">
21
It isn't really necessary to do this
22
if you place all the installation files on floppies; but it still
23
makes it easier to find the files when you need them.
27
You should start your local directory structure at the level under
28
<filename>installer-&architecture;</filename>, for example:
30
<informalexample><screen arch="i386">
31
current/images/floppy/boot.img
32
</screen><screen arch="not-i386">
33
current/images/<replaceable>subarchitecture</replaceable>/netboot/initrd.gz
34
</screen></informalexample>
36
You don't need to download every file under that level, just those
37
that apply to you (you'll find out which ones apply as you read on).
38
Just name the directories the same as the mirror's, and keep the files
39
in their proper directories.
43
If your machine is set up to automatically decompress/decode files you
44
download, you must turn that feature off when downloading the
45
installation system files. They will be decompressed just-in-time by
46
the installer. Decompressing in your current system will waste space
47
and time, and if the original compressed archives are deleted by the
48
decompression program, they won't be there later when the installer
51
</para><para arch="powerpc;m68k">
53
This is particularly true on the Macintosh, where <filename>.bin</filename>
54
files are interpreted to be MacBinary, and the decoder's attempts to
55
convert them will fail noisily.
57
</para><para arch="powerpc">
59
Also, many of the binary files such as <filename>yaboot</filename>
60
will be automatically interpreted as text since they have no file
61
extensions unless you specifically select binary transfer mode. These
62
files will be <emphasis>unusable</emphasis> if they are transferred in
68
<title>Installation Options</title>
71
For m68k (except VME), the installation system files
72
(<filename>rescue.bin, linux.bin, root.bin, and
73
drivers.tgz</filename>) have been compiled into one tarball. You may
74
also need the base system installation file
75
<filename>basedebs.tar</filename>.
79
If you have a working Ethernet connection on the computer, and your
80
Ethernet card is of one of the types compiled into the installation
81
kernel, you may only need the install system tarball.
85
If you are installing on a system without a working network
86
connection, or if your network connection is via PPP (using a modem)
87
rather than Ethernet, you will also need to download
88
<filename>basedebs.tar</filename> before starting the installation.
93
<sect2 arch="not-m68k">
94
<title>Installation Options</title>
97
Files you may need fall into three categories:
103
Files needed to boot into the installation system (for example,
104
<phrase arch="not-s390">
105
<filename>boot.img</filename> and <filename>root.img</filename>, or
106
<filename>vmlinuz</filename> and <filename>initrd.gz</filename>)
110
<filename>kernel.debian</filename>,
111
<filename>parmfile.debian</filename>, and
112
<filename>initrd.debian</filename>)
118
Files the installation system will need access to
119
after it has been booted in order to install the operating system
120
kernel and peripheral drivers (for example,
121
<filename>net-drivers.img</filename> and
122
<filename>cd-drivers.img</filename>)
128
Base system installation files
134
If you have a working Ethernet connection on the computer, and your
135
Ethernet card is of one of the types compiled into the installation
136
kernel, you may only need the install system boot files. The installer
137
is capable of installing drivers and the rest of the system over the
138
network for many common Ethernet cards.
142
If you have an Ethernet connection for which the installer doesn't
143
have built-in support, you may need both the install system boot files
144
and the peripheral driver installation files.
148
If you are installing on a system without a working network
149
connection, or if your network connection is via PPP (using a modem)
150
rather than Ethernet, you will need to obtain all three types of files
151
before starting the installation. The base system installation files
152
are available on the first Debian CD (or on its smaller variant called
153
<firstterm>netinst</firstterm>, which is under 120MB). You can use
154
this ISO image even if you don't have a CD-ROM drive.
158
If you're not sure which files you need, just start with the install
159
system boot files. If your first attempt to configure the network
160
within the installer fails, you can just quit, get the extra files you
161
need, and re-start the installation.
166
<sect2 arch="i386" id="kernel-choice">
167
<title>Choosing the Right Installation Set</title>
170
Installation files include kernel images, which are available in
171
various <firstterm>flavors</firstterm>. Each flavor supports a
172
different set of hardware. The flavors available for &arch-title; are:
179
The standard kernel package available in Debian. This includes almost
180
all drivers supported by Linux built as modules, which includes
181
drivers for network devices, SCSI devices, sound cards, Video4Linux
182
devices, etc. The <quote>vanilla</quote> flavor includes one boot
183
floppy, one root and two driver floppies.
192
Almost like <quote>vanilla</quote>, but it contains support for
193
braille display. A complete list of supported models may be found in
194
brltty documentation. This flavor includes one boot floppy, one root
195
floppy and one driver floppy.
204
This is an experimental flavor which uses kernel from the 2.6
205
series. It might not be as stable as the other flavors, but it
206
supports some newer hardware components. If you can't complete the
207
installation due to a missing driver for your hardware, try this
216
Although we have described above how many 1.44MB diskettes the
217
different sets occupy, you may still choose different methods of
222
The kernel config files for these flavors can be found in their
223
respective directories in a file named <filename>kernel-config</filename>.
228
<sect2 arch="not-i386">
229
<title>Choosing the Right Installation Set</title>
232
Installation files include kernel images, which are available for
233
various <firstterm>subarchitectures</firstterm>. Each subarchitecture
234
supports a different set of hardware. The kernel config files for
235
these subarchitectures can be found in their respective directories in
236
a file named <filename>kernel-config</filename>. The subarchitectures
237
available for &arch-title; are:
241
<variablelist arch="sparc">
243
<term>`sun4cmd'</term>
246
This is the kernel required for older SPARC hardware. For specific
247
models supported, see <xref linkend="sparc-cpus"/>.
264
The kernel config files for these subarchitectures can be found in their
265
respective directories in a file named <filename>kernel-config</filename>.
269
<variablelist arch="mipsel">
271
<term>`r4k-kn04'</term>
274
This is the kernel required for the R4000 based DECstation 5000/150 and
275
similar machines, such as the R4400 based DECstation 5000/260.
281
<term>`r3k-kn02'</term>
284
This is the kernel required for R3000 based DECstations with KN02 (or
285
compatible) main board, such as the DECstation 5000/1xx series with
286
xx=20,25,33 and the DECstation 5000/240.
294
The kernel config files for these subarchitectures can be found in their
295
respective directories in a file named <filename>kernel-config</filename>.
299
<variablelist arch="mips">
301
<term>`r4k-ip22'</term>
304
This is the kernel required for SGI Indy, Indigo 2 and Challenge S machines.
305
The kernel includes almost all drivers supported by Linux built as modules,
306
which includes drivers for network devices, SCSI devices, etc. There are no
307
other flavors for &arch-title; available currently.
315
The kernel config files for these subarchitectures can be found in their
316
respective directories in a file named <filename>kernel-config</filename>.
320
<variablelist arch="hppa">
325
This is the kernel to use on all 32 bit processors. On processors
326
that support 32 and 64 bit modes, this is probably also the best
327
kernel to use for installation.
337
This is the kernel to use on all 64 bit processors. On processors
338
that support 32 and 64 bit modes, the 32 bit kernel is probably the
339
best kernel to use for installation.
347
These kernels include almost all drivers supported by Linux built as
348
modules, which includes drivers for network devices, SCSI devices,
349
etc. Support for standard hardware is compiled in to the kernel,
350
so it is unlikely that you will need to configure any modules during
353
</para><para arch="hppa">
355
The kernel config files for these subarchitectures can be found in their
356
respective directories in a file named <filename>kernel-config</filename>.
361
<variablelist arch="s390">
366
Includes a kernel image which supports booting (IPL) from a tape
367
(emulated or real) and a DASD (Direct Access Storage Device). You need
368
these files if you want to install &debian; native or in an
369
LPAR (logical partition) but they can also be used to install under VM
370
with a tape (real or emulated).
372
</para><para arch="s390"><phrase condition="FIXME">
374
<emphasis>FIXME: what about the nolabel kernel?</emphasis>
384
Includes a kernel image which supports booting (IPL) from the VM
385
reader and a DASD, These files can only be used if you want to install
386
&debian; in a VM guest.
394
Both of these kernels include almost all drivers supported by Linux
395
built as modules. Support for standard hardware is compiled into the
396
kernel, so it is unlikely that you will need to configure any modules
399
</para><para arch="s390">
401
Both kernels were also built to directly support IBM's OCO modules. You
402
can simply download then from IBM's
403
<ulink url="http://oss.software.ibm.com/developerworks/opensource/linux390/index.shtml">
404
developerWorks web site</ulink> and load them into the running kernel.
405
Please make sure that you pick the modules for the standard kernel,
406
i.e. not the ones for a kernel with the ``on-demand'' timer patch.
408
</para><para arch="s390">
410
The kernel config files for these subarchitectures can be found in their
411
respective directories in a file named <filename>kernel-config</filename>.
416
<variablelist arch="powerpc">
418
<term>`powermac'</term>
421
This is the kernel to use for most Power Macintosh computers; it uses
422
version 2.2 of the Linux kernel.
428
<term>`new-powermac'</term>
431
Use this kernel for very new Power Macintosh computers; it is based on
432
version 2.4 of the Linux kernel. If you want to install the
433
new-powermac version on an OldWorld machine, you are limited to using
434
BootX to boot the installer; the kernel doesn't fit on a floppy and
435
Debian CDs are not bootable on OldWorlds. You could also switch to the
436
&kernelversion; kernel after you finish the powermac flavor install.
445
Use this kernel for Amiga Power-UP Systems (APUS); it is based on
446
version 2.2 of the Linux kernel.
454
Use this kernel for embedded CHRP computers; it is based on
455
version 2.2 of the Linux kernel.
463
Use this kernel for Motorola and IBM RS/6000 PReP computers; it is based on
464
version 2.2 of the Linux kernel.
470
<para arch="powerpc">
472
The kernel config files for these subarchitectures can be found in their
473
respective directories in a file named <filename>config.gz</filename>.
475
</para><para arch="arm">
477
There is only one installation kernel available for each supported ARM
480
</para><para arch="m68k;ia64">
482
There is only one install kernel available for &arch-title;, which
483
should include sufficient functionality to install on all systems. It
484
is unlikely to be optimised for your particular hardware, and you
485
might consider replacing it once installation is complete. In
486
particular, this kernel does not support SMP.
488
</para><para arch="m68k;ia64">
490
The kernel config files for these kernels can be found in their
491
respective directories in a file named <filename>config.gz</filename>.
497
20
<sect2 id="where-files">
498
<title>Where to Find Installation Files</title>
502
For Amiga, Atari, and 68k Mac, the install system files have been
503
compiled into one tarball. You will download the appropriate tarball
505
<xref linkend="amiga-install-files"/>,
506
<xref linkend="atari-install-files"/>, or
507
<xref linkend="mac-install-files"/>. Only
508
VME machines will need the separate boot, root, kernel and drivers
515
<term>boot image</term>
523
<varlistentry condition="rescue-needs-root-disk">
524
<term>root image(s) or tarball</term>
533
<term>kernel binary</term>
542
<term>driver images or tarball</term>
546
&list-driver-disk-tarball;
552
<para arch="not-powerpc">
554
The boot image contains a compressed Linux boot
555
kernel. It is used for
556
<phrase arch="not-s390">both floppy disk booting (when transferred to a
557
floppy) and as the source for </phrase>
558
the Linux kernel when the kernel is
559
being installed on your machine. The kernel binary
560
<filename>vmlinuz</filename>
561
is an uncompressed binary kernel. It is used when booting the
563
<phrase arch="not-s390">
565
the hard disk, usb stick, network or CD-ROM, and is not needed for
566
floppy installer booting.
568
</phrase><phrase arch="s390">
570
tape, emulated tape or the VM reader.
576
Besides the file <filename>linux.bin</filename>, which is a kernel image in
577
ELF format, the file <filename>linux.ecoff</filename> contains the same
578
kernel in ECOFF format, which is required for net booting DECstations.
580
</para><para arch="powerpc">
582
Both the <filename>boot-floppy-hfs</filename> floppy image and the
583
<filename>boot.img</filename> image contain a compressed Linux boot
584
kernel. The <filename>boot-floppy-hfs</filename> floppy is used to
585
boot the installation system, while <filename>boot.img</filename>
586
serves as the source for the Linux kernel when the kernel is being
587
installed on your machine. A <filename>boot.img</filename> floppy
588
cannot be booted on &arch-title;. A third uncompressed kernel image,
589
simply named <filename>linux.bin</filename>, is used when booting the
590
installer from the hard disk or CD-ROM. It is not needed for floppy
593
</para><para arch="powerpc">
595
There are two versions of the hfs boot floppy image. The standard one,
596
<filename>boot-floppy-hfs.img</filename>, may work best on older
597
machines such as the 7200 and 8500 with no added video cards. If the
598
standard image gives a black screen when booting, try the image with
599
video=ofonly added to the boot arguments:
600
<filename>boot-video-ofonly.img</filename>.
602
</para><para condition="supports-floppy-boot">
604
Refer to <xref linkend="create-floppy"/>
605
for important information on properly
606
creating floppy disks from floppy images.
608
</para><para condition="rescue-needs-root-disk">
610
The root floppy image <filename>root.img</filename> contains a
611
compressed RAMdisk filesystem which gets loaded into memory after you
616
The peripheral drivers may be downloaded as a series of floppy images
617
or as a tarball (<filename>drivers.tgz</filename>). The installer
618
system will need access to the drivers file during installation. If
619
you have a hard drive partition or connected computer which will be
620
accessible to the installer (see below), the tarball will be more
621
convenient to handle. The floppy image files are needed only if you
622
must install the drivers from floppies.
626
When downloading files, you should also pay attention to the type of
627
file system you are downloading them <emphasis>to</emphasis>, unless
628
you will use floppies for the kernel and drivers. The installer can
629
read files from many kinds of file systems, including FAT, HFS,
630
ext2fs, and Minix. When downloading files to a *nix file system,
631
choose the largest possible files from the archive.
635
During the installation, you will erase the partition(s) on which you
636
are installing Debian before beginning the installation. All
637
downloaded files must be placed on partitions
638
<emphasis>other</emphasis> than those on which you are planning to
21
<title>Where to Find Installation Images</title>
24
The installation images are located on each Debian mirror in the directory
25
<ulink url="&url-debian-installer;/images">debian/dists/&releasename;/main/installer-&architecture;/current/images/</ulink>
26
-- the <ulink url="&url-debian-installer;/images/MANIFEST">MANIFEST</ulink>
27
lists each image and its purpose.
643
30
&download-alpha.xml;