Changeset f3429309 for postlfs/config
- Timestamp:
- 11/13/2015 02:24:57 PM (8 years ago)
- Branches:
- 10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 7.10, 7.9, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, basic, bdubbs/svn, elogind, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, lazarus, lxqt, nosym, perl-modules, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal
- Children:
- 9fd7f516
- Parents:
- 6c91a92a
- Location:
- postlfs/config
- Files:
-
- 3 edited
Legend:
- Unmodified
- Added
- Removed
-
postlfs/config/firmware.xml
r6c91a92a rf3429309 23 23 to make them work at their best. There is a directory, <filename 24 24 class="directory">/lib/firmware</filename>, where the kernel or kernel 25 drivers look for firmware images.</para> 26 25 drivers look for firmware images.</para> 26 27 27 <para>Preparing firmware for multiple different machines, as a distro would 28 28 do, is outside the scope of this book.</para> … … 35 35 browser at <ulink 36 36 url="&sources-anduin-http;/linux-firmware/"/>.</para> 37 37 38 38 <para>To get the firmware, either point a browser to one of the above 39 39 repositories and then download the item(s) which you need, or install 40 40 <userinput>git</userinput> and clone that repository.</para> 41 41 42 42 <para>For some other firmware, particularly for Intel microcode and certain 43 43 wifi devices, the needed firmware is not available in the above repository. … … 75 75 </itemizedlist> 76 76 77 <note><para>Although not needed to load a firmware blob, the following 78 tools may be useful for determining, obtaining, or preparing the needed 77 <note><para>Although not needed to load a firmware blob, the following 78 tools may be useful for determining, obtaining, or preparing the needed 79 79 firmware in order to load it into the system: 80 80 <xref linkend="cpio"/>, … … 96 96 released. These updates only last until the machine is powered off, so they 97 97 need to be applied on every boot.</para> 98 98 99 99 <para>There are two ways of loading the microcode, described as 'early' and 100 100 'late'. Early loading happens before userspace has been started, late … … 109 109 Broadwell-Y</ulink>.) Without this update glibc can do the wrong thing in 110 110 uncommon situations.</para> 111 111 112 112 <para>It is much simpler to begin by building a kernel which boots on 113 113 your hardware, try late microcode loading to see if there is an update (in 114 114 many cases the BIOS or UEFI will have already applied any update), and then 115 115 take the extra steps required for early loading.</para> 116 116 117 117 <para>This means you will be reconfiguring your kernel if you use early 118 118 loading, so keep the built source around to minimise what gets rebuilt, and … … 120 120 of the EXTRAVERSION in the kernel configuration, e.g. "EXTRAVERSION -A" if 121 121 nothing was set.</para> 122 122 123 123 <para>To confirm what processor(s) you have (if more than one, they will be 124 124 identical) look in /proc/cpuinfo.</para> … … 146 146 to install it.</para> 147 147 148 <para>Begin by extracting the tarball and changing to the directory it created. 148 <para>Begin by extracting the tarball and changing to the directory it created. 149 149 Then change to the source diirectory and run:</para> 150 150 … … 201 201 <para>If the microcode was not updated, there is no new microcode for 202 202 this system's processor. If it did get updated, you can now proceed to <xref 203 linkend='early-microcode'/>.</para> 203 linkend='early-microcode'/>.</para> 204 204 205 205 </sect3> … … 220 220 221 221 <para>When you configure the kernel, use the following options to try 222 late loading of AMD microcode:</para> 222 late loading of AMD microcode:</para> 223 223 224 224 <screen><literal>Processor type and features ---> … … 239 239 <para>If the microcode was not updated, there is no new microcode for 240 240 this system's processor. If it did get updated, you can now proceed to <xref 241 linkend='early-microcode'/>.</para> 241 linkend='early-microcode'/>.</para> 242 242 243 243 </sect3> … … 255 255 working you can apply the same initrd to later LFS systems or newer 256 256 kernels on this same machine, at least until any newer microcode is 257 released. Use the following commands:</para> 257 released. Use the following commands:</para> 258 258 259 259 <screen><userinput>mkdir -p initrd/kernel/x86/microcode … … 310 310 311 311 <screen><literal>[ 0.000000] CPU0 microcode updated early to revision 0x29, date = 2013-06-12 312 [ 0.000000] Linux version 4.0.0-rc6 (ken@jtm1) (gcc version 4.9.2 (GCC) ) 312 [ 0.000000] Linux version 4.0.0-rc6 (ken@jtm1) (gcc version 4.9.2 (GCC) ) 313 313 #3 SMP PREEMPT Mon Mar 30 21:26:02 BST 2015 314 314 [ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-4.0.0-rc6-sda13 root=/dev/sda13 ro … … 329 329 kernel on an older version of LFS. Note that here there is no mention of 330 330 the previous microcode version — compare this output to the AMD 331 late loading messages (above) from the same machine:</para> 332 333 <screen><literal>[ 0.000000] Linux version 3.18.11 (ken@milliways) (gcc version 4.9.1 (GCC) ) 331 late loading messages (above) from the same machine:</para> 332 333 <screen><literal>[ 0.000000] Linux version 3.18.11 (ken@milliways) (gcc version 4.9.1 (GCC) ) 334 334 #4 SMP Thu Apr 9 21:51:05 BST 2015 335 335 [ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.18.11-sda5 root=/dev/sda5 video=800x600 ro … … 348 348 <sect2 id="ati-video-firmware"> 349 349 <title>Firmware for ATI video chips (R600 and later)</title> 350 350 351 351 <para>These instructions do NOT apply to old radeons before the R600 352 352 family. For those, the firmware is in the kernel's <filename … … 371 371 Sea Islands use the radeonsi driver) and the specific model.</para> 372 372 373 <para>Now that you know which controller you are using, consult the 373 <para>Now that you know which controller you are using, consult the 374 374 <ulink url="https://wiki.gentoo.org/wiki/Radeon#Firmware">Radeon</ulink> page 375 375 of the Gentoo wiki which has a table listing the required firmware blobs … … 433 433 online to check which module it uses, which firmware, and where to obtain 434 434 the firmware — not all of it is in linux-firmware.</para> 435 435 436 436 <para>If possible, you should begin by using a wired connection when you 437 437 first boot your LFS system. To use a wireless connection you will need to 438 438 use a network tools such as <xref linkend='wireless_tools'/> and <xref 439 439 linkend='wpa_supplicant'/>.</para> 440 440 441 441 <para>Firmware may also be needed for other devices such as some SCSI 442 442 controllers, bluetooth adaptors, or TV recorders. The same principles -
postlfs/config/lsb-release.xml
r6c91a92a rf3429309 86 86 87 87 <para> 88 The configuration for this package was done in 89 <ulink url="&lfs-website;/lfs/view/stable/chapter09/theend.html">LFS</ulink>. 88 The configuration for this package was done in 89 <ulink url="&lfs-website;/lfs/view/stable/chapter09/theend.html">LFS</ulink>. 90 90 The file <filename>/etc/lsb-release</filename> should already exist. 91 91 Be sure that the DISTRIB_CODENAME entry has been set properly. -
postlfs/config/profile.xml
r6c91a92a rf3429309 220 220 <para>This script adds some useful paths to the <envar>PATH</envar> and 221 221 can be used to customize other PATH related environment variables 222 (e.g. LD_LIBRARY_PATH, etc) that may be needed for all users.</para> 222 (e.g. LD_LIBRARY_PATH, etc) that may be needed for all users.</para> 223 223 224 224 <screen role="root"><userinput>cat > /etc/profile.d/extrapaths.sh << "EOF"
Note:
See TracChangeset
for help on using the changeset viewer.