Subversion Repositories svn LFS-FR

Rev

Rev 7190 | Rev 7210 | Go to most recent revision | Blame | Compare with Previous | Last modification | View Log | RSS feed

# SOME DESCRIPTIVE TITLE
# Copyright (C) YEAR Free Software Foundation, Inc.
# This file is distributed under the same license as the PACKAGE package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2016-12-04 04:10+0100\n"
"PO-Revision-Date: 2016-12-04 17:14+0000\n"
"Last-Translator: roptat <roptat@lepiller.eu>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"Language: fr\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=(n > 1);\n"
"X-Generator: Pootle 2.7\n"
"X-POOTLE-MTIME: 1480871693.765662\n"

#. type: Content of: <sect1><sect1info>
#: blfs-en/postlfs/config/firmware.xml:12
msgid ""
"<othername>$LastChangedBy: bdubbs $</othername> <date>$Date: 2016-07-25 "
"00:52:11 +0200 (Mon, 25 Jul 2016) $</date>"
msgstr ""
"<othername>$LastChangedBy: bdubbs $</othername> <date>$Date: 2016-07-25 "
"00:52:11 +0200 (Mon, 25 Jul 2016) $</date>"

#. type: Content of: <sect1><title>
#: blfs-en/postlfs/config/firmware.xml:16
msgid "About Firmware"
msgstr "À propos des Firmwares"

#. type: Content of: <sect1><indexterm><primary>
#: blfs-en/postlfs/config/firmware.xml:19
msgid "/lib/firmware"
msgstr "/lib/firmware"

#. type: Content of: <sect1><para>
#: blfs-en/postlfs/config/firmware.xml:22
msgid ""
"On some recent PCs it can be necessary, or desirable, to load firmware to "
"make them work at their best. There is a directory, <filename "
"class=\"directory\">/lib/firmware</filename>, where the kernel or kernel "
"drivers look for firmware images."
msgstr ""
"Sur certains PCs actuels il peut être nécessaire, ou désirable, de charger "
"des firmwares pour faire travailler les PC au maximum de leurs possibilités."
" Le noyau contient un répertoire, <filename "
"class=\"directory\">/lib/firmware</filename>, ou le noyau ou les pilotes du "
"noyau cherche des images de firmware."

#. type: Content of: <sect1><para>
#: blfs-en/postlfs/config/firmware.xml:27
msgid ""
"Preparing firmware for multiple different machines, as a distro would do, is"
" outside the scope of this book."
msgstr ""
"Préparer des firmwares pour de multiples machines différente, comme les "
"distributions le font, est en dehors du périmètre de ce livre."

#. type: Content of: <sect1><para>
#: blfs-en/postlfs/config/firmware.xml:30
msgid ""
"Currently, most firmware can be found at a <userinput>git</userinput> "
"repository: <ulink "
"url=\"http://git.kernel.org/cgit/linux/kernel/git/firmware/linux-"
"firmware.git/tree/\"/>.  For convenience, the LFS Project has created a "
"mirror, updated daily, where these firmware files can be accessed via "
"<userinput>wget</userinput> or a web browser at <ulink url=\"&sources-"
"anduin-http;/linux-firmware/\"/>."
msgstr ""
"Actuellement, on peut trouver la plupart des firmwares sur un dépot "
"<userinput>git</userinput>&nbsp;: <ulink "
"url=\"http://git.kernel.org/cgit/linux/kernel/git/firmware/linux-"
"firmware.git/tree/\"/>. Par commodité, le projet LFS a créé un miroir, mis à"
" jour quotidiennement, ou on peut accéder à ces fichiers de firmwares via "
"<userinput>wget</userinput> ou un navigateur web à <ulink url=\"&sources-"
"anduin-http;/linux-firmware/\"/>."

#. type: Content of: <sect1><para>
#: blfs-en/postlfs/config/firmware.xml:38
msgid ""
"To get the firmware, either point a browser to one of the above repositories"
" and then download the item(s) which you need, or install "
"<userinput>git</userinput> and clone that repository."
msgstr ""
"Pour avoir le microprogramme, vous devez soit aller sur un des dépôts ci-"
"dessus avec un navigateur pour télécharger le(s) fichier(s) dont vous avez "
"besoin, soit installer <userinput>git</userinput> et cloner ce dépôt."

#. type: Content of: <sect1><para>
#: blfs-en/postlfs/config/firmware.xml:42
msgid ""
"For some other firmware, particularly for Intel microcode and certain wifi "
"devices, the needed firmware is not available in the above repository.  Some"
" of this will be addressed below, but a search of the Internet for needed "
"firmware is sometimes necessary."
msgstr ""
"Pour certains autres firmwares, particulièrement pour les micro-codes "
"d'Intel, et certains périphériques wi-fi, le firmware recherché n'est pas "
"disponible dans le dépôt précédent. Certains d'entre eux seront ajouté "
"ensuite, mais il est parfois nécessaire de faire une recherche sur internet "
"pour les firmwares souhaités."

#. type: Content of: <sect1><para>
#: blfs-en/postlfs/config/firmware.xml:47
msgid ""
"Firmware files are conventionally referred to as blobs because you cannot "
"determine what they will do. Note that firmware is distributed under various"
" different licenses which do not permit disassembly or reverse-engineering."
msgstr ""
"Les fichiers firmwares sont par convention référencés comme des blobs car "
"vous ne pouvez pas déterminer ce qu'ils font. Notez que ces firmwares sont "
"distribués sous des licences différentes et variées qui ne permettent pas le"
" désassemblage ou la retro ingénierie."

#. type: Content of: <sect1><para>
#: blfs-en/postlfs/config/firmware.xml:51
msgid "Firmware for PCs falls into four categories:"
msgstr "Les firmwares pour PC tombent dans 4 catégories&nbsp;:"

#. type: Content of: <sect1><itemizedlist><listitem><para>
#: blfs-en/postlfs/config/firmware.xml:55
msgid ""
"Updates to the CPU to work around errata, usually referred to as microcode."
msgstr ""
"Les firmwares mettant à jour le CPU pour travailler correctement, couramment"
" appelé micro-code."

#. type: Content of: <sect1><itemizedlist><listitem><para>
#: blfs-en/postlfs/config/firmware.xml:59
msgid ""
"Firmware for video controllers. On x86 machines this seems to only apply to "
"ATI devices : Radeons require firmware to be able to use KMS (kernel "
"modesetting - the preferred option) as well as for Xorg. For earlier radeon "
"chips (before the R600), the firmware is still in the kernel."
msgstr ""
"Les firmwares pour les contrôleurs vidéo. Sur les machines x86 cela semble "
"s'appliquer seulement aux périphériques ATI&nbsp;: les Radeons demandent des"
" firmwares pour pouvoir utiliser le KMS (kernel modesetting &mdash; option "
"préférable) avec Xorg. Pour les puces radeons plus anciennes (avant R600), "
"le firmware est resté dans le noyau."

#. type: Content of: <sect1><itemizedlist><listitem><para>
#: blfs-en/postlfs/config/firmware.xml:66
msgid ""
"Firmware updates for wired network ports. Mostly they work even without the "
"updates, but one must assume that they will work better with the updated "
"firmware."
msgstr ""
"Les Firmwares mettant à jour les ports réseaux câblés. Souvent ils "
"fonctionnent sans les mises à jour, mais on peut penser qu'ils travaillent "
"mieux avec les firmwares mis à jour."

#. type: Content of: <sect1><itemizedlist><listitem><para>
#: blfs-en/postlfs/config/firmware.xml:71
msgid ""
"Firmware for other devices, such as wifi. These devices are not required for"
" the PC to boot, but need the firmware before these devices can be used."
msgstr ""
"Les Firmwares pour les autres périphériques, comme le wi-fi. Ces "
"périphériques ne sont pas requis pour que le PC démarre, mais demande un "
"firmware avant que ces périphériques puissent être utilisés."

