I have something to add to this. Recently I tested gatos drivers going from dri to gatos was painless. However when I went back my computer locked up. I sent a report off to gatos of my findings. If it's helpfull I could try a gatos to fglrx and back to see if there are any lockups. Would there be any use in a merge of gatos init to dri or are thay just too diffrent?
--- Roland Scheidegger <[EMAIL PROTECTED]> wrote: > In my experience, this isn't entirely true. The ati and dri driver can > happily be installed together - both have their own *drm.a, *dri.o and > *drv.o (unlike nvidia's driver which comes more or less with their own X > Server...). The only thing you need to change when switching from dri to > ati's driver (and vice versa) is you need to exchange the libGL.so.1.2 > and just change the driver "radeon" to "fglrx" in the device section. > Though I prefer having two device sections so I don't get the (harmless) > messages about unused options at XFree86 startup. > And you need to make sure the right kernel module is loaded - > unfortunately in my experience terminating the X Server, unloading the > fglrx module, inserting the dri one (and changing the XFree86 config > file and libGL) and then restarting X often results in lockups, so a > reboot is required (though the other way dri->fglrx seems to work > better). (Though I've only used 2.9.13, not the newer 3.x ATI driver - > don't know if this still works, but unless ATI started to replace some > XFree libraries it still should.) > > Roland > __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
