nvidia-drivers-390.x and libglvnd

[NathanZachary]

Hello all,

I had to do some research to find out a little more about libglvnd and the whole point of switching away from eselect-opengl in favour of it. After these changes, though, my graphics rendering has been quite sluggish. I'm currently using the 390.x nvidia driver (for my ancient GTX 470). I see that direct rendering is enabled:

[Ionen]

libglvnd support was added to the 390 ebuild only recently (in ~arch), I honestly wouldn't be surprised if it simply doesn't work right now, but I don't use 390 to be able to confirm.

It certainly "should" be showing nvidia in those greps if libglvnd is working normally and nvidia-drivers are in-use by xorg+kernel without having to do anything special (at most may want to confirm in your Xorg.0.log it's still loading nvidia drivers).

[NathanZachary]

Looks like the driver is failing:

[dmpogo]

Honestly speaking, if you are to use nvidia-drivers, it is better to disable all DRM support in the kernel completely.

Saying that, your opengl is indeed not provided by nividia but by MESA, so it will be slow. Critical error is

[ 26.678] (EE) NVIDIA(0): Failed to initialize the GLX module; please check in your X
[ 26.678] (EE) NVIDIA(0): log file that the GLX module has been loaded in your X
[ 26.678] (EE) NVIDIA(0): server, and that the module is the NVIDIA GLX module. If
[ 26.678] (EE) NVIDIA(0): you continue to encounter problems, Please try
[ 26.678] (EE) NVIDIA(0): reinstalling the NVIDIA driver.
[

[Ionen]

Configuration looks fine (seems to be discarding the RegistryDword but that should be just a warning).

The glx module is likely trying to use GL libraries and failing. If it's failing with libglvnd but not with eselect-opengl (Edit: may want to try to revert with USE=-libglvnd globally, if still broken could try to revert to stable -r1 drivers too), then my personal bets would be that the libglvnd support for 390 is broken unless someone else can confirm it works (I wouldn't say that normally, but as I said, it was added very recently and I'm not sure if really been tested beyond "it builds fine").

[NathanZachary]

@Ionen, those are good points. I will do some further testing soon. For now, the only bug that I can see related to the 390.x nvidia drivers and libglvnd is this one:
https://bugs.gentoo.org/711942
_________________
“Truth, like infinity, is to be forever approached but never reached.” --Jean Ayres (1972)
---avatar cropped from =AimanStudio---

[Ionen]

Seen a similar report in #gentoo with 390.132-r2+libglvnd (glx failing to load, llvmpipe being used), can't confirm but does reinforce the possibility of it being a bug.

Edit: EGL apparently does work as expected, this looks xorg/glx-specific

[NathanZachary]

I did some further testing, but alas, still haven't been able to get GLX working with libglvnd and nvidia-drivers-390.x. At first, I thought it may be that the nvidia GLX driver wasn't being loaded at all, and found the following locations for it:

[NathanZachary]

Also, I found the components section of the nvidia-drivers README to be informative:
https://download.nvidia.com/XFree86/Linux-x86_64/390.132/README/installedcomponents.html
_________________
“Truth, like infinity, is to be forever approached but never reached.” --Jean Ayres (1972)
---avatar cropped from =AimanStudio---

[grooveman]

This looks like the same exact issue I've been struggling with...
https://forums.gentoo.org/viewtopic-t-1114466-highlight-llvmpipe.html

Perhaps this is a bug...
_________________
To look without without looking within is like looking without without looking at all.

[Ionen]

[grooveman]

Holy cow, Ionen!

You nailed it! I did as post #16 and #17 said to do in the bug, and it works! Thank you!!

I was losing all hope there

G
_________________
To look without without looking within is like looking without without looking at all.

[Ionen]

Well, glad to hear it works Honestly wasn't sure how it'd go on that setup.

[Maf]

The solution from https://forums.gentoo.org/viewtopic-p-8490710.html#8490710 fixed the problem for me as well (if only temporarily, we'll see...)

@OP: please mark topic as [SOLVED]

[mrbassie]

[quote="Ionen"]

[tld]

Wow...Just starting to read about all this. My MythTV frontend needs the 390 drivers and the last thing I want is to break that. I see that my upcoming update uninstalls eselect opengl and is adding libglvnd to nvidia-drivers and mesa. Am I to understand that, with the removal of that eselect that this is the only option?

So I take is that, at least for now, this setup should be OK with the addition of that new /etc/X11/xorg.conf.d/nvidia.conf file?

Tom

EDIT: I currently have this file under /etc/X11/xorg.conf.d. I certainly never added that, and it doesn't appear to belong to any packages:

[tld]

One thing I can see right off regarding the suggested fix is that it's intended for 64-bit and this is an older 32-bit front and. I think this is probably what I want in that nvidia.conf file:

[Ionen]

[Ionen]

Also, looks like bug #713546 has finally reached a resolution so self-added workaround for module path should no longer be needed with >=nvidia-drivers-390.138-r2.

Edit: It also force-selects the nvidia driver given auto-detection may not be doing so well, likely removes the need for any user-made configuration at all.

[tld]

Thanks for the replies! I think you're correct and I have no choice but to go with all the new libglvnd stuff. One good sign is that I can add the above nvidia.conf to /etc/X11/xorg.conf.d with my existing setup and it at least doesn't break anything. I suspect that you're correct in that the existing 20opengl.conf probably should be removed after I upgrade. Thanks!

Tom

[tld]

[Ionen]

Hmm, if I install 390 I don't have that path either (on 64bit), the fix looks wrong for everyone.

This is supposed to be "/usr/lib64/extensions/nvidia" and in your case it'd likely be "/usr/lib/extensions/nvidia" not that I have a 32bit system to check.

Edit: Made a note of it in the bug, hopefully it'll be re-opened and revised. This comment #8 from all the way back to March with a patch mostly had it right and used $(get_libdir) Wish it had gotten some attention before the "libglvnd supporting" version of 390 was dumped still-broken into stable and this whole rushed removal process then forced people to use it (there's no real going back to non-libglvnd, flag is profile forced and things about to be removed -- and I doubt something sensible like temporarily reverting this for at least few months is going to happen).

[tld]

[Ionen]

[Ionen]