A minor RH9 video problem - GF4

[Metaxas]

Ok, I have finally gotten the video driver installed...however, I edited /etc/X11/XF86Config as per the instructions in the video driver file...however, I STILL cannot activiate Hardware 3D Acceleration...what did I do wrong?

Yes, I am a Linux n00b.

That is all.

:D

[Metaxas]

Well, I did some more editing on the XF86Config file, using the XF86Conig-sample provided from nVidia and I seem to be having a problem...

I keep getting a parse error on line 5 of the config file when X tries to start, I know how its formatted, and I can't figure out what the deal is....of course I made sure it was formatted for my particular version, and didn't just copy the XF86Config-sample and rename it....

[bwkaz]

So... post line 5 of your config file...

[Metaxas]

Screen 0 "Screen AGP" 0 0

I made sure to keep the formatting from the original version of the config, but I made sure to keep the names from both sections matched up.

I know its probably something simple.

[Metaxas]

Here is a copy of my entire XF86Config file:



# XFree86 4 configuration created by redhat-config-xfree86

Section "ServerLayout"
Identifier "AGP”
Screen 0 “Screen AGP” 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"
EndSection

ection "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 "Dell"
ModelName "Dell 1800FP (Analog)"
HorizSync 30.0 - 80.0
VertRefresh 56.0 - 85.0
Option "dpms"
EndSection

Section “Device”
Identifier “NV AGP”
VendorName “nvidia”
Driver “nvidia”
BusID “PCI:2:00.0”
End Section

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

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

Now I used lspci to see where my video card was, and it listed it as 02:00.0 - does that extra zero on the beginning have any impact?

[bwkaz]

Are you editing this config file in MS Word? Because I see the Word trademark "smart quotes" (which, BTW, are really misnamed -- they are really quite stupid) on that line and the line above it. Notice how the quotes are curved, where in certain other cases, they're straight? I also see the same thing after extmod, inside the normal quotes.

If you're using Word, then try using a normal plaintext editor (like Notepad or something, or gvim/kedit/gedit/mc's editor/pico -w/nano -w or similar) to do the editing.

No, the extra zero in the PCI ID shouldn't have anything to do with it. But unrecognized characters probably do. ;)

[Metaxas]

You know, that is just cool, and I don't know if I would have ever noticed that either;. Thanks! Maybe this mess will work now... :)

[Metaxas]

Ok, I fixed the parse errors...all the quotes and everything are fixed...including that space that hanging out between the words End and Section a little later down the list...oops.

But now...I STILL cannot boot with this config...

I used lspci to get a reading on where everything is, so I could get the approaite BusID...however, it says it can't find the card there, and lspci says

02:00.0 VGA Compatible Controller..blah blah blah

Huh?

:D

[bwkaz]

Can you post (edit: never mind, not post, attach it) the new log file?

[Metaxas]

Ok, let me tell you what I did....

I took the BusID statment OUT of the XF86Config just to see what it would do...it worked...well, sorta.

I can now get into RH error free, however, I STILL cannot activiate Hardware 3D Acceleration.

You still want to see my logs?

Edit: Which ones, if so?

[Metaxas]

Ok here you go....

[bwkaz]

You cannot activate "hardware 3D" because, again, RH does not understand how the drivers work, or does not want to acknowledge that they work. You still very likely have 3D!

Instead of relying on (broken) GUI tools, try running tuxracer. Or try running glxinfo -- if you see a line that says "direct rendering: Yes", then you should be OK. If tuxracer works at more than 1 fps, you should also be OK.

That log looks fine.

[Metaxas]

Thank you.