Display Errors with Americas Army

[BritishNemesis]

I just installed Americas Army and the latest nvidia drivers and everything went very well.... the problem I have is when I run AA I get this error:

Xlib: extension "XFree86-DRI" missing on display ":0.0".
Xlib: extension "XiG-SUNDRY-NONSTANDARD" missing on display ":0.0".


Now I tried adding the dri module back into the xf86config but it changes nothing I still get this error. How do I fix this?

Below is my XF86Config file:

# XFree86 4 configuration created by redhat-config-xfree86

Section "ServerLayout"
Identifier "single head configuration"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "DevInputMice" "AlwaysCore"
EndSection

Section "Files"

# RgbPath is the location of the RGB database. Note, this is the name of the
# file minus the extension (like ".txt" or ".db"). There is normally
# no need to change the default.
# Multiple FontPath entries are allowed (they are concatenated together)
# By default, Red Hat 6.0 and later now use a font server independent of
# the X server to render fonts.
RgbPath "/usr/X11R6/lib/X11/rgb"
FontPath "unix/:7100"
EndSection

Section "Module"
Load "dbe"
Load "extmod"
Load "fbdevhw"
Load "glx"
Load "record"
Load "freetype"
Load "type1"
Load "dri"

EndSection

Section "InputDevice"

# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
# Option "Xleds" "1 2 3"
# To disable the XKEYBOARD extension, uncomment XkbDisable.
# Option "XkbDisable"
# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults). For example, for a non-U.S.
# keyboard, you will probably want to use:
# Option "XkbModel" "pc102"
# If you have a US Microsoft Natural keyboard, you can use:
# Option "XkbModel" "microsoft"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
# Option "XkbLayout" "de"
# or:
# Option "XkbLayout" "de"
# Option "XkbVariant" "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
# Option "XkbOptions" "ctrl:swapcaps"
# Or if you just want both to be control, use:
# Option "XkbOptions" "ctrl:nocaps"
#
Identifier "Keyboard0"
Driver "keyboard"
Option "XkbRules" "xfree86"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
EndSection

Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "IMPS/2"
Option "Device" "/dev/psaux"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "no"
EndSection

Section "InputDevice"

# If the normal CorePointer mouse is not a USB mouse then
# this input device can be used in AlwaysCore mode to let you
# also use USB mice at the same time.
Identifier "DevInputMice"
Driver "mouse"
Option "Protocol" "IMPS/2"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "no"
EndSection

Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "G90fb-2"
DisplaySize 360 270
HorizSync 30.0 - 97.0
VertRefresh 50.0 - 180.0
Option "dpms"
EndSection

Section "Device"
Identifier "Videocard0"
Driver "nvidia"
VendorName "Videocard vendor"
BoardName "NVIDIA GeForce 3 (generic)"
EndSection

Section "Screen"
Identifier "Screen0"
Device "Videocard0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Depth 24
Modes "1280x1024" "1280x960" "1152x864" "1024x768" "800x600" "640x480"
EndSubSection
EndSection

Section "DRI"
Group 0
Mode 0666
EndSection

[bwkaz]

What the...???

Your other post has been removed (along with my first response to it), since it's the same issue as this.

If you read nVidia's README file, you will see that you should NOT have the line in XF86Config that reads:

Load "dri"

Since you should not be loading that X module, you also don't need the Section "DRI", but it doesn't hurt anything. Having Load "dri" in there, though, does.

If you look at your /var/log/XFree86.0.log, you will see the reason that GLX failed to load, or failed to initialize, or failed to do whatever it is that it failed to do. Most likely it's due to either the wrong "glx" extension being used (libglx.a instead of nVidia's libglx.so), or it's due to your loading of the "dri" X module.

Also get rid of the Load "fbdevhw". That X module is not necessary for nVidia hardware, and while I don't know for sure whether it does cause problems, it wouldn't surprise me if it did.

