[elrepo] NVIDIA and RHEL 6.5 issue (libglamoregl)

[Phil Perry]

On 03/12/13 00:24, Akemi Yagi wrote:
> On Sat, Nov 30, 2013 at 5:30 AM, Phil Perry <phil at elrepo.org> wrote:
>> Hi all,
>>
>> I just wanted to bring to the attention of NVIDIA users one potential issue
>> with the release of RHEL6.5 and NVIDIA proprietary drivers.
>>
>> Taken from the NVIDIA changelog for the 304.xx release:
>>
>>      * Updated nvidia-installer to consider the "libglamoregl.so" X loadable
>>        extension module to be in conflict with the NVIDIA OpenGL driver. This
>>        module can cause the NVIDIA libGL to be loaded into the same process
>>        (the X server) as the NVIDIA libglx.so extension module, which is not
>>        a supported use case.
>
> In http://www.phoronix.com/scan.php?page=news_item&px=MTUwNjA , I
> found this description:
>
> "The NVIDIA 331.20 binary driver also updates the NVIDIA driver
> installer to now detect the EGL GLAMOR library (libglamoregl.so) X
> extension module as it conflicts with the NVIDIA binary driver. GLAMOR
> is just used by the AMD RadeonSI driver and other select use-cases for
> doing 2D acceleration over OpenGL, but conflicts with NVIDIA's libGL
> and libglx.so modules."
>
> What is not clear to me is that the new installer 'considers' (1st
> quote) or 'detects' (2nd quote) libglamoregl.so ... and ... does what?
> Is it saying that therefore libglamoregl.so should not pose a problem
> with this new installer ??
>
> Can someone explain this in plain English?
>

I interpreted this to mean the newer (starting with 304.xx) NVIDIA 
driver installer (which we don't use) will detect the presence of glamor 
and disable it. Knowing how NVIDIA have dealt with such conflicts in the 
past (e.g, LibGL) I suspect they move the offending libs to backup files 
and restore them on uninstallation of the proprietary NVIDIA drivers. Of 
course this approach falls over on RPM based distros as each time the 
package supplying these libs gets updated any changes the NVIDIA driver 
installer has made gets overwritten. This is just my best guess without 
having actually run the NVIDIA installer lately to see what it does.