Component Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
FAQ CC-BY-NC-SA-2.0 0 0 0 0 13 0 0
Glossary Terminology CC-BY-NC-SA-2.0 0 0 0 0 0 0 0

Overview

Project website www.linuxfromscratch.org/faq
Instructions for translators

This is the translation of the FAQ from the official LFS website. Preserve HTML markup, but you should change the links to the location of a translated resource.
Translation license CC-BY-NC-SA-2.0 FAQ
5 hours ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 484 8,640 59,530
Translated 100% 484 100% 8,640 100% 59,530
Needs editing 0% 0 0% 0 0% 0
Read-only 100% 484 100% 8,640 100% 59,530
Failing checks 2% 13 2% 185 2% 1,234
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 485 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes
Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct

Quick numbers

8,640
Hosted words
484
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 None

Resource updated
File “faq/faq.pot” was added. a year ago
User avatar admin

Source string added
Note that a governor may behave differently on different CPUs. For example, the "powersave" governor may work fine for one CPU model, but lock another CPU at 800 MHz no matter if there is a workload running. If you can't (or don't want to spend too much time to) find an ideal setting, use the "performance" governor.
a year ago
User avatar admin

Source string added
If your CPU is running at a much lower frequency than expected (an Intel Core i3 building the kernel but running at only 800 MHz is definitely too slow), try to adjust the setting of "Default CPUFreq governor" in the kernel configuration and rebuild the kernel. The ideal setting should limit the CPU at a low frequency when the system is idle, but boost it to the maximum performance while a workload is running.
a year ago
User avatar admin

Source string added
But, if the LFS system is <b>very</b> slow (for example, takes 5 hours to build a kernel while the host distro needs only one hour to build the same kernel with exactly same configuration), it likely indicates a CPU dynamic frequency scaling issue. You can monitor the value of "cpu MHz" in <code>/proc/cpuinfo</code> to see if your CPU is running at a reasonable frequency while a workload (like, building the kernel) is running on the CPU.
a year ago
User avatar admin

Source string added
If the LFS system is slower than another distro but not much slower, it's normal. We focus on building a Linux system from source code and we do nothing to tweak the system for marginal performance improvements. The other distros may enable additional compiler optimizations, tune kernel options (via sysctl), or use other approaches to squeeze more performance out. And, LFS uses a latest GCC release which is likely slower than an old GCC release. A new GCC release often attempts to optimize the target code more heavily (these optimizations will slow down the compiliation, but hopefully make the compiled program faster). So LFS will take more time building a large package (like Linux kernel).
a year ago
User avatar admin

Source string added
LFS system is much slower than the host distro (or another distro)
a year ago
User avatar admin

Source string added
You can always report this kind of issue to <a href="https://bugzilla.kernel.org">Kernel bug tracker</a>, no matter if it's a BIOS bug. The kernel developers want to make Linux runable even if the BIOS has this kind of bug.
a year ago
User avatar admin

Source string added
And, you can try <a href="https://wiki.debian.org/OverridingDSDT">ACPI DSDT override</a> if you really understand it.
a year ago
User avatar admin

Source string added
If you see message like this but your system functions normally, you can ignore it. If the system malfunctions, you can try the combinations of several kernel options to workaround: <code>irqpoll</code>, <code>noapic</code>, <code>pci=nocrs</code>, and <code>i8042.nopnp=1</code>.
a year ago
User avatar admin

Source string added
It may be a bug in the firmware (BIOS) or the drivers in kernel. Some hardware vendors tend to use Windows-specific hacks in their BIOS, which is misinterpreted by Linux kernel and causing this kind of issue.
a year ago
Browse all changes for this language