Hey azeemarif,
the 0822 DRI packs work like a breeze. DRI is now enabled and I even tested it by playing tuxracer. Thanks again for the extremely prompt and professional help.

I hadn't noticed this before, but after having made successfully working DRI on savage twister (on a laptop),
I get this warning messages when I launch any libGL based app :

libGL warning: 3D driver claims to not support visual 0x23
libGL warning: 3D driver claims to not support visual 0x24
libGL warning: 3D driver claims to not support visual 0x25
libGL warning: 3D driver claims to not support visual 0x26
libGL warning: 3D driver claims to not support visual 0x27
libGL warning: 3D driver claims to not support visual 0x28
libGL warning: 3D driver claims to not support visual 0x29
libGL warning: 3D driver claims to not support visual 0x2a
libGL warning: 3D driver claims to not support visual 0x2b
libGL warning: 3D driver claims to not support visual 0x2c
libGL warning: 3D driver claims to not support visual 0x2d
libGL warning: 3D driver claims to not support visual 0x2e
libGL warning: 3D driver claims to not support visual 0x2f
libGL warning: 3D driver claims to not support visual 0x30
libGL warning: 3D driver claims to not support visual 0x31
libGL warning: 3D driver claims to not support visual 0x32


Does somebody knows what this really means ?

Hi /bin/bash, I am running Fedora Core 3 on a Presario 725 (with ProSavage KN133), and tried using your guide. it compiled successfully, but the XFree86 binary wouldn't work since all my libraries were for X.org. I tried this guide, it compiled OK, but it didn't work either. I am really frustrated and want to play TuxRacer! Please help me.

The procedure mentioned in post #40 of this thread works with Xfree86 as well as Xorg. There must be some other problem... please provide some more information.......

check /var/log/Xfree86.0.log or /var/log/xorg.log or something similar ............

The procedure mentioned in post #40 doesn't work anymore, since the link there doesn't work anymore. Is there any mirror I can use?

EDIT: I found some unofficial files that worked perfectly at http://freedesktop.org/~fxkuehl/snapshots/
Thank you all.

the URL for the snapshots is now http://www.freedesktop.org/dri/snapshots/ (instead of ~dri) but since the site's attack in november the snapshots are temporarily removed (see the README)

I have installed latest snapshots deb pkg 2004.11.23 but cant get XvMC enabled

I get

(II) SAVAGE(0): Direct rendering enabled
(--) SAVAGEInitMC: Cannot add map to drm!
(**) SAVAGE(0): XvMC is not enabled
(==) RandR enabled

everything is great except for this.
mem is

(II) SAVAGE(0): 9348 kB of Videoram needed for 3D; 32768 kB of Videoram available
(II) SAVAGE(0): Sufficient Videoram available for 3D
(II) SAVAGE(0): [drm] bpp: 32 depth: 24
(II) SAVAGE(0): [drm] Sarea 2200+872: 3072
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 7, (OK)

it all looks ok.
how much mem do I need?
cheers
mpoos

Hi, before I install these drivers I would like to know if they also enable other functions like the graphical output to a beamer or lcd monitor?
As far as I understood only the DRI module and nothing else is supported, isn't it?

Your color depth is set to 24 (32bpp). You can reduce it to 16 (24bpp) in your /etc/X11/XFree86.conf or /etc/X11/Xorg.conf. It will not only solve your DRI problem but also increase X speed.

if anyone could help.. please! :)

http://www.linuxquestions.org/questi...hreadid=280959

I'm not sure this will work with your chip. Look HERE

This is your chip:
(--) PCI:*(1:0:0) S3 Inc. VT8375 [ProSavage8 KM266/KL266] rev 0



