/usr/share/doc/installation-guide-armel/en/ch05s04.html is in installation-guide-armel 20100518ubuntu6.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 | <html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>5.4. Troubleshooting the Installation Process</title>
<link rel="stylesheet" type="text/css" href="install.css">
<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
<link rel="home" href="index.html" title="Ubuntu Installation Guide">
<link rel="up" href="ch05.html" title="Chapter 5. Booting the Installation System">
<link rel="prev" href="ch05s03.html" title="5.3. Boot Parameters">
<link rel="next" href="ch06.html" title="Chapter 6. Using the Ubuntu Installer">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
<div class="navheader">
<table width="100%" summary="Navigation header">
<tr><th colspan="3" align="center">5.4. Troubleshooting the Installation Process</th></tr>
<tr>
<td width="20%" align="left">
<a accesskey="p" href="ch05s03.html">Prev</a> </td>
<th width="60%" align="center">Chapter 5. Booting the Installation System</th>
<td width="20%" align="right"> <a accesskey="n" href="ch06.html">Next</a>
</td>
</tr>
</table>
<hr>
</div>
<div class="sect1" title="5.4. Troubleshooting the Installation Process">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
<a name="boot-troubleshooting"></a>5.4. Troubleshooting the Installation Process</h2></div></div></div>
<p>
</p>
<div class="sect2" title="5.4.1. CD-ROM Reliability">
<div class="titlepage"><div><div><h3 class="title">
<a name="unreliable-cd"></a>5.4.1. CD-ROM Reliability</h3></div></div></div>
<p>
Sometimes, especially with older CD-ROM drives, the installer may fail
to boot from a CD-ROM. The installer may also — even after booting
successfully from CD-ROM — fail to recognize the CD-ROM or return
errors while reading from it during the installation.
</p>
<p>
There are many different possible causes for these problems. We can
only list some common issues and provide general suggestions on how to
deal with them. The rest is up to you.
</p>
<p>
There are two very simple things that you should try first.
</p>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem"><p>
If the CD-ROM does not boot, check that it was inserted correctly and that
it is not dirty.
</p></li>
<li class="listitem"><p>
If the installer fails to recognize a CD-ROM, try just running the option
<span class="guimenuitem">Detect and mount CD-ROM</span>
a second time. Some DMA related issues with older CD-ROM drives are known to
be resolved in this way.
</p></li>
</ul></div>
<p>
</p>
<p>
If this does not work, then try the suggestions in the subsections below.
Most, but not all, suggestions discussed there are valid for both CD-ROM and
DVD, but we'll use the term CD-ROM for simplicity.
</p>
<p>
If you cannot get the installation working from CD-ROM, try one of the
other installation methods that are available.
</p>
<div class="sect3" title="5.4.1.1. Common issues">
<div class="titlepage"><div><div><h4 class="title">
<a name="idp3469208"></a>5.4.1.1. Common issues</h4></div></div></div>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem"><p>
Some older CD-ROM drives do not support reading from discs that were burned
at high speeds using a modern CD writer.
</p></li>
<li class="listitem"><p>
If your system boots correctly from the CD-ROM, it does not necessarily
mean that Linux also supports the CD-ROM (or, more correctly, the controller
that your CD-ROM drive is connected to).
</p></li>
<li class="listitem"><p>
Some older CD-ROM drives do not work correctly if <span class="quote">“<span class="quote">direct memory
access</span>”</span> (DMA) is enabled.
</p></li>
</ul></div>
</div>
<div class="sect3" title="5.4.1.2. How to investigate and maybe solve issues">
<div class="titlepage"><div><div><h4 class="title">
<a name="idp3471144"></a>5.4.1.2. How to investigate and maybe solve issues</h4></div></div></div>
<p>
If the CD-ROM fails to boot, try the suggestions listed below.
</p>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem"><p>
Check that your BIOS actually supports booting from CD-ROM (older systems
possibly don't) and that your CD-ROM drive supports the media you are using.
</p></li>
<li class="listitem">
<p>
If you downloaded an iso image, check that the md5sum of that image matches
the one listed for the image in the <code class="filename">MD5SUMS</code> file that
should be present in the same location as where you downloaded the image
from.
</p>
<div class="informalexample"><pre class="screen">
$ md5sum <em class="replaceable"><code>debian-testing-i386-netinst.iso</code></em>
a20391b12f7ff22ef705cee4059c6b92 <em class="replaceable"><code>debian-testing-i386-netinst.iso</code></em>
</pre></div>
<p>
Next, check that the md5sum of the burned CD-ROM matches as well. The
following command should work. It uses the size of the image to read the
correct number of bytes from the CD-ROM.
</p>
<div class="informalexample"><pre class="screen">
$ dd if=/dev/cdrom | \
> head -c `stat --format=%s <em class="replaceable"><code>debian-testing-i386-netinst.iso</code></em>` | \
> md5sum
a20391b12f7ff22ef705cee4059c6b92 -
262668+0 records in
262668+0 records out
134486016 bytes (134 MB) copied, 97.474 seconds, 1.4 MB/s
</pre></div>
<p>
</p>
</li>
</ul></div>
<p>
</p>
<p>
If, after the installer has been booted successfully, the CD-ROM is not
detected, sometimes simply trying again may solve the problem. If you have
more than one CD-ROM drive, try changing the CD-ROM to the other drive.
If that does not work or if the CD-ROM is recognized but there are errors
when reading from it, try the suggestions listed below. Some basic knowledge
of Linux is required for this.
To execute any of the commands, you should first switch to the second
virtual console (VT2) and activate the shell there.
</p>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem"><p>
Switch to VT4 or view the contents of <code class="filename">/var/log/syslog</code>
(use <span class="command"><strong>nano</strong></span> as editor) to check for any specific error
messages. After that, also check the output of <span class="command"><strong>dmesg</strong></span>.
</p></li>
<li class="listitem">
<p>
Check in the output of <span class="command"><strong>dmesg</strong></span> if your CD-ROM drive was
recognized. You should see something like (the lines do not necessarily
have to be consecutive):
</p>
<div class="informalexample"><pre class="screen">
Probing IDE interface ide1...
hdc: TOSHIBA DVD-ROM SD-R6112, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
hdc: ATAPI 24X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.20
</pre></div>
<p>
If you don't see something like that, chances are the controller your CD-ROM
is connected to was not recognized or may be not supported at all. If you
know what driver is needed for the controller, you can try loading it manually
using <span class="command"><strong>modprobe</strong></span>.
</p>
</li>
<li class="listitem"><p>
Check that there is a device node for your CD-ROM drive under
<code class="filename">/dev/</code>. In the example above, this would be
<code class="filename">/dev/hdc</code>.
There should also be a <code class="filename">/dev/cdrom</code>.
</p></li>
<li class="listitem">
<p>
Use the <span class="command"><strong>mount</strong></span> command to check if the CD-ROM is already
mounted; if not, try mounting it manually:
</p>
<div class="informalexample"><pre class="screen">
$ mount /dev/<em class="replaceable"><code>hdc</code></em> /cdrom
</pre></div>
<p>
Check if there are any error messages after that command.
</p>
</li>
<li class="listitem">
<p>
Check if DMA is currently enabled:
</p>
<div class="informalexample"><pre class="screen">
$ cd /proc/<em class="replaceable"><code>ide</code></em>/<em class="replaceable"><code>hdc</code></em>
$ grep using_dma settings
using_dma 1 0 1 rw
</pre></div>
<p>
A <span class="quote">“<span class="quote">1</span>”</span> in the first column after <code class="literal">using_dma</code>
means it is enabled. If it is, try disabling it:
</p>
<div class="informalexample"><pre class="screen">
$ echo -n "using_dma:0" >settings
</pre></div>
<p>
Make sure that you are in the directory for the device that corresponds
to your CD-ROM drive.
</p>
</li>
<li class="listitem"><p>
If there are any problems during the installation, try checking the integrity
of the CD-ROM using the option near the bottom of the installer's main menu.
This option can also be used as a general test if the CD-ROM can be read
reliably.
</p></li>
</ul></div>
<p>
</p>
</div>
</div>
<div class="sect2" title="5.4.2. Boot Configuration">
<div class="titlepage"><div><div><h3 class="title">
<a name="idp3484912"></a>5.4.2. Boot Configuration</h3></div></div></div>
<p>
If you have problems and the kernel hangs during the boot process,
doesn't recognize peripherals you actually have, or drives are not
recognized properly, the first thing to check is the boot parameters,
as discussed in <a class="xref" href="ch05s03.html" title="5.3. Boot Parameters">Section 5.3, “Boot Parameters”</a>.
</p>
<p>
Often, problems can be solved by removing add-ons and peripherals, and
then trying booting again.
</p>
<p>
If you have a large amount of memory installed in your machine, more
than 512M, and the installer hangs when booting the kernel, you may
need to include a boot argument to limit the amount of memory the
kernel sees, such as <strong class="userinput"><code>mem=512m</code></strong>.
</p>
</div>
<div class="sect2" title="5.4.3. Interpreting the Kernel Startup Messages">
<div class="titlepage"><div><div><h3 class="title">
<a name="kernel-msgs"></a>5.4.3. Interpreting the Kernel Startup Messages</h3></div></div></div>
<p>
During the boot sequence, you may see many messages in the form
<code class="computeroutput">can't find <em class="replaceable"><code>something</code></em></code>,
or <code class="computeroutput"><em class="replaceable"><code>something</code></em>
not present</code>, <code class="computeroutput">can't initialize
<em class="replaceable"><code>something</code></em></code>,
or even <code class="computeroutput">this driver release depends
on <em class="replaceable"><code>something</code></em></code>.
Most of these messages are harmless. You
see them because the kernel for the installation system is built to
run on computers with many different peripheral devices. Obviously, no
one computer will have every possible peripheral device, so the
operating system may emit a few complaints while it looks for
peripherals you don't own. You may also see the system pause for a
while. This happens when it is waiting for a device to respond, and
that device is not present on your system. If you find the time it
takes to boot the system unacceptably long, you can create a
custom kernel later (see <a class="xref" href="ch08s06.html" title="8.6. Compiling a New Kernel">Section 8.6, “Compiling a New Kernel”</a>).
</p>
</div>
<div class="sect2" title="5.4.4. Reporting Installation Problems">
<div class="titlepage"><div><div><h3 class="title">
<a name="problem-report"></a>5.4.4. Reporting Installation Problems</h3></div></div></div>
<p>
If you get through the initial boot phase but cannot complete the install,
the menu option <span class="guimenuitem">Save debug logs</span> may be helpful.
It lets you store system error logs and configuration information from the
installer to a floppy, or download them using a web browser.
This information may provide clues as to what went wrong and how to
fix it. If you are submitting a bug report, you may want to attach
this information to the bug report.
</p>
<p>
Other pertinent installation messages may be found in
<code class="filename">/var/log/</code> during the
installation, and <code class="filename">/var/log/installer/</code>
after the computer has been booted into the installed system.
</p>
</div>
<div class="sect2" title="5.4.5. Submitting Installation Reports">
<div class="titlepage"><div><div><h3 class="title">
<a name="submit-bug"></a>5.4.5. Submitting Installation Reports</h3></div></div></div>
<p>
If you still have problems, please submit an installation report. We also
encourage installation reports to be sent even if the installation is
successful, so that we can get as much information as possible on the largest
number of hardware configurations.
</p>
<p>
Note that your installation report will be published in the Debian Bug
Tracking System (BTS) and forwarded to a public mailing list. Make sure that
you use an e-mail address that you do not mind being made public.
</p>
<p>
If you have a working Ubuntu system, the easiest way to send an installation
report is to install the <code class="classname">installation-report</code> and
<code class="classname">reportbug</code> packages
(<span class="command"><strong>aptitude install installation-report reportbug</strong></span>),
configure <code class="classname">reportbug</code> as explained in
<a class="xref" href="ch08s05.html#mail-outgoing" title="8.5.2. Sending E-Mails Outside The System">Section 8.5.2, “Sending E-Mails Outside The System”</a>, and run the command <span class="command"><strong>reportbug
installation-reports</strong></span>.
</p>
<p>
Alternatively you can use this template when filling out
installation reports, and send the report to
<code class="email"><<a class="email" href="mailto:ubuntu-users@lists.ubuntu.com">ubuntu-users@lists.ubuntu.com</a>></code>.
</p>
<div class="informalexample"><pre class="screen">
Package: installation-reports
Boot method: <How did you boot the installer? CD? floppy? network?>
Image version: <Full URL to image you downloaded is best>
Date: <Date and time of the install>
Machine: <Description of machine (eg, IBM Thinkpad R32)>
Processor:
Memory:
Partitions: <df -Tl will do; the raw partition table is preferred>
Output of lspci -knn (or lspci -nn):
Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Initial boot: [ ]
Detect network card: [ ]
Configure network: [ ]
Detect CD: [ ]
Load installer modules: [ ]
Detect hard drives: [ ]
Partition hard drives: [ ]
Install base system: [ ]
Clock/timezone setup: [ ]
User/password setup: [ ]
Install tasks: [ ]
Install boot loader: [ ]
Overall install: [ ]
Comments/Problems:
<Description of the install, in prose, and any thoughts, comments
and ideas you had during the initial install.>
</pre></div>
<p>
In the bug report, describe what the problem is, including the last
visible kernel messages in the event of a kernel hang. Describe the
steps that you did which brought the system into the problem state.
</p>
</div>
</div>
<div class="navfooter">
<hr>
<table width="100%" summary="Navigation footer">
<tr>
<td width="40%" align="left">
<a accesskey="p" href="ch05s03.html">Prev</a> </td>
<td width="20%" align="center"><a accesskey="u" href="ch05.html">Up</a></td>
<td width="40%" align="right"> <a accesskey="n" href="ch06.html">Next</a>
</td>
</tr>
<tr>
<td width="40%" align="left" valign="top">5.3. Boot Parameters </td>
<td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td>
<td width="40%" align="right" valign="top"> Chapter 6. Using the Ubuntu Installer</td>
</tr>
</table>
</div>
</body>
</html>
|