Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
nvidia drivers and fedora core 3
#1

to install the nvidia driver and get it working with the default kernels shipped with Fedora Core Release 3 do as follows (you may want to print this document or save it as a file to read while in Text mode):-

 

Step one: GET THE DRIVER

 

first of all get this nvidia driver (for i386, if you have amd or other architecture, go to www.nvidia.com and download the correct driver).

 

download it somewhere easy to remember like /home/anyweb

 

Step Two: BACKUP IMPORTANT FILES

 

now login via root in a console and do as follows

 



Code:
cp /etc/X11/xorg.conf /etc/X11/xorg.conf.org
cp /boot/grub/grub.conf /boot/grub/grub.conf.org
cp /etc/inittab /etc/inittab.org




 

Step Three: EDIT SOME FILES

 

* first we will stop the GUI from automatically loading

 

login as root and do as follows:

 



Code:
vi /etc/inittab

find the line that reads

id:5:initdefault: and change it to read id:3:initdefault:

save your changes with :wq




 

*now (as root) we will edit the grub boot loader and stop the red hat graphical boot (rhgb)

 



Code:
vi /boot/grub/grub.conf

find the line that reads

kernel /vmlinuz-2.6.9-1.667 ro root=LABEL=/1 rhgb quiet
and change it to read
kernel /vmlinuz-2.6.9-1.667 ro root=LABEL=/1 quiet




 

Step Four: EXIT GUI MODE

 

easy way to do this is to reboot, so go ahead and reboot, or as root type init 3

 

Step Five: INSTALL THE DRIVER

 

Login as root again, and cd to the directory you saved the nvidia file (/home/anyweb/)

 

do as follows

 

 



Code:
sh NVIDIA-Linux-x86-1.0-6629-pkg1.run




 

