View Full Version : NVIDIA 3D Problems Install
Sniffer
2004-10-01, 05:12 AM CDT
Hi to you all,
i have been able with the help of all of you to solve some problems that i was having, many thanks for that.
Though i'm stuck with NVIDIA 3D Now:
My system:
AGP - NVIDIA GeForce 5500
Fedora Core 3 Test 2 with Kernel 2.6.8-1.541 (Default Kernel)
I can't use livna rpm because their depot don't have the module for my kernel...so i proceed to the manual way:
1 - i have done a clean install
2 - i went to nvidia.com and download the linux driver
3 - init 3 and sh ./NVIDIA-Linux-x86-1.0-6111-pkg1.run
4 - Then accept the license and there wasn't any prebuild module on the nvidia.com so my system build their own module with the WARNING that RIVA module could not be load on boot because conflict with nvidia drivers.
5 - init 5 and i went to /etc/X11/Xorg.conf and i make the follow modifications:
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"
i reboot but just don't work.
Where and how can i add that nvidia module being launched on boot?
How can i see or disable that Riva module is not being loaded on boot?
Do i have to make more modifications on Xorg.conf, iam i missing something?
Any rpm module that is for my kernel (i think many of you must have the same kernel as me) so i can make an easy install of nvidia drivers?
Thanks for your time and help and please be detailed.
Sniff.
Linux_Justice
2004-10-01, 05:16 AM CDT
to edit file open terminal, you have to be root and type: gedit /etc/X11/xorg.cont and edit the file
Sniffer
2004-10-01, 05:25 AM CDT
hmmm, so i have to edit file in terminal mode (init 3).....i was editing in graphical mode (in gnome).
But that's all i have to do, i don't have to give instructions so the module nvidia can be load on boot (or this is made automatically?), or disable riva module (i don't know if it's active).
Many Thanks for the help and quick trigger :)
ghaefb
2004-10-01, 05:28 AM CDT
I guess you are using FedoraCore3test2
There is some nvidia module loading issue in this test release.
Solution:
Edit file /etc/rc.local and add this line: /sbin/modprobe nvidia
cylamanae
2004-10-01, 05:34 AM CDT
I basicly have the same system. The module is loaded automaticly. One way of ckecking this is go to test it with something with OpenGL support. The best that i have found is the screensavers. Which some of the screensavers run in OpenGL. Just basicly test the system with an opengl screensaver. That would tell you if the nvidia driver is installed correctly.
Calvin
Sniffer
2004-10-01, 11:21 AM CDT
Thanks for the reply's.
By your answers i presume i'm doing everything correctly, except that i have to change xorg.conf in terminal mode and maybe i need to edit etc/rc.local.
I will try this and i hope that i come with good news :).
In order to help me out here it's my xorg.conf after i have just installed nvidia drivers with the command:
sh :/NVIDIA-Linux-x86..........
# XFree86 4 configuration created by pyxf86config
Section "ServerLayout"
Identifier "Default Layout"
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 "ServerFlags"
Option "AllowMouseOpenFail" "yes"
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 "kbd"
Option "XkbModel" "pc105"
Option "XkbLayout" "pt"
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 "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "FP 747"
DisplaySize 340 270
HorizSync 31.0 - 83.0
VertRefresh 56.0 - 76.0
Option "dpms"
EndSection
Section "Device"
Identifier "Videocard0"
Driver "nvidia"
VendorName "Videocard vendor"
BoardName "VESA driver (generic)"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Videocard0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 16
Modes "800x600" "640x480"
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1024x768" "800x600" "640x480"
EndSubSection
EndSection
Section "DRI"
Group 0
Mode 0666
EndSection
Sniffer
2004-10-01, 12:41 PM CDT
I didn't reboot yet but when i try glxgears on the terminal it appears this:
[root@localhost ~]# glxgears
Xlib: extension "GLX" missing on display ":0.0".
glxgears: Error: couldn't get an RGB, Double-buffered visual.
[root@localhost ~]#
ln modules i have Load "glx"...!!
ghaefb
2004-10-01, 12:45 PM CDT
You need to restart X.
You can do that by Loging out. Or just press Ctrl+Alt+Backspace
Sniffer
2004-10-01, 12:50 PM CDT
Thanks for the tip, i have only see it now.
And yes the issue was the sbin/modprobe nvidia...many thanks for sharing your knowledge.
I have run glxgears
and i got:
[root@localhost ~]# glxgears
4717 frames in 5.0 seconds = 943.400 FPS
4682 frames in 5.0 seconds = 936.400 FPS
4813 frames in 5.0 seconds = 962.600 FPS
5070 frames in 5.0 seconds = 1014.000 FPS
5068 frames in 5.0 seconds = 1013.600 FPS
4785 frames in 5.0 seconds = 957.000 FPS
5006 frames in 5.0 seconds = 1001.200 FPS
4560 frames in 5.0 seconds = 912.000 FPS
X connection to :0.0 broken (explicit kill or server shutdown).
[root@localhost ~]#
I don't know but i achieve this result in kurumin (Debian Based) with an ATI Radeon 9200SE of 1000fps
But with my new AGP GF 5500FX i was expecting something better.......in linuxconsole (games distro) i got about 3500fps..............
In Fedora only 1000fps............
skythra
2004-10-15, 09:29 PM CDT
[skythra@localhost ~]$ glxgears
28924 frames in 5.0 seconds = 5784.800 FPS
29325 frames in 5.0 seconds = 5865.000 FPS
29326 frames in 5.0 seconds = 5865.200 FPS
29406 frames in 5.0 seconds = 5881.200 FPS
X connection to :0.0 broken (explicit kill or server shutdown).
[skythra@localhost ~]$
Just for comparison, thats on a ti4200 64mb
edit: (also running fedora core 3 test 3)
vBulletin® v3.8.1, Copyright ©2000-2009, Jelsoft Enterprises Ltd.