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