HOWTO: Radeon 9500 (and newer) with DRI

Message

MADevil · Post by **MADevil** » Mon Jan 15, 2007 1:37 am

the PARSE and USE files are here for all the packages. and PROVIDE contain the packages which emerge complain (>=media-libs/mesa-6.5.2 for mesa-9999 .....). It's only esthetic , but that's distubs me , i'm maniac. / EDIT : Fixed since 16/01

And each time i rsync mesa-cvs , all my 'digest-ok-for-me' are replaced by others don't work for me. Primozic , can you redigest this ebuilds please ?

txboy · Post by **txboy** » Wed Jan 17, 2007 12:52 pm

After asking at DRI mailing list, I found a solution for my GL_MAX_TEXTURE_SIZE limit (mergedfb & dualhead & beryl).
Just editing the src/mesa/main/config.h and changing the MAX_TEXTURE_LEVELS to 13 did the trick.
Now my system shows 4096 as max texture size.
The texture covers the screens without problems but now the desktop background goes white, only the desktop background. Rest of desktop is showed right.

I've tried changing MAX_TEXTURE_RECT_SIZE, which also was 2048, to 4096 and get a background, but a deformed background.

Any help at this point ?

Beinii · Post by **Beinii** » Wed Jan 17, 2007 12:54 pm

Wow... AIGLX + Beryl works very smooth with current version

But what's with the memory usage of X? Machine has been up for a day and X uses 330Mb of RAM

txboy · Post by **txboy** » Wed Jan 17, 2007 1:35 pm

Beinii wrote:Wow... AIGLX + Beryl works very smooth with current version

But what's with the memory usage of X? Machine has been up for a day and X uses 330Mb of RAM

How can I check that memory usage ?

n0rbi666 · Post by **n0rbi666** » Wed Jan 17, 2007 1:47 pm

Check memoru usage with

Code: Select all

free -m

Beinii: do you have in xorg.conf

Code: Select all

Option GartSIZE "64"

??

Beinii · Post by **Beinii** » Wed Jan 17, 2007 3:46 pm

n0rbi666 wrote: Beinii: do you have in xorg.conf
Code: Select all
Option GartSIZE "64"
??

Yes, I do...

txboy · Post by **txboy** » Wed Jan 17, 2007 3:54 pm

Beinii wrote:But what's with the memory usage of X? Machine has been up for a day and X uses 330Mb of RAM

Checked free ram with & without beryl and the difference is about 65Mb only.

n0rbi666 · Post by **n0rbi666** » Wed Jan 17, 2007 4:28 pm

Beinii - so GARTSize "64" consumes 64MB of memory for all the time ... try to turn it off, and see, what will happen

Beinii · Post by **Beinii** » Wed Jan 17, 2007 4:40 pm

n0rbi666 wrote:Beinii - so GARTSize "64" consumes 64MB of memory for all the time ... try to turn it off, and see, what will happen

Alright, I will check that later...

To the Txboy... I have almost the same results, around 60mb lower than with beryl... but the usage of X is still little high even without beryl it is at 278Mb.

Well.. i don't know whats the normal usage with AIGLX. Im just comparing the results to FGLRX drivers and Xorg 7.1 Stable...

Jesterhead · Post by **Jesterhead** » Wed Jan 17, 2007 6:26 pm

hmmm

# free -m
total used free shared buffers cached
Mem: 503 459 44 0 54 179

most memory is normally allocated for buffers, so if you are low on memory this doesnt mean that an app needs much..

Beinii · Post by **Beinii** » Wed Jan 17, 2007 8:36 pm

I checked the memory usage of X using top.

Right now it uses 30% of memory. ~290mb

Whole system:

Code: Select all

             total       used       free     shared    buffers     cached
Mem:          1000        978         21          0          0        367
-/+ buffers/cache:        611        389
Swap:         2000        114       1886

kernelOfTruth · Post by **kernelOfTruth** » Wed Jan 17, 2007 10:08 pm

@prymitive:

you've enabled DynamicClocks in your xorg.conf, is this working for you?

Option "DynamicClocks" "1"

I mean does this improve battery time ?

I'm considering in switching to the opensource radeon drivers (Mobility Radeon x600), ATI's driver support is crap

, if they achieve NVIDIA's level perhaps I'll switch back ...)

Thanks in advance

Kovid · Post by **Kovid** » Thu Jan 18, 2007 4:10 am

Hi all,

I have two monitors 1680x1050 and 1280x1024 powered by an X300. At the moment with both ATI Big desktop and MergedFB, direct rendering works only upto the 2048 boundary. Is there any way to stretch it beyond that boundar. Reading txboy's post above leads me to hope that there is.

tontudelbot · Post by **tontudelbot** » Thu Jan 18, 2007 2:49 pm

kernelOfTruth wrote:@prymitive:

you've enabled DynamicClocks in your xorg.conf, is this working for you?

Option "DynamicClocks" "1"
I mean does this improve battery time ?

I'm considering in switching to the opensource radeon drivers (Mobility Radeon x600), ATI's driver support is crap , if they achieve NVIDIA's level perhaps I'll switch back ...)

Thanks in advance

I don't know if DynamicClocks improve battery time because i don't have a laptop (it should i think), but yes, it works (almost in my 9600)

n0rbi666 · Post by **n0rbi666** » Fri Jan 19, 2007 8:24 am

Hm, when I try to execute glxgears, I have an error:

Code: Select all

libGL warning: 3D driver claims to not support visual 0x4b
X Error of failed request:  BadRequest (invalid request code or no such operation)
  Major opcode of failed request:  156 (DAMAGE)
  Minor opcode of failed request:  4 ()
  Serial number of failed request:  37
  Current serial number in output stream:  38

