| 1 |
<!-- retain these comments for translator revision tracking -->
|
| 2 |
<!-- $Id$ -->
|
| 3 |
|
| 4 |
<sect2 arch="m68k"><title>Choosing an Installation Method</title>
|
| 5 |
|
| 6 |
<para>
|
| 7 |
|
| 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
|
| 12 |
and 2.4.x uses tmpfs.
|
| 13 |
|
| 14 |
</para><para>
|
| 15 |
|
| 16 |
If you are using a 2.2.x linux kernel, then you must make sure you
|
| 17 |
are using a ramdisk built to accommodate 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. In general, this
|
| 19 |
means you need to use the initrd22.gz ramdisk from the respective
|
| 20 |
directory.
|
| 21 |
|
| 22 |
</para><para>
|
| 23 |
|
| 24 |
Make sure <userinput>root=/dev/ram</userinput> is one of your kernel
|
| 25 |
parameters.
|
| 26 |
|
| 27 |
</para><para>
|
| 28 |
|
| 29 |
If you're having trouble, check
|
| 30 |
<ulink url="&url-m68k-cts-faq;">cts's &arch-title; debian-installer FAQ</ulink>.
|
| 31 |
|
| 32 |
</para>
|
| 33 |
|
| 34 |
<itemizedlist>
|
| 35 |
<listitem><para><xref linkend="m68k-boot-amiga"/></para></listitem>
|
| 36 |
<listitem><para><xref linkend="m68k-boot-atari"/></para></listitem>
|
| 37 |
<listitem><para><xref linkend="m68k-boot-bvme6000"/></para></listitem>
|
| 38 |
<listitem><para><xref linkend="m68k-boot-mac"/></para></listitem>
|
| 39 |
<listitem><para><xref linkend="m68k-boot-mvme"/></para></listitem>
|
| 40 |
<listitem><para><xref linkend="m68k-boot-q40"/></para></listitem>
|
| 41 |
</itemizedlist>
|
| 42 |
|
| 43 |
|
| 44 |
<sect3 arch="m68k" id="m68k-boot-amiga"><title>Amiga</title>
|
| 45 |
<para>
|
| 46 |
|
| 47 |
The only method of installation available to amiga is the hard drive
|
| 48 |
(see <xref linkend="m68k-boot-hd"/>).
|
| 49 |
<emphasis>In other words the cdrom is not bootable.</emphasis>
|
| 50 |
|
| 51 |
</para><para>
|
| 52 |
|
| 53 |
Amiga does not currently work with bogl, so if
|
| 54 |
you are seeing bogl errors, you need to include the kernel parameter
|
| 55 |
<userinput>debian-installer/framebuffer=false</userinput>.
|
| 56 |
|
| 57 |
</para>
|
| 58 |
</sect3>
|
| 59 |
|
| 60 |
<sect3 arch="m68k" id="m68k-boot-atari"><title>Atari</title>
|
| 61 |
<para>
|
| 62 |
|
| 63 |
The installer for atari may be started from either the hard
|
| 64 |
drive (see <xref linkend="m68k-boot-hd"/>) or from floppies
|
| 65 |
(see <xref linkend="boot-from-floppies"/>).
|
| 66 |
<emphasis>In other words the cdrom is not bootable.</emphasis>
|
| 67 |
|
| 68 |
</para><para>
|
| 69 |
|
| 70 |
Atari does not currently work with bogl, so if
|
| 71 |
you are seeing bogl errors, you need to include the kernel parameter
|
| 72 |
<userinput>debian-installer/framebuffer=false</userinput>.
|
| 73 |
|
| 74 |
</para>
|
| 75 |
</sect3>
|
| 76 |
|
| 77 |
<sect3 arch="m68k" id="m68k-boot-bvme6000"><title>BVME6000</title>
|
| 78 |
<para>
|
| 79 |
|
| 80 |
The installer for BVME6000 may be started from a cdrom
|
| 81 |
(see <xref linkend="m68k-boot-cdrom"/>), floppies
|
| 82 |
(see <xref linkend="boot-from-floppies"/>), or the net
|
| 83 |
(see <xref linkend="boot-tftp"/>).
|
| 84 |
|
| 85 |
</para>
|
| 86 |
</sect3>
|
| 87 |
|
| 88 |
<sect3 arch="m68k" id="m68k-boot-mac"><title>Macintosh</title>
|
| 89 |
<para>
|
| 90 |
|
| 91 |
The only method of installation available to mac is from
|
| 92 |
the hard drive (see <xref linkend="m68k-boot-hd"/>).
|
| 93 |
<emphasis>In other words the cdrom is not bootable.</emphasis>
|
| 94 |
Macs do not have a working 2.4.x kernel.
|
| 95 |
|
| 96 |
</para><para>
|
| 97 |
|
| 98 |
If your hardware uses a 53c9x-based scsi bus, then you may need to
|
| 99 |
include the kernel parameter <userinput>mac53c9x=1</userinput>.
|
| 100 |
Hardware with two such scsi buses, such as the Quadra 950, will need
|
| 101 |
<userinput>mac53c9x=2</userinput> instead.
|
| 102 |
|
| 103 |
</para>
|
| 104 |
</sect3>
|
| 105 |
|
| 106 |
<sect3 arch="m68k" id="m68k-boot-mvme"><title>MVME147 and MVME16x</title>
|
| 107 |
<para>
|
| 108 |
|
| 109 |
The installer for MVEM147 and MVEM16x may be started from
|
| 110 |
either floppies (see <xref linkend="boot-from-floppies"/>)
|
| 111 |
or the net (see <xref linkend="boot-tftp"/>).
|
| 112 |
<emphasis>In other words the cdrom is not bootable.</emphasis>
|
| 113 |
|
| 114 |
</para>
|
| 115 |
</sect3>
|
| 116 |
|
| 117 |
<sect3 arch="m68k" id="m68k-boot-q40"><title>Q40/Q60</title>
|
| 118 |
<para>
|
| 119 |
|
| 120 |
The only method of installation available to Q40/Q60 is
|
| 121 |
from the hard drive (see <xref linkend="m68k-boot-hd"/>).
|
| 122 |
<emphasis>In other words the cdrom is not bootable.</emphasis>
|
| 123 |
|
| 124 |
</para>
|
| 125 |
</sect3>
|
| 126 |
|
| 127 |
</sect2>
|
| 128 |
|
| 129 |
<sect2 arch="m68k" id="m68k-boot-hd"><title>Booting from a Hard Disk</title>
|
| 130 |
|
| 131 |
&boot-installer-intro-hd.xml;
|
| 132 |
|
| 133 |
<para>
|
| 134 |
|
| 135 |
At least six different ramdisks may be used to boot from the hard
|
| 136 |
drive, three different types each with and without support for a
|
| 137 |
2.2.x linux kernel (see
|
| 138 |
<ulink url="&disturl;/main/installer-&architecture;/current/images/MANIFEST">MANIFEST</ulink>
|
| 139 |
for details).
|
| 140 |
|
| 141 |
</para><para>
|
| 142 |
|
| 143 |
The three different types of ramdisks are <filename>cdrom</filename>,
|
| 144 |
<filename>hd-media</filename>, and <filename>nativehd</filename>. These
|
| 145 |
ramdisks differ only in their source for installation packages.
|
| 146 |
The <filename>cdrom</filename> ramdisk uses a cdrom to get
|
| 147 |
debian-installer packages. The <filename>hd-media</filename> ramdisk
|
| 148 |
uses an iso image file of a cdrom currently residing on a hard disk.
|
| 149 |
Finally, the <filename>nativehd</filename> ramdisk uses the net to
|
| 150 |
install packages.
|
| 151 |
|
| 152 |
</para>
|
| 153 |
|
| 154 |
<itemizedlist>
|
| 155 |
<listitem><para><xref linkend="m68k-boothd-amiga"/></para></listitem>
|
| 156 |
<listitem><para><xref linkend="m68k-boothd-atari"/></para></listitem>
|
| 157 |
<listitem><para><xref linkend="m68k-boothd-mac"/></para></listitem>
|
| 158 |
<listitem><para><xref linkend="m68k-boothd-q40"/></para></listitem>
|
| 159 |
</itemizedlist>
|
| 160 |
|
| 161 |
|
| 162 |
<sect3 arch="m68k" id="m68k-boothd-amiga"><title>Booting from AmigaOS</title>
|
| 163 |
<para>
|
| 164 |
|
| 165 |
In the <command>Workbench</command>, start the Linux installation
|
| 166 |
process by double-clicking on the <guiicon>StartInstall</guiicon> icon
|
| 167 |
in the <filename>debian</filename> directory.
|
| 168 |
|
| 169 |
</para><para>
|
| 170 |
|
| 171 |
You may have to press the &enterkey; key twice after the Amiga
|
| 172 |
installer program has output some debugging information into a window.
|
| 173 |
After this, the screen will go grey, there will be a few seconds'
|
| 174 |
delay. Next, a black screen with white text should come up, displaying
|
| 175 |
all kinds of kernel debugging information. These messages may scroll
|
| 176 |
by too fast for you to read, but that's OK. After a couple of
|
| 177 |
seconds, the installation program should start automatically, so you
|
| 178 |
can continue down at <xref linkend="d-i-intro"/>.
|
| 179 |
|
| 180 |
</para>
|
| 181 |
</sect3>
|
| 182 |
|
| 183 |
|
| 184 |
<sect3 arch="m68k" id="m68k-boothd-atari"><title>Booting from Atari TOS</title>
|
| 185 |
<para>
|
| 186 |
|
| 187 |
At the GEM desktop, start the Linux installation process by
|
| 188 |
double-clicking on the <guiicon>bootstra.prg</guiicon> icon in the
|
| 189 |
<filename>debian</filename> directory and clicking
|
| 190 |
<guibutton>Ok</guibutton> at the program options dialog box.
|
| 191 |
|
| 192 |
</para><para>
|
| 193 |
|
| 194 |
You may have to press the &enterkey; key after the Atari
|
| 195 |
bootstrap program has output some debugging information into a
|
| 196 |
window. After this, the screen will go grey, there will be a few
|
| 197 |
seconds' delay. Next, a black screen with white text should come up,
|
| 198 |
displaying all kinds of kernel debugging information. These messages
|
| 199 |
may scroll by too fast for you to read, but that's OK. After a couple
|
| 200 |
of seconds, the installation program should start automatically, so
|
| 201 |
you can continue below at <xref linkend="d-i-intro"/>.
|
| 202 |
|
| 203 |
</para>
|
| 204 |
</sect3>
|
| 205 |
|
| 206 |
|
| 207 |
<sect3 arch="m68k" id="m68k-boothd-mac"><title>Booting from MacOS</title>
|
| 208 |
<para>
|
| 209 |
|
| 210 |
You must retain the original Mac system and
|
| 211 |
boot from it. It is <emphasis>essential</emphasis> that, when booting
|
| 212 |
MacOS in preparation for booting the Penguin linux loader, you
|
| 213 |
hold the <keycap>shift</keycap> key down to prevent extensions from
|
| 214 |
loading. If you don't use MacOS except for loading linux, you can
|
| 215 |
accomplish the same thing by removing all extensions and control
|
| 216 |
panels from the Mac's System Folder. Otherwise extensions may be left
|
| 217 |
running and cause random problems with the running linux kernel.
|
| 218 |
|
| 219 |
</para><para>
|
| 220 |
|
| 221 |
Macs require the <command>Penguin</command>
|
| 222 |
bootloader. If you do not have the tools to handle
|
| 223 |
a <command>Stuffit</command> archive, &penguin19.hfs; is an
|
| 224 |
hfs disk image with <command>Penguin</command> unpacked.
|
| 225 |
<xref linkend="create-floppy"/> describes how to copy this
|
| 226 |
image to a floppy.
|
| 227 |
|
| 228 |
</para><para>
|
| 229 |
|
| 230 |
At the MacOS desktop, start the Linux installation process by
|
| 231 |
double-clicking on the <guiicon>Penguin Prefs</guiicon> icon in
|
| 232 |
the <filename>Penguin</filename> directory. The
|
| 233 |
<command>Penguin</command> booter will start up. Go to the
|
| 234 |
<guimenuitem>Settings</guimenuitem> item in the
|
| 235 |
<guimenu>File</guimenu> menu, click the
|
| 236 |
<guilabel>Kernel</guilabel> tab. Select the kernel
|
| 237 |
(<filename>vmlinuz</filename>) and ramdisk
|
| 238 |
(<filename>initrd.gz</filename>) images in the
|
| 239 |
<filename>install</filename> directory by clicking on the corresponding
|
| 240 |
buttons in the upper right corner, and navigating the file select
|
| 241 |
dialogs to locate the files.
|
| 242 |
|
| 243 |
</para><para>
|
| 244 |
|
| 245 |
To set the boot parameters in Penguin, choose <guimenu>File</guimenu> ->
|
| 246 |
<guimenuitem>Settings...</guimenuitem>, then switch to the
|
| 247 |
<guilabel>Options</guilabel> tab. Boot parameters may be typed in to
|
| 248 |
the text entry area. If you will always want to use these settings,
|
| 249 |
select <guimenu>File</guimenu> -> <guimenuitem>Save Settings as
|
| 250 |
Default</guimenuitem>.
|
| 251 |
|
| 252 |
</para><para>
|
| 253 |
|
| 254 |
Close the <guilabel>Settings</guilabel>
|
| 255 |
dialog, save the settings and start the bootstrap using the
|
| 256 |
<guimenuitem>Boot Now</guimenuitem> item in the
|
| 257 |
<guimenu>File</guimenu> menu.
|
| 258 |
|
| 259 |
</para><para>
|
| 260 |
|
| 261 |
The <command>Penguin</command> booter will output some debugging
|
| 262 |
information into a window. After this, the screen will go grey, there
|
| 263 |
will be a few seconds' delay. Next, a black screen with white text
|
| 264 |
should come up, displaying all kinds of kernel debugging
|
| 265 |
information. These messages may scroll by too fast for you to read,
|
| 266 |
but that's OK. After a couple of seconds, the installation program
|
| 267 |
should start automatically, so you can continue below at
|
| 268 |
<xref linkend="d-i-intro"/>.
|
| 269 |
|
| 270 |
</para>
|
| 271 |
|
| 272 |
</sect3>
|
| 273 |
|
| 274 |
<sect3 arch="m68k" id="m68k-boothd-q40"><title>Booting from Q40/Q60</title>
|
| 275 |
|
| 276 |
<para>
|
| 277 |
|
| 278 |
FIXME
|
| 279 |
|
| 280 |
</para><para>
|
| 281 |
|
| 282 |
The installation program should start automatically, so you can
|
| 283 |
continue below at <xref linkend="d-i-intro"/>.
|
| 284 |
|
| 285 |
</para>
|
| 286 |
|
| 287 |
</sect3>
|
| 288 |
</sect2>
|
| 289 |
|
| 290 |
|
| 291 |
<sect2 arch="m68k" id="m68k-boot-cdrom"><title>Booting from a CD-ROM</title>
|
| 292 |
<para>
|
| 293 |
|
| 294 |
Currently, the only &arch-title; subarchitecture that
|
| 295 |
supports CD-ROM booting is the BVME6000.
|
| 296 |
|
| 297 |
</para>
|
| 298 |
|
| 299 |
&boot-installer-intro-cd.xml;
|
| 300 |
|
| 301 |
</sect2>
|
| 302 |
|
| 303 |
|
| 304 |
<sect2 arch="m68k" id="boot-tftp"><title>Booting with TFTP</title>
|
| 305 |
|
| 306 |
&boot-installer-intro-net.xml;
|
| 307 |
|
| 308 |
<para>
|
| 309 |
|
| 310 |
After booting the VMEbus systems you will be presented with the LILO
|
| 311 |
<prompt>Boot:</prompt> prompt. At that prompt enter one of the
|
| 312 |
following to boot Linux and begin installation proper of the Debian
|
| 313 |
software using vt102 terminal emulation:
|
| 314 |
|
| 315 |
<!-- Because the &enterkey; definition uses <keycap>, -->
|
| 316 |
<!-- we use <screen> instead of <userinput> in this list -->
|
| 317 |
|
| 318 |
<itemizedlist>
|
| 319 |
<listitem><para>
|
| 320 |
|
| 321 |
type <screen>i6000 &enterkey;</screen> to install a BVME4000/6000
|
| 322 |
|
| 323 |
</para></listitem>
|
| 324 |
<listitem><para>
|
| 325 |
|
| 326 |
type <screen>i162 &enterkey;</screen> to install an MVME162
|
| 327 |
|
| 328 |
</para></listitem>
|
| 329 |
<listitem><para>
|
| 330 |
|
| 331 |
type <screen>i167 &enterkey;</screen> to install an MVME166/167
|
| 332 |
|
| 333 |
</para></listitem>
|
| 334 |
</itemizedlist>
|
| 335 |
|
| 336 |
</para><para>
|
| 337 |
|
| 338 |
You may additionally append the string
|
| 339 |
<screen>TERM=vt100</screen> to use vt100 terminal emulation,
|
| 340 |
e.g., <screen>i6000 TERM=vt100 &enterkey;</screen>.
|
| 341 |
|
| 342 |
</para>
|
| 343 |
</sect2>
|
| 344 |
|
| 345 |
|
| 346 |
<sect2 arch="m68k" id="boot-from-floppies">
|
| 347 |
<title>Booting from Floppies</title>
|
| 348 |
<para>
|
| 349 |
|
| 350 |
For most &arch-title; architectures, booting from a local filesystem is the
|
| 351 |
recommended method.
|
| 352 |
|
| 353 |
</para><para>
|
| 354 |
|
| 355 |
Booting from the boot floppy is supported only for Atari and VME
|
| 356 |
(with a SCSI floppy drive on VME) at this time.
|
| 357 |
|
| 358 |
</para>
|
| 359 |
</sect2>
|
| 360 |
|
Parent Directory
| 
Revision Log