ATI Radeon R100 QD (7200) refuses to work with Compiz (Kernel 2.6.34-rc4)

[Uwe Bugla]

Am Samstag, den 24.04.2010, 12:31 -0400 schrieb Alex Deucher:
> On Sat, Apr 24, 2010 at 11:48 AM, Chicken Shack <chicken.shack at gmx.de> wrote:
> > Am Donnerstag, den 22.04.2010, 01:36 -0400 schrieb Alex Deucher:
> >> On Mon, Apr 19, 2010 at 4:25 AM, Uwe Bugla <uwe.bugla at gmx.de> wrote:
> >> > Hi,
> >> > I am running kernel 2.6.33-rc4 on a Debian Testing Squeeze release.
> >> > I have debianized the latest driver snapshot from
> >> > http://cgit.freedesktop.org/xorg/driver/xf86-video-ati.
> >> >
> >> > So I am using the ATI driver version 6.13 in connection with the latest
> >> > Radeon driver in kernel with KMS enabled.
> >> > Everything is fine so far, until I try to start Compiz:
> >> >
> >> > "drmRadeonCmdBuffer: -12. Kernel failed to parse or rejected command
> >> > stream. See dmesg for more info."
> >>
> >> What does dmesg say?  This looks like a dupe of bug 26302:
> >> https://bugs.freedesktop.org/show_bug.cgi?id=26302
> >>
> >> Alex
> >>
> >> >
> >> > This is the message when Compiz is started via "compiz --replace &"
> >> >
> >> > The card's memory is 32 MB Video RAM - it's a quite old one :))
> >> >
> >> > I do NOT use a specified xorg.conf in connection with
> >> > xserver-xorg-1.7.6, as it is a new driver where everything is being
> >> > managed via KMS.
> >> >
> >> > And that's it what Gnome's System Information spurks out under Computer
> >> > -> Display:
> >> >
> >> > Vendor          Tungsten Graphics, Inc.
> >> > Renderer        Mesa DRI R100 (R100 5144) 20090101 x86/MMX/SSE2 TCL DRI2
> >> > Version         1.3 Mesa 7.9-devel
> >> > Direct Rendering Yes
> >> >
> >> > So everything is OK except the "-12" kernel crash above, performed every
> >> > time when I try to start Compiz Fusion.
> >> >
> >> > Any idea or patches available?
> >> >
> >> > Thanks!
> >> >
> >> > If you need further information please ask me for it.
> >> >
> >> > Uwe
> >> >
> >> > P. S.: I compile the Mesa Library as described in the Internet, but with
> >> > two exceptions:
> >> >
> >> > a. I do not take the master branch, I prefer Luca Barbieri's
> >> > nvfx-next-branch instead because I need
> >> > a working solution for my two Nvidia NV34 cards, and Compiz works if I
> >> > use that branch while the master
> >> > repo is not yet compatible with Compiz.
> >> >
> >> > b. I do not take "disable-gallium" as a configure switch, I prefer
> >> > "-enable gallium-nouveau" instead because
> >> > I do need a functionable Gallium nouveau driver too when compiling the
> >> > mesa library.
> >> >
> >> > c. When will Luca Barbieri's nvfs-next-tree be synchronized with the
> >> > master tree?
> >> >
> >> > d. Is it possible that the current ATI driver's texture size is erratic
> >> > (i. e. too big)? I have no idea where the error could result from!
> >> >
> >> > e. Although stated differently in the error message above neither the
> >> > dmesg nor the xorg.0.log file reveal any information that could be
> >> > really helpful.
> >> >
> >> >
> >> >
> >
> > Hi Alex,
> >
> > 1. The real issue of that Compiz problem IS NOT what dmesg says.
> >
> > The real issue of my problem is that the FIRST patch Dave Airlie
> > attached for resolving this Compiz issue NEVER reached kernel mainline
> > while the second one did obviously.
> >
> > So PLEASE do push up Dave's FIRST patch titled "fallback on VRAM memory
> > placement" as fast as possible so that it becomes part of the kernel
> > mainline!
> 
> The first patch caused problems on some AGP systems due to the
> unreliability of AGP so it wasn't pushed to mainline.  It should be
> safe to push once this patch hits mainline:
> http://git.kernel.org/?p=linux/kernel/git/airlied/drm-2.6.git;a=commit;h=61cf059325a30995a78c5001db2ed2a8ab1d4c36
> 
> Alex
> 
> >
> > 2. When I apply Dave's patch Nr. 2 against kernel 2.6.34-rc5 Compiz will
> > NOT run without errors, but it will at least run, what is impossible
> > without the mentioned patch.
> >
> > It will show the follwing errors:
> > a. the windows I open will not have a blue frame on top.
> > Instead there will be a menu starting up at the upper left side.
> > This is a typical old error.
> > b. Due to missing VRAM I guess that the effect "Burning fire into the
> > screen" is coloured white instead of orange.
> >
> > I add a patch plus 2 logfiles as outline attachment.
> >
> > Cheers
> >
> > Uwe
> >
> >

So this is what I call perfection:
With Dave's first patch combined with the one mentioned above Compiz
runs perfect again in connection with driver 6.13 for my R100 Radeon!

I combined the two necessary patches, adjusted the line numbers for
2.6.34-rc5 and attached the needed result outline as an intermediate
solution for people needing it.

Thanks to everyone contributing to this - you're beautiful!

Uwe

-------------- next part --------------
A non-text attachment was scrubbed...
Name: radeon.patch
Type: text/x-patch
Size: 10530 bytes
Desc: not available
URL: <http://lists.x.org/archives/xorg/attachments/20100425/5e32cdcf/attachment.bin>