HOW-TO: ProSavage, SuperSavage DDR and dri-drm 3d drivers

salivian · Tux's lil' helper Joined: 15 Sep 2002 Posts: 91

yeah. the opengl-update thingy is still problematic

to resolve that:
cp /usr/lib/libGL.so.1.2 /usr/lib/opengl/xorg-x11/lib/
cp /usr/lib/modules/extensions/libglx.so /usr/lib/opengl/xorg-x11/extensions/

mlybarger · Guru Joined: 04 Sep 2002 Posts: 463

AIgor: i tried your suggestion, and got some error about noXFree86DRIExtension symbol. the server came up but no dri. btw, i'm not exactly using the Savage driver, i'm using the via. i have a via S3 UniChrome] Integrated Video card on my lappy. using the binary via driver gives worse perf in glxgears than using vesa driver. i've had this lappy for about a year almost and have used vesa on it because i couldn't get via driver ever to work.

now, i'm ready to give it a go.

AIgor · Posted: Thu Feb 10, 2005 10:44 am Post subject:

Uhm... Look if libraries were installed in right places, and give me more informations about errors in your logs.

salivian · Tux's lil' helper Joined: 15 Sep 2002 Posts: 91

noXFree86DRIExtension is related to your /usr/X11R6/bin/Xorg binary in my experience.

You need at least the ~x86, if not CVS, Xserver or Xorg binary, try nm your Xorg and look for that symbol.

masterinferno · Apprentice Joined: 28 Jul 2004 Posts: 236 Location: France

Hi !
I've got a desperate problem with my Shuttle SK41G (ProSavageDDR integrated to the main board)

salivian · Tux's lil' helper Joined: 15 Sep 2002 Posts: 91

In my experience .... No.

I even compile everything as modules (agp savage etc ), the xserver should make a access request to your pci bus then the kernel should load the modules properly.

for you CVS symbol problem.

did you have dlloader in USE and did a make install after the server is built ?

CVS builds .so's by default.

masterinferno · Apprentice Joined: 28 Jul 2004 Posts: 236 Location: France

Yes, the first time I tried, I emerged with +dlloader and +opengl but I gave up with this method.. :oops:

I remember, when I tried this method, I reboot a first time..No glitches ! but glxinfo said me "no opengl"...

(in spite of the 0666 section)
So I put the modules in /etc/modules.autoload.d/kernel-2.6, I reboot, and then it began to crash my display.
So I removed the modules from this file, and it changed nothing (crash+glitches)..

And then I tried with the binaries, without dlloader...which is my actual x.org (with vesa driver

)

No, I didn't remember I made a "make install" after the server built..you mean the dri cvs ?(my x.org is not from cvs, it's a ~x86)
I'm going to make a last try with this..and if it gives me bad results, I think I will give up..
Thank you a lot ! :cry:

_________________
"La vérité, c'est comme la peau du saucisson: desfois, c'est dur à avaler."

salivian · Tux's lil' helper Joined: 15 Sep 2002 Posts: 91

There are 3 thing that you need from CVS
1. xc (which is really xorg, but dri folks provided a minimal build config)
2. Mesa (provides DRI driver)
3. drm (Modules)

disregard you have the latest ~x86(6.8.2) or not, you still need to bulid things from CVS (including xc) according to http://dri.freedesktop.org/wiki/Building.

The current 6.8.2 comes with a Savage 3D DRI modules but without a Savage DDX 2D DRI aware driver. So that driver must be bulit from CVS as well.

The symbol error should be related to the version of /usr/bin/Xorg. there is an Xorg in extras/ in the binary snapshot server.

Gullible Jones · n00b Joined: 22 Jan 2005 Posts: 41 Location: Dog Solitude

Ummm... aren't Mesa and x11-drm (both with Savage support) in Portage right now?

salivian · Tux's lil' helper Joined: 15 Sep 2002 Posts: 91

To my knowledge ... No...

Xorg 6.8.2 comes with a DRI unaware 2D driver and a DRI module ( ie useless...)...

so all 2D and (Mesa) DRI drivers need to be bulit from CVS.

