From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 100239] Incorrect rendering in CS:GO
Date: Tue, 17 Sep 2019 02:09:21 +0000 [thread overview]
Message-ID: <bug-100239-502-BSc1emPHxo@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-100239-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1398 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=100239
--- Comment #27 from Timothy Arceri <t_arceri@yahoo.com.au> ---
(In reply to Bruno Jacquet (Xaapyks) from comment #26)
> (In reply to Michel Dänzer from comment #25)
> > (In reply to Bruno Jacquet (Xaapyks) from comment #23)
> > > So I'd say the issue is still there.
> >
> > Maybe you have a ~/.drirc or other drirc file which gets picked up and
> > disables radeonsi_zerovram? (E.g. due to ever starting the old "driconf"
> > application with a driver which supported the option)
>
> ~/.drirc and /etc/drirc do not exist on my fs.
> /usr/share/drirc.d only contains 00-mesa-defaults.conf which is not modified
> from what the mesa build provides and is packaged in Arch.
>
> strace seems to confirm it is not loading any other "drirc" file any and I
> don't have any "*MESA*" or "*GL*" env var.
I just tested the trace from comment 16 on my Vega 64 and using the environment
variable fixed the issue for me. Do you have an old kernel?
radeonsi_zeroram=true will do nothing on pre 4.9 kernels.
If you have at least 4.9 can you try closing steam then running it from the
command line with:
radeonsi_zeroram=true steam
And then run CS:GO. This should force the setting even if your system is not
picking up the right config file.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2459 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-09-17 2:09 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-16 20:35 [Bug 100239] Incorrect rendering in CS:GO bugzilla-daemon
2017-03-16 21:05 ` bugzilla-daemon
2017-03-22 16:54 ` bugzilla-daemon
2017-03-22 18:56 ` bugzilla-daemon
2017-04-27 19:39 ` bugzilla-daemon
2017-04-29 8:52 ` bugzilla-daemon
2017-04-29 12:22 ` bugzilla-daemon
2017-05-01 3:44 ` bugzilla-daemon
2017-05-01 12:16 ` bugzilla-daemon
2017-05-06 14:59 ` bugzilla-daemon
2017-05-10 23:44 ` bugzilla-daemon
2017-05-13 8:32 ` bugzilla-daemon
2017-12-16 16:04 ` bugzilla-daemon
2018-04-02 11:02 ` bugzilla-daemon
2018-07-07 21:11 ` bugzilla-daemon
2018-07-07 21:12 ` bugzilla-daemon
2018-07-08 9:30 ` bugzilla-daemon
2018-07-08 10:27 ` bugzilla-daemon
2018-11-25 9:52 ` bugzilla-daemon
2019-01-10 9:44 ` bugzilla-daemon
2019-05-03 1:20 ` bugzilla-daemon
2019-05-03 6:08 ` bugzilla-daemon
2019-05-06 4:31 ` bugzilla-daemon
2019-05-06 23:43 ` bugzilla-daemon
2019-08-08 20:53 ` bugzilla-daemon
2019-08-08 20:59 ` bugzilla-daemon
2019-08-09 8:40 ` bugzilla-daemon
2019-09-14 12:45 ` bugzilla-daemon
2019-09-17 2:09 ` bugzilla-daemon [this message]
2019-09-25 17:58 ` 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-100239-502-BSc1emPHxo@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).