Please attach your xorg log, dmesg output, and glxinfo output.  Also, are you running a 64 bit distro and is wolfenstein enemy territory a 32 bit app?  If so, you may need to upgrade the 32 bit version of your 3D driver.

Created attachment 50397 [details]
the xorg log

Created attachment 50398 [details]
my dmesg

Created attachment 50399 [details]
glxinfo > glxinfo

(In reply to comment #1)
> Please attach your xorg log, dmesg output, and glxinfo output.

see attachment

>  Also, are you
> running a 64 bit distro and is wolfenstein enemy territory a 32 bit app?

yes I'm running amd64 Debian Sid and ET is a 32 bit app

>  If so, you may need to upgrade the 32 bit version of your 3D driver.

ok, (I know this is distro related but perhaps you know this too)

as I'm using the libgl1-mesa-{dri,glx} packages, I don't see any package
relative to ia32 arch in my package repository list...
for nvidia I have libgl1-nvidia-glx-ia32 (I have a radeon just for listing).

I have no id about updating my 32 bit version of the 3d driver.
all the files in libgl1-mesa-{dri,glx} are in /usr/lib64 or 
/usr/lib/x86_64-linux-gnu/dri

do you know where I could find the 32bit ones? ( they exists as the app
is about to run...)

As I could'nt stop playing my favorite game, I reinstalled the fglrx
proprietary driver in order too show you my output logs. I blacklisted the
fglrx.ko module, loaded the radeon.ko changed my xorg.conf and did an update-
alternative for glx.
The problem now is when I run ET, the game crash just after the introduction
scene, here is the error in the console:

X Error of failed request: GLXBadRenderRequest
  Major opcode of failed request: 153
  Minor opcode of failed request: 1
  Serial number of failed request: 4872

sorry for not beeing able to reproduce the texture bug....
should I open a new bug report and close this one?

(In reply to comment #5)
> as I'm using the libgl1-mesa-{dri,glx} packages, I don't see any package
> relative to ia32 arch in my package repository list...

The 32 bit drivers are in the ia32-libs package, but they tend to be outdated. This should get better in the future with multiarch, which will allow installing the 32 bit libgl1-mesa-dri package directly. In the meantime, I'm afraid you'll have to build the driver yourself from the upstream Mesa Git 7.11 branch.


> As I could'nt stop playing my favorite game, I reinstalled the fglrx
> proprietary driver in order too show you my output logs. I blacklisted the
> fglrx.ko module, loaded the radeon.ko changed my xorg.conf and did an update-
> alternative for glx.
> The problem now is when I run ET, the game crash just after the introduction
> scene, here is the error in the console:
> 
> X Error of failed request: GLXBadRenderRequest
>   Major opcode of failed request: 153
>   Minor opcode of failed request: 1
>   Serial number of failed request: 4872

Something from fglrx is probably still interfering.

Can you test again with a newer version of mesa?
In the meantime debian has mesa-8.0.4 in sid and testing.

Created attachment 68363 [details]
my glxinfo output with mesa 8.0.4

Hi,

I updated my Debian Sid distro to mesa 8.0.4
unfortunately, Enemy Territory continue to have
- texture blinking
- error in drawing landscapes (I can see thru the walls)
- many objects (all the screen when enterring limbo menu)
appearing only a fraction of second then disappearing

Tell me if I can do any testing or provide some more log
to help diagnose the pb.

(In reply to comment #8)
> my glxinfo output with mesa 8.0.4

That's actually a post-8.0 Git snapshot...

Did you sort out the 32 vs. 64 bit issues?

yes, using Debian Sid, the libgl1-mesa-* package are multi-arch ready.
dpkg -L libgl1-mesa-glx:i386
shows:
.
/usr/lib/i386-linux-gnu/libGL.so.1.2
.
.
.

I have installed the libtxc-dxtn-s2tc0 both x86_64 and i386
I suppose Enemy Territory would complain if 32bit libGL was
not installed.
However, using wine on simple win32 opengGL binary demo
http://freewebs.com/mannymax/cpp/GLTest.exe
I get:
err:winediag:X11DRV_WineGL_InitOpenglInfo Direct rendering is disabled, most likely your OpenGL drivers haven't been installed correctly (using GL renderer "Gallium 0.4 on AMD RV770", version "1.4 (2.1 Mesa 8.0.4)").
Despite the above error, the demo run (I see a multicolor pyramyd and cube,
moving)

I don't know what to think, wine is reporting Gallium and Mesa 8.0.4...

(In reply to comment #11)
> err:winediag:X11DRV_WineGL_InitOpenglInfo Direct rendering is disabled, most
> likely your OpenGL drivers haven't been installed correctly (using GL
> renderer "Gallium 0.4 on AMD RV770", version "1.4 (2.1 Mesa 8.0.4)").

Did you install libgl1-mesa-dri:i386?

yes it's installed

Okay, but I still wonder why Wine ends up with indirect rendering, and if that's the case for ET as well.

Can you see if running with the environment variable LIBGL_DEBUG=verbose gives any hints for either, and attach the terminal output from ET?

Sorry for the late reply, I was off last week.

after settings LIBGL_DEBUG=verbose
it appears I had in my environment a
LIBGL_DRIVERS_PATH=/opt/mesa/ pointing
on an old build of mesa tree.

Enemy Territory work like a charm.
close this (non-)bug 
I'm sorry for the noise....

Thank you for support

PS: wine work perfectly
PS2: I will continue testing games and try
to make usefull report this time...