Also from your post:
(II) SAVAGE: driver (version 1.1.27) for S3 Savage chipsets: Savage4,
Savage3D, Savage3D-MV, Savage2000, Savage/MX-MV, Savage/MX,
Savage/IX-MV, Savage/IX, ProSavage PM133, ProSavage KM133,
ProSavage PN133, ProSavage KN133, SuperSavage/MX 128,
SuperSavage/MX 64, SuperSavage/MX 64C, SuperSavage/IX 128,
SuperSavage/IX 128, SuperSavage/IX 64, SuperSavage/IX 64,
SuperSavage/IXC 64, SuperSavage/IXC 64, ProSavage DDR,
ProSavage DDR-K

http://www.linuxquestions.org/hcl/sh...p?product=1908 i guess you're not right.. maybe it uses another driver.. anybody knows anything about this? =|

http://ubuntuforums.org/archive/index.php/t-11400.html -> i've found something.. anyone knows about this patch?

I didn't say the card would not work at all, I just dont think the savage dri driver will work with it. It will probably work with the generic svga driver.

Good luck.

OK bodymind you were right. This should work with your chips.

It should work as written in the first post without any patches.

Remember as I stated in post #1 this is a work-in-progress and as such it is constantly changing. Also the documentation is constantly changing. You should always check the dri homepage for the latest documentation.

I'm terribly sorry about the mistake. Good-Luck.

prosavage8 ddr dri on Debian, no go
 

Using debian with a 2.6.11.6 kernel with DRM and savage enabled (seemingly), and trying to get DRI installed for S3 Prosavage8 DDR card. Im using X Window System Version 6.8.2 (Debian 6.8.2.dfsg.1-3) which is supposedly xorg, though Ive heard it may be some mutant version of xfree86. After running install.sh, I get-

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

Please help me find whats wrong here, really want 3D to work. Any ideas?
Thanks,
KE

Look in dri.log and se if there are any errors listed.

Make sure you have the kernel-sources installed properly (many post here explain that). You should make sure your kernel has DRM enabled

ls /lib/modules/`uname -r`/kernel/drivers/char/drm

If you don't have a drm.ko module then check if it is built into the kernel:
grep -i drm /usr/src/linux/.config
CONFIG_DRM=m #Yours may say CONFIG_DRM=y
# CONFIG_DRM_TDFX 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

BTW I am currently running SimplyMEPIS, kernel 2.6.12.2
X Window System Version 6.8.2 (Debian 6.8.2.dfsg.1-4)

And I have direct rendering working, on my ProSavage8 DDR. So don't give up.

Hi /bin/bash, thanks for looking, had some problems with gcc versions, so I changed to 3.3 from 4.0, and tried installing again, here is my dri.log:

