On 12/09/05, Carl Hartung <suselinux@cehartung.com> wrote:
On Monday 12 September 2005 13:19, Paul Howie wrote: 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.
I think the hardware is fairly safe, and this is a new install of suse so I don't have a lot to lose by experimenting. I've tried before when I was installing 9.0 and 9.2 to get some answers with this kind of general approach. As best as I can tell, no one on the list has ever managed to get suse to use dri... if they have they've kept it pretty quiet! I think I've got most of the details down myself now, I was just interested in a few of the SuSE specific aspects of the process, specifically how YaST and SaX would handle me messing with their files. I thought this time I'd see if I could get those kind of more generic answers from the list, rather than hoping to get some savage-specific info. It's maybe worth mentioning that all the other dri drivers seem to be supported by suse by an rpm. Only s3 savage users are likely to have helpful experience, and it's an oldish and not too common chipset.
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.
So far I'm sitting here with a raw 9.3 install. I've read a LOT, but not tried anything since 9.2 a long while ago. I'm sure I'll get there, but I was after clarification on a few points that still confuse me a little.
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
Yeah, I can edit the file, but I wasn't sure if I'd be messing up SaX by doing it. The header does say something like "generated by SaX - DO NOT EDIT" after all ;-)
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.
I thought about this too, but I'm a little concerned that a future YOU update to xorg will overwrite it again. And, as I said, I'm not even 100% sure where the current video driver is in the filesystem.
- Carl
Thanks a lot for the quick replies. If I run into a brick wall I'll probably end up doing what I did the last couple of times and give up for a while before trying the list again. If I do that, I'll make sure to take your advice on board and give a good run down of my whole situation. Cheers again, -- Paul