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 Benchmarking Platform
Phoromatic Test Orchestration

Running The NVIDIA GeForce GTX 680 On An Open-Source Driver

Michael Larabel

Published on 26 April 2012
Written by Michael Larabel
Page 1 of 4 - 13 Comments

Thanks to clean-room reverse-engineering, it is already possible to run the NVIDIA GeForce GTX 680 "Kepler" graphics card on a fully open-source graphics driver complete with OpenGL acceleration. Here are the first benchmarks of this work-in-progress, community-created open-source GeForce 600 series graphics driver.

As mentioned on the NVIDIA GeForce GTX 680 launch-day back in March, the Nouveau project that seeks to clean-room reverse-engineer the closed-source NVIDIA driver in order to write an open-source alternative, had a huge set of surprises. Two of the Nouveau developers managed to get their hands on two GeForce GTX 680 graphics cards before launch. As a result, and since the NVIDIA driver changes from the GeForce 400/500 "Fermi" to GeForce 600 "Kepler" series were not too invasive, they managed same-day open-source driver support.

The Nouveau developers already merged their Kepler driver changes into the Linux kernel and then once the Nouveau libdrm re-write landed in mid-April, they merged their Nouveau Kepler Gallium3D code. This published code already allows for OpenGL 2.1 acceleration on Kepler graphics processors with this fully open-source driver, but there is still a lot of work left.

Like the other GeForce hardware on the Nouveau driver, the developers still working out proper re-clocking support, proper power/fan management, OpenGL 3.0+ support, merging OpenCL, etc. Additionally, the open-source Kepler support currently requires closed-source firmware for operation. In order to obtain this Kepler firmware/microcode, the official NVIDIA Linux driver must first be loaded on the hardware while running MMIOtrace within the Linux kernel to trace register writes, following by dumping the traces back into certain files in order to come up with this "FUC" microcode. This is a temporary issue and in a future Linux kernel release there should be a better solution, similar to the initial Nouveau Fermi FUC microcode situation.

Latest Articles & Reviews
  1. Radeon Linux Benchmarks: Catalyst 15.3 Beta vs. Linux 4.0 + Mesa 10.6-devel
  2. Trying Out The Modern Linux Desktops With 4 Monitors + AMD/NVIDIA Graphics
  3. Turning A Basement Into A Big Linux Server Room
  4. NVIDIA's $1000+ GeForce GTX TITAN X Delivers Maximum Linux Performance
  5. OS X 10.10 vs. Ubuntu 15.04 vs. Fedora 21 Tests: Linux Sweeps The Board
  6. The New Place Where Linux Code Is Constantly Being Benchmarked
Latest Linux News
  1. Debian 8.0 Jessie Gets A Release Date
  2. Firefox 37 Coming Today With Heartbeat, HTTPS Bing
  3. OpenIndiana 2015.03 Updates Its Solaris/Illumos Environment
  4. GNOME 3.16 SDK Runtime Now Available
  5. Initial Intel Braxton Support Might Come To Linux 4.1
  6. Why KDE's KWin Doesn't Integrate Weston/QtCompositor For Wayland Support
  7. Clang Now Supports Targeting The NaCl OS
  8. PC-BSD Updates Its Lumina Desktop (v0.8.3)
  9. Fedora 22 Alpha Now Available For AArch64 & PowerPC64
  10. Systemd Developers Did NOT Fork The Linux Kernel
Most Viewed News This Week
  1. The Big Features Of The Linux 4.0 Kernel
  2. Improved OpenCL Support For Blender's Cycles Renderer
  3. Open-Source Driver Fans Will Love NVIDIA's New OpenGL Demo
  4. Allwinner Continues Jerking Around The Open-Source Community
  5. GNOME 3.16 Released: It's Their Best Release Yet
  6. Ubuntu 15.04 Final Beta Released
  7. Nuclide: Facebook's New Unified IDE
  8. LibreOffice Online: A Cloud Version Of LibreOffice