[how-to] 3d hardware acc with ati open source driver.

[kernelOfTruth]

[pingufunkybeat]

Yes, I have DRI2 running with both 2.6.32-rc1 and the git version with the drm-next bits pulled in.

I was referring to building the kernel module from git://anongit.freedesktop.org/~agd5f/drm . AFAIK, that tree isn't being developed anymore, the drm bits are now in the kernel tree and you should switch to building the drm included in the latest kernels.

[kernelOfTruth]

[pingufunkybeat]

It's quite easy -- it's described in the RadeonBuildHowto I linked to earlier.

The only problem is waiting for the whole source to get downloaded via git without stalling (git can't resume broken downloads).

[DaggyStyle]

[pingufunkybeat]

Many things on freedesktop.org were nuked recently, which might explain the connection errors.

But regardless of that, the x11-drm ebuild has been masked for some time, and people should be using the in-kernel drm from the drm-next branch now, AFAIK.

[DaggyStyle]

[pingufunkybeat]

[DaggyStyle]

ok, I've went to the source and talked to Dave Airlie in order to geth thing straight up.
fact 1, all drm stuff went into the kernel, they are maintained directly into the kernel git.
fact 2, /home at freedesktop.org got nuked.
fact 3, agdf is traveling currently so he cannot help much.
fact 4, he probably have a copy on his hd.
fact 5, all most latest hd stuff can be located in drm-next here http://wiki.x.org/wiki/radeonBuildHowTo#head-a6271d23a9199673cea21478e0198d772a55fad3 which allows kms+3d for r6xx-r7xx.
fact 6, agdf's branch don't supports kms.

hope this clears up things.
now I haven't found any ebuild for drm-next, maybe someone could try and take a shot on creating one.
_________________
Only two things are infinite, the universe and human stupidity and I'm not sure about the former - Albert Einstein

[pingufunkybeat]

Thanks for the update.

With KMS, I prefer to build the drm stuff directly into the kernel. People were having trouble booting because you need the drm code even for the framebuffer console, and it has to be loaded at the right time, and other voodoo stuff.

[DaggyStyle]

[Kingoftherings]

[DaggyStyle]

the question is, does it have agdf's repository too?
if not, then I'll rather wait till .32 will come out or agdf will come back.
_________________
Only two things are infinite, the universe and human stupidity and I'm not sure about the former - Albert Einstein

[Kingoftherings]

[DaggyStyle]

agdf's repository is up an running again
_________________
Only two things are infinite, the universe and human stupidity and I'm not sure about the former - Albert Einstein

[Joseph K.]

OK, I'm confused. Would someone mind summarizing what the state of play is for KMS and non-KMS? That is, what are the minimum/recommended kernel, x11-drm and xf86-video-ati versions (including repository if necessary)? At the moment I'm using 2.6.31, with x11-drm and xf86-video-ati both from [x11] (the plain overlay, no modifications). From what I've just been reading, maybe I should ditch x11-drm and switch to the in-kernel DRM? Or is that only for 2.6.32? Or only for KMS? KMS sounds like too much trouble for me right now, so I'm happy to stick with non-KMS until it all settles down a bit. Thanks!

[mikkoc]

I'm assuming the vga is the one in your signature. If so, 3D/KMS support for your card is in 2.6.32.
You should use in-kernel module, since afaik x11-drm isn't maintained anymore.
To enable/disable KMS you can just pass "radeon.modeset=1/0" when booting.

[DaggyStyle]

if you are using agdf's drm, then that's the best out there currently, but kms might be a problem.
the radeon driver supports kms.
when kernel 2.6.32 will go stable, then you can safely switch.
_________________
Only two things are infinite, the universe and human stupidity and I'm not sure about the former - Albert Einstein

[Joseph K.]

[pingufunkybeat]

There are different ways to get what you need, but this is what I recommend as the most future-proof and hassle-free approach:

- Either kernel 2.6.32-rc1 or later, --OR-- a git kernel from the drm-next branch (git://git.kernel.org/pub/scm/linux/kernel/git/airlied/drm-2.6.git)
- libdrm from the X overlay (git://cgit.freedesktop.org/mesa/drm)
- mesa from the X overlay (git://anongit.freedesktop.org/mesa/mesa)
- xf86-video-ati from the X overlay (git://anongit.freedesktop.org/git/xorg/driver/xf86-video-ati)

It's the same as before, only instead of emerging x11-drm, you build a new kernel. I recommend upgrading to 2.6.32-rc1. In the future, the drm development will be in the kernel, so you'll have to switch eventually. Once you get this working, you can switch to a drm-next git kernel if you want to be closer to the bleeding edge.


If you don't want KMS:

- Turn on Drivers -> Graphics devices -> Direct Rendering Manager -> ATI Radeon (I recommend building it in, not as a module)

If you DO want KMS:

- Additionally, turn on Drivers -> Staging Drivers -> Enable modesetting on radeon by default

Install the new kernel, and voila.

KMS is very stable here, and in some ways provides a better experience, due to DRI2. Some rendering bugs are also absent with KMS. Unfortunately, a recent commit to mesa breaks some games (OpenArena, for example). If you can live with that, I think it's a good time to switch.

[Joseph K.]

Awesome, thanks pingu.

[Joseph K.]

If I want KMS (which I am warming to), should I be concerned that at the end of configuring xf86-video-ati, it says this:

[Joseph K.]

Hmmm, after upgrading to xorg-server-1.7.0 because now the video driver depends on it, mesa fails to build:

[pingufunkybeat]

[Joseph K.]