All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 28477] New: [R300g] dxdiag directx tests fail on vmware workstation 7.1.0 w/ r500 card using gallium
Date: Wed,  9 Jun 2010 19:46:54 -0700 (PDT)	[thread overview]
Message-ID: <bug-28477-502@http.bugs.freedesktop.org/> (raw)

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

           Summary: [R300g] dxdiag directx tests fail on vmware
                    workstation 7.1.0 w/ r500 card using gallium
           Product: Mesa
           Version: git
          Platform: x86-64 (AMD64)
        OS/Version: Linux (All)
            Status: NEW
          Severity: major
          Priority: medium
         Component: Drivers/DRI/r300
        AssignedTo: dri-devel@lists.freedesktop.org
        ReportedBy: crumja@gmail.com


Windows XP guest. 3D acceleration enabled under vmware workstation 7.1.0.
This is running git mesa with gallium3d and r300g built in from tormod's ubuntu
archives under kubuntu 10.04 amd64 edition.

The guest's 3D abilities are tested by running dxdiag within Windows XP. This
has worked fine under classic r300 and i965 drivers. However, with r300g
nightly builds (as of 06/09), fails with the following error when using
LIBGL_DEBUG=VERBOSE:

vmware-vmx: state_tracker/st_manager.c:483:
st_context_notify_invalid_framebuffer: Assertion `stfb && stfb->iface == stfbi'
failed.

-- 
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:[~2010-06-10  2:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-10  2:46 bugzilla-daemon [this message]
2010-06-10  2:51 ` [Bug 28477] [R300g] dxdiag directx tests fail on vmware workstation 7.1.0 w/ r500 card using gallium bugzilla-daemon
2010-08-06  2:15 ` 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-28477-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.