1. Computers
  2. Display Drivers
  3. Graphics Cards
  4. Memory
  5. Motherboards
  6. Processors
  7. Software
  8. Storage
  9. Operating Systems


Facebook RSS Twitter Twitter Google Plus


Phoronix Test Suite

OpenBenchmarking.org

NVIDIA Confirms Linux Driver Problems

NVIDIA

Published on 17 April 2012 06:19 AM EDT
Written by Michael Larabel in NVIDIA
5 Comments

Yesterday I reported on it appearing the 295.40 NVIDIA Linux driver effectively fell off a cliff with a range of performance regressions, stability issues, and other problems. This issue has been confirmed by NVIDIA and they're working to address the situation.

Last week NVIDIA released the 295.40 Linux driver in order to address a high-risk security vulnerability that could allow hackers to gain access to the system memory via the GPU and the un-patched graphics driver. It turns out that the security fix is responsible for these weird issues now being experienced by a number of NVIDIA GeForce Linux users.

Fortunately, it turns out that the problem is namely affecting those with pre-G80 graphics hardware. For any GeForce 6 or GeForce 7 series graphics cards, or the GeForce 8800GTX and first-generation 8800GTS, are affected by these problems if upgrading the driver. The mainline NVIDIA Linux driver just goes back to the GeForce 6 series but their legacy drivers haven't been updated for this security fix.

"We have been made aware of an interaction problem between the fix contained in the newest release any any card with a chip older than G80, inclusive. This includes the full GeForce 6 and 7 series as well as GeForce 8800GTX and first-gen 8800GTS. We are actively working on resolving this issue and will provide an update as soon as possible. The symptoms can include graphical corruption, performance issues, crashes and temporary hangs. The release should be perfectly safe to use with more recent cards than that," writes a NVIDIA Linux engineer in this forum thread.

Separately, if you're noticing weird clock frequencies reported by the NVIDIA Linux driver on GeForce 600 "Kepler" series hardware, you're not alone. In my testing last week of the NVIDIA GeForce GTX 680 Linux driver with their binary driver, I noticed that PowerMizer and the "GPU3DClockFreqs" attribute for their control extension were reporting the GK104 GPU operating at 705MHz for its core. The GTX 680 should be topping out at 1006MHz.

At first it looked like it might have been a video BIOS issue with the MSI GeForce GTX 680, but it was a retail card and yesterday I received a message from NVIDIA's Andy Ritger when he got to the bottom of the situation. Andy's message is below.
GPU clock management changed significantly with Kepler, and not all of that is correctly reflected in nvidia-settings, yet. At this point, I believe what you are seeing is strictly due to nvidia-settings reporting deficiencies, rather than the driver not taking proper advantage of the GPU clocks.

For a little more detail:

* On Kepler, select clock domains, such as what nvidia-settings calls "graphics", have a range of possible clock values per Performance Level, and the driver dynamically adjusts within the range of possible values per clock per Performance Level.

* I think what is getting reported in nvidia-settings (both in the PowerMizer page and GPU3DClockFreqs) is the minimum value of each range.

You can be confident that the clock is certainly not running below what is reported in nvidia-settings, and it is likely running above that.

We'll work to get nvidia-settings updated to correctly report clock information on Kepler.
So for any Kepler owners running the NVIDIA Linux driver, the graphics card should be running at the correct frequencies, it just might not be reported that way for now. Coming up tomorrow will be the long-awaited NVIDIA GeForce GTX 680 Linux benchmarks and review.

About The Author
Michael Larabel is the principal author of Phoronix.com and founded the web-site in 2004 with a focus on enriching the Linux hardware experience and being the largest web-site devoted to Linux hardware reviews, particularly for products relevant to Linux gamers and enthusiasts but also commonly reviewing servers/workstations and embedded Linux devices. Michael has written more than 10,000 articles covering the state of Linux hardware support, Linux performance, graphics hardware drivers, and other topics. Michael is also the lead developer of the Phoronix Test Suite, Phoromatic, and OpenBenchmarking.org automated testing software. He can be followed via and or contacted via .
Latest Linux Hardware Reviews
  1. Rosewill RS-MI-01: An Ultra Low-Cost Mini-ITX Chassis
  2. D-Link DCS-2330L HD Wireless Network Camera
  3. Gigabyte AM1M-S2H
  4. AMD's New Athlon/Semprons Give Old Phenom CPUs A Big Run For The Money
Latest Linux Articles
  1. AMD Catalyst 14.4 Brings Few Linux Performance Improvements
  2. The Performance Of Fedora 20 Updated
  3. Clang Fights GCC On AMD's Athlon AM1 APU With Jaguar Cores
  4. Ubuntu 14.04 LTS vs. Oracle Linux vs. CentOS vs. openSUSE
Latest Linux News
  1. Valve Is Bringing VOGL To Windows & Working On Regression Tests
  2. Canonical Is Taking Over Linux 3.13 Kernel Maintenance
  3. Google Web Designer Is Now Natively Available On Linux
  4. Ubuntu 14.10 Is Codenamed The Utopic Unicorn
  5. Audacious 3.5 Lightweight Audio Player Released
  6. Steam Updated For Ubuntu 14.04 LTS, SteamOS
  7. DNF 0.5 Yum Replacement Now Supports Groups
  8. Red Hat Enterprise Linux 7.0 Is Looking Fantastic
  9. Intel Is Launching An Interesting Bay Trail NUC Next Week
  10. Another X.Org EVoC Proposed For OpenGL 4+ Tests
  11. The Best Features Coming With Qt 5.3
  12. Red Hat's RHEL7 RC ISO Is Now Publicly Available
Latest Forum Discussions
  1. Linux Kernel Developers Fed Up With Ridiculous Bugs In Systemd
  2. The Most Amazing OpenGL Tech Demo In 64kb
  3. Announcing radeontop, a tool for viewing the GPU usage
  4. HTPC-upgrade advice: AMD Richland A8-7600 or Kaveri A10-6700T ???
  5. New card. Open source drivers only.
  6. The GNOME Foundation Is Running Short On Money
  7. Script for Fan Speed Control
  8. Torvalds Is Unconvinced By LTO'ing A Linux Kernel