Re: The AMD/ATI Bar & Grill

I removed xorg-server-1.8-catalyst-maximize-fix and tried the vanilla version, no luck. Window resizing is still painfully slow.

Which "patched-xorg" is better to use ??

Vi0L0 wrote:

Gillian00 wrote:

Sometimes and with no apparent reason, xorg is working hard and eat 100% of one cpu. Then I have to kill X and take a new session. How can I know if it is a xorg problem or a application problem or a kde problem or a catalyst problem ?

Well... it's not easy to get such information, because to investigate it you will have to involve debugging, tracing, mapping and other developing tricks. And even for good developer it's sometimes hard to tell whats causing the problem...

So i suggest you to do some easier things like:- disabling some kde features/services (like plasma elements or powerdevil) or kwin's effects or kwin's settings- playing with amdcccle- if you are still observing high CPU usage i guess you should search web for fixes (sometimes it's related with hardware like gpu or mobo, so it's good to provide such info in search query)

Also maybe you are catching some X server lockup, and high cpu is just a side effect for this. You should look up at /var/log/Xorg.0.log for some errors. Plus look at /var/log/kdm.log and if there is something similar to "stuck in an infinite loop" related with a date when you experinced high cpu usage - it's most probably an X bug, and you should fill bug report. If you dicide to fill bug report - be sure to name it as "xserver lockup', not 'high cpu usage'.

Re: The AMD/ATI Bar & Grill

After struggling for a good 4 hours with kernel update, catalyst 10.9 upgrade and finally xorg-server-1.8-catalyst-maximize-fix update I'm a having a super fast and stable KDE SC.Also, I installed catalyst-hook - I prefer this way over daemon way.

Re: The AMD/ATI Bar & Grill

KMS and Catalyst

Is there any way to use KMS with Catalyst? Since I have 23" wide monitor native framebuffer resolution 1440x1050 makes tty fonts ugly and hard to read but with KMS enabled I get full screen resolution support with tiny fonts looking nice - and easy on eyes. However seems there's no way to use KMS while using Catalyst instead open-source modules...

Re: The AMD/ATI Bar & Grill

msx wrote:

KMS and Catalyst

Is there any way to use KMS with Catalyst? Since I have 23" wide monitor native framebuffer resolution 1440x1050 makes tty fonts ugly and hard to read but with KMS enabled I get full screen resolution support with tiny fonts looking nice - and easy on eyes. However seems there's no way to use KMS while using Catalyst instead open-source modules...

No. I'm pretty sure that there will be no such support, ever (same for nvidia's drivers).

Re: The AMD/ATI Bar & Grill

Today i wanna show you something i have been working on lately. xmL throw idea that maybe we could use makepkg inside catalyst_build_module script to build catalyst packages with fglrx modules inside, and i just coded it.I'm showing you this (actually tested only by me) "project" right now, because in just a few days i'm gonna go for a trip, i will be afk for i dunno a week maybe little longer, and i don't wanna wait so long with this

Basically it's modified catalyst_build_module script able to generate catalyst-{kernver} package(s) (with only fglrx module inside) and install/upgrade it (+ some other files like pkgbuild for catalyst-{kernver} package).By catalyst-{kernver} i mean ie. catalyst-2.6.35-ARCH package for kernel 2.6.35-ARCH, or catalyst-2.6.36-rc5-mainline package for 2.6.36-rc5-mainline kernel, and so on...

It's building those packages as unprivileged user and you will be asked which user exactly after typing catalyst_build_module command (so it's safer than catalyst_build_module known from hook or daemon). Also fglrx modules built by this generator should "fit" to you hardware more precisely (because of makepkg).Since it's using pacman to install packages you may easily manage catalyst's packages generated by it. You may ie. remove catalyst-2.6.35-ARCH with pacman -R catalyst-2.6.35-ARCH command.

Of course such commands like:- catalyst_build_module remove- catalyst_build_module remove_allor- catalyst_build_module some_kernel_version- catalyst_build_module allshould also work fine, but now on packages .

