Bug 62571

Summary: Mesa 9.0 uses missing nouveau library
Product: Mesa Reporter: Jesus Cortez <jesus.cortezjr>
Component: Mesa coreAssignee: mesa-dev
Status: RESOLVED INVALID QA Contact:
Severity: major    
Priority: medium    
Version: 9.0   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:

Description Jesus Cortez 2013-03-20 18:53:09 UTC
We are using Scientific Linux 6.3, and noticed that our 3D applications started breaking after the auto-update to Mesa 9.0.

After the upgrade, glxinfo (with LIBGL_DEBUG=verbose) would return:

libGL: OpenDriver: trying /usr/lib/dri/nouveau_dri.so
libGL error: dlopen /usr/lib/dri/nouveau_dri.so failed (/usr/lib/dri/nouveau_dri.so: cannot open shared object file: No such file or directory)
libGL error: unable to load driver: nouveau_dri.so
libGL error: driver pointer missing
libGL error: failed to load driver: nouveau
libGL: OpenDriver: trying /usr/lib/dri/swrast_dri.so
GLVersion major: 1 minor: 4 

This error was also being returned in our application, resulting in crashes that did not occur the previous day.

We were able to fix the issue by running the following commands:

rpm -e --nodeps mesa-dri1-drivers
yum -y downgrade mesa-libGL-devel mesa-libGL mesa-dri-drivers

to downgrade Mesa back to 7.11.
Comment 1 Armin K 2013-03-20 19:26:03 UTC
nouveau_dri.so exists on my system in the very same directory. It's Gallium driver. Add "nouveau" to the --with-gallium-drivers list at build time.
Comment 2 Maarten Lankhorst 2013-03-20 20:23:16 UTC
First of all, this is a bug with scientific linux' packaging probably.

Second, are you sure that it doesn't exist?

ldd /usr/lib/dri/nouveau_dri.so
Comment 3 Jesus Cortez 2013-03-20 20:29:49 UTC
(In reply to comment #2)
> First of all, this is a bug with scientific linux' packaging probably.
> 
> Second, are you sure that it doesn't exist?
> 
> ldd /usr/lib/dri/nouveau_dri.so

Yes, the nouveau_dri.so is completely missing from the machine.

Just to verify that it was the upgrade, I ran 

yum -y upgrade mesa-libGL-devel mesa-libGL mesa-dri-drivers

and the glxinfo, and sure enough, the problem came back.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.