Changeset 83cc2cc3
- Timestamp:
- 05/07/2022 07:33:11 AM (2 years ago)
- Branches:
- 11.2, 11.3, 12.0, 12.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, xry111/llvm18, xry111/soup3, xry111/xf86-video-removal
- Children:
- ac7f1b0
- Parents:
- 083a8d7
- Files:
-
- 3 edited
Legend:
- Unmodified
- Added
- Removed
-
postlfs/config/firmware.xml
r083a8d7 r83cc2cc3 612 612 </sect3> 613 613 614 <sect3 id="amdgpu-video-firmware"> 615 <title>Firmware for AMD/ATI amdgpu video chips</title> 616 617 <para> 618 All video controllers using the amdgpu kernel driver require firmware, 619 whether you will be using the xorg amdgpu driver, the xserver's modesetting 620 driver, or just kernel modesetting to get a console framebuffer larger than 621 80x25. 622 </para> 623 624 <para> 625 Install <xref linkend="pciutils"/> and use that to check the model name 626 (look for 'VGA compatible controller:'). If you have an APU (Accelerated 627 Processing Unit, i.e. CPU and video on the same chip) that will probably 628 tell you the name. If you have a separate amdgpu video card you will need 629 to search to determine which name it uses (e.g. a card described as 630 Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 550 640SP / RX 631 560/560X] needs Polaris11 firmware. There is a table of "Family, Chipset 632 name, Product name and Firmware" at the end of the Kernel sections in 633 <ulink url="https://wiki.gentoo.org/wiki/AMDGPU#Known_firmware_blobs"> 634 AMDGPU</ulink> page of the Gentoo wiki. 635 </para> 636 637 <para> 638 Once you have identified the firmware name, install all the relevant 639 files for it. For example, the Baffin card mentioned above has 21 different 640 polaris11* files, APUs such as renoir and picasso have at least 12 files and 641 might gain more in future updates (e.g. the raven APU now has a 13th file, 642 raven_ta.bin). 643 </para> 644 645 <screen><userinput>mkdir -pv /lib/firmware/amdgpu 646 cp -v <YOUR_BLOBS> /lib/firmware/amdgpu</userinput></screen> 647 648 <para> 649 If disk space is not a problem, you could install all the current amdgpu 650 firmware files and not worry about exactly which chipset is installed. 651 </para> 652 653 <para> 654 You are recommended to build the kernel amdgpu driver as a module. 655 In your kernel .config set at least the following options and review 656 the other AMDGPU options according to what hardware you are building 657 for, e.g ACP (Audio Co-Processor) support for some APUs, 658 </para> 659 660 <screen><literal>Device Drivers ---> 661 Graphics support ---> 662 Direct Rendering Manager ---> 663 [*] Direct Rendering Manager (XFree86 ... support) [CONFIG_DRM] 664 [M] AMD GPU [CONFIG_DRM_AMDGPU] 665 Display Engine Configuration ---> 666 [*] AMD DC - Enable new display engine (NEW) [CONFIG_DRM_AMD_DC]</literal></screen> 667 668 <para> 669 As written above at the end of the section on 'Firmware for ATI video 670 chips', loading large blobs from /lib/firmware can take a noticeable 671 time during which the screen will be blank. On a slow machine you might 672 wish to refer to the 'Kernel Configuration for additional firmware' 673 part of <xref linkend="xorg-amdgpu-driver"/> and compile all the 674 required modules into the kernel to reduce this time, at the cost of 675 using more kernel memory. 676 </para> 677 678 </sect3> 679 614 680 <sect3 id="nvidia-video-firmware"> 615 681 <title>Firmware for Nvidia video chips</title> -
x/installing/x7driver-amdgpu.xml
r083a8d7 r83cc2cc3 49 49 driver at <xref linkend="mesa"/> build time. Also, all cards and newer APUs 50 50 require Firmware to be available when the kernel driver is loaded. 51 Firmware can be obtained from <ulink 52 url="&sources-anduin-http;/linux-firmware/"/>. 53 See <xref linkend="xorg-amdgpu-firmware-kernel"/> below for additional 51 If you have not followed the instructions in the Firmware 52 for Video Cards part of <xref linkend="postlfs-firmware"/> which provided 53 that firmware in <filename class="directory">/lib/firmware</filename> 54 for a modular build, 55 firmware can be obtained from <ulink 56 url="&sources-anduin-http;/linux-firmware/"/> - 57 see <xref linkend="xorg-amdgpu-firmware-kernel"/> below for additional 54 58 firmware. 55 59 </para> -
x/installing/x7driver-ati.xml
r083a8d7 r83cc2cc3 48 48 drivers at <xref linkend="mesa"/> build time. Also, some cards 49 49 require Firmware to be available when the kernel driver is loaded. 50 Firmware can be obtained from <ulink 51 url="&sources-anduin-http;/linux-firmware/"/>. 52 See <xref linkend="xorg-ati-firmware-kernel"/> below for additional 50 In that case, if you have not followed the instructions in the Firmware 51 for Video Cards part of <xref linkend="postlfs-firmware"/> which provided 52 that firmware in <filename class="directory">/lib/firmware</filename> 53 for a modular build, 54 firmware can be obtained from <ulink 55 url="&sources-anduin-http;/linux-firmware/"/> - 56 see <xref linkend="xorg-ati-firmware-kernel"/> below for additional 53 57 firmware. 54 58 </para>
Note:
See TracChangeset
for help on using the changeset viewer.