It's not another auto re-compilation solution(!), you must to use it manually.Catalyst-hook isn't able to work with it because there cannot be more than 1 pacman instance running (pacman -Syu is 1 instance, there's no place for another).I modified catalyst-daemon to use it, but with it daemon is starting in like 15-20s when it need to build a module, so i think it's too long... maybe xmL will figure out how to speed it up, but for now he's busy.

So umm... it's just some idea and some project, maybe you will find it useful, maybe you can show me a way to make it more useful .

Oh and don't forget to run catalyst_build_module as a root after installing catalyst-generator package.

Plus - yes, after typing 'catalyst_build_module' or 'catalyst_build_module all' - it will build AND install/upgrade package(s).

Re: The AMD/ATI Bar & Grill

Did anyone's tearing issues get fixed with this release?

I thought it was the Direct2d acceleration, so I set ForceXAA to true and rebooted to test, and it's not tearing, either. I've switched resolutions, refresh rates, jiggled windows with videos playing, and the tearing is just gone.

Also, is anyone's Xorg.0.log being spammed with a "timer =" messages. I'm getting it in both my slim.log and Xorg.0.log from X. It's possible the new slim version is causing/doing it or it might be fglrx. They're the only two Xorg-related packages I've updated in a while.

Re: The AMD/ATI Bar & Grill

ragnarok2040 wrote:

Did anyone's tearing issues get fixed with this release?

I thought it was the Direct2d acceleration, so I set ForceXAA to true and rebooted to test, and it's not tearing, either. I've switched resolutions, refresh rates, jiggled windows with videos playing, and the tearing is just gone.

Also, is anyone's Xorg.0.log being spammed with a "timer =" messages. I'm getting it in both my slim.log and Xorg.0.log from X. It's possible the new slim version is causing/doing it or it might be fglrx. They're the only two Xorg-related packages I've updated in a while.

Looks like you gained known from open source ati driver "v-sync to v-blank" functionality

Can you show me a file generated by your /usr/sbin/atigetsysteminfo.sh ?

Here it is. My kernel is patched with the BFS scheduler, and uses a custom configuration, since the stock kernel used to segfault on me. I haven't tested the stock kernel since .28 or so. My specific video card is a VisionTek HD4850 made around June/July of '08.

Re: The AMD/ATI Bar & Grill

Check these comments on phoronix forum

"In maverick repositories just landed fglrx driver with xserver 1.9 support and fixed vertical synchronization !!!!"" THE GAUSSIAN BLUR IS WORKING! Docky is working a slow as hell with it, but ITS WORKING!"

ok, will check this out , new catalyst will probably land in catalyst-test package, but first i wanna say LOL...

@ragnarok2040:you have got same cpu and same gpu as me even my gfx's bios is just a few days newer, and yes - i also got this strange timer spam in Xorg log...basically only our xorg.conf files were different so i've generated new one with aticonfig.... and... LOOOOOOOOL!You are right! v-sync is always working, simply always, i cannot believe this...

msx wrote:

Hi Vi0L0, today I used Yaourt to update AUR's packages and I get this:

Packages that were installed as dependencies but are no longer required by any installed package: catalyst-hook

May be I'm wrong but this package shouldn't be removed, right?

Well, if you like auto re-compilation - you need it. There's no dependencies, but indeed - catalyst won't work without fglrx module (which is provided by catalyst, catayst-daemon, catalyst-generator or catalyst-hook )

@Cdh:i hope that there will be day when oss radeon will kick catalyst's ass on every dimension and we will all migrate to it! Good luck mate!

Re: The AMD/ATI Bar & Grill

Re: The AMD/ATI Bar & Grill

Sadly it's looking like v-sync in this new ubuntu's catalyst isn't always working like in 10.9 (i mean: it's good, it's working, but not always - so not for "un-fullscreened" movies/flash videos when composite is on)... so personally i will roll back to 10.9, and wait with the update until xserver 1.9 will land in [extra]