1
<!-- retain these comments for translator revision tracking -->
2
<!-- original version: 30283 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
14
</para><para condition="etch">
16
If you are using a 2.2.x linux kernel, then you need to use the &ramdisksize;
21
</para><para condition="sarge">
23
Also, if you are using a 2.2.x linux kernel, then you must make sure you
24
are using a ramdisk built to accommodate it, see the
25
<ulink url="&disturl;/main/installer-&architecture;/current/images/MANIFEST">MANIFEST</ulink>.
26
In general, this means you need to use the initrd22.gz ramdisk from the respective
31
Make sure <userinput>root=/dev/ram</userinput> is one of your kernel
36
If you're having trouble, check
37
<ulink url="&url-m68k-cts-faq;">cts's &arch-title; debian-installer FAQ</ulink>.
42
<listitem><para><xref linkend="m68k-boot-amiga"/></para></listitem>
43
<listitem><para><xref linkend="m68k-boot-atari"/></para></listitem>
44
<listitem><para><xref linkend="m68k-boot-bvme6000"/></para></listitem>
45
<listitem><para><xref linkend="m68k-boot-mac"/></para></listitem>
46
<listitem><para><xref linkend="m68k-boot-mvme"/></para></listitem>
47
<listitem><para><xref linkend="m68k-boot-q40"/></para></listitem>
51
<sect3 id="m68k-boot-amiga"><title>Amiga</title>
54
The only method of installation available to amiga is the hard drive
55
(see <xref linkend="m68k-boot-hd"/>).
56
<emphasis>In other words the cdrom is not bootable.</emphasis>
60
Amiga does not currently work with bogl, so if
61
you are seeing bogl errors, you need to include the kernel parameter
62
<userinput>debian-installer/framebuffer=false</userinput>.
67
<sect3 id="m68k-boot-atari"><title>Atari</title>
70
The installer for atari may be started from either the hard
71
drive (see <xref linkend="m68k-boot-hd"/>) or from floppies
72
(see <xref linkend="boot-from-floppies"/>).
73
<emphasis>In other words the cdrom is not bootable.</emphasis>
77
Atari does not currently work with bogl, so if
78
you are seeing bogl errors, you need to include the kernel parameter
79
<userinput>debian-installer/framebuffer=false</userinput>.
84
<sect3 id="m68k-boot-bvme6000"><title>BVME6000</title>
87
The installer for BVME6000 may be started from a cdrom
88
(see <xref linkend="m68k-boot-cdrom"/>), floppies
89
(see <xref linkend="boot-from-floppies"/>), or the net
90
(see <xref linkend="boot-tftp"/>).
95
<sect3 id="m68k-boot-mac"><title>Macintosh</title>
98
The only method of installation available to mac is from
99
the hard drive (see <xref linkend="m68k-boot-hd"/>).
100
<emphasis>In other words the cdrom is not bootable.</emphasis>
101
Macs do not have a working 2.4.x kernel.
105
If your hardware uses a 53c9x-based scsi bus, then you may need to
106
include the kernel parameter <userinput>mac53c9x=1,0</userinput>.
107
Hardware with two such scsi buses, such as the Quadra 950, will need
108
<userinput>mac53c9x=2,0</userinput> instead. Alternatively, the
109
parameter can be specified as <userinput>mac53c9x=-1,0</userinput>
110
which will leave autodetection on, but which will disable SCSI
111
disconnects. Note that specifying this parameter is only necessary
112
if you have more than one hard disk; otherwise, the system will run
113
faster if you do not specify it.
118
<sect3 id="m68k-boot-mvme"><title>MVME147 and MVME16x</title>
121
The installer for MVME147 and MVME16x may be started from
122
either floppies (see <xref linkend="boot-from-floppies"/>)
123
or the net (see <xref linkend="boot-tftp"/>).
124
<emphasis>In other words the cdrom is not bootable.</emphasis>
129
<sect3 id="m68k-boot-q40"><title>Q40/Q60</title>
132
The only method of installation available to Q40/Q60 is
133
from the hard drive (see <xref linkend="m68k-boot-hd"/>).
134
<emphasis>In other words the cdrom is not bootable.</emphasis>
141
<sect2 arch="m68k" id="m68k-boot-hd"><title>Booting from a Hard Disk</title>
143
&boot-installer-intro-hd.xml;
147
At least six different ramdisks may be used to boot from the hard
148
drive, three different types each with and without support for a
149
2.2.x linux kernel (see
150
<ulink url="&disturl;/main/installer-&architecture;/current/images/MANIFEST">MANIFEST</ulink>
155
The three different types of ramdisks are <filename>cdrom</filename>,
156
<filename>hd-media</filename>, and <filename>nativehd</filename>. These
157
ramdisks differ only in their source for installation packages.
158
The <filename>cdrom</filename> ramdisk uses a cdrom to get
159
debian-installer packages. The <filename>hd-media</filename> ramdisk
160
uses an iso image file of a cdrom currently residing on a hard disk.
161
Finally, the <filename>nativehd</filename> ramdisk uses the net to
167
<listitem><para><xref linkend="m68k-boothd-amiga"/></para></listitem>
168
<listitem><para><xref linkend="m68k-boothd-atari"/></para></listitem>
169
<listitem><para><xref linkend="m68k-boothd-mac"/></para></listitem>
170
<listitem><para><xref linkend="m68k-boothd-q40"/></para></listitem>
174
<sect3 id="m68k-boothd-amiga"><title>Booting from AmigaOS</title>
177
In the <command>Workbench</command>, start the Linux installation
178
process by double-clicking on the <guiicon>StartInstall</guiicon> icon
179
in the <filename>debian</filename> directory.
183
You may have to press the &enterkey; key twice after the Amiga
184
installer program has output some debugging information into a window.
185
After this, the screen will go grey, there will be a few seconds'
186
delay. Next, a black screen with white text should come up, displaying
187
all kinds of kernel debugging information. These messages may scroll
188
by too fast for you to read, but that's OK. After a couple of
189
seconds, the installation program should start automatically, so you
190
can continue down at <xref linkend="d-i-intro"/>.
196
<sect3 id="m68k-boothd-atari"><title>Booting from Atari TOS</title>
199
At the GEM desktop, start the Linux installation process by
200
double-clicking on the <guiicon>bootstra.prg</guiicon> icon in the
201
<filename>debian</filename> directory and clicking
202
<guibutton>Ok</guibutton> at the program options dialog box.
206
You may have to press the &enterkey; key after the Atari
207
bootstrap program has output some debugging information into a
208
window. After this, the screen will go grey, there will be a few
209
seconds' delay. Next, a black screen with white text should come up,
210
displaying all kinds of kernel debugging information. These messages
211
may scroll by too fast for you to read, but that's OK. After a couple
212
of seconds, the installation program should start automatically, so
213
you can continue below at <xref linkend="d-i-intro"/>.
219
<sect3 id="m68k-boothd-mac"><title>Booting from MacOS</title>
222
You must retain the original Mac system and
223
boot from it. It is <emphasis>essential</emphasis> that, when booting
224
MacOS in preparation for booting the Penguin linux loader, you
225
hold the <keycap>shift</keycap> key down to prevent extensions from
226
loading. If you don't use MacOS except for loading linux, you can
227
accomplish the same thing by removing all extensions and control
228
panels from the Mac's System Folder. Otherwise extensions may be left
229
running and cause random problems with the running linux kernel.
233
Macs require the <command>Penguin</command>
234
bootloader. If you do not have the tools to handle
235
a <command>Stuffit</command> archive, &penguin19.hfs; is an
236
hfs disk image with <command>Penguin</command> unpacked.
237
<xref linkend="create-floppy"/> describes how to copy this
242
At the MacOS desktop, start the Linux installation process by
243
double-clicking on the <guiicon>Penguin Prefs</guiicon> icon in
244
the <filename>Penguin</filename> directory. The
245
<command>Penguin</command> booter will start up. Go to the
246
<guimenuitem>Settings</guimenuitem> item in the
247
<guimenu>File</guimenu> menu, click the
248
<guilabel>Kernel</guilabel> tab. Select the kernel
249
(<filename>vmlinuz</filename>) and ramdisk
250
(<filename>initrd.gz</filename>) images in the
251
<filename>install</filename> directory by clicking on the corresponding
252
buttons in the upper right corner, and navigating the file select
253
dialogs to locate the files.
257
To set the boot parameters in Penguin, choose <guimenu>File</guimenu> ->
258
<guimenuitem>Settings...</guimenuitem>, then switch to the
259
<guilabel>Options</guilabel> tab. Boot parameters may be typed in to
260
the text entry area. If you will always want to use these settings,
261
select <guimenu>File</guimenu> -> <guimenuitem>Save Settings as
262
Default</guimenuitem>.
266
Close the <guilabel>Settings</guilabel>
267
dialog, save the settings and start the bootstrap using the
268
<guimenuitem>Boot Now</guimenuitem> item in the
269
<guimenu>File</guimenu> menu.
273
The <command>Penguin</command> booter will output some debugging
274
information into a window. After this, the screen will go grey, there
275
will be a few seconds' delay. Next, a black screen with white text
276
should come up, displaying all kinds of kernel debugging
277
information. These messages may scroll by too fast for you to read,
278
but that's OK. After a couple of seconds, the installation program
279
should start automatically, so you can continue below at
280
<xref linkend="d-i-intro"/>.
286
<sect3 id="m68k-boothd-q40"><title>Booting from Q40/Q60</title>
294
The installation program should start automatically, so you can
295
continue below at <xref linkend="d-i-intro"/>.
303
<sect2 arch="m68k" id="m68k-boot-cdrom"><title>Booting from a CD-ROM</title>
306
Currently, the only &arch-title; subarchitecture that
307
supports CD-ROM booting is the BVME6000.
311
&boot-installer-intro-cd.xml;
316
<sect2 arch="m68k" id="boot-tftp"><title>Booting with TFTP</title>
318
&boot-installer-intro-net.xml;
322
After booting the VMEbus systems you will be presented with the LILO
323
<prompt>Boot:</prompt> prompt. At that prompt enter one of the
324
following to boot Linux and begin installation proper of the Debian
325
software using vt102 terminal emulation:
327
<!-- Because the &enterkey; definition uses <keycap>, -->
328
<!-- we use <screen> instead of <userinput> in this list -->
333
type <screen>i6000 &enterkey;</screen> to install a BVME4000/6000
338
type <screen>i162 &enterkey;</screen> to install an MVME162
343
type <screen>i167 &enterkey;</screen> to install an MVME166/167
350
You may additionally append the string
351
<screen>TERM=vt100</screen> to use vt100 terminal emulation,
352
e.g., <screen>i6000 TERM=vt100 &enterkey;</screen>.
358
<sect2 arch="m68k" id="boot-from-floppies">
359
<title>Booting from Floppies</title>
362
For most &arch-title; architectures, booting from a local filesystem is the
367
Booting from the boot floppy is supported only for Atari and VME
368
(with a SCSI floppy drive on VME) at this time.