I've tried to recompile mesa, mesa-progs, libdrm, x11-drm, xf86-video-ati and xorg-server - but that does'nt help ...

txboy · Post by **txboy** » Fri Jan 19, 2007 9:44 am

txboy wrote:After asking at DRI mailing list, I found a solution for my GL_MAX_TEXTURE_SIZE limit (mergedfb & dualhead & beryl).
Just editing the src/mesa/main/config.h and changing the MAX_TEXTURE_LEVELS to 13 did the trick.
Now my system shows 4096 as max texture size.
The texture covers the screens without problems but now the desktop background goes white, only the desktop background. Rest of desktop is showed right.
I've tried changing MAX_TEXTURE_RECT_SIZE, which also was 2048, to 4096 and get a background, but a deformed background.

Any help at this point ?

Does someone know any help? Maybe some patch to try?
I know there was a white cube patch.

Thanks in advance.

Primozic · Post by **Primozic** » Fri Jan 19, 2007 3:20 pm

n0rbi666 wrote:Hm, when I try to execute glxgears, I have an error:
Code: Select all
libGL warning: 3D driver claims to not support visual 0x4b
X Error of failed request:  BadRequest (invalid request code or no such operation)
  Major opcode of failed request:  156 (DAMAGE)
  Minor opcode of failed request:  4 ()
  Serial number of failed request:  37
  Current serial number in output stream:  38
I've tried to recompile mesa, mesa-progs, libdrm, x11-drm, xf86-video-ati and xorg-server - but that doesn't help ...

I was wondering if someone else was going to come across this...

You will need to downgrade to x11-libs/libXdamage-1.0.4. It's no longer in the Portage tree, but it's in the overlay.

I've backported several patches to make xorg-server-1.9.99.999 compatible with the new XDamage protocol, but they are rather large and cumbersome. They work, as I've been using them all week, but I'm not sure if I should include them in the overlay.

phuber · Post by **phuber** » Fri Jan 19, 2007 4:06 pm

Hi Primozic

I've been out of the loop for a while, trying to get up to speed -- I read about this beryl thing and lots of new useflags. I guess your readme at sturmartillerie is a bit out of date?

n0rbi666 · Post by **n0rbi666** » Fri Jan 19, 2007 5:16 pm

Primozic wrote:I was wondering if someone else was going to come across this...

You will need to downgrade to x11-libs/libXdamage-1.0.4. It's no longer in the Portage tree, but it's in the overlay.

I've backported several patches to make xorg-server-1.9.99.999 compatible with the new XDamage protocol, but they are rather large and cumbersome. They work, as I've been using them all week, but I'm not sure if I should include them in the overlay.

Ok, downgrading libXdamage and reemerging mesa helped

ThX

(You could put these patches in some kind of experimental overlay ?

)

phuber · Post by **phuber** » Sun Jan 21, 2007 9:37 am

Ok I think I've gotten pretty far but now I could use some help:

- I reinstalled the mesa-cvs stuff including xorg-server-1.99.999 anf xf86-video-ati-9999
- 2800fps in glxgears

Now I went on and installed beryl (9999 versions) from the xeffects overlay, following the official install instructions: http://wiki.gentoo-xeffects.org/Beryl
- Now I just get a white screen after starting. The xeffects blog suggests to recompile pango but that doesn't help.
- I've been playing with xorg.conf a bit but that doesn't help either
-> How do I solve that?

I also have a few general questions:
- What are xf86-video-nouveau-9999 and xf86-video-xgi-9999 for? Do I need these?
- Do I need libtxcdxtn?

---

I'll now try to rebuild a few packages, using the USE flags a few pages back. Using this as packages.use
=x11-base/xorg-server-1.1.99.999 beryl exa aiglx -nptl
=media-libs/mesa-9999 -nptl
=x11-base/x11-drm-9999 tools
=x11-drivers/xf86-video-ati-9999 patch exa modesetting

emerge xf86-video-ati x11-drm mesa xorg-server

phuber · Post by **phuber** » Sun Jan 21, 2007 10:20 am

ooohhh... it works!!! so cool

Phlogiston · Post by **Phlogiston** » Sun Jan 21, 2007 11:58 am

phuber wrote:ooohhh... it works!!! so cool

Please tell us how you did it: Attach all configs and list the versions you installed. What hardware are u running?

Phlogiston · Post by **Phlogiston** » Sun Jan 21, 2007 12:13 pm

As I see some guys in this thread really managed to get beryl +r300 to work. Because its a bit difficult to find out how and to follow this thread I thought its a good idea to start a new thread for reporting successful installations of beryl + ati radeon r300

Thanks a lot for reporting there!

Phlogiston · Post by **Phlogiston** » Mon Jan 22, 2007 9:25 am

Today I emerged latest stuff again and came across the following trouble:

-X won't start when using x11-drivers/xf86-video-ati-9999 (with or without that patch useflag), downgrading to x11-drivers/xf86-video-ati-6.6.3 solves that issue

a hint to the creator of that ebuild: It would be better to use a more specific name for that patch useflag, because there is already an official useflag called patch.

Something else: Does anyone know how I can get back my normal key combinations in kde when running beryl(-manager)?

I especially mean the very handy ctrl-alt-esc to kill an app? Why does that not?

Thanks

phuber · Post by **phuber** » Mon Jan 22, 2007 6:32 pm

I noticed that too, most key-combinations have changed. You can run beryl-settings and then change the key combinations. Alternatively, you could write a kde-based beryl

HOWTO: Radeon 9500 (and newer) with DRI

mergedfb + dualhead