#. type: Content of: <sect1><note><para>
#: blfs-en/postlfs/config/firmware.xml:77
msgid ""
"Although not needed to load a firmware blob, the following tools may be "
"useful for determining, obtaining, or preparing the needed firmware in order"
" to load it into the system: <xref linkend=\"cpio\"/>, <xref "
"linkend=\"git\"/>, <xref linkend=\"pciutils\"/>, and <xref "
"linkend=\"wget\"/>"
msgstr ""
"Bien qu’ils soient inutile pour charger un firmware fermé (blob), les outils"
" suivants peuvent être utiles pour déterminer, obtenir, ou préparer le "
"firmware à utiliser afin de le charger dans le système&nbsp;: <xref "
"linkend=\"cpio\"/>, <xref linkend=\"git\"/>, <xref linkend=\"pciutils\"/> et"
" <xref linkend=\"wget\"/>"

#. type: Content of: <sect1><para>
#: blfs-en/postlfs/config/firmware.xml:85
msgid "User Notes: <ulink url=\"&blfs-wiki;/aboutfirmware\"/>"
msgstr "Notes utilisateur&nbsp;: <ulink url=\"&blfs-wiki;/aboutfirmware\"/>"

#. type: Content of: <sect1><sect2><title>
#: blfs-en/postlfs/config/firmware.xml:89
msgid "Microcode updates for CPUs"
msgstr "Mise à jour de micro-codes pour les CPU"

#. type: Content of: <sect1><sect2><para>
#: blfs-en/postlfs/config/firmware.xml:91
msgid ""
"In general, microcode can be loaded by the BIOS or UEFI, and it might be "
"updated by upgrading to a newer version of those. On linux, you can also "
"load the microcode from the kernel if you are using an AMD family 10h or "
"later processor (first introduced late 2007), or an Intel processor from "
"1998 and later (Pentium4, Core, etc), if updated microcode has been "
"released. These updates only last until the machine is powered off, so they "
"need to be applied on every boot."
msgstr ""
"En général, le micro-code peut être chargé par le BIOS ou l'UEFI, et il peut"
" être mis à jour en passant à une nouvelle version de celui-ci. Sur Linux, "
"vous pouvez également charger le micro-code depuis le noyau si vous utilisez"
" au moins un AMD de la famille 10h ou un plus récent (introduit après fin "
"2007), ou un processeur Intel de 1998 et plus (Pentium4, Core, etc), si un "
"micro-code mis à jour a été publié. Ces mises à jour sont actives seulement "
"jusqu'à ce que la machine soit éteinte, il est donc nécessaire de les "
"appliquer à chaque démarrage."

#. type: Content of: <sect1><sect2><para>
#: blfs-en/postlfs/config/firmware.xml:99
msgid ""
"There are two ways of loading the microcode, described as 'early' and "
"'late'. Early loading happens before userspace has been started, late "
"loading happens when userspace has started. Not surprisingly, early loading "
"is preferred, (see e.g. an explanatory comment in a kernel commit noted at "
"<ulink url=\"https://lwn.net/Articles/530346/\">x86/microcode: Early load "
"microcode </ulink> on LWN.)  Indeed, it is needed to work around one "
"particular erratum in early Intel Haswell processors which had TSX enabled."
"  (See <ulink url=\"http://www.anandtech.com/show/8376/intel-disables-tsx-"
"instructions-erratum-found-in-haswell-haswelleep-broadwellyi/\"> Intel "
"Disables TSX Instructions: Erratum Found in Haswell, Haswell-E/EP, "
"Broadwell-Y</ulink>.) Without this update glibc can do the wrong thing in "
"uncommon situations."
msgstr ""
"Il y a deux façons de charger le micro-code, décrit comme \"au plus tôt\" et"
" \"le plus tard\". Le chargement \"au plus tôt\" arrive avant que l'espace "
"utilisateur ai été démarré, le chargement \"le plus tard\" arrive quand "
"l'espace utilisateur est démarré. Sans surprise, le chargement \"au plus "
"tôt\" est préféré (voir par exemple un commentaire d'explication dans un "
"commit du noyau noté <ulink "
"url=\"https://lwn.net/Articles/530346/\">x86/microcode: Early load "
"microcode</ulink> sur LWN). En effet, il est utile de contourner une erreur "
"particulière dans les premiers processeurs Intel Haswell qui ont le TSX "
"d'activé. (Voir <ulink url=\"http://www.anandtech.com/show/8376/intel-"
"disables-tsx-instructions-erratum-found-in-haswell-haswelleep-"
"broadwellyi/\">Intel Disables TSX Instructions: Erratum Found in Haswell, "
"Haswell-E/EP, Broadwell-Y</ulink>). Sans cette mise à jour glibc peut "
"produire des erreurs dans des situations particulières."

#. type: Content of: <sect1><sect2><para>
#: blfs-en/postlfs/config/firmware.xml:112
msgid ""
"It is much simpler to begin by building a kernel which boots on your "
"hardware, try late microcode loading to see if there is an update (in many "
"cases the BIOS or UEFI will have already applied any update), and then take "
"the extra steps required for early loading."
msgstr ""
"Il est beaucoup plus simple de commencer par construire un noyau qui démarre"
" sur votre matériel, essayer de charger le micro-code «&nbsp;le plus "
"tard&nbsp;» pour voir s'il y a une mise à jour (dans la plupart des cas le "
"BIOS ou l'UEFI aura déjà appliqué toutes les mises à jours), et ensuite "
"faire les étapes supplémentaires dans la configuration du noyau pour un "
"chargement «&nbsp;au plus tôt&nbsp;»."

#. type: Content of: <sect1><sect2><para>
#: blfs-en/postlfs/config/firmware.xml:117
msgid ""
"This means you will be reconfiguring your kernel if you use early loading, "
"so keep the built source around to minimise what gets rebuilt, and if you "
"are at all uncertain, add your own identifier (A,B, etc) to the end of the "
"EXTRAVERSION in the kernel configuration, e.g. \"EXTRAVERSION -A\" if "
"nothing was set."
msgstr ""
"Cela signifie que vous devrez reconfigurer votre noyau si vous utilisez le "
"chargement «&nbsp;au plus tôt&nbsp;», aussi laissez les sources construites "
"afin de minimiser ce qui aura besoin d'être reconstruit, et si vous êtes "
"incertain, ajoutez votre propre identifiant (A, B, etc) à la fin de "
"l'EXTRAVERSION dans la configuration du noyau, soit \"EXTRAVERSION -A\" si "
"rien est initialisé."

#. type: Content of: <sect1><sect2><para>
#: blfs-en/postlfs/config/firmware.xml:123
msgid ""
"To confirm what processor(s) you have (if more than one, they will be "
"identical) look in /proc/cpuinfo."
msgstr ""
"Pour confirmer quel(s) processeur(s) vous avez (si plus d'un, ils seront "
"identiques) regardez dans /proc/cpuinfo."

#. type: Content of: <sect1><sect2><sect3><title>
#: blfs-en/postlfs/config/firmware.xml:127
msgid "Intel Microcode for the CPU"
msgstr "Micro-code Intel pour le CPU"

#. type: Content of: <sect1><sect2><sect3><bridgehead>
#: blfs-en/postlfs/config/firmware.xml:129
msgid "Required Package"
msgstr "Paquet requis"

#. type: Content of: <sect1><sect2><sect3><para>
#: blfs-en/postlfs/config/firmware.xml:131
msgid "<ulink url='http://fedorahosted.org/released/microcode_ctl/'/>"
msgstr "<ulink url='http://fedorahosted.org/released/microcode_ctl/'/>"

#. type: Content of: <sect1><sect2><sect3><para>
#: blfs-en/postlfs/config/firmware.xml:133
msgid ""
"For Intel CPUs an extra package, microcode_ctl, is required. The package "
"chosen is the version hosted at fedora &mdash; there is an alternative "
"version at github from the same packager, but that still includes a "
"redundant old version of an AMD microcode container, and also requires the "
"unzip package."
msgstr ""
"Pour les CPU Intel, un paquet supplémentaire, microcode_ctl, est requis. Le "
"paquet choisi est la version hébergée sur Fedora — il y a une version "
"alternative sur github du même empaqueteur, mais qui laisse une ancienne "
"version redondante d'un container de micro-code AMD, et qui requiert aussi "
"le paquet unzip."

