| 5.4. Fejlsøgning af installationsprocessen | ||
|---|---|---|
 |
Kapitel 5. Opstart af installationssystemet | 
|
| 5.4. Fejlsøgning af installationsprocessen | ||
|---|---|---|
|
|
Kapitel 5. Opstart af installationssystemet |
|
Sometimes, especially with older drives, the installer may fail to boot from an optical disc. The installer may also — even after booting successfully from such disc — fail to recognize the disc or return errors while reading from it during the installation.
Der er mangle forskellige mulige årsager for disse problemer. Vi kan kun vise nogle gængse problemstillinger og tilbyde generelle forslag til hvordan du håndterer dem. Resten er op til dig.
Der er to meget simple metoder, du bør prøve først.
If the disc does not boot, check that it was inserted correctly and that it is not dirty.
If the installer fails to recognize the disc, try just running the option a second time. Some DMA related issues with very old 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 CD-ROM and DVD.
If you cannot get the installation working from optical disc, try one of the other installation methods that are available.
Nogle ældre cd-rom-drev understøtter ikke læsning fra diske som blev brændt med høje hastigheder via et moderne cd-rom-drev.
Nogle meget gamle cd-rom-drev virker ikke korrekt hvis “direct memory access” (DMA) er aktiveret for dem.
If the optical disc fails to boot, try the suggestions listed below.
Check that your BIOS actually supports booting from optical disc (only an issue for very old systems) and that booting from such media is enabled in the BIOS.
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 disc matches as well. The following command should work. It uses the size of the image to read the correct number of bytes from the disc.
> head -c `stat --format=%s debian-testing-i386-netinst.iso` | \
> md5sum
a20391b12f7ff22ef705cee4059c6b92 -
262668+0 poster ind
262668+0 poster ud
134486016 byte (134 MB) kopieret, 97,474 sekunder, 1,4 MB/s
If, after the installer has been booted successfully, the disc is not detected, sometimes simply trying again may solve the problem. If you have more than one optical drive, try changing the disc to the other drive. If that does not work or if the disc 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.
Skift til VT4 eller vis indholdet af /var/log/syslog (brug nano som redigeringsprogram) til at kontrollere efter specifikke fejlbeskeder. Derefter kontrolleres også resultatet af dmesg.
Check in the output of dmesg if your optical drive was recognized. You should see something like (the lines do not necessarily have to be consecutive):
ata1.00: ATAPI: MATSHITADVD-RAM UJ-822S, 1.61, max UDMA/33 ata1.00: configured for UDMA/33 scsi 0:0:0:0: CD-ROM MATSHITA DVD-RAM UJ-822S 1.61 PQ: 0 ANSI: 5 sr0: scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw xa/form2 cdda tray cdrom: Uniform CD-ROM driver Revision: 3.20
If you don't see something like that, chances are the controller your drive 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 optical drive under /dev/. In the example above, this would be /dev/sr0. There should also be a /dev/cdrom.
Use the mount command to check if the optical disc 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 optical drive.
If there are any problems during the installation, try checking the integrity of the installation media using the option near the bottom of the installer's main menu. This option can also be used as a general test if the disc can be read reliably.
Hvis du har problemer og kernen hænger under opstartsprocessen, ikke genkender perifære enheder du rent faktisk har, eller driverne ikke bliver genkendt korrekt, så er den første ting du skal gøre er at kontrollere opstartsparametrene, som omtalt i Afsnit 5.3, “Opstartsparametre”.
I nogle tilfælde kan fejlsituationer opstå på grund af manglende firmware for udstyr (se Afsnit 2.2, “Enheder som kræver firmware” og Afsnit 6.4, “Indlæsning af manglende firmware”).
Under opstartssekvensen, kan du se beskeder i form af kan ikke finde eller et eller andetnoget er ikke til stedekan ikke initialisere , eller endda nogetdenne driverudgivelse afhænger af . De fleste af disse beskeder er harmløse. Du ser dem fordi kernen for installationssystemet er bygget til at køre på computere med mange forskellige perifære enheder. Det er indlysende at ikke alle computere har hver eneste perifære enhed, så operativsystemet kan give nogle få beklagelser, når det leder efter perifære enheder, du ikke har. Du kan også se at systemet kan gå i pause i et øjeblik. Dette sker når systemet venter på at en enhed svarer, og denne enhed ikke er tilgængelig på dit system. Hvis du synes at tiden systemet er om at starte op er for lang, så kan du oprette en tilpasset kerne senere (see Afsnit 8.5, “Kompilering af en ny kerne”). et eller andet
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 on a storage medium, 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.
Andre relevante installationsbeskeder kan findes i /var/log/ under installationen og /var/log/installer/ efter at computeren er blevet startet op i det installerede system.
Hvis du stadig har problemer, så indsend en installationsrapport. Vi opmuntrer også til, at installationsrapporter indsendes selvom installationen lykkes, så vi kan få så meget information som muligt om det største antal udstyrskonfigurationer.
Bemærk at din installationsrapport vil blive vist i Debians fejlsøgningssystem (BTS) og videresendt til en offentlig postliste. Sikr dig at du bruger en e-post-adresse, som du ikke har problemer med er offentlig.
Hvis du har et fungerende Debian-system, så er den nemmeste måde at sende en installationsrapport at installere pakkerne installation-report og reportbug (apt install installation-report reportbug), konfigurere reportbug som forklaret i Afsnit 8.4.2, “Sende e-post udenfor systemet”, og køre kommandoen 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/DVD? USB stick? 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 media: [ ]
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.
|
|
 |
|
| 5.3. Opstartsparametre |  |
Kapitel 6. Brug af Debian-installationsprogrammet |