Alas,

I downloaded an earlier version of

tar xjvf savage-2004xxxx-linux.i386.tar.bz2
tar xjvf common-2004xxxx-linux.i386.tar.bz2

installed them and tried to sudo ./install.sh but no go!

Still get:

bob@linux:~/dripkg> cat dri.log
cc -o .o
cc: no input files
make: *** [.o] Error 1

Maybe it's time to go by another graphics card

Sorry you are still not having any luck. I got it to work using

common-20040829-linux.i386.tar.bz2 29-Aug-2004 07:14 1.0M
and
savage-20040829-linux.i386.tar.bz2 29-Aug-2004 07:13 1.9M

I'm still trying to tweak ut2k4 so it runs a little faster. But it works!

first I used tar -xjvf common.....
then I untar the savage package.
cd dripkg
./install.sh

shep fc3,

No, I used the same packages as you and still same result:

bob@linux:~/dripkg> cat dri.log
cc -o .o
cc: no input files
make: *** [.o] Error 1

Anybody else able to make sense of this error message?

Hello,

Is S3 savage IX not capable of DRI?

I get this error message (copy-pasted from /var/log/XFree86.0.log)

I have latest (unstable) debian with latest (2.6.8.1) 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

Hi,

The problem you mentioned is faced by me as well....

make sure

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

also have a look at http://azeemarif.blogspot.com .... I have put the instructions how I was able to make things work....

I hope it helps...

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.

Hey wondering_jew I've got the same problem as you can read above. I'm running Suse 9.1, what is your flavor? I wonder if it's something with Suse?

I'm running ubuntu, guess i should put that in my profile on the side sometime huh

Hello bob,

this is very trivial problem (I have mentioned this problem in my blog at http://azeemarif.blogspot.com)

To solve this problem, you have to extract

1) common module first
2) savage module second

(in you posts above, you mentioned that you extracted the packages in the opposite order)

~Arif

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 2.6.8.1 and it works fine. Also someone was wondering if this works on Suse-9.1 and I can say yes it does.


azeemarifI 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.

Good luck to everyone.

Well I untarred "common" first and then "savage" but still no luck.

Here's my "cat dri.log"

make DRM_MODULES=savage.o modules
make[1]: Entering directory `/home/bob/dripkg/drm'
make -C /lib/modules/2.6.5-7.108-default/source SUBDIRS=`pwd` DRMSRCDIR=`pwd` modules
make[2]: Entering directory `/usr/src/linux-2.6.5-7.108'

WARNING: Symbol version dump /usr/src/linux-2.6.5-7.108/Module.symvers is missing, modules will have CONFIG_MODVERSIONS disabled.

Building modules, stage 2.
MODPOST
/bin/sh: line 1: scripts/modpost: No such file or directory
make[3]: *** [__modpost] Error 127
make[2]: *** [modules] Error 2
make[2]: Leaving directory `/usr/src/linux-2.6.5-7.108'
make[1]: *** [modules] Error 2
make[1]: Leaving directory `/home/bob/dripkg/drm'
make: *** [savage.o] Error 2
linux:/home/bob/dripkg #

Now it seems to be a problem with your kernel source tree

please check if you have `/usr/src/linux-2.6.5-7.108/scripts/modpost' script file ?

if not, try to get new kernel source!

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
or
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.