#. type: Content of: <sect1><sect2><sect3><para>
#: blfs-en/postlfs/config/firmware.xml:139
msgid ""
"Download the latest version from the link above; when last checked this was "
"2.1-8 and is updated when Intel releases new microcode."
msgstr ""
"Téléchargez la dernière version depuis le lien précédent&nbsp;; à la "
"dernière vérification, il était en version 2.1-8 et est mis à jour quand "
"Intel publie de nouveaux micro-codes."

#. type: Content of: <sect1><sect2><sect3><para>
#: blfs-en/postlfs/config/firmware.xml:142
msgid ""
"This package reformats the microcode supplied by Intel into a format which "
"the kernel can apply. The program <userinput>intel-"
"microcode2ucode</userinput> is built and invoked by the Makefile to create "
"the individual firmware blobs, so there is no reason to install it."
msgstr ""
"Ce paquet reformate le micro-code fourni par Intel dans un format que le "
"noyau peut appliquer. Le programme <userinput>intel-"
"microcode2ucode</userinput> est construit et invoqué par le Makefile pour "
"créer des blobs individuels de micro-codes, donc il n'y a pas de raison de "
"l'installer."

#. type: Content of: <sect1><sect2><sect3><para>
#: blfs-en/postlfs/config/firmware.xml:148
msgid ""
"Begin by extracting the tarball and changing to the directory it created.  "
"Then change to the source directory and run:"
msgstr ""
"Commencez par extraire l'archive et allez dans le répertoire créé. Ensuite "
"allez dans le répertoire des sources et lancez&nbsp;:"

#. type: Content of: <sect1><sect2><sect3><screen>
#: blfs-en/postlfs/config/firmware.xml:151
#, no-wrap
msgid "<userinput>make</userinput>"
msgstr "<userinput>make</userinput>"

#. type: Content of: <sect1><sect2><sect3><para>
#: blfs-en/postlfs/config/firmware.xml:153
msgid ""
"This creates various blobs with names in the form XX-YY-ZZ. Now you need to "
"determine your processor's identity, to see if there is any microcode for "
"it. Determine the decimal values of the cpu family, model and stepping by "
"running:"
msgstr ""
"Cela crée de nombreux blobs avec des noms de la forme XX-YY-ZZ. Maintenant "
"vous devez déterminer l'identité de votre processeur, pour vois s'il y a un "
"micro-code pour lui. Déterminez les valeurs décimales de la famille du CPU, "
"le modèle, et le pas en lançant&nbsp;:"

#. type: Content of: <sect1><sect2><sect3><screen>
#: blfs-en/postlfs/config/firmware.xml:158
#, no-wrap
msgid "<userinput>head -n7 /proc/cpuinfo</userinput>"
msgstr "<userinput>head -n7 /proc/cpuinfo</userinput>"

#. type: Content of: <sect1><sect2><sect3><para>
#: blfs-en/postlfs/config/firmware.xml:160
msgid ""
"Now convert the cpu family, model and stepping to pairs of hexadecimal "
"digits. For a SandyBridge i3-2120 (described as Intel(R) Core(TM) i3-2120 "
"CPU) the relevant values are cpu family 6, model 42, stepping 7 so in this "
"case the required identification is 06-2a-07. A look at the blobs will show "
"that there is one for this CPU (although it might have already been applied "
"by the BIOS). If there is a blob for your system then test if it will be "
"applied by copying it (replace &lt;XX-YY-ZZ&gt; by the identifier for your "
"machine) to where the kernel can find it:"
msgstr ""
"Maintenant convertissez la famille du CPU, le modèle et le pas en paire de "
"digits hexadécimal. Pour un SandyBridge i3-2120 (décrit comme un Intel(R) "
"Core(TM) i3-2120 CPU) les bonnes valeurs sont famille de CPU 6, modèle 42, "
"pas 7 donc dans ce cas l'identification requise est 06-2a-07. Un coup d’œil "
"sur les blobs montrera qu'il y en a un pour ce CPU (cependant qui semble "
"déjà appliqué par le BIOS). S'il y a un blob pour votre système alors testez"
" s'il peut être appliqué en le copiant (remplacez &lt;XX-YY-ZZ&gt; par "
"l'identifiant de votre machine) où le noyau pourra le trouver."

#. type: Content of: <sect1><sect2><sect3><screen>
#: blfs-en/postlfs/config/firmware.xml:169
#, no-wrap
msgid ""
"<userinput>mkdir -pv /lib/firmware/intel-ucode\n"
"cp -v &lt;XX-YY-ZZ&gt; /lib/firmware/intel-ucode</userinput>"
msgstr ""
"<userinput>mkdir -pv /lib/firmware/intel-ucode\n"
"cp -v &lt;XX-YY-ZZ&gt; /lib/firmware/intel-ucode</userinput>"

#. type: Content of: <sect1><sect2><sect3><para>
#: blfs-en/postlfs/config/firmware.xml:172
msgid ""
"Now that the Intel microcode has been prepared, use the following options "
"when you configure the kernel to try late loading of the Intel microcode:"
msgstr ""
"Maintenant que le micro-code Intel a été préparé, utilisez les options "
"suivantes quand vous configurez le noyau pour essayer le chargement \"le "
"plus tard\" du micro-code Intel&nbsp;:"

#. type: Content of: <sect1><sect2><sect3><screen>
#: blfs-en/postlfs/config/firmware.xml:176
#, no-wrap
msgid ""
"<literal>Processor type and features  ---&gt;\n"
"  &lt;M&gt; CPU microcode loading support  [CONFIG_MICROCODE]\n"
"  [*]      Intel microcode loading support [CONFIG_MICROCODE_INTEL]</literal>"
msgstr ""
"<literal>Processor type and features  ---&gt;\n"
"  &lt;M&gt; CPU microcode loading support  [CONFIG_MICROCODE]\n"
"  [*]      Intel microcode loading support [CONFIG_MICROCODE_INTEL]</literal>"

#. type: Content of: <sect1><sect2><sect3><para>
#: blfs-en/postlfs/config/firmware.xml:180
msgid ""
"After you have successfully booted the new system, use the command "
"<userinput>dmesg | grep microcode</userinput> and study the results to see "
"if the message new patch_level appears.  This example from the SandyBridge "
"i3:"
msgstr ""
"Après que vous ayez démarré le nouveau système avec succès, utilisez la "
"commande <userinput>dmesg | grep microcode</userinput> et étudiez les "
"résultats pour voir si le message patch_level apparaît. Voici un exemple "
"pour le SandyBridge i3&nbsp;:"