answer OK to any questions it asks and make note of any errors (there will be some, don't worry).

 

Step Six: EDIT YOUR xorg.conf FILE

 

now we need to edit the xorg.conf file and remove the following line (under module)

 

 

 

 



Code:
vi /etc/X11/xorg.conf

find this section

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

edit it so it now reads

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


and find this section

Section "Device"
       Identifier  "Videocard0"
       Driver      "vesa"
       VendorName  "Videocard vendor"
       BoardName   "VESA driver (generic)"


edit it so it now reads

Section "Device"
       Identifier  "Videocard0"
       Driver      "nvidia"
       VendorName  "Videocard vendor"
       BoardName   "VESA driver (generic)"



save the file :wq




 

Step Seven: LOAD THE NVIDIA MODULE AT BOOT

 

login as root and do as follows:



Code:
vi /etc/rc.d/rc.local

add the line 'modprobe nvidia
' so it now looks something like this

#!/bin/sh
#
# This script will be executed *after* all the other init scripts.
# You can put your own initialization stuff in here if you don't
# want to do the full Sys V style init stuff.

touch /var/lock/subsys/local
modprobe nvidia

save the file :wq




 

Step Eight: COPY FILE/CHANGE OWNERSHIP

 

now copy some files.. as root

 



Code:
cp -a /dev/nvidia* /etc/udev/devices
chown root.root /etc/udev/devices/nvidia*




 

 

Step Nine REBOOT THE COMPUTER

 

this howto worked fine for me on a plain Fedora Core Release 3 install, with Nvidia Geforce 6800 GT (AGP) and the default kernel.

 

Quote:[anyweb@localhost ~]$ glxgears45844 frames in 5.0 seconds = 9168.800 FPS

66613 frames in 5.0 seconds = 13322.600 FPS

56198 frames in 5.0 seconds = 11239.600 FPS

66199 frames in 5.0 seconds = 13239.800 FPS

68422 frames in 5.0 seconds = 13684.400 FPS

68244 frames in 5.0 seconds = 13648.800 FPS

68221 frames in 5.0 seconds = 13644.200 FPS

66314 frames in 5.0 seconds = 13262.800 FPS

68218 frames in 5.0 seconds = 13643.600 FPS

67884 frames in 5.0 seconds = 13576.800 FPS

65867 frames in 5.0 seconds = 13173.400 FPS

66753 frames in 5.0 seconds = 13350.600 FPS

68425 frames in 5.0 seconds = 13685.000 FPS

66579 frames in 5.0 seconds = 13315.800 FPS

66013 frames in 5.0 seconds = 13202.600 FPS

57304 frames in 5.0 seconds = 11460.800 FPS

42549 frames in 5.0 seconds = 8509.800 FPS

51651 frames in 5.0 seconds = 10330.200 FPS

57783 frames in 5.0 seconds = 11556.600 FPS

67616 frames in 5.0 seconds = 13523.200 FPS

68449 frames in 5.0 seconds = 13689.800 FPS

65505 frames in 5.0 seconds = 13101.000 FPS
 

look at those numbers ^^ !!! :P

 

here is my working xorg.conf for you in case you are interested

 

cheers

 

anyweb

xorg.conf



Attached Files
.conf   xorg.conf (Size: 2.8 KB / Downloads: 17)
Reply
#2

if you get the following error when trying to run tuxracer or glxgears

Quote:[anyweb@localhost ~]$ glxgearsError: Could not open /dev/nvidiactl because the permissions

are too resticitive.  Please see the FREQUENTLY ASKED QUESTIONS

section of /usr/share/doc/NVIDIA_GLX-1.0/README for steps

to correct.

Segmentation fault
 

the read this

 

Quote:Q: OpenGL applications exit with the following error message: 

        Error: Could not open /dev/nvidiactl because the permissions

        are too restrictive.  Please see the FREQUENTLY ASKED QUESTIONS

        section of /usr/share/doc/NVIDIA_GLX-1.0/README for steps

        to correct.

 

A: It is likely that a security module for the PAM system may be

changing the permissions on the NVIDIA device files.  In most cases

this security system works, but it can get confused.  To correct this

problem it is recommended that you disable this security feature.

Different Linux distributions have different files to control this;

please consult with your distributor for the correct method of

disabling this security feature.  As an example, if your system has

the file

        /etc/security/console.perms

then you should edit the file and remove the line that starts with

"<dri>" (we have also received reports that additional references to

<dri> in console.perms must be removed, but this has not been verified

by NVIDIA).  If instead your system has the file

        /etc/logindevperms

then you should edit the file and remove the line that lists

/dev/nvidiactl.  The above steps will prevent the PAM security system

from modifying the permissions on the NVIDIA device files.  Next,

you will need to reset the permissions on the device files back

to their original permissions and owner.  You can do that with the

following commands:

        chmod 0666 /dev/nvidia* chown root /dev/nvidia*
 

two ways around it, do as it says above by



Code:
vi /etc/security/console.perms

find the <dri> section and DELETE it

save :wq




 

then do

 



Code:
[root@localhost ~]# chmod 0666 /dev/nvidia*
[root@localhost ~]# chown root /dev/nvidia*




 

 

or run the game temporarily as root (it will work, just be security conscious !)

 

cheers

 

anyweb

Reply
#3

Worked for me with my GeForce4 Ti4200 not a problem.

 

Thanks for that tip B)

Reply
#4
If anyone tries this with the Gforce 440 MX SE let me know hehe
Reply
#5

i might need a new video card ;)

 

1159 frames in 5.0 seconds = 231.800 FPS

1060 frames in 5.0 seconds = 212.000 FPS

1320 frames in 5.0 seconds = 264.000 FPS

1200 frames in 5.0 seconds = 240.000 FPS

1320 frames in 5.0 seconds = 264.000 FPS

1200 frames in 5.0 seconds = 240.000 FPS

1080 frames in 5.0 seconds = 216.000 FPS

1200 frames in 5.0 seconds = 240.000 FPS