Gullible Jones · n00b Joined: 22 Jan 2005 Posts: 41 Location: Dog Solitude

Mesa

x11-drm

The only problem would be the 2D drivers, you would have to build those from CVS AFAIK.

RoadRunner · Posted: Sun Feb 13, 2005 8:08 pm Post subject:

http://www.gentoo.org/doc/en/dri-howto.xml#doc_chap5

I believe salivian is correct, since I tried the mesa and x11-drm packages with ~x86 and no dri on my savage MX. Don't know about the hard masked versions though.

Gullible Jones · n00b Joined: 22 Jan 2005 Posts: 41 Location: Dog Solitude

Yep... You're right.
(Hmm... Why are the current version of DRM and the only available Mesa ebuild hard masked?

)

RoadRunner · Posted: Mon Feb 14, 2005 12:02 am Post subject:

That's easy to reply =)

Check /usr/portage/profiles/package.mask:

firephoto · Posted: Thu Feb 17, 2005 11:21 pm Post subject:

Ok I'm trying to get better performance with X on my thinkpad 20 so I need dri-drm I suppose and the instructions here seem to be chaning as the weeks pass so I need a little help.
I have xorg-x11-6.8.2. emerged and x11-drm-20050104 but as I've come to the conclusion my system is still using the Xorg dri and drm. I'm re-emerging xorg-x11 with the "insecure-drivers" option now since I saw that mentioned above and it mentions savage in the use.desc but I'm pretty sure I need more.

firephoto · Posted: Sat Feb 19, 2005 3:52 am Post subject:

I got it working finally.
I removed x11-drm, followed the gentoo guide for that, went to the dri cvs guide and followed that for a binary install from a snapshot. Installed the Xorg and the modules binary packages (once I had a lesson in where xorg gets emerged to now), installed the "common" package, installed the "savage" package. I'm not sure if I need to really install them like I did or just copy the modules to their proper homes but I used the install.sh script with both and it worked. When I first tried it the system locked up and was stuck, magic-sysrq was no help so I powered off and started back up searching for clues. Made sure the proper modules were loading (I have a savage.ko in 2 places) and the proper ones were loading. Did some more lookin and grep'n and finally just tried it and it worked. Agp was set to 1x at first but I got the set in my xorg.conf to 2x now. Way better than before, no more cpu load from moving the pointer around.

I'm getting this with a default glxgears window.

Beleaguered · n00b Joined: 06 Jan 2003 Posts: 19

Do the cvs builds of xorg-x11 and xorg-drm from fluidportage work? I'd still need a meas from cvs, right?

salivian · Tux's lil' helper Joined: 15 Sep 2002 Posts: 91

One question is "Do you want a complete CVS of X?"

Current DRI-cvs building instructions just bulid a minimal Xserver with updated 2D drivers and OpenGL libs , no fonts and special extensions.
I think the DRI folks just don't want to touch (DRI unnecessary) X components that are stable.

firephoto · Posted: Thu Mar 03, 2005 3:31 am Post subject: [SOLVED]

I can't get the savage.ko module to load after updating my kernel to 2.6.11-ck1. I get these errors.

odocoileus · n00b Joined: 27 Dec 2004 Posts: 45

Ok, I read these five pages, and I have no clue, can someone break it down for me? Please? Someone linked to http://www.gentoo.org/doc/en/dri-howto.xml#configure_xorg and I followed it, but it didn't work. After reading more, I am under the impression that I need more current versions? If so do I need to remove just the xorg-drm, or X altogether? Do I just follow the instructions on http://dri.freedesktop.org/wiki/Building? And finally, I didn't see anyone mention the savage drivers under i2c hardware in the kernel config, should I use that or not? And if so, which one...One lists the supported chip as '...8365...aka savage4' (the numbers match my lspci) the other one says it supports savage4... how confusing is that?

odocoileus · n00b Joined: 27 Dec 2004 Posts: 45

firephoto · Posted: Wed Mar 09, 2005 7:36 pm Post subject:

I got the drm and savage module working with 2.6.11, I had CONFIG_DRM=y selected in my kernel.

