On Wed, 20 Nov 2002, Dieter Nützel wrote:
> >
> > It's _really_ really slow, though, reporting a frame rate of 1.95 - 2.0
> > fps or so when viewing the thing (whatever it is) head on.
>
> What do you get with LIBGL_DEBUG=verbose?
> glinfo?
GL_VERSION: 1.4 Mesa 5.0
GL_EXTENSIONS: GL_ARB_depth_texture GL_ARB_imaging GL_ARB_multisample
GL_ARB_multitexture GL_ARB_point_parameters GL_ARB_shadow
GL_ARB_shadow_ambient GL_ARB_texture_border_clamp
GL_ARB_texture_compression GL_ARB_texture_cube_map GL_ARB_texture_env_add
GL_ARB_texture_env_combine GL_ARB_texture_env_crossbar
GL_ARB_texture_env_dot3 GL_ARB_texture_mirrored_repeat
GL_ARB_transpose_matrix GL_ARB_window_pos GL_ATI_texture_mirror_once
GL_EXT_abgr GL_EXT_bgra GL_EXT_blend_color GL_EXT_blend_func_separate
GL_EXT_blend_logic_op GL_EXT_blend_minmax GL_EXT_blend_subtract
GL_EXT_clip_volume_hint GL_EXT_convolution GL_EXT_compiled_vertex_array
GL_EXT_fog_coord GL_EXT_histogram GL_EXT_multi_draw_arrays
GL_EXT_packed_pixels GL_EXT_paletted_texture GL_EXT_point_parameters
GL_EXT_polygon_offset GL_EXT_rescale_normal GL_EXT_secondary_color
GL_EXT_shadow_funcs GL_EXT_shared_texture_palette GL_EXT_stencil_wrap
GL_EXT_stencil_two_side GL_EXT_texture3D GL_EXT_texture_edge_clamp
GL_EXT_texture_env_add GL_EXT_texture_env_combine GL_EXT_texture_env_dot3
GL_EXT_texture_object GL_EXT_texture_lod_bias GL_EXT_vertex_array
GL_HP_occlusion_test GL_IBM_rasterpos_clip GL_IBM_texture_mirrored_repeat
GL_INGR_blend_func_separate GL_MESA_pack_invert GL_MESA_resize_buffers
GL_MESA_ycbcr_texture GL_MESA_window_pos GL_NV_blend_square
GL_NV_point_sprite GL_NV_texture_rectangle GL_NV_texgen_reflection
GL_NV_vertex_program GL_NV_vertex_program1_1 GL_SGI_color_matrix
GL_SGI_color_table GL_SGIS_generate_mipmap GL_SGIS_pixel_texture
GL_SGIS_texture_border_clamp GL_SGIS_texture_edge_clamp
GL_SGIX_depth_texture GL_SGIX_pixel_texture GL_SGIX_shadow
GL_SGIX_shadow_ambient
GL_RENDERER: Mesa X11
GL_VENDOR: Brian Paul
GLU_VERSION: 1.3
GLU_EXTENSIONS: GLU_EXT_nurbs_tessellator GLU_EXT_object_space_tess
GLUT_API_VERSION: 5
GLUT_XLIB_IMPLEMENTATION: 15
> Is DRI (glx/dri) really working?
Absolutely. Trust me, tuxracer isn't playable if DRI isn't working ;)
And interrupts etc are working:
CPU0 CPU1 CPU2 CPU3
22: 3104889 3131056 3084624 3136987 IO-APIC-level radeon@PCI:1:0:0
so everything looks fine.
> Didn't have commercial tuxracer but gears (MesaDemo, glxgears is the same)
> should run at ~2995 fps. I heard from over ~5000 fps with a Geforce4 4600 on
> a system like yours.
I've never gotten more than ~1700 fps on this system on glxgears. Oh,
well. I've never tried to bump AGPMode up from the default "1", though, so
it may be something simple like that.
Linus
-------------------------------------------------------
This SF.net email is sponsored by: The Sourceforge Network Survey
Take Our Survey and You Could Win a $500 Gift Certificate!
http://ugamsolutions.com/psurvey/osdn/SourceForge/index_sourceforge.htm
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
