Same here w/i915. and glxgears shows only 70-75 fps...
On Mon, Oct 20, 2008 at 2:02 PM, Clemens Eisserer <[EMAIL PROTECTED]> wrote:
> Same here, cannot play many games which run absolutly pefect with
> Windows-Drivers because of low performance.
> Tuxracer-0.69 is only playable at low resolutions
Hello Keith,
It topped at about 70-75fps max. Now it produces only ~50-56fps...
These 'no drirc found' messages could be my problem? (See glxinfo output below)
distro: gentoo
kernel: vanilla 2.6.27.1
mesa: 7.2
xorg-server: 1.5.1
xf86-video-intel: 2.4.2-r2
thanks,
Adam
[EMAIL PROTECTED] ~
Now I tried with vblank disabled, and voilá! - 860fps.
So I guess that was the problem, thanks for pointing it out
cheers,
Adam
On Tue, Oct 21, 2008 at 1:36 PM, Adam Lantos <[EMAIL PROTECTED]> wrote:
> Hello Keith,
>
>
> It topped at about 70-75fps max. Now it produ
I have the same resume problem with UXA (GM915), GEM + Tuxonice. Mesa,
xorg-server and xf86-video-intel from git master. EXA resumes
correctly.
cheers,
adam
On Mon, Jan 5, 2009 at 2:15 PM, Thomas Ilnseher wrote:
>
>
>
> -- Forwarded message --
> From: Thomas Ilnseher
> To: Xo
Hello,
I've updated my 915GM system to vanilla 2.6.28 + intel 2008Q4 patches,
libdrm, mesa, xorg-server master and xf86-video-intel-2.6.0. I use
AIGLX and UXA, but nothing else special in my xorg.conf.
I confirm https://bugs.freedesktop.org/show_bug.cgi?id=19578 on my
i915+LVDS setup. With frameb
Great work Eric, it finally fixed memory problems with my i915. We
definitely need 2.6.3 with this piece of code :)
cheers,
Adam
On Sat, Feb 28, 2009 at 6:21 AM, Eric Anholt wrote:
> On Wed, 2009-02-25 at 19:13 +0100, Brice Goglin wrote:
>> Eric Anholt wrote:
>> > On Wed, 2009-02-25 at 14:10
Jesse,
Thanks for the patch, I'm testing it now - it looks promising :)
X memory usage is more stable, but lsof | grep "drm mm" | wc -l still
increases - after 10 minutes it went up from 100 to 500... Is this
normal?
cheers,
Adam
2009/3/28 Jesse Barnes :
> On Fri, 27 Mar 2009 13:20:25 -0400
I had the same problem, I suspect it's a KDE bug - my colleague
suggested to switch krunner to task oriented interface and back to
command oriented. It helped, keyboard was working again after this.
I didn't ask him how he found this solution, but he reported it in KDE bugzilla.
cheers,
Adam
O