Radeon Gallium on ubuntu

[hmmm]

Wow did you just update the info on the page?

BTW while I've got your attention sarvatt - a big thankyou to you, tormod and the rest of the xorg-edgers team for the ppa!!!

[Sarvatt]

Will this land in the normal xorg-edgers PPA for Maverick?

It's been in there for awhile, in the libgl1-mesa-dri-experimental package. It's installed to /usr/lib/dri/gallium/ though so you'll need to use env vars to test it out or replace your /usr/lib/dri/r600_dri.so with it if you're just silly. Not that I recommend the latter All of that is mentioned in the notes on the main PPA page.

[hmmm]

I don't have the hardware to test if it is any useful, but the mesa packages in the Radeon Gallium PPA ppa:xorg-edgers/radeon ships the r600g now. Please remember that it is to be used on top of stock Lucid (not the normal xorg-edgers PPA), and you probably will need to install the latest Maverick kernel and the -ati drivers from ppa:xorg-edgers/drivers-only to get anywhere.

Will this land in the normal xorg-edgers PPA for Maverick?

[hobbes]

I noticed this messages on dmesg:

[ 2795.089924] radeon 0000:01:00.0: ffff880048749600 reserve failed for wait
[ 3273.494269] radeon 0000:01:00.0: ffff880048749600 reserve failed for wait
[ 3285.863913] radeon 0000:01:00.0: ffff880048749600 reserve failed for wait
[ 3310.732791] radeon 0000:01:00.0: ffff880048749600 reserve failed for wait
[ 3336.425249] radeon 0000:01:00.0: ffff880048749600 reserve failed for wait
[ 3336.890328] radeon 0000:01:00.0: ffff880048749600 reserve failed for wait
[ 3337.406172] radeon 0000:01:00.0: ffff880048749600 reserve failed for wait
[ 3337.590795] radeon 0000:01:00.0: ffff880048749600 reserve failed for wait
[ 3393.944474] radeon 0000:01:00.0: ffff880048749600 reserve failed for wait

Someone at #radeon hinted me about possible vram leaking.

Hope that could shed some light into it.

[hobbes]

Hi,

I own a X1600 pro (AGP) / Pentium D 2.8 Ghz. Using the very latest xorg-edgers packages and a 2.6.36 -Rc2 mainline ubuntu kernel. (Maverick Meerkat)

I can play HD videos (720p) with compiz disabled.

But, if I try to watch it with Compiz (Gallium 3d is also enabled) on the movie playback starts to freeze at 8 ~10 min. (audio goes on ..) and everything else (video related) starts to consume too much CPU, even a youtube SD video, forcing me to restart.

Is that a know bug?

[zand]

Hello, i'm having a trouble with panoramio pictures in google-earth (they aren't displaying, just white area with small googleearth icon in the middle). Must have smth to do with 2D rendering. I'm using r300g driver from git.
So, how is it possible to chage 2D prferences in ati-gallium stack?

[tormod]

Dear tormod and sarvatt,

what is your plan, when will you add the r600g driver to the xorg-edgers ppa? It can already run glxgears and ioquake games (if I remember correctly), so it might be in a state to start testing it/regularly checking out how it evolves.

Thanks in advance!

I don't have the hardware to test if it is any useful, but the mesa packages in the Radeon Gallium PPA ppa:xorg-edgers/radeon ships the r600g now. Please remember that it is to be used on top of stock Lucid (not the normal xorg-edgers PPA), and you probably will need to install the latest Maverick kernel and the -ati drivers from ppa:xorg-edgers/drivers-only to get anywhere.

[nanonyme]

what is your plan, when will you add the r600g driver to the xorg-edgers ppa? It can already run glxgears and ioquake games (if I remember correctly), so it might be in a state to start testing it/regularly checking out how it evolves.!

Sounds like a good idea especially if the Gallium driver gets installed into the gallium subdirectory of dri so it won't get used as default but user has to enable it himself.

[HokTar]

Dear tormod and sarvatt,

what is your plan, when will you add the r600g driver to the xorg-edgers ppa? It can already run glxgears and ioquake games (if I remember correctly), so it might be in a state to start testing it/regularly checking out how it evolves.

Thanks in advance!

[kihon]

Had same problem - the latest update seems to have fixed it.