dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 75794] Accumulation of black squares with OpenGL applications at high resolutions
Date: Tue, 11 Mar 2014 07:45:06 +0000	[thread overview]
Message-ID: <bug-75794-502-ulqJRwwWKc@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-75794-502@http.bugs.freedesktop.org/>


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

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

--- Comment #10 from l.mollari@gmx.net ---
My attempt to track down the commit that introduced the glitches ended with the
following error from the configure script, using revisions "mesa-9.1" and
"mesa-9.0.3":

configure: error: DRI driver directory 'r300' does not exist

I followed the instructions given at the Ubuntu wiki site, using the configure
command with the parameters as listed below:

https://wiki.ubuntu.com/X/BisectingMesa

git clone git://anongit.freedesktop.org/git/mesa/mesa

...

./configure --prefix=/usr --mandir=\${prefix}/share/man \
    --infodir=\${prefix}/share/info --sysconfdir=/etc \
    --localstatedir=/var --build=i486-linux-gnu --disable-gallium
--with-driver=dri \
    --with-dri-drivers="r300" --with-demos=xdemos --libdir=/usr/lib/glx \
    --enable-glx-tls --enable-driglx-direct --disable-egl \
    --disable-glu --disable-glut --disable-glw CFLAGS="-Wall -g -O2"

To my understanding the particular driver "r300" is not (any longer?) part of
what I have cloned so far from the git repository, hence the configure script
wants to include a precompiled version. Could you please give me a hint how I
can get past this missing driver obstacle?

However opting out the parameter --with-dri-drivers="r300" enables the
configure script and subsequently the make command to succeed even though
glxgears, now running without artifacts at decent fps, is stuttering
noticeably. This applies to 9.0.3 and 9.1 likewise.

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

[-- Attachment #1.2: Type: text/html, Size: 2490 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:[~2014-03-11  7:45 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-05 11:47 [Bug 75794] New: Accumulation of black squares with OpenGL applications at high resolutions bugzilla-daemon
2014-03-05 11:48 ` [Bug 75794] " bugzilla-daemon
2014-03-05 11:49 ` bugzilla-daemon
2014-03-05 11:50 ` bugzilla-daemon
2014-03-05 11:51 ` bugzilla-daemon
2014-03-05 11:52 ` bugzilla-daemon
2014-03-05 11:53 ` bugzilla-daemon
2014-03-05 11:55 ` bugzilla-daemon
2014-03-05 11:55 ` bugzilla-daemon
2014-03-05 14:13 ` bugzilla-daemon
2014-03-05 20:34 ` bugzilla-daemon
2014-03-11  7:45 ` bugzilla-daemon [this message]
2014-03-11  8:29 ` bugzilla-daemon
2014-03-11 13:00 ` bugzilla-daemon
2018-10-28 16:26 ` bugzilla-daemon
2019-09-18 18:52 ` 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-75794-502-ulqJRwwWKc@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).