Click to See Complete Forum and Search --> : Video problem with RedHat 9
Metaxas
04-03-2003, 10:59 AM
Ok, specs first... :)
Asus A7N8X Deluxe
XP2400+
512Megs (2 x 256) PC3500 ram
Maxtor ATA 133 40Gig HDD
Enermax 431Watt P/S
GForce4 Ti4600
Cheiftec server case
Ok, I got the network drivers installed, and now I'm working on the video drivers. I ran the installer, and it did its thing with no problems, but it said I needed to edit my XF86Config file accordingly...ok, no problem...so I looked at the XF86Config-sample file provided from nVidia that gives you the things to put into your own config file. So I followed it, (I didn't just copy it though...heehee) and I though everything was ok.
Well, when I restart, I get a parse error on line 5 in the ServerLayout area of the config file. Now my screen names are matched up in both sections of the config file...and I have no clue as to what is causing this parse error. However, until I get this figured out, I have zero access to Hardware 3D acceleration, or any exteneded 3D functions.
Can someone maybe, hook me up with some
JamminJoeyB
04-03-2003, 11:06 AM
Post your XF86Config file. Once we can see what is in there maybe we can spot the problem.
Metaxas
04-03-2003, 11:34 AM
# 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
Ok, now I know that there was some useless stuff in here, but its better to post everything, that way I myself don't miss anything, I'm getting the parse error on line 5 in Serverlayout. Also, under section device, I used lspci to give me a list of PCI devices, as that is what the nVidia instructions said to do, now it was listed as 02:00.00 - however, I didn't put that extra 0 in there in the beginning...is that important...I know that sounds stupid...but I'm still learning Linux...and I'm sick of M$'s junk.
Metaxas
04-04-2003, 03:03 AM
Ok, I got it fixed.
[/thread]
bosox79
04-04-2003, 03:17 AM
Originally posted by Metaxas
Ok, I got it fixed.
[/thread]
just for future reference you may want to post what you did to fix your problem, so other JL uses will be able to solve this problem in the future:D
just a thought
Metaxas
04-04-2003, 04:35 AM
Oops, well, I hadn't seen anyone here in this thread so figured I was on the "ignore" list... :D
I fixed it by first, getting RID of those stupid "smart quotes"....and using the text editor..that took care of the parse errors, and fixing that line that said End Section, where it should have said EndSection.
Then, I had a BusID problem...so, out of desperation, I just took that line out.
And it works. :)
Now I have another problem. I'll start another thread that is realated to that problem though.
Thanks.
bosox79
04-04-2003, 10:34 PM
Originally posted by Metaxas
Oops, well, I hadn't seen anyone here in this thread so figured I was on the "ignore" list... :D
I fixed it by first, getting RID of those stupid "smart quotes"....and using the text editor..that took care of the parse errors, and fixing that line that said End Section, where it should have said EndSection.
Then, I had a BusID problem...so, out of desperation, I just took that line out.
And it works. :)
Now I have another problem. I'll start another thread that is realated to that problem though.
Thanks.
no problem:) like I said before other JL users may come in search on an answer to the exact same problem & it is helpful to post solutions, I have been guilty of not doing so myself:)