В сообщении от 17 Сентябрь 2003 19:40 Alex Deucher написал:
> I don't think the drivers S3 released will work properly on savage3D
> based cores like the MX/IX chips. They were designed for savage4 cores
> like the prosavage and twister. You may want to compare the S3 driver
> to the utah-glx sav
В сообщении от 17 Сентябрь 2003 19:16 Rafael Maximo написал:
> I'm getting a similar problem on my xfree86 4.3.0, the 2D screen is
> corrupted but it looks better than yours :)
the screen corruption represented on my screenshot happens only whith
enlightenment window manager other WMs haven't th
I don't think the drivers S3 released will work properly on savage3D
based cores like the MX/IX chips. They were designed for savage4 cores
like the prosavage and twister. You may want to compare the S3 driver
to the utah-glx savage driver. the utah driver only supports savage3D
cores, but not s
I'm getting a similar problem on my xfree86 4.3.0, the 2D screen is
corrupted but it looks better than yours :) but here glxinfo reports Direct
Rendering disable. Your XFree86 log shows something not good:
(--) SAVAGEInitMC: There is no enough memory!
Someone also reported a similar problem usin
В сообщении от 17 Сентябрь 2003 16:44 Dimitry N. Naldaev написал:
I'v practicaly duplicateded message of Rick Harris two week ago
Sorry
> After that I force init DRI by doing
>
[ snip ]
>
> but when I start glxgears Xserver crashes
> full X log also attached
| (--) SAVAGE(0): SavageMatchBiosM
