All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 33172] New: [r600g] ingame rendering broken (black screen) in ut2003
Date: Sat, 15 Jan 2011 15:01:10 -0800 (PST)	[thread overview]
Message-ID: <bug-33172-502@http.bugs.freedesktop.org/> (raw)

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

           Summary: [r600g] ingame rendering broken (black screen) in
                    ut2003
           Product: DRI
           Version: DRI CVS
          Platform: x86-64 (AMD64)
        OS/Version: Linux (All)
            Status: NEW
          Severity: major
          Priority: medium
         Component: DRM/Radeon
        AssignedTo: dri-devel@lists.freedesktop.org
        ReportedBy: liquid.acid@gmx.net


Hello!

Found some time to retest this popular game with fresh git pulls and it looks
like that it completly broke. The menu renders fine, but upon entering the
actual game you just get a black screen.

The kernel log then produces these nice messages:
[drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -12!
...

System:
ATI Technologies Inc Radeon HD 4770 [RV740]

drm-radeon-testing kernel
libdrm, mesa and xf86-video-ati are all git master
xorg-server-1.9.3.901

Greets,
Tobias

-- 
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-01-15 23:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-15 23:01 bugzilla-daemon [this message]
2011-01-15 23:21 ` [Bug 33172] [r600g] ingame rendering broken (black screen) in ut2003 bugzilla-daemon
2011-01-16 15:35 ` bugzilla-daemon
2011-01-19 22:35 ` bugzilla-daemon
2011-01-26 19:46 ` bugzilla-daemon
2011-01-27 15:28 ` bugzilla-daemon
2011-01-27 15:49 ` bugzilla-daemon
2011-02-01 21:04 ` 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-33172-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.