Edit Info Other
Login

xorg-x11-drv-nvidia"

Differences between revisions 7 and 8
Revision 7 as of 2009-02-13 11:05:49
Size: 4715
Editor: sunset06
Comment: mod eg FPS values for actual nvidia card, add extra section in config re nvidia ettings tool
Revision 8 as of 2009-04-19 10:57:37
Size: 5284
Editor: sunset06
Comment:
Deletions are marked like this. Additions are marked like this.
Line 78: Line 78:
If the animation is choppy or if FPS values are less than 800 FPS, 3D rendering is possibly being done in software. Please remember that glxgears ''is not a benchmark'', and should not be used to evaluate GPU performance. If the animation is choppy or if FPS values are less than 800 FPS, 3D rendering is possibly being done in software. Please remember that glxgears [[http://qa-rockstar.livejournal.com/7869.html|''is not a benchmark'']], and should not be used to evaluate GPU performance.

 * Check correct hardware 3D acceleration using applications (as suggested by above link)
{{{
yum install mesa-demos extremetuxracer xscreensaver-gl-extras
}}}
  * mesa-demos: Run {{{mesa-rain}}}, or {{{teapot}}}. Look for smooth animations.
  * extremetuxracer: Run {{{etuxracer}}}. If screen updates are in the order of once per second, 3D rendering is being performed in software.
  * xscreensaver-gl-extras: Set the active screensaver to one of the opengl screensavers ({{{sierpinski3d}}} or {{{glblur}}}).

What is xorg-x11-drv-nvidia?

xorg-x11-drv-nvidia is the package which provides the common files required by the nVidia driver. Its subpackage, xorg-x11-drv-nvidia-libs, provides the binary libraries used by the driver.

Installation Instructions

yum install xorg-x11-drv-nvidia

x86_64 users

If you are running x86_64 and want to have 3D acceleration with 32bit applications, you'll need to install the 32bit version of xorg-x11-drv-nvidia-libs:

yum install xorg-x11-drv-nvidia-libs.i386

Configuration

After initial driver installation or upon driver upgrades

The nVidia driver will be activated after a login / logout cycle, however it is highly recommended that you reboot immediately after initially installing or updating the nVidia drivers. Please note that you do not need to run nvidia-xconfig or nvidia-settings to configure your system's xorg.conf after driver installation. xorg.conf and any other applicable files will be edited for you.

Adjusting driver settings

Enabling the driver and basic configuration settings

Run Livna Display Configuration from the System | Administration menu or livna-config-display from the command line.

Detailed driver settings

RunnVidia Display Settings from the Applications | System Tools menu.

Common Problems

Scrolling in Firefox is slow (no 3D)

This often happens when you use nvidia-settings or nvidia-xconfig to configure your xorg.conf without letting livna-config-display do it's autoconfiguration first. To fix this, run these two commands:

nvidia-config-display disable
nvidia-config-display enable

Yum gives me a dependency errors about kmods and won't let me update.

This happens when a new kernel has been released and a matching kmod from RPM Fusion hasn't synced across all the mirrors, or vice-versa. Try giving it a few hours and if the problems persist, you can also try refreshing yum's cache:

yum clean metadata

If after this you still experience problems, please report a bug.

FAQ

Why should I use this package rather than the ones from nvidia.com?

The packages from nvidia.com have been known to replace libGL, which isn't a problem until you decide to use another X driver or uninstall the nvidia driver. The RPM Fusion packages will never overwrite files like this. As well, the drivers packaged at RPM Fusion will make your life a bit easier by letting you grab new kmods through Yum or the Software Update tool. A few extra utilities, to ensure that the drivers 'just work' with minimal user interaction (the initscripts, livna-config-display), are also included.

How come my xorg.conf is always getting edited for me ?

This is a known problem, it will be fixed with the introduction of rpmfusion-config-display. In the mean time, if you'd really like to stop the drivers from making changes to your xorg.conf, run the livna-config-display GUI interface and you'll find a checkbutton to disable editing. Alternatively, you can run this command in a terminal:

livna-config-display --active off

How can I tell if I am actually running the RPM Fusion packaged nVidia driver ?

  • Be sure you are using the 'nvidia' Xorg driver and that the kernel module is loaded:

cat /etc/X11/xorg.conf | grep Driver
lsmod | grep nvidia

You should see something similar to this (numbers will vary):

Driver     "nvidia"
nvidia 3923388 14
  • Check if OpenGL 3D acceleration is working:

glxinfo | grep direct

You should see:

direct rendering: Yes
  • Check using glxgears:

glxgears

A small window will open up showing a rotating cogs animation. Meanwhile, after every 5 seconds, the program displays the number of frames per second, for example (FX5600):

15377 frames in 5.0 seconds = 3075.217 FPS
15400 frames in 5.0 seconds = 3079.943 FPS
15395 frames in 5.0 seconds = 3078.872 FPS
<ctrl+c>

If the animation is choppy or if FPS values are less than 800 FPS, 3D rendering is possibly being done in software. Please remember that glxgears ''is not a benchmark'', and should not be used to evaluate GPU performance.

  • Check correct hardware 3D acceleration using applications (as suggested by above link)

yum install mesa-demos extremetuxracer xscreensaver-gl-extras
  • mesa-demos: Run mesa-rain, or teapot. Look for smooth animations.

  • extremetuxracer: Run etuxracer. If screen updates are in the order of once per second, 3D rendering is being performed in software.

  • xscreensaver-gl-extras: Set the active screensaver to one of the opengl screensavers (sierpinski3d or glblur).

Reporting bugs

If you think you've found a problem and would like to report it, include the following information along with the description of the bug:

  • Attach your /var/log/Xorg.0.log file
  • Attach your /etc/X11/xorg.conf file, if it exists
  • Run dmesg > ~/dmesg.txt and attach the "dmesg.txt" found in your home folder


CategoryPackage