dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 92302] Unigine Tropics freeze-crashes R390X
Date: Tue, 06 Oct 2015 08:52:21 +0000	[thread overview]
Message-ID: <bug-92302-502-60lG6HUvpq@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-92302-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1058 bytes --]

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

--- Comment #5 from Andy Furniss <adf.lists@gmail.com> ---
(In reply to MC Return from comment #4)
> Hi Michel,
> thanks a lot for the swift response.
> 
> I've built Mesa by checking out origin/11.0 and configuring the build with
> ./autogen.sh --prefix=/usr --enable-texture-float
> --libdir=/usr/lib/x86_64-linux-gnu/
> --with-gallium-drivers=nouveau,radeonsi,r600 --with-egl-platforms=drm,x11
> --enable-glx-tls --enable-shared-glapi --enable-glx --enable-driglx-direct
> --enable-gles1 --enable-gles2 --enable-experimental-targets=R600
> 
> How can I find out if my 32-bit Mesa binaries are up to date ?

Maybe nothing to do with the issue here, but there are some unigine workarounds
in drirc that may not get read if (historically at least) you don't specify
that they should go in /etc. I haven't looked recently but in the past with
your options they would end up in /usr/etc and not get used so add -

--sysconfdir=/etc

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1897 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

  parent reply	other threads:[~2015-10-06  8:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-05 21:16 [Bug 92302] Unigine Tropics freeze-crashes R390X bugzilla-daemon
2015-10-06  1:34 ` bugzilla-daemon
2015-10-06  8:22 ` bugzilla-daemon
2015-10-06  8:25 ` bugzilla-daemon
2015-10-06  8:32 ` bugzilla-daemon
2015-10-06  8:52 ` bugzilla-daemon [this message]
2015-10-06  9:11 ` bugzilla-daemon
2015-10-06  9:33 ` bugzilla-daemon
2015-10-06 10:45 ` bugzilla-daemon
2015-10-06 10:53 ` bugzilla-daemon
2015-10-06 11:37 ` bugzilla-daemon
2016-06-02 14:53 ` bugzilla-daemon
2019-09-25 17:53 ` 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-92302-502-60lG6HUvpq@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