| View previous topic :: View next topic |
| Author |
Message |
RayDude
Advocate
Joined: 29 May 2004
Posts: 2066
Location: San Jose, CA
|
 Posted: Sat Mar 21, 2020 8:18 am Post subject: eselect-opengl conflicts with xorg and nvidia-driver? |
 |
|
why?
| Code: | emerge eselect-opengl
Calculating dependencies... done!
[ebuild N ] app-eselect/eselect-opengl-1.3.1-r4
[uninstall ] x11-base/xorg-server-1.20.7
[blocks B ] app-eselect/eselect-opengl ("app-eselect/eselect-opengl" is blocking x11-drivers/nvidia-drivers-440.64, x11-base/xorg-server-1.20.7, media-libs/mesa-19.3.5)
* Error: The above package list contains packages which cannot be
* installed at the same time on the same system.
(app-eselect/eselect-opengl-1.3.1-r4:0/0::gentoo, ebuild scheduled for merge) pulled in by
eselect-opengl
(x11-drivers/nvidia-drivers-440.64:0/440::gentoo, installed) pulled in by
x11-drivers/nvidia-drivers required by @selected
(media-libs/mesa-19.3.5:0/0::gentoo, installed) pulled in by
media-libs/mesa required by @selected |
_________________
Some day there will only be free software. |
|
| Back to top |
|
 |
