Bug 708644

Summary: Cant run Doom 3 demo on nouveau driver
Product: [Fedora] Fedora Reporter: Rafael Louback Ferraz <ferrazrafael>
Component: mesaAssignee: Adam Jackson <ajax>
Status: CLOSED CANTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 15CC: damianatorrpm, frederik.hertzum
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-07-27 02:18:44 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Log from starting up doom3 none

Description Rafael Louback Ferraz 2011-05-28 14:52:01 UTC 
Im using nvidia M310 gpu, with nouveau driver provided on Fedora 15. My glxinfo shows direct rendering, but I cant start doom3 demo. 

OpenGL vendor string: nouveau
OpenGL renderer string: Gallium 0.4 on NVA8
OpenGL version string: 2.1 Mesa 7.11-devel
OpenGL shading language version string: 1.20

Doom report:

----- R_InitOpenGL -----
Setup X display connection
dlopen(libGL.so.1)
dlopen(libGL.so.1)
idRenderSystem::Shutdown()
signal caught: Segmentation fault
si_code 1
Was in fatal error shutdown: Unable to initialize OpenGL
Trying to exit gracefully..
Comment 1 Ben Skeggs 2011-06-02 01:04:59 UTC 
As far as I can see it doesn't even get as far as trying to load the nouveau 3D driver.  Not a clue if it's even a mesa bug, or something weird in the 32-bit multilib magic..
Comment 2 Rafael Louback Ferraz 2011-06-02 15:59:30 UTC 
I will try to install the full doom 3 and see if is there too. Maybe an update fixed that.
Comment 3 Damian Ivanov 2012-07-10 09:10:22 UTC 
This should be fixed by installing mesa-dri-drivers from Fedora
if you have ingame problems libtxc_dxtn is also a good idea (google it is not in official Fedora repos.
Comment 4 Rafael Louback Ferraz 2012-07-27 02:18:44 UTC 
still same thing in fedora 17, I installed mesa-dri-drivers (32 and 64 bits) and dxtn (from rpm fusion). Doesnt work, maybe a driver problem.
Comment 5 Frederik Hertzum 2013-06-08 18:58:46 UTC 
I am unable to start doom 3 on Fedora 18 x86_64 with the nouveau driver -- all relevant 32 bit libraries have been installed. The GPU I am using is a Geforce GT 640 (lspci | grep -i vga = 01:00.0 VGA compatible controller: NVIDIA Corporation GK107 [GeForce GT 640] (rev a1) )

doom3 complains that it cannot find a bunch of opengl extensions -- one of which (GL_ARB_vertex_buffer_object) glxgears (glxgears -info) claims is present.

after having searched the opengl extensions errors related to shader programs are reported in the style of 

glprogs/<filename>
GL_PROGRAM_ERROR_STRING_ARB: (null)
GL_PROGRAM_ERROR_POSITION_ARB < 0 with error

This happens for 16 files. doom3 tries to open two files (glprogs/arbVP_glasswarp.txt and glprogs/arbFP_glasswarp.txt), which is not found in any of the .pk4 fles of the game.

A warning then appears about vertex array range being in virtual memory which is slow, followed by a caught seg fault and a graceful exit.

libtxc_dxtn 32 and 64 bit libraries have been installed.
Comment 6 Frederik Hertzum 2013-06-08 18:59:16 UTC 
Created attachment 758620 [details]
Log from starting up doom3
Comment 7 Frederik Hertzum 2013-06-08 19:08:18 UTC 
The bug is caused by the bundled libstdc++.so.6 file -- simply removing it will fix the seg fault and doom3 will start as it supposed to (this will also require removing the libgcc_s.so.1 file as well since /lib/libstdc++.so.6 will take over and this requires libgcc_s.so.1 version GCC_4.2.0).