From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 61883] New: wine shader_generate_glsl_declarations fail
Date: Wed, 06 Mar 2013 01:36:40 +0000 [thread overview]
Message-ID: <bug-61883-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1054 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=61883
Priority: medium
Bug ID: 61883
Assignee: dri-devel@lists.freedesktop.org
Summary: wine shader_generate_glsl_declarations fail
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: victoraur.santos@gmail.com
Hardware: All
Status: NEW
Version: 9.1
Component: Drivers/DRI/r300
Product: Mesa
Trying to run RE4 on my r300 freeze completely system
Submitted on wine bug tracker and suggested to report here.
----
err:winediag:shader_generate_glsl_declarations The hardware does not support
enough uniform components to run this shader, it may not render correctly.
----
and lot of:
----
r300: ERROR: FS input fog unassigned, not enough hardware slots. (it's not a
bug, do not report it)
----
for more details and full log see: http://bugs.winehq.org/show_bug.cgi?id=33129
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2412 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2013-03-06 1:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-06 1:36 bugzilla-daemon [this message]
2013-03-06 8:29 ` [Bug 61883] wine shader_generate_glsl_declarations fail bugzilla-daemon
2013-03-06 15:43 ` bugzilla-daemon
2013-03-06 15:43 ` bugzilla-daemon
2019-09-18 18:51 ` 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-61883-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox