[elrepo-devel] We have fglrx packages and X does not behave. How to proceed ?

[Manuel Wolfshant]

Hello

     As some of you already know, for sometime I am the maintainer of 
the fglrx (AMD video drivers ) packages.
     Things look fine on EL6 ( at least I have not heard about any 
complains ) but on EL7 there is a problem which seems to occur more or 
less randomly. I for one was not able to identify the pattern triggering 
it ( and to make things worse, I still do not have an actual EL7 system 
to test with my own set of hands and eyes ).  To cut a long story short, 
despite the presence of a file named /etc/X11/xorg.conf.d/20-fglrx.conf 
which contains
     Section "Files"
         ModulePath   "/usr/lib64/xorg/modules/extensions/fglrx"
         ModulePath   "/usr/lib64/xorg/modules"
     EndSection
Xorg randomly decides to load 
/usr/lib64/xorg/modules/extensions/libglx.so rather than 
/usr/lib64/xorg/modules/extensions/fglrx/libglx.so . This leads to:
[    38.173] (II) "glx" will be loaded by default.
[    38.173] (II) LoadModule: "glx"
[    38.174] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so
which later on leads to a SIG11 given that the fglrx.so hates stock 
libglx.so

     Now, the obvious solution would be the one originally implemented 
by AMD (and disabled in elrepo packages ): renaming the stock libglx.so 
to something else when the package is installed and restoring it at 
removal time. However this leads the system prone to issues if/when 
xorg-x11-server-Xorg is updated given that the file will get recreated.

     Therefore I come to you with this question: beside trying to file a 
bug against RHEL/xorg  and asking for their help in identifying the 
reason why the behaviour of X is erratic, what can I ( emphasize on I ) 
can do to make the users of the fglrx packages on EL7 happier  ? I've 
never used it before in my 9 years of packaging but I wonder if 
something along

             %triggerin  -- xorg-x11-server-Xorg
                     mv /usr/lib64/xorg/modules/extensions/libglx.so 
/usr/lib64/xorg/modules/extensions/libglx.so.elrepo

(and the corresponding %triggerun to restore the file ) would be fine 
for this case.

     Thoughts, anyone ?


         wolfy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.elrepo.org/pipermail/elrepo-devel/attachments/20151223/f62fd559/attachment.html>