QUOTE (coverup @ Aug 24 2005, 08:40 AM)
A jerky motion in tuxracer usually means that 3D accelaration does not work. It's easy to check. Open the terminal and run
CODE
glxinfo | grep direct
.
Sorry about the delay,
According to MCC hdwr, the video is:
SiS 325 2D/3D accelerator
location on bus 1::
type display-vga
in the monitor settings I have noticed that MDK setup likes to setup custom vesa for the default monitor setting instead of vga. Could this be a problem? Other than the games, everything seems normal.
message upon loading frozen bubble from console
Can't load '/usr/lib/perl5/vendor_perl/5.8.2/i386-linux-thread-multi/auto/SDL_perl/SDL_perl.so' for module SDL_perl: libGL.so.1: cannot handle TLS data at /usr/lib/perl5/5.8.3/i386-linux-thread-multi/DynaLoader.pm line 229.
at /usr/lib/perl5/vendor_perl/5.8.2/i386-linux-thread-multi/SDL.pm line 9
Compilation failed in require at /usr/lib/perl5/vendor_perl/5.8.2/i386-linux-thread-multi/SDL.pm line 9.
BEGIN failed--compilation aborted at /usr/lib/perl5/vendor_perl/5.8.2/i386-linux-thread-multi/SDL.pm line 9.
Compilation failed in require at /usr/games/frozen-bubble line 51.
BEGIN failed--compilation aborted at /usr/games/frozen-bubble line 51.
here is the output of glxinfo | grep direct
Xlib: extension "XFree86-DRI" missing on display ":0.0".
direct rendering: No
OpenGL renderer string: Mesa GLX Indirect
Thanks for any help