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

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 News
  1. Phoronix Test Suite 5.8 Milestone 5 Brings Near Final "Belev" Experience
  2. For AMD Users, Linux 4.2 Will Bring The New AMDGPU Driver & VCE1 For Radeon
  3. Atomic Mode-Setting Still Baking For Samsung's Exynos DRM Driver
  4. Ubuntu Phone Update This Month Brings Many Improvements
  5. Fedora's "Fedup" To Be Replaced In Fedora 23
  6. Android M Should Bring Greater Performance & Efficiency
  7. AMD Teases Upcoming Radeon "Fiji" GPU Launch
  8. Dell Makes An Ubuntu Installation Guide, Suggests Users Try It Out
  9. Running Linux On The Intel Compute Stick
  10. AMD Launches The A10-7870K "Godavari" APU
Latest Articles & Reviews
  1. Opening The Gates To Our Daily Open-Source Linux Benchmark Results
  2. The Latest Features For Linux Performance Management + Benchmark Monitoring
  3. Noctua NH-U12DX i4 + NF-F12
  4. Btrfs RAID 0/1 Benchmarks On The Linux 4.1 Kernel
Most Viewed News This Week
  1. NVIDIA's Proprietary Driver Is Moving Closer With Kernel Mode-Setting
  2. Zapcc Claims To Be A "Much Faster C++ Compiler"
  3. OpenWRT 15.05 Preparing Improved Security & Better Networking
  4. Features Added To Mesa 10.6 For Open-Source GPU Drivers
  5. Ubuntu's LXD vs. KVM For The Linux Cloud
  6. The Latest Linux Kernel Git Code Fixes The EXT4 RAID0 Corruption Problem
  7. Friction Building Around An Ubuntu Community Council Decision
  8. Fedora 22 Is Being Released Next Tuesday