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

Will Mesa/Gallium3D Work With The Open-Source Doom 3?

Michael Larabel

Published on 17 November 2011
Written by Michael Larabel
Page 2 of 7 - 42 Comments

For those NVIDIA GeForce and ATI/AMD Radeon users using the vendor's respective proprietary Linux drivers, there shouldn't be any issue in handling Doom 3 / id Tech 4. On the ATI side I remember running Doom 3 easily on a Radeon X800XL 256MB back in the day along with a GeForce 6600GT on the NVIDIA side. With the current Catalyst driver only supporting the Radeon HD 2000 series and newer, anything that is running with the Catalyst driver in 2011 should be able to run Doom 3. On the NVIDIA side, their mainline binary driver supports the GeForce 6 series and newer, so there you should be set too. Any modern graphics card with the proprietary Linux drivers will likely be CPU-bound. The binary drivers deliver Doom 3 results that are much faster and more visually advanced than what is illustrated in this article, so the binary drivers are not the focus of this article.


Using Mesa/Gallium3D drivers for rendering Doom 3 can work, but the image quality doesn't match the proprietary Linux graphics drivers.

First to be tested was the integrated Intel HD 3000 graphics from the Core i5 Sandy Bridge. While Intel has had seven years to advance their Linux graphics driver since the release of Doom 3, the latest Mesa driver code still is not perfect. Running Doom 3 in a stock driver configuration for the Intel Linux graphics under Sandy Bridge caused issues. There were multiple times where the system would hang and there would be visible memory corruption to varying extents.

There were also times there would not be frame-buffer corruption, but the Sandy Bridge graphics processor would be hung and then restarted by Intel's DRM kernel driver (as reported by dmesg). Sometimes there would be the GPU being hung twice, which was not gracefully recovered.

In the end, however, I did manage to get some Sandy Bridge performance numbers from Doom 3 on the Linux 3.2 kernel and with Mesa 7.12-devel.

Latest Linux Hardware Reviews
  1. Mini-Box M350: A Simple, Affordable Mini-ITX Case
  2. Overclocking The AMD AM1 Athlon & Sempron APUs
  3. AMD Athlon 5350 / 5150 & Sempron 3850 / 2650
  4. Upgraded Kernel & Mesa Yield A Big Boost For Athlon R3 Graphics
Latest Linux Articles
  1. A Quick Look At GCC 4.9 vs. LLVM Clang 3.5
  2. Are AMD Athlon/Sempron APUs Fast Enough For Steam On Linux?
  3. AMD Athlon's R3 Graphics: RadeonSI Gallium3D vs. Catalyst
  4. GCC 4.9 Compiler Optimization Benchmarks For Faster Binaries
Latest Linux News
  1. R600 Gallium3D Disables LLVM Back-End By Default
  2. Fedora 21 Gets GNOME 3.12, PHP 5.6, Mono 3.4
  3. Fedora Workstation Is Making Me Quite Excited
  4. Maynard: A Lightweight Wayland Desktop
  5. Chromium Browser Going Through Growing Pains In Ubuntu 14.04
  6. KDE 4.13 Is Being Released Today With New Features
  7. Trying Out Radeon R9 290 Graphics On Open-Source
  8. Intel Broadwell GT3 Graphics Have Dual BSD Rings
  9. Early Linux 3.15 Benchmarks Of Intel Core i7 + Radeon
  10. Red Hat Releases Its RHEL 7 Release Candidate
  11. New Features Coming To Xubuntu 14.04 LTS
  12. NVIDIA Officially Releases CUDA 6
Latest Forum Discussions
  1. The GNOME Foundation Is Running Short On Money
  2. Updated and Optimized Ubuntu Free Graphics Drivers
  3. Linux Kernel Developers Fed Up With Ridiculous Bugs In Systemd
  4. Change installation destination from home directory
  5. After Jack Keane, RuseSoft will briing Ankh 3 to Linux through Desura
  6. Bye bye BSD, Hello Linux: A Sys Admin's Story
  7. New tool for undervolt/overclock AMD K8L and K10 processors
  8. How to enable opengl 3.3 on r9 270?