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.
i'm Firefox and Kernel actual at Slackware, but and is not what's all.
And what you think to do, what do i think about at all ? Right ! ...
bassmadrigal write from Windows ? Yes ! Is thread for Slackware.
Let work now !
i now have actual 3 system's: GhostBSD (FreeBSD 13.0-STABLE); UbuntuStudio 21.04 beta (5.11.13), Slackware 15.0 (5.11.11)
At all system's i have now actual situation Firefox and other.
And jeremy fox erase my post string about AMD RADEON 6770 1Gb GDDR5
Let work !
p.s. I'm really talk direct with madam D-r Lisa Su. She is scientist. I'm Happy !
bassmadrigal write from Windows ? Yes ! Is thread for Slackware.
GASP! You found me out. Yes, sometimes I post from a Windows machine. However, I don't discuss Windows, I talk about Slackware. What computer I use to make my posts is irrelevant. Who cares?
Quote:
Originally Posted by Roman Dyaba
i now have actual 3 system's: GhostBSD (FreeBSD 13.0-STABLE); UbuntuStudio 21.04 beta (5.11.13), Slackware 15.0 (5.11.11)
Congratulations. However, discussion in this thread is about Slackware and AMD drivers.
Quote:
Originally Posted by Roman Dyaba
p.s. I'm really talk direct with madam D-r Lisa Su. She is scientist. I'm Happy !
Well, then if she's telling you that AMD does not provide Linux drivers and only Windows drivers, she's very wrong and uninformed. It is unlikely the CEO of AMD is telling you that AMD doesn't provide Linux drivers. CEOs don't tend to share wrong information like that. They'll either choose to not say something about it if they're not sure or have accurate information.
Yes, this is the link I posted earlier showing the AMD is still providing Linux drivers directly and not just through the drivers included with the kernel. I'm not sure why you decided to post it again.
Are we done repeating info and discussing things that don't apply to the topic of this thread?
All graphics drivers come in two parts, in kernel driver provides access to the device and X11 driver does the actual work. Telling AMD drivers are in kernel is incorrect, only DRI is in kernel, the main driver is loaded with X and is not part of kernel.
All graphics drivers come in two parts, in kernel driver provides access to the device and X11 driver does the actual work. Telling AMD drivers are in kernel is incorrect, only DRI is in kernel, the main driver is loaded with X and is not part of kernel.
Yeah, I probably should've used "open source drivers" rather than kernel driver, since even the AMD proprietary drivers still compile a kernel module. It just seemed a lot was getting lost in the language difference and I didn't want to go too in depth.
Yeah, I probably should've used "open source drivers" rather than kernel driver, since even the AMD proprietary drivers still compile a kernel module. It just seemed a lot was getting lost in the language difference and I didn't want to go too in depth.
Yes, but even closed source driver has kernel module and Xorg driver, nVidia does the same. One handles the hardware access (kernel module) and the other one does the rendering (Xorg driver).
I see not everyone has thought how it works, here is short description. It is all in Xorg log.
Step 1.
Code:
[ 37.890] (II) xfree86: Adding drm device (/dev/dri/card0)
This is kernel driver in action. It prepares the card for use, loads firmware as needed and creates this device node. Open source and closed source kernel module do the same, no difference here. As a bonus you may get a nice high res framebuffer, but not necessarily.
Step 2. User starts Xorg.
a) In case there is proper hardware-specific driver available it will be loaded. This driver knows all about the features your card has and makes use of them, using the node kernel created to access the card. This driver actually draws the picture and uses all hardware acceleration available.
Code:
[ 37.913] (II) LoadModule: "intel"
[ 37.913] (II) Loading /usr/lib64/xorg/modules/drivers/intel_drv.so
[ 37.916] (II) Module intel: vendor="X.Org Foundation"
[ 37.916] compiled for 1.20.10, module version = 2.99.917
[ 37.916] Module class: X.Org Video Driver
[ 37.916] ABI class: X.Org Video Driver, version 24.1
[ 37.916] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets:
i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G,
915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM,
Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33,
GM45, 4 Series, G45/G43, Q45/Q43, G41, B43
...
b) In case there is no vendor specific driver found Xorg tries built-in fallback drivers, modesetting, fbdev, vgahw. You can see Xorg trying these in Xorg log when no suitable driver is found. I have currently no logs to paste here with this.
As you can see kernel driver is more like a gatekeeper, while all traffic thru that gate comes from Xorg driver.
Emerson is only partially correct. AMDGPU is the AMD GPU hardware driver: this is the hardware interface that sets software interface, DRM/DRI and firmware. A better description is here: https://en.wikipedia.org/wiki/Free_a..._device_driver
amdpgu does more that just "create a node" and has more functionality that just as a gatekeeper. It does all the low level hardware communication. The X.org module is a library of functions allow X/Mesa to send and query data on the hardware. It really does not need to now exactly what GPU chipset is there. Hence, amdgpu.ko is the driver and amdgpu_drv.so is a library.
We can argue over the software details, but suffice to say AMD and amdgpu FTW on Slackware!
This is exactly what I meant. It handles the hardware, as I said in post #22. Lets not split hairs here, my wording wasn't perhaps very scientific, but it wasn't meant to be.
Yes, but even closed source driver has kernel module and Xorg driver, nVidia does the same. One handles the hardware access (kernel module) and the other one does the rendering (Xorg driver).
I didn't say otherwise... The conversation didn't seem to require that level of detail for the driver and I wasn't wanting to make things more confusing when so much was already being lost due to the language barrier.
I can't speak for Nvidia (as I have no experience with them), but AMD's amdgpu-pro provides a separate open source kernel driver that needs to be compiled during driver installation and a pre-compiled Xorg driver that is tied to a specific X version (and many other packages and software -- I don't remember all that was included as it's been years since I maintained my SlackBuild to repackage their "pro" driver). Due to the Xorg driver being pre-compiled, it eventually led to newer "pro" drivers not working on 14.2 as that Xorg driver was compiled against a newer version of X than was provided by 14.2 and it prevented loading that driver.
nVidia and Intel have both options and settings one can set in xorg.conf. For instance, if I want to use Intel SNA hardware acceleration I pass this option to Xorg driver, not kernel driver. Same is with nVidia, a bunch of options can be specified for Xorg driver, but the kernel modules are loaded without customizing. I do not have any modern AMD video hardware, therefore can't tell if you configure the Xorg part or kernel part of driver with AMD.
AMD hardware can use both kernel parameters and xorg.conf options for various settings, although, most users won't need to adjust the kernel module parameters.
AMD hardware can use both kernel parameters and xorg.conf options for various settings, although, most users won't need to adjust the kernel module parameters.
I am among these. I use 4 monitors, and the default KDE settings for the displays is sufficient for what I need done with the AMD driver. Simple to use, couldn't be easier!
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,095
Original Poster
Rep:
"...A rare update...."
Quote:
xf86-video-amdgpu 21.0.0 Released For Radeon Linux Users Still On X.Org
Written by Michael Larabel in Radeon on 30 July 2021 at 01:45 PM EDT.
RADEON --
For those making use of Radeon graphics on Linux with an X.Org-based environment and not using the generic xf86-video-modesetting DDX but rather than the xf86-video-amdgpu driver, AMD today put out a rare update to that diminishing driver component.,,,,,,,,
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
