G550 3D acceleration and kubuntu 7.04 (Feisty Fawn)

This forum is for questions about all G-series cards (G200, G400, G450, ...) that need the mga driver to work properly

G550 3D acceleration and kubuntu 7.04 (Feisty Fawn)

Postby fission » Mon Jul 30, 2007 11:25 pm

Hi,

I have this G550 card which apparently has some support for 3D acceleration, only I can't figure out what I need to do to make it work.

So far, I:
    extracted the latest Matrox drivers and copied mga_drv.so and mga_hal_drv.so into /usr/lib/xorg/modules/drivers;
    configured Xorg to load DRI

I'm at a bit of a loss. I see in the log:
Code: Select all
(EE) MGA(0): [drm] Could not boot-strap DMA (-12)
(WW) MGA(0): Direct rendering disabled
(EE) AIGLX: Screen 0 is not DRI capable
but haven't the foggiest idea what that all means.

The kernel module is loaded:
Code: Select all
% lsmod | grep mga
mga                    68352  0
drm                   103464  1 mga


I've attached my Xorg.0.log and xorg.conf.

UPDATE: When using your mga_drv.so (or the Xorg mga_drv.so), I get DRI enabled! Wow! But it freezes X hard as soon as anything OpenGL-ish runs... here's the Xorg.0.log from that, too.

Thanks for any insight,
Tyler
Attachments
Xorg.0.log
Xorg.0.log with mga_drv.so from this forum
(48.04 KiB) Downloaded 341 times
xorg.conf
(2.93 KiB) Downloaded 362 times
Xorg.0.log
Xorg.0.log with Matrox original mga_drv.so
(46.9 KiB) Downloaded 327 times
fission
Private
Private
 
Posts: 9
Joined: Mon Jul 30, 2007 11:15 pm
Location: Vancouver, BC

Postby tuxx-home.at » Wed Aug 08, 2007 11:46 am

Well, the second Xorg.0.log file looks good.
Can you `ssh` in from another machine when your system seems to hang?

Is the file "/usr/lib/dri/mga_dri.so" installed on your system?

What's the output of `glxinfo` and `xdpyinfo`?
User avatar
tuxx-home.at
Supreme Commander
Supreme Commander
 
Posts: 2199
Joined: Mon Jan 01, 2007 12:51 pm
Location: Vassach - Austria - Europe

Postby fission » Mon Sep 03, 2007 10:27 pm

tuxx-home.at wrote:Well, the second Xorg.0.log file looks good.
Can you `ssh` in from another machine when your system seems to hang?

Is the file "/usr/lib/dri/mga_dri.so" installed on your system?

Yes to both.

What's the output of `glxinfo` and `xdpyinfo`?

Attached.

Thanks,
Tyler
Attachments
glxinfo.nodri.out
(4.46 KiB) Downloaded 321 times
glxinfo.dri.out
(4.09 KiB) Downloaded 315 times
fission
Private
Private
 
Posts: 9
Joined: Mon Jul 30, 2007 11:15 pm
Location: Vancouver, BC

Postby fission » Mon Sep 03, 2007 10:28 pm

Seems you can't attach more than 3 items per post. Pity.
Attachments
xdpyinfo.nodri.out
(4.21 KiB) Downloaded 336 times
xdpyinfo.dri.out
(6.12 KiB) Downloaded 298 times
fission
Private
Private
 
Posts: 9
Joined: Mon Jul 30, 2007 11:15 pm
Location: Vancouver, BC

Postby Stratis » Tue Sep 04, 2007 6:21 am

I was under the impression that acceleration is not possible with
Xinerama enabled (on Linux):

Mgadriver-4.0 Matrox distribution Readme.txt wrote:After starting X, there should be a "direct rendering enabled"
message in the X server startup log. Please note that DRI isn't
enabled if you're using the Xinerama extension. You may want to
keep two "XF86Config" files on hand -- one for DRI and the other
for DualHead.


