| 1 |
<!-- retain these comments for translator revision tracking -->
|
| 2 |
<!-- $Id$ -->
|
| 3 |
|
| 4 |
<sect1 id="boot-troubleshooting">
|
| 5 |
<title>Troubleshooting the Installation Process</title>
|
| 6 |
<para>
|
| 7 |
</para>
|
| 8 |
|
| 9 |
<sect2 arch="not-s390" id="unreliable-cd">
|
| 10 |
<title>CD-ROM Reliability</title>
|
| 11 |
<para>
|
| 12 |
|
| 13 |
Sometimes, especially with older CD-ROM drives, the installer may fail
|
| 14 |
to boot from a CD-ROM. The installer may also — even after booting
|
| 15 |
successfully from CD-ROM — fail to recognize the CD-ROM or return
|
| 16 |
errors while reading from it during the installation.
|
| 17 |
|
| 18 |
</para><para>
|
| 19 |
|
| 20 |
There are a many different possible causes for these problems. We can
|
| 21 |
only list some common issues and provide general suggestions on how to
|
| 22 |
deal with them. The rest is up to you.
|
| 23 |
|
| 24 |
</para><para>
|
| 25 |
|
| 26 |
There are two very simple things that you should try first.
|
| 27 |
|
| 28 |
<itemizedlist>
|
| 29 |
<listitem><para>
|
| 30 |
|
| 31 |
If the CD-ROM does not boot, check that it was inserted correctly and that
|
| 32 |
it is not dirty.
|
| 33 |
|
| 34 |
</para></listitem>
|
| 35 |
<listitem><para>
|
| 36 |
|
| 37 |
If the installer fails to recognize a CD-ROM, try just running the option
|
| 38 |
<menuchoice> <guimenuitem>Detect and mount CD-ROM</guimenuitem> </menuchoice>
|
| 39 |
a second time. Some DMA related issues with older CD-ROM drives are known to
|
| 40 |
be resolved in this way.
|
| 41 |
|
| 42 |
</para></listitem>
|
| 43 |
</itemizedlist>
|
| 44 |
|
| 45 |
</para><para>
|
| 46 |
|
| 47 |
If this does not work, then try the suggestions in the subsections below.
|
| 48 |
Most, but not all, suggestions discussed there are valid for both CD-ROM and
|
| 49 |
DVD, but we'll use the term CD-ROM for simplicity.
|
| 50 |
|
| 51 |
</para><para>
|
| 52 |
|
| 53 |
If you cannot get the installation working from CD-ROM, try one of the
|
| 54 |
other installation methods that are available.
|
| 55 |
|
| 56 |
</para>
|
| 57 |
|
| 58 |
<sect3>
|
| 59 |
<title>Common issues</title>
|
| 60 |
|
| 61 |
<itemizedlist>
|
| 62 |
<listitem><para>
|
| 63 |
|
| 64 |
Some older CD-ROM drives do not support reading from discs that were burned
|
| 65 |
at high speeds using a modern CD writer.
|
| 66 |
|
| 67 |
</para></listitem>
|
| 68 |
<listitem><para>
|
| 69 |
|
| 70 |
If your system boots correctly from the CD-ROM, it does not necessarily
|
| 71 |
mean that Linux also supports the CD-ROM (or, more correctly, the controller
|
| 72 |
that your CD-ROM drive is connected to).
|
| 73 |
|
| 74 |
</para></listitem>
|
| 75 |
<listitem><para>
|
| 76 |
|
| 77 |
Some older CD-ROM drives do not work correctly if <quote>direct memory
|
| 78 |
access</quote> (DMA) is enabled.
|
| 79 |
|
| 80 |
</para></listitem>
|
| 81 |
</itemizedlist>
|
| 82 |
|
| 83 |
</sect3>
|
| 84 |
|
| 85 |
<sect3>
|
| 86 |
<title>How to investigate and maybe solve issues</title>
|
| 87 |
<para>
|
| 88 |
|
| 89 |
If the CD-ROM fails to boot, try the suggestions listed below.
|
| 90 |
|
| 91 |
<itemizedlist>
|
| 92 |
<listitem><para>
|
| 93 |
|
| 94 |
Check that your BIOS actually supports booting from CD-ROM (older systems
|
| 95 |
possibly don't) and that your CD-ROM drive supports the media you are using.
|
| 96 |
|
| 97 |
</para></listitem>
|
| 98 |
<listitem><para>
|
| 99 |
|
| 100 |
If you downloaded an iso image, check that the md5sum of that image matches
|
| 101 |
the one listed for the image in the <filename>MD5SUMS</filename> file that
|
| 102 |
should be present in the same location as where you downloaded the image
|
| 103 |
from.
|
| 104 |
|
| 105 |
<informalexample><screen>
|
| 106 |
$ md5sum <replaceable>debian-testing-i386-netinst.iso</replaceable>
|
| 107 |
a20391b12f7ff22ef705cee4059c6b92 <replaceable>debian-testing-i386-netinst.iso</replaceable>
|
| 108 |
</screen></informalexample>
|
| 109 |
|
| 110 |
Next, check that the md5sum of the burned CD-ROM matches as well. The
|
| 111 |
following command should work. It uses the size of the image to read the
|
| 112 |
correct number of bytes from the CD-ROM.
|
| 113 |
|
| 114 |
<informalexample><screen>
|
| 115 |
$ dd if=/dev/cdrom | \
|
| 116 |
> head -c `stat --format=%s <replaceable>debian-testing-i386-netinst.iso</replaceable>` | \
|
| 117 |
> md5sum
|
| 118 |
a20391b12f7ff22ef705cee4059c6b92 -
|
| 119 |
262668+0 records in
|
| 120 |
262668+0 records out
|
| 121 |
134486016 bytes (134 MB) copied, 97.474 seconds, 1.4 MB/s
|
| 122 |
</screen></informalexample>
|
| 123 |
|
| 124 |
</para></listitem>
|
| 125 |
</itemizedlist>
|
| 126 |
|
| 127 |
</para><para>
|
| 128 |
|
| 129 |
If, after the installer has been booted successfully, the CD-ROM is not
|
| 130 |
detected, sometimes simply trying again may solve the problem. If you have
|
| 131 |
more than one CD-ROM drive, try changing the CD-ROM to the other drive.
|
| 132 |
If that does not work or if the CD-ROM is recognized but there are errors
|
| 133 |
when reading from it, try the suggestions listed below. Some basic knowledge
|
| 134 |
of Linux is required for this.
|
| 135 |
To execute any of the commands, you should first switch to the second
|
| 136 |
virtual console (VT2) and activate the shell there.
|
| 137 |
|
| 138 |
<itemizedlist>
|
| 139 |
<listitem><para>
|
| 140 |
|
| 141 |
Switch to VT4 or view the contents of <filename>/var/log/syslog</filename>
|
| 142 |
(use <command>nano</command> as editor) to check for any specific error
|
| 143 |
messages. After that, also check the output of <command>dmesg</command>.
|
| 144 |
|
| 145 |
</para></listitem>
|
| 146 |
<listitem><para>
|
| 147 |
|
| 148 |
Check in the output of <command>dmesg</command> if your CD-ROM drive was
|
| 149 |
recognized. You should see something like (the lines do not necessarily
|
| 150 |
have to be consecutive):
|
| 151 |
|
| 152 |
<informalexample><screen>
|
| 153 |
Probing IDE interface ide1...
|
| 154 |
hdc: TOSHIBA DVD-ROM SD-R6112, ATAPI CD/DVD-ROM drive
|
| 155 |
ide1 at 0x170-0x177,0x376 on irq 15
|
| 156 |
hdc: ATAPI 24X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33)
|
| 157 |
Uniform CD-ROM driver Revision: 3.20
|
| 158 |
</screen></informalexample>
|
| 159 |
|
| 160 |
If you don't see something like that, chances are the controller your CD-ROM
|
| 161 |
is connected to was not recognized or may be not supported at all. If you
|
| 162 |
know what driver is needed for the controller, you can try loading it manually
|
| 163 |
using <command>modprobe</command>.
|
| 164 |
|
| 165 |
</para></listitem>
|
| 166 |
<listitem><para>
|
| 167 |
|
| 168 |
Check that there is a device node for your CD-ROM drive under
|
| 169 |
<filename>/dev/</filename>. In the example above, this would be
|
| 170 |
<filename>/dev/hdc</filename>.
|
| 171 |
There should also be a <filename>/dev/cdroms/cdrom0</filename>.
|
| 172 |
|
| 173 |
</para></listitem>
|
| 174 |
<listitem><para>
|
| 175 |
|
| 176 |
Use the <command>mount</command> command to check if the CD-ROM is already
|
| 177 |
mounted; if not, try mounting it manually:
|
| 178 |
|
| 179 |
<informalexample><screen>
|
| 180 |
$ mount /dev/<replaceable>hdc</replaceable> /cdrom
|
| 181 |
</screen></informalexample>
|
| 182 |
|
| 183 |
Check if there are any error messages after that command.
|
| 184 |
|
| 185 |
</para></listitem>
|
| 186 |
<listitem><para>
|
| 187 |
|
| 188 |
Check if DMA is currently enabled:
|
| 189 |
|
| 190 |
<informalexample><screen>
|
| 191 |
$ cd /proc/<replaceable>ide</replaceable>/<replaceable>hdc</replaceable>
|
| 192 |
$ grep using_dma settings
|
| 193 |
using_dma 1 0 1 rw
|
| 194 |
</screen></informalexample>
|
| 195 |
|
| 196 |
A <quote>1</quote> in the first column after <literal>using_dma</literal>
|
| 197 |
means it is enabled. If it is, try disabling it:
|
| 198 |
|
| 199 |
<informalexample><screen>
|
| 200 |
$ echo -n "using_dma:0" >settings
|
| 201 |
</screen></informalexample>
|
| 202 |
|
| 203 |
Make sure that you are in the directory for the device that corresponds
|
| 204 |
to your CD-ROM drive.
|
| 205 |
|
| 206 |
</para></listitem>
|
| 207 |
<listitem><para>
|
| 208 |
|
| 209 |
If there are any problems during the installation, try checking the integrity
|
| 210 |
of the CD-ROM using the option near the bottom of the installer's main menu.
|
| 211 |
This option can also be used as a general test if the CD-ROM can be read
|
| 212 |
reliably.
|
| 213 |
|
| 214 |
</para></listitem>
|
| 215 |
</itemizedlist>
|
| 216 |
|
| 217 |
</para>
|
| 218 |
</sect3>
|
| 219 |
</sect2>
|
| 220 |
|
| 221 |
<sect2 condition="supports-floppy-boot" id="unreliable-floppies">
|
| 222 |
<title>Floppy Disk Reliability</title>
|
| 223 |
|
| 224 |
<para>
|
| 225 |
|
| 226 |
The biggest problem for people using floppy disks to install Debian
|
| 227 |
seems to be floppy disk reliability.
|
| 228 |
|
| 229 |
</para><para>
|
| 230 |
|
| 231 |
The boot floppy is the floppy with the worst problems, because it
|
| 232 |
is read by the hardware directly, before Linux boots. Often, the
|
| 233 |
hardware doesn't read as reliably as the Linux floppy disk driver, and
|
| 234 |
may just stop without printing an error message if it reads incorrect
|
| 235 |
data. There can also be failures in the driver floppies, most of which
|
| 236 |
indicate themselves with a flood of messages about disk I/O errors.
|
| 237 |
|
| 238 |
</para><para>
|
| 239 |
|
| 240 |
If you are having the installation stall at a particular floppy, the first
|
| 241 |
thing you should do is write the image to a <emphasis>different</emphasis>
|
| 242 |
floppy and see if that solves the problem. Simply reformatting the old
|
| 243 |
floppy may not be sufficient, even if it appears that the floppy was
|
| 244 |
reformatted and written with no errors. It is sometimes useful to try
|
| 245 |
writing the floppy on a different system.
|
| 246 |
|
| 247 |
</para><para>
|
| 248 |
|
| 249 |
One user reports he had to write the images to floppy
|
| 250 |
<emphasis>three</emphasis> times before one worked, and then
|
| 251 |
everything was fine with the third floppy.
|
| 252 |
|
| 253 |
</para><para>
|
| 254 |
|
| 255 |
Normally you should not have to download a floppy image again, but if you
|
| 256 |
are experiencing problems it is always useful to verify that the images
|
| 257 |
were downloaded correctly by verifying their md5sums.
|
| 258 |
|
| 259 |
</para><para>
|
| 260 |
|
| 261 |
Other users have reported that simply rebooting a few times with the
|
| 262 |
same floppy in the floppy drive can lead to a successful boot. This is
|
| 263 |
all due to buggy hardware or firmware floppy drivers.
|
| 264 |
|
| 265 |
</para>
|
| 266 |
</sect2>
|
| 267 |
|
| 268 |
<sect2><title>Boot Configuration</title>
|
| 269 |
|
| 270 |
<para>
|
| 271 |
|
| 272 |
If you have problems and the kernel hangs during the boot process,
|
| 273 |
doesn't recognize peripherals you actually have, or drives are not
|
| 274 |
recognized properly, the first thing to check is the boot parameters,
|
| 275 |
as discussed in <xref linkend="boot-parms"/>.
|
| 276 |
|
| 277 |
</para><para>
|
| 278 |
|
| 279 |
Often, problems can be solved by removing add-ons and peripherals, and
|
| 280 |
then trying booting again. <phrase arch="x86">Internal modems, sound
|
| 281 |
cards, and Plug-n-Play devices can be especially problematic.</phrase>
|
| 282 |
|
| 283 |
</para><para>
|
| 284 |
|
| 285 |
If you have a large amount of memory installed in your machine, more
|
| 286 |
than 512M, and the installer hangs when booting the kernel, you may
|
| 287 |
need to include a boot argument to limit the amount of memory the
|
| 288 |
kernel sees, such as <userinput>mem=512m</userinput>.
|
| 289 |
|
| 290 |
</para>
|
| 291 |
</sect2>
|
| 292 |
|
| 293 |
<sect2 arch="x86" id="i386-boot-problems">
|
| 294 |
<title>Common &arch-title; Installation Problems</title>
|
| 295 |
<para>
|
| 296 |
|
| 297 |
There are some common installation problems that can be solved or avoided by
|
| 298 |
passing certain boot parameters to the installer.
|
| 299 |
|
| 300 |
</para><para>
|
| 301 |
|
| 302 |
Some systems have floppies with <quote>inverted DCLs</quote>. If you receive
|
| 303 |
errors reading from the floppy, even when you know the floppy is good,
|
| 304 |
try the parameter <userinput>floppy=thinkpad</userinput>.
|
| 305 |
|
| 306 |
</para><para>
|
| 307 |
|
| 308 |
On some systems, such as the IBM PS/1 or ValuePoint (which have ST-506
|
| 309 |
disk drivers), the IDE drive may not be properly recognized. Again,
|
| 310 |
try it first without the parameters and see if the IDE drive is
|
| 311 |
recognized properly. If not, determine your drive geometry
|
| 312 |
(cylinders, heads, and sectors), and use the parameter
|
| 313 |
<userinput>hd=<replaceable>cylinders</replaceable>,<replaceable>heads</replaceable>,<replaceable>sectors</replaceable></userinput>.
|
| 314 |
|
| 315 |
</para><para>
|
| 316 |
|
| 317 |
If you have a very old machine, and the kernel hangs after saying
|
| 318 |
<computeroutput>Checking 'hlt' instruction...</computeroutput>, then
|
| 319 |
you should try the <userinput>no-hlt</userinput> boot argument, which
|
| 320 |
disables this test.
|
| 321 |
|
| 322 |
</para><para>
|
| 323 |
|
| 324 |
If your screen begins to show a weird picture while the kernel boots,
|
| 325 |
eg. pure white, pure black or colored pixel garbage, your system may
|
| 326 |
contain a problematic video card which does not switch to the
|
| 327 |
framebuffer mode properly. Then you can use the boot parameter
|
| 328 |
<userinput>fb=false video=vga16:off</userinput> to disable the framebuffer
|
| 329 |
console. Only a reduced set of
|
| 330 |
languages will be available during the installation due to limited
|
| 331 |
console features. See <xref linkend="boot-parms"/> for details.
|
| 332 |
|
| 333 |
</para>
|
| 334 |
|
| 335 |
<sect3>
|
| 336 |
<title>System Freeze During the PCMCIA Configuration Phase</title>
|
| 337 |
<para>
|
| 338 |
|
| 339 |
Some laptop models produced by Dell are known to crash when PCMCIA device
|
| 340 |
detection tries to access some hardware addresses. Other laptops may display
|
| 341 |
similar problems. If you experience such a problem and you don't need PCMCIA
|
| 342 |
support during the installation, you can disable PCMCIA using the
|
| 343 |
<userinput>hw-detect/start_pcmcia=false</userinput> boot parameter. You can
|
| 344 |
then configure PCMCIA after the installation is completed and exclude the
|
| 345 |
resource range causing the problems.
|
| 346 |
|
| 347 |
</para><para>
|
| 348 |
|
| 349 |
Alternatively, you can boot the installer in expert mode. You will
|
| 350 |
then be asked to enter the resource range options your hardware
|
| 351 |
needs. For example, if you have one of the Dell laptops mentioned
|
| 352 |
above, you should enter <userinput>exclude port
|
| 353 |
0x800-0x8ff</userinput> here. There is also a list of some common
|
| 354 |
resource range options in the <ulink
|
| 355 |
url="http://pcmcia-cs.sourceforge.net/ftp/doc/PCMCIA-HOWTO-1.html#ss1.12">System
|
| 356 |
resource settings section of the PCMCIA HOWTO</ulink>. Note that you
|
| 357 |
have to omit the commas, if any, when you enter this value in the
|
| 358 |
installer.
|
| 359 |
|
| 360 |
</para>
|
| 361 |
</sect3>
|
| 362 |
|
| 363 |
<sect3>
|
| 364 |
<title>System Freeze while Loading USB Modules</title>
|
| 365 |
<para>
|
| 366 |
|
| 367 |
The kernel normally tries to install USB modules and the USB keyboard driver
|
| 368 |
in order to support some non-standard USB keyboards. However, there are some
|
| 369 |
broken USB systems where the driver hangs on loading. A possible workaround
|
| 370 |
may be disabling the USB controller in your mainboard BIOS setup. Another option
|
| 371 |
is passing the <userinput>nousb</userinput> parameter at the boot prompt.
|
| 372 |
|
| 373 |
</para>
|
| 374 |
</sect3>
|
| 375 |
</sect2>
|
| 376 |
|
| 377 |
<sect2 arch="sparc" id="sparc-boot-problems">
|
| 378 |
<title>Common &arch-title; Installation Problems</title>
|
| 379 |
<para>
|
| 380 |
|
| 381 |
There are some common installation problems that are worth mentioning.
|
| 382 |
|
| 383 |
</para>
|
| 384 |
<sect3>
|
| 385 |
<title>Misdirected video output</title>
|
| 386 |
<para>
|
| 387 |
|
| 388 |
It is fairly common for &arch-title; to have two video cards in one machine,
|
| 389 |
for example an ATI card and a Sun Creator 3D. In some cases, this may result
|
| 390 |
in the video output getting misdirected soon after the system boots. In
|
| 391 |
typical cases, the display will only show:
|
| 392 |
|
| 393 |
<informalexample><screen>
|
| 394 |
Remapping the kernel... done
|
| 395 |
Booting Linux...
|
| 396 |
</screen></informalexample>
|
| 397 |
|
| 398 |
To work around this, you can either pull out one of the video cards, or
|
| 399 |
disable the one not used during the OpenProm boot phase using a kernel
|
| 400 |
parameter. For example, to disable an ATI card, you should boot the
|
| 401 |
installer with <userinput>video=atyfb:off</userinput>.
|
| 402 |
|
| 403 |
</para><para>
|
| 404 |
|
| 405 |
Note that you may also have to manually add this parameter to the silo
|
| 406 |
configuration (edit <filename>/target/etc/silo.conf</filename> before
|
| 407 |
rebooting) and, if you installed X11, modify the video driver in
|
| 408 |
<filename>/etc/X11/xorg.conf</filename>.
|
| 409 |
|
| 410 |
</para>
|
| 411 |
</sect3>
|
| 412 |
|
| 413 |
<sect3>
|
| 414 |
<title>Failure to Boot or Install from CD-ROM</title>
|
| 415 |
<para>
|
| 416 |
|
| 417 |
Some Sparc systems are notoriously difficult to boot from CD-ROM and
|
| 418 |
even if they do boot, there may be inexplicable failures during the
|
| 419 |
installation. Most problems have been reported with SunBlade systems.
|
| 420 |
|
| 421 |
</para><para>
|
| 422 |
|
| 423 |
We recommend to install such systems by netbooting the installer.
|
| 424 |
|
| 425 |
</para>
|
| 426 |
</sect3>
|
| 427 |
</sect2>
|
| 428 |
|
| 429 |
<sect2 id="kernel-msgs">
|
| 430 |
<title>Interpreting the Kernel Startup Messages</title>
|
| 431 |
|
| 432 |
<para>
|
| 433 |
|
| 434 |
During the boot sequence, you may see many messages in the form
|
| 435 |
<computeroutput>can't find <replaceable>something</replaceable></computeroutput>,
|
| 436 |
or <computeroutput><replaceable>something</replaceable>
|
| 437 |
not present</computeroutput>, <computeroutput>can't initialize
|
| 438 |
<replaceable>something</replaceable></computeroutput>,
|
| 439 |
or even <computeroutput>this driver release depends
|
| 440 |
on <replaceable>something</replaceable></computeroutput>.
|
| 441 |
Most of these messages are harmless. You
|
| 442 |
see them because the kernel for the installation system is built to
|
| 443 |
run on computers with many different peripheral devices. Obviously, no
|
| 444 |
one computer will have every possible peripheral device, so the
|
| 445 |
operating system may emit a few complaints while it looks for
|
| 446 |
peripherals you don't own. You may also see the system pause for a
|
| 447 |
while. This happens when it is waiting for a device to respond, and
|
| 448 |
that device is not present on your system. If you find the time it
|
| 449 |
takes to boot the system unacceptably long, you can create a
|
| 450 |
custom kernel later (see <xref linkend="kernel-baking"/>).
|
| 451 |
|
| 452 |
</para>
|
| 453 |
</sect2>
|
| 454 |
|
| 455 |
|
| 456 |
<sect2 id="problem-report">
|
| 457 |
<title>Reporting Installation Problems</title>
|
| 458 |
<para>
|
| 459 |
|
| 460 |
If you get through the initial boot phase but cannot complete the install,
|
| 461 |
the menu option <guimenuitem>Save debug logs</guimenuitem> may be helpful.
|
| 462 |
It lets you store system error logs and configuration information from the
|
| 463 |
installer to a floppy, or download them using a web browser.
|
| 464 |
|
| 465 |
This information may provide clues as to what went wrong and how to
|
| 466 |
fix it. If you are submitting a bug report, you may want to attach
|
| 467 |
this information to the bug report.
|
| 468 |
|
| 469 |
</para><para>
|
| 470 |
|
| 471 |
Other pertinent installation messages may be found in
|
| 472 |
<filename>/var/log/</filename> during the
|
| 473 |
installation, and <filename>/var/log/installer/</filename>
|
| 474 |
after the computer has been booted into the installed system.
|
| 475 |
|
| 476 |
</para>
|
| 477 |
</sect2>
|
| 478 |
|
| 479 |
<sect2 id="submit-bug">
|
| 480 |
<title>Submitting Installation Reports</title>
|
| 481 |
<para>
|
| 482 |
|
| 483 |
If you still have problems, please submit an installation report. We also
|
| 484 |
encourage installation reports to be sent even if the installation is
|
| 485 |
successful, so that we can get as much information as possible on the largest
|
| 486 |
number of hardware configurations.
|
| 487 |
|
| 488 |
</para><para>
|
| 489 |
|
| 490 |
Note that your installation report will be published in the Debian Bug
|
| 491 |
Tracking System (BTS) and forwarded to a public mailing list. Make sure that
|
| 492 |
you use an e-mail address that you do not mind being made public.
|
| 493 |
|
| 494 |
</para><para>
|
| 495 |
|
| 496 |
If you have a working Debian system, the easiest way to send an installation
|
| 497 |
report is to install the <classname>installation-report</classname> and
|
| 498 |
<classname>reportbug</classname> packages
|
| 499 |
(<command>aptitude install installation-report reportbug</command>),
|
| 500 |
configure <classname>reportbug</classname> as explained in
|
| 501 |
<xref linkend="mail-outgoing"/>, and run the command <command>reportbug
|
| 502 |
installation-reports</command>.
|
| 503 |
|
| 504 |
</para><para>
|
| 505 |
|
| 506 |
Alternatively you can use this template when filling out
|
| 507 |
installation reports, and file the report as a bug report against the
|
| 508 |
<classname>installation-reports</classname> pseudo package, by sending it to
|
| 509 |
<email>submit@bugs.debian.org</email>.
|
| 510 |
|
| 511 |
<informalexample><screen>
|
| 512 |
Package: installation-reports
|
| 513 |
|
| 514 |
Boot method: <How did you boot the installer? CD? floppy? network?>
|
| 515 |
Image version: <Full URL to image you downloaded is best>
|
| 516 |
Date: <Date and time of the install>
|
| 517 |
|
| 518 |
Machine: <Description of machine (eg, IBM Thinkpad R32)>
|
| 519 |
Processor:
|
| 520 |
Memory:
|
| 521 |
Partitions: <df -Tl will do; the raw partition table is preferred>
|
| 522 |
|
| 523 |
Output of lspci -nn and lspci -vnn:
|
| 524 |
|
| 525 |
Base System Installation Checklist:
|
| 526 |
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
|
| 527 |
|
| 528 |
Initial boot: [ ]
|
| 529 |
Detect network card: [ ]
|
| 530 |
Configure network: [ ]
|
| 531 |
Detect CD: [ ]
|
| 532 |
Load installer modules: [ ]
|
| 533 |
Detect hard drives: [ ]
|
| 534 |
Partition hard drives: [ ]
|
| 535 |
Install base system: [ ]
|
| 536 |
Clock/timezone setup: [ ]
|
| 537 |
User/password setup: [ ]
|
| 538 |
Install tasks: [ ]
|
| 539 |
Install boot loader: [ ]
|
| 540 |
Overall install: [ ]
|
| 541 |
|
| 542 |
Comments/Problems:
|
| 543 |
|
| 544 |
<Description of the install, in prose, and any thoughts, comments
|
| 545 |
and ideas you had during the initial install.>
|
| 546 |
</screen></informalexample>
|
| 547 |
|
| 548 |
In the bug report, describe what the problem is, including the last
|
| 549 |
visible kernel messages in the event of a kernel hang. Describe the
|
| 550 |
steps that you did which brought the system into the problem state.
|
| 551 |
|
| 552 |
</para>
|
| 553 |
</sect2>
|
| 554 |
</sect1>
|
Parent Directory
| 
Revision Log