All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 38478] New: r600g fails to identify the screen refresh rate
Date: Sun, 19 Jun 2011 14:21:51 -0700 (PDT)	[thread overview]
Message-ID: <bug-38478-502@http.bugs.freedesktop.org/> (raw)

https://bugs.freedesktop.org/show_bug.cgi?id=38478

           Summary: r600g fails to identify the screen refresh rate
           Product: Mesa
           Version: git
          Platform: x86 (IA32)
        OS/Version: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/Gallium/r600
        AssignedTo: dri-devel@lists.freedesktop.org
        ReportedBy: steve@sk2.org


Created an attachment (id=48172)
 --> (https://bugs.freedesktop.org/attachment.cgi?id=48172)
Xorg log file

Hi,

With the current git tree (up to 2fe39b46e73aea37152777fe11d489e0b1bc3f92) I'm
only getting 10fps running glxgears on my HD4650; other 3D programs exhibit the
same problem.

This is an improvement over previous versions of r600g on my system: before
7.10.3 the driver causes constant freezes, and 7.10.3 works but only at 0.8fps
(constantly).

I'm attaching the Xorg log and [drm] info from my kernel log. Let me know what
other information you need and I'll happily provide it!

Regards,

Stephen

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

             reply	other threads:[~2011-06-19 21:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-19 21:21 bugzilla-daemon [this message]
2011-06-19 21:22 ` [Bug 38478] r600g fails to identify the screen refresh rate bugzilla-daemon
2011-06-19 21:46 ` bugzilla-daemon
2011-06-19 21:47 ` bugzilla-daemon
2011-06-19 21:51 ` bugzilla-daemon
2011-06-21 17:48 ` bugzilla-daemon
2011-06-21 18:41 ` bugzilla-daemon
2011-08-13 23:06 ` 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-38478-502@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.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 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.