Probably a difference with my G400 and your G550.

I would love to get that working too...
Stratis
Sergeant
Sergeant
 
Posts: 10
Joined: Thu Jul 26, 2007 10:12 am

Postby fission » Tue Sep 04, 2007 7:06 pm

Stratis wrote:I was under the impression that acceleration is not possible with Xinerama enabled (on Linux):


Yeah, I remember reading that, too. But I do get that message even with Xinerama enabled:
Code: Select all
(II) MGA(0): Direct rendering enabled


I'll try it without Xinerama later today to see if that makes any difference.

Tyler
fission
Private
Private
 
Posts: 9
Joined: Mon Jul 30, 2007 11:15 pm
Location: Vancouver, BC

Postby tuxx-home.at » Mon Sep 17, 2007 9:37 am

Yeah, I remember reading that, too. But I do get that message even with
Xinerama enabled:


And does the logfile contain statements like "Disabling DRI" later on?
Sometimes, DRI gets disabled on the second head only, but that depends
on your configuration.
User avatar
tuxx-home.at
Supreme Commander
Supreme Commander
 
Posts: 2199
Joined: Mon Jan 01, 2007 12:51 pm
Location: Vassach - Austria - Europe

Postby fission » Thu Oct 11, 2007 4:43 am

tuxx-home.at wrote:And does the logfile contain statements like "Disabling DRI" later on?
Sometimes, DRI gets disabled on the second head only, but that depends
on your configuration.

It turns out that I can't disable XINERAMA, as it's a builtin extension and adding the disable option in ServerFlags doesn't help any.

You're right, though! There are thousands of entries like this just after the display freezes:
Code: Select all
(EE) MGA(0): [dri] Idle timed out, resetting engine...
fission
Private
Private
 
Posts: 9
Joined: Mon Jul 30, 2007 11:15 pm
Location: Vancouver, BC

Postby tuxx-home.at » Thu Oct 11, 2007 8:17 am

It turns out that I can't disable XINERAMA, as it's a builtin extension


The extension is always built-in, but it usually isn't enabled by default, you
need to specify this in your xorg.conf.

You can specify this either in the ServerLayout or ServerFlags section of
your xorg.conf:

Code: Select all
Section "ServerLayout"     # or ServerFlags
   [...]
   Option "Xinerama" "Off"
   [...]
EndSection


And it should get disabled.
You can check this with the help of `xdpyinfo` (output should look like
below if xinerama is disabled):

Code: Select all
tuxx@vi-edv003:~$ xdpyinfo | grep -i xinerama
tuxx@vi-edv003:~$


(EE) MGA(0): [dri] Idle timed out, resetting engine...


Are you sure that you're using the unofficial drivers from within this forum??
I know this bug only occured on the Xorg mga driver a while ago when
heavy DRI usage was requested by Xclients.
User avatar
tuxx-home.at
Supreme Commander
Supreme Commander
 
Posts: 2199
Joined: Mon Jan 01, 2007 12:51 pm
Location: Vassach - Austria - Europe

Postby fission » Mon Oct 15, 2007 11:42 pm

tuxx-home.at wrote:Are you sure that you're using the unofficial drivers from within this forum??
I know this bug only occured on the Xorg mga driver a while ago when
heavy DRI usage was requested by Xclients.

I am quite certain:
Code: Select all
% md5sum /usr/lib/xorg/modules/drivers/mga_{drv.so,hal_drv.so}
dfef4aeb7168d8e85c9366e2a38a4e0a  /usr/lib/xorg/modules/drivers/mga_drv.so
bc983da5899268025e453e0d5d892d5e  /usr/lib/xorg/modules/drivers/mga_hal_drv.so

These should match the MD5s in your driver pack.
fission
Private
Private
 
Posts: 9
Joined: Mon Jul 30, 2007 11:15 pm
Location: Vancouver, BC

Postby tuxx-home.at » Thu Oct 18, 2007 9:18 pm

Well, no, they don't.

Code: Select all
tuxx@thor:/tmp/matroxdriver_mga-x86_32-4.4.3/xserver$ md5sum */*.so
10e1353c10af6038b3b9c0476857e17f  4.3.0/mga_drv.so
e6d8460e0d34b9480b90c448e28640c5  4.3.0/mga_hal_drv.so
0d4b6a8678979d3851ebed296dc79654  6.7.0/mga_drv.so
8f19c44b7c1cb341d59b9003c18d803d  6.7.0/mga_hal_drv.so
d1804b61bdf38d7aa7a9f1c07da20c73  6.8.0/mga_drv.so
93fcfb87dfa4ec3ccaa6018661dc40e7  6.8.0/mga_hal_drv.so
8ee03c6acc927c66fd56633a0f3f9f9b  6.8.1/mga_drv.so
547b7f4be7d7c4011c0fae62b9a0b5d8  6.8.1/mga_hal_drv.so
cbca906dac47808e285c7af74f4967cd  6.8.2/mga_drv.so
8ad43c29d6a5fb59f0db2583b1ff2ee6  6.8.2/mga_hal_drv.so
6051fa0225f627d53668483d3f18409a  6.9.0/mga_drv.so
2349697c5dca2f8b5bc1949328eb3c7e  6.9.0/mga_hal_drv.so
307d30a1ea10a25ee1ed928bacdffb41  7.0.0/mga_drv.so
233b308ec0d13825573fcb0cb3554b5a  7.0.0/mga_hal_drv.so
307d30a1ea10a25ee1ed928bacdffb41  7.1.0/mga_drv.so
233b308ec0d13825573fcb0cb3554b5a  7.1.0/mga_hal_drv.so
tuxx@thor:/tmp/matroxdriver_mga-x86_32-4.4.3/xserver$
User avatar
tuxx-home.at
Supreme Commander
Supreme Commander
 
Posts: 2199
Joined: Mon Jan 01, 2007 12:51 pm
Location: Vassach - Austria - Europe

Postby fission » Tue Nov 06, 2007 12:12 am

tuxx-home.at wrote:Well, no, they don't.


I believe they do match the 64-bit versions.
fission
Private
Private
 
Posts: 9
Joined: Mon Jul 30, 2007 11:15 pm
Location: Vancouver, BC

Postby tuxx-home.at » Wed Nov 07, 2007 7:40 am

Ah, you're right. I somehow missed the point that you're using 64bit drivers.

Lately people are reporting this problem again and I don't know how it has
been reintroduced (maybe due to a new version of the X server, the mesa
libraries, or something like this).

Currently, I don't have a solution to this, but I'll keep you updated if I have
any updates on this.
User avatar
tuxx-home.at
Supreme Commander
Supreme Commander
 
Posts: 2199
Joined: Mon Jan 01, 2007 12:51 pm
Location: Vassach - Austria - Europe

Postby fission » Wed Nov 07, 2007 10:00 am

No worries; I don't think I mentioned it. ;-)

Thanks for all your help. I'm planning to move to Gutsy next month once I've ironed out a few kinks in my test environment. Maybe it will work then.
fission
Private
Private
 
Posts: 9
Joined: Mon Jul 30, 2007 11:15 pm
Location: Vancouver, BC

Postby tuxx-home.at » Thu Nov 22, 2007 10:52 am

Maybe you're interested in giving admered1's patchset a try?

[http://matrox.tuxx-home.at/viewtopic.php?t=415]

If you want to, I can make you an installer package with this patch included
to see if it helps you.
User avatar
tuxx-home.at
Supreme Commander
Supreme Commander
 
Posts: 2199
Joined: Mon Jan 01, 2007 12:51 pm
Location: Vassach - Austria - Europe

Next

Return to Matrox G-Series Cards

Who is online

Users browsing this forum: No registered users and 8 guests

cron