odocoileus:
I just have the latest xorg-x11 from portage installed then I use the drm instructions and install the the drm enabled xorg X server over the emerged one and then build the drm and savage modules.

http://dri.freedesktop.org/wiki/Building is the way to do it, you can use the snapshots though if you don't want to build all the parts. I used the files from
http://dri.freedesktop.org/snapshots/extras/ instead of building those.

I wish there was an ebuild that wrapped all the necessary things together so it would be just a simple "emerge savage-drm" and you'd get the proper X server, mesa, drm, and savage parts. I guess when xorg gets split into pieces it won't be such an issue and maybe an ebuild will work better then.

dom_ · n00b Joined: 30 Apr 2004 Posts: 50

edit : i am using an omnibook xe3gc with S3 Inc. 86C270-294 Savage/IX-MV rev 19

I did not succeed having dri with xorg-x11 6.8.2-r1 and x11-drm 20050104 nor with latest cvs of dri.

But the snapshot from http://dri.freedesktop.org/snapshots/savage-20050225-linux.i386.tar.bz2 did it.
glxinfo
name of display: :0.0
display: :0 screen: 0
direct rendering: Yes

So dri is working with this snapshot, the xorg-x11 and gentoo-dev-source from portage.

I just have questions for the use flags to build xorg. What are dlloader, dmx for ?
Second question is about the doc flag, what the extra doc contains ?
and the last one is for USE_INPUT_DEVICES flag, are this flags used in the build process as i
will need his wacom functionnality ?

here is my uses :

equery uses xorg-x11
[ Searching for packages matching xorg-x11... ]
[ Colour Code : set unset ]
[ Legend : Left column (U) - USE flags from make.conf ]
[ : Right column (I) - USE flags packages was installed with ]
[ Found these USE variables for x11-base/xorg-x11-6.8.2-r1 ]
U I
- - 3dfx : Adds support for 3dfx video cards to XFree86. See: voodoo3
- - 3dnow : Adds support for 3dnow multimedia processor instructions
+ + bitmap-fonts : <unknown>
- - cjk : Adds support for Multi-byte character languages (Chinese, Japanese, Korean)
- - debug : Tells configure and the makefiles to build for debugging. Effects vary across packages, but generally it will at least add -g to CFLAGS. Remember to set FEATURES=nostrip too
- - dlloader : <unknown>
- - dmx : <unknown>
- - doc : Adds extra documentation (API, Javadoc, etc)
+ + font-server : <unknown>
- - hardened : activate default security enhancements for toolchain (gcc, glibc, binutils)
- - insecure-drivers : <unknown>
+ + ipv6 : Adds support for IP version 6
- - minimal : Install a very minimal build (disables, for example, plugins, fonts, most drivers, non-critical features)
+ + mmx : Adds support for optimizations for Pentium MMX and Athlon class processors
+ + nls : <unknown>
+ + opengl : Adds support for OpenGL
+ + pam : <unknown>
- + sdk : <unknown>
+ + sse : fast floating point optimization for PentiumIII+ class chips
- - static : !!do not set this during bootstrap!! Causes binaries to be statically linked instead of dynamically
+ + truetype-fonts : <unknown>
+ + type1-fonts : <unknown>
- - uclibc : Enable uclibc specific patches and build or link uclibc
- - xprint : Support for xprint, http://www.mozilla.org/projects/xprint/
+ + xv : Adds in optional support for the Xvideo extension (an X API for video playback)
- - debug : Tells configure and the makefiles to build for debugging. Effects vary across packages, but generally it will at least add -g to CFLAGS. Remember to set FEATURES=nostrip too

@+
dom

salivian · Tux's lil' helper Joined: 15 Sep 2002 Posts: 91

I guess the experience is similar.

the current DRI,xc ... 10-Mar-2005 does not work....

2005-02-18 works fine for me
add -D 2005-02-18 to cvs command will set the time tag.

AIgor · Posted: Fri Mar 11, 2005 10:13 am Post subject:

Uhm... The current cvs version (installed on 9-mar-2005) works for me... also the new option DmaMode... I should write here the installation steps, but now I must work :evil:

. Wait me...