make DRM_MODULES=savage.o modules
make[1]: Entering directory `/home/flow/dripkg/drm/linux-core'
make -C /lib/modules/2.6.11.6.050620.2/source SUBDIRS=`pwd` DRMSRCDIR=`pwd` modules
make[2]: Entering directory `/usr/src/kernel-source-2.6.11.6'
CC [M] /home/flow/dripkg/drm/linux-core/drm_auth.o
CC [M] /home/flow/dripkg/drm/linux-core/drm_bufs.o
CC [M] /home/flow/dripkg/drm/linux-core/drm_context.o
CC [M] /home/flow/dripkg/drm/linux-core/drm_dma.o
CC [M] /home/flow/dripkg/drm/linux-core/drm_drawable.o
CC [M] /home/flow/dripkg/drm/linux-core/drm_drv.o
CC [M] /home/flow/dripkg/drm/linux-core/drm_fops.o
CC [M] /home/flow/dripkg/drm/linux-core/drm_ioctl.o
CC [M] /home/flow/dripkg/drm/linux-core/drm_irq.o
CC [M] /home/flow/dripkg/drm/linux-core/drm_lock.o
CC [M] /home/flow/dripkg/drm/linux-core/drm_memory.o
CC [M] /home/flow/dripkg/drm/linux-core/drm_proc.o
CC [M] /home/flow/dripkg/drm/linux-core/drm_stub.o
CC [M] /home/flow/dripkg/drm/linux-core/drm_vm.o
CC [M] /home/flow/dripkg/drm/linux-core/drm_sysfs.o
CC [M] /home/flow/dripkg/drm/linux-core/drm_pci.o
CC [M] /home/flow/dripkg/drm/linux-core/drm_agpsupport.o
CC [M] /home/flow/dripkg/drm/linux-core/drm_scatter.o
CC [M] /home/flow/dripkg/drm/linux-core/drm_memory_debug.o
CC [M] /home/flow/dripkg/drm/linux-core/ati_pcigart.o
CC [M] /home/flow/dripkg/drm/linux-core/savage_drv.o
CC [M] /home/flow/dripkg/drm/linux-core/savage_bci.o
CC [M] /home/flow/dripkg/drm/linux-core/savage_state.o
LD [M] /home/flow/dripkg/drm/linux-core/drm.o
LD [M] /home/flow/dripkg/drm/linux-core/savage.o
Building modules, stage 2.
MODPOST
*** Warning: "agp_backend_release" [/home/flow/dripkg/drm/linux-core/drm.ko] undefined!
*** Warning: "agp_copy_info" [/home/flow/dripkg/drm/linux-core/drm.ko] undefined!
*** Warning: "agp_unbind_memory" [/home/flow/dripkg/drm/linux-core/drm.ko] undefined!
*** Warning: "agp_allocate_memory" [/home/flow/dripkg/drm/linux-core/drm.ko] undefined!
*** Warning: "agp_free_memory" [/home/flow/dripkg/drm/linux-core/drm.ko] undefined!
*** Warning: "agp_backend_acquire" [/home/flow/dripkg/drm/linux-core/drm.ko] undefined!
*** Warning: "agp_enable" [/home/flow/dripkg/drm/linux-core/drm.ko] undefined!
*** Warning: "agp_bind_memory" [/home/flow/dripkg/drm/linux-core/drm.ko] undefined!
CC /home/flow/dripkg/drm/linux-core/drm.mod.o
LD [M] /home/flow/dripkg/drm/linux-core/drm.ko
CC /home/flow/dripkg/drm/linux-core/savage.mod.o
LD [M] /home/flow/dripkg/drm/linux-core/savage.ko
make[2]: Leaving directory `/usr/src/kernel-source-2.6.11.6'
make[1]: Leaving directory `/home/flow/dripkg/drm/linux-core'
/usr/X11R6/lib
WARNING: Error inserting drm (/lib/modules/2.6.11.6.050620.2/kernel/drivers/char/drm/drm.ko): Invalid module format
FATAL: Error inserting savage (/lib/modules/2.6.11.6.050620.2/kernel/drivers/char/drm/savage.ko): Invalid module format


After typing ls /lib/modules/`uname -r`/kernel/drivers/char/drm I get:

dri-old.drm.ko drm.ko i830.ko mga.ko radeon.ko sis.ko
dri-old.savage.ko i810.ko i915.ko r128.ko savage.ko tdfx.ko

grep -i drm /usr/src/linux/.config gives me:

CONFIG_DRM=m
CONFIG_DRM_TDFX=m
CONFIG_DRM_R128=m
CONFIG_DRM_RADEON=m
CONFIG_DRM_I810=m
CONFIG_DRM_I830=m
CONFIG_DRM_I915=m
CONFIG_DRM_MGA=m
CONFIG_DRM_SIS=m


Glad to hear you're running almost the same setup as me and have success. Hope you can offer some further guidance based on this info. Thanks

<EDIT>
I got it running after lots of learning and guessing... I think my version.h was wrong after some failed kernel compiles... had the name of kernel that isn't used. Seems after doing this and also changing my gcc from 4.0 to 3.3, it worked. GLX gears shows 250fps, not bad, more than double what I had without dri. Tux racer looks great except the image size(resolution) is small, not sure how to change that except by monitor settings buttons, but will fool around with it. Thanks for the encouragement!

