10
10
Your system's first boot on its own power is what electrical engineers
11
11
call the <quote>smoke test</quote>.
13
</para><para arch="x86">
15
If you did a default installation, the first thing you should see when you
16
boot the system is the menu of the <classname>grub</classname> or possibly
17
the <classname>lilo</classname> bootloader.
18
The first choices in the menu will be for your new Ubuntu system. If you
19
had any other operating systems on your computer (like Windows) that were
20
detected by the installation system, those will be listed lower down in the
15
If you are booting directly into Ubuntu, and the system doesn't start
16
up, either use your original installation boot media, or insert the
17
custom boot floppy if you have one, and reset your system. This way,
18
you will probably need to add some boot arguments like
19
<userinput>root=<replaceable>root</replaceable></userinput>, where
20
<replaceable>root</replaceable> is your root partition, such as
21
<filename>/dev/sda1</filename>.
22
Alternatively, see <xref linkend="rescue"/> for instructions on using
23
the installer's built-in rescue mode.
25
If the system fails to start up correctly, don't panic. If the installation
26
was successful, chances are good that there is only a relatively minor
27
problem that is preventing the system from booting Ubuntu. In most cases
28
such problems can be fixed without having to repeat the installation.
29
One available option to fix boot problems is to use the installer's
30
built-in rescue mode (see <xref linkend="rescue"/>).
32
</para><para condition="not-ubuntu">
34
If you are new to Debian and Linux, you may need some help from more
36
<phrase arch="x86">For direct on-line help you can try the IRC channels
37
#debian or #debian-boot on the OFTC network. Alternatively you can contact
38
the <ulink url="&url-list-subscribe;">debian-user mailing list</ulink>.</phrase>
39
<phrase arch="not-x86">For less common architectures like &arch-title;,
40
your best option is to ask on the
41
<ulink url="&url-list-subscribe;">debian-&arch-listname; mailing
42
list</ulink>.</phrase>
43
You can also file an installation report as described in
44
<xref linkend="submit-bug"/>. Please make sure that you describe your problem
45
clearly and include any messages that are displayed and may help others to
48
</para><para arch="x86">
50
If you had any other operating systems on your computer that were not detected
51
or not detected correctly, please file an installation report.
65
93
<userinput>Settings</userinput> dialogue (<keycombo>
66
94
<keycap>command</keycap> <keycap>T</keycap> </keycombo>), and locate
67
95
the kernel options line which should look like
68
<userinput>root=/dev/ram video=font:VGA8x16</userinput> or similar.
96
<userinput>root=/dev/ram ramdisk_size=15000</userinput> or similar.
72
100
You need to change the entry to
73
101
<userinput>root=/dev/<replaceable>yyyy</replaceable></userinput>.
74
102
Replace the <replaceable>yyyy</replaceable> with the Linux name of the
75
partition onto which you installed the system
76
(e.g. <filename>/dev/sda1</filename>); you wrote this down earlier.
77
The <userinput>video=font:VGA8x8</userinput> is recommended especially
78
for users with tiny screens. The kernel would pick a prettier (6x11)
79
font but the console driver for this font can hang the machine, so
80
using 8x16 or 8x8 is safer at this stage. You can change this at any
103
partition onto which you installed the system (e.g.
104
<filename>/dev/sda1</filename>); you wrote this down earlier. For users
105
with tiny screens, adding <userinput>fbcon=font:VGA8x8</userinput> (or
106
<userinput>video=font:VGA8x8</userinput> on pre-2.6 kernels) may help
107
readability. You can change this at any time.
191
<sect1 id="mount-encrypted-volumes">
192
<title>Mounting encrypted volumes</title>
196
If you created encrypted volumes during the installation and assigned
197
them mount points, you will be asked to enter the passphrase for each
198
of these volumes during the boot. The actual procedure differs
199
slightly between dm-crypt and loop-AES.
203
<sect2 id="mount-loop-aes">
204
<title>loop-AES</title>
208
For partitions encrypted via loop-AES you will be shown the following
209
prompt during the boot:
211
<informalexample><screen>
212
mount: going to use loop device /dev/loop<replaceable>X</replaceable>
214
</screen></informalexample>
216
In the first line of the prompt, <replaceable>X</replaceable> is the
217
number of the loop device. You are now probably wondering
218
<emphasis>for which volume</emphasis> you are actually entering the
219
passphrase. Does it relate to your <filename>/home</filename>? Or to
220
<filename>/var</filename>? Of course, if you have just one encrypted
221
volume, this is easy and you can just enter the passphrase you used
222
when setting up this volume. If you set up more than one encrypted
223
volume during the installation, the notes you wrote down as the last
224
step in <xref linkend="partman-crypto"/> come in handy. If you did not
225
make a note of the mapping between
226
<filename>loop<replaceable>X</replaceable></filename> and the mount
227
points before, you can still find it
228
in <filename>/etc/fstab</filename> of your new system.
232
No characters (even asterisks) will be shown while entering the
233
passphrase. Be careful, you have only <emphasis>one try</emphasis>. If
234
you enter wrong passphrase, an error message will appear and the boot
235
process will skip that volume and continue to mount the next
236
filesystem. Please see <xref linkend="crypto-troubleshooting"/> for
241
After entering all passphrases the boot should continue as usual.
246
<sect2 id="mount-dm-crypt" condition="FIXME">
247
<title>dm-crypt</title>
251
TODO: write something once it works.
256
<sect2 id="crypto-troubleshooting">
257
<title>Troubleshooting</title>
261
If some of the encrypted volumes could not be mounted because a wrong
262
passphrase was entered, you will have to mount them manually after the
263
boot. There are several cases.
270
The first case concerns the root partition. When it is not mounted
271
correctly, the boot process will halt and you will have to reboot the
272
computer to try again.
277
The easiest case is for encrypted volumes holding data like
278
<filename>/home</filename> or <filename>/srv</filename>. You can
279
simply mount them manually after the boot. For loop-AES this is
282
<informalexample><screen>
283
<prompt>#</prompt> <userinput>mount <replaceable>/mount_point</replaceable></userinput>
284
<prompt>Password:</prompt>
285
</screen></informalexample>
287
where <replaceable>/mount_point</replaceable> should be replaced by
288
the particular directory (e.g. <filename>/home</filename>). The only
289
difference from an ordinary mount is that you will be asked to enter
290
the passphrase for this volume.
294
For dm-crypt this is a bit trickier. First you need to register the
295
volumes with <application>device mapper</application> by running:
297
<informalexample><screen>
298
<prompt>#</prompt> <userinput>/etc/init.d/cryptdisks start</userinput>
299
</screen></informalexample>
301
This will scan all volumes mentioned
302
in <filename>/etc/crypttab</filename> and will create appropriate
303
devices under the <filename>/dev</filename> directory after entering
304
the correct passphrases. (Already registered volumes will be skipped,
305
so you can repeat this command several times without worrying.) After
306
successful registration you can simply mount the volumes the usual
309
<informalexample><screen>
310
<prompt>#</prompt> <userinput>mount <replaceable>/mount_point</replaceable></userinput>
311
</screen></informalexample>
316
If the volumes holding noncritical system files could not be mounted
317
(<filename>/usr</filename> or <filename>/var</filename>), the system
318
should still boot and you should be able to mount the volumes manually
319
like in the previous case. However, you will also need to (re)start
320
any services usually running in your default runlevel because it is
321
very likely that they were not started. The easiest way to achieve
322
this is by switching to the first runlevel and back by entering
324
<informalexample><screen>
325
<prompt>#</prompt> <userinput>init 1</userinput>
326
</screen></informalexample>
328
at the shell prompt and pressing <keycombo> <keycap>Control</keycap>
329
<keycap>D</keycap> </keycombo> when asked for the root password.
217
&mount-encrypted.xml;
338
219
<sect1 id="login">
339
220
<title>Log In</title>
357
Documentation accompanying programs you have installed is in
358
<filename>/usr/share/doc/</filename>, under a subdirectory named after
359
the program. For example, the APT User's Guide for using
360
<command>apt</command> to install other programs on your system, is
362
<filename>/usr/share/doc/apt/guide.html/index.html</filename>.
238
Documentation accompanying programs you have installed can be found in
239
<filename>/usr/share/doc/</filename>, under a subdirectory named after the
240
program (or, more precise, the Debian package that contains the program).
241
However, more extensive documentation is often packaged separately in
242
special documentation packages that are mostly not installed by default.
243
For example, documentation about the package management tool
244
<command>apt</command> can be found in the packages
245
<classname>apt-doc</classname> or <classname>apt-howto</classname>.
367
249
In addition, there are some special folders within the
368
250
<filename>/usr/share/doc/</filename> hierarchy. Linux HOWTOs are
369
installed in <emphasis>.gz</emphasis> format, in
251
installed in <emphasis>.gz</emphasis> (compressed) format, in
370
252
<filename>/usr/share/doc/HOWTO/en-txt/</filename>. After installing
371
<command>dhelp</command> you will find a browse-able index of
253
<classname>dhelp</classname>, you will find a browse-able index of
372
254
documentation in <filename>/usr/share/doc/HTML/index.html</filename>.
376
One easy way to view these documents is to <userinput>cd
377
/usr/share/doc/</userinput>, and type <userinput>lynx</userinput>
378
followed by a space and a dot (the dot stands for the current
258
One easy way to view these documents using a text based browser is to
259
enter the following commands:
261
<informalexample><screen>
264
</screen></informalexample>
266
The dot after the <command>w3c</command> command tells it to show the
267
contents of the current directory.
271
If you have a graphical desktop environment installed, you can also use
272
its web browser. Start the web browser from the application menu and
273
enter <userinput>/usr/share/doc/</userinput> in the address bar.
387
281
<userinput>help</userinput> will display help on shell commands. And
388
282
typing a command followed by <userinput>--help</userinput> will
389
283
usually display a short summary of the command's usage. If a command's
390
results scroll past the top of the screen, type <userinput>|
391
more</userinput> after the command to cause the results to pause
392
before scrolling past the top of the screen. To see a list of all
284
results scroll past the top of the screen, type
285
<userinput>| more</userinput> after the command to cause the results
286
to pause before scrolling past the top of the screen. To see a list of all
393
287
commands available which begin with a certain letter, type the letter
394
288
and then two tabs.
396
</para><para condition="not-ubuntu">
398
For a more complete introduction to Debian and GNU/Linux, see
399
<filename>/usr/share/doc/debian-guide/html/noframes/index.html</filename>.
added
removed
en/boot-new/boot-new.xml
