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 get this error message (copy-pasted from /var/log/XFree86.0.log)
I have latest (unstable) debian with latest (184.108.40.206) kernel. I followed the instructions in post 40 of this thread. Everything went well without any errors.
Please suggest something....
(--) SAVAGE(0): mapping framebuffer @ 0xf0000000 with size 0x800000
(==) SAVAGE(0): Write-combining range (0xf0000000,0x800000)
(II) SAVAGE(0): Splitting WC range: base: 0xf2000000, size: 0x5000000
(II) SAVAGE(0): Splitting WC range: base: 0xf4000000, size: 0x3000000
(==) SAVAGE(0): Write-combining range (0xf6000000,0x1000000)
(==) SAVAGE(0): Write-combining range (0xf4000000,0x3000000)
(==) SAVAGE(0): Write-combining range (0xf2000000,0x5000000)
(II) SAVAGE(0): map aperture:0x40bb4000
(--) SAVAGE(0): Chose mode 118 at 60Hz. (II) SAVAGE(0): 9348 kB of Videoram needed for 3D; 8192 kB of Videoram available
(EE) SAVAGE(0): Insufficient Videoram available for 3D
(EE) SAVAGE(0): Try a lower color depth or smaller desktop.
(EE) SAVAGE(0): For integrated savages try increasing the videoram in the BIOS.
(EE) SAVAGE(0): DRI isn't enabled
(II) SAVAGE(0): Using 1232 lines for offscreen memory.
(II) SAVAGE(0): Using XFree86 Acceleration Architecture (XAA)
IWhen i try the method suggested in post # 40 at the step where i am running the install.sh It fails to compile and says "The DRI drivers can not be installed without the latest kernel modules." II made sure i had the latest avaliable and it still would not work. I should add that i have gone through the steps suggested in the posts after the last person with this problem and still nothing works
Last edited by wondering_jew; 10-13-2004 at 02:31 AM.
The problem you mentioned is faced by me as well....
1) you have your kernel source in /usr/src/<your kernel dir>
2) have the same version of gcc which you used to compile the kernel
3) when following the instructions in post #40, first you unpack common package and then savage package
well im still at it i tried again and got the same thing about needing current modules, When i open dri.log it says "Makefile:182: *** Cannot find a kernel config file. Stop." where is it looking for this kernel config file, i copied the one from the boot folder to where it should be looking for it (per earlier post) and still nothing.
I edited Post 40 to reflect that the common package needs to be un-tared first. I guess I just got lucky all the times I did this and always seem to do it in the right order.
I just build another module for 220.127.116.11 and it works fine. Also someone was wondering if this works on Suse-9.1 and I can say yes it does.
S3/VIA released the source code to their savage DRI driver for xfree86 4.2.0. It is based on mesa 3.x, and as such needs to be ported to mesa 4.x for 4.3.0 or 5.x for CVS. There is some work going on to port the driver to the new mesa. For information on compiling the source for 4.2.0, see this page or this page. The code released by S3/VIA only works on prosavage and twister based chips. The UtahGLX project has support for savage 3D/MX/IX for XFree86 3.3.x and 4.x.
I am currently trying to get DRI working on my laptop (VIA S3 UniChrome Pro), this makes the Savage DRI install look like a cake-walk.
Sorry for not answering any of these questions but I've been real busy. Fortunately there has been plenty of help from the good people here at LQ.
Well I won a battle today, but ended up losing ground overall... I finally managed to get dri installed following the steps in post 40, however upon restart my screen just blinked repeatedly as X tried to start and then i guess the x server just crashed- any suggestion as to what else i may need to configure when i restart this battle would be greatly appreciated.
wandering_jew, I agree it sounds like your X server is crashing. Do you have the agpgart & via_agp modules loaded? Do you have the device /dev/agpgart ?
Try looking through /var/log/XFree86.0.log or /var/log/Xorg.0.log, depending on if you use XFree86 or Xorg...
grep EE /var/log/XFree86.0.log
grep EE /var/log/Xorg.0.log
That should show you any errors you are having.
The nice thing about doing it using the method in Post #1 is that you will be sure that the driver is compatible with the X server because you are building your X server and your driver together. The bad thing about Post #1 method of course is it is much more complicated.