Glad to hear you got it working. Just to give you something to compare to. While running KDE in 24bit 1280 x 1024 resolution I get ~ 450FPS. In XFCE I can get >480FPS. Also have 2G P4 w/512M ram if that matters?

This thread is such a wonderful resource for the people stuck with S3 graphics card for enabling DRI in Linux. Thanks to /bin/bash for starting this thread.

Since the time I read this thread the very first time, to the present, I had to enable DRI for S3 Savage graphics card many a times (sometimes because of new installation and sometimes because of kernel compilation).

I have learned few lessons during the process. I have put this knowledge in a post in my blog .

I hope it helps.

Has anyone heard of DRI working when loading X with the startx command but NOT working when loading with the kdm command? This also means that it doesn't work if I load up in run level 5, but it will work if I load in run level 3 and then type in startx.

I'm using Mandriva LE 2005 (10.2). I have a compaq presario 721 with a Savage Twister K.

Any ideas what the difference between the kdm and startx commands could be that would totally foobar up dri?

springshades


The problem you mentioned seems to be "libGL Hell" (Similar to DLL hell on windows).

In simple words, you might have more that 1 copy of libGL (or any other essential part of DRI), and starting X in run level 5 and run level 3 might have linked to the different libs or modules.

Please perform a simple test...

In run level 3, check if the command "glxinfo |grep direct" gives an answer "yes". It means DRI is enabled. Now please run the command "ldd glxinfo" and save the output.

In run level 5, check if the command "glxinfo |grep direct" gives an answer "No". It means DRI is not enabled. Now please run the command "ldd glxinfo" and save the output.

Compare these two outputs of "ldd glxinfo" command. If they point to different libraries .. then there lies the problem (for the solution to this problem, check my last post).

Thanks for the info azeemarif.

I'll let you know if things work out in a few days. I started updating my computer and there was an update to Xorg that messed up dri. I'll have to finish updating (to make sure that I finish messing things up before starting to fix them) and then set up dri again. Then I'll check on whether libGL hell is my problem. Thanks.

/bin/bash
"Glad to hear you got it working. Just to give you something to compare to. While running KDE in 24bit 1280 x 1024 resolution I get ~ 450FPS. In XFCE I can get >480FPS. Also have 2G P4 w/512M ram if that matters?"

Wow, thats amazing, in KDE with 24 bit, 1024x768, I get 250fps, my system is Athlon XP 1800 with 512M DDRram. Wonder why yours is so much faster?

Well, something in the update that I did seems to have fixed MOST of the issues that I had with DRI. I can now boot into run level 5 with dri support for my card working. I'm not going to complain about the few issues left (I have to restart the X server once each time I start my computer because after a certain amount of time, I have a small graphical glitch and my keyboard stops working. Restarting X fixes it and the problem doesn't happen until the next time I boot my computer.

BTW, my issues were pretty weird. It actually sounds like it might not have been libGL hell. In glxinfo, dri was always listed as enabled. There was some bug that caused any application that used it to simply error out. Glxinfo gave some of the information, but most of the way through it gave a segment fault. Glxgears gave a segment fault immediately. Most of the 3D games I tried froze the entire system and needed a hard reset.

Possibly you have more services or programs running. Try running top and see if you can disable the most resource intensive programs temporarily and then run glxgears again to see if it helps.

I have noticed my FPS have increased quite a bit since my first post when I was getting 350FPS. I figure it is because I keep my DRI updated by installing the latest snapshots regurlarly.

knowerrors

Check your kernel config and make sure you have mtrr turned on in the Processor type and features section. I have it built into my kernel however you could also build it as a module.

If you want to check if your kernel has mtrr enabled do this:
You should have something similar to the above.

/bash/bin- Thanks for the suggestion, looks like mine has mtrr turned on already:

