en/boot-installer/m68k.xml

<!-- retain these comments for translator revision tracking -->
<!-- $Id: m68k.xml,v 1.7 2004/03/11 17:29:52 mck-guest Exp $ -->


  <sect2 arch="m68k"><title>Booting from Hard Disk</title>

&boot-installer-intro-hd.xml;

  </sect2>

  <sect2 arch="m68k"><title>Booting from AmigaOS</title>
<para>

In the <command>Workbench</command>, start the Linux installation
process by double-clicking on the <guiicon>StartInstall</guiicon> icon
in the <filename>debian</filename> directory.

</para><para>

You may have to press the &enterkey; key twice after the Amiga
installer program has output some debugging information into a window.
After this, the screen will go grey, there will be a few seconds'
delay. Next, a black screen with white text should come up, displaying
all kinds of kernel debugging information.  These messages may scroll
by too fast for you to read, but that's OK.  After a couple of
seconds, the installation program should start automatically, so you
can continue down at <xref linkend="init-config"/>.

</para>
  </sect2>


  <sect2 arch="m68k"><title>Booting from Atari TOS</title>
<para>

At the GEM desktop, start the Linux installation process by
double-clicking on the <guiicon>bootstra.prg</guiicon> icon in the
<filename>debian</filename> directory and clicking
<guibutton>Ok</guibutton> at the program options dialog box.

</para><para>

You may have to press the &enterkey; key after the Atari
bootstrap program has output some debugging information into a
window. After this, the screen will go grey, there will be a few
seconds' delay.  Next, a black screen with white text should come up,
displaying all kinds of kernel debugging information. These messages
may scroll by too fast for you to read, but that's OK. After a couple
of seconds, the installation program should start automatically, so
you can continue below at <xref linkend="init-config"/>.

</para>
  </sect2>


  <sect2 arch="m68k"><title>Booting from 68k MacOS</title>
<para>

At the MacOS desktop, start the Linux installation process by
double-clicking on the <guiicon>Penguin Prefs</guiicon> icon in
the <filename>debian</filename> directory. The
<command>Penguin</command> booter will start up. Go to the
<guimenuitem>Settings</guimenuitem> item in the
<guimenu>File</guimenu> menu, click the
<guilabel>Kernel</guilabel> tab.  Select the kernel
(<filename>linux.bin</filename>) and ramdisk
(<filename>root.bin</filename>) images in the
<filename>debian</filename> directory by clicking on the corresponding
buttons in the upper right corner, and navigating the file select
dialogs to locate the files. Close the <guilabel>Settings</guilabel>
dialog, save the settings and start the bootstrap using the
<guimenuitem>Boot Now</guimenuitem> item in the
<guimenu>File</guimenu> menu.

</para><para>

The <command>Penguin</command> booter will output some debugging
information into a window. After this, the screen will go grey, there
will be a few seconds' delay. Next, a black screen with white text
should come up, displaying all kinds of kernel debugging
information. These messages may scroll by too fast for you to read,
but that's OK. After a couple of seconds, the installation program
should start automatically, so you can continue below at 
<xref linkend="init-config"/>.

</para>
  </sect2>


  <sect2 arch="m68k"><title>Booting from a CD-ROM</title>

&boot-installer-intro-cd.xml;

<para>

Currently, the only &arch-title; subarchitecture that
supports CD-ROM booting is the BVME6000. The easiest route In that
case will be to use a 
<ulink url="&url-debian-cd-vendors;">set of Debian CDs</ulink>. 
Simply insert your CD, reboot, and proceed to the next chapter.  

</para>
  </sect2>


  <sect2 arch="m68k" id="boot-tftp"><title>Booting with TFTP</title>

&boot-installer-intro-net.xml;

<para>

After booting the VMEbus systems you will be presented with the LILO
<prompt>Boot:</prompt> prompt.  At that prompt enter one of the
following to boot Linux and begin installation proper of the Debian
software using vt102 terminal emulation:

<!-- Because the &enterkey; definition uses <keycap>,    -->
<!-- we use <screen> instead of <userinput> in this list -->

<itemizedlist>
<listitem><para>

type <screen>i6000 &enterkey;</screen> to install a BVME4000/6000

</para></listitem>
<listitem><para>

type <screen>i162 &enterkey;</screen> to install an MVME162

</para></listitem>
<listitem><para>

type <screen>i167 &enterkey;</screen> to install an MVME166/167

</para></listitem>
    </itemizedlist>

</para><para>

You may additionally append the string
<screen>TERM=vt100</screen> to use vt100 terminal emulation,
e.g., <screen>i6000 TERM=vt100 &enterkey;</screen>.

