Bug 608138

Summary:	Missing 3D acceleration for Matrox graphics cards
Product:	[openSUSE] openSUSE 11.3	Reporter:	Klaus Peichl <pei>
Component:	X.Org	Assignee:	Forgotten User Wum0mkMcd8 <forgotten_Wum0mkMcd8>
Status:	RESOLVED DUPLICATE	QA Contact:	E-mail List <xorg-maintainer-bugs>
Severity:	Normal
Priority:	P5 - None	CC:	AmigaPhil
Version:	Milestone 6
Target Milestone:	---
Hardware:	PC
OS:	openSUSE 11.3
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Klaus Peichl 2010-05-23 09:56:59 UTC

Although enabled in sax2, the 3D hardware acceleration of a Matrox G550 card does not work (e.g. in Google Earth or glxgears).

/var/log/Xorg.0.log reports:

(EE) AIGLX error: dlopen of /usr/lib/dri/mga_dri.so failed (/usr/lib/dri/mga_dri.so: cannot open shared object file: No such file or directory)

Apparently the Mesa package is simply missing the file "mga_dri.so".
A work-around is to extract this file from the Mesa package of another
Linux distribution (e.g. mesa-dri-drivers-7.8.1-6.fc13.i686.rpm) and copying
it to /usr/lib/dri/mga_dri.so.
I (and many others) had this problem already with openSuSE 11.1.

Comment 1 Stefan Dirsch 2010-05-23 11:30:26 UTC

mga DRI driver has been disabled by intention.

*** This bug has been marked as a duplicate of bug 403071 ***

Comment 2 Klaus Peichl 2010-05-23 12:50:15 UTC

> mga DRI driver has been disabled by intention.

Actually, DRI was *enabled* by default, but since the driver was missing,
it did not work and the Xorg server reported an error. Imho providing options that just don't work creates a very bad user experience.
Using the driver from Fedora has worked for my many months and I did not encounter any graphics related crashes.

Comment 3 Stefan Dirsch 2010-05-23 15:08:38 UTC

You mean, you can't run any OpenGL application using the software renderer, i.e. you need to set the env. variable LIBGL_ALWAYS_INDIRECT manually?

Comment 4 Klaus Peichl 2010-05-24 21:42:05 UTC

No, I was referring to the 3D hardware acceleration that does not work because
mga_dri.so could not be loaded. The software renderer worked without setting
any variables, but for most 3D applications this is not really an option.

Comment 5 Stefan Dirsch 2010-05-25 00:16:46 UTC

Ok. Thanks for confirmation.

Comment 6 Philippe Duchenne 2010-07-28 20:16:38 UTC

(In reply to comment #4)
> No, I was referring to the 3D hardware acceleration that does not work because
> mga_dri.so could not be loaded. The software renderer worked without setting
> any variables, but for most 3D applications this is not really an option.

In the meantime...

mga_dri.so is back in Mesa. :-)
See bnc #466635
https://bugzilla.novell.com/show_bug.cgi?id=466635