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. ZFS On Linux 0.6.4.2 Brings Linux 4.1 Support, Fixes
  2. Old Net Burst Tests, Ubuntu Phone & Assembly x86 Were Popular Topics Last Month
  3. Qt 5.5 Officially Released
  4. Global Shortcuts In KDE Plasma Under Wayland
  5. LLVMpipe FP64 Support Knocks Off Some GL4 Extensions
  6. Dell Gets An Airplane Mode Switch Driver In Linux 4.2
  7. I Gave Up Waiting On The Water-Cooled Radeon R9 Fury X
  8. NVIDIA Tegra X1 Chromebooks Appear Closer, Support Added To Coreboot
  9. Pinos Is For Linux Video What PulseAudio Is For Audio
  10. Crossing 200,000 Benchmark Results Posted On LinuxBenchmarking.com
Latest Articles & Reviews
  1. How KDE VDG Is Trying To Make Open-Source Software Beautiful
  2. Attempting To Try Out BCache On The Linux 4.1 Kernel
  3. CompuLab's Fitlet Is A Very Tiny, Fanless, Linux PC With AMD A10 Micro
  4. AMD A10-7870K Godavari: RadeonSI Gallium3D vs. Catalyst Linux Drivers
Most Viewed News This Week
  1. Kubuntu 15.10 Could Be The End Of The Road
  2. NVIDIA Starts Supplying Open-Source Hardware Reference Headers
  3. KDBUS Won't Be Pushed Until The Linux 4.3 Kernel
  4. The Staging Pull For Linux 4.2: "Big, Really Big"
  5. The State & Complications Of Porting The Unity Editor To Linux
  6. SteamOS "Brewmaster" Is Valve's New Debian 8.1 Based Version
  7. Jonathan Riddell Steps Down From The Kubuntu Council
  8. ARM Posts Pictures Of AMD's New Development Board