PDA

View Full Version : segmentation fault after font problem


ertuni
20th August 2004, 19:15
Help!

I'm trying to run ATITD on a SuSE 8.1 installation with a Matrox G550 graphics card. CPU is an Intel P4 2.53, 512 MB physical RAM, 2.5 G virtual.

With 3D acceleration disabled, the game is so slow as to be unuseable (less than 1 fps, including menus), but it basically works.

With 3D acceleration enabled, I get as far as seeing my character on the island, but about one second later, the game just segfaults. In this screen and also while loading the game (but not in the login screen where I enter character name and password!), most fonts are very strange, like colourful noise. Nothing is decipherable. It looks as if random data was being copied to the frame buffer device. (I've cut a sample from the eGenesis logo screen; see attached file).

OpenGL demos such as tuxracer, racer, glxgears just work perfectly.

glxinfo says things like:

direct rendering: Yes
server glx vendor string: SGI
[...]
OpenGL vendor string: VA Linux Systems Inc.
OpenGL renderer string: Mesa DRI G400 20020221 AGP 1x x86/MMX/SSE
OpenGL version string: 1.2 Mesa 4.0.4

I start the client using cd ~/eClient; ./elaunch. I tried ./elaunch -noext as well, for the same result. I tried LD_ASSUME_KERNEL=2.4.1 ./elaunch as suggested in some of the posts here, but it just does the same thing.

Any ideas?

Pluribus
21st August 2004, 05:18
Can you email me a copy of your egenesis.bug file? I want to see if there is anything obvious... Although you system is attempting to use a 2 year old G400 driver on the G550.

pluribus@pluribus.org

ertuni
21st August 2004, 08:28
Can you email me a copy of your egenesis.bug file? I want to see if there is anything obvious...

It's on its way.

Although you system is attempting to use a 2 year old G400 driver on the G550.

I was wondering about that G400 note as well. Is there any way to get a more current driver without updating the whole X system?

Thanks,
Marc

ertuni
21st August 2004, 09:38
Although you system is attempting to use a 2 year old G400 driver on the G550.

I just went to the Matrox site, downloading their latest binary driver package for the G550 (dated 7/03). This includes an updated mga_drv.o module for X (which does not improve anything), but no newer mga_dri.o module. They say that the mga_dri.o module included in XFree86 4.3.0 is current. In fact, the mga_dri.o modules included for older XFree86 versions do not include references to G550 cards. Thus, the official G550 DRI module is apparently supposed to identify itself as a G400 driver.

No driver problem, then.

Pluribus
22nd August 2004, 03:03
Major stump... Can you update Mesa to something newer than 4.0.4 (According to the Mesa page it was released in October 2002. And there have been a LOT of multitexturing fixes since then....

ertuni
22nd August 2004, 10:41
Major stump... Can you update Mesa to something newer than 4.0.4 (According to the Mesa page it was released in October 2002. And there have been a LOT of multitexturing fixes since then....
Of course, I can try that. Before I go overhauling my whole system, could you or anybody explain to me how Mesa, DRI and XFree86 come together?

(I consider myself somewhat unix savvy, but I've only ever used 3d acceleration once before, and I really have no idea how it's being put together on the lower levels.)

'Cause it seems that this particular system already has Mesa 5.0 installed, which, however, is not even being used by eClient -- the binary is statically linked, and the couple of dynamic libraries that are included only reference pretty basic stuff.

So to update that 4.0.4 reference, I guess I would have to update XFree86's DRI (which is based on Mesa in turn, I know), not the Mesa libraries themselves? And since DRI appears to be an integral part of X, I would have to redo the core X installation? Is that right?

Thanks for taking the time to troubleshoot this! ;-)

ertuni
28th August 2004, 14:02
So to update that 4.0.4 reference, I guess I would have to update XFree86's DRI (which is based on Mesa in turn, I know), not the Mesa libraries themselves? And since DRI appears to be an integral part of X, I would have to redo the core X installation? Is that right?
Since there've been no further followups to this, I conclude that I would probably have to do a major overhaul of the system. Exchanging the whole X installation just for a game seems like a lot of work to me. :)

Don't try to run ATITD on XFree 4.3.0 or earlier with a Matrox Graphics Adaptor.

Thanks, anyway!