flow@3[Enigma]$ cat /proc/mtrr
reg00: base=0x00000000 ( 0MB), size= 512MB: write-back, count=1
reg01: base=0x1e000000 ( 480MB), size= 32MB: uncachable, count=1
reg02: base=0xe8000000 (3712MB), size= 64MB: write-combining, count=2
reg03: base=0xe0000000 (3584MB), size= 16MB: write-combining, count=1
reg04: base=0xe6000000 (3680MB), size= 16MB: write-combining, count=1
reg05: base=0xe8000000 (3712MB), size= 64MB: write-combining, count=1
reg06: base=0xe4000000 (3648MB), size= 32MB: write-combining, count=1
reg07: base=0xe2000000 (3616MB), size= 32MB: write-combining, count=1

I looked at what "top" command showed, and nothing was sucking that much cpu/mem besides Xorg. I am also running the latest dri snapshot, as well as the most up to date x.org packages. Could it just be that your cpu is that much better? BTW, my card is an onboard prosavageddr... the one thats part of the M7VIG Biostar http://www.biostar-usa.com/mbdetails.asp?model=m7vig
And Im running kernel 2.6.12.3. I know it seems picky, but its killing me and not to mention the jealousy, that your're getting such incredible faster frame rates on what seem to be such similarly equiped boxes. Any more ideas to boost my fps would be great!

I have the VIA P4MA Pro Mainboard in this computer.

Processor
- Intel® Pentium® 4 Processor (478pin)
- 400MHz Front Side Bus
Chipset
- VIA ProSavageDDR™ P4M266 North Bridge Featuring integrated S3 ProSavage8™ AGP engine
- VT8235 South Bridge
System Memory
- 2 DDR266 DIMM Sockets
- Up to 2GB
Expansion Slots
- 1 AGP 4X slot (1.5V Support)
- 3 PCI Slots
- 1 CNR Slot
On Board IDE
- 2 x ATA133/100 Connectors
On Board FDD
- 1 x FDD Connector
Onboard Audio
- VIA VT1616 6 Channel AC’97 CODEC
Onboard LAN
- VIA VT6103 10/100 ETHERNET PHY
Back Panel I/O
- 1 PS2 mouse Port
- 1 PS2 keyboard Port
- 1 RJ 45 100/10Mb LAN Port
- 1 VGA Port
- 2 USB 2.0/1.1 Ports
- 1 Serial Ports
- 1 Parallel Port
- 3 Audio Jacks: line-out, line-in and mic-in
Smart5.1™ Front L/R, Rear L/R, Center/Subwoofer
- 1 Game/MIDI Port
BIOS
- Award BIOS
- 2/4Mbit Flash Memory
Applications
- VIA FliteDeck™ System Management UtilityMissionControl-H/W Monitoring, Remote SNMP ManagementJetStream-Overclocking Optimized UtilityFlashPort-Live BIOS FlashSysProbe-Live DMI Browser
Overclocking
- 100MHz up to 200MHz adjustment by 1MHz Increments
- Tunable Vcore/Vdimm/Vagp
- BIOS Overclocking Auto-Recovery
System Monitoring & Management
- CPU Temperature Monitoring
- CPU Voltage Monitoring
- Wake-on-LAN, Wake-on-Ring, Keyboard-Power-on, Timer-Power-on
- System Power Management
- AC Power Failure Recovery
Form Factor
- Micro ATX (4 Layers)
- 24.5cm x 20.5cm

Aside from the different processors there isn't that much difference that I could be getting nearly 2X the FPS. I am running 2.6.12.4 kernel. Did you build your kernel and if so did you optimize for the AMD processor?

It could be the front side bus speed; 266 vs. 400.

