View Single Post
Old 04-05-2020, 06:35 PM   #13
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 28,716
Karma: 205159604
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
It is my understanding that it's an either/or thing with the proprietary nvidia drivers and mesa. On some systems, the openGL portions of each may actually conflict.

See what the output of the following command is:

Code:
LIBGL_DEBUG=verbose glxinfo | grep -iE "opengl|^direct|^libgl"
That assumes the glxinfo binary is installed. Depending on the distro, it might be provided by the mesa package (or maybe mesa-utils). On my Arch system, it's provided by mesa-demos.

Last edited by DiapDealer; 04-05-2020 at 06:51 PM.
DiapDealer is offline   Reply With Quote