On Monday 12 September 2005 13:19, Paul Howie wrote:
I'm still trying to get my laptop with integrated S3 savage chip to use dri. I've found some good resources, but I still have a couple of concerns that I hope someone can help with.
I've already mailed about the first problem (modifying xorg.conf).
The second is that SaX2 currently reports my display driver as "savage" and xorg.conf has the line
Driver "savage"
in the Device section. I assume this corresponds to the file /usr/X11R6/lib/modules/driver/savage_drv.o (but I'm not sure how to check).
The problem is that I think the driver I need to compile will end up as /usr/X11R6/lib/modules/dri/savage.so and I'm not sure how I can make xorg use this file instead. -- Paul
Paul, I'm not going to be responsible for you frying any hardware. And I think you'd be better served pulling these separate questions into a single thread, since they're all about enabling DRI on your system. Furthermore, a lot of the context that you're omitting would actually help people to be more helpful to you. Instead of doling out isolated crumbs, start with a fair description of your hardware, the OS and the problem. Then discuss (concisely) what you've researched and undertaken to resolve it. That way, people won't waste time listing off a bunch of things that have already been done. xorg.conf is just a text file with a time-stamped SaX2 header at the top. This is the procedure I use when modifying it: - copy it to my desktop - change the permissions to edit not as root - open in text editor - save (no changes yet) under a backup name and close - reopen the first copy in the editor and make changes - copy the modified version, as root, to overwrite the in situ file - cross fingers and test A ".o" file is an object file A ".so" file is a /shared/ object file. If I'm mistaken, someone will undoubtedly correct me, but I think all you'd need to do is copy the original savage_dri.o to savage_dri-o.bak and then rename the file you've compiled to match the one originally installed. - Carl