#. type: Content of: <sect1><sect2><sect3><screen>
#: blfs-en/postlfs/config/firmware.xml:185
#, no-wrap
msgid ""
"<literal>[    0.059906] perf_event_intel: PEBS disabled due to CPU errata, please upgrade microcode\n"
"[    2.603083] microcode: CPU0 sig=0x206a7, pf=0x2, revision=0x23\n"
"[    2.669378] microcode: CPU0 sig=0x206a7, pf=0x2, revision=0x23\n"
"[    2.669994] microcode: CPU0 updated to revision 0x29, date = 2013-06-12\n"
"[    2.670069] microcode: CPU1 sig=0x206a7, pf=0x2, revision=0x23\n"
"[    2.670139] microcode: CPU1 sig=0x206a7, pf=0x2, revision=0x23\n"
"[    2.670501] microcode: CPU1 updated to revision 0x29, date = 2013-06-12\n"
"[    2.670509] microcode: CPU2 sig=0x206a7, pf=0x2, revision=0x23\n"
"[    2.670540] microcode: CPU2 sig=0x206a7, pf=0x2, revision=0x23\n"
"[    2.670917] microcode: CPU2 updated to revision 0x29, date = 2013-06-12\n"
"[    2.670955] microcode: CPU3 sig=0x206a7, pf=0x2, revision=0x23\n"
"[    2.670988] microcode: CPU3 sig=0x206a7, pf=0x2, revision=0x23\n"
"[    2.671348] microcode: CPU3 updated to revision 0x29, date = 2013-06-12\n"
"[    2.671356] perf_event_intel: PEBS enabled due to microcode update\n"
"[    2.671412] microcode: Microcode Update Driver: v2.00 &lt;tigran@aivazian.fsnet.co.uk&gt;, Peter Oruba</literal>"
msgstr ""
"<literal>[    0.059906] perf_event_intel: PEBS disabled due to CPU errata, please upgrade microcode\n"
"[    2.603083] microcode: CPU0 sig=0x206a7, pf=0x2, revision=0x23\n"
"[    2.669378] microcode: CPU0 sig=0x206a7, pf=0x2, revision=0x23\n"
"[    2.669994] microcode: CPU0 updated to revision 0x29, date = 2013-06-12\n"
"[    2.670069] microcode: CPU1 sig=0x206a7, pf=0x2, revision=0x23\n"
"[    2.670139] microcode: CPU1 sig=0x206a7, pf=0x2, revision=0x23\n"
"[    2.670501] microcode: CPU1 updated to revision 0x29, date = 2013-06-12\n"
"[    2.670509] microcode: CPU2 sig=0x206a7, pf=0x2, revision=0x23\n"
"[    2.670540] microcode: CPU2 sig=0x206a7, pf=0x2, revision=0x23\n"
"[    2.670917] microcode: CPU2 updated to revision 0x29, date = 2013-06-12\n"
"[    2.670955] microcode: CPU3 sig=0x206a7, pf=0x2, revision=0x23\n"
"[    2.670988] microcode: CPU3 sig=0x206a7, pf=0x2, revision=0x23\n"
"[    2.671348] microcode: CPU3 updated to revision 0x29, date = 2013-06-12\n"
"[    2.671356] perf_event_intel: PEBS enabled due to microcode update\n"
"[    2.671412] microcode: Microcode Update Driver: v2.00 &lt;tigran@aivazian.fsnet.co.uk&gt;, Peter Oruba</literal>"

#. type: Content of: <sect1><sect2><sect3><para>
#: blfs-en/postlfs/config/firmware.xml:201
#: blfs-en/postlfs/config/firmware.xml:239
msgid ""
"If the microcode was not updated, there is no new microcode for this "
"system's processor. If it did get updated, you can now proceed to <xref "
"linkend='early-microcode'/>."
msgstr ""
"Si le micro-code n'a pas été mis à jour, il n'y a pas de nouveau micro-code "
"pour ce processeur. S'il a été mis à jour, vous pouvez maintenant faire la "
"section intitulée <xref linkend='early-microcode'/>."

#. type: Content of: <sect1><sect2><sect3><title>
#: blfs-en/postlfs/config/firmware.xml:208
msgid "AMD Microcode for the CPU"
msgstr "Micro-code AMD pour le CPU"

#. type: Content of: <sect1><sect2><sect3><para>
#: blfs-en/postlfs/config/firmware.xml:210
msgid ""
"Begin by downloading a container of firmware for your CPU family from <ulink"
" url='&sources-anduin-http;/linux-firmware/amd-ucode/'/>.  The family is "
"always specified in hex. Families 10h to 14h (16 to 20)  are in "
"microcode_amd.bin.  Families 15h and 16h have their own containers.  Create "
"the required directory and put the firmware you downloaded into it as the "
"<systemitem class=\"username\">root</systemitem> user:"
msgstr ""
"Commencez par télécharger un paquet de firmware pour votre famille de CPU "
"sur <ulink url='&sources-anduin-http;/linux-firmware/amd-ucode/'/>. La "
"famille est toujours spécifiées en hexadécimal. Les familles 10h à 14h (16 à"
" 20) sont dans microcode_amd.bin. Les familles 15h et 16h ont leur propre "
"paquet. Créez le répertoire requis et placez le firmware télécharger dedans "
"en tant qu'utilisateur <systemitem "
"class=\"username\">root</systemitem>&nbsp;:"

#. type: Content of: <sect1><sect2><sect3><screen>
#: blfs-en/postlfs/config/firmware.xml:218
#, no-wrap
msgid ""
"<userinput>mkdir -pv /lib/firmware/amd-ucode\n"
"cp -v microcode_amd* /lib/firmware/amd-ucode</userinput>"
msgstr ""
"<userinput>mkdir -pv /lib/firmware/amd-ucode\n"
"cp -v microcode_amd* /lib/firmware/amd-ucode</userinput>"

#. type: Content of: <sect1><sect2><sect3><para>
#: blfs-en/postlfs/config/firmware.xml:221
msgid ""
"When you configure the kernel, use the following options to try late loading"
" of AMD microcode:"
msgstr ""
"Quand vous configurez le noyau, utilisez les options suivantes pour essayer "
"un chargement \"tard\" du micro-code AMD:"

#. type: Content of: <sect1><sect2><sect3><screen>
#: blfs-en/postlfs/config/firmware.xml:224
#, no-wrap
msgid ""
"<literal>Processor type and features  ---&gt;\n"
"  &lt;M&gt; CPU microcode loading support   [CONFIG_MICROCODE]\n"
"  [*]   AMD microcode loading support [CONFIG_MICROCODE_AMD]</literal>"
msgstr ""
"<literal>Processor type and features  ---&gt;\n"
"  &lt;M&gt; CPU microcode loading support   [CONFIG_MICROCODE]\n"
"  [*]   AMD microcode loading support [CONFIG_MICROCODE_AMD]</literal>"

#. type: Content of: <sect1><sect2><sect3><para>
#: blfs-en/postlfs/config/firmware.xml:228
msgid ""
"After you have successfully booted the new system, use the command "
"<userinput>dmesg | grep microcode</userinput> and study the results to see "
"if the message new patch_level appears, as in this example from an old "
"Athlon(tm) II X2:"
msgstr ""
"Après avoir démarré correctement votre nouveau système, utilisez la commande"
" <userinput>dmesg | grep microcode</userinput> et étudiez le résultat pour "
"voir si le message new patch_level apparaît, comme dans l’exemple suivant "
"provenant l’un vieil Athlon(tm) II X2&nbsp;:"

#. type: Content of: <sect1><sect2><sect3><screen>
#: blfs-en/postlfs/config/firmware.xml:233
#, no-wrap
msgid ""
"<literal>[    4.183907] microcode: CPU0: patch_level=0x010000b6\n"
"[    4.184271] microcode: CPU0: new patch_level=0x010000c8\n"
"[    4.184278] microcode: CPU1: patch_level=0x010000b6\n"
"[    4.184283] microcode: CPU1: new patch_level=0x010000c8\n"
"[    4.184359] microcode: Microcode Update Driver: v2.00 &lt;tigran@aivazian.fsnet.co.uk&gt;, Peter Oruba</literal>"
msgstr ""
"<literal>[    4.183907] microcode: CPU0: patch_level=0x010000b6\n"
"[    4.184271] microcode: CPU0: new patch_level=0x010000c8\n"
"[    4.184278] microcode: CPU1: patch_level=0x010000b6\n"
"[    4.184283] microcode: CPU1: new patch_level=0x010000c8\n"
"[    4.184359] microcode: Microcode Update Driver: v2.00 &lt;tigran@aivazian.fsnet.co.uk&gt;, Peter Oruba</literal>"

#. type: Content of: <sect1><sect2><sect3><title>
#: blfs-en/postlfs/config/firmware.xml:246
msgid "Early loading of microcode"
msgstr "Chargement \"tôt\" du micro-code"

