Changeset 0f5515d
- Timestamp:
- 03/13/2023 05:38:33 PM (15 months ago)
- Branches:
- 12.0, 12.1, kea, ken/TL2024, ken/tuningfonts, lazarus, lxqt, plabs/newcss, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, trunk, xry111/llvm18, xry111/xf86-video-removal
- Children:
- 457f841, f751d6e
- Parents:
- 00120f96
- git-author:
- Pierre Labastie <pierre.labastie@…> (03/13/2023 05:36:58 PM)
- git-committer:
- Pierre Labastie <pierre.labastie@…> (03/13/2023 05:38:33 PM)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
postlfs/config/firmware.xml
r00120f96 r0f5515d 665 665 </sect2> 666 666 667 <sect2 id="other-firmware"> 668 <title>Firmware for Other Devices</title> 669 670 <para> 671 Identifying the correct firmware will typically require you to install 672 <xref linkend='pciutils'/>, and then use <userinput>lspci</userinput> 673 to identify the device. You should then search online to check which 674 module it uses, which firmware, and where to obtain the firmware — 675 not all of it is in linux-firmware. 676 </para> 677 678 <para> 679 If possible, you should begin by using a wired connection when you first 680 boot your LFS system. To use a wireless connection you will need to 681 use a network tools such as <xref linkend='wireless_tools'/> and <xref 682 linkend='wpa_supplicant'/>. 683 </para> 667 <sect2 id="regulatory-db"> 668 <title>Firmware for Regulatory Database of Wireless Devices</title> 684 669 685 670 <para> … … 693 678 To install it, simply extract <filename>regulatory.db</filename> and 694 679 <filename>regulatory.db.p7s</filename> from the tarball into 695 <filename class="directory">/lib/firmware</filename>. 696 The access point would send a country code to your wireless NIC, 680 <filename class="directory">/lib/firmware</filename>. Note that either 681 the <option>cfg80211</option> driver needs to be selected as a module 682 for the <filename>regulatory.*</filename> 683 files to be loaded, or those files need to be included as firmware into 684 the kernel, as explained above in <xref linkend="video-firmware"/>. 685 </para> 686 687 <para> 688 The access point (AP) would send a country code to your wireless NIC, 697 689 and <xref linkend='wpa_supplicant'/> would tell the kernel to load 698 690 the regulation of this country from 699 <filename>regulatory.db</filename>, and enforce it. 691 <filename>regulatory.db</filename>, and enforce it. Note that several AP 692 don't send this country code, so you may be locked to a rather 693 restricted usage (specially if you want to use your interface as an AP). 694 </para> 695 </sect2> 696 697 <sect2 id="other-firmware"> 698 <title>Firmware for Other Devices</title> 699 700 <para> 701 Identifying the correct firmware will typically require you to install 702 <xref linkend='pciutils'/>, and then use <userinput>lspci</userinput> 703 to identify the device. You should then search online to check which 704 module it uses, which firmware, and where to obtain the firmware — 705 not all of it is in linux-firmware. 706 </para> 707 708 <para> 709 If possible, you should begin by using a wired connection when you first 710 boot your LFS system. To use a wireless connection you will need to 711 use a network tools such as <xref linkend="iw"/>, 712 <xref linkend='wireless_tools'/>, or <xref linkend='wpa_supplicant'/>. 700 713 </para> 701 714
Note:
See TracChangeset
for help on using the changeset viewer.