public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Lord Sauron" <lordsauronthegreat@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] AIGLX responseness (WAS: libGL issues & AIGLX slowness)
Date: Sun, 29 Oct 2006 11:16:04 -0800	[thread overview]
Message-ID: <e5a3e9ac0610291116j45f9f8ebu6c98fe15ba3c0847@mail.gmail.com> (raw)
In-Reply-To: <7573e9640610291051v314a1debp6b9e6f175075a9ab@mail.gmail.com>

Be sure DRI is working.  use glxinfo if you need to verify if it's active.

If you don't have DRI working, then most of the graphics will be done
on CPU.  Or at least that's how my laptop did it.

On 10/29/06, Richard Fish <bigfish@asmallpond.org> wrote:
> On 10/29/06, Tomáš Bartoň <tommz9@gmail.com> wrote:
> > On Sunday 29 October 2006 13:36, Marco Calviani wrote:
> > > Hi list,
> > >   the slowness of AIGLX was due to the fact that i was running
> > > xorg-server without enabling the aiglx flag. After having enabled it
> > > xorg started running with AIGLX (using compiz or beryl).
> > > Although the system is quite usable there is still an issue: i thought
> > > the system would have relied completely on video card acceleration.
> > > However whenever i run an AIGLX effect such as the cube or just window
> > > moving the CPU goes up to 80-90% during all the time the effect is
> > > running. This behaviour makes the system A LOT less responsive than it
> > > is without AIGLX.
> > > Is this a known issue?
> > >
> > > Thanks a lot,
> > > MC
> >
> > I tkink its normal. I run beryl with NVidia driver and when I move a window or
> > something the CPU goes up to 100% ...
>
> Hmm, I also have an nvidia GPU, and my system doesn't exhibit this
> behavior.  Of course, I get the black-windows bug due to a memory leak
> in the drivers, but certainly no excessive CPU usage for any of the
> beryl effects.
>
> -Richard
>
> --
> gentoo-user@gentoo.org mailing list
>
>


-- 
========== GCv3.12 ==========
GCS d-(++) s+: a? C++ UL+>++++ P+
L++ E--- W+(+++) N++ o? K? w--- O? M+
V? PS- PE+ Y-(--) PGP- t+++ 5? X R tv-- b+
                DI+++ D+ G e* h- !r !y
========= END GCv3.12 ========

-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2006-10-29 19:20 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-29 12:36 [gentoo-user] AIGLX responseness (WAS: libGL issues & AIGLX slowness) Marco Calviani
2006-10-29 12:43 ` Tomáš Bartoň
2006-10-29 12:48   ` Marco Calviani
2006-10-29 12:50     ` Marco Calviani
2006-10-29 18:51   ` Richard Fish
2006-10-29 19:16     ` Lord Sauron [this message]
2006-10-30  8:07       ` Marco Calviani
2006-10-30  0:25 ` Iain Buchanan
2006-10-30  0:44   ` Bo Ørsted Andresen
2006-10-30  1:43     ` Iain Buchanan
2006-10-30  2:08       ` Bo Ørsted Andresen
2006-11-01  4:27         ` Iain Buchanan
2006-11-01 14:44           ` [gentoo-user] issues with equery (WAS: AIGLX responseness [...]) Bo Ørsted Andresen
2006-11-02  0:01             ` Iain Buchanan
2006-11-02  0:09               ` Bo Ørsted Andresen
2006-10-30  8:09   ` [gentoo-user] AIGLX responseness (WAS: libGL issues & AIGLX slowness) Marco Calviani

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e5a3e9ac0610291116j45f9f8ebu6c98fe15ba3c0847@mail.gmail.com \
    --to=lordsauronthegreat@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox