Error after launching

[Gniss]

I'm trying to run ATITD in Linux for first time and after successful launch it goes into infinite loop producing following message in the loop. Anyone know what's wrong?

Xlib: extension "GLX" missing on display ":0.0".

[Pluribus]

Either your video card doesnt support OpenGL or your driver install isnt correct.

What video card?

[ArmEagle]

If you have a NVidia, then don't forget to read the documentation after downloading their installation file (the latest [5328] might cause problems)
(/usr/share/doc/NVIDIA..../README here).
You need to load the Glx module in your XF86Config-4 (or just XF86Config) file. And do a bit more, but it's all in the readme.

If you're using ATI ore other type, then I have no tips.


(Just typing this for the record)

[Guido]

If you are using SuSE -

run sax2 from the prompt
if you are not root you will be prompted for the password
under graphics card enable 3D support
restart the xserver

If there is a problem with the hardware driver opengl can be run using the messa files - these are a software alternative to the hardware 3d acceleration of the graphics, perfromance though is notoriously slow.

if gears is on your system

> gears

you will be able to see a frames per second 3d gears program.

> glxinfo

will show you information about your opengl setup.

For messa not to be working and the hardware acceleration to be, you will not want to see messa mentioned in the output, but instead references to your graphic card.

ATITD appears to be using glut so ensure that is installed corectly as well.

YAST(2) is the best place, on a SuSE install, to quickly update software required on your system.

When it comes to NVIDIA drivers though, on 8.2 (not sure of 9.0 - though the support forums also make ref) SuSE they should be downloaded from NVIDIA (probably best not to use the latest driver 5328 - but use 4496 instead). Not only check the readme supplied with the NVIDIA driver, but also the support forums for installation of the NVIDIA driver on the SuSE website

Hope this helps.

[Gniss]

A brand new Linux install. It is Nvidia 4496 currently under Suse 9.0. I was tempted to try to upgrade but will leave that alone for now. It's a Sony PCG-GRT270G laptop with an Nvidia FX Go 5600 chip set. I've had it about 6 weeks, and for what it is worth have not had any video problems under Windows with a variety of games, though ATITD in Windows runs but dies after about 10 minutes as described by me on an earlier post on old Windows forum....never fixed though Teepy said it seemed like a bug. I'll try some of these suggestions when I get home later.

[Pluribus]

All of this information comes DIRECTLY from the NVIDIA README...

If you already have an XF86Config file working with a different driver
(such as the 'nv' or 'vesa' driver), then all you need to do is find
the relevant Device section and replace the line:

Driver "nv"
(or Driver "vesa")

with

Driver "nvidia"

In the Module section, make sure you have:

Load "glx"

You should also remove the following lines:

Load "dri"
Load "GLcore"

if they exist. There are also numerous options that can be added to
the XF86Config file to fine-tune the NVIDIA XFree86 driver. Please see
Appendix D for a complete list of these options.

Q: X starts for me, but OpenGL applications terminate immediately.

A: If X starts, but OpenGL causes problems, you most likely have a
problem with other libraries in the way, or there are stale symlinks.
See Appendix C for details. Sometimes, all it takes is to rerun
'ldconfig'.

You should also check that the correct extensions are present;
'xdpyinfo' should show the "GLX", "NV-GLX" and "NVIDIA-GLX" extensions
present. If these three extensions are not present, then there is
most likely a problem with the glx module getting loaded or it is
unable to implicitly load GLcore. Check your XF86Config file and make
sure that you are loading glx (see "Editing Your XF86Config File"
above). If your XF86Config file is correct, then check the XFree86
log file for warnings/errors pertaining to GLX. Also check that all
of the necessary symlinks are in place (refer to Appendix C).

Q: Why do OpenGL applications run so slow?

A: The application is probably using a different library still on your
system, rather than the NVIDIA supplied OpenGL library. Please see
APPENDIX C for details.

[Gniss]

Thanks for your patience and all the suggestions...still not working though I am getting the hang of Linux a bit.

The previous error was encountered when XF86Config was set to use driver 'nv'. glxinfo would produce the same error message ('glx' missing etc.). I gather that 'nv' is not really an nvidia driver, but something Suse supplies.

Next stop was to try to download drivers directly from Nvidia.

Again, it is a Nvidia FX Go 5600 chip set....pretty new. This is not listed as supported in version 4496. It is listed as supported in version 5328. I boot into runlevel 3 at a command prompt and the install of either of these goes fine and then results in the same problem. Sax2 starts and then hangs with a blank screen. I have to reboot. When I do, XF86Config has been set as I imagine is correct to use driver 'nvidia'. To get system to reboot into KDE I have to manually edit that back to 'nv'.

Any suggestions as to what to try next?

[Hirokache]

In general you have to edit the XF86Config file yourself after installing the NVIDIA drivers. And generally you will have to change the driver listed there to "nvidia" and add the line "Load glx" to the module section.

Do you also have an XF86Config-4? If so, and you are not sure which one you are actually using, try making the changes to both.

[Gniss]

In general you have to edit the XF86Config file yourself after installing the NVIDIA drivers. And generally you will have to change the driver listed there to "nvidia" and add the line "Load glx" to the module section.

Do you also have an XF86Config-4? If so, and you are not sure which one you are actually using, try making the changes to both.

Thanks...tried this with same results. :(

[Gniss]

Got it! After looking through my error log files it seemed like problem had something to do with AGP not being detected or used. Guido mentioned the site eee.nvnews.net. After scanning lots of posts there discovered that the problem could be fixed by manually editing Option "NvAGP" "1" in XF86Config.

[Hirokache]

Yay! Welcome to a brand new world ;p

[ArmEagle]

Ah gratz,

Just for reference..
If you have problems then take a look in /var/log/XFree86.0.log
And search for a line starting with (EE).
That should say what the rpoblem is and searching a bit on the net should give you a solution.

Happy Fragging!...
euh. wel ;)