Awesome guide ! :) I was successful getting DRI working in my Asus A1300 laptop with a S3 twister chip :) Glxgears gives me about 350fps which is OK, but I wouldn't mind getting a higher value! I have tried running Quake III Arena and it works at least, but I'm getting some weird graphic glitches which are really annoying me :( (Any ideas ?)
And, for those of you who are stuck with the "Cannot find a kernel config file" problem, I also had this problem in my Ubuntu Hoary distribution, but was able to solve this by using the kernel-headers package instead of linux-source.

Oh happy days! Kernel 2.6.14 has savage drm support!

From the Changelog.
Yes it does work!

I realize that this thread is kind of old but I really want DRI to work on my laptop (twister_k chipset)...

I am using SUSE 10 with Xorg 6.8.2 on Kernel 2.6.13-15.8

I tried different savage and common packages and get similar error outputs... This is one of them >>>
BTW... /usr/src/linux-2.6.13-15.8/ originally did not have .config file, so I copied it from /boot ... I heared people saying that some link has to be removed there after copying maybe that's the problem...

Thanks in advance

Try going into /usr/src/linux-2.6.13-15.8 and run make menuconfig or make xconfig and make sure that your kernel has DRI turned on. I believe it is in Drivers -> Char section just below agpgart. If your config does not have DRI enabled then you need to enable it and build a new kernel. If it is already enabled then try running make all and then try building the DRI module again after that finishes. You should also start with a new dripkg directory (remove the old and reinstall fresh.)

Thanks for reply,
building the new kernel now...
by the way, I am about to update to SuSE 10.1 and it has 2.6.16 rc1 kernel...
So, will that solve the problems or will I still have to do the above steps?
Thanks

ok, so i turned on DRM in .config
then I did "make all"
after this the script ran fine and installed
i made the changes to the xorg.conf and modprobe.conf
and after i restarted X, it crashed...
here is what it said
ok, that sucked, didnt it? :)
after removing Load "dri" line from xorg.conf i at least got X to start, but how do I enable DRI???

Thanks

Make sure you have agpgart enabled. Before starting X run modprobe via-agp, that should load both via-agp and agpgart. Make sure you have correct permissions to access /dev/agpgart.

In xorg.conf

Section "DRI"
Mode 0666
EndSection

As of 2.6.14 the kernel has savage DRI support built in so as long as SUSE has it enabled you shouldn't have to do anything except possibly edit your xorg.conf file.

Hello everybody.
I have some problems left too.
I installed the drivers. there seems to be no prob till there. also, i have already modified my xorg.conf.
but where do i have to tell my ubuntu or x.org to load up the modules on startup since i have NO modprobe.conf or local.start on my system?? someone mentioned the etc/modprobe.d/aliases would be the same as the modprobe.conf but didn't write much more, and also i can't find it anymore.
BruceCadieux mentioned something about modprobing in the /etc/init.d/rc in Thread #39
but i have no clue how to put that at the end of rc...
I'm really greatfull for any help!

Thanks!

su
nano /etc/init.d/rc
<PageDn> to end of file.
modprobe via-agp
<Ctrl>+x
y<Enter>

thanx /bin/bash.
found out that the etc/modules file loads these modules also on start up.

0% of this works for me I have read and tried every single thing in this thread and on dri.freedesktop.org and their mailing lists and right now all I want is to get rid of this stuff. Does anyone have any idea how to reverse the changes and go back to stock I'm sick of searching through this stuff? X doesn't even work going to vesa and no dri! This thread literally destroyed X on my system and I don't want dri I just want X back. Reversal techniques please :(

From Post #1
You didn't read post 1 very carefully. Also you should re-read Post #132. You don't have to do anything except build a new kernel >= 2.6.14 and select DRM and dri savage support.

Now, since you might be running Fedora? I would suggest:
rpm -qa|grep xorg
rpm -i --force <xorg packages>

ok this may be and old thread but i am lost in all this info im new to linux and just want my games to work dri is disabled and i need some help like maybe on a few things if at all possible ill edit if anyone will help me.

can someone plsz help with this im so confused on what to do and what not to do

first of all, what is your hardware and what distribution are you using?
the simplest way to solve the DRI problem is installing the latest version of your linux distribution, then all you'll have to do is modify your xorg.conf file...

pro savage sucks get another card from newegg.com i recommend a geforce
for 62 dollars its a 256 mb video card with 16 great review so id say its worth the upgrade and also this driver is supported by suse without alot of trouble.