mesa DRI drivers path

414N · 12-10-2020, 04:59 PM

Greetings,

while discussing a Steam-runtime issue on GitHub, it came to light that Slackware uses what is, for today distros "standard", an unconventional path for DRI drivers, e.g "/usr/lib${LIBDIRSUFFIX}/xorg/modules/dri".

This setting is enforced in past and current mesa.SlackBuild scripts with an explicit option ("-Ddri-drivers-path=/usr/lib${LIBDIRSUFFIX}/xorg/modules/dri") but is there a reason for putting DRI drivers there instead of "/usr/lib${LIBDIRSUFFIX}/dri", where VA-API drivers are already put by the same mesa package?

business_kid · 12-11-2020, 05:43 AM

Having suffered over drivers in the past with my sucky video, there are actually two directories for video drivers, one for 2D and one for 3D. I suppose it makes sense, as they could name them identically.

414N · 12-11-2020, 02:53 PM

Hello business_kid, thanks for chiming in.

So, if I'm not mistaken, you're saying that there could be an "aliasing" issue (between different driver packages I assume, i.e. mesa against some other driver package) that could hinder driver usage.

business_kid · 12-12-2020, 12:01 PM

I'm no software genius, I'm a hardware guy. My drivers come split between 2D & 3D (I can't speak for anyone else's), so I guess the 2D is used if 3D is not active