For what it's worth, a quick and dirty command that would tell if there are
any nvidia or ati module loaded:
lsmod | egrep -cw fglrx|nvidia
That would work on some configurations but I don't know if that would be the
case on most or all systems.
HTH
--
To UNSUBSCRIBE, email to [EMAIL
On Thu, 2008-10-09 at 17:26 -0400, Andres Mejia wrote:
Hello Debian X Strike Force. There's a bug in warsow that according to the
Warsow developers, is due to a buggy driver.
I can reproduce this bug with a machine using a mesa driver, but on a machine
with the proprietary nvidia drivers,
--- Michel Dänzer [EMAIL PROTECTED] schrieb am Fr, 10.10.2008:
Does it still happen with libgl1-mesa-dri 7.2-1 from
experimental? If so, it would be good to make sure this
is reported in upstream bugzilla (preferably after first
confirming it isn't fixed in upstream Git either).
I got word
--- hangy [EMAIL PROTECTED] schrieb am Fr, 10.10.2008:
A user could simply disable GLSL completely in config.cfg:
seta gl_ext_GLSL 1
Sorry, setting it to 1 obviously enables GLSL functionality,
setting it to 0 disables it.
-hangy
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a
Here's a new warsow script that could help, but it will disable GLSL
regardless of what driver is being used. What could we use to tell if
we're using the proprietary ATI or Nvidia drivers?
On Fri, Oct 10, 2008 at 12:09 PM, 01 [EMAIL PROTECTED] wrote:
Yup, starting the game with...
warsow
Hello Debian X Strike Force. There's a bug in warsow that according to the
Warsow developers, is due to a buggy driver.
I can reproduce this bug with a machine using a mesa driver, but on a machine
with the proprietary nvidia drivers, I can't reproduce this bug.
On Wednesday 08 October 2008
Hi,
warsow_bin: shader/slang/slang_emit.c:978: emit_move:
Assertion
`n-Children[0]-Store-Index = 0' failed.
according to our coders, this assertion indicates a driver bug. Was the Mesa
OpenGL driver updated recently? It might be a good idea to contact one of their
maintainers/coders.
Hello Debian X Strike Force. There's a bug in warsow that according to the
Warsow developers, is due to a buggy driver.
I can reproduce this bug with a machine using a mesa driver, but on a machine
with the proprietary nvidia drivers, I can't reproduce this bug.
On Wednesday 08 October 2008
8 matches
Mail list logo
