I tried installing the new ati binary drivers, and every game, except Enemy
Territory hard locks on start-up. I can, however, alt-ctrl-backspace back to
the console, so it's not the end of the world.
I initially though it was an issue with the ati drivers, but when I reverted
to the DRI
On Thursday 01 January 2004 08:41, Michel Dnzer wrote:
Nor is it a hard lock. :) Can you also log in remotely and kill the
game? What about glxgears, does it also lock up? Can you close the
window? ...
I haven't tried to log in remotely, but I can alt-ctrl-f2 to a console and
kill the
I've recently upgraded to mandrake 9.1, and have since been unable to load the
radeon.o module when I've compiled it from the source. I'm using the same
compiler for the module as for the kernel (gcc 3.2).
Here's the output:
radeon.o: unresolved symbol mmu_cr4_features
I have high-mem
DUDE! I was wondering what the environment variable was!!!
Thanks a million!
On Mon, 24 Mar 2003 04:39 pm, Ian Romanick wrote:
MichaelM wrote:
GLX extensions:
GLX_ARB_get_proc_address, GLX_EXT_import_context,
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_agp_offset
Hi.
I've recently bought an ATI radeon 9100 pro. I've installed, played around
with it, and have noticed something strange. Though I can play 3d games such
as UT and quake3 with excellent frame-rates, running something like gears
will only get me 80 FPS.
What's up with that? I'm currently
I just checked the logs, and there was no such message, even though what you
descibed seems the most logical reason.
The problem doesn't bother me (i can play games now =) ), but the fact that's
its there may be of concern for others ...
On Sat, 22 Mar 2003 01:30 pm, you wrote:
MichaelM wrote
extensions:
GLU_EXT_nurbs_tessellator, GLU_EXT_object_space_tess
On Sat, 22 Mar 2003 01:43 pm, you wrote:
On Sat, Mar 22, 2003 at 01:25:36PM +, MichaelM wrote:
Hi.
I've recently bought an ATI radeon 9100 pro. I've installed, played
around with it, and have noticed something strange. Though I
() from /lib/libc.so.6
On Sat, 22 Mar 2003 01:56 pm, you wrote:
MichaelM wrote:
Here they are:
CPU0
0:1972383 XT-PIC timer
1: 35769 XT-PIC keyboard
2: 0 XT-PIC cascade
3:2729881 XT-PIC serial
4
Hi.
I recently updated to the current CVS, and now I get hard locks with my
G400 (thus far on Return to Castle WOlfenstein, haven't tested
others...). An old backup I have (from the older X 4.1.x version) works
fine.
I'm using linux-2.4.17 on Mandrake 8.0. My motherboard is an Asus A7V133A.
Busjahn
MichaelM wrote:
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
Hi. I recently updated my version to the current tree (recently updated
to Mesa 4.0), and DRI no longer works. I'm using a 16MB G400, along with
kernel 2.4.17.
I ran glxinfo with the LIBGL_DEBUG=verbose and this is the output I got:
libGL: XF86DRIGetClientDriverName: 1.1.0 mga (screen 0)
Would you consider it a good ideato make DRI
part of the sourceof a kernel?Direct 3d graphicssupported from
theboot sequence.
I'm really concerned about your answer. There was a
whole thread on the linux-kernel mailing list about the hypothesis of the
release of an X-Kernel, a kernel which
12 matches
Mail list logo