But even still -- my entire post is nothing but conjecture based on your config file. I would have to see your log file to know what the problem is for sure (DON'T post it here! it's way too long -- either read it yourself and try to fix the problem in it, or rename it to have a .txt extension and attach it to your post so we don't have to scroll through it).

[BritishNemesis]

Great sorry about the repeat posts..... something must have gone wrong on my side.

I removed all those entries you discussed from the X86Config and rebooted... then tried to run Americas Army again with the same effect. Here's my XF86Config files... there were two of them and I wasn't sure which one was the most current so I'll attach both.

[BritishNemesis]

and the second file....

[bwkaz]

What does glxinfo | grep direct say now?

Anything helpful in the output of dmesg (after starting X)?

Did you upgrade to 2.6.0-test9 yourself? Or did Fedora come installed like that?

Either way, did you apply the patches required for kernel 2.6 to your nVidia driver source before compiling the kernel module? www.minion.de to get them, or wait until kernel 2.6 is released as stable, because then nVidia will release their 2.6-compatible drivers (which I'm assuming they have internally, though I don't know for sure).

[BritishNemesis]

Ok here's what I get from dmesg in terms of relevancy to the nvidia issue:

nvidia: module license 'NVIDIA' taints kernel.
0: nvidia: loading NVIDIA Linux x86 nvidia.o Kernel Module 1.0-4496 Wed Jul 16 19:03:09 PDT 2003
Linux agpgart interface v0.100 (c) Dave Jones
0: NVRM: AGPGART: unable to retrieve symbol table

and closer to the bottom:
0: NVRM: AGPGART: unable to retrieve symbol table

and glxinfo |grep direct produces:
[centurion@Centurion centurion]$ glxinfo |grep direct
Xlib: extension "XFree86-DRI" missing on display ":0.0".
direct rendering: No


Oh and yes I did upgrade the kernel myself and yes I did apply the kernel patch from minion.de

[bwkaz]

Originally posted by BritishNemesis
nvidia: module license 'NVIDIA' taints kernel.
0: nvidia: loading NVIDIA Linux x86 nvidia.o Kernel Module 1.0-4496 Wed Jul 16 19:03:09 PDT 2003
Linux agpgart interface v0.100 (c) Dave Jones This is all pretty standard...

0: NVRM: AGPGART: unable to retrieve symbol table That's wrong. ;)

Try adding Option "NvAgp" "1" to your XF86Config file.

Or, cat /proc/driver/nvidia/agp/status to see which AGP driver it tried to use. It still may have tried to use agpgart, which means you'll need to use the NvAgp option. If it fell back to nVidia internal AGP support (or whatever it calls it), then don't bother, as that's not the problem. You might try Option "NvAgp" "0" temporarily, to see if disabling AGP completely helps. It's not like you'll see any performance degradation anyway, unless the textures that you put onto the graphics card overflow its onboard memory...

Or, make sure you load (in addition to agpgart) the module for your specific AGP chipset. They're not all built into the agpgart.ko module anymore; you have to load both agpgart.ko and via-agp.ko (if you have a Via chipset).

[BritishNemesis]

Try adding Option "NvAgp" "1" to your XF86Config file. Try adding Option "NvAgp" "1" to your XF86Config file.

Tried that and got the same result. Then I tried NvAgp "0" and got this result....

[root@Centurion root]# armyops
Xlib: extension "XFree86-DRI" missing on display ":0.0".
open /dev/[sound/]dsp: Device or resource busy
Xlib: extension "XiG-SUNDRY-NONSTANDARD" missing on display ":0.0".
GL_EXT_bgra not supported - bailing out.

History:
Exiting due to error


Or, make sure you load (in addition to agpgart) the module for your specific AGP chipset. They're not all built into the agpgart.ko module anymore; you have to load both agpgart.ko and via-agp.ko (if you have a Via chipset).


When I run your cat command I get...
[root@Centurion root]# cat /proc/driver/nvidia/agp/status
Status: Enabled
Driver: NVIDIA
AGP Rate: 4x
Fast Writes: Disabled
SBA: Disabled

And when I run glxinfo I've noticed something else...
[root@Centurion root]# glxinfo
name of display: :0.0
Xlib: extension "XFree86-DRI" missing on display ":0.0".
display: :0 screen: 0
direct rendering: No
server glx vendor string: NVIDIA Corporation
server glx version string: 1.3
server glx extensions:
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_SGIX_fbconfig,
GLX_SGIX_pbuffer, GLX_ARB_multisample
client glx vendor string: SGI
client glx version string: 1.2
client glx extensions:
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context
GLX extensions:
GLX_EXT_visual_info, GLX_EXT_visual_rating
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce3/AGP/SSE/3DNOW!
OpenGL version string: 1.4.0 NVIDIA 44.96
OpenGL extensions:
GL_ARB_imaging, GL_ARB_multitexture, GL_ARB_texture_border_clamp,
GL_ARB_texture_cube_map, GL_ARB_texture_env_add,
GL_ARB_texture_env_combine, GL_ARB_texture_env_dot3, GL_EXT_abgr,
GL_EXT_blend_color, GL_EXT_blend_minmax, GL_EXT_blend_subtract,
GL_EXT_texture_env_add, GL_EXT_texture_env_combine,
GL_EXT_texture_env_dot3, GL_EXT_texture_lod_bias
glu version: 1.3
glu extensions:
GLU_EXT_nurbs_tessellator, GLU_EXT_object_space_tess

[bwkaz]

What about ldd /usr/X11R6/bin/glxinfo? Is it linking against nVidia's libGL.so?

If it's not that, I'm stumped.... :(

[BritishNemesis]

[centurion@Centurion centurion]$ ldd /usr/X11R6/bin/glxinfo
libGLU.so.1 => /usr/X11R6/lib/libGLU.so.1 (0x001a7000)
libGL.so.1 => /usr/X11R6/lib/tls/libGL.so.1 (0x004bf000)
libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x00b50000)
libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00a70000)
libpthread.so.0 => /lib/tls/libpthread.so.0 (0x00b96000)
libm.so.6 => /lib/tls/libm.so.6 (0x00a47000)
libc.so.6 => /lib/tls/libc.so.6 (0x0090c000)
libstdc++.so.5 => /usr/lib/libstdc++.so.5 (0x00d27000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00d1d000)
libdl.so.2 => /lib/libdl.so.2 (0x00a6b000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x008f4000)


