Bug 19572

Summary: mcc graphical menu not working with nVidia proprietary driver
Product: Mageia Reporter: aguador <waterbearer54>
Component: RPM PackagesAssignee: Mageia tools maintainers <mageiatools>
Status: RESOLVED WORKSFORME QA Contact:
Severity: normal    
Priority: Normal CC: doc-bugs, marja11, rverschelde
Version: Cauldron   
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: CVE:
Status comment:
Attachments: Output of glxinfo

Description aguador 2016-10-12 15:03:05 CEST
Created attachment 8524 [details]
Output of glxinfo

Mageia 6 Cauldron E20 installation on an Asus A53S laptop with Optimus (nVidia GeForece 610M card) technology and proprietary (GeForce 420 series and later) driver.

In order to properly activate the proprietary driver, xorg.conf was deleted after installation of the driver (comment 9 Bug 13986 which addresses PRIME; Bug 19570) to allow bumblebee to switch the driver. When trying to open Mageia Control Center, the menu of options is unavailable. MCC displayed properly with the Intel integrated graphics.

Terminal output from calling MCC shows the follow 5 lines after the Gtk3 warnings:

Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".

which accords with the glxinfo attached.

I have confirmed that nvidia-current is present, and other graphical components function (e.g., drakrpm, harddrake2, drakx11).
aguador 2016-10-12 15:03:41 CEST

Summary: mcc graphics not working with nVidia proprietary driver => mcc graphical menu not working with nVidia proprietary driver

Marja Van Waes 2016-10-13 11:52:23 CEST

CC: (none) => marja11
Assignee: bugsquad => mageiatools

Comment 1 aguador 2016-11-14 23:21:45 CET
Perhaps this bug can be closed, but some clarity is needed for installing/configuring Mageia for Optimus systems. With no xorg.conf file the nVidia driver seemed to be functioning and a non-functional left edge binding worked. However, the above description indicates that something was not operating properly. . . and I recently discovered the Evolution refused to start because of the missing GLX extension. In addition, the last update of the EFL libraries resulted in an error message indicating that my graphics card did not support OpenGL.

After running Drakx11 again to create an xorg.conf file with the Intel card as display 1 and nVidia as display 2, everything is now functioning (mcc and Evolution AND the left edge binding). The curious thing is that in selecting automatic for the second display driver, the xorg.conf file generated indicates that "nouveau" is the driver, when indeed it is the proprietary driver I have installed. Bumblee is installed, but I have no idea if it is working with this configuration.

See this forum thread for a longer version of this tale: https://forums.mageia.org/en/viewtopic.php?f=15&t=11386&p=66375&hilit=nvidia#p66375

If I can help with documentation of this issue, let me know. However, I think I am missing something in understanding what is going on!
Comment 2 aguador 2016-11-15 00:35:10 CET
With above cited xorg.conf file in place:

$ optirun glxinfo | grep OpenGL
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce 610M/PCIe/SSE2
OpenGL core profile version string: 4.5.0 NVIDIA 367.57
OpenGL core profile shading language version string: 4.50 NVIDIA
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 4.5.0 NVIDIA 367.57
OpenGL shading language version string: 4.50 NVIDIA
OpenGL context flags: (none)
OpenGL profile mask: (none)
OpenGL extensions:
Comment 3 Marja Van Waes 2016-11-15 13:01:22 CET
(In reply to Roy Reese from comment #1)


> If I can help with documentation of this issue, let me know. However, I
> think I am missing something in understanding what is going on!

CC'ing documentation team

CC: (none) => doc-bugs

Comment 4 Marja Van Waes 2016-11-15 13:08:44 CET
(In reply to Marja van Waes from comment #3)
> (In reply to Roy Reese from comment #1)
> 
> 
> > If I can help with documentation of this issue, let me know. However, I
> > think I am missing something in understanding what is going on!
> 
> CC'ing documentation team

And also CC'ing Akien, who has much better understanding of the issue than me.

If this report should be closed as duplicate, then it can be changed into a "improve our documentation about Optimus and the like" request

CC: (none) => rverschelde

Comment 5 aguador 2019-02-24 11:32:53 CET
As I recall this has been addressed in the documentation and/or is no longer a problem. Due to lack of support for my nVidia card and improvements in nouveau, I have dropped the nVidia proprietary driver. I am simply closing as resolved.

Resolution: (none) => WORKSFORME
Status: NEW => RESOLVED