Selecting a display driver
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
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
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
On 12/09/05, Paul Howie <paulhowie@gmail.com> wrote:
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.
I don't have a clue about the rest of the problem but this last bit is fairly easy. Mark the relvant files as TABOO when it comes to updating. This will prevent any auto updating taking place too. Or, that's what I have done with stuff like Xine after I have got it running the way 'I' want :-) -- ============================================== I am only human, please forgive me if I make a mistake it is not deliberate. ============================================== Take care. Kevan Farmer 34 Hill Street Cheslyn Hay Staffordshire WS6 7HR
On 13/09/05, Kevanf1 <kevanf1@gmail.com> wrote:
On 12/09/05, Paul Howie <paulhowie@gmail.com> wrote:
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.
I don't have a clue about the rest of the problem but this last bit is fairly easy. Mark the relvant files as TABOO when it comes to updating. This will prevent any auto updating taking place too. Or, that's what I have done with stuff like Xine after I have got it running the way 'I' want :-)
Is there any way to know which packages include a specific file? I've marked things like kaffeine as taboo, but a single file? -- Paul
On Tuesday 13 September 2005 11:58, Paul Howie wrote:
Is there any way to know which packages include a specific file? I've marked things like kaffeine as taboo, but a single file?
Hi Paul, Try the "Search" field in YaST's Install/Remove Software module. Be sure to click the "Provides" checkbox so the "provides" field in the rpm package database is searched. - Carl
* Paul Howie <paulhowie@gmail.com> [09-13-05 11:01]:
Is there any way to know which packages include a specific file? I've marked things like kaffeine as taboo, but a single file?
rpm -q --whatprovides /<path>/<to>/<file-name> -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/gallery2
On 13/09/05, Patrick Shanahan <ptilopteri@gmail.com> wrote:
* Paul Howie <paulhowie@gmail.com> [09-13-05 11:01]:
Is there any way to know which packages include a specific file? I've marked things like kaffeine as taboo, but a single file?
rpm -q --whatprovides /<path>/<to>/<file-name>
Thanks Patrick. At the moment I'm still trying to figure out exactly where my driver file is kept. I've tried modprobe -l *savage*, modprobe -l | grep video and (on a hunch) cat /dev/video but I don't see anything that looks like a definate match. Any idea? -- Paul
* Paul Howie <paulhowie@gmail.com> [09-13-05 12:50]:
At the moment I'm still trying to figure out exactly where my driver file is kept.
I've tried modprobe -l *savage*, modprobe -l | grep video and (on a hunch) cat /dev/video
Look in /lib/modules/<kernel-#>-default/kernel/drivers/video and /usr/X11/lib/modules/drivers/ and/or locate savage|less for an indication of what and where the files are looks like savage may not be the name of the driver pat@wahoo:~> /sbin/modprobe -l |grep nvidia /lib/modules/2.4.21-297-default/kernel/drivers/video/nvidia.o also grep Driver /etc/X11/XF86Config -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/gallery2
On 13/09/05, Patrick Shanahan <ptilopteri@gmail.com> wrote:
* Paul Howie <paulhowie@gmail.com> [09-13-05 12:50]: Look in /lib/modules/<kernel-#>-default/kernel/drivers/video
a load of stuff in here, including a directory called savage with 3 files: savagefb_accel.ko, savagefb-ic2.ko and savagefb.ko
and
/usr/X11/lib/modules/drivers/
again a load of files, including one called savage_drv.o I also have a /usr/X11/lib/modules/dri/ directory that contains all the dri drivers except the one I need! I think I need to start looking in xorg log files... -- Paul
On 13/09/05, Paul Howie <paulhowie@gmail.com> wrote:
I think I need to start looking in xorg log files...
Bingo! /var/log/Xorg.0.log has a couple of lies that read: (II) LoadModule: "savage" (II) Loading /usr/X11R6/lib/modules/drivers/savage_drv.o Now I just need to compile the dri enabled driver, replace savage_drv.o, taboo anything that references it in YaST and keep my fingers crossed! Thanks for all the help everyone. -- Paul
On Tuesday 13 September 2005 15:09, Paul Howie wrote:
Now I just need to compile the dri enabled driver, replace savage_drv.o, taboo anything that references it in YaST and keep my fingers crossed!
Thanks for all the help everyone.
Good going, Paul, and good luck. I can't remember if I posted this resource earlier, or not, so I'll post it again just in case: http://www.winischhofer.at/linuxsisvga.shtml FYI, I haven't looked at the 3D/SiS issue since 9.0 and the 2.4 kernel. It seems that, since kernel 2.6.3+, DRI is enabled by default on this chipset. Now I understand why a couple of games I checked out long ago are working now, albeit slowly due to the built-in memory scheme in this system. I guess it's better than no 3D at all! Keep us posted! regards, - Carl
On 14/09/05, Carl Hartung <suselinux@cehartung.com> wrote:
Good going, Paul, and good luck. I can't remember if I posted this resource earlier, or not, so I'll post it again just in case:
Thanks, handy link. If you're interested, I've found these useful so far: http://azeemarif.blogspot.com/2005/07/simple-steps-to-make-3d-accelaration.h... http://dri.freedesktop.org/wiki/S3Savage http://dri.freedesktop.org/wiki/Building http://www.linuxquestions.org/questions/showthread.php?s=&postid=1834980#post1834980 The 3D on the savage chip is really poor, even with the official windows drivers, but it's enough for a screensaver ;-) -- Paul
On Wednesday 14 September 2005 03:33, Paul Howie wrote:
The 3D on the savage chip is really poor, even with the official windows drivers, but it's enough for a screensaver ;-) I understand exactly how you feel!
Thanks for the links, Paul, and keep me posted on your progress. regards, - Carl
On Tuesday 13 September 2005 02:56 pm, Paul Howie wrote:
On 13/09/05, Patrick Shanahan <ptilopteri@gmail.com> wrote:
* Paul Howie <paulhowie@gmail.com> [09-13-05 12:50]: Look in /lib/modules/<kernel-#>-default/kernel/drivers/video
a load of stuff in here, including a directory called savage with 3 files: savagefb_accel.ko, savagefb-ic2.ko and savagefb.ko
and
/usr/X11/lib/modules/drivers/
again a load of files, including one called savage_drv.o
I also have a /usr/X11/lib/modules/dri/ directory that contains all the dri drivers except the one I need!
I think I need to start looking in xorg log files...
-- Paul ========
Paul, I don't want to sound like the pessimist here, but I'm guessing you are not going to have any luck in getting the dri working on that chipset. I recently put together a system that had the Savage graphics on it. After doing a lot of research, I found that it was just not going to happen! 2d is fine and Sax2 works well to get you there, but for some reason, nobody has bothered to take it further. Now you might find a 3rd party graphics developer's files better able to help, if you just gotta have 3d, but I think that is going to be the only way. Sorry to add more bad news to your efforts. end of line Lee
On 13/09/05, BandiPat <penguin0601@earthlink.net> wrote:
Paul, I don't want to sound like the pessimist here, but I'm guessing you are not going to have any luck in getting the dri working on that chipset. I recently put together a system that had the Savage graphics on it. After doing a lot of research, I found that it was just not going to happen! 2d is fine and Sax2 works well to get you there, but for some reason, nobody has bothered to take it further.
Now you might find a 3rd party graphics developer's files better able to help, if you just gotta have 3d, but I think that is going to be the only way. Sorry to add more bad news to your efforts.
end of line Lee
Well, I do know that it is possible, in gentoo I wouldn't have even needed to post to a list as there's plenty of info out there how to get it working by recompiling the kernel, xorg, mesa and dri. I'm just trying to do it without breaking future YaST updates as much as possible. It's the suse angle that's making this such a challenge. 3D isn't a big deal, I've been using suse since 9.0 on my laptop when I finally dumped windows altogether and I've never missed 3d. But I hate being defeated when I know success is a possibility. This is really more of a learning experience than anything else. I'll let you know if I get it working, and what I had to do. Maybe we should try to get the OpenSuSE guys to compile the savage driver along with the rest? Ciao -- Paul
participants (5)
-
BandiPat -
Carl Hartung -
Kevanf1 -
Patrick Shanahan -
Paul Howie