Looks like I am out of luck :(

[bwkaz]

Yeah, wish I had a clue what it was... sorry. :(

Unless there are some other logs that you haven't looked at...

[BritishNemesis]

thanks for your time man. I really appreciate the help :D

[bwkaz]

Hmm, this might help. Just saw it in another thread.

Do you have an XFree86-MESA package installed? If so, blow it away.

[BritishNemesis]

k I tried but it seems that there are a junk load of dependencies

[centurion@Centurion centurion]$ rpm -e XFree86-Mesa-libGL-4.3.0-42
error: Failed dependencies:
libGL.so.1 is needed by (installed) XFree86-libs-4.3.0-42
libGL.so.1 is needed by (installed) qt-3.1.2-14
libGL.so.1 is needed by (installed) chromium-0.9.12-24
libGL.so.1 is needed by (installed) tuxracer-0.61-23
libGL.so.1 is needed by (installed) xawtv-3.88-6
libGL.so.1 is needed by (installed) XFree86-tools-4.3.0-42
libGL.so.1 is needed by (installed) xmms-1.2.8-3.p
libGL.so.1 is needed by (installed) xscreensaver-4.14-2


Also there are 2 of these mesa things which one do I want to get rid of?

XFree86-Mesa-libGLU-4.3.0-42
XFree86-Mesa-libGL-4.3.0-42

[bwkaz]

You want to get rid of libGL (libGLU is based on top of libGL; it can use just about any libGL in existence as long as it's recent enough).

You could always try to rpm -e --nodeps it, so that rpm doesn't check the dependencies (then reinstall the nVidia package, because the nVidia package supplies its own libGL.so.1).

I am not sure, however, that this won't screw up some of the packages that were listed...