Hallo,
recently I found, X.org is not idiot-proof. Today I have booted up and my PC was almost useless. X server took around 80% of CPU usage. Suitable solution was to remove xcompmgr - X server is in normal with CPU, but eats a lot of memory (understand - more than usual). And also performance in glxgears is much lower (8-9x).

I'm using X.org 1.7.3.901, graphic card ATI Radeon 9200 with "radeon" driver. My WM is Openbox (current version from Arch repository).

Some info from log:

[michal@arch-linux ~]$ cat /var/log/Xorg.0.log |grep EE
(EE) Failed to load module "record" (module does not exist, 0)
(EE) RADEON(0): [dri] RADEONDRIGetVersion failed because of a version mismatch.

[michal@arch-linux ~]$ cat /var/log/Xorg.0.log |grep WW
(WW) AllowEmptyInput is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
(WW) Disabling Mouse0
(WW) Disabling Keyboard0
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
(WW) Warning, couldn't open module record
(WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
(WW) RADEON(0): Direct rendering disabled

And my xorg.conf - section Device (I think the most useful)

Section "Device"

Identifier "Card0"
Driver "radeon"
VendorName "ATI Technologies Inc"
BoardName "RV280 [Radeon 9200]"
BusID "PCI:1:0:0"

EndSection

And maybe I should say - I have almost original version of xorg.conf from "# X -configure". Yesterday I had a bit tweaked, but it stoped working. And of course - I have no backup .

Really I don't know, what I have done or not, maybe new version of X.org? Yesterday evening was everything ok. Than the electricity fell and I went sleep.


I really appreciate any help, link to google or just "kick" into the right way.

--
P.S. Sorry for my English

Can you attach your full /var/log/Xorg.0.log to a post here?

EDIT: Just to explain... You have no direct rendering, which drastically slows down composite and 3D rendering. The full log file should reveal more.

Adam

Sure, here you are: http://kvaky.net/nahrano/Xorg.log

And, again, thank you for your response.

Well apparently Xorg isn't even working at all. You don't appear to have the radeon driver installed. It's probably in a package called something like xf86-video-ati. Can you try (re)installing it and starting X again?

Adam

The performance is the same - still around 110 FPS. Here you are log from X.org - http://kvaky.net/nahrano/Xorg.0.lo

Looks to me like you have KMS enabled in the kernel? If that's the case, you need to build libdrm with support for KMS (via the --enable-radeon-experimental-api option) and then rebuild xf86-video-ati and, possibly, Mesa.

Alternatively, you could reboot with the radeon.modeset=0 option to the kernel (disabling KMS) and see if direct rendering then works.

Adam

I think it's not a solution. Yesterday and days before was everything ok. My FPS was around 900 (after I installed xf86-video-ati - as you had advised me). Do you think the xorg.conf will told us something more? (In this case - here it is: http://kvaky.net/nahrano/xorg.conf)

And direct rendering - X.org probably tells something else, than glxinfo, see.
[michal@arch-linux ~]$ glxinfo |grep render
direct rendering: Yes

EDIT: And where can I find, what I have enabled in kernel?

No, I am quite certain that your xorg.conf has nothing to do with this. The fundamental problem is this:

I've really only seen that recently when KMS is involved. What is the output of 'cat /proc/fb'? Please show the output of 'dmesg'.

Adam

Ok, I don't know, here you are the outputs

[michal@arch-linux ~]$ cat /proc/fb
0 radeondrmfb

And dmesg: http://kvaky.net/nahrano/dmesg

Thank you for your patience

So you are using KMS, then. Please try that test I suggested earlier and reboot with radeon.modeset=0 or nomodeset as a kernel option.

Adam

1 members found this post helpful.

Adam, you are really such a great wizard! Again, you have solved my problem. Thank you a lot.

Btw. radeon.modeset=0 changed only the size of letters in console (during boot and after pressing ctrl + alt + fx). The second option (nomodeset) was correct - my actual FPS is around 1500. I can't belive... ) Thank you.

No problem. You can keep kernel modesetting if you update various components (such as libdrm, xf86-video-ati, and Mesa) but that can be a PITA :-)

Adam