1200 frames in 5.0 seconds = 240.000 FPS

1320 frames in 5.0 seconds = 264.000 FPS

1320 frames in 5.0 seconds = 264.000 FPS

1200 frames in 5.0 seconds = 240.000 FPS

Reply
#6

all that was needed was a lot of tweaking here and there ;)

 

53476 frames in 5.0 seconds = 10695.200 FPS

70572 frames in 5.0 seconds = 14114.400 FPS

70492 frames in 5.0 seconds = 14098.400 FPS

70176 frames in 5.0 seconds = 14035.200 FPS

70241 frames in 5.0 seconds = 14048.200 FPS

70073 frames in 5.0 seconds = 14014.600 FPS

Reply
#7

cool what tweaking did you do, share with us mortals !

 

and what video card

 

cheers

 

anyweb

Reply
#8

the main thing causing it to go so slow was 'rivafb' running along with it causing it to become unstable i removed that. The I made it so that only the necessary processes could run and reduced to 2 desktops (as oppesed to 6, still allowing gnome to look nice.) After this i just performed an update of FC3 and that did the opposite effect on what i thought would do. I thought doing this would make my fps drop but it had the opposite effect.

 

After performing this update i got the error on eggcups (printing system) and fixed it with

Code:
prelink /usr/lib/libdbus*so*


[i had to find it the hard way :( ]

 

Then thats where i left it.

 

Thats on my Nvidia Gforce4 4200Ti 64mb vram [Pretty bad really]

Reply
#9

Thanks anyweb...

 

I used your "how to" for nvidia drivers to get my dual head MX4000-64Twin running on FC3.

I only changed a few "strings" like the VESA driver (generic) to what FC3 labeled as my video card (NVIDIA GeForce 4 MX (generic). Also, I noticed if one were to change the display settings using the Applications, System Settings, Display GUI, that IT will write "nv" for the drivers string. I had to edit /etc/X11/xorg.conf replacing that system entry "nv" with "nvidia".

 

I knew it will work after seeing the Nvidia splash screen on both monitors.

 

Quick hardware list:

1 x G Force MX4000-64Twin (AGP)

2 x ViewSonic VG710s

 

Once again thanks anyweb for showing me the basics for installing the nvidia drivers for FC3.

 

Below are a few settings from my /etc/X11/xorg.conf for dual monitors.

 



Code:
Section "ServerLayout"
       Identifier     "Multihead layout"
       Screen      0  "Screen0" LeftOf "Screen1"
       Screen      1  "Screen1" 0 0
       InputDevice    "Mouse0" "CorePointer"
       InputDevice    "Keyboard0" "CoreKeyboard"
       Option      "Xinerama" "on"
       Option      "Clone" "off"
EndSection




 

Dual



Code:
Section "Monitor"
       Identifier   "Monitor0"
       VendorName   "Monitor Vendor"
       ModelName    "ViewSonic VG710s"
       DisplaySize  340        270
       HorizSync    30.0 - 82.0
       VertRefresh  50.0 - 85.0
       Option      "dpms"
EndSection

Section "Monitor"
       Identifier   "Monitor1"
       VendorName   "Monitor Vendor"
       ModelName    "ViewSonic VG710s"
       HorizSync    30.0 - 82.0
       VertRefresh  50.0 - 85.0
       Option      "dpms"
EndSection

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

Section "Device"
       Identifier  "Videocard1"
       Driver      "nvidia"
       VendorName  "Videocard Vendor"
       BoardName   "NVIDIA GeForce 4 MX (generic)"
       BusID       "PCI:1:0:0"
       Screen      1
EndSection




Reply
#10

I did do exactly as anyweb stated... When I rebooted my machine, I got an odd error...

 

It said "KERNEL panic! something"... It won't get any further, and I have to pull the plug.

 

Now, I'm running from windows, and I really don't wanna re-download and re-install everything again...

 

What can I do?

Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)