Direct Rendering Infrastructure DRI on VIA\S3 Savage
Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I went and compiled the savage drivers like you said, and it compiled without errors. Copied the drivers to /lib/modules/linuxversion/kernel/drivers/char/drm directory and then ran depmod -a. Result was unresolved symbol errors with the drm modules. The new XF86 server was awesome! It made my mouse run like as if I was running 2.6............., gee whiz fast! Glinfo shows dri as not enabled. How do I sort out the unresolved symbols? Oh and btw, I found the same drm driver in the kernel source and then edited the config.in file to enable me to choose to compile the savage drm driver into the kernel or as a module and then recompiled a new kernel, inserted kernel, rebooted, and then tried to insert the savage module with the same unresolved symbols errors. Grrrrrr, I've been wanting to get the 3d thing going for a long while, and this is frustrating to say the least.
Here is a quicker method I discovered. I used this method when I installed Suse-9.1, but it should work for most distros. The default Suse kernel doesn't have DRI turned on so I had to build a new kernel and enable DRI. Even though there is no S3/VIA option in the kernel config you still must turn on DRI in the kernel (it's below /dev/agpgart in the Device drivers/Character devices section.) I did not stress this point in my first post and this may be causing some people some problems. So as long as you have your kernel sources properly installed(see post #1) and you enabled DRI in the kernel you should be OK. This should also work on other Graphics cards besides the S3/VIA Savage.
I know this is kinda an old thread, but I found it pretty helpful. However I am not able to get it installed and running properly. I have tried 3 different methods and none have worked. When I try the one from the first post, and also the method posted at http://www.linux-sxs.org/guis/DRIS3.html I get the following error:
accessx.c:532: error: `XtNstate' undeclared (first use in this function)
accessx.c:532: warning: left-hand operand of comma expression has no effect
make: *** [accessx.o] Error 1
Then when I try the method in the last post (which is much faster), I get this error:
ERROR: Kernel modules did not compile
The DRI drivers can not be installed without the latest kernel modules.
Installation will be aborted. See the dri.log file for information on
what went wrong.
I just upgraded to kernel 2.6.7, so it should be ok. Any help would be greatly appreciated.
Did you enable enable DRI in your 2.6.7 kernel? I know there is no S3/VIA dri module in the kernel but it seems you still need to turn that option on.
$ grep DRM /usr/src/linux/.config
# CONFIG_DRM_TDFX is not set
# CONFIG_DRM_GAMMA is not set
# CONFIG_DRM_R128 is not set
# CONFIG_DRM_RADEON is not set
# CONFIG_DRM_MGA is not set
# CONFIG_DRM_SIS is not set
If that doesn't help check your dri.log file, and post it here if you think it will help.
Humm.. It looks like maybe your snapshot was corrupted. The savage.bz2 file should be about 1.9M and the common.bz2 file is 1.08M. You should create 5 subdirectories and 4 files in the dripkg directory. Maybe you should try starting over.