</para>
  </sect2>


  <sect2 arch="m68k" id="boot-from-floppies">
  <title>Booting from Floppies</title>
<para>

For most m68k architectures, booting from a local filesystem is the
recommended method.

</para><para>

Booting from the boot floppy is supported only for Atari and VME
(with a SCSI floppy drive on VME) at this time. 

</para>
 </sect2>


  <sect2 arch="m68k"><title>Macintosh Limitations</title>
<para>

In the case of Macintosh, you must retain the original Mac system and
boot from it. It is <emphasis>essential</emphasis> that, when booting
MacOS in preparation for booting the Penguin linux loader, you must
hold the <keycap>shift</keycap> key down to prevent extensions from
loading. If you
don't use MacOS except for loading linux, you can accomplish the same
thing by removing all extensions and control panels from the Mac's
System Folder. Otherwise extensions may be left running and cause
random problems with the running linux kernel.

</para>
  </sect2>


  <sect2 arch="m68k"><title>Penguin Boot Parameters</title>
<para>

In the Penguin boot program, choose <guimenu>File</guimenu> -&gt;
<guimenuitem>Settings...</guimenuitem>, then switch to the
<guilabel>Options</guilabel> tab.  Boot parameters may be typed in to
the text entry area.  If you will always want to use these settings,
select <guimenu>File</guimenu> -&gt; <guimenuitem>Save Settings as
Default</guimenuitem>.

</para>
  </sect2>
