Rev 7210 | Rev 7220 | Go to most recent revision | Details | Compare with Previous | Last modification | View Log | RSS feed
Rev | Author | Line No. | Line |
---|---|---|---|
7156 | jlepiller | 1 | # SOME DESCRIPTIVE TITLE |
2 | # Copyright (C) YEAR Free Software Foundation, Inc. |
||
3 | # This file is distributed under the same license as the PACKAGE package. |
||
4 | # FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. |
||
5 | # |
||
6 | msgid "" |
||
7 | msgstr "" |
||
8 | "Project-Id-Version: PACKAGE VERSION\n" |
||
7209 | jlepiller | 9 | "POT-Creation-Date: 2016-12-04 04:10+0100\n" |
10 | "PO-Revision-Date: 2016-12-04 17:14+0000\n" |
||
7156 | jlepiller | 11 | "Last-Translator: roptat <roptat@lepiller.eu>\n" |
12 | "Language-Team: LANGUAGE <LL@li.org>\n" |
||
13 | "MIME-Version: 1.0\n" |
||
14 | "Content-Type: text/plain; charset=UTF-8\n" |
||
15 | "Content-Transfer-Encoding: 8bit\n" |
||
7210 | jlepiller | 16 | "Language: fr\n" |
7156 | jlepiller | 17 | "Plural-Forms: nplurals=2; plural=(n > 1);\n" |
18 | "X-Generator: Pootle 2.7\n" |
||
7209 | jlepiller | 19 | "X-POOTLE-MTIME: 1480871693.765662\n" |
7156 | jlepiller | 20 | |
21 | #. type: Content of: <sect1><sect1info> |
||
22 | #: blfs-en/postlfs/config/firmware.xml:12 |
||
23 | msgid "" |
||
7164 | jlepiller | 24 | "<othername>$LastChangedBy: bdubbs $</othername> <date>$Date: 2016-07-25 " |
25 | "00:52:11 +0200 (Mon, 25 Jul 2016) $</date>" |
||
7156 | jlepiller | 26 | msgstr "" |
7165 | jlepiller | 27 | "<othername>$LastChangedBy: bdubbs $</othername> <date>$Date: 2016-07-25 " |
28 | "00:52:11 +0200 (Mon, 25 Jul 2016) $</date>" |
||
7156 | jlepiller | 29 | |
30 | #. type: Content of: <sect1><title> |
||
31 | #: blfs-en/postlfs/config/firmware.xml:16 |
||
32 | msgid "About Firmware" |
||
33 | msgstr "À propos des Firmwares" |
||
34 | |||
35 | #. type: Content of: <sect1><indexterm><primary> |
||
36 | #: blfs-en/postlfs/config/firmware.xml:19 |
||
37 | msgid "/lib/firmware" |
||
38 | msgstr "/lib/firmware" |
||
39 | |||
40 | #. type: Content of: <sect1><para> |
||
41 | #: blfs-en/postlfs/config/firmware.xml:22 |
||
42 | msgid "" |
||
43 | "On some recent PCs it can be necessary, or desirable, to load firmware to " |
||
7165 | jlepiller | 44 | "make them work at their best. There is a directory, <filename " |
45 | "class=\"directory\">/lib/firmware</filename>, where the kernel or kernel " |
||
46 | "drivers look for firmware images." |
||
7156 | jlepiller | 47 | msgstr "" |
48 | "Sur certains PCs actuels il peut être nécessaire, ou désirable, de charger " |
||
7165 | jlepiller | 49 | "des firmwares pour faire travailler les PC au maximum de leurs possibilités." |
50 | " Le noyau contient un répertoire, <filename " |
||
51 | "class=\"directory\">/lib/firmware</filename>, ou le noyau ou les pilotes du " |
||
52 | "noyau cherche des images de firmware." |
||
7156 | jlepiller | 53 | |
54 | #. type: Content of: <sect1><para> |
||
55 | #: blfs-en/postlfs/config/firmware.xml:27 |
||
56 | msgid "" |
||
7165 | jlepiller | 57 | "Preparing firmware for multiple different machines, as a distro would do, is" |
58 | " outside the scope of this book." |
||
7156 | jlepiller | 59 | msgstr "" |
60 | "Préparer des firmwares pour de multiples machines différente, comme les " |
||
61 | "distributions le font, est en dehors du périmètre de ce livre." |
||
62 | |||
63 | #. type: Content of: <sect1><para> |
||
64 | #: blfs-en/postlfs/config/firmware.xml:30 |
||
65 | msgid "" |
||
66 | "Currently, most firmware can be found at a <userinput>git</userinput> " |
||
7165 | jlepiller | 67 | "repository: <ulink " |
68 | "url=\"http://git.kernel.org/cgit/linux/kernel/git/firmware/linux-" |
||
69 | "firmware.git/tree/\"/>. For convenience, the LFS Project has created a " |
||
70 | "mirror, updated daily, where these firmware files can be accessed via " |
||
71 | "<userinput>wget</userinput> or a web browser at <ulink url=\"&sources-" |
||
7156 | jlepiller | 72 | "anduin-http;/linux-firmware/\"/>." |
73 | msgstr "" |
||
74 | "Actuellement, on peut trouver la plupart des firmwares sur un dépot " |
||
7165 | jlepiller | 75 | "<userinput>git</userinput> : <ulink " |
76 | "url=\"http://git.kernel.org/cgit/linux/kernel/git/firmware/linux-" |
||
77 | "firmware.git/tree/\"/>. Par commodité, le projet LFS a créé un miroir, mis à" |
||
78 | " jour quotidiennement, ou on peut accéder à ces fichiers de firmwares via " |
||
79 | "<userinput>wget</userinput> ou un navigateur web à <ulink url=\"&sources-" |
||
80 | "anduin-http;/linux-firmware/\"/>." |
||
7156 | jlepiller | 81 | |
82 | #. type: Content of: <sect1><para> |
||
83 | #: blfs-en/postlfs/config/firmware.xml:38 |
||
84 | msgid "" |
||
7165 | jlepiller | 85 | "To get the firmware, either point a browser to one of the above repositories" |
86 | " and then download the item(s) which you need, or install " |
||
87 | "<userinput>git</userinput> and clone that repository." |
||
7156 | jlepiller | 88 | msgstr "" |
7209 | jlepiller | 89 | "Pour avoir le microprogramme, vous devez soit aller sur un des dépôts ci-" |
90 | "dessus avec un navigateur pour télécharger le(s) fichier(s) dont vous avez " |
||
91 | "besoin, soit installer <userinput>git</userinput> et cloner ce dépôt." |
||
7156 | jlepiller | 92 | |
93 | #. type: Content of: <sect1><para> |
||
94 | #: blfs-en/postlfs/config/firmware.xml:42 |
||
95 | msgid "" |
||
96 | "For some other firmware, particularly for Intel microcode and certain wifi " |
||
7165 | jlepiller | 97 | "devices, the needed firmware is not available in the above repository. Some" |
98 | " of this will be addressed below, but a search of the Internet for needed " |
||
7156 | jlepiller | 99 | "firmware is sometimes necessary." |
100 | msgstr "" |
||
101 | "Pour certains autres firmwares, particulièrement pour les micro-codes " |
||
102 | "d'Intel, et certains périphériques wi-fi, le firmware recherché n'est pas " |
||
103 | "disponible dans le dépôt précédent. Certains d'entre eux seront ajouté " |
||
104 | "ensuite, mais il est parfois nécessaire de faire une recherche sur internet " |
||
105 | "pour les firmwares souhaités." |
||
106 | |||
107 | #. type: Content of: <sect1><para> |
||
7214 | jlepiller | 108 | #. « convention » et « référencés » ne semblent pas bien accordés en genre. |
7156 | jlepiller | 109 | #: blfs-en/postlfs/config/firmware.xml:47 |
7214 | jlepiller | 110 | #, fuzzy |
7156 | jlepiller | 111 | msgid "" |
112 | "Firmware files are conventionally referred to as blobs because you cannot " |
||
7165 | jlepiller | 113 | "determine what they will do. Note that firmware is distributed under various" |
114 | " different licenses which do not permit disassembly or reverse-engineering." |
||
7156 | jlepiller | 115 | msgstr "" |
116 | "Les fichiers firmwares sont par convention référencés comme des blobs car " |
||
117 | "vous ne pouvez pas déterminer ce qu'ils font. Notez que ces firmwares sont " |
||
7165 | jlepiller | 118 | "distribués sous des licences différentes et variées qui ne permettent pas le" |
119 | " désassemblage ou la retro ingénierie." |
||
7156 | jlepiller | 120 | |
121 | #. type: Content of: <sect1><para> |
||
122 | #: blfs-en/postlfs/config/firmware.xml:51 |
||
123 | msgid "Firmware for PCs falls into four categories:" |
||
124 | msgstr "Les firmwares pour PC tombent dans 4 catégories :" |
||
125 | |||
126 | #. type: Content of: <sect1><itemizedlist><listitem><para> |
||
7214 | jlepiller | 127 | #. « le » et « CPU » ne semblent pas bien accordés en genre. |
7156 | jlepiller | 128 | #: blfs-en/postlfs/config/firmware.xml:55 |
7214 | jlepiller | 129 | #, fuzzy |
7156 | jlepiller | 130 | msgid "" |
131 | "Updates to the CPU to work around errata, usually referred to as microcode." |
||
132 | msgstr "" |
||
7165 | jlepiller | 133 | "Les firmwares mettant à jour le CPU pour travailler correctement, couramment" |
134 | " appelé micro-code." |
||
7156 | jlepiller | 135 | |
136 | #. type: Content of: <sect1><itemizedlist><listitem><para> |
||
137 | #: blfs-en/postlfs/config/firmware.xml:59 |
||
138 | msgid "" |
||
139 | "Firmware for video controllers. On x86 machines this seems to only apply to " |
||
140 | "ATI devices : Radeons require firmware to be able to use KMS (kernel " |
||
141 | "modesetting - the preferred option) as well as for Xorg. For earlier radeon " |
||
142 | "chips (before the R600), the firmware is still in the kernel." |
||
143 | msgstr "" |
||
144 | "Les firmwares pour les contrôleurs vidéo. Sur les machines x86 cela semble " |
||
7165 | jlepiller | 145 | "s'appliquer seulement aux périphériques ATI : les Radeons demandent des" |
146 | " firmwares pour pouvoir utiliser le KMS (kernel modesetting — option " |
||
7156 | jlepiller | 147 | "préférable) avec Xorg. Pour les puces radeons plus anciennes (avant R600), " |
148 | "le firmware est resté dans le noyau." |
||
149 | |||
150 | #. type: Content of: <sect1><itemizedlist><listitem><para> |
||
151 | #: blfs-en/postlfs/config/firmware.xml:66 |
||
152 | msgid "" |
||
153 | "Firmware updates for wired network ports. Mostly they work even without the " |
||
154 | "updates, but one must assume that they will work better with the updated " |
||
155 | "firmware." |
||
156 | msgstr "" |
||
157 | "Les Firmwares mettant à jour les ports réseaux câblés. Souvent ils " |
||
158 | "fonctionnent sans les mises à jour, mais on peut penser qu'ils travaillent " |
||
159 | "mieux avec les firmwares mis à jour." |
||
160 | |||
161 | #. type: Content of: <sect1><itemizedlist><listitem><para> |
||
162 | #: blfs-en/postlfs/config/firmware.xml:71 |
||
163 | msgid "" |
||
7165 | jlepiller | 164 | "Firmware for other devices, such as wifi. These devices are not required for" |
165 | " the PC to boot, but need the firmware before these devices can be used." |
||
7156 | jlepiller | 166 | msgstr "" |
167 | "Les Firmwares pour les autres périphériques, comme le wi-fi. Ces " |
||
168 | "périphériques ne sont pas requis pour que le PC démarre, mais demande un " |
||
169 | "firmware avant que ces périphériques puissent être utilisés." |
||
170 | |||
171 | #. type: Content of: <sect1><note><para> |
||
7214 | jlepiller | 172 | #. Le mot singulier « inutile » n’est pas accordé en nombre avec le mot |
173 | #. pluriel « ils ». |
||
7156 | jlepiller | 174 | #: blfs-en/postlfs/config/firmware.xml:77 |
7214 | jlepiller | 175 | #, fuzzy |
7156 | jlepiller | 176 | msgid "" |
177 | "Although not needed to load a firmware blob, the following tools may be " |
||
7165 | jlepiller | 178 | "useful for determining, obtaining, or preparing the needed firmware in order" |
179 | " to load it into the system: <xref linkend=\"cpio\"/>, <xref " |
||
180 | "linkend=\"git\"/>, <xref linkend=\"pciutils\"/>, and <xref " |
||
181 | "linkend=\"wget\"/>" |
||
7156 | jlepiller | 182 | msgstr "" |
7165 | jlepiller | 183 | "Bien qu’ils soient inutile pour charger un firmware fermé (blob), les outils" |
184 | " suivants peuvent être utiles pour déterminer, obtenir, ou préparer le " |
||
185 | "firmware à utiliser afin de le charger dans le système : <xref " |
||
186 | "linkend=\"cpio\"/>, <xref linkend=\"git\"/>, <xref linkend=\"pciutils\"/> et" |
||
187 | " <xref linkend=\"wget\"/>" |
||
7156 | jlepiller | 188 | |
189 | #. type: Content of: <sect1><para> |
||
190 | #: blfs-en/postlfs/config/firmware.xml:85 |
||
191 | msgid "User Notes: <ulink url=\"&blfs-wiki;/aboutfirmware\"/>" |
||
192 | msgstr "Notes utilisateur : <ulink url=\"&blfs-wiki;/aboutfirmware\"/>" |
||
193 | |||
194 | #. type: Content of: <sect1><sect2><title> |
||
195 | #: blfs-en/postlfs/config/firmware.xml:89 |
||
196 | msgid "Microcode updates for CPUs" |
||
197 | msgstr "Mise à jour de micro-codes pour les CPU" |
||
198 | |||
199 | #. type: Content of: <sect1><sect2><para> |
||
7214 | jlepiller | 200 | #. La lettre h doit être espacée dans les heures abrégées. Voulez-vous écrire |
201 | #. <suggestion>10 h</suggestion> ? |
||
7156 | jlepiller | 202 | #: blfs-en/postlfs/config/firmware.xml:91 |
7214 | jlepiller | 203 | #, fuzzy |
7156 | jlepiller | 204 | msgid "" |
205 | "In general, microcode can be loaded by the BIOS or UEFI, and it might be " |
||
206 | "updated by upgrading to a newer version of those. On linux, you can also " |
||
207 | "load the microcode from the kernel if you are using an AMD family 10h or " |
||
7164 | jlepiller | 208 | "later processor (first introduced late 2007), or an Intel processor from " |
7156 | jlepiller | 209 | "1998 and later (Pentium4, Core, etc), if updated microcode has been " |
210 | "released. These updates only last until the machine is powered off, so they " |
||
211 | "need to be applied on every boot." |
||
212 | msgstr "" |
||
7190 | jlepiller | 213 | "En général, le micro-code peut être chargé par le BIOS ou l'UEFI, et il peut" |
214 | " être mis à jour en passant à une nouvelle version de celui-ci. Sur Linux, " |
||
215 | "vous pouvez également charger le micro-code depuis le noyau si vous utilisez" |
||
216 | " au moins un AMD de la famille 10h ou un plus récent (introduit après fin " |
||
7175 | jlepiller | 217 | "2007), ou un processeur Intel de 1998 et plus (Pentium4, Core, etc), si un " |
218 | "micro-code mis à jour a été publié. Ces mises à jour sont actives seulement " |
||
7156 | jlepiller | 219 | "jusqu'à ce que la machine soit éteinte, il est donc nécessaire de les " |
220 | "appliquer à chaque démarrage." |
||
221 | |||
222 | #. type: Content of: <sect1><sect2><para> |
||
7214 | jlepiller | 223 | #. Le mot « commit » ne peut pas être un verbe après « un ». |
7156 | jlepiller | 224 | #: blfs-en/postlfs/config/firmware.xml:99 |
7214 | jlepiller | 225 | #, fuzzy |
7156 | jlepiller | 226 | msgid "" |
227 | "There are two ways of loading the microcode, described as 'early' and " |
||
228 | "'late'. Early loading happens before userspace has been started, late " |
||
229 | "loading happens when userspace has started. Not surprisingly, early loading " |
||
230 | "is preferred, (see e.g. an explanatory comment in a kernel commit noted at " |
||
231 | "<ulink url=\"https://lwn.net/Articles/530346/\">x86/microcode: Early load " |
||
232 | "microcode </ulink> on LWN.) Indeed, it is needed to work around one " |
||
7165 | jlepiller | 233 | "particular erratum in early Intel Haswell processors which had TSX enabled." |
234 | " (See <ulink url=\"http://www.anandtech.com/show/8376/intel-disables-tsx-" |
||
7156 | jlepiller | 235 | "instructions-erratum-found-in-haswell-haswelleep-broadwellyi/\"> Intel " |
7165 | jlepiller | 236 | "Disables TSX Instructions: Erratum Found in Haswell, Haswell-E/EP, " |
237 | "Broadwell-Y</ulink>.) Without this update glibc can do the wrong thing in " |
||
238 | "uncommon situations." |
||
7156 | jlepiller | 239 | msgstr "" |
7190 | jlepiller | 240 | "Il y a deux façons de charger le micro-code, décrit comme \"au plus tôt\" et" |
241 | " \"le plus tard\". Le chargement \"au plus tôt\" arrive avant que l'espace " |
||
7156 | jlepiller | 242 | "utilisateur ai été démarré, le chargement \"le plus tard\" arrive quand " |
7165 | jlepiller | 243 | "l'espace utilisateur est démarré. Sans surprise, le chargement \"au plus " |
7175 | jlepiller | 244 | "tôt\" est préféré (voir par exemple un commentaire d'explication dans un " |
7190 | jlepiller | 245 | "commit du noyau noté <ulink " |
246 | "url=\"https://lwn.net/Articles/530346/\">x86/microcode: Early load " |
||
247 | "microcode</ulink> sur LWN). En effet, il est utile de contourner une erreur " |
||
248 | "particulière dans les premiers processeurs Intel Haswell qui ont le TSX " |
||
249 | "d'activé. (Voir <ulink url=\"http://www.anandtech.com/show/8376/intel-" |
||
250 | "disables-tsx-instructions-erratum-found-in-haswell-haswelleep-" |
||
251 | "broadwellyi/\">Intel Disables TSX Instructions: Erratum Found in Haswell, " |
||
252 | "Haswell-E/EP, Broadwell-Y</ulink>). Sans cette mise à jour glibc peut " |
||
253 | "produire des erreurs dans des situations particulières." |
||
7156 | jlepiller | 254 | |
255 | #. type: Content of: <sect1><sect2><para> |
||
7214 | jlepiller | 256 | #. Voulez-vous écrire <suggestion>mises à jour</suggestion> ? |
7156 | jlepiller | 257 | #: blfs-en/postlfs/config/firmware.xml:112 |
7214 | jlepiller | 258 | #, fuzzy |
7156 | jlepiller | 259 | msgid "" |
260 | "It is much simpler to begin by building a kernel which boots on your " |
||
261 | "hardware, try late microcode loading to see if there is an update (in many " |
||
262 | "cases the BIOS or UEFI will have already applied any update), and then take " |
||
263 | "the extra steps required for early loading." |
||
264 | msgstr "" |
||
7165 | jlepiller | 265 | "Il est beaucoup plus simple de commencer par construire un noyau qui démarre" |
266 | " sur votre matériel, essayer de charger le micro-code « le plus " |
||
7156 | jlepiller | 267 | "tard » pour voir s'il y a une mise à jour (dans la plupart des cas le " |
268 | "BIOS ou l'UEFI aura déjà appliqué toutes les mises à jours), et ensuite " |
||
269 | "faire les étapes supplémentaires dans la configuration du noyau pour un " |
||
270 | "chargement « au plus tôt »." |
||
271 | |||
272 | #. type: Content of: <sect1><sect2><para> |
||
273 | #: blfs-en/postlfs/config/firmware.xml:117 |
||
274 | msgid "" |
||
275 | "This means you will be reconfiguring your kernel if you use early loading, " |
||
276 | "so keep the built source around to minimise what gets rebuilt, and if you " |
||
277 | "are at all uncertain, add your own identifier (A,B, etc) to the end of the " |
||
278 | "EXTRAVERSION in the kernel configuration, e.g. \"EXTRAVERSION -A\" if " |
||
279 | "nothing was set." |
||
280 | msgstr "" |
||
281 | "Cela signifie que vous devrez reconfigurer votre noyau si vous utilisez le " |
||
282 | "chargement « au plus tôt », aussi laissez les sources construites " |
||
283 | "afin de minimiser ce qui aura besoin d'être reconstruit, et si vous êtes " |
||
284 | "incertain, ajoutez votre propre identifiant (A, B, etc) à la fin de " |
||
285 | "l'EXTRAVERSION dans la configuration du noyau, soit \"EXTRAVERSION -A\" si " |
||
286 | "rien est initialisé." |
||
287 | |||
288 | #. type: Content of: <sect1><sect2><para> |
||
289 | #: blfs-en/postlfs/config/firmware.xml:123 |
||
290 | msgid "" |
||
291 | "To confirm what processor(s) you have (if more than one, they will be " |
||
292 | "identical) look in /proc/cpuinfo." |
||
293 | msgstr "" |
||
294 | "Pour confirmer quel(s) processeur(s) vous avez (si plus d'un, ils seront " |
||
295 | "identiques) regardez dans /proc/cpuinfo." |
||
296 | |||
297 | #. type: Content of: <sect1><sect2><sect3><title> |
||
7214 | jlepiller | 298 | #. « le » et « CPU » ne semblent pas bien accordés en genre. |
7156 | jlepiller | 299 | #: blfs-en/postlfs/config/firmware.xml:127 |
7214 | jlepiller | 300 | #, fuzzy |
7156 | jlepiller | 301 | msgid "Intel Microcode for the CPU" |
302 | msgstr "Micro-code Intel pour le CPU" |
||
303 | |||
304 | #. type: Content of: <sect1><sect2><sect3><bridgehead> |
||
305 | #: blfs-en/postlfs/config/firmware.xml:129 |
||
306 | msgid "Required Package" |
||
307 | msgstr "Paquet requis" |
||
308 | |||
309 | #. type: Content of: <sect1><sect2><sect3><para> |
||
310 | #: blfs-en/postlfs/config/firmware.xml:131 |
||
311 | msgid "<ulink url='http://fedorahosted.org/released/microcode_ctl/'/>" |
||
312 | msgstr "<ulink url='http://fedorahosted.org/released/microcode_ctl/'/>" |
||
313 | |||
314 | #. type: Content of: <sect1><sect2><sect3><para> |
||
7214 | jlepiller | 315 | #. « Container » est un anglicisme. Employez |
316 | #. <suggestion>conteneur</suggestion>. |
||
7156 | jlepiller | 317 | #: blfs-en/postlfs/config/firmware.xml:133 |
7214 | jlepiller | 318 | #, fuzzy |
7156 | jlepiller | 319 | msgid "" |
7164 | jlepiller | 320 | "For Intel CPUs an extra package, microcode_ctl, is required. The package " |
7156 | jlepiller | 321 | "chosen is the version hosted at fedora — there is an alternative " |
322 | "version at github from the same packager, but that still includes a " |
||
323 | "redundant old version of an AMD microcode container, and also requires the " |
||
324 | "unzip package." |
||
325 | msgstr "" |
||
326 | "Pour les CPU Intel, un paquet supplémentaire, microcode_ctl, est requis. Le " |
||
7175 | jlepiller | 327 | "paquet choisi est la version hébergée sur Fedora — il y a une version " |
7156 | jlepiller | 328 | "alternative sur github du même empaqueteur, mais qui laisse une ancienne " |
329 | "version redondante d'un container de micro-code AMD, et qui requiert aussi " |
||
330 | "le paquet unzip." |
||
331 | |||
332 | #. type: Content of: <sect1><sect2><sect3><para> |
||
333 | #: blfs-en/postlfs/config/firmware.xml:139 |
||
334 | msgid "" |
||
335 | "Download the latest version from the link above; when last checked this was " |
||
7164 | jlepiller | 336 | "2.1-8 and is updated when Intel releases new microcode." |
7156 | jlepiller | 337 | msgstr "" |
338 | "Téléchargez la dernière version depuis le lien précédent ; à la " |
||
339 | "dernière vérification, il était en version 2.1-8 et est mis à jour quand " |
||
340 | "Intel publie de nouveaux micro-codes." |
||
341 | |||
342 | #. type: Content of: <sect1><sect2><sect3><para> |
||
343 | #: blfs-en/postlfs/config/firmware.xml:142 |
||
344 | msgid "" |
||
7164 | jlepiller | 345 | "This package reformats the microcode supplied by Intel into a format which " |
7165 | jlepiller | 346 | "the kernel can apply. The program <userinput>intel-" |
347 | "microcode2ucode</userinput> is built and invoked by the Makefile to create " |
||
348 | "the individual firmware blobs, so there is no reason to install it." |
||
7156 | jlepiller | 349 | msgstr "" |
350 | "Ce paquet reformate le micro-code fourni par Intel dans un format que le " |
||
7175 | jlepiller | 351 | "noyau peut appliquer. Le programme <userinput>intel-" |
352 | "microcode2ucode</userinput> est construit et invoqué par le Makefile pour " |
||
353 | "créer des blobs individuels de micro-codes, donc il n'y a pas de raison de " |
||
354 | "l'installer." |
||
7156 | jlepiller | 355 | |
356 | #. type: Content of: <sect1><sect2><sect3><para> |
||
357 | #: blfs-en/postlfs/config/firmware.xml:148 |
||
358 | msgid "" |
||
359 | "Begin by extracting the tarball and changing to the directory it created. " |
||
360 | "Then change to the source directory and run:" |
||
361 | msgstr "" |
||
362 | "Commencez par extraire l'archive et allez dans le répertoire créé. Ensuite " |
||
363 | "allez dans le répertoire des sources et lancez :" |
||
364 | |||
365 | #. type: Content of: <sect1><sect2><sect3><screen> |
||
366 | #: blfs-en/postlfs/config/firmware.xml:151 |
||
367 | #, no-wrap |
||
368 | msgid "<userinput>make</userinput>" |
||
369 | msgstr "<userinput>make</userinput>" |
||
370 | |||
371 | #. type: Content of: <sect1><sect2><sect3><para> |
||
7214 | jlepiller | 372 | #. Le verbe « vois » devrait être à l’infinitif après la préposition « pour » |
373 | #. « du » et « CPU » ne semblent pas bien accordés en genre. |
||
7156 | jlepiller | 374 | #: blfs-en/postlfs/config/firmware.xml:153 |
7214 | jlepiller | 375 | #, fuzzy |
7156 | jlepiller | 376 | msgid "" |
377 | "This creates various blobs with names in the form XX-YY-ZZ. Now you need to " |
||
378 | "determine your processor's identity, to see if there is any microcode for " |
||
379 | "it. Determine the decimal values of the cpu family, model and stepping by " |
||
380 | "running:" |
||
381 | msgstr "" |
||
382 | "Cela crée de nombreux blobs avec des noms de la forme XX-YY-ZZ. Maintenant " |
||
383 | "vous devez déterminer l'identité de votre processeur, pour vois s'il y a un " |
||
384 | "micro-code pour lui. Déterminez les valeurs décimales de la famille du CPU, " |
||
385 | "le modèle, et le pas en lançant :" |
||
386 | |||
387 | #. type: Content of: <sect1><sect2><sect3><screen> |
||
388 | #: blfs-en/postlfs/config/firmware.xml:158 |
||
389 | #, no-wrap |
||
390 | msgid "<userinput>head -n7 /proc/cpuinfo</userinput>" |
||
391 | msgstr "<userinput>head -n7 /proc/cpuinfo</userinput>" |
||
392 | |||
393 | #. type: Content of: <sect1><sect2><sect3><para> |
||
7214 | jlepiller | 394 | #. « du » et « CPU » ne semblent pas bien accordés en genre. |
395 | #. « ce » et « CPU » ne semblent pas bien accordés en genre. |
||
7156 | jlepiller | 396 | #: blfs-en/postlfs/config/firmware.xml:160 |
7214 | jlepiller | 397 | #, fuzzy |
7156 | jlepiller | 398 | msgid "" |
399 | "Now convert the cpu family, model and stepping to pairs of hexadecimal " |
||
400 | "digits. For a SandyBridge i3-2120 (described as Intel(R) Core(TM) i3-2120 " |
||
401 | "CPU) the relevant values are cpu family 6, model 42, stepping 7 so in this " |
||
402 | "case the required identification is 06-2a-07. A look at the blobs will show " |
||
403 | "that there is one for this CPU (although it might have already been applied " |
||
404 | "by the BIOS). If there is a blob for your system then test if it will be " |
||
405 | "applied by copying it (replace <XX-YY-ZZ> by the identifier for your " |
||
406 | "machine) to where the kernel can find it:" |
||
407 | msgstr "" |
||
408 | "Maintenant convertissez la famille du CPU, le modèle et le pas en paire de " |
||
409 | "digits hexadécimal. Pour un SandyBridge i3-2120 (décrit comme un Intel(R) " |
||
410 | "Core(TM) i3-2120 CPU) les bonnes valeurs sont famille de CPU 6, modèle 42, " |
||
411 | "pas 7 donc dans ce cas l'identification requise est 06-2a-07. Un coup d’œil " |
||
412 | "sur les blobs montrera qu'il y en a un pour ce CPU (cependant qui semble " |
||
7165 | jlepiller | 413 | "déjà appliqué par le BIOS). S'il y a un blob pour votre système alors testez" |
414 | " s'il peut être appliqué en le copiant (remplacez <XX-YY-ZZ> par " |
||
7156 | jlepiller | 415 | "l'identifiant de votre machine) où le noyau pourra le trouver." |
416 | |||
417 | #. type: Content of: <sect1><sect2><sect3><screen> |
||
418 | #: blfs-en/postlfs/config/firmware.xml:169 |
||
419 | #, no-wrap |
||
420 | msgid "" |
||
421 | "<userinput>mkdir -pv /lib/firmware/intel-ucode\n" |
||
422 | "cp -v <XX-YY-ZZ> /lib/firmware/intel-ucode</userinput>" |
||
423 | msgstr "" |
||
424 | "<userinput>mkdir -pv /lib/firmware/intel-ucode\n" |
||
425 | "cp -v <XX-YY-ZZ> /lib/firmware/intel-ucode</userinput>" |
||
426 | |||
427 | #. type: Content of: <sect1><sect2><sect3><para> |
||
428 | #: blfs-en/postlfs/config/firmware.xml:172 |
||
429 | msgid "" |
||
7164 | jlepiller | 430 | "Now that the Intel microcode has been prepared, use the following options " |
431 | "when you configure the kernel to try late loading of the Intel microcode:" |
||
7156 | jlepiller | 432 | msgstr "" |
433 | "Maintenant que le micro-code Intel a été préparé, utilisez les options " |
||
7175 | jlepiller | 434 | "suivantes quand vous configurez le noyau pour essayer le chargement \"le " |
435 | "plus tard\" du micro-code Intel :" |
||
7156 | jlepiller | 436 | |
437 | #. type: Content of: <sect1><sect2><sect3><screen> |
||
438 | #: blfs-en/postlfs/config/firmware.xml:176 |
||
439 | #, no-wrap |
||
440 | msgid "" |
||
441 | "<literal>Processor type and features --->\n" |
||
442 | " <M> CPU microcode loading support [CONFIG_MICROCODE]\n" |
||
443 | " [*] Intel microcode loading support [CONFIG_MICROCODE_INTEL]</literal>" |
||
444 | msgstr "" |
||
445 | "<literal>Processor type and features --->\n" |
||
446 | " <M> CPU microcode loading support [CONFIG_MICROCODE]\n" |
||
447 | " [*] Intel microcode loading support [CONFIG_MICROCODE_INTEL]</literal>" |
||
448 | |||
449 | #. type: Content of: <sect1><sect2><sect3><para> |
||
450 | #: blfs-en/postlfs/config/firmware.xml:180 |
||
451 | msgid "" |
||
452 | "After you have successfully booted the new system, use the command " |
||
453 | "<userinput>dmesg | grep microcode</userinput> and study the results to see " |
||
454 | "if the message new patch_level appears. This example from the SandyBridge " |
||
455 | "i3:" |
||
456 | msgstr "" |
||
457 | "Après que vous ayez démarré le nouveau système avec succès, utilisez la " |
||
458 | "commande <userinput>dmesg | grep microcode</userinput> et étudiez les " |
||
459 | "résultats pour voir si le message patch_level apparaît. Voici un exemple " |
||
460 | "pour le SandyBridge i3 :" |
||
461 | |||
462 | #. type: Content of: <sect1><sect2><sect3><screen> |
||
463 | #: blfs-en/postlfs/config/firmware.xml:185 |
||
464 | #, no-wrap |
||
465 | msgid "" |
||
466 | "<literal>[ 0.059906] perf_event_intel: PEBS disabled due to CPU errata, please upgrade microcode\n" |
||
467 | "[ 2.603083] microcode: CPU0 sig=0x206a7, pf=0x2, revision=0x23\n" |
||
468 | "[ 2.669378] microcode: CPU0 sig=0x206a7, pf=0x2, revision=0x23\n" |
||
469 | "[ 2.669994] microcode: CPU0 updated to revision 0x29, date = 2013-06-12\n" |
||
470 | "[ 2.670069] microcode: CPU1 sig=0x206a7, pf=0x2, revision=0x23\n" |
||
471 | "[ 2.670139] microcode: CPU1 sig=0x206a7, pf=0x2, revision=0x23\n" |
||
472 | "[ 2.670501] microcode: CPU1 updated to revision 0x29, date = 2013-06-12\n" |
||
473 | "[ 2.670509] microcode: CPU2 sig=0x206a7, pf=0x2, revision=0x23\n" |
||
474 | "[ 2.670540] microcode: CPU2 sig=0x206a7, pf=0x2, revision=0x23\n" |
||
475 | "[ 2.670917] microcode: CPU2 updated to revision 0x29, date = 2013-06-12\n" |
||
476 | "[ 2.670955] microcode: CPU3 sig=0x206a7, pf=0x2, revision=0x23\n" |
||
477 | "[ 2.670988] microcode: CPU3 sig=0x206a7, pf=0x2, revision=0x23\n" |
||
478 | "[ 2.671348] microcode: CPU3 updated to revision 0x29, date = 2013-06-12\n" |
||
479 | "[ 2.671356] perf_event_intel: PEBS enabled due to microcode update\n" |
||
480 | "[ 2.671412] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba</literal>" |
||
481 | msgstr "" |
||
482 | "<literal>[ 0.059906] perf_event_intel: PEBS disabled due to CPU errata, please upgrade microcode\n" |
||
483 | "[ 2.603083] microcode: CPU0 sig=0x206a7, pf=0x2, revision=0x23\n" |
||
484 | "[ 2.669378] microcode: CPU0 sig=0x206a7, pf=0x2, revision=0x23\n" |
||
485 | "[ 2.669994] microcode: CPU0 updated to revision 0x29, date = 2013-06-12\n" |
||
486 | "[ 2.670069] microcode: CPU1 sig=0x206a7, pf=0x2, revision=0x23\n" |
||
487 | "[ 2.670139] microcode: CPU1 sig=0x206a7, pf=0x2, revision=0x23\n" |
||
488 | "[ 2.670501] microcode: CPU1 updated to revision 0x29, date = 2013-06-12\n" |
||
489 | "[ 2.670509] microcode: CPU2 sig=0x206a7, pf=0x2, revision=0x23\n" |
||
490 | "[ 2.670540] microcode: CPU2 sig=0x206a7, pf=0x2, revision=0x23\n" |
||
491 | "[ 2.670917] microcode: CPU2 updated to revision 0x29, date = 2013-06-12\n" |
||
492 | "[ 2.670955] microcode: CPU3 sig=0x206a7, pf=0x2, revision=0x23\n" |
||
493 | "[ 2.670988] microcode: CPU3 sig=0x206a7, pf=0x2, revision=0x23\n" |
||
494 | "[ 2.671348] microcode: CPU3 updated to revision 0x29, date = 2013-06-12\n" |
||
495 | "[ 2.671356] perf_event_intel: PEBS enabled due to microcode update\n" |
||
496 | "[ 2.671412] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba</literal>" |
||
497 | |||
498 | #. type: Content of: <sect1><sect2><sect3><para> |
||
499 | #: blfs-en/postlfs/config/firmware.xml:201 |
||
500 | #: blfs-en/postlfs/config/firmware.xml:239 |
||
501 | msgid "" |
||
502 | "If the microcode was not updated, there is no new microcode for this " |
||
503 | "system's processor. If it did get updated, you can now proceed to <xref " |
||
504 | "linkend='early-microcode'/>." |
||
505 | msgstr "" |
||
506 | "Si le micro-code n'a pas été mis à jour, il n'y a pas de nouveau micro-code " |
||
507 | "pour ce processeur. S'il a été mis à jour, vous pouvez maintenant faire la " |
||
508 | "section intitulée <xref linkend='early-microcode'/>." |
||
509 | |||
510 | #. type: Content of: <sect1><sect2><sect3><title> |
||
7214 | jlepiller | 511 | #. « le » et « CPU » ne semblent pas bien accordés en genre. |
7156 | jlepiller | 512 | #: blfs-en/postlfs/config/firmware.xml:208 |
7214 | jlepiller | 513 | #, fuzzy |
7156 | jlepiller | 514 | msgid "AMD Microcode for the CPU" |
515 | msgstr "Micro-code AMD pour le CPU" |
||
516 | |||
517 | #. type: Content of: <sect1><sect2><sect3><para> |
||
7214 | jlepiller | 518 | #. Le mot pluriel « spécifiées » n’est pas accordé en nombre avec le mot |
519 | #. singulier « famille ». |
||
520 | #. La lettre h doit être espacée dans les heures abrégées. Voulez-vous écrire |
||
521 | #. <suggestion>10 h</suggestion> ? |
||
522 | #. La lettre h doit être espacée dans les heures abrégées. Voulez-vous écrire |
||
523 | #. <suggestion>14 h</suggestion> ? |
||
524 | #. La lettre h doit être espacée dans les heures abrégées. Voulez-vous écrire |
||
525 | #. <suggestion>15 h</suggestion> ? |
||
526 | #. La lettre h doit être espacée dans les heures abrégées. Voulez-vous écrire |
||
527 | #. <suggestion>16 h</suggestion> ? |
||
528 | #. Voulez-vous écrire <suggestion>placez-le</suggestion> ? |
||
7156 | jlepiller | 529 | #: blfs-en/postlfs/config/firmware.xml:210 |
7214 | jlepiller | 530 | #, fuzzy |
7156 | jlepiller | 531 | msgid "" |
7165 | jlepiller | 532 | "Begin by downloading a container of firmware for your CPU family from <ulink" |
533 | " url='&sources-anduin-http;/linux-firmware/amd-ucode/'/>. The family is " |
||
7156 | jlepiller | 534 | "always specified in hex. Families 10h to 14h (16 to 20) are in " |
535 | "microcode_amd.bin. Families 15h and 16h have their own containers. Create " |
||
536 | "the required directory and put the firmware you downloaded into it as the " |
||
537 | "<systemitem class=\"username\">root</systemitem> user:" |
||
538 | msgstr "" |
||
539 | "Commencez par télécharger un paquet de firmware pour votre famille de CPU " |
||
540 | "sur <ulink url='&sources-anduin-http;/linux-firmware/amd-ucode/'/>. La " |
||
7165 | jlepiller | 541 | "famille est toujours spécifiées en hexadécimal. Les familles 10h à 14h (16 à" |
542 | " 20) sont dans microcode_amd.bin. Les familles 15h et 16h ont leur propre " |
||
7156 | jlepiller | 543 | "paquet. Créez le répertoire requis et placez le firmware télécharger dedans " |
7165 | jlepiller | 544 | "en tant qu'utilisateur <systemitem " |
545 | "class=\"username\">root</systemitem> :" |
||
7156 | jlepiller | 546 | |
547 | #. type: Content of: <sect1><sect2><sect3><screen> |
||
548 | #: blfs-en/postlfs/config/firmware.xml:218 |
||
549 | #, no-wrap |
||
550 | msgid "" |
||
551 | "<userinput>mkdir -pv /lib/firmware/amd-ucode\n" |
||
552 | "cp -v microcode_amd* /lib/firmware/amd-ucode</userinput>" |
||
553 | msgstr "" |
||
554 | "<userinput>mkdir -pv /lib/firmware/amd-ucode\n" |
||
555 | "cp -v microcode_amd* /lib/firmware/amd-ucode</userinput>" |
||
556 | |||
557 | #. type: Content of: <sect1><sect2><sect3><para> |
||
558 | #: blfs-en/postlfs/config/firmware.xml:221 |
||
559 | msgid "" |
||
7165 | jlepiller | 560 | "When you configure the kernel, use the following options to try late loading" |
561 | " of AMD microcode:" |
||
7156 | jlepiller | 562 | msgstr "" |
563 | "Quand vous configurez le noyau, utilisez les options suivantes pour essayer " |
||
564 | "un chargement \"tard\" du micro-code AMD:" |
||
565 | |||
566 | #. type: Content of: <sect1><sect2><sect3><screen> |
||
567 | #: blfs-en/postlfs/config/firmware.xml:224 |
||
568 | #, no-wrap |
||
569 | msgid "" |
||
570 | "<literal>Processor type and features --->\n" |
||
571 | " <M> CPU microcode loading support [CONFIG_MICROCODE]\n" |
||
572 | " [*] AMD microcode loading support [CONFIG_MICROCODE_AMD]</literal>" |
||
573 | msgstr "" |
||
574 | "<literal>Processor type and features --->\n" |
||
575 | " <M> CPU microcode loading support [CONFIG_MICROCODE]\n" |
||
576 | " [*] AMD microcode loading support [CONFIG_MICROCODE_AMD]</literal>" |
||
577 | |||
578 | #. type: Content of: <sect1><sect2><sect3><para> |
||
579 | #: blfs-en/postlfs/config/firmware.xml:228 |
||
580 | msgid "" |
||
581 | "After you have successfully booted the new system, use the command " |
||
582 | "<userinput>dmesg | grep microcode</userinput> and study the results to see " |
||
583 | "if the message new patch_level appears, as in this example from an old " |
||
584 | "Athlon(tm) II X2:" |
||
585 | msgstr "" |
||
7165 | jlepiller | 586 | "Après avoir démarré correctement votre nouveau système, utilisez la commande" |
587 | " <userinput>dmesg | grep microcode</userinput> et étudiez le résultat pour " |
||
7156 | jlepiller | 588 | "voir si le message new patch_level apparaît, comme dans l’exemple suivant " |
589 | "provenant l’un vieil Athlon(tm) II X2 :" |
||
590 | |||
591 | #. type: Content of: <sect1><sect2><sect3><screen> |
||
592 | #: blfs-en/postlfs/config/firmware.xml:233 |
||
593 | #, no-wrap |
||
594 | msgid "" |
||
595 | "<literal>[ 4.183907] microcode: CPU0: patch_level=0x010000b6\n" |
||
596 | "[ 4.184271] microcode: CPU0: new patch_level=0x010000c8\n" |
||
597 | "[ 4.184278] microcode: CPU1: patch_level=0x010000b6\n" |
||
598 | "[ 4.184283] microcode: CPU1: new patch_level=0x010000c8\n" |
||
599 | "[ 4.184359] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba</literal>" |
||
600 | msgstr "" |
||
601 | "<literal>[ 4.183907] microcode: CPU0: patch_level=0x010000b6\n" |
||
602 | "[ 4.184271] microcode: CPU0: new patch_level=0x010000c8\n" |
||
603 | "[ 4.184278] microcode: CPU1: patch_level=0x010000b6\n" |
||
604 | "[ 4.184283] microcode: CPU1: new patch_level=0x010000c8\n" |
||
605 | "[ 4.184359] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba</literal>" |
||
606 | |||
607 | #. type: Content of: <sect1><sect2><sect3><title> |
||
608 | #: blfs-en/postlfs/config/firmware.xml:246 |
||
609 | msgid "Early loading of microcode" |
||
610 | msgstr "Chargement \"tôt\" du micro-code" |
||
611 | |||
612 | #. type: Content of: <sect1><sect2><sect3><para> |
||
613 | #: blfs-en/postlfs/config/firmware.xml:248 |
||
614 | msgid "" |
||
7165 | jlepiller | 615 | "If you have established that updated microcode is available for your system," |
616 | " it is time to prepare it for early loading. This requires an additional " |
||
617 | "package, <xref linkend='cpio'/>, as well as changes to the kernel config and" |
||
618 | " the creation of an initrd which will need to be added to grub.cfg." |
||
7156 | jlepiller | 619 | msgstr "" |
620 | "Si vous avez établi d'un micro-code mis à jour est disponible pour votre " |
||
621 | "système, il est temps de le préparer pour un chargement \"tôt\". Cela " |
||
7184 | jlepiller | 622 | "demande un paquet supplémentaire, <xref linkend='cpio'/>, ainsi que des " |
623 | "modifications à la configuration du noyau et la création d'un initrd qui " |
||
624 | "devra être ajouté à grub.cfg." |
||
7156 | jlepiller | 625 | |
626 | #. type: Content of: <sect1><sect2><sect3><para> |
||
627 | #: blfs-en/postlfs/config/firmware.xml:254 |
||
628 | msgid "" |
||
629 | "It does not matter where you prepare the initrd, and once it is working you " |
||
7165 | jlepiller | 630 | "can apply the same initrd to later LFS systems or newer kernels on this same" |
631 | " machine, at least until any newer microcode is released. Use the following " |
||
7156 | jlepiller | 632 | "commands:" |
633 | msgstr "" |
||
634 | "L'endroit ou vous préparez l'initrd n'est pas important, et une fois " |
||
7165 | jlepiller | 635 | "fonctionnel vous pouvez appliquer le même initrd aux versions futures de LFS" |
636 | " ou aux nouveaux noyaux sur cette même machine, au moins jusqu'à ce qu'une " |
||
7156 | jlepiller | 637 | "nouvelle version du micro-code soit publiée. Utiliser la suite :" |
638 | |||
639 | #. type: Content of: <sect1><sect2><sect3><screen> |
||
640 | #: blfs-en/postlfs/config/firmware.xml:259 |
||
641 | #, no-wrap |
||
642 | msgid "" |
||
643 | "<userinput>mkdir -p initrd/kernel/x86/microcode\n" |
||
644 | "cd initrd</userinput>" |
||
645 | msgstr "" |
||
646 | "<userinput>mkdir -p initrd/kernel/x86/microcode\n" |
||
647 | "cd initrd</userinput>" |
||
648 | |||
649 | #. type: Content of: <sect1><sect2><sect3><para> |
||
650 | #: blfs-en/postlfs/config/firmware.xml:262 |
||
651 | msgid "" |
||
652 | "For an AMD machine, use the following command (replace <MYCONTAINER> " |
||
653 | "with the name of the container for your CPU's family):" |
||
654 | msgstr "" |
||
7165 | jlepiller | 655 | "Pour une machine AMD, utilisez la commande suivante (remplacez " |
656 | "<MYCONTAINER> par le nom du paquet de votre famille de CPU) :" |
||
7156 | jlepiller | 657 | |
658 | #. type: Content of: <sect1><sect2><sect3><screen> |
||
659 | #: blfs-en/postlfs/config/firmware.xml:266 |
||
660 | #, no-wrap |
||
7165 | jlepiller | 661 | msgid "" |
662 | "<userinput>cp -v /lib/firmware/amd_ucode/<MYCONTAINER> " |
||
663 | "kernel/x86/microcode/AuthenticAMD.bin</userinput>" |
||
664 | msgstr "" |
||
665 | "<userinput>cp -v /lib/firmware/amd_ucode/<MYCONTAINER> " |
||
666 | "kernel/x86/microcode/AuthenticAMD.bin</userinput>" |
||
7156 | jlepiller | 667 | |
668 | #. type: Content of: <sect1><sect2><sect3><para> |
||
669 | #: blfs-en/postlfs/config/firmware.xml:268 |
||
670 | msgid "Or for an Intel machine copy the appropriate blob using this command:" |
||
671 | msgstr "" |
||
672 | "Ou pour une machine Intel copiez le blob approprié en utilisant cette " |
||
673 | "commande :" |
||
674 | |||
675 | #. type: Content of: <sect1><sect2><sect3><screen> |
||
676 | #: blfs-en/postlfs/config/firmware.xml:270 |
||
677 | #, no-wrap |
||
7165 | jlepiller | 678 | msgid "" |
679 | "<userinput>cp -v /lib/firmware/intel-ucode/<XX-YY-ZZ> " |
||
680 | "kernel/x86/microcode/GenuineIntel.bin</userinput>" |
||
681 | msgstr "" |
||
682 | "<userinput>cp -v /lib/firmware/intel-ucode/<XX-YY-ZZ> " |
||
683 | "kernel/x86/microcode/GenuineIntel.bin</userinput>" |
||
7156 | jlepiller | 684 | |
685 | #. type: Content of: <sect1><sect2><sect3><para> |
||
686 | #: blfs-en/postlfs/config/firmware.xml:272 |
||
687 | msgid "Now prepare the initrd:" |
||
688 | msgstr "Maintenant préparez l'initrd :" |
||
689 | |||
690 | #. type: Content of: <sect1><sect2><sect3><screen> |
||
691 | #: blfs-en/postlfs/config/firmware.xml:274 |
||
692 | #, no-wrap |
||
7165 | jlepiller | 693 | msgid "" |
694 | "<userinput>find . | cpio -o -H newc > /boot/microcode.img</userinput>" |
||
695 | msgstr "" |
||
696 | "<userinput>find . | cpio -o -H newc > /boot/microcode.img</userinput>" |
||
7156 | jlepiller | 697 | |
698 | #. type: Content of: <sect1><sect2><sect3><para> |
||
699 | #: blfs-en/postlfs/config/firmware.xml:276 |
||
700 | msgid "" |
||
701 | "You will now need to reconfigure and rebuild your kernel. It is safer to " |
||
7165 | jlepiller | 702 | "either add/change the EXTRAVERSION in the kernel's configuration and install" |
703 | " the newer kernel with a new name, or else (unless you have a machine which " |
||
704 | "requires an early firmware update) wait for the next SUBLEVEL kernel release" |
||
705 | " so that you can fall back to the existing kernel in the event that " |
||
706 | "something goes wrong." |
||
7156 | jlepiller | 707 | msgstr "" |
708 | "Vous devez maintenant reconfigurer et reconstruire votre noyau. Il est " |
||
709 | "prudent pour chaque d'ajouter/changer l'EXTRAVERSION dans la configuration " |
||
710 | "du noyau et d'installer le nouveau noyau avec un nouveau nom, ou alors (à " |
||
711 | "moins que vous ayez une machine qui requiert une mise à jour du firmware " |
||
712 | "\"tôt\") attendre la prochaine publication SUBLEVEL du noyau de sorte que " |
||
713 | "vous puissiez revenir au noyau existant dans le cas où quelque chose irait " |
||
714 | "mal." |
||
715 | |||
716 | #. type: Content of: <sect1><sect2><sect3><para> |
||
717 | #: blfs-en/postlfs/config/firmware.xml:283 |
||
718 | msgid "" |
||
719 | "You will also need to add a new entry to /boot/grub/grub.cfg and here you " |
||
7165 | jlepiller | 720 | "should add a new line after the linux line within the stanza. If /boot is a" |
721 | " separate mountpoint:" |
||
7156 | jlepiller | 722 | msgstr "" |
723 | "Vous devrez également ajouter une nouvelle entrée à /boot/grub/grub.cfg et " |
||
724 | "vous devrez ajouter une ligne après la ligne linux. Si /boot est dans une " |
||
725 | "partition séparée :" |
||
726 | |||
727 | #. type: Content of: <sect1><sect2><sect3><screen> |
||
728 | #: blfs-en/postlfs/config/firmware.xml:287 |
||
729 | #, no-wrap |
||
730 | msgid "<userinput>initrd /microcode.img</userinput>" |
||
731 | msgstr "<userinput>initrd /microcode.img</userinput>" |
||
732 | |||
733 | #. type: Content of: <sect1><sect2><sect3><para> |
||
734 | #: blfs-en/postlfs/config/firmware.xml:289 |
||
735 | msgid "or this if it is not:" |
||
736 | msgstr "ou sinon :" |
||
737 | |||
738 | #. type: Content of: <sect1><sect2><sect3><screen> |
||
739 | #: blfs-en/postlfs/config/firmware.xml:291 |
||
740 | #, no-wrap |
||
741 | msgid "<userinput>initrd /boot/microcode.img</userinput>" |
||
742 | msgstr "<userinput>initrd /boot/microcode.img</userinput>" |
||
743 | |||
744 | #. type: Content of: <sect1><sect2><sect3><para> |
||
745 | #: blfs-en/postlfs/config/firmware.xml:293 |
||
746 | msgid "You must also change the kernel config:" |
||
747 | msgstr "Vous devez également modifier la config du noyau :" |
||
748 | |||
749 | #. type: Content of: <sect1><sect2><sect3><screen> |
||
750 | #: blfs-en/postlfs/config/firmware.xml:295 |
||
751 | #, no-wrap |
||
752 | msgid "" |
||
753 | "<literal>General Setup --->\n" |
||
754 | " [y] Initial RAM filesystem and RAM disk (initramfs/initrd) support [CONFIG_BLK_DEV_INITRD]\n" |
||
755 | " [y] CPU microcode loading support [CONFIG_MICROCODE]</literal>" |
||
756 | msgstr "" |
||
757 | "<literal>General Setup --->\n" |
||
758 | " [y] Initial RAM filesystem and RAM disk (initramfs/initrd) support [CONFIG_BLK_DEV_INITRD]\n" |
||
759 | " [y] CPU microcode loading support [CONFIG_MICROCODE]</literal>" |
||
760 | |||
761 | #. type: Content of: <sect1><sect2><sect3><para> |
||
762 | #: blfs-en/postlfs/config/firmware.xml:299 |
||
763 | msgid "" |
||
7165 | jlepiller | 764 | "Retain the setting for INTEL or AMD microcode. When you have saved the " |
765 | ".config file, either CONFIG_MICROCODE_INTEL_EARLY=y or " |
||
7156 | jlepiller | 766 | "CONFIG_MICROCODE_AMD_EARLY=y should be set, together with " |
767 | "CONFIG_MICROCODE_EARLY=y." |
||
768 | msgstr "" |
||
769 | "Gardez les préférences pour le micro-code INTEL ou AMD. Quand vous avez " |
||
770 | "sauvegardé le fichier .config, soit CONFIG_MICROCODE_INTEL_EARLY=y ou " |
||
771 | "CONFIG_MICROCODE_AMD_EARLY=y doit être initialisé, avec " |
||
772 | "CONFIG_MICROCODE_EARLY=y." |
||
773 | |||
774 | #. type: Content of: <sect1><sect2><sect3><para> |
||
775 | #: blfs-en/postlfs/config/firmware.xml:304 |
||
776 | msgid "" |
||
777 | "When you have installed and booted this kernel, you should check the output " |
||
778 | "of dmesg to confirm that the early load worked. The places and times where " |
||
779 | "this happens are very different in AMD and Intel machines. First, an Intel " |
||
780 | "example where a development kernel is being tested, showing that the first " |
||
781 | "notification comes before the kernel version is mentioned:" |
||
782 | msgstr "" |
||
7165 | jlepiller | 783 | "Quand vous avez installé et démarré ce noyau, vous pouvez vérifier la sortie" |
784 | " de dmesg pour confirmer que le chargement \"tôt\" fonctionne. Les endroits " |
||
785 | "et les temps ou cela se passent sont très différents sur les machines AMD et" |
||
786 | " Intel. En premier, un exemple d'Intel ou un noyau de développement est " |
||
7156 | jlepiller | 787 | "testé, regardez que la première notification vient avant que la version du " |
788 | "noyau soit indiquée:" |
||
789 | |||
790 | #. type: Content of: <sect1><sect2><sect3><screen> |
||
791 | #: blfs-en/postlfs/config/firmware.xml:311 |
||
792 | #, no-wrap |
||
793 | msgid "" |
||
794 | "<literal>[ 0.000000] CPU0 microcode updated early to revision 0x29, date = 2013-06-12\n" |
||
795 | "[ 0.000000] Linux version 4.0.0-rc6 (ken@jtm1) (gcc version 4.9.2 (GCC) )\n" |
||
796 | " #3 SMP PREEMPT Mon Mar 30 21:26:02 BST 2015\n" |
||
797 | "[ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-4.0.0-rc6-sda13 root=/dev/sda13 ro\n" |
||
798 | "...\n" |
||
799 | "[ 0.103091] CPU1 microcode updated early to revision 0x29, date = 2013-06-12\n" |
||
800 | "[ 0.113241] #2\n" |
||
801 | "[ 0.134631] #3\n" |
||
802 | "[ 0.147821] x86: Booted up 1 node, 4 CPUs\n" |
||
803 | "[ 0.147936] smpboot: Total of 4 processors activated (26338.66 BogoMIPS)\n" |
||
804 | "...\n" |
||
805 | "[ 0.272643] microcode: CPU0 sig=0x206a7, pf=0x2, revision=0x29\n" |
||
806 | "[ 0.272709] microcode: CPU1 sig=0x206a7, pf=0x2, revision=0x29\n" |
||
807 | "[ 0.272775] microcode: CPU2 sig=0x206a7, pf=0x2, revision=0x29\n" |
||
808 | "[ 0.272842] microcode: CPU3 sig=0x206a7, pf=0x2, revision=0x29\n" |
||
809 | "[ 0.272941] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba</literal>" |
||
810 | msgstr "" |
||
811 | "<literal>[ 0.000000] CPU0 microcode updated early to revision 0x29, date = 2013-06-12\n" |
||
812 | "[ 0.000000] Linux version 4.0.0-rc6 (ken@jtm1) (gcc version 4.9.2 (GCC) )\n" |
||
813 | " #3 SMP PREEMPT Mon Mar 30 21:26:02 BST 2015\n" |
||
814 | "[ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-4.0.0-rc6-sda13 root=/dev/sda13 ro\n" |
||
815 | "...\n" |
||
816 | "[ 0.103091] CPU1 microcode updated early to revision 0x29, date = 2013-06-12\n" |
||
817 | "[ 0.113241] #2\n" |
||
818 | "[ 0.134631] #3\n" |
||
819 | "[ 0.147821] x86: Booted up 1 node, 4 CPUs\n" |
||
820 | "[ 0.147936] smpboot: Total of 4 processors activated (26338.66 BogoMIPS)\n" |
||
821 | "...\n" |
||
822 | "[ 0.272643] microcode: CPU0 sig=0x206a7, pf=0x2, revision=0x29\n" |
||
823 | "[ 0.272709] microcode: CPU1 sig=0x206a7, pf=0x2, revision=0x29\n" |
||
824 | "[ 0.272775] microcode: CPU2 sig=0x206a7, pf=0x2, revision=0x29\n" |
||
825 | "[ 0.272842] microcode: CPU3 sig=0x206a7, pf=0x2, revision=0x29\n" |
||
826 | "[ 0.272941] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba</literal>" |
||
827 | |||
828 | #. type: Content of: <sect1><sect2><sect3><para> |
||
7214 | jlepiller | 829 | #. « que ici » s’élide en <suggestion>qu’ici</suggestion>. |
7156 | jlepiller | 830 | #: blfs-en/postlfs/config/firmware.xml:328 |
7214 | jlepiller | 831 | #, fuzzy |
7156 | jlepiller | 832 | msgid "" |
833 | "A second AMD example is where the machine was running a stable kernel on an " |
||
834 | "older version of LFS. Note that here there is no mention of the previous " |
||
835 | "microcode version — compare this output to the AMD late loading " |
||
836 | "messages (above) from the same machine:" |
||
837 | msgstr "" |
||
7165 | jlepiller | 838 | "Un deuxième exemple AMD ou la machine lance un noyau stable sur une ancienne" |
839 | " version de LFS. Notez que ici, il n'est pas indiqué la version du micro-" |
||
840 | "code précédent — comparez cette sortie aux messages de chargement " |
||
841 | "\"tard\" (plus haut) de la même machine :" |
||
7156 | jlepiller | 842 | |
843 | #. type: Content of: <sect1><sect2><sect3><screen> |
||
844 | #: blfs-en/postlfs/config/firmware.xml:333 |
||
845 | #, no-wrap |
||
846 | msgid "" |
||
847 | "<literal>[ 0.000000] Linux version 3.18.11 (ken@milliways) (gcc version 4.9.1 (GCC) )\n" |
||
848 | " #4 SMP Thu Apr 9 21:51:05 BST 2015\n" |
||
849 | "[ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.18.11-sda5 root=/dev/sda5 video=800x600 ro\n" |
||
850 | "...\n" |
||
851 | "[ 0.584009] Trying to unpack rootfs image as initramfs...\n" |
||
852 | "[ 0.584092] microcode: updated early to new patch_level=0x010000c8\n" |
||
853 | "...\n" |
||
854 | "[ 0.586733] microcode: CPU0: patch_level=0x010000c8\n" |
||
855 | "[ 0.586778] microcode: CPU1: patch_level=0x010000c8\n" |
||
856 | "[ 0.586866] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba</literal>" |
||
857 | msgstr "" |
||
858 | "<literal>[ 0.000000] Linux version 3.18.11 (ken@milliways) (gcc version 4.9.1 (GCC) )\n" |
||
859 | " #4 SMP Thu Apr 9 21:51:05 BST 2015\n" |
||
860 | "[ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.18.11-sda5 root=/dev/sda5 video=800x600 ro\n" |
||
861 | "...\n" |
||
862 | "[ 0.584009] Trying to unpack rootfs image as initramfs...\n" |
||
863 | "[ 0.584092] microcode: updated early to new patch_level=0x010000c8\n" |
||
864 | "...\n" |
||
865 | "[ 0.586733] microcode: CPU0: patch_level=0x010000c8\n" |
||
866 | "[ 0.586778] microcode: CPU1: patch_level=0x010000c8\n" |
||
867 | "[ 0.586866] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba</literal>" |
||
868 | |||
869 | #. type: Content of: <sect1><sect2><title> |
||
870 | #: blfs-en/postlfs/config/firmware.xml:349 |
||
871 | msgid "Firmware for Video Cards" |
||
872 | msgstr "Firmware pour les cartes vidéo" |
||
873 | |||
874 | #. type: Content of: <sect1><sect2><sect3><title> |
||
875 | #: blfs-en/postlfs/config/firmware.xml:352 |
||
876 | msgid "Firmware for ATI video chips (R600 and later)" |
||
877 | msgstr "Firmware pour les puces vidéo ATI (R600 et plus)" |
||
878 | |||
879 | #. type: Content of: <sect1><sect2><sect3><para> |
||
7214 | jlepiller | 880 | #. Le verbe « applique » devrait être à la 3e personne du pluriel. |
881 | #. Voulez-vous écrire <suggestion>Appliquez-les</suggestion> ? |
||
7156 | jlepiller | 882 | #: blfs-en/postlfs/config/firmware.xml:354 |
7214 | jlepiller | 883 | #, fuzzy |
7156 | jlepiller | 884 | msgid "" |
885 | "These instructions do NOT apply to old radeons before the R600 family. For " |
||
7165 | jlepiller | 886 | "those, the firmware is in the kernel's <filename " |
887 | "class='directory'>/lib/firmware/</filename> directory. Nor do they apply if " |
||
888 | "you intend to avoid a graphical setup such as Xorg and are content to use " |
||
889 | "the default 80x25 display rather than a framebuffer." |
||
7156 | jlepiller | 890 | msgstr "" |
891 | "Ces instructions NE s'applique pas aux anciennes radeons avant la famille " |
||
7184 | jlepiller | 892 | "R600. Pour elles, le firmware est dans le répertoire du noyau <filename " |
7190 | jlepiller | 893 | "class='directory'>/lib/firmware/</filename>. Appliquez les seulement si vous" |
894 | " prévoyez d'éviter une configuration graphique tels que Xorg et que vous " |
||
7184 | jlepiller | 895 | "voulez vous contenter d'utiliser l'affichage 80x25 par défaut plutôt qu'un " |
896 | "framebuffer." |
||
7156 | jlepiller | 897 | |
898 | #. type: Content of: <sect1><sect2><sect3><para> |
||
899 | #: blfs-en/postlfs/config/firmware.xml:360 |
||
900 | msgid "" |
||
901 | "Early radeon devices only needed a single 2K blob of firmware. Recent " |
||
902 | "devices need several different blobs, and some of them are much bigger. The " |
||
903 | "total size of the radeon firmware directory is over 500K — on a large " |
||
7165 | jlepiller | 904 | "modern system you can probably spare the space, but it is still redundant to" |
905 | " install all the unused files each time you build a system." |
||
7156 | jlepiller | 906 | msgstr "" |
907 | "Les périphériques radeon plus anciens demandaient seulement un simple blob " |
||
908 | "de 2Ko. Les périphériques récents ont besoin de plusieurs blobs différents, " |
||
909 | "et certain d'entre eux sont plus gros. La taille totale du répertoire des " |
||
910 | "firmwares radeon est de plus de 500 ko — sur un gros système moderne vous " |
||
911 | "pouvez probablement utiliser cet espace, mais cela reste redondant " |
||
912 | "d'installer tous les fichiers inutiles chaque fois que vous construisez un " |
||
913 | "système." |
||
914 | |||
915 | #. type: Content of: <sect1><sect2><sect3><para> |
||
916 | #: blfs-en/postlfs/config/firmware.xml:366 |
||
917 | msgid "" |
||
918 | "A better approach is to install <xref linkend='pciutils'/> and then use " |
||
919 | "<userinput>lspci</userinput> to identify which VGA controller is installed." |
||
920 | msgstr "" |
||
921 | "Une meilleure approche est d'installer<xref linkend='pciutils'/> et ensuite " |
||
922 | "utiliser <userinput>lspci</userinput> pour identifier quel controleur VGA " |
||
923 | "est installé." |
||
924 | |||
925 | #. type: Content of: <sect1><sect2><sect3><para> |
||
7214 | jlepiller | 926 | #. « Engineering » est un anglicisme. Employez |
927 | #. <suggestion>ingénierie</suggestion>. |
||
7156 | jlepiller | 928 | #: blfs-en/postlfs/config/firmware.xml:370 |
7214 | jlepiller | 929 | #, fuzzy |
7156 | jlepiller | 930 | msgid "" |
931 | "With that information, check the RadeonFeature page of the Xorg wiki for " |
||
932 | "<ulink url=\"http://wiki.x.org/wiki/RadeonFeature/#index5h2\">Decoder ring " |
||
933 | "for engineering vs marketing names</ulink> to identify the family (you may " |
||
934 | "need to know this for the Xorg driver in BLFS — Southern Islands and " |
||
935 | "Sea Islands use the radeonsi driver) and the specific model." |
||
936 | msgstr "" |
||
937 | "Avec cette information, vérifiez la page RadeonFeature du wiki Xorg <ulink " |
||
938 | "url=\"http://wiki.x.org/wiki/RadeonFeature/#index5h2\">Decoder ring for " |
||
939 | "engineering vs marketing names</ulink> pour identifier la famille (vous " |
||
940 | "aurez besoin de savoir cela pour identifier le pilote Xorg dans BLFS — " |
||
941 | "Southern Islands et Sea Islands utilise le pilote radeonsi) et le modèle " |
||
942 | "spécifique." |
||
943 | |||
944 | #. type: Content of: <sect1><sect2><sect3><para> |
||
7214 | jlepiller | 945 | #. Voulez-vous écrire <suggestion>téléchargez-les</suggestion> ? |
7156 | jlepiller | 946 | #: blfs-en/postlfs/config/firmware.xml:376 |
7214 | jlepiller | 947 | #, fuzzy |
7156 | jlepiller | 948 | msgid "" |
7165 | jlepiller | 949 | "Now that you know which controller you are using, consult the <ulink " |
950 | "url=\"https://wiki.gentoo.org/wiki/Radeon#Firmware\">Radeon</ulink> page of " |
||
951 | "the Gentoo wiki which has a table listing the required firmware blobs for " |
||
952 | "the various chipsets. Note that Southern Islands and Sea Islands chips use " |
||
7156 | jlepiller | 953 | "different firmware for kernel 3.17 and later compared to earlier kernels. " |
954 | "Identify and download the required blobs then install them:" |
||
955 | msgstr "" |
||
956 | "Maintenant que vous savez quel contrôleur vous allez utiliser, consultez la " |
||
7190 | jlepiller | 957 | "page <ulink " |
958 | "url=\"https://wiki.gentoo.org/wiki/Radeon#Firmware\">Radeon</ulink> du wiki " |
||
959 | "Gentoo qui a un tableau listant les blobs de firmware requis pour les " |
||
960 | "différentes puces. Notez que les puces Southern Islands et Sea Islands " |
||
961 | "utilise des firmwares différents pour les noyaux 3.17 et supérieur en " |
||
962 | "comparaison des kernels antérieurs. Identifiez et téléchargez les blobs " |
||
963 | "requis et ensuite installez les :" |
||
7156 | jlepiller | 964 | |
965 | #. type: Content of: <sect1><sect2><sect3><screen> |
||
966 | #: blfs-en/postlfs/config/firmware.xml:383 |
||
967 | #, no-wrap |
||
968 | msgid "" |
||
969 | "<userinput>mkdir -pv /lib/firmware/radeon\n" |
||
970 | "cp -v <YOUR_BLOBS> /lib/firmware/radeon</userinput>" |
||
971 | msgstr "" |
||
972 | "<userinput>mkdir -pv /lib/firmware/radeon\n" |
||
973 | "cp -v <YOUR_BLOBS> /lib/firmware/radeon</userinput>" |
||
974 | |||
975 | #. type: Content of: <sect1><sect2><sect3><para> |
||
976 | #: blfs-en/postlfs/config/firmware.xml:386 |
||
977 | msgid "" |
||
978 | "There are actually two ways of installing this firmware. BLFS, in the " |
||
979 | "'Kernel Configuration for additional firmware' section part of the <xref " |
||
980 | "linkend=\"xorg-ati-driver\"/> section gives an example of compiling the " |
||
981 | "firmware into the kernel - that is slightly faster to load, but uses more " |
||
982 | "kernel memory. Here we will use the alternative method of making the radeon " |
||
983 | "driver a module. In your kernel config set the following:" |
||
984 | msgstr "" |
||
985 | "Il y a en fait deux façons d'installer ces firmwares. BLFS, dans le sous-" |
||
986 | "chapitre 'Configuration du noyau pour les firmwares supplémentaires' du " |
||
7165 | jlepiller | 987 | "chapitre <xref linkend=\"xorg-ati-driver\"/> donne un exemple de compilation" |
988 | " des firmwares dans le noyau - c'est légèrement plus rapide à charger, mais " |
||
7156 | jlepiller | 989 | "utilises plus de mémoire pour le noyau. Ici nous utiliserons la méthode " |
990 | "alternative en faisant un module du pilote radeon. Dans votre configuration " |
||
991 | "du noyau initialisez la suite :" |
||
992 | |||
993 | #. type: Content of: <sect1><sect2><sect3><screen> |
||
994 | #: blfs-en/postlfs/config/firmware.xml:393 |
||
995 | #, no-wrap |
||
996 | msgid "" |
||
997 | "<literal>Device Drivers --->\n" |
||
998 | " Graphics support --->\n" |
||
999 | " Direct Rendering Manager --->\n" |
||
1000 | " <*> Direct Rendering Manager (XFree86 ... support) [CONFIG_DRM]\n" |
||
1001 | " <m> ATI Radeon [CONFIG_DRM_RADEON]</literal>" |
||
1002 | msgstr "" |
||
1003 | "<literal>Device Drivers --->\n" |
||
1004 | " Graphics support --->\n" |
||
1005 | " Direct Rendering Manager --->\n" |
||
1006 | " <*> Direct Rendering Manager (XFree86 ... support) [CONFIG_DRM]\n" |
||
1007 | " <m> ATI Radeon [CONFIG_DRM_RADEON]</literal>" |
||
1008 | |||
1009 | #. type: Content of: <sect1><sect2><sect3><para> |
||
1010 | #: blfs-en/postlfs/config/firmware.xml:399 |
||
1011 | msgid "" |
||
1012 | "Loading several large blobs from /lib/firmware takes a noticeable time, " |
||
1013 | "during which the screen will be blank. If you do not enable the penguin " |
||
1014 | "framebuffer logo, or change the console size by using a bigger font, that " |
||
1015 | "probably does not matter. If desired, you can slightly reduce the time if " |
||
1016 | "you follow the alternate method of specifying 'y' for CONFIG_DRM_RADEON " |
||
1017 | "covered in BLFS at the link above — you must specify each needed " |
||
1018 | "radeon blob if you do that." |
||
1019 | msgstr "" |
||
1020 | "Le chargement de plusieurs blobs volumineux dans /lib/firmware prend un " |
||
1021 | "temps notable, pendant lequel l'écran est blanc. Si vous n'avez pas activé " |
||
1022 | "le logo framebuffer du pingouin, ou changé la taille de la console en " |
||
7165 | jlepiller | 1023 | "utilisant une police plus grosse, cela n'a probablement pas d'importance. Si" |
1024 | " vous le souhaitez, vous pouvez légèrement réduire le temps si vous suivez " |
||
1025 | "la méthode alternative en spécifiant 'y' pour CONFIG_DRM_RADEON couvert dans" |
||
1026 | " BLFS au lien précédent — vous devez spécifier chaque blob radeon " |
||
1027 | "utile si vous faite cela." |
||
7156 | jlepiller | 1028 | |
1029 | #. type: Content of: <sect1><sect2><sect3><title> |
||
1030 | #: blfs-en/postlfs/config/firmware.xml:410 |
||
1031 | msgid "Firmware for Nvidia video chips" |
||
1032 | msgstr "Firmware pour les puces vidéo Nvidia" |
||
1033 | |||
1034 | #. type: Content of: <sect1><sect2><sect3><para> |
||
1035 | #: blfs-en/postlfs/config/firmware.xml:412 |
||
1036 | msgid "" |
||
1037 | "Some Nvidia graphics chips need firmware updates to take advantage of all " |
||
1038 | "the card's capability. These are generally the GeForce 8, 9, 9300, and " |
||
7165 | jlepiller | 1039 | "200-900 series chips. For more exact information, see <ulink " |
1040 | "url=\"https://nouveau.freedesktop.org/wiki/VideoAcceleration/#firmware\"> " |
||
1041 | "https://nouveau.freedesktop.org/wiki/VideoAcceleration/#firmware</ulink>." |
||
7156 | jlepiller | 1042 | msgstr "" |
1043 | "Certaines puces graphiques Nvidia requièrent une mise à jour de leur " |
||
1044 | "firmware pour tirer parti de toutes les capacités de la carte. Ce sont " |
||
1045 | "généralement les puces des séries GeForce 8, 9, 9300 et 200-900. Pour de " |
||
7165 | jlepiller | 1046 | "plus amples informations, visitez <ulink " |
1047 | "url=\"https://nouveau.freedesktop.org/wiki/VideoAcceleration/#firmware\">https://nouveau.freedesktop.org/wiki/VideoAcceleration/#firmware</ulink>." |
||
7156 | jlepiller | 1048 | |
1049 | #. type: Content of: <sect1><sect2><sect3><para> |
||
1050 | #: blfs-en/postlfs/config/firmware.xml:418 |
||
1051 | msgid "First, the kernel Nvidia driver must be activated:" |
||
1052 | msgstr "Tout d'abord, le pilote Nvidia doit être activé dans le noyau :" |
||
1053 | |||
1054 | #. type: Content of: <sect1><sect2><sect3><screen> |
||
1055 | #: blfs-en/postlfs/config/firmware.xml:420 |
||
1056 | #, no-wrap |
||
1057 | msgid "" |
||
1058 | "<literal>Device Drivers --->\n" |
||
1059 | " Graphics support --->\n" |
||
1060 | " Direct Rendering Manager --->\n" |
||
1061 | " <*> Direct Rendering Manager (XFree86 ... support) [CONFIG_DRM]\n" |
||
1062 | " <*/m> Nouveau (NVIDIA) cards [CONFIG_DRM_NOUVEAU]</literal>" |
||
1063 | msgstr "" |
||
1064 | "<literal>Device Drivers --->\n" |
||
1065 | " Graphics support --->\n" |
||
1066 | " Direct Rendering Manager --->\n" |
||
1067 | " <*> Direct Rendering Manager (XFree86 ... support) [CONFIG_DRM]\n" |
||
1068 | " <*/m> Nouveau (NVIDIA) cards [CONFIG_DRM_NOUVEAU]</literal>" |
||
1069 | |||
1070 | #. type: Content of: <sect1><sect2><sect3><para> |
||
1071 | #: blfs-en/postlfs/config/firmware.xml:426 |
||
1072 | msgid "The steps to install the Nvidia firmware are:" |
||
1073 | msgstr "Les étapes pour installer le firmware Nvidia sont :" |
||
1074 | |||
1075 | #. type: Content of: <sect1><sect2><sect3><screen> |
||
1076 | #: blfs-en/postlfs/config/firmware.xml:428 |
||
1077 | #, no-wrap |
||
1078 | msgid "" |
||
1079 | "<userinput>wget https://raw.github.com/imirkin/re-vp2/master/extract_firmware.py\n" |
||
1080 | "wget http://us.download.nvidia.com/XFree86/Linux-x86/325.15/NVIDIA-Linux-x86-325.15.run\n" |
||
1081 | "sh NVIDIA-Linux-x86-325.15.run --extract-only\n" |
||
1082 | "python extract_firmware.py \n" |
||
1083 | "mkdir -p /lib/firmware/nouveau\n" |
||
1084 | "cp -d nv* vuc-* /lib/firmware/nouveau/</userinput>" |
||
1085 | msgstr "" |
||
1086 | "<userinput>wget https://raw.github.com/imirkin/re-vp2/master/extract_firmware.py\n" |
||
1087 | "wget http://us.download.nvidia.com/XFree86/Linux-x86/325.15/NVIDIA-Linux-x86-325.15.run\n" |
||
1088 | "sh NVIDIA-Linux-x86-325.15.run --extract-only\n" |
||
1089 | "python extract_firmware.py \n" |
||
1090 | "mkdir -p /lib/firmware/nouveau\n" |
||
1091 | "cp -d nv* vuc-* /lib/firmware/nouveau/</userinput>" |
||
1092 | |||
1093 | #. type: Content of: <sect1><sect2><title> |
||
1094 | #: blfs-en/postlfs/config/firmware.xml:439 |
||
1095 | msgid "Firmware for Network Interfaces" |
||
1096 | msgstr "Firmware pour les interfaces réseaux" |
||
1097 | |||
1098 | #. type: Content of: <sect1><sect2><para> |
||
7214 | jlepiller | 1099 | #. « pilotes » et « réseau » ne semblent pas bien accordés en nombre. |
1100 | #. Le verbe « avez » devrait être à la 3e personne. |
||
7156 | jlepiller | 1101 | #: blfs-en/postlfs/config/firmware.xml:441 |
7214 | jlepiller | 1102 | #, fuzzy |
7156 | jlepiller | 1103 | msgid "" |
1104 | "The kernel likes to load firmware for some network drivers, particularly " |
||
1105 | "those from Realtek (the /lib/linux-firmware/rtl_nic/) directory, but they " |
||
1106 | "generally appear to work without it. Therefore, you can boot the kernel, " |
||
1107 | "check dmesg for messages about this missing firmware, and if necessary " |
||
7165 | jlepiller | 1108 | "download the firmware and put it in the specified directory in /lib/firmware" |
1109 | " so that it will be found on subsequent boots. Note that with current " |
||
1110 | "kernels this works whether or not the driver is compiled in or built as a " |
||
1111 | "module, there is no need to build this firmware into the kernel. Here is an" |
||
1112 | " example where the R8169 driver has been compiled in but the firmware was " |
||
1113 | "not made available. Once the firmware had been provided, there was no " |
||
1114 | "mention of it on later boots." |
||
7156 | jlepiller | 1115 | msgstr "" |
1116 | "Le noyau aime charger des firmware pour quelques pilotes réseau, " |
||
1117 | "particulièrement ceux du répertoire Realtek (/lib/linux-firmware/rtl_nic/), " |
||
1118 | "mais il apparaît généralement que cela fonctionne sans. Cependant, vous " |
||
1119 | "pouvez démarrer le noyau, vérifiez dmesg pour les messages à propos de " |
||
1120 | "firmwares manquants, et si nécessaire télécharger les firmwares et les " |
||
7165 | jlepiller | 1121 | "mettre dans un répertoire spécifique dans /lib/firmware afin qu'ils puissent" |
1122 | " être trouvés pendant la séquence de démarrage. Notez qu'avez les noyaux " |
||
1123 | "actuels cela fonctionne que le pilote soit compilé dedans ou construit comme" |
||
1124 | " un module, il n'est pas utile de construire ce firmware dans le noyau. Ici " |
||
7156 | jlepiller | 1125 | "un exemple ou le pilote R8169 a été compilé dedans mais le firmware n'est " |
1126 | "pas disponible. Une fois que le firmware a été fourni, il n'y est plus fait " |
||
1127 | "mention dans les démarrages suivants." |
||
1128 | |||
1129 | #. type: Content of: <sect1><sect2><screen> |
||
1130 | #: blfs-en/postlfs/config/firmware.xml:453 |
||
1131 | #, no-wrap |
||
1132 | msgid "" |
||
1133 | "<literal>dmesg | grep firmware | grep r8169\n" |
||
1134 | "[ 7.018028] r8169 0000:01:00.0: Direct firmware load for rtl_nic/rtl8168g-2.fw failed with error -2\n" |
||
1135 | "[ 7.018036] r8169 0000:01:00.0 eth0: unable to load firmware patch rtl_nic/rtl8168g-2.fw (-2)</literal>" |
||
1136 | msgstr "" |
||
1137 | "<literal>dmesg | grep firmware | grep r8169\n" |
||
1138 | "[ 7.018028] r8169 0000:01:00.0: Direct firmware load for rtl_nic/rtl8168g-2.fw failed with error -2\n" |
||
1139 | "[ 7.018036] r8169 0000:01:00.0 eth0: unable to load firmware patch rtl_nic/rtl8168g-2.fw (-2)</literal>" |
||
1140 | |||
1141 | #. type: Content of: <sect1><sect2><title> |
||
1142 | #: blfs-en/postlfs/config/firmware.xml:460 |
||
1143 | msgid "Firmware for Other Devices" |
||
1144 | msgstr "Firmware pour les autres périphériques" |
||
1145 | |||
1146 | #. type: Content of: <sect1><sect2><para> |
||
1147 | #: blfs-en/postlfs/config/firmware.xml:462 |
||
1148 | msgid "" |
||
7165 | jlepiller | 1149 | "Identifying the correct firmware will typically require you to install <xref" |
1150 | " linkend='pciutils'/>, and then use <userinput>lspci</userinput> to identify" |
||
1151 | " the device. You should then search online to check which module it uses, " |
||
1152 | "which firmware, and where to obtain the firmware — not all of it is in" |
||
1153 | " linux-firmware." |
||
7156 | jlepiller | 1154 | msgstr "" |
1155 | "Pour identifier le bon firmware vous devrez normallement install <xref " |
||
1156 | "linkend='pciutils'/> puis utiliser <userinput>lspci</userinput> pour " |
||
7165 | jlepiller | 1157 | "identifier le matériel. Vous devriez ensuite chercher en ligne pour vérifier" |
1158 | " le module qu’il utilise, quel firmware et où obtenir le firmware — " |
||
1159 | "ils ne sont pas tous dans linux-firmware." |
||
7156 | jlepiller | 1160 | |
1161 | #. type: Content of: <sect1><sect2><para> |
||
1162 | #: blfs-en/postlfs/config/firmware.xml:468 |
||
1163 | msgid "" |
||
1164 | "If possible, you should begin by using a wired connection when you first " |
||
1165 | "boot your LFS system. To use a wireless connection you will need to use a " |
||
1166 | "network tools such as <xref linkend='wireless_tools'/> and <xref " |
||
1167 | "linkend='wpa_supplicant'/>." |
||
1168 | msgstr "" |
||
1169 | "Si possible, vous pouvez commencer par utiliser une connexion filaire quand " |
||
1170 | "vous démarrez la première fois votre système LFS. Pour utiliser une " |
||
1171 | "connexion sans fils vous aurez besoin d'utiliser des outils réseau tel que " |
||
1172 | "<xref linkend='wireless_tools'/> et <xref linkend='wpa_supplicant'/>." |
||
1173 | |||
1174 | #. type: Content of: <sect1><sect2><para> |
||
1175 | #: blfs-en/postlfs/config/firmware.xml:473 |
||
1176 | msgid "" |
||
7165 | jlepiller | 1177 | "Firmware may also be needed for other devices such as some SCSI controllers," |
1178 | " bluetooth adaptors, or TV recorders. The same principles apply." |
||
7156 | jlepiller | 1179 | msgstr "" |
1180 | "Les firmwares peuvent aussi être utiles pour d'autres périphériques comme " |
||
1181 | "les contrôleurs SCSI, les adaptateurs Bluetooth, ou les enregistreurs TV. " |
||
1182 | "Les mêmes principes s'appliquent." |