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.
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.
There are two very simple things that you should try first.
If the CD-ROM does not boot, check that it was inserted correctly and that it is not dirty.
If the installer fails to recognize a CD-ROM, try just running the option a second time. Some DMA related issues with older CD-ROM drives are known to be resolved in this way.
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.
If you cannot get the installation working from CD-ROM, try one of the other installation methods that are available.
Some older CD-ROM drives do not support reading from discs that were burned at high speeds using a modern CD writer.
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).
Some older CD-ROM drives do not work correctly if “direct memory access” (DMA) is enabled.
If the CD-ROM fails to boot, try the suggestions listed below.
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.
If you downloaded an iso image, check that the md5sum of that image matches the one listed for the image in the MD5SUMS file that should be present in the same location as where you downloaded the image from.
$ md5sumdebian-testing-i386-netinst.isoa20391b12f7ff22ef705cee4059c6b92debian-testing-i386-netinst.iso
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.
$ dd if=/dev/cdrom | \
> head -c `stat --format=%s debian-testing-i386-netinst.iso` | \
> md5sum
a20391b12f7ff22ef705cee4059c6b92 -
262668+0 records in
262668+0 records out
134486016 bytes (134 MB) copied, 97.474 seconds, 1.4 MB/s
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.
Switch to VT4 or view the contents of /var/log/syslog (use nano as editor) to check for any specific error messages. After that, also check the output of dmesg.
Check in the output of dmesg if your CD-ROM drive was recognized. You should see something like (the lines do not necessarily have to be consecutive):
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
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 modprobe.
Check that there is a device node for your CD-ROM drive under /dev/. In the example above, this would be /dev/hdc. There should also be a /dev/cdrom.
Use the mount command to check if the CD-ROM is already mounted; if not, try mounting it manually:
$ mount /dev/hdc /cdrom
Check if there are any error messages after that command.
Check if DMA is currently enabled:
$ cd /proc/ide/hdc$ grep using_dma settings using_dma 1 0 1 rw
A “1” in the first column after using_dma means it is enabled. If it is, try disabling it:
$ echo -n "using_dma:0" >settings
Make sure that you are in the directory for the device that corresponds to your CD-ROM drive.
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.
如果在開機過程中您遇到了問題或者核心當掉、無法辨識存在的周邊設備或者辨識錯誤，首先要做的事情是檢查開機參數，如同 節 5.3, “開機參數” 之中的內容。
Often, problems can be solved by removing add-ons and peripherals, and then trying booting again. Internal modems, sound cards, and Plug-n-Play devices can be especially problematic.
如果您的機器上裝有多於 512M 的大容量的記憶體，並且安裝程式在啟動核心時當住，您可能需要加入一個開機參數，來限制核心能夠看到的記憶體數量，例如 mem=512m。
傳入某些啟動參數可以解決或避免一些常見的安裝問題。
一些系統的軟碟會有 ``inverted DCLs''。如果您在讀軟碟時遇到錯誤資訊，並且您可以確定軟碟是好的，嘗試參數 floppy=thinkpad。
在一些系統上，例如 IBM PS/1 或者 ValuePoint (具有 ST-506 設備)，IDE 設備可能無法辨識。請首先嘗試沒有參數的開機情況下是否能夠被識別。如果不行，請確定設備的幾何參數 (柱面，磁頭還有磁區)。然後使用參數 hd=。 cylinders,heads,sectors
如果您有一台非常老的機器，並且核心在顯示 Checking 'hlt' instruction... 時中斷，需要嘗試 no-hlt 參數來取消這個測試。
Some systems (especially laptops) that have a native resolution that is not a 4:3 ratio (i.e. not for example 800x600 or 1024x768) may have a blank display after the installer has been booted. In that case adding the boot parameter vga=788[13] may help. If that does not work, try adding the boot parameter fb=false.
If your screen begins to show a weird picture while the kernel boots, eg. pure white, pure black or colored pixel garbage, your system may contain a problematic video card which does not switch to the framebuffer mode properly. Then you can use the boot parameter fb=false to disable the framebuffer console. Only a reduced set of languages will be available during the installation due to limited console features. See 節 5.3, “開機參數” for details.
某些型號的 Dell 筆記型電腦會在 PCMCIA 設備檢測程式嘗試存取一些硬體位址的時候當機。其他筆記型電腦可能顯示類似的問題。如果您遇到那樣的問題，並且在安裝的時候不需要 PCMCIA 的支援，可以用 hw-detect/start_pcmcia=false 啟動參數來取消 PCMCIA 功能。您可以在安裝後，配定 PCMCIA 並且避開可能引起問題的資源範圍。
或者，您可以在啟動安裝程式時進入專家模式。您需要按照要求輸入硬體資源範圍選項。例如，您如果有如上所說的 Dell 筆記型電腦問題，應該在這裡輸入 exclude port 0x800-0x8ff。在 System resource settings section of the PCMCIA HOWTO 處有一個列表，整理出一些有問題的資源範圍選項。注意在安裝程式中，輸入這些值的時候必須忽略逗號。
The kernel normally tries to install USB modules and the USB keyboard driver in order to support some non-standard USB keyboards. However, there are some broken USB systems where the driver hangs on loading. A possible workaround may be disabling the USB controller in your mainboard BIOS setup. Another option is passing the nousb parameter at the boot prompt.
During the boot sequence, you may see many messages in the form can't find , or somethingsomething not presentcan't initialize , or even somethingthis driver release depends on . 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 節 8.6, “編譯新核心”). something
If you get through the initial boot phase but cannot complete the install, the menu option 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.
Other pertinent installation messages may be found in /var/log/ during the installation, and /var/log/installer/ after the computer has been booted into the installed system.
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.
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.
If you have a working Debian system, the easiest way to send an installation report is to install the installation-report and reportbug packages (aptitude install installation-report reportbug), configure reportbug as explained in 節 8.5.2, “Sending E-Mails Outside The System”, and run the command reportbug installation-reports.
Alternatively you can use this template when filling out installation reports, and file the report as a bug report against the installation-reports pseudo package, by sending it to <submit@bugs.debian.org>.
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.>
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.
[13] The parameter vga=788 will activate the VESA framebuffer with a resolution of 800x600. This will probably work, but may not be the optimal resolution for your system. A list of supported resolutions can be obtained by using vga=ask, but you should be aware that list may not be complete.