[Dri-users] Re: [Dri-devel] Savage: integrated driver

[Felix <fx...@gm...>]

On Sun, 8 Feb 2004 17:17:10 +0100
George Lengel <le...@co...> wrote:

> Hi,
> 
> I built the module with the -f flag which made the difference. I copied it to 
> my modules directory in my kernel tree and then did a modprobe savage. Then I 
> killed X and restarted it. My XFRee86.0.log shows
> 
> (II) SAVAGE(0): [junkers]       sarea_priv_offset:0x00000898
> (II) SAVAGE(0): Direct rendering enabled
> (==) RandR enabled

Looks good so far.

> 
> but if I run 'glxinfo' I get
> 
> name of display: :0.0
> display: :0  screen: 0
> direct rendering: No
> 
> 'glxgears gives me between 200 and 225 FPS when I run it. Is there something 
> else I can run to see if I do have hardware 3D or not?

"direct rendering: No" means hardware 3D is not working. Try running
glxgears with the environment variable LIBGL_DEBUG set to verbose. In
bash you can use this command line:

LIBGL_DEBUG=verbose glxgears.

The output should give some clue to what's going wrong.

> 
> There is a problem with the driver. My terminals (accessed by CTRL-ALT-F*) are 
> all corrupted. It is like there are four columns of text across the screen 
> each one with only  a part of each letter. I did not see this with the 
> 1.1.27t version I got from http://www.probo.com/timr/savage40.html.

This is a known problem whith Alex's new 2D driver you downloaded. He
warned us that it's experimental. ;-)

Regards,
  Felix