#. type: Content of: <sect1><sect2><sect3><para>
#: blfs-en/postlfs/config/firmware.xml:248
msgid ""
"If you have established that updated microcode is available for your system,"
" it is time to prepare it for early loading. This requires an additional "
"package, <xref linkend='cpio'/>, as well as changes to the kernel config and"
" the creation of an initrd which will need to be added to grub.cfg."
msgstr ""
"Si vous avez établi d'un micro-code mis à jour est disponible pour votre "
"système, il est temps de le préparer pour un chargement \"tôt\". Cela "
"demande un paquet supplémentaire, <xref linkend='cpio'/>, ainsi que des "
"modifications à la configuration du noyau et la création d'un initrd qui "
"devra être ajouté à grub.cfg."

#. type: Content of: <sect1><sect2><sect3><para>
#: blfs-en/postlfs/config/firmware.xml:254
msgid ""
"It does not matter where you prepare the initrd, and once it is working you "
"can apply the same initrd to later LFS systems or newer kernels on this same"
" machine, at least until any newer microcode is released. Use the following "
"commands:"
msgstr ""
"L'endroit ou vous préparez l'initrd n'est pas important, et une fois "
"fonctionnel vous pouvez appliquer le même initrd aux versions futures de LFS"
" ou aux nouveaux noyaux sur cette même machine, au moins jusqu'à ce qu'une "
"nouvelle version du micro-code soit publiée. Utiliser la suite&nbsp;:"

#. type: Content of: <sect1><sect2><sect3><screen>
#: blfs-en/postlfs/config/firmware.xml:259
#, no-wrap
msgid ""
"<userinput>mkdir -p initrd/kernel/x86/microcode\n"
"cd initrd</userinput>"
msgstr ""
"<userinput>mkdir -p initrd/kernel/x86/microcode\n"
"cd initrd</userinput>"

#. type: Content of: <sect1><sect2><sect3><para>
#: blfs-en/postlfs/config/firmware.xml:262
msgid ""
"For an AMD machine, use the following command (replace &lt;MYCONTAINER&gt; "
"with the name of the container for your CPU's family):"
msgstr ""
"Pour une machine AMD, utilisez la commande suivante (remplacez "
"&lt;MYCONTAINER&gt; par le nom du paquet de votre famille de CPU)&nbsp;:"

#. type: Content of: <sect1><sect2><sect3><screen>
#: blfs-en/postlfs/config/firmware.xml:266
#, no-wrap
msgid ""
"<userinput>cp -v /lib/firmware/amd_ucode/&lt;MYCONTAINER&gt; "
"kernel/x86/microcode/AuthenticAMD.bin</userinput>"
msgstr ""
"<userinput>cp -v /lib/firmware/amd_ucode/&lt;MYCONTAINER&gt; "
"kernel/x86/microcode/AuthenticAMD.bin</userinput>"

#. type: Content of: <sect1><sect2><sect3><para>
#: blfs-en/postlfs/config/firmware.xml:268
msgid "Or for an Intel machine copy the appropriate blob using this command:"
msgstr ""
"Ou pour une machine Intel copiez le blob approprié en utilisant cette "
"commande&nbsp;:"

#. type: Content of: <sect1><sect2><sect3><screen>
#: blfs-en/postlfs/config/firmware.xml:270
#, no-wrap
msgid ""
"<userinput>cp -v /lib/firmware/intel-ucode/&lt;XX-YY-ZZ&gt; "
"kernel/x86/microcode/GenuineIntel.bin</userinput>"
msgstr ""
"<userinput>cp -v /lib/firmware/intel-ucode/&lt;XX-YY-ZZ&gt; "
"kernel/x86/microcode/GenuineIntel.bin</userinput>"

#. type: Content of: <sect1><sect2><sect3><para>
#: blfs-en/postlfs/config/firmware.xml:272
msgid "Now prepare the initrd:"
msgstr "Maintenant préparez l'initrd&nbsp;:"

#. type: Content of: <sect1><sect2><sect3><screen>
#: blfs-en/postlfs/config/firmware.xml:274
#, no-wrap
msgid ""
"<userinput>find . | cpio -o -H newc &gt; /boot/microcode.img</userinput>"
msgstr ""
"<userinput>find . | cpio -o -H newc &gt; /boot/microcode.img</userinput>"

#. type: Content of: <sect1><sect2><sect3><para>
#: blfs-en/postlfs/config/firmware.xml:276
msgid ""
"You will now need to reconfigure and rebuild your kernel. It is safer to "
"either add/change the EXTRAVERSION in the kernel's configuration and install"
" the newer kernel with a new name, or else (unless you have a machine which "
"requires an early firmware update) wait for the next SUBLEVEL kernel release"
" so that you can fall back to the existing kernel in the event that "
"something goes wrong."
msgstr ""
"Vous devez maintenant reconfigurer et reconstruire votre noyau. Il est "
"prudent pour chaque d'ajouter/changer l'EXTRAVERSION dans la configuration "
"du noyau et d'installer le nouveau noyau avec un nouveau nom, ou alors (à "
"moins que vous ayez une machine qui requiert une mise à jour du firmware "
"\"tôt\") attendre la prochaine publication SUBLEVEL du noyau de sorte que "
"vous puissiez revenir au noyau existant dans le cas où quelque chose irait "
"mal."

#. type: Content of: <sect1><sect2><sect3><para>
#: blfs-en/postlfs/config/firmware.xml:283
msgid ""
"You will also need to add a new entry to /boot/grub/grub.cfg and here you "
"should add a new line after the linux line within the stanza.  If /boot is a"
" separate mountpoint:"
msgstr ""
"Vous devrez également ajouter une nouvelle entrée à /boot/grub/grub.cfg et "
"vous devrez ajouter une ligne après la ligne linux. Si /boot est dans une "
"partition séparée&nbsp;:"

#. type: Content of: <sect1><sect2><sect3><screen>
#: blfs-en/postlfs/config/firmware.xml:287
#, no-wrap
msgid "<userinput>initrd /microcode.img</userinput>"
msgstr "<userinput>initrd /microcode.img</userinput>"

#. type: Content of: <sect1><sect2><sect3><para>
#: blfs-en/postlfs/config/firmware.xml:289
msgid "or this if it is not:"
msgstr "ou sinon&nbsp;:"

#. type: Content of: <sect1><sect2><sect3><screen>
#: blfs-en/postlfs/config/firmware.xml:291
#, no-wrap
msgid "<userinput>initrd /boot/microcode.img</userinput>"
msgstr "<userinput>initrd /boot/microcode.img</userinput>"

#. type: Content of: <sect1><sect2><sect3><para>
#: blfs-en/postlfs/config/firmware.xml:293
msgid "You must also change the kernel config:"
msgstr "Vous devez également modifier la config du noyau&nbsp;:"

#. type: Content of: <sect1><sect2><sect3><screen>
#: blfs-en/postlfs/config/firmware.xml:295
#, no-wrap
msgid ""
"<literal>General Setup ---&gt;\n"
"  [y] Initial RAM filesystem and RAM disk (initramfs/initrd) support [CONFIG_BLK_DEV_INITRD]\n"
"  [y] CPU microcode loading support                                  [CONFIG_MICROCODE]</literal>"
msgstr ""
"<literal>General Setup ---&gt;\n"
"  [y] Initial RAM filesystem and RAM disk (initramfs/initrd) support [CONFIG_BLK_DEV_INITRD]\n"
"  [y] CPU microcode loading support                                  [CONFIG_MICROCODE]</literal>"

#. type: Content of: <sect1><sect2><sect3><para>
#: blfs-en/postlfs/config/firmware.xml:299
msgid ""
"Retain the setting for INTEL or AMD microcode. When you have saved the "
".config file, either CONFIG_MICROCODE_INTEL_EARLY=y or "
"CONFIG_MICROCODE_AMD_EARLY=y should be set, together with "
"CONFIG_MICROCODE_EARLY=y."
msgstr ""
"Gardez les préférences pour le micro-code INTEL ou AMD. Quand vous avez "
"sauvegardé le fichier .config, soit CONFIG_MICROCODE_INTEL_EARLY=y ou "
"CONFIG_MICROCODE_AMD_EARLY=y doit être initialisé, avec "
"CONFIG_MICROCODE_EARLY=y."

