RenderAccel bug?

Erik Harrison erikharrison at
Mon Sep 13 07:45:44 PDT 2004

Oh I've got the driver. Like I said, I was testing Composite under
standard workloads using nvidia, nv, and vesa

To clarify what I am talking about, if I use

Option "RenderAccel" "true"

in xorg.conf, running the vesa or nv driver, resizing an xterm rapidly
will hang, the display reproducible everytime, and cause a noticible
slowdown with fadeouts.

I wasn't aware that RenderAccel was a nvidia specific option, but if
so, shouldn't enabling it do nothing with other drivers?


On Mon, 13 Sep 2004 14:21:46 +0200, Gerben Wijnja
<mailinglists at> wrote:
> On Mon, 2004-09-13 at 04:54, Erik Harrison wrote:
> > I've been messing around finally with 6.8.0, testing the nvidia binary
> > driver, the nv driver, and vesa with xcompmgr running.
> >
> > I don't know about whether or not nv supports RenderAccel, but with
> > RenderAccel enabled on any of the three drivers, resizing xterms and
> > gedit windows becomes very likely to freeze up the display quite
> > quickly, Switching VTs and killing xcompmgr restores the display, and
> > shows that hundreds of "error 3" messages have been dumped to the
> > terminal.
> >
> > Running with RenderAccel on in nv and vesa makes fadeout slower than
> > with it off. As closed or minimized apps are faded out, then the app
> > seems to hang. Menus fading out is very slow. Disabling accell
> > restores usable performance for fadeout.
> >
> > Slackware current w/ 2.6.7 kernel
> > Abit Siluro (Nvidia 5200 chipset) 128 Megs
> > Athlon XP 2400+
> > ASUS A7N8x-Deluxe
> > 512 MB of RAM.
> As far as I know, "RenderAccel" is an option NVIDIA added for their own
> driver, which is the "nvidia"-driver instead of the "nv"-driver. You can
> get it at
> Gerben


More information about the xorg mailing list