1
<!-- retain these comments for translator revision tracking -->
2
<!-- original version: 20629 untranslated -->
4
<sect2 arch="m68k"><title>Choosing an Installation Method</title>
8
Some &arch-title; subarchs have the option of booting using either a
9
2.4.x or 2.2.x linux kernel. When such a choice exists, try the 2.4.x
10
linux kernel. The installer should also require less memory when using
11
a 2.4.x linux kernel as 2.2.x support requires a fixed-sized ramdisk
16
If you are using a 2.2.x linux kernel, then you must make sure you
17
are using a ramdisk built to accomodate it, see the <ulink url="&disturl;/main/installer-&architecture;/current/images/MANIFEST">MANIFEST</ulink>. You will
18
also need to use the &ramdisksize; kernel parameter.
22
Make sure <userinput>root=/dev/ram</userinput> is one of your kernel
27
If you're having trouble, check
28
<ulink url="&url-m68k-cts-faq;">cts's &arch-title; debian-installer FAQ</ulink>.
33
<listitem><xref linkend="m68k-boot-amiga"/></listitem>
34
<listitem><xref linkend="m68k-boot-atari"/></listitem>
35
<listitem><xref linkend="m68k-boot-bvme6000"/></listitem>
36
<listitem><xref linkend="m68k-boot-mac"/></listitem>
37
<listitem><xref linkend="m68k-boot-mvme"/></listitem>
38
<listitem><xref linkend="m68k-boot-q40"/></listitem>
42
<sect3 arch="m68k" id="m68k-boot-amiga"><title>Amiga</title>
45
The only method of installation available to amiga is the hard drive
46
(see <xref linkend="m68k-boot-hd"/>).
47
<emphasis>In other words the cdrom is not bootable.</emphasis>
51
Amiga does not currently work with bogl, so if
52
you are seeing bogl errors, you need to include the kernel parameter
53
<userinput>debian-installer/framebuffer=false</userinput>.
58
<sect3 arch="m68k" id="m68k-boot-atari"><title>Atari</title>
61
The installer for atari may be started from either the hard
62
drive (see <xref linkend="m68k-boot-hd"/>) or from floppies
63
(see <xref linkend="boot-from-floppies"/>).
64
<emphasis>In other words the cdrom is not bootable.</emphasis>
68
Atari does not currently work with bogl, so if
69
you are seeing bogl errors, you need to include the kernel parameter
70
<userinput>debian-installer/framebuffer=false</userinput>.
75
<sect3 arch="m68k" id="m68k-boot-bvme6000"><title>BVME6000</title>
78
The installer for BVME6000 may be started from a cdrom
79
(see <xref linkend="m68k-boot-cdrom"/>), floppies
80
(see <xref linkend="boot-from-floppies"/>), or the net
81
(see <xref linkend="boot-tftp"/>).
86
<sect3 arch="m68k" id="m68k-boot-mac"><title>Macintosh</title>
89
The only method of installation available to mac is from
90
the hard drive (see <xref linkend="m68k-boot-hd"/>).
91
<emphasis>In other words the cdrom is not bootable.</emphasis>
92
Macs do not have a working 2.4.x kernel.
97
<sect3 arch="m68k" id="m68k-boot-mvme"><title>MVME147 and MVME16x</title>
100
The installer for MVEM147 and MVEM16x may be started from
101
either floppies (see <xref linkend="boot-from-floppies"/>)
102
or the net (see <xref linkend="boot-tftp"/>).
103
<emphasis>In other words the cdrom is not bootable.</emphasis>
108
<sect3 arch="m68k" id="m68k-boot-q40"><title>Q40/Q60</title>
111
The only method of installation available to Q40/Q60 is
112
from the hard drive (see <xref linkend="m68k-boot-hd"/>).
113
<emphasis>In other words the cdrom is not bootable.</emphasis>
120
<sect2 arch="m68k" id="m68k-boot-hd"><title>Booting from a Hard Disk</title>
122
&boot-installer-intro-hd.xml;
126
At least six different ramdisks may be used to boot from the hard
127
drive, three different types each with and without support for a
128
2.2.x linux kernel (see <ulink url="&disturl;/main/installer-&architecture;/current/images/MANIFEST">MANIFEST</ulink> for details).
132
The three different types of ramdisks are <filename>cdrom</filename>,
133
<filename>hd-media</filename>, and <filename>nativehd</filename>. These
134
ramdisks differ only in their source for installation packages.
135
The <filename>cdrom</filename> ramdisk uses a cdrom to get
136
debian-installer packages. The <filename>hd-media</filename> ramdisk
137
uses an iso image file of a cdrom currently residing on a hard disk.
138
Finally, the <filename>nativehd</filename> ramdisk uses the net to
144
<listitem><xref linkend="m68k-boothd-amiga"/></listitem>
145
<listitem><xref linkend="m68k-boothd-atari"/></listitem>
146
<listitem><xref linkend="m68k-boothd-mac"/></listitem>
147
<listitem><xref linkend="m68k-boothd-q40"/></listitem>
151
<sect3 arch="m68k" id="m68k-boothd-amiga"><title>Booting from AmigaOS</title>
154
In the <command>Workbench</command>, start the Linux installation
155
process by double-clicking on the <guiicon>StartInstall</guiicon> icon
156
in the <filename>debian</filename> directory.
160
You may have to press the &enterkey; key twice after the Amiga
161
installer program has output some debugging information into a window.
162
After this, the screen will go grey, there will be a few seconds'
163
delay. Next, a black screen with white text should come up, displaying
164
all kinds of kernel debugging information. These messages may scroll
165
by too fast for you to read, but that's OK. After a couple of
166
seconds, the installation program should start automatically, so you
167
can continue down at <xref linkend="d-i-intro"/>.
173
<sect3 arch="m68k" id="m68k-boothd-atari"><title>Booting from Atari TOS</title>
176
At the GEM desktop, start the Linux installation process by
177
double-clicking on the <guiicon>bootstra.prg</guiicon> icon in the
178
<filename>debian</filename> directory and clicking
179
<guibutton>Ok</guibutton> at the program options dialog box.
183
You may have to press the &enterkey; key after the Atari
184
bootstrap program has output some debugging information into a
185
window. After this, the screen will go grey, there will be a few
186
seconds' delay. Next, a black screen with white text should come up,
187
displaying all kinds of kernel debugging information. These messages
188
may scroll by too fast for you to read, but that's OK. After a couple
189
of seconds, the installation program should start automatically, so
190
you can continue below at <xref linkend="d-i-intro"/>.
196
<sect3 arch="m68k" id="m68k-boothd-mac"><title>Booting from MacOS</title>
199
You must retain the original Mac system and
200
boot from it. It is <emphasis>essential</emphasis> that, when booting
201
MacOS in preparation for booting the Penguin linux loader, you
202
hold the <keycap>shift</keycap> key down to prevent extensions from
203
loading. If you don't use MacOS except for loading linux, you can
204
accomplish the same thing by removing all extensions and control
205
panels from the Mac's System Folder. Otherwise extensions may be left
206
running and cause random problems with the running linux kernel.
210
Macs require the <command>Penguin</command>
211
bootloader. If you do not have the tools to handle
212
a <command>Stuffit</command> archive, &penguin19.hfs; is an
213
hfs disk image with <command>Penguin</command> unpacked.
214
<xref linkend="create-floppy"/> describes how to copy this
219
At the MacOS desktop, start the Linux installation process by
220
double-clicking on the <guiicon>Penguin Prefs</guiicon> icon in
221
the <filename>Penguin</filename> directory. The
222
<command>Penguin</command> booter will start up. Go to the
223
<guimenuitem>Settings</guimenuitem> item in the
224
<guimenu>File</guimenu> menu, click the
225
<guilabel>Kernel</guilabel> tab. Select the kernel
226
(<filename>vmlinuz</filename>) and ramdisk
227
(<filename>initrd.gz</filename>) images in the
228
<filename>install</filename> directory by clicking on the corresponding
229
buttons in the upper right corner, and navigating the file select
230
dialogs to locate the files.
234
To set the boot parameters in Penguin, choose <guimenu>File</guimenu> ->
235
<guimenuitem>Settings...</guimenuitem>, then switch to the
236
<guilabel>Options</guilabel> tab. Boot parameters may be typed in to
237
the text entry area. If you will always want to use these settings,
238
select <guimenu>File</guimenu> -> <guimenuitem>Save Settings as
239
Default</guimenuitem>.
243
Close the <guilabel>Settings</guilabel>
244
dialog, save the settings and start the bootstrap using the
245
<guimenuitem>Boot Now</guimenuitem> item in the
246
<guimenu>File</guimenu> menu.
250
The <command>Penguin</command> booter will output some debugging
251
information into a window. After this, the screen will go grey, there
252
will be a few seconds' delay. Next, a black screen with white text
253
should come up, displaying all kinds of kernel debugging
254
information. These messages may scroll by too fast for you to read,
255
but that's OK. After a couple of seconds, the installation program
256
should start automatically, so you can continue below at
257
<xref linkend="d-i-intro"/>.
263
<sect3 arch="m68k" id="m68k-boothd-q40"><title>Booting from Q40/Q60</title>
271
The installation program should start automatically, so you can
272
continue below at <xref linkend="d-i-intro"/>.
280
<sect2 arch="m68k" id="m68k-boot-cdrom"><title>Booting from a CD-ROM</title>
283
Currently, the only &arch-title; subarchitecture that
284
supports CD-ROM booting is the BVME6000.
288
&boot-installer-intro-cd.xml;
293
<sect2 arch="m68k" id="boot-tftp"><title>Booting with TFTP</title>
295
&boot-installer-intro-net.xml;
299
After booting the VMEbus systems you will be presented with the LILO
300
<prompt>Boot:</prompt> prompt. At that prompt enter one of the
301
following to boot Linux and begin installation proper of the Debian
302
software using vt102 terminal emulation:
304
<!-- Because the &enterkey; definition uses <keycap>, -->
305
<!-- we use <screen> instead of <userinput> in this list -->
310
type <screen>i6000 &enterkey;</screen> to install a BVME4000/6000
315
type <screen>i162 &enterkey;</screen> to install an MVME162
320
type <screen>i167 &enterkey;</screen> to install an MVME166/167
327
You may additionally append the string
328
<screen>TERM=vt100</screen> to use vt100 terminal emulation,
329
e.g., <screen>i6000 TERM=vt100 &enterkey;</screen>.
335
<sect2 arch="m68k" id="boot-from-floppies">
336
<title>Booting from Floppies</title>
339
For most &arch-title; architectures, booting from a local filesystem is the
344
Booting from the boot floppy is supported only for Atari and VME
345
(with a SCSI floppy drive on VME) at this time.