#. type: Content of: <sect1><sect2><sect3><para>
#: blfs-en/postlfs/config/firmware.xml:304
msgid ""
"When you have installed and booted this kernel, you should check the output "
"of dmesg to confirm that the early load worked. The places and times where "
"this happens are very different in AMD and Intel machines.  First, an Intel "
"example where a development kernel is being tested, showing that the first "
"notification comes before the kernel version is mentioned:"
msgstr ""
"Quand vous avez installé et démarré ce noyau, vous pouvez vérifier la sortie"
" de dmesg pour confirmer que le chargement \"tôt\" fonctionne. Les endroits "
"et les temps ou cela se passent sont très différents sur les machines AMD et"
" Intel. En premier, un exemple d'Intel ou un noyau de développement est "
"testé, regardez que la première notification vient avant que la version du "
"noyau soit indiquée:"

#. type: Content of: <sect1><sect2><sect3><screen>
#: blfs-en/postlfs/config/firmware.xml:311
#, no-wrap
msgid ""
"<literal>[    0.000000] CPU0 microcode updated early to revision 0x29, date = 2013-06-12\n"
"[    0.000000] Linux version 4.0.0-rc6 (ken@jtm1) (gcc version 4.9.2 (GCC) )\n"
"               #3 SMP PREEMPT Mon Mar 30 21:26:02 BST 2015\n"
"[    0.000000] Command line: BOOT_IMAGE=/vmlinuz-4.0.0-rc6-sda13 root=/dev/sda13 ro\n"
"...\n"
"[    0.103091] CPU1 microcode updated early to revision 0x29, date = 2013-06-12\n"
"[    0.113241]  #2\n"
"[    0.134631]  #3\n"
"[    0.147821] x86: Booted up 1 node, 4 CPUs\n"
"[    0.147936] smpboot: Total of 4 processors activated (26338.66 BogoMIPS)\n"
"...\n"
"[    0.272643] microcode: CPU0 sig=0x206a7, pf=0x2, revision=0x29\n"
"[    0.272709] microcode: CPU1 sig=0x206a7, pf=0x2, revision=0x29\n"
"[    0.272775] microcode: CPU2 sig=0x206a7, pf=0x2, revision=0x29\n"
"[    0.272842] microcode: CPU3 sig=0x206a7, pf=0x2, revision=0x29\n"
"[    0.272941] microcode: Microcode Update Driver: v2.00 &lt;tigran@aivazian.fsnet.co.uk&gt;, Peter Oruba</literal>"
msgstr ""
"<literal>[    0.000000] CPU0 microcode updated early to revision 0x29, date = 2013-06-12\n"
"[    0.000000] Linux version 4.0.0-rc6 (ken@jtm1) (gcc version 4.9.2 (GCC) )\n"
"               #3 SMP PREEMPT Mon Mar 30 21:26:02 BST 2015\n"
"[    0.000000] Command line: BOOT_IMAGE=/vmlinuz-4.0.0-rc6-sda13 root=/dev/sda13 ro\n"
"...\n"
"[    0.103091] CPU1 microcode updated early to revision 0x29, date = 2013-06-12\n"
"[    0.113241]  #2\n"
"[    0.134631]  #3\n"
"[    0.147821] x86: Booted up 1 node, 4 CPUs\n"
"[    0.147936] smpboot: Total of 4 processors activated (26338.66 BogoMIPS)\n"
"...\n"
"[    0.272643] microcode: CPU0 sig=0x206a7, pf=0x2, revision=0x29\n"
"[    0.272709] microcode: CPU1 sig=0x206a7, pf=0x2, revision=0x29\n"
"[    0.272775] microcode: CPU2 sig=0x206a7, pf=0x2, revision=0x29\n"
"[    0.272842] microcode: CPU3 sig=0x206a7, pf=0x2, revision=0x29\n"
"[    0.272941] microcode: Microcode Update Driver: v2.00 &lt;tigran@aivazian.fsnet.co.uk&gt;, Peter Oruba</literal>"

#. type: Content of: <sect1><sect2><sect3><para>
#: blfs-en/postlfs/config/firmware.xml:328
msgid ""
"A second AMD example is where the machine was running a stable kernel on an "
"older version of LFS. Note that here there is no mention of the previous "
"microcode version &mdash; compare this output to the AMD late loading "
"messages (above) from the same machine:"
msgstr ""
"Un deuxième exemple AMD ou la machine lance un noyau stable sur une ancienne"
" version de LFS. Notez que ici, il n'est pas indiqué la version du micro-"
"code précédent &mdash; comparez cette sortie aux messages de chargement "
"\"tard\" (plus haut) de la même machine&nbsp;:"

#. type: Content of: <sect1><sect2><sect3><screen>
#: blfs-en/postlfs/config/firmware.xml:333
#, no-wrap
msgid ""
"<literal>[    0.000000] Linux version 3.18.11 (ken@milliways) (gcc version 4.9.1 (GCC) )\n"
"               #4 SMP Thu Apr 9 21:51:05 BST 2015\n"
"[    0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.18.11-sda5 root=/dev/sda5 video=800x600 ro\n"
"...\n"
"[    0.584009] Trying to unpack rootfs image as initramfs...\n"
"[    0.584092] microcode: updated early to new patch_level=0x010000c8\n"
"...\n"
"[    0.586733] microcode: CPU0: patch_level=0x010000c8\n"
"[    0.586778] microcode: CPU1: patch_level=0x010000c8\n"
"[    0.586866] microcode: Microcode Update Driver: v2.00 &lt;tigran@aivazian.fsnet.co.uk&gt;, Peter Oruba</literal>"
msgstr ""
"<literal>[    0.000000] Linux version 3.18.11 (ken@milliways) (gcc version 4.9.1 (GCC) )\n"
"               #4 SMP Thu Apr 9 21:51:05 BST 2015\n"
"[    0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.18.11-sda5 root=/dev/sda5 video=800x600 ro\n"
"...\n"
"[    0.584009] Trying to unpack rootfs image as initramfs...\n"
"[    0.584092] microcode: updated early to new patch_level=0x010000c8\n"
"...\n"
"[    0.586733] microcode: CPU0: patch_level=0x010000c8\n"
"[    0.586778] microcode: CPU1: patch_level=0x010000c8\n"
"[    0.586866] microcode: Microcode Update Driver: v2.00 &lt;tigran@aivazian.fsnet.co.uk&gt;, Peter Oruba</literal>"

#. type: Content of: <sect1><sect2><title>
#: blfs-en/postlfs/config/firmware.xml:349
msgid "Firmware for Video Cards"
msgstr "Firmware pour les cartes vidéo"

#. type: Content of: <sect1><sect2><sect3><title>
#: blfs-en/postlfs/config/firmware.xml:352
msgid "Firmware for ATI video chips (R600 and later)"
msgstr "Firmware pour les puces vidéo ATI (R600 et plus)"

#. type: Content of: <sect1><sect2><sect3><para>
#: blfs-en/postlfs/config/firmware.xml:354
msgid ""
"These instructions do NOT apply to old radeons before the R600 family. For "
"those, the firmware is in the kernel's <filename "
"class='directory'>/lib/firmware/</filename> directory. Nor do they apply if "
"you intend to avoid a graphical setup such as Xorg and are content to use "
"the default 80x25 display rather than a framebuffer."
msgstr ""
"Ces instructions NE s'applique pas aux anciennes radeons avant la famille "
"R600. Pour elles, le firmware est dans le répertoire du noyau <filename "
"class='directory'>/lib/firmware/</filename>. Appliquez les seulement si vous"
" prévoyez d'éviter une configuration graphique tels que Xorg et que vous "
"voulez vous contenter d'utiliser l'affichage 80x25 par défaut plutôt qu'un "
"framebuffer."

