[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Compiz fails to start after an upgrade (software rasterizer in use)



On Wed, Nov 04, 2009 at 12:27:58 +0100, Král Gergely wrote:
> On Sat, 2009-10-31 at 14:07 +0100, Florian Kulzer wrote:

[...]

> > > (WW) RADEON(0): Direct rendering disabled
> > > (II) RADEON(0): XAA Render acceleration unsupported on Radeon 9500/9700 and newer. Please use EXA instead.
> > > (II) RADEON(0): Render acceleration disabled
> > 
> > Try to force the driver to use EXA instead of XAA and comment out all
> > XAA-related directives in your xorg.conf. (see the description of
> > AccelMethod in "man radeon")
> 
> Thanks Florian for your response. I tried using EXA instead of XAA, but
> the symptoms are the same, it is still using the software rasterizer,
> and compiz fails to start.

[...]

> (II) [drm] DRM interface version 1.3
> (II) [drm] DRM open master succeeded.
> (II) RADEON(0): [drm] Using the DRM lock SAREA also for drawables.
> (II) RADEON(0): [drm] framebuffer handle = 0xd0000000
> (II) RADEON(0): [drm] added 1 reserved context for kernel
> (II) RADEON(0): X context handle = 0x1
> (II) RADEON(0): [drm] installed DRM signal handler

[...]

> (II) RADEON(0): [DRI] installation complete
> (II) RADEON(0): [drm] removed 1 reserved context for kernel
> (II) RADEON(0): [drm] unmapping 8192 bytes of SAREA 0xf8fd9000 at 0xb7b26000
> (II) RADEON(0): [drm] Closed DRM master.
> (WW) RADEON(0): Direct rendering disabled

OK, it seems that the problem happened before Xorg complained about XAA,
and it is still present now with EXA.

> (II) RADEON(0): Render acceleration enabled for R300/R400/R500 type cards.
> (II) RADEON(0): Setting EXA maxPitchBytes
> (II) RADEON(0): num quad-pipes is 1
> (II) EXA(0): Offscreen pixmap area of 45350912 bytes
> (II) EXA(0): Driver registered support for the following operations:
> (II)         Solid
> (II)         Copy
> (II)         Composite (RENDER acceleration)
> (II) RADEON(0): Acceleration enabled

I am afraid that this is a radeon-specicific problem and that I cannot
help you further. Maybe a radeon user on the list recognizes your
symptoms?

-- 
Regards,            |
          Florian   |


Reply to: