I am filing this bug in relation to the demo version of the game Enemy Territory: Quake Wars. Hardware is an ATI Radeon 9800Pro 128Mb. Running kernel 2.6.31 Using the Mesa 7.6 git snapshot from the 17th August 2009 (which is the default in Ubuntu 9.10 beta) this game loads successfully and I am able to access the menu, create/select a user, and change the various configuration options. Opening the in-game console at this point shows that it is using the recently added GL_ARB_occlusion_query (the lack of which previously prevented this game from working on Radeons) along with the recently added GL_ARB_vertex_buffer_object. There are also various errors. Launching a match against the computer causes the game to crash to it's console with further errors, after which I can type "quit" to exit the game and return to my desktop. After upgrading to the final release of Mesa 7.6, the game now crashes to a black screen immediately after launch (no menu loads), locking my system. At this point the keyboard does not respond (not even CTRL-ALT-DEL), and I have to manually power off.
can you use git bisect to find the change that broke it? You might also try the 7.6 branch as there have been several fixes since 7.6 was released.
I meant to mention that the ATI Radeon 9800Pro 128Mb is an R350, although everybody probably knows that. Also meant to mention the KMS is off. Also, when I said "the game now crashes to a black screen" I should have said "a blank screen", as my monitor powers off. I have no idea how to use git bisect - can you point me to a site with details on that? Checking out the latest 7.6 branch sounds easier, but I think the easiest thing to try first is to wait a couple more days for the Ubuntu 9.10 "Karmic Koala" RC (have completely broken my filesystem) and then apply the xorg-edgers PPA, which has Mesa 7.7.0~git20091020.cbd20e18-0ubuntu0tormod + libdrm - 2.4.15~git-0ubuntu0tormod + xserver-xorg-video-ati - 1:6.12.99+git20091019.bd89b750-0ubuntu0tormod. Will get back to you then.
Since my last post I have found the Ubuntu “X Updates” PPA, which currently contains mesa - 7.6.1~git20091017.3594b53c-0ubuntu0~xup~1 I decide to give this a try before doing anything else. I am still getting the blank screen. Details of this package are: * Checkout from git 20091017 (mesa_7_6_branch branch) up to commit 3594b53c0173ac810106f667604bf94b5cfc4a1e * Copy in debian/ tree from karmic 7.6.0-1ubuntu4 and disable patches 108 and 110 (applied upstream) but keep patch 109 (which reverts 284a7af2, fdo #24131)
fwiw r600 git doesn't work either, it lacks GL_ARB_occlusion_query at detection time
@ Paul Heldens - I think you have a different bug/missing feature. My R350 was definitely using GL_ARB_occlusion_query, as mentioned in my original description. If I recall correctly, R600-R700 use a different code path than R300-R500. However it seems you are in luck - on the 28th October 2009 commit 660acd60d00366c97fbe7caf3995a75ce935a19b landed in git master, with the title "r600: add occlusion query support". @ Alex Deucher - I have cloned git master and figured out how to use bisect, once I figure out the compilation and install I'll test and get back to you.
It's working again with the Ubuntu “X Updates” PPA containing mesa - 7.6.1~git20091118.fe5c4654-0ubuntu0-xup~1 Details of this package are: * Checkout from git 20091118 (mesa_7_6_branch branch) up to commit fe5c46546e740a16a13fe9e8aaa4b071bc13d70b * Copy in debian/ tree from karmic 7.6.0-1ubuntu4 and disable patches 108, 109 and 110 (applied upstream) * Drop 05_hurd-ftbfs.diff (fails and is not useful here) * + Add --with-dri-searchpath (LP: #248392) I'm still not able to actually launch a game, but the menus are available and working again, and it only crashes to the in-game console, after which I can type "quit" to exit the game and return to my desktop. The game is also still using GL_ARB_occlusion_query and GL_ARB_vertex_buffer_object. I never was able to use git bisect to find the change that broke it, but it's working now. I consider this bug fixed.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.