https://wiki.archlinux.org/api.php?action=feedcontributions&user=Yobar73&feedformat=atomArchWiki - User contributions [en]2024-03-28T17:54:30ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=DVD_Burning&diff=73818DVD Burning2009-08-13T08:17:19Z<p>Yobar73: Ajout i18n</p>
<hr />
<div>[[Category:Optical (English)]]<br />
[[Category:Utilities (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|:DVD writing}}<br />
{{i18n_entry|Français|:DVD writing(Français)}}<br />
{{i18n_links_end}}<br />
<br />
==Introduction==<br />
Writing (or "Burning") DVDs is different from CDs. DVDs can contain much more data (I use 4.7GB single-layer discs), and the standard CD writing tools don't suffice anymore.<br />
<br />
This howto only covers a very simple part for now: writing data onto DVDs using the command line.<br />
<br />
==Tools for the job==<br />
#You still need the standard CD writing tools known as '''cdrtools''' (which can be replaced by '''cdrkit''').<br />
#You also need the new DVD writing tools known as '''dvd+rw-tools''', found in the '''extra''' repository.<br />
<br />
'''Note 1''': Do not install the package known as '''dvdrtools'''. It conflicts with cdrtools, and dvd+rw-tools is a better DVD writing package than dvdrtools.<br><br />
'''Note 2''': If you wish to use a graphical frontend, install '''k3b''' and you need to read no further.<br><br />
'''Note 3''': I used to use '''xcdroast''' for my CD writing needs, but I found it to have grown buggy and outdated. I also don't trust its method for writing DVDs. However, if you can reconcile my view on xcdroast, feel free.<br />
<br />
''Update 2006-07: I have found '''graveman''' to be an excellent replacement for xcdroast, so you can also use that instead.''<br />
<br />
==Getting the job done==<br />
Your new friend to burning DVDs will be the command ''''growisofs'''' from the DVD+RW-tools package. If you've ever written CDs from the command line before, you'll know the process of first creating an iso9660 file ('''mkisofs'''), and then burning it to CD ('''cdrecord'''). growisofs merges these steps for you, so you don't need extra storage space for the ISO file anymore. Another advantage is that multisession[http://www.google.com/search?hl=en&lr=&oi=defmore&q=define:Multisession ?] writing has been simplified. I won't explain how it ''used'' to be done, but I will explain how it works with growisofs.<br />
<br />
===basics===<br />
In basics, writing a '''new''' DVD goes like this:<br />
growisofs -Z ''/dev/cdrw'' -r -J /path/to/files<br />
Where /dev/cdrw is your DVD writer device.<br />
<br />
To '''continue''' a DVD (write an additional session) you use:<br />
growisofs -M ''/dev/cdrw'' -r -J /path/to/files<br />
<br />
'''-Z''': start at the beginning of the DVD using the following device,<br><br />
'''-M''': start after the last session on the disc using the following device,<br><br />
'''-r''': Rockridge support with sane permission settings (Recommended, extended UNIX info. Note that <tt>'''-r'''</tt> will choose a different permissions than the real ones, to use the exact permissions use <tt>'''-R'''</tt> instead, see the manual page of <tt>''mkisofs''</tt> for more information),<br><br />
'''-J''': Joliet support (Recommended, extended info for Win NT and Win95).<br />
<br />
<br />
'''Burning DVDs from ISO Image Files'''<br />
<br />
To burn a DVD from an ISO image use:<br />
growisofs -Z /dev/cdrw=/path/to/iso<br />
<br />
If you want to copy an existing DVD one way that works is to make an iso using readcd:<br />
<br />
readcd -v dev=/dev/cdrw -f isoimage.iso<br />
<br />
as per the CD burning tips in the CD burning howto in this wiki, then use the growisofs example above to burn the iso to a new blank disc.<br />
<br />
===Better examples===<br />
<br />
Although the above might suffice for you, I myself needed some extra settings to successfully write my DVD (I hope I didn't scare you off yet).<br />
<br />
The template that I use to start off my DVD writing:<br />
growisofs -Z /dev/cdrw -v -l -dry-run -iso-level 3 -R -J -speed=2 -joliet-long -graft-points /Magazines/=/home/citral/books/mags/<br />
<br />
Don't worry. I'll explain what everything does:<br />
*'''-Z''': As seen above, this tells to start off a new DVD. If I wanted to continue a multisession DVD, I'd use -M.<br />
*'''-v''': Increase verbosity level (more output).<br />
*'''-l''': Breaks DOS compatibility but allows for longer filenames.<br />
*'''-dry-run''': Important flag: Simulate writing. Remove this flag if you are sure that everything is set up correctly.<br />
*'''-iso-level 3''': Basically this flag just defines how strict you want to adhere to the iso9660 standard. -iso-level 1 is very strict; while -iso-level 4 is very loose. I use level 3 because I don't want to be limited (length of filenames for example), and so far I haven't ran into problems.<br />
*'''-R/-J''': see above.<br />
*'''-speed=2''': Just to be sure, I start burning at 2x speed.<br />
*'''-joliet-long''': Allows longer joliet filenames. The manual advices caution, but so far I had no problems.<br />
<br />
The final part needs some more explanation:<br />
-graft-points /Magazines/=/home/citral/books/mags/<br />
This specifies that I don't want the files at the root of my DVD, but in the subdirectory 'Magazines'.<br />
<br />
From the mkisofs manual:<br />
<tt><br />
:This is easiest to illustrate with a couple of examples. Let's start by assuming that a local file ../old.lis exists, and you wish to include it in the cdrom image.<br />
::foo/bar/=../old.lis<br />
:will include the file old.lis in the cdrom image at /foo/bar/old.lis, while<br />
::foo/bar/xxx=../old.lis<br />
:will include the file old.lis in the cdrom image at /foo/bar/xxx. The same sort of syntax can be used with directories as well. mkisofs will create any directories required such that the graft points exist on the cdrom image - the directories do not need to appear in one of the paths.</tt><br />
<br />
''As a last note'': growisofs is basically just a frontend to mkisofs. That means that any option to mkisofs also works to growisofs. You can check the mkisofs manpage for options you want to add.<br />
<br />
==DVD Rewritables==<br />
<br />
The process for burning rewritables is practically the same as normal DVDs. However, keep in mind that virgin DVD+RW media needs to be initially formatted ("blanked") prior to usage. Blanking can be done using the program '''dvd+rw-format''', like this:<br />
dvd+rw-format ''/dev/cdrw''<br />
Where /dev/cdrw is your DVD writer device.<br />
<br />
==Further Readings==<br />
*[http://fy.chalmers.se/~appro/linux/DVD+RW/ DVD+RW-tools site]<br />
*[http://www.jdrowell.com/archives/2005/03/backup_to_dvd_u.html Backup to DVD script] (404 as of 2009-05-23)<br />
*[http://www.students.cs.uu.nl/people/wbeekhui/ Usage examples] (404 as of 2009-05-23)<br />
* The growisofs, mkisofs and cdrtools man pages.</div>Yobar73https://wiki.archlinux.org/index.php?title=DVD_Playing&diff=73817DVD Playing2009-08-13T08:13:53Z<p>Yobar73: ajout i18n</p>
<hr />
<div>[[Category:Audio/Video (English)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|:DVD}}<br />
{{i18n_entry|Français|:DVD (Français)}}<br />
{{i18n_links_end}}<br />
<br />
==Playback Video==<br />
<br />
Some popular programs to play DVDs are mplayer, Xine and VLC. Xine and VLC support dvd menus where mplayer will play any title you specify.<br />
<br />
You will need to add your user to the group optical to be able to access your dvd drive, if you have not done so already:<br />
gpasswd -a USERNAME optical<br />
<br />
==libdvd Install==<br />
<br />
You will of course need to install the libdvd packages if you want to play encrypted DVDs<br />
<br />
#pacman -S libdvdread libdvdcss libdvdnav<br />
<br />
===mplayer===<br />
Mplayer is efficient and not heavy on the system requirements. There isn't much that can't be played with this program. To play a DVD with mplayer<br />
mplayer dvd://N<br />
''Where N is the chapter that you want to play, start at 1 and work your way up if you are not too sure.''<br />
<br />
To play a dvd image file<br />
mplayer -dvd-device movie.iso dvd://N<br />
To play a loopback mounted image (shouldn't be needed, use the above)<br />
# as root<br />
mount -o loop movie.iso /mnt/dvd<br />
# as a user<br />
mplayer -dvd-device /mnt/dvd dvd://N<br />
To find your audio language you can start mplayer with the '''-v''' switch and it will output audio IDs. You can make use of any auido track with '''-aid <audio_id>'''. You can set a default audio language by editing ''~/.mplayer/config'' and adding the line ''alang=en'' for english. <br />
<br />
DVDs can have volume too low. To increase the maximum volume to 400% use ''softvol=yes'' and ''softvol-max=400''. The startup volume defaults to 100% of software volume and the global mixer levels will remain untouched. Using the 9 and 0 keys, volume can be adjusted between 0 and 400 percent.<br />
alang=en<br />
softvol=yes<br />
softvol-max=400<br />
<br />
===gmplayer===<br />
The GUI version of mplayer is not quite as powerful as the console version but still efficient.<br />
<br />
===Xine===<br />
A good GUI player which works quite well on slower computers and supports menus.<br />
<br />
===VLC===<br />
A capable player which supports menus, installed with<br />
pacman -S vlc<br />
<br />
To make VLC the default DVD player in GNOME edit ''/usr/share/applications/vlc.desktop'' and at the bottom of the file add:<br />
MimeType=video/dv;video/mpeg;video/x-mpeg;video/msvideo;video/quicktime;video/x-anim;video/x-avi;video/x-ms-asf;video/x-ms-wmv;video/x-msvideo;video/x-nsv;video/x-flc;video/x-fli;application/ogg;application/x-ogg;application/x-matroska;audio/x-mp3;audio/x-mpeg;audio/mpeg;audio/x-wav;audio/x-mpegurl;audio/x-scpls;audio/x-m4a;audio/x-ms-asf;audio/x-ms-asx;audio/x-ms-wax;application/vnd.rn-realmedia;audio/x-real-audio;audio/x-pn-realaudio;application/x-flac;audio/x-flac;application/x-shockwave-flash;misc/ultravox;audio/vnd.rn-realaudio;audio/x-pn-aiff;audio/x-pn-au;audio/x-pn-wav;audio/x-pn-windows-acm;image/vnd.rn-realpix;video/vnd.rn-realvideo;audio/x-pn-realaudio-plugin;application/x-extension-mp4;audio/mp4;video/mp4;video/mp4v-es;x-content/video-vcd;x-content/video-svcd;x-content/video-dvd;x-content/audio-cdda;x-content/audio-player;<br />
<br />
Then as root run:<br />
update-desktop-database /usr/share/applications<br />
<br />
Open '''System>>Preferences>>File Management>>Media''' and next to ''DVD Video'' select ''Open VLC media player''<br />
<br />
==Backing up Video==<br />
See [[Make backup of DVD Video]] or use '''k9copy''' or '''dvdshrink''' under wine for the easy way out.<br />
<br />
==DVD Writing==<br />
See [[DVD writing]].</div>Yobar73https://wiki.archlinux.org/index.php?title=Kernel_Panics_(%CE%95%CE%BB%CE%BB%CE%B7%CE%BD%CE%B9%CE%BA%CE%AC)&diff=73692Kernel Panics (Ελληνικά)2009-08-10T17:01:17Z<p>Yobar73: ajout traduction française</p>
<hr />
<div>[[Category: Επαναφορά Συστήματος (Ελληνικά)]]<br />
[[Category:Σύντομοι Οδηγοί (HOWTOs) (Ελληνικά)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|Česky|:Kernel Panics (Česky)}}<br />
{{i18n_entry|English|:Kernel Panics}}<br />
{{i18n_entry|Español|:Kernel Panics (Español)}}<br />
{{i18n_entry|Italiano|:Kernel Panics (Italiano)}}<br />
{{i18n_entry|Français|:Kernel Panics (francais)}}<br />
{{i18n_entry|简体中文|:Kernel Panics (简体中文)}}<br />
{{i18n_entry|Ελληνικά|:Kernel Panics (Ελληνικά)}}<br />
{{i18n_entry|Türkçe|:Çekirdek Hataları}}<br />
{{i18n_links_end}}<br />
<br />
<!-- Dutch is my native language, so probably there are some spelling mistakes in this text. Please, feel free to edit them :) (Edited spelling and grammar by Archuser. :))--><br />
<br />
<br />
<br />
Αυτή η σελίδα περιγράφει πως να γυρίσετε πίσω, σε μια προηγουμένως εγκατεστημένη έκδοση πυρήνα αν η τρέχουσα αποτύχει να ξεκινήσει<br />
<br />
<br />
==Ξεκινώντας από το CD εγκατάστασης==<br />
<br />
Το πρώτο βήμα είναι να ξεκινήσετε τον υπολογιστή σας από το CD εγκατάστασης. Όταν ξεκινήσει, πληκτρολογήστε arch, όπως θα κάνατε αν θα κάνατε εγκατάσταση του arch<br />
# arch<br />
<br />
<br />
<br />
==Κάνοντας chroot στην κανονική σας εγκατάσταση==<br />
Όταν τελειώσει η διαδικασία του boot, είσαστε σε ένα μινιμαλιστικό αλλά λειτουργικό live GNU/Linux περιβάλλον με κάποια βασικά εργαλεία.<br />
Τώρα, πρέπει να κάνετε mount το κανονικό σας root διαμέρισμα (partition) στο φάκελο /mnt.<br />
# mount /dev/sdXY /mnt<br />
Αν χρησιμοποιείτε ξεχωριστό boot partition, μην ξεχάσετε να κάνετε mount και αυτό<br />
# mount /dev/sdXZ /mnt/boot<br />
<br />
<br />
<br />
Οι νεότεροι πυρήνες χρησιμοποιούν ένα αρχικό ramdisk για να σετάρουν το περιβάλλον πυρήνα. Όταν επανεγκαθιστάτε έναν πυρήνα, εκείνο το αρχικό ramdisk θα δημιουργηθεί με το mkinitcpio. Ένα από τα χαρακτηριστικά του mkinitcpio είναι ότι χρησιμοποιεί αυτόματο εντοπισμό (autodetection) για να διαπιστώσει ποια modules που πυρήνα είναι απαραίτητα για να ξεκινήσει ο υπολογιστής σας. Για να λειτουργήσει ο αυτόματος εντοπισμός, τα /dev /sys και /proc πρέπει να γίνουν κ αυτά mount στο περιβάλλον chroot:<br />
<br />
<br />
<br />
# mount -t proc none /mnt/proc<br />
# mount -t sysfs none /mnt/sys<br />
# mount --bind /dev /mnt/dev<br />
<br />
<br />
Τώρα θα κάνουμε chroot σε αυτό τον φάκελο:<br />
<br />
<br />
# chroot /mnt<br />
<br />
<br />
<br />
==Επιστροφή σε προηγούμενη έκδοση πυρήνα==<br />
Εάν διατηρείται τα κατεβασμένα πακέτα του pacman, μπορείτε εύκολα να γυρίσετε πίσω. Εάν δεν τα κρατάτε, πρέπει να βρείτε έναν τρόπο να φέρετε στο σύστημα σας μια προηγούμενη έκδοση πυρήνα.<br />
<br />
<br />
Ας υποθέσουμε ότι κρατούσατε τις προηγούμενες εκδόσεις. Θα εγκαταστήσουμε τώρα την προηγούμενη που λειτουργούσε.<br />
# pacman -U /var/cache/pacman/pkg/kernel26-2.6.23.''xx-x''.pkg.tar.gz<br />
<br />
<br />
Ίσως θα πρέπει να αλλάξετε τα νούμερα της έκδοσης σε αυτά της έκδοσης η οποία προηγουμένως λειτουργούσε, αλλά αυτή δεν είναι μεγάλη διαφορά.<br />
<br />
<br />
<br />
==Επανεκκίνηση==<br />
Τώρα που ο πυρήνας που δουλεύει έχει εγκατασταθεί, μπορείτε άφοβα να επανεκκινήσετε τον υπολογιστή σας, και να τον ξεκινήσετε ως συνήθως.</div>Yobar73https://wiki.archlinux.org/index.php?title=Kernel_Panics_(Italiano)&diff=73691Kernel Panics (Italiano)2009-08-10T17:00:36Z<p>Yobar73: ajout traduction française</p>
<hr />
<div>[[Category: System recovery (Italiano)]]<br />
[[Category:HOWTOs (Italiano)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|Česky|:Kernel Panics (Česky)}}<br />
{{i18n_entry|English|:Kernel Panics}}<br />
{{i18n_entry|Español|:Kernel Panics (Español)}}<br />
{{i18n_entry|Italiano|:Kernel Panics (Italiano)}}<br />
{{i18n_entry|Français|:Kernel Panics (francais)}}<br />
{{i18n_entry|简体中文|:Kernel Panics (简体中文)}}<br />
{{i18n_entry|Ελληνικά|:Kernel Panics (Ελληνικά)}}<br />
{{i18n_entry|Türkçe|:Çekirdek Hataları}}<br />
{{i18n_links_end}}<br />
<br />
In questa pagina si descrive come ritornare ad una versione precedente del kernel, nel caso in cui quella corrente abbia avuto qualche problema.<br />
<br />
==Avvio dal CD di installazione==<br />
Il primo passo è l'avvio del CD di installazione. Una volta lanciato, digitare "arch", come se si volesse installare Arch Linux per la prima volta. <br />
# arch<br />
<br />
==Chroot nel proprio disco di root==<br />
Una volta avviato, avrete un ambiente Linux ridotto, ma perfettamente funzionale, completo di alcuni strumenti di base.<br />
Ora, bisogna montare il disco di root in /mnt.<br />
# mount /dev/hdXY /mnt<br />
Se si utilizza una partizione di boot, non dimenticare di montarla<br />
# mount /dev/hdaXY /mnt/boot<br />
<br />
I kernel più nuovi utilizzano una ramdisk iniziale per impostare l'ambiente del kernel. Quando si reinstalla un kernel, quella ramdisk iniziale va rigenerata con mkinitcpio. Una delle caratteristiche di mkinitcpio è l'autorilevamento dei moduli del kernel che sono necessari per avviare il proprio computer. Per far funzionare questo autorilevamento, è necessario che /dev, /sys e /proc siano montati nel proprio ambiente chroot:<br />
<br />
# mount -t proc none /mnt/proc<br />
# mount -t sysfs none /mnt/sys<br />
# mount --bind /dev /mnt/dev<br />
<br />
Ora, si dovrà eseguire un chroot in questo disco, in modo da poterlo utilizzare come si avviasse il proprio computer "normalmente". Molte funzionalità non saranno comunque disponibili.<br />
# chroot /mnt<br />
<br />
==Ritornare ad una versione precedente del kernel (rollback)==<br />
Se si mantengono i pacchetti scaricati con pacman nella sua cache, allora si può facilmente eseguire il rollback. Se invece non si è scelto di mantenerli, bisogna trovare un modo per ottenere una versione precedente del kernel nel proprio sistema.<br />
<br />
Supponiamo che si è scelto di mantenere le precedenti versioni dei pacchetti. Si dovrà quindi installare l'ultima versione funzionante, per esempio con il seguente comando:<br />
# pacman -U /var/cache/pacman/pkg/kernel26-2.6.16.13-1.pkg.tar.gz<br />
<br />
Probabilmente si dovrà cambiare il numero di versione riportato appena sopra con quello dell'ultima versione funzionante.<br />
<br />
==Reboot==<br />
A questo punto, se si è reinstallato il kernel funzionante, si può riavviare il proprio computer ed eseguire il boot come si fa usualmente.<br />
Non dimenticare di controllare la pagina delle news di Arch Linux, per capire che cosa è andato storto con l'ultima versione del kernel.</div>Yobar73https://wiki.archlinux.org/index.php?title=Kernel_Panics_(Espa%C3%B1ol)&diff=73690Kernel Panics (Español)2009-08-10T16:59:59Z<p>Yobar73: ajout traduction francaise</p>
<hr />
<div>[[Category:Recuperación del sistema (Español)]]<br />
[[Category:Núcleo (Español)]]<br />
[[Category:CÓMOs (Español)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|Česky|:Kernel Panics (Česky)}}<br />
{{i18n_entry|English|:Kernel Panics}}<br />
{{i18n_entry|Español|:Kernel Panics (Español)}}<br />
{{i18n_entry|Italiano|:Kernel Panics (Italiano)}}<br />
{{i18n_entry|Français|:Kernel Panics (francais)}}<br />
{{i18n_entry|简体中文|:Kernel Panics (简体中文)}}<br />
{{i18n_entry|Ελληνικά|:Kernel Panics (Ελληνικά)}}<br />
{{i18n_entry|Türkçe|:Çekirdek Hataları}}<br />
{{i18n_links_end}}<br />
<br />
== Introducción ==<br />
Esta página describe como volver a una versión del kernel anterior si la actual falla.<br />
<br />
== Iniciar desde el CD de instalación ==<br />
Bootea desde el CD de instalación. Cuando haya cargado, escribe arch, como harías cuando instalas arch.<br />
# arch<br />
<br />
== Chroot a tu partición raíz ==<br />
Cuando ya hayas booteado, tendrás un pequeño pero funcional mini-entorno de trabajo.<br />
Ahora, debes montar tu partición raíz en /mnt:<br />
# mount /dev/hdXY /mnt<br />
Si usas una partición de booteo no olvides montarla:<br />
# mount /dev/hdaXY /mnt/boot<br />
<br />
Kernels nuevos usan un ramdisk inicial para acelerar su entorno. Cuando reinstalas un kernel, ese ramdisk inicial se regenerará con mkinitcpio. Una de las características de mkinitcpio es que hace una auto-detección para encontrar cuales son los módulos que cargan al inicio del sistema. Para que esta auto-detección funcione, /dev, /sys y /proc deben estar montados en tu chroot:<br />
<br />
# mount -t proc none /mnt/proc<br />
# mount -t sysfs none /mnt/sys<br />
# mount --bind /dev /mnt/dev<br />
<br />
Ahora haremos un chroot a este disco, así puedes usarlo como si tu PC hubiera booteado normalmente. Claro, muchas cosas no funcionarán.<br />
# chroot /mnt<br />
<br />
== Volver a la versión anterior del Kernel ==<br />
Si dejas tus ficheros descargados del pacman, puedes volver fácilmente. Si no, deberás buscar una versión anterior del kernel de tu sistema ahora.<br />
<br />
Supongamos que dejaste guardado el paquete. Lo instalaremos:<br />
# pacman -U /var/cache/pacman/pkg/kernel26-<tt>VERSIÓN-ANTERIOR-DEL-KERNEL-ACTUAL</tt>.pkg.tar.gz<br />
<br />
== Reiniciando ==<br />
Ahora el kernel funcional esta instalado. Sal de chroot, desmonta las particiones y reinicia:<br />
# cd /<br />
# umount -a<br />
# exit<br />
# cd /<br />
# umount -a<br />
# reboot<br />
<br />
No olvides visitar [http://www.archlinux.org/ el sitio oficial de Arch], y dirigirte a la parte de noticias, para ver que salió mal con esa versión del Kernel.</div>Yobar73https://wiki.archlinux.org/index.php?title=Kernel_Panics_(%C4%8Ce%C5%A1tina)&diff=73689Kernel Panics (Čeština)2009-08-10T16:59:23Z<p>Yobar73: ajout traduction française</p>
<hr />
<div>[[Category: System recovery (Česky)]]<br />
[[Category:HOWTOs (Česky)]]<br />
[[Category:Kernel (Česky)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|Česky|:Kernel Panics (Česky)}}<br />
{{i18n_entry|English|:Kernel Panics}}<br />
{{i18n_entry|Español|:Kernel Panics (Español)}}<br />
{{i18n_entry|Italiano|:Kernel Panics (Italiano)}}<br />
{{i18n_entry|Français|:Kernel Panics (francais)}}<br />
{{i18n_entry|简体中文|:Kernel Panics (简体中文)}}<br />
{{i18n_entry|Ελληνικά|:Kernel Panics (Ελληνικά)}}<br />
{{i18n_entry|Türkçe|:Çekirdek Hataları}}<br />
{{i18n_links_end}}<br />
<br />
Tato stránka popisuje jak opravit počítač, jehož jádro při náběhu zpanikaří (= '''kernel panic''', jádro zastaví svoji činnost).<br />
<br />
==Řešení problému==<br />
Abyste řešení problému usnadnili, ujistěte se, že jádro není v tichém (quiet) režimu. Je-li, odstraňte "quiet" z řádku kernel v konfiguraci GRUBu. Při nabíhání systému ověřujte výstup hned před panikou a rozhodněte, zda je tam jakákoliv užitečná informace. Příčin panik je zřejmě příliš mnoho na to, aby mohly být dobře zdokumentovány v této wiki. Ujistěte se, že konfigurace vašeho systému v /boot je správná a že žádný z hardware počítače není vadný. Pokud věříte, že je panika jádra selháním paniky samotné, následujte níže uvedenou první možnost pro instalaci dřívějšího jádra. Pokud věříte, že konfigurace v /boot může být chybná, následujte možnost 2.<br />
<br />
==1. možnost: Přeinstalace jádra==<br />
Přeinstalace jádra je pravděpodobně ta nejlepší sázka, pokud nedávno nebyly provedeny žádné jiné velké systémové úpravy.<br />
<br />
===Spusťte instalační CD===<br />
První krok je nabootování instalačního CD. Po startu zadejte <tt>arch</tt>, jako byste instalovali Arch Linux.<br />
# arch<br />
<br />
===Chroot do svého kořenového adresáře===<br />
Po nabootování jste v minimálním ale funkčním živém prostředí GNU/Linux s některými základními nástroji.<br />
Nyní musít připojit svůj běžný kořenový oddíl do /mnt.<br />
# mount /dev/sdXY /mnt<br />
Pokud používáte oddělený boot oddíl, nezapomeňte ho připojit také.<br />
# mount /dev/sdXZ /mnt/boot<br />
<br />
Novější jádra používají počáteční ramdisk (initrd) pro nastavení prostředí jádra. Když přeinstalováváte jádro, daný počáteční ramdisk bude pomocí mkinitcpio vytvořen znovu. Jednou z dovedností mkinitcpio je autodetekce modulů jádra, které jsou vyžadovány pro spuštění vašeho počítače. Aby tato autodetekce pracovala, ve vašem chrootu musí být připojeny adresáře /dev, /sys a /proc:<br />
<br />
# mount -t proc none /mnt/proc<br />
# mount -t sysfs none /mnt/sys<br />
# mount --bind /dev /mnt/dev<br />
<br />
Nyní provedeme chroot do tohoto oddílu:<br />
# chroot /mnt<br />
<br />
===Návrat k předchozí verzi jádra===<br />
Pokud si ponecháváte stažené balíčky pacmana, můžete se lehce navrátit k předchozí verzi. Pokud jste si je neponechali, musíte si najít nějaký způsob, jak nyní na svůj systém dostanete předchozí verzi jádra.<br />
<br />
Předpokládejme, že jste si předchozí verze ponechali. Nyní nainstalujeme tu poslední funkční.<br />
# pacman -U /var/cache/pacman/pkg/kernel26-2.6.23.''xx-x''.pkg.tar.gz<br />
Samozřejmě že si musíte tento řádek poupravit pro vlastní verzi jádra.<br />
<br />
V opačném případě se pro balíček poohlédněte na instalačním CD. Například i686 CD verze 2008.06 obsahuje addons/core-pkgs/kernel26-2.6.25.6-1-i686.pkg.tar.gz.<br />
<br />
==2. možnost: Ověřte konfiguraci zavaděče==<br />
Další možnost je chyba v konfiguraci zavaděče operačního systému. Například změna oddílů na pevném disku může zapříčinit změnu pořadí oddílů. Uživatelé GRUBu si mohou vzpomenout, zda se změna oddílů stala nedávno a ověřit si, že řádky ''root'' a ''kernel'' skutečně odpovídají novému schéma oddílů.<br />
<br />
==Restart==<br />
Nyní je ten čas restartovat a zjistit, zda úpravy systému zastavily paniku.<br />
Pokud funguje návrat ke starší verzi jádra, nezapomeňte se podívat na arch-newspage, abyste zjistili, co se v daném sestavení jádra nepovedlo.</div>Yobar73https://wiki.archlinux.org/index.php?title=Kernel_Panics&diff=73688Kernel Panics2009-08-10T16:58:34Z<p>Yobar73: ajout traduction française</p>
<hr />
<div>[[Category: System recovery (English)]]<br />
[[Category:HOWTOs (English)]]<br />
[[Category:Kernel (English)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|Česky|:Kernel Panics (Česky)}}<br />
{{i18n_entry|English|:Kernel Panics}}<br />
{{i18n_entry|Español|:Kernel Panics (Español)}}<br />
{{i18n_entry|Italiano|:Kernel Panics (Italiano)}}<br />
{{i18n_entry|Français|:Kernel Panics (francais)}}<br />
{{i18n_entry|简体中文|:Kernel Panics (简体中文)}}<br />
{{i18n_entry|Ελληνικά|:Kernel Panics (Ελληνικά)}}<br />
{{i18n_entry|Türkçe|:Çekirdek Hataları}}<br />
{{i18n_links_end}}<br />
<br />
This page describes how to repair a computer whose kernel panics at boot. This has to do with the very basic OS kernel and the first part of the boot routine. (For issues regarding graphical interface problems or program freeze-ups, etc., save yourself some wasted effort and time, and please look elsewhere.)<br />
<br />
==Definition==<br />
A decent definition of Kernel Panic comes to us from Wikipedia, which states in part; "A kernel panic is an action taken by an operating system upon detecting an internal fatal error from which it cannot safely recover; the term is largely specific to Unix and Unix-like systems. The equivalent in Microsoft Windows operating systems is the Blue Screen of Death." Read more by following this link: [http://en.wikipedia.org/wiki/Kernel_panic Kernal Panic]<br />
<br />
==What To Do==<br />
Basically, the problem is that the operating system doesn't start correctly. Various behavior may be expressed, such as that one may get the computer to freeze, or the operating system may give an error message of some sort or one may not go to the place they were expecting (Command prompt, Desktop or whathaveyou). This will require some basic troubleshooting from the command line, if you can boot to it, or from a boot disk if it will get you a command prompt or your favorite interface.<br />
<br />
==Troubleshooting==<br />
To make troubleshooting easier, ensure that the kernel is not in quiet mode. Remove 'quiet' from the kernel line in GRUB, if it is found there. Upon boot, check the output immediately before the panic, and decide whether there is any useful information. There are probably too many causes for a kernel panic to keep well-documented in this wiki. Make sure that your system's configuration in /boot is correct, and that none of the computer's hardware is faulty - it is good idea to run memtest from the Arch install/rescue CD or another utility (red entries are bad). If you believe the configuration in /boot may be erroneous, try Option 1 to repair your bootloader setup. If you believe the kernel panic is the fault of the kernel itself, follow Option 2 in order to reinstall the existing version or an earlier kernel.<br />
<br />
==Option 1: Check bootloader configuration==<br />
Another possibility is an error in the bootloader's configuration (e.g. <tt>/boot/grub/menu.lst</tt>). For example, repartitioning hard drives can change partitions' order. GRUB users may recall whether repartitioning has occurred recently and make sure the ''root'' and ''kernel'' lines match up with the new partitioning scheme. And examine the file for typos and extraneous characters. An extra space, or a character in the wrong place will cause a kernel panic.<br />
<br />
==Option 2: Reinstall kernel==<br />
Reinstalling the kernel is probably the best bet when no other major system modifications have taken place recently.<br />
<br />
===Start from the installation CD===<br />
The first step is booting the installation CD. When started, type arch, like you would when installing arch.<br />
# arch<br />
<br />
===Chroot to your normal root===<br />
When booted, you are in a minimal but functional live GNU/Linux environment with some basic tools.<br />
Now, you have to mount your normal root disk to /mnt.<br />
# mount /dev/sdXY /mnt<br />
If you use a boot partition, don't forget to mount it<br />
# mount /dev/sdXZ /mnt/boot<br />
<br />
Newer kernels use an initial ramdisk to set up the kernel environment. When you reinstall a kernel, that initial ramdisk will be regenerated with mkinitcpio. One of mkinitcpio's features is that it does autodetection to find out what kernel modules are required for starting up your computer. For this autodetection to work, /dev, /sys and /proc need to mounted in your chroot:<br />
<br />
# mount -t proc none /mnt/proc<br />
# mount -t sysfs none /mnt/sys<br />
# mount --bind /dev /mnt/dev<br />
<br />
Now, we will chroot to this disk:<br />
# chroot /mnt<br />
<br />
===Roll back to previous kernel version===<br />
If you keep your downloaded pacman packages, you now can easily roll back. If you didn't keep them, you have to find a way to get a previous kernel version on your system now.<br />
<br />
Let's suppose you keep the previous versions. We will now install the last working one.<br />
# pacman -U /var/cache/pacman/pkg/kernel26-2.6.23.''xx-x''.pkg.tar.gz<br />
Of course, make sure that you adapt this line to your own kernel version.<br />
<br />
Otherwise, check the install CD for a package. For example, the version 2008.06 i686 CD contains addons/core-pkgs/kernel26-2.6.25.6-1-i686.pkg.tar.gz.<br />
<br />
==Reboot==<br />
Now is the time to reboot and see if the system modifications have stopped the panic.<br />
If reverting to an older kernel works, don't forget to check the arch-newspage to check what went wrong with the kernel build.</div>Yobar73