as for Xorg.0.log:

OK, so it looks like your X server is disabling direct rendering for some reason. Your /var/log/Xorg.0.log and the output of 'dmesg | grep drm' would help.

EDIT: You beat me to it with the Xorg log file. I suspect I know what's going on, but dmesg should tell us.

Adam

ok here is

Well this is almost certainly the problem:

Driver vs. GPU issue, perhaps? I can only suggest that an updated kernel might fix that problem, but that's just a guess. I've sent out a query on #radeon on Freenode, where the developers typically hang out, but have not heard back yet if they know what that error means.

Adam

1 members found this post helpful.

at least we have a starting point..
peronally, I don't have any clue about the startup sequence of gpus or what ring_test and cp_init are..

however I am using a 2.6.35.7 kernel at the moment... so not much to update there.
if you do have feedback from them, please let me know and I will attempt to incorporate possible changes in the morning

Thank you for digging in

Well there's always 2.6.36 but, yeah, 2.6.35.7 is pretty damn new. Sorry I missed that in our Xorg log file.

The 'cp' error is referring to the command processor for the video card. Without control over it, the kernel DRM can't provide acceleration, hence the problem. So we know this is an issue with the kernel and not the Xorg driver, at least.

This isn't a Xen kernel, is it? I see a number of similar errors on google coming from xen-devel, but your kernel doesn't have xen in the name, which is usually the case. Was this taken after a cold boot?

Adam

For the guys with "DRM smoking too much weed", the 2.6.36 kernel will be the Heaven | Hell, because the massive changes/improvements on the DRM drivers. Take a look on the running a 2.6.36 kernel.

This is a laptop computer and a rather old one I might add (from about 2k4 not exactly sure when it was bought). The processor is Intel Centrino (Pentium M). so no virtualization stuff going on. unless I enabled something wrong in the kernel but there seems nothing Xen (fgrep -i xen /boot/config) related and as for KVM (in case it has something to do with it):

Well Maybe I can try disabling this too in a kernel.

@Darth Vader: Wheree did you read about these changes? cause I only found this related to KMS and It only includes intel gpus at the moment http://kernelnewbies.org/LinuxChange...34c7c848f79792 (1.3 - KMS+KDB integration)

@nass Well, the changes on Radeon DRM are important, I don't known why they missed it.

Then, the 2.6.36 kernel is the first shipped with the Radeon/KMS 2.6.0, instead of the ol'good 2.5.0 version, previously used by the 2.6.3x series...

well thats worth a shot for sure.
I'll let you know if things are different.

nope the error persists with a fresh 2.6.36 kernel... pity

Ouch! This is most probably, an old R300 bug, still not fixed.

Then, try the top Mesa (a current git build) with Gallium support. Your video card use the R300 driver, right?

Well, the current git Mesa have a new&fresh R300 stable driver, using the next-gen system (Gallium).

You need as dependencies: updated util-macros, libdrm, (lib)talloc and very important! LLVM.

Compared to a standard build, I suggest to use those additional flags for Mesa's ./configure: --enable-gallium --enable-gallium-llvm --enable-gallium-swrast

Also, use a git build for xf86-video-ati.

<edit>

Another interesting flag is "--enable-gallium-radeon", wich build a new Radeon (R300) DDX driver (something like xf86-video-ati), on top of Gallium. But, I don't have a R300 video card to test it.

Anyways, looks like in future the video drivers will be integrated in Mesa, simplifying the 2D/3D stack.

well I am not sure which driver... :S
I mean
the card is "ATI Mobility Radeon X300".
the code name is "RV370"
and the model name is "M22"
according to wikipedia http://en.wikipedia.org/wiki/Compari..._Radeon_Series

and Xorg.o.log from above states:
so how do I check to tell you if I am using more than the "radeon" driver ?

"glxinfo | grep OpenGL" will say the used Mesa driver.

BUT, for sure this is a videocard wich use the R300 Mesa driver. SO, because you use the latest DRM now, we should work on rest of graphics stack.

DRM -> DDX & MESA

<edit>

Sorry! You posted the glxinfo log. And you have Mesa 7.8.1. That's version is an oldie today.

hmmm ok I have a few Questions before I start with this completely new thing for me.

1. http://mesa3d.sourceforge.net/ doesn't seem to have what we are after (i.e. anything gallium related link). So i got to http://cgit.freedesktop.org/mesa/mesa/. is that right? what i see in the top right drop down list (next to 'switch' button) is an entry for R300_DRIVER with a commit date from 2k4 (appears in the page below when you click on it). It also has quite a few gallium related entries.
In the end , do I just have to to get the new r300 driver sources??

2. ok I get util-macros from X.org and libdrm from http://dri.freedesktop.org/libdrm/ and llvm is pretty obvious.

3. I presume I 'll use --enable-gallium-radeon INSTEAD of --enable-gallium

4. xf86-video-ati.. where do I get it from ?

sorry for the newbie Q's