I had similar DRI issue due the following things: 1. Have to load agpgart and the module that corresponds to your agp chipset (For instance on my Gigabyte K8NS Ultra 939 m/b I need agpgart and amd64_agp modules loaded) You'll need to check your hardware for the right modules
2. the XF86Config-4/xorg.conf should have the following setting changed: from: Option "UseInternalAGPGART" "yes" to: Option "UseInternalAGPGART" "no" After you've done the changes you should see major improvements in 3d acceleration and your X/Xorg logs should not have any errors related to DRI. Also, check the glxinfo command (it should have "direct rendering: Yes" if the DRI is working properly Hope that helps On Tue, 2005-02-08 at 15:21 +0100, Filippo Carone wrote: > * Andrei Mikhailovsky ([EMAIL PROTECTED]) ha scritto: > > Try fglrx and see for yourself ) > > I'm trying them, but: > - glxgears runs at half speed (~800fps windowed) > - if I enable the Composite extension in xorg.conf, DRI will be > disabled: > (II) fglrx(0): Composite extension enabled, disabling direct rendering > (WW) fglrx(0): *********************************************** > (WW) fglrx(0): * DRI initialization failed! * > (WW) fglrx(0): * (maybe driver kernel module missing or bad) * > (WW) fglrx(0): * 2D acceleraton available (MMIO) * > (WW) fglrx(0): * no 3D acceleration available * > (WW) fglrx(0): ********************************************* * > > > Also, the terminal transparency is very very slow in opensource drivers. > > Do you mean you are able to get Composite/Damage working with the > proprietary drivers? > > Cheers, > fc > -- Andrei Mikhailovsky Arhont Ltd - Information Security Web: http://www.arhont.com http://www.wi-foo.com Tel: +44 (0)870 4431337 Fax: +44 (0)117 9690141 PGP: Key ID - 0xFF67A4F4 PGP: Server - keyserver.pgp.com
signature.asc
Description: This is a digitally signed message part