AMD Linux Graphics Drivers and How They Are Used in Slackware.
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Use "inxi -G" in terminal emulator.
You can create an xorg.conf file to choose between modesetting and amdgpu 2D drivers. I believe amdgpu should probably load if no xorg.conf is present.
Wayland is an option you can choose out of the box on Slackware64-current only with Plasma Desktop. I generally still use Xorg with xfce4.
Use "inxi -G" in terminal emulator.
You can create an xorg.conf file to choose between modesetting and amdgpu 2D drivers. I believe amdgpu should probably load if no xorg.conf is present.
Wayland is an option you can choose out of the box on Slackware64-current only with Plasma Desktop. I generally still use Xorg with xfce4.
I learned something today. Had no idea inxi existed but thanks to you I can finally stop using "glxinfo |grep Open" to check my gpu drivers.
Use "inxi -G" in terminal emulator.
You can create an xorg.conf file to choose between modesetting and amdgpu 2D drivers. I believe amdgpu should probably load if no xorg.conf is present.
Wayland is an option you can choose out of the box on Slackware64-current only with Plasma Desktop. I generally still use Xorg with xfce4.
Awesome!
Based on this, I am using the amdgpu driver. Anyone know if there is any benefit on 14.2 to be running the modesetting driver over the amdgpu driver?
I lost track of this thread and should have jumped in sooner. To review, AMDGPU-PRO is the proprietary driver and also contains the open source components. The main proprietary components are OpenCL and Vulkan. AMDGPU (kernel amdgpu.ko) is the F/OSS piece (from -PRO), along with GPU kernel firmware and MESA provides OpenGL/Vulkan 2D/3D.
xf86-video-amdgpu is the X.org driver (amdgpu.drv) that will use amdgpu.ko if present. amddrv.drv is required for xorg-server etc to function optimally with amdgpu.ko. Everyone running default Slackware and Xfce, KDE or another DE or WM, is using X.org to draw pretty 2D/3D desktop GUIs useless they loaded something else. AFAIK, Wayland can't as of yet provide hardware 3D acceleration and rendering.
There is generally no benefit to running the modesetting driver for newer cards recognized by amdgpu.drv (loaded by default, see /usr/share/X11/xorg.conf.d/10-amdgpu.conf) as this driver will look for amdgpu.ko. However, since AMD GPU kernel support in 14.2 is old, you will not benefit if you have a newer AMD Sea/Volcanic Islands, Polaris, Vega, or Navi era gpu from any available driver or kernel module. All new code development goes into newer kernels for amdgpu and Mesa. This is why I waited until Slackware-current kernel 5.4.x to switch from Nvidia to AMD Radeon RX590 (Polaris) and Radeon RX 570O XT (Navi).
If you are running older cards, for X.org these will use (in xorg.conf etc) either 'ati', 'radeon'. Details for which kernel module is used is on the respective manpages. These drivers are pretty much dead, from XFree86 and then X.org project. AMD does not provide code to these drives.
The 'modesetting' X.org driver (framebuffer, part of xorg-server-xx) is device agnostic and requires a kernel KMS module, if your GPU has a KMS module. Both have nothing to do with xf86-video-amdgpu. (see man modesetting) It is horribly slow but may be useful in certain use cases and applications.
The phoronix article was not entirely correct. Anyone using X.org and newer AMD GPU needs xf86-video-amdgpu for full 2D/3D support. X.org needed to update xf86-video-amdgpu to add support for newer AMD GPUs from GPU series Sea/Volcanic Islands, Polaris, Vega, and now NAVI and Navi2. If you don't use X.org, then you don't need it.
The OpenCL bits are enabled thanks to @kingbeowulf's amdgpu-opencl.SlackBuild. Despite being a bit outdated now, it still works with OSS amdgpu built into kernel-modules-5.17.1-x86_64-1 from -current.
OpenCL benefits are way beyond crypto-whatever stuff. They are also available to some processing intensive tasks for the average joe. I have it enabled for LibreOffice Calc, Gimp and ImageMagick.
Problem with OpenCL enabled apps is not the feature itself. It's the lack of proper documentation. In fact, PV had disabled OpenCL support in Slackware's ImageMagick altogether as it was crashing peoples boxes around. It turned out that ImageMagick's OpenCL documentation was way outdated. I got the job of understanding the actual state of the things to update the documentation accordingly. After that, OpenCL support for ImageMagick in Slackware was enabled again. People who uses it get what they want, people who don´t are not annoyed by random crashes.
Anyway, I have both intel and amd boxes here. No nvidia for years and it was PITA. My amd box is a breeze to keep up and running and gpu performance is just where I need it to be. I don't game on computers, but I crunch some serious bits on more general computing tasks (no mining tho).
Kudos to amd devs providing OSS patches, to the community developing the amdgpu driver and to @kingbeowulf for providing a way to include the proprietary part. I'm looking forward and excited for proper OpenCL support landing on Mesa.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,109
Original Poster
Rep:
Quote:
Some Older AMD GPUs + Intel Alder Lake Is Causing ASPM Problems For Linux Users
Michael Larabel in Radeon on 9 April 2022
Older AMD GPUs paired with Intel Alder Lake Platforms is leading to hangs during suspend/resume cycles so a patch is pending for the Linux kernel to disable Active State Power Management (ASPM) in such combinations........
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.