![](https://seccdn.libravatar.org/avatar/98a99ec06421e9c7299f284a0d1fba6e.jpg?s=120&d=mm&r=g)
Well, one thing is not right... the version of xf86-4.2.0 should be 107, not 64. I wonder if there is a slightly compatibility issue. As for Kevin's email, I was commenting about the frame rates. The hardware acceleration should work (windowed or full screen.) Judging by the frame rates that were reported, one could assume that 300 frames per second in a small window is not accelerated. I get 1400 fps in a window and roughly 240 at full screen. - Herman On Tue, 13 Aug 2002, Thom Nuzum wrote: -> ->Below are the 2 outputs: Incidentally a SAX configuration causes a crash where ->YAst2 does not. Thanks Again -> ->thom@linux:~> rpm -qa|grep -i xf86 ->xf86_glx-4.2.0-107 ->xf86-4.2.0-64 ->xf86_3x-3.3.6-375 ->xf86tools-0.1-221 -> ->thom@linux:~> 3Ddiag ->3Ddiag version 0.397 ->Verifying 3D configuration: ->Using 3dinfo ->************************************************************ -> ->Verifying 3D configuration based on XFree86 4 for 3D board ->"ATI Technologies Inc Radeon VE (1002@5159)": -> ->Tests for package "xf86_glx": -> package ... done. -> package files ... done. -> ->Tests for correct OpenGL libraries/GLX extensions: -> Symbolic Links ... done. -> /etc/sysconfig/3ddiag (SCRIPT_3D=switch2xf86_glx) ... done. -> ->Test for correct XFree86 version ... done. -> ->Tests for XFree86 configuration: -> Config File /etc/X11/XF86Config ... done. -> Driver ... done. -> Color Depth ... done. -> Extensions ... done. -> Options ... done. -> ->----------------------- NOTE ----------------------------------- ->If 3D hardware OpenGL configuration is not stable enough, you ->should switch back to 'Mesa Software Rendering'. You can ->verify this configuration with the command "3Ddiag --mesasoft". ->----------------------- NOTE ----------------------------------- -> ->Checking GLU/glut runtime configuration: -> GLU ... done (package mesaglu) -> glut ... done (package mesaglut) -> ->thom@linux:~> -> -> -> ->