fedeliallalinea
Administrator
Joined: 08 Mar 2003
Posts: 30954
Location: here
|
|
| Back to top |
|
|
Ionen
Developer
Joined: 06 Dec 2018
Posts: 2727
|
| Posted: Sat Mar 21, 2020 1:02 pm Post subject: |
|
|
You should not be trying to "emerge eselect-opengl" directly (or have in world file), this package is made obsolete by libglvnd. You can safely ignore any wiki instructions telling you to use "eselect opengl".
Sounds like you don't actually have issues, but if anyone has any, more particularly see the this post in the above mentioned thread. I've updated it a bit to be clearer and cover other issues. |
|
| Back to top |
|
|
RayDude
Advocate
Joined: 29 May 2004
Posts: 2066
Location: San Jose, CA
|
| Posted: Sat Mar 21, 2020 4:31 pm Post subject: |
|
|
Okay. Just to confirm.
eselect-opengl has gone the way of the dinosaur and has been replaced by libglvnd, which I'm assuming negotiates with all the GL providers automagically.
So I don't need to install it and I don't need to run it any more.
If that's right, thanks for the explanation. I appreciate it.
_________________
Some day there will only be free software. |
|
| Back to top |
|
|
Ionen
Developer
Joined: 06 Dec 2018
Posts: 2727
|
| Posted: Sat Mar 21, 2020 4:36 pm Post subject: |
|
|
Yep, that is right. If you were using multiple GL providers, shouldn't be any need to use weird switching scripts anymore (Edit: if needed, an environment variable is usable to force a provider for a particular screen).
Only ones that still need it is those on very old nvidia-drivers, which isn't your case given using latest drivers  |
|
| Back to top |
|
|
Carlos227
n00b
Joined: 31 Jul 2020
Posts: 25
|
| Posted: Fri Aug 14, 2020 2:30 am Post subject: |
|
|
I just got this in the last update, is it safe to update with nvidia version 390.138-r1 now?
| Code: | [ebuild U ~] dev-libs/nspr-4.27 [4.26]
[ebuild N ] media-libs/libglvnd-1.3.2 USE="X -test"
[ebuild R ] media-libs/mesa-20.0.8 USE="(libglvnd*)"
[blocks b ] media-libs/mesa[-libglvnd(-)] ("media-libs/mesa[-libglvnd(-)]" is blocking media-libs/libglvnd-1.3.2)
[ebuild R ] x11-drivers/nvidia-drivers-390.138-r1 USE="(libglvnd*)"
[ebuild R ] x11-base/xorg-server-1.20.8-r1 USE="(libglvnd*)"
[uninstall ] app-eselect/eselect-opengl-1.3.1-r4
[blocks b ] app-eselect/eselect-opengl ("app-eselect/eselect-opengl" is blocking x11-base/xorg-server-1.20.8-r1, media-libs/mesa-20.0.8, x11-drivers/nvidia-drivers-390.138-r1) |
|
|
| Back to top |
|
|
Ionen
Developer
Joined: 06 Dec 2018
Posts: 2727
|
| Posted: Fri Aug 14, 2020 3:13 am Post subject: |
|
|
| Carlos227 wrote: | | I just got this in the last update, is it safe to update with nvidia version 390.138-r1 now? |
Yes, it's a bit of a hack but glx should work with libglvnd and 390 now.
Support for eselect-opengl will be removed entirely in about a month, thus the forced use for the libglvnd flag. |
|
| Back to top |
|
|
Carlos227
n00b
Joined: 31 Jul 2020
Posts: 25
|
| Posted: Fri Aug 14, 2020 6:01 pm Post subject: |
|
|
| Ionen wrote: | | Carlos227 wrote: | | I just got this in the last update, is it safe to update with nvidia version 390.138-r1 now? |
Yes, it's a bit of a hack but glx should work with libglvnd and 390 now.
Support for eselect-opengl will be removed entirely in about a month, thus the forced use for the libglvnd flag. |
After updating the nvidia driver does not work even though it is installed, normally I would use eselect-opengl, but it is no longer there.
How do I select the nvidia driver?
| Code: | Vendedor: VMware, Inc.
Tarjeta Grafica: llvmpipe (LLVM 10.0.0, 128 bits)
Version OpenGl: 3.1 Mesa 20.0.8
Version GLSL: 1.40 |
Why do I need mesa if I already have x11-drivers/nvidia-drivers installed? |
|
| Back to top |
|
|
Ionen
Developer
Joined: 06 Dec 2018
Posts: 2727
|
| Posted: Fri Aug 14, 2020 9:30 pm Post subject: |
|
|
| Carlos227 wrote: | | Why do I need mesa if I already have x11-drivers/nvidia-drivers installed? |
Formerly it was needed for GL headers given nvidia-drivers don't provide them, but now libglvnd provides headers so technically you "hardly" need it (still needed for 1 header file currently, mesa libraries certainly don't get used), but gentoo dependencies aren't designed to allow not needing mesa nor do header-only install of it at the moment either way.
Edit:
I was convinced it had gotten fixed by now, especially with the flag getting forced _and_ drivers being stabilized, but seems bug #713546 is still seeing activity despite formerly holding back stabilization  Sorry for misinforming. That aside, it's possible to work around it with a xorg.conf.d file, see the bug for details. Either way non-glvnd will break entirely soon so have to do something about this.
I still don't know why eselect-opengl removal need to be rushed like this still with open bugs, but oh well.
Last edited by Ionen on Fri Aug 14, 2020 9:51 pm; edited 2 times in total |
|
| Back to top |
|
|
Carlos227
n00b
Joined: 31 Jul 2020
Posts: 25
|
| Posted: Fri Aug 14, 2020 9:46 pm Post subject: |
|
|
| Ionen wrote: | | Carlos227 wrote: | | Why do I need mesa if I already have x11-drivers/nvidia-drivers installed? |
Formerly it was needed for GL headers given nvidia-drivers don't provide them, but now libglvnd provides headers so technically you "hardly" need it (still needed for 1 header file currently, mesa libraries certainly don't get used), but gentoo dependencies aren't designed to allow not needing mesa nor do header-only install of it at the moment either way.
That aside it "should" be auto-detecting the right vendor to use here, assuming xorg itself is using nvidia drivers (are you selecting the driver yourself in xorg.conf(.d) or leaving it up to auto-detection?). Not that I've tried 390 myself (I use nouveau on my older box, and 450.57 on my newer), I only know that the related bug is supposed to be fixed. |
If I have my xorg file, but it doesn't work right
| Code: | Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce GT 610"
EndSection |
The gpu is hardly used and the cpu is used more than ever.
NVIDIA X Server Setting Data
Used Dedicated Memory: 101 MB (5%)
GPU Utilization 8%
Video Engine Utilization: 0%
And now a process appeared that I had not seen before "GPU" (when using firefox) uses CPU at 80% or more and the whole interface is very slow |
|
| Back to top |
|
|
Ionen
Developer
Joined: 06 Dec 2018
Posts: 2727
|
| Posted: Fri Aug 14, 2020 9:48 pm Post subject: |
|
|
| I realized what was up and edited my post right before you posted, may want to re-read it. |
|
| Back to top |
|
|
Carlos227
n00b
Joined: 31 Jul 2020
Posts: 25
|
| Posted: Fri Aug 14, 2020 10:15 pm Post subject: |
|
|
| Ionen wrote: | | Carlos227 wrote: | | Why do I need mesa if I already have x11-drivers/nvidia-drivers installed? |
Formerly it was needed for GL headers given nvidia-drivers don't provide them, but now libglvnd provides headers so technically you "hardly" need it (still needed for 1 header file currently, mesa libraries certainly don't get used), but gentoo dependencies aren't designed to allow not needing mesa nor do header-only install of it at the moment either way.
Edit:
I was convinced it had gotten fixed by now, especially with the flag getting forced _and_ drivers being stabilized, but seems bug #713546 is still seeing activity despite formerly holding back stabilization Sorry for misinforming. That aside, it's possible to work around it with a xorg.conf.d file, see the bug for details. Either way non-glvnd will break entirely soon so have to do something about this.
I still don't know why eselect-opengl removal need to be rushed like this still with open bugs, but oh well. |
Thanks, that fixed the error for me.
/etc/X11/xorg.conf.d/nvidia.conf
| Code: | Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce GT 610"
EndSection
Section "OutputClass"
Identifier "nvidia"
MatchDriver "nvidia-drm"
Driver "nvidia"
Option "AllowEmptyInitialConfiguration"
ModulePath "/usr/lib64/extensions/nvidia/"
EndSection |
|
|
| Back to top |
|
|
dmpogo
Advocate
Joined: 02 Sep 2004
Posts: 3267
Location: Canada
|
| Posted: Sat Aug 15, 2020 2:58 pm Post subject: |
|
|
| Carlos227 wrote: | | Ionen wrote: | | Carlos227 wrote: | | Why do I need mesa if I already have x11-drivers/nvidia-drivers installed? |
Formerly it was needed for GL headers given nvidia-drivers don't provide them, but now libglvnd provides headers so technically you "hardly" need it (still needed for 1 header file currently, mesa libraries certainly don't get used), but gentoo dependencies aren't designed to allow not needing mesa nor do header-only install of it at the moment either way.
Edit:
I was convinced it had gotten fixed by now, especially with the flag getting forced _and_ drivers being stabilized, but seems bug #713546 is still seeing activity despite formerly holding back stabilization Sorry for misinforming. That aside, it's possible to work around it with a xorg.conf.d file, see the bug for details. Either way non-glvnd will break entirely soon so have to do something about this.
I still don't know why eselect-opengl removal need to be rushed like this still with open bugs, but oh well. |
Thanks, that fixed the error for me.
/etc/X11/xorg.conf.d/nvidia.conf
| Code: | Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce GT 610"
EndSection
Section "OutputClass"
Identifier "nvidia"
MatchDriver "nvidia-drm"
Driver "nvidia"
Option "AllowEmptyInitialConfiguration"
ModulePath "/usr/lib64/extensions/nvidia/"
EndSection |
|
Hm, I wonder whether this works with nvidia-drivers-340 series as well |
|
| Back to top |
|
|
Ionen
Developer
Joined: 06 Dec 2018
Posts: 2727
|
| Posted: Sat Aug 15, 2020 3:16 pm Post subject: |
|
|
| dmpogo wrote: | | Hm, I wonder whether this works with nvidia-drivers-340 series as well |
You'd still have the problems of libraries not being found without eselect-opengl, 390 does support libglvnd unlike 340 and its issues is just about xorg's glx module (and giving the path is more of a workaround than a proper solution, but should be irrelevant for most). |
|
| Back to top |
|
|
dmpogo
Advocate
Joined: 02 Sep 2004
Posts: 3267
Location: Canada
|
| Posted: Sat Aug 15, 2020 4:17 pm Post subject: |
|
|
| Ionen wrote: | | dmpogo wrote: | | Hm, I wonder whether this works with nvidia-drivers-340 series as well |
You'd still have the problems of libraries not being found without eselect-opengl, 390 does support libglvnd unlike 340 and its issues is just about xorg's glx module (and giving the path is more of a workaround than a proper solution, but should be irrelevant for most). |
OK, got it about the libraries |
|
| Back to top |
|
|
fargred
n00b
Joined: 19 Oct 2010
Posts: 67
|
| Posted: Tue Apr 18, 2023 5:36 pm Post subject: |
|
|
| Carlos227 wrote: |
| Code: |
Section "OutputClass"
Identifier "nvidia"
MatchDriver "nvidia-drm"
Driver "nvidia"
Option "AllowEmptyInitialConfiguration"
ModulePath "/usr/lib64/extensions/nvidia/"
EndSection |
|
May your next year be happy, dude, this section saved me a world update. After restarting X I got “EE Failed to initialize the GLX module” error (that goes after “Enabling 2D acceleration” line). Reinstalling nvidia-drivers and libglvnd from binary package (the error message hinted at broken files) didn’t help. The wiki says this error is related to MTRR, but in my case it was something related to how libglvnd handles paths (or X searching them).
P.S. No idea what was the source of error, the last time I changed something in the configuration was months ago and since then it just worked. Without a reboot, but with some X restarts. The last thing merged, as I now remember after searching the logs, was libstrangle, which force-pulled vulkan-headers (machine doesn’t support vulkan).
P.P.S. How I miss eselect-opengl… |
|
| Back to top |
|
|
|
Installing Gentoo
