On Tuesday May 21 2002 7:42 pm, Patrick wrote:
OK, Howard, let me see if I can be of some help then. If you are running the Radeon QD, then that will be pretty close to my 7200 Radeon as it is a QD also. SuSE 8 installed quite nicely with my card and the only thing missing was the DRI files to activate 3D for me. I installed those files from the 7.3 XFree86 files in the DRI folder, run /sbin/SuSEconfig afterwards and all was fixed. Now I did notice that the actual 3D did not get started until I restarted X, but it is working as well as it did with 7.3, well actually better.
Have you checked the DRI files to see if they are installed? You can do rpm -qa | grep xf86 in a console/shell to get the complete list. It should show you the same as mine: xf86_glx-4.2.0-107 xf86_3x-3.3.6-375 xf86tools-0.1-221 xf86glx-devel-4.2.0-64 xf86-4.2.0-107 You might have different build numbers, but they all should be there for 3d to work. You might also want to check your libGL.so.1 library to make sure it is linked to the xf86_glx and not mesa. You can check this by ls -l /usr/lib/libGL.so.1 in a shell.
Well I finally found some time to work on this again and here are the results. I really appreciate all of you helping. I have everything you list there with the same numbers except for the xf86glx-devel-4.2.0-64. I checked the link and it was correctly linked.
Once you have determined what you have installed and where everything is pointing, then you can actually edit your XFree86.config file to add 3D or you might want to rename the present file to .old before running sax2 again. I know I ran into problems when trying to run sax2 with a corrupted config file, so just deleted, moved or renamed it, so sax2 could start fresh. Be sure to run sax2 in run level 3 and not 5 though as I have always had problems doing that.
If you are booted into KDE, then open a shell and type as root, rcxdm stop, which will take you out of X and into the console mode (run level 3) where you will log in as root to run sax2 -m 0=radeon. This should allow you to setup XF86 again and get 3D started.
I did this and it appears I still have something wrong. Here's what I get when I run Armagetron for example: (/usr/games/armagetron) NUM_AIS changed from 1 to 4. ZTRICK changed from 1 to 0. WRAP_MENU changed from 0 to 1. DITHER changed from 1 to 0. HIGH_RIM changed from 1 to 0. FLOOR_DETAIL changed from 2 to 1. TEXT_OUT changed from 0 to 1. ALPHA_BLEND changed from 1 to 0. PERSP_CORRECT changed from 0 to -1. POLY_ANITALIAS changed from 0 to -1. LINE_ANITALIAS changed from 0 to -1. GL_VENDOR changed from to Brian Paul. GL_RENDERER changed from to Mesa X11. GL_VERSION changed from to 1.3 Mesa 4.0.1. GL_EXTENSIONS changed from to GL_ARB_imaging GL_ARB_multisample GL_ARB_multitexture 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_dot3 GL_ARB_texture_mirrored_repeat GL_ARB_transpose_matrix 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_packed_pixels GL_EXT_paletted_texture GL_EXT_point_parameters GL_EXT_polygon_offset GL_EXT_rescale_normal GL_EXT_secondary_color GL_EXT_shared_texture_palette GL_EXT_stencil_wrap 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_INGR_blend_func_separate GL_MESA_resize_buffers GL_MESA_window_pos GL_NV_blend_sqtòÿ¿@. TEXTURE_MODE_3 changed from 0 to 9728. TEXTURE_MODE_2 changed from 0 to 9984. TEXTURE_MODE_1 changed from 0 to -1. TEXTURE_MODE_0 changed from 0 to -1. SOFTWARE_RENDERER changed from 0 to 1. LAST_FULLSCREEN changed from 1 to 0. FIRST_USE changed from 1 to 0. Xlib: connection to ":0.0" refused by server Xlib: Invalid XDM-AUTHORIZATION-1 key (failed key comparison) Xlib: connection to ":0.0" refused by server Xlib: Invalid XDM-AUTHORIZATION-1 key (failed key comparison) Couldn't set video mode: Couldn't set video mode: Couldn't set video mode: Couldn't set video mode: Couldn't set video mode: Couldn't set video mode: Couldn't set video mode: Couldn't set video mode: Couldn't set video mode: Couldn't set video mode: Fatal signal: Segmentation Fault (SDL Parachute Deployed) There are two lines above that appear to have something to do with rights, "XDM-AUTHORIZATION-1 key" do you know what that is all about? --- See Ya' Howard Coles Jr. John 3:16!