Overview

Project website www.linuxfromscratch.org
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Any authenticated user can contribute.
  • The translation uses bilingual files.
Source code repository git@git.linuxfromscratch.org:fr-lfs
Repository branch 12.0
Last remote commit Add Portuguese (Brazil) BLFS 5a031b636f
Julien Lepiller authored 8 months ago
Last commit in Weblate Translated using Weblate (Portuguese (Brazil)) e69745902a
User avatar jamenson authored 7 months ago
Weblate repository https://translate.linuxfromscratch.org/git/linux-from-scratch-12-0/index/
File mask blfs/*/postlfs/config/firmware.po
Translation file Download blfs/fr/postlfs/config/firmware.po
Last change March 22, 2024, 7:42 a.m.
Last author Weblate Admin
a month ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 101 3,450 24,501
Translated 100% 101 100% 3,450 100% 24,501
Needs editing 0% 0 0% 0 0% 0
Read-only 0% 0 0% 0 0% 0
Failing checks 10% 11 17% 592 19% 4,716
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 0% 0 0% 0 0% 0
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 1 change 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 102 changes 0 changes 0 changes 0 changes
Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct

Quick numbers

3,450
Hosted words
101
Hosted strings
100%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
+100%
—
Hosted strings
+100%
—
Translated
+100%
—
Contributors
—
User avatar admin

Resource updated
The “blfs/fr/postlfs/config/firmware.po” file was changed. 8 months ago
User avatar None

Resource updated
File “blfs/fr/postlfs/config/firmware.po” was added. a year ago
User avatar None

String updated in the repository
Do not distribute a kernel image containing the firmware to others or you may violate the GPL.
Ne distribuez pas une image du noyau contenant les micrologiciels à d'autres personnes ou vous pourriez violer la licence GPL.
a year ago
User avatar None

String updated in the repository
Replace <replaceable>amdgpu/*</replaceable> with a shell pattern matching the needed firmware files.
Remplacez <replaceable>amdgpu/*</replaceable> par un motif shell correspondant aux fichiers de micrologiciel requis.
a year ago
User avatar None

String updated in the repository
<userinput>echo CONFIG_EXTRA_FIRMWARE='"'$({ cd /lib/firmware; echo <replaceable>amdgpu/*</replaceable> })'"' &gt;&gt; .config
make oldconfig</userinput>
<userinput>echo CONFIG_EXTRA_FIRMWARE='"'$({ cd /lib/firmware; echo <replaceable>amdgpu/*</replaceable> })'"' &gt;&gt; .config
make oldconfig</userinput>
a year ago
User avatar None

String updated in the repository
Replace <replaceable>xx/aa.bin xx/bb.bin</replaceable> with a whitespace-separated list of paths to the needed firmware files, relative to <filename class='directory'>/lib/firmware</filename>. A method easier than manually typing the list (it may be long) is running the following command:
Remplacez <replaceable>xx/aa.bin xx/bb.bin</replaceable> par une liste de chemins séparés par des espaces vers les fichiers requis, relativement à <filename class='directory'>/lib/firmware</filename>. Une méthode plus simple que de taper la liste complète à la main (ça peut être long) consiste à exécuter la commande suivante&nbsp;:
a year ago
User avatar None

String updated in the repository
Some drivers, notably the drivers for ATI or AMD GPU, requires the firmware files accessible at the time it is loaded. The easiest method to handle these drivers is building them as a kernel module. An alternative method is creating an initramfs (read <xref linkend='initramfs'/> for details) including the firmware files. If you don't want to use either methods, you may include the firmware files in the kernel image itself. Install the needed firmware files into <filename class='directory'>/lib/firmware</filename> first, then set the following kernel configuration and rebuild the kernel:
Certains pilotes, surtout les pilotes pour les GPU ATI ou AMD, ont besoin que des fichiers de micrologiciel soient accessibles au chargement. La méthode la plus facile de gérer ces pilotes est de les construire en tant que module du noyau. Une autre méthode consiste à créer un initramfs (consultez <xref linkend='initramfs'/> pour les détails) qui contiendrait les fichiers du micrologiciel. Si vous ne voulez pas utiliser ces méthodes, vous pouvez inclure directement les fichiers du micrologiciel dans l'image du noyau. Installez d'abord les fichiers de micrologiciel requis dans <filename class='directory'>/lib/firmware</filename>, puis configurez le noyau et reconstruisez-le&nbsp;:
a year ago
User avatar None

String updated in the repository
Include Firmware Blobs in the Kernel Image
Inclure les blobs des micrologiciels dans l'image du noyau
a year ago
User avatar None

String updated in the repository
Firmware may also be needed for other devices such as some SCSI controllers, bluetooth adaptors, or TV recorders. The same principles apply.
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.
a year ago
User avatar None

String updated in the repository
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="iw"/>, <xref linkend='wireless_tools'/>, or <xref linkend='wpa_supplicant'/>.
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 tels que <xref linkend="iw"/>, <xref linkend='wireless_tools'/> ou <xref linkend='wpa_supplicant'/>.
a year ago
Browse all translation changes