From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 95080] Source games "Could not find required OpenGL entry point 'glColorMaskIndexedEXT'!" RC410M [Mobility Radeon Xpress 200M]
Date: Mon, 25 Apr 2016 17:16:36 +0000 [thread overview]
Message-ID: <bug-95080-502-4dLWrRxZhM@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-95080-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 862 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=95080
Nicolai Hähnle <nhaehnle@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |NOTABUG
Status|NEW |RESOLVED
--- Comment #2 from Nicolai Hähnle <nhaehnle@gmail.com> ---
Keep in mind that the RC410 is a very old chip which lacks many features that
modern games require.
If you do a brief search on Steam forums, you'll find many discussions of
similar "error messages" regarding TF2. It seems some people have had luck by
hacking the driver to pretend that it supports certain features, but it seems
safe to say that your hardware is simply too old.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2583 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2016-04-25 17:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-23 10:50 [Bug 95080] Source games "Could not find required OpenGL entry point 'glColorMaskIndexedEXT'!" RC410M [Mobility Radeon Xpress 200M] bugzilla-daemon
2016-04-23 10:52 ` bugzilla-daemon
2016-04-25 17:16 ` bugzilla-daemon [this message]
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-95080-502-4dLWrRxZhM@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;
as well as URLs for NNTP newsgroup(s).