hi there, does anyone use hd2600pro card with any OS driver? Now I have a really slow scrolling in terminal and have to use laptop for work. and `Option "MigrationHeuristic" "greedy"` does nothing for me.

I'm using an HD2600 pro GPU. I stopped using the packages from Perry3D's repo a while ago due to compatibility problems at the time. Using the packages from the Arch stable repos is & has been working fine for me. I'm not a game player under Linux though.

One year ago everything was fine for me either but with some updates problems come. may I know what driver do you use and xorg settings? and whether `less -f /dev/urandom` have no delay on scroll for you? ** with this message you gave me a hope *smile*

I have been using just the standard Arch packages with no special changes on both of my machines - hd2600 pro & hd6450. Though I must say that, the hd2600 pro machine went down recently. So if there have been recent changes that have caused unreliability for the hd2600 pro I have not had the chance to experience them.

Have you tried using a different terminal app'? I use both Sakura & ROXterm these days, with not problems in either.

Do any other people using the hd2600 pro card have problems?

I think that that is an important question for obvious reasons.

Last edited by handy (2012-05-03 14:52:46)

I used to be surprised that I was still surprised by my own stupidity, finding it strangely refreshing.Well, now I don't find it refreshing. I'm over it!

Yes, you are right. It's really obvious, but compare only with more few terminals. I found out that problem somehow connected with redraw method. Unfortunately, I used only terminals significantly affected by this 'lag' (rxvt, xterm). ROXterm work fine, mlterm (I stopped at that one) and many others. Despite the fact that sometimes something draw slowly it's better than in xterm so I can ignore this.

i'm sorry, but i will no longer update the repository from the first page. As you might have noticed, I've hardly had time for it.

A big thanks for the four plus years of dedicated effort Perry, I'm sure that everyone who has benefited from this great thread, especially back in earlier days when we needed all the help we could get is also thankful for your efforts & ALL that time you donated to our community.

On another note, I guess I should shut down your space on the spiralinear.org server. I'll give it a couple of weeks then close it.

Thanks again Perry.

I used to be surprised that I was still surprised by my own stupidity, finding it strangely refreshing.Well, now I don't find it refreshing. I'm over it!

Currently there is no hardware decoding for the open source driver other than mpeg1 and mpeg2 anyway. You should be able to use the "presentation" layer from vdpau though. Not sure if it is better than xv.

A little request: Could people please give this a holyspirit (diablo clone) from aur a try and just look whether it works? http://aur.archlinux.org/packages.php?ID=59882The kernel thinks the textures are too small to render for me...

I have a HD 4870 card, and I'm not quite satisfied with the power saving. I hope you'll be able to help me.

From what I've found out, the only thing separating the (Windows) Catalyst driver and the open source driver is the clock regulation. While the proprietary driver clocks down both the core and memory to 500 MHz, the open source only clocks down the core clock. The memory, however, is still running at 900 MHz (default). This is all using KMS and the "low" power profile. How can I get the open source driver to clock down the memory as well to 500 MHz?

However; what I noticed is that the number of PCIE lanes always keeps on 16.I did find traces in the sourcecode of the radeon driver that there is code to reduce the number of active lanes, but does not seems to work for me. Anyone having any luck with that?

I have a HD 4870 card, and I'm not quite satisfied with the power saving. I hope you'll be able to help me.

From what I've found out, the only thing separating the (Windows) Catalyst driver and the open source driver is the clock regulation. While the proprietary driver clocks down both the core and memory to 500 MHz, the open source only clocks down the core clock. The memory, however, is still running at 900 MHz (default). This is all using KMS and the "low" power profile. How can I get the open source driver to clock down the memory as well to 500 MHz?

AFAIK AMD hasn't published all the documents needed in order to have the best possible power management. I don't think you can do more than what we have now unless you can code a better solution with the existing documents.

And a question. Apart from installing libtxc_dxtn from AUR and setting radeon.pcie_gen2=1 is there something more you can do with the open drivers to make them work better??