All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 26641] New: RV730 agp xf86-video-ati with kms poor performance
Date: Thu, 18 Feb 2010 15:46:55 -0800 (PST)	[thread overview]
Message-ID: <bug-26641-502@http.bugs.freedesktop.org/> (raw)

http://bugs.freedesktop.org/show_bug.cgi?id=26641

           Summary: RV730 agp xf86-video-ati with kms poor performance
           Product: Mesa
           Version: git
          Platform: x86 (IA32)
        OS/Version: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/DRI/R600
        AssignedTo: dri-devel@lists.sourceforge.net
        ReportedBy: nemrood@gmail.com


I use Radeon 4650 AGP (RV730). System: Archlinux. CPU: AMD Athlon(tm) 64
Processor 3000+

I use kernel 2.6.33 rc8 with ati kms support. I have compiled mesa and driver
from git (exact compile options in attachments). I can get no more than 600fps
in glxgears.

glxgears
2529 frames in 5.0 seconds = 505.756 FPS
2415 frames in 5.0 seconds = 482.971 FPS
2440 frames in 5.0 seconds = 487.853 FPS
1905 frames in 5.0 seconds = 380.890 FPS
1901 frames in 5.0 seconds = 380.119 FPS
1935 frames in 5.0 seconds = 386.888 FPS
1887 frames in 5.0 seconds = 377.399 FPS
1843 frames in 5.0 seconds = 368.464 FPS
^C

I must say, I didn't do anything when I ran glxgears. What is strange just
after I startx, I get 550-600 fps. When I start a few apps (like, psi, firefox,
a few urxvt terminals (nothing more is running in background except openbox and
tint2) it looks like above. After some time, I have ~ 110fps (as when I'm
writing this report now).

Tried also extreme tux racer. I can run it ( ~ 9fps), but it crashes after
while (1024x768, rest of the options not touched).

Inside the attachment I've put all used pkgbuilds, kernel config, glxinfo, X
log.

If you need any more info, please ask - I'll do my best to answer.

Regards


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
--

             reply	other threads:[~2010-02-18 23:46 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-18 23:46 bugzilla-daemon [this message]
2010-02-18 23:50 ` [Bug 26641] RV730 agp xf86-video-ati with kms poor performance bugzilla-daemon
2010-02-19  0:44 ` bugzilla-daemon
2010-02-19  1:25 ` bugzilla-daemon
2010-02-19  1:30 ` bugzilla-daemon
2010-02-19 19:43 ` bugzilla-daemon
2010-02-19 22:40 ` bugzilla-daemon
2010-02-19 22:52 ` bugzilla-daemon
2010-02-20  0:13 ` bugzilla-daemon
2010-03-09 19:38 ` bugzilla-daemon
2010-03-15 12:23 ` bugzilla-daemon
2010-03-15 16:58 ` bugzilla-daemon
2010-03-15 18:15 ` bugzilla-daemon
2010-04-08  0:06 ` bugzilla-daemon
2010-04-08 13:45 ` bugzilla-daemon
2010-04-20 11:32 ` bugzilla-daemon
2012-09-11 17:32 ` bugzilla-daemon

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=bug-26641-502@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.