#. type: Content of: <sect1><sect2><sect3><para>
#: blfs-en/postlfs/config/firmware.xml:360
msgid ""
"Early radeon devices only needed a single 2K blob of firmware.  Recent "
"devices need several different blobs, and some of them are much bigger. The "
"total size of the radeon firmware directory is over 500K &mdash; on a large "
"modern system you can probably spare the space, but it is still redundant to"
" install all the unused files each time you build a system."
msgstr ""
"Les périphériques radeon plus anciens demandaient seulement un simple blob "
"de 2Ko. Les périphériques récents ont besoin de plusieurs blobs différents, "
"et certain d'entre eux sont plus gros. La taille totale du répertoire des "
"firmwares radeon est de plus de 500 ko — sur un gros système moderne vous "
"pouvez probablement utiliser cet espace, mais cela reste redondant "
"d'installer tous les fichiers inutiles chaque fois que vous construisez un "
"système."

#. type: Content of: <sect1><sect2><sect3><para>
#: blfs-en/postlfs/config/firmware.xml:366
msgid ""
"A better approach is to install <xref linkend='pciutils'/> and then use "
"<userinput>lspci</userinput> to identify which VGA controller is installed."
msgstr ""
"Une meilleure approche est d'installer<xref linkend='pciutils'/> et ensuite "
"utiliser <userinput>lspci</userinput> pour identifier quel controleur VGA "
"est installé."

#. type: Content of: <sect1><sect2><sect3><para>
#: blfs-en/postlfs/config/firmware.xml:370
msgid ""
"With that information, check the RadeonFeature page of the Xorg wiki for "
"<ulink url=\"http://wiki.x.org/wiki/RadeonFeature/#index5h2\">Decoder ring "
"for engineering vs marketing names</ulink> to identify the family (you may "
"need to know this for the Xorg driver in BLFS &mdash; Southern Islands and "
"Sea Islands use the radeonsi driver) and the specific model."
msgstr ""
"Avec cette information, vérifiez la page RadeonFeature du wiki Xorg <ulink "
"url=\"http://wiki.x.org/wiki/RadeonFeature/#index5h2\">Decoder ring for "
"engineering vs marketing names</ulink> pour identifier la famille (vous "
"aurez besoin de savoir cela pour identifier le pilote Xorg dans BLFS — "
"Southern Islands et Sea Islands utilise le pilote radeonsi) et le modèle "
"spécifique."

#. type: Content of: <sect1><sect2><sect3><para>
#: blfs-en/postlfs/config/firmware.xml:376
msgid ""
"Now that you know which controller you are using, consult the <ulink "
"url=\"https://wiki.gentoo.org/wiki/Radeon#Firmware\">Radeon</ulink> page of "
"the Gentoo wiki which has a table listing the required firmware blobs for "
"the various chipsets. Note that Southern Islands and Sea Islands chips use "
"different firmware for kernel 3.17 and later compared to earlier kernels. "
"Identify and download the required blobs then install them:"
msgstr ""
"Maintenant que vous savez quel contrôleur vous allez utiliser, consultez la "
"page <ulink "
"url=\"https://wiki.gentoo.org/wiki/Radeon#Firmware\">Radeon</ulink> du wiki "
"Gentoo qui a un tableau listant les blobs de firmware requis pour les "
"différentes puces. Notez que les puces Southern Islands et Sea Islands "
"utilise des firmwares différents pour les noyaux 3.17 et supérieur en "
"comparaison des kernels antérieurs. Identifiez et téléchargez les blobs "
"requis et ensuite installez les&nbsp;:"

#. type: Content of: <sect1><sect2><sect3><screen>
#: blfs-en/postlfs/config/firmware.xml:383
#, no-wrap
msgid ""
"<userinput>mkdir -pv /lib/firmware/radeon\n"
"cp -v &lt;YOUR_BLOBS&gt; /lib/firmware/radeon</userinput>"
msgstr ""
"<userinput>mkdir -pv /lib/firmware/radeon\n"
"cp -v &lt;YOUR_BLOBS&gt; /lib/firmware/radeon</userinput>"

#. type: Content of: <sect1><sect2><sect3><para>
#: blfs-en/postlfs/config/firmware.xml:386
msgid ""
"There are actually two ways of installing this firmware. BLFS, in the "
"'Kernel Configuration for additional firmware' section part of the <xref "
"linkend=\"xorg-ati-driver\"/> section gives an example of compiling the "
"firmware into the kernel - that is slightly faster to load, but uses more "
"kernel memory. Here we will use the alternative method of making the radeon "
"driver a module. In your kernel config set the following:"
msgstr ""
"Il y a en fait deux façons d'installer ces firmwares. BLFS, dans le sous-"
"chapitre 'Configuration du noyau pour les firmwares supplémentaires' du "
"chapitre <xref linkend=\"xorg-ati-driver\"/> donne un exemple de compilation"
" des firmwares dans le noyau - c'est légèrement plus rapide à charger, mais "
"utilises plus de mémoire pour le noyau. Ici nous utiliserons la méthode "
"alternative en faisant un module du pilote radeon. Dans votre configuration "
"du noyau initialisez la suite&nbsp;:"

#. type: Content of: <sect1><sect2><sect3><screen>
#: blfs-en/postlfs/config/firmware.xml:393
#, no-wrap
msgid ""
"<literal>Device Drivers ---&gt;\n"
"  Graphics support ---&gt;\n"
"      Direct Rendering Manager ---&gt;\n"
"        &lt;*&gt; Direct Rendering Manager (XFree86 ... support)  [CONFIG_DRM]\n"
"      &lt;m&gt; ATI Radeon                                        [CONFIG_DRM_RADEON]</literal>"
msgstr ""
"<literal>Device Drivers ---&gt;\n"
"  Graphics support ---&gt;\n"
"      Direct Rendering Manager ---&gt;\n"
"        &lt;*&gt; Direct Rendering Manager (XFree86 ... support)  [CONFIG_DRM]\n"
"      &lt;m&gt; ATI Radeon                                        [CONFIG_DRM_RADEON]</literal>"

#. type: Content of: <sect1><sect2><sect3><para>
#: blfs-en/postlfs/config/firmware.xml:399
msgid ""
"Loading several large blobs from /lib/firmware takes a noticeable time, "
"during which the screen will be blank. If you do not enable the penguin "
"framebuffer logo, or change the console size by using a bigger font, that "
"probably does not matter. If desired, you can slightly reduce the time if "
"you follow the alternate method of specifying 'y' for CONFIG_DRM_RADEON "
"covered in BLFS at the link above &mdash; you must specify each needed "
"radeon blob if you do that."
msgstr ""
"Le chargement de plusieurs blobs volumineux dans /lib/firmware prend un "
"temps notable, pendant lequel l'écran est blanc. Si vous n'avez pas activé "
"le logo framebuffer du pingouin, ou changé la taille de la console en "
"utilisant une police plus grosse, cela n'a probablement pas d'importance. Si"
" vous le souhaitez, vous pouvez légèrement réduire le temps si vous suivez "
"la méthode alternative en spécifiant 'y' pour CONFIG_DRM_RADEON couvert dans"
" BLFS au lien précédent &mdash; vous devez spécifier chaque blob radeon "
"utile si vous faite cela."

#. type: Content of: <sect1><sect2><sect3><title>
#: blfs-en/postlfs/config/firmware.xml:410
msgid "Firmware for Nvidia video chips"
msgstr "Firmware pour les puces vidéo Nvidia"

#. type: Content of: <sect1><sect2><sect3><para>
#: blfs-en/postlfs/config/firmware.xml:412
msgid ""
"Some Nvidia graphics chips need firmware updates to take advantage of all "
"the card's capability.  These are generally the GeForce 8, 9, 9300, and "
"200-900 series chips.  For more exact information, see <ulink "
"url=\"https://nouveau.freedesktop.org/wiki/VideoAcceleration/#firmware\"> "
"https://nouveau.freedesktop.org/wiki/VideoAcceleration/#firmware</ulink>."
msgstr ""
"Certaines puces graphiques Nvidia requièrent une mise à jour de leur "
"firmware pour tirer parti de toutes les capacités de la carte. Ce sont "
"généralement les puces des séries GeForce 8, 9, 9300 et 200-900. Pour de "
"plus amples informations, visitez <ulink "
"url=\"https://nouveau.freedesktop.org/wiki/VideoAcceleration/#firmware\">https://nouveau.freedesktop.org/wiki/VideoAcceleration/#firmware</ulink>."

#. type: Content of: <sect1><sect2><sect3><para>
#: blfs-en/postlfs/config/firmware.xml:418
msgid "First, the kernel Nvidia driver must be activated:"
msgstr "Tout d'abord, le pilote Nvidia doit être activé dans le noyau&nbsp;:"

#. type: Content of: <sect1><sect2><sect3><screen>
#: blfs-en/postlfs/config/firmware.xml:420
#, no-wrap
msgid ""
"<literal>Device Drivers ---&gt;\n"
"  Graphics support ---&gt;\n"
"      Direct Rendering Manager ---&gt;\n"
"        &lt;*&gt; Direct Rendering Manager (XFree86 ... support)  [CONFIG_DRM]\n"
"      &lt;*/m&gt; Nouveau (NVIDIA) cards                          [CONFIG_DRM_NOUVEAU]</literal>"
msgstr ""
"<literal>Device Drivers ---&gt;\n"
"  Graphics support ---&gt;\n"
"      Direct Rendering Manager ---&gt;\n"
"        &lt;*&gt; Direct Rendering Manager (XFree86 ... support)  [CONFIG_DRM]\n"
"      &lt;*/m&gt; Nouveau (NVIDIA) cards                          [CONFIG_DRM_NOUVEAU]</literal>"

#. type: Content of: <sect1><sect2><sect3><para>
#: blfs-en/postlfs/config/firmware.xml:426
msgid "The steps to install the Nvidia firmware are:"
msgstr "Les étapes pour installer le firmware Nvidia sont&nbsp;:"

#. type: Content of: <sect1><sect2><sect3><screen>
#: blfs-en/postlfs/config/firmware.xml:428
#, no-wrap
msgid ""
"<userinput>wget https://raw.github.com/imirkin/re-vp2/master/extract_firmware.py\n"
"wget http://us.download.nvidia.com/XFree86/Linux-x86/325.15/NVIDIA-Linux-x86-325.15.run\n"
"sh NVIDIA-Linux-x86-325.15.run --extract-only\n"
"python extract_firmware.py \n"
"mkdir -p /lib/firmware/nouveau\n"
"cp -d nv* vuc-* /lib/firmware/nouveau/</userinput>"
msgstr ""
"<userinput>wget https://raw.github.com/imirkin/re-vp2/master/extract_firmware.py\n"
"wget http://us.download.nvidia.com/XFree86/Linux-x86/325.15/NVIDIA-Linux-x86-325.15.run\n"
"sh NVIDIA-Linux-x86-325.15.run --extract-only\n"
"python extract_firmware.py \n"
"mkdir -p /lib/firmware/nouveau\n"
"cp -d nv* vuc-* /lib/firmware/nouveau/</userinput>"

#. type: Content of: <sect1><sect2><title>
#: blfs-en/postlfs/config/firmware.xml:439
msgid "Firmware for Network Interfaces"
msgstr "Firmware pour les interfaces réseaux"

#. type: Content of: <sect1><sect2><para>
#: blfs-en/postlfs/config/firmware.xml:441
msgid ""
"The kernel likes to load firmware for some network drivers, particularly "
"those from Realtek (the /lib/linux-firmware/rtl_nic/) directory, but they "
"generally appear to work without it. Therefore, you can boot the kernel, "
"check dmesg for messages about this missing firmware, and if necessary "
"download the firmware and put it in the specified directory in /lib/firmware"
" so that it will be found on subsequent boots. Note that with current "
"kernels this works whether or not the driver is compiled in or built as a "
"module, there is no need to build this firmware into the kernel.  Here is an"
" example where the R8169 driver has been compiled in but the firmware was "
"not made available. Once the firmware had been provided, there was no "
"mention of it on later boots."
msgstr ""
"Le noyau aime charger des firmware pour quelques pilotes réseau, "
"particulièrement ceux du répertoire Realtek (/lib/linux-firmware/rtl_nic/), "
"mais il apparaît généralement que cela fonctionne sans. Cependant, vous "
"pouvez démarrer le noyau, vérifiez dmesg pour les messages à propos de "
"firmwares manquants, et si nécessaire télécharger les firmwares et les "
"mettre dans un répertoire spécifique dans /lib/firmware afin qu'ils puissent"
" être trouvés pendant la séquence de démarrage. Notez qu'avez les noyaux "
"actuels cela fonctionne que le pilote soit compilé dedans ou construit comme"
" un module, il n'est pas utile de construire ce firmware dans le noyau. Ici "
"un exemple ou le pilote R8169 a été compilé dedans mais le firmware n'est "
"pas disponible. Une fois que le firmware a été fourni, il n'y est plus fait "
"mention dans les démarrages suivants."

#. type: Content of: <sect1><sect2><screen>
#: blfs-en/postlfs/config/firmware.xml:453
#, no-wrap
msgid ""
"<literal>dmesg | grep firmware | grep r8169\n"
"[    7.018028] r8169 0000:01:00.0: Direct firmware load for rtl_nic/rtl8168g-2.fw failed with error -2\n"
"[    7.018036] r8169 0000:01:00.0 eth0: unable to load firmware patch rtl_nic/rtl8168g-2.fw (-2)</literal>"
msgstr ""
"<literal>dmesg | grep firmware | grep r8169\n"
"[    7.018028] r8169 0000:01:00.0: Direct firmware load for rtl_nic/rtl8168g-2.fw failed with error -2\n"
"[    7.018036] r8169 0000:01:00.0 eth0: unable to load firmware patch rtl_nic/rtl8168g-2.fw (-2)</literal>"

#. type: Content of: <sect1><sect2><title>
#: blfs-en/postlfs/config/firmware.xml:460
msgid "Firmware for Other Devices"
msgstr "Firmware pour les autres périphériques"

#. type: Content of: <sect1><sect2><para>
#: blfs-en/postlfs/config/firmware.xml:462
msgid ""
"Identifying the correct firmware will typically require you to install <xref"
" linkend='pciutils'/>, and then use <userinput>lspci</userinput> to identify"
" the device. You should then search online to check which module it uses, "
"which firmware, and where to obtain the firmware &mdash; not all of it is in"
" linux-firmware."
msgstr ""
"Pour identifier le bon firmware vous devrez normallement install <xref "
"linkend='pciutils'/> puis utiliser <userinput>lspci</userinput> pour "
"identifier le matériel. Vous devriez ensuite chercher en ligne pour vérifier"
" le module qu’il utilise, quel firmware et où obtenir le firmware &mdash; "
"ils ne sont pas tous dans linux-firmware."

#. type: Content of: <sect1><sect2><para>
#: blfs-en/postlfs/config/firmware.xml:468
msgid ""
"If possible, you should begin by using a wired connection when you first "
"boot your LFS system. To use a wireless connection you will need to use a "
"network tools such as <xref linkend='wireless_tools'/> and <xref "
"linkend='wpa_supplicant'/>."
msgstr ""
"Si possible, vous pouvez commencer par utiliser une connexion filaire quand "
"vous démarrez la première fois votre système LFS. Pour utiliser une "
"connexion sans fils vous aurez besoin d'utiliser des outils réseau tel que "
"<xref linkend='wireless_tools'/> et <xref linkend='wpa_supplicant'/>."

#. type: Content of: <sect1><sect2><para>
#: blfs-en/postlfs/config/firmware.xml:473
msgid ""
"Firmware may also be needed for other devices such as some SCSI controllers,"
" bluetooth adaptors, or TV recorders. The same principles apply."
msgstr ""
"Les firmwares peuvent aussi être utiles pour d'autres périphériques comme "
"les contrôleurs SCSI, les adaptateurs Bluetooth, ou les enregistreurs TV. "
"Les mêmes principes s'appliquent."