Ignore:
Timestamp:
01/09/2020 04:18:14 PM (4 years ago)
Author:
Pierre Labastie <pieere@…>
Branches:
10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 9.1, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, lazarus, lxqt, 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:
cce4984
Parents:
e3b66f3
Message:

Add early loading of microcode to the initramfs
Fix a bug in mkinitramfs, leading to a "cp" error

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@22557 af4574ff-66df-0310-9fd7-8a98e5e911e0

File:
1 edited

Legend:

Unmodified
Added
Removed
  • postlfs/config/firmware.xml

    re3b66f3 r6e493187  
    309309
    310310      <para>If you are already booting with an initrd (see <xref
    311       linkend="initramfs"/>) you must specify the microcode initrd first, using
    312       a line such as <userinput>initrd /microcode.img
    313       /other-initrd.img</userinput> (adapt that as above if /boot is not a
    314       separate mountpoint).</para>
     311      linkend="initramfs"/>), you should run <command>mkinitramfs</command>
     312      again after putting the appropriate blob or container into <filename
     313      class="directory">/lib/firmware</filename> as explained above.
     314      Alternatively, you can have both initrd on the same line, such as
     315      <userinput>initrd /microcode.img /other-initrd.img</userinput> (adapt
     316      that as above if /boot is not a separate mountpoint).</para>
    315317
    316318      <para>You can now reboot with the added initrd, and then use the same
Note: See TracChangeset for help on using the changeset viewer.