Hi all I'm having trouble with DRI in Fedora, well I think that may be the prob anyway here are some of the erros messages I get: While trying to start ut2003 I get Xlib: extension "XiG-SUNDRY-NONSTANDARD" missing on display ":0.0".
Xlib: extension "XFree86-DRI" missing on display ":0.0".

While trying glxgears: Xlib: extension "XFree86-DRI" missing on display ":0.0".
Now this is a weird one, some times the gears show up but sometimes they don't

I'm running the newest updated kernel for fedora which is kernel-2.4.22-1.2140.nptl
my video card is a Geforce FX 5200 and I'm using the 4496 drivers.
Here is a copy of 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"
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/input/mice"
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 "PHILIPS 107T"
DisplaySize 310 230
HorizSync 30.0 - 71.0
VertRefresh 50.0 - 160.0
Option "dpms"
EndSection

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

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

Section "DRI"
Group 0
Mode 666
EndSection

Thanks for any help or pointers to docs

oops forgot to say that tuxracer works.

Nvidia just released a new set of drivers. Try that. Are you using a generic 5200 card? If that doesn't work try uninstalling and reinstalling with an old set of drivers. Some driver sets seem to support some things and not others. Sounds like it can handle GL ok?

Nvidia just released a new set of drivers. Try that. Are you using a generic 5200 card? If that doesn't work try uninstalling and reinstalling with an old set of drivers. Some driver sets seem to support some things and not others. Sounds like it can handle GL ok?

I did try the new drivers but they seemed crappy, I might try them again... anyway my card can handle GL pretty good. I tried glxgears first it worked fine, then when I tried it agian just a window with a blank black screen showed up with output in the console with how many fps I was getting but I couldn't see the gears!!! I have know idea what is going on

Your config file says its still using the generic nvidia drivers. After you install the new drivers there may be a reference to it at the top of the driver list called "custom" select that and reboot and see if you find any difference. That was how Fedora treated my Intel driver installation. Good luck!

I ran into that problem also to fix it I removed the following RPM :
rpm -qa | grep Mesa
rpm -e --nodeps XFree86-Mesa-libGL(which version is being used)

Re-install the NVIDIA drivers and it should work, then if you require the Mesa-libGL librairies re-install the rpm using rpm -Uhv XFree86-Mesa-libGL. Then you should have no problem with your GLX Gears.

HTH

Thanks this seemed to have worked!!! Is is safe to reinstall Mesa??? Asking this because tuxracer and other games need it.

Interesting, I have another box with a GeForce card. I'll have to remember that when I install on there. Thanks

For People who have the same problems as me here is what todo: uninstall Mesa because it screws up the Nvidia GLX but keep Mesa libGLU because it is used by tuxracer and other games. Don't worry about errors like: Xlib: extension "XFree86-DRI" missing on display ":0.0" because the Nvidia drivers don't use it anyway(they have there own way). Well for more info just have a look at the README for Nvidia GLX.

Well as far as I know it is okay, I did a yum install of a package and it re-installed the Mesa-libGL to satisfy a dependency but my GLX gears still work and there was no DRI error, you could try it and if it doesn't work properly go over the steps as above again to fix the problem.