1	toff	5236	<!-- retain these comments for translator revision tracking -->
2	mck-guest	10377	<!-- $Id: m68k.xml,v 1.7 2004/03/11 17:29:52 mck-guest Exp $ -->
3	toff	5236
4
5	toff	5444	<sect2 arch="m68k"><title>Booting from Hard Disk</title>
6
7			&boot-installer-intro-hd.xml;
8
9			</sect2>
10
11	toff	5236	<sect2 arch="m68k"><title>Booting from AmigaOS</title>
12			<para>
13
14	toff	5444	In the <command>Workbench</command>, start the Linux installation
15	mck	5692	process by double-clicking on the <guiicon>StartInstall</guiicon> icon
16			in the <filename>debian</filename> directory.
17	toff	5236
18			</para><para>
19
20			You may have to press the &enterkey; key twice after the Amiga
21			installer program has output some debugging information into a window.
22			After this, the screen will go grey, there will be a few seconds'
23			delay. Next, a black screen with white text should come up, displaying
24			all kinds of kernel debugging information. These messages may scroll
25			by too fast for you to read, but that's OK. After a couple of
26			seconds, the installation program should start automatically, so you
27	toff	5338	can continue down at <xref linkend="init-config"/>.
28	toff	5236
29			</para>
30			</sect2>
31
32
33			<sect2 arch="m68k"><title>Booting from Atari TOS</title>
34			<para>
35
36			At the GEM desktop, start the Linux installation process by
37	mck	5692	double-clicking on the <guiicon>bootstra.prg</guiicon> icon in the
38			<filename>debian</filename> directory and clicking
39	mck-guest	7337	<guibutton>Ok</guibutton> at the program options dialog box.
40	toff	5236
41			</para><para>
42
43			You may have to press the &enterkey; key after the Atari
44			bootstrap program has output some debugging information into a
45			window. After this, the screen will go grey, there will be a few
46			seconds' delay. Next, a black screen with white text should come up,
47			displaying all kinds of kernel debugging information. These messages
48			may scroll by too fast for you to read, but that's OK. After a couple
49			of seconds, the installation program should start automatically, so
50	toff	5338	you can continue below at <xref linkend="init-config"/>.
51	toff	5236
52			</para>
53			</sect2>
54
55
56			<sect2 arch="m68k"><title>Booting from 68k MacOS</title>
57			<para>
58
59			At the MacOS desktop, start the Linux installation process by
60	mck	5692	double-clicking on the <guiicon>Penguin Prefs</guiicon> icon in
61	toff	5444	the <filename>debian</filename> directory. The
62			<command>Penguin</command> booter will start up. Go to the
63	mck	5692	<guimenuitem>Settings</guimenuitem> item in the
64			<guimenu>File</guimenu> menu, click the
65			<guilabel>Kernel</guilabel> tab. Select the kernel
66	toff	5444	(<filename>linux.bin</filename>) and ramdisk
67			(<filename>root.bin</filename>) images in the
68			<filename>debian</filename> directory by clicking on the corresponding
69	toff	5236	buttons in the upper right corner, and navigating the file select
70	mck	5692	dialogs to locate the files. Close the <guilabel>Settings</guilabel>
71	toff	5444	dialog, save the settings and start the bootstrap using the
72	mck	5692	<guimenuitem>Boot Now</guimenuitem> item in the
73			<guimenu>File</guimenu> menu.
74	toff	5236
75			</para><para>
76
77	toff	5444	The <command>Penguin</command> booter will output some debugging
78			information into a window. After this, the screen will go grey, there
79			will be a few seconds' delay. Next, a black screen with white text
80			should come up, displaying all kinds of kernel debugging
81			information. These messages may scroll by too fast for you to read,
82			but that's OK. After a couple of seconds, the installation program
83			should start automatically, so you can continue below at
84			<xref linkend="init-config"/>.
85	toff	5236
86			</para>
87			</sect2>
88
89
90	toff	5444	<sect2 arch="m68k"><title>Booting from a CD-ROM</title>
91
92			&boot-installer-intro-cd.xml;
93
94	toff	5236	<para>
95
96			Currently, the only &arch-title; subarchitecture that
97			supports CD-ROM booting is the BVME6000. The easiest route In that
98			case will be to use a
99	toff	5338	<ulink url="&url-debian-cd-vendors;">set of Debian CDs</ulink>.
100	toff	5236	Simply insert your CD, reboot, and proceed to the next chapter.
101
102			</para>
103			</sect2>
104
105
106	stappers-guest	10363	<sect2 arch="m68k" id="boot-tftp"><title>Booting with TFTP</title>
107	toff	5444
108			&boot-installer-intro-net.xml;
109
110	toff	5236	<para>
111
112	toff	5444	After booting the VMEbus systems you will be presented with the LILO
113	mck	5692	<prompt>Boot:</prompt> prompt. At that prompt enter one of the
114	toff	5236	following to boot Linux and begin installation proper of the Debian
115			software using vt102 terminal emulation:
116	toff	5338
117	mck	5692	<!-- Because the &enterkey; definition uses <keycap>, -->
118	toff	5444	<!-- we use <screen> instead of <userinput> in this list -->
119
120	toff	5236	<itemizedlist>
121	toff	5338	<listitem><para>
122
123	toff	5444	type <screen>i6000 &enterkey;</screen> to install a BVME4000/6000
124	toff	5338
125			</para></listitem>
126			<listitem><para>
127
128	toff	5444	type <screen>i162 &enterkey;</screen> to install an MVME162
129	toff	5338
130			</para></listitem>
131			<listitem><para>
132
133	toff	5444	type <screen>i167 &enterkey;</screen> to install an MVME166/167
134	toff	5338
135			</para></listitem>
136	toff	5236	</itemizedlist>
137
138	toff	5338	</para><para>
139	toff	5236
140	toff	5338	You may additionally append the string
141	toff	5444	<screen>TERM=vt100</screen> to use vt100 terminal emulation,
142			e.g., <screen>i6000 TERM=vt100 &enterkey;</screen>.
143	toff	5236
144			</para>
145			</sect2>
146
147
148	toff	5338	<sect2 arch="m68k" id="boot-from-floppies">
149			<title>Booting from Floppies</title>
150	toff	5236	<para>
151
152			For most m68k architectures, booting from a local filesystem is the
153			recommended method.
154
155			</para><para>
156
157	mck-guest	10377	Booting from the boot floppy is supported only for Atari and VME
158	toff	5236	(with a SCSI floppy drive on VME) at this time.
159
160			</para>
161			</sect2>
162
163
164			<sect2 arch="m68k"><title>Macintosh Limitations</title>
165			<para>
166
167	toff	5444	In the case of Macintosh, you must retain the original Mac system and
168			boot from it. It is <emphasis>essential</emphasis> that, when booting
169	toff	5236	MacOS in preparation for booting the Penguin linux loader, you must
170	mck	5692	hold the <keycap>shift</keycap> key down to prevent extensions from
171			loading. If you
172	toff	5236	don't use MacOS except for loading linux, you can accomplish the same
173			thing by removing all extensions and control panels from the Mac's
174			System Folder. Otherwise extensions may be left running and cause
175			random problems with the running linux kernel.
176
177			</para>
178			</sect2>
179
180
181			<sect2 arch="m68k"><title>Penguin Boot Parameters</title>
182			<para>
183
184	mck	5692	In the Penguin boot program, choose <guimenu>File</guimenu> ->
185			<guimenuitem>Settings...</guimenuitem>, then switch to the
186	mck-guest	7337	<guilabel>Options</guilabel> tab. Boot parameters may be typed in to
187	mck	5692	the text entry area. If you will always want to use these settings,
188	mck-guest	7337	select <guimenu>File</guimenu> -> <guimenuitem>Save Settings as
189			Default</guimenuitem>.
190	toff	5236
191			</para>
192			</sect2>