linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Timothy A. Seufert" <tas@mindspring.com>
To: "Gareth Hughes" <gareth@valinux.com>,
	"Michel Dänzer" <michdaen@iiic.ethz.ch>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: r128 DRI driver now fully functional on PPC
Date: Tue, 27 Feb 2001 02:03:33 -0800	[thread overview]
Message-ID: <v04220800b6c12899d73e@[10.0.0.42]> (raw)
In-Reply-To: <3A9A2FBF.B304ADD1@valinux.com>


At 9:28 PM +1100 2/26/01, Gareth Hughes wrote:
>Michel Dänzer wrote:
>>
>>  First I thought I'd stand corrected, but on second thought - it looks for
>>  /usr/X11R6-DRI/lib/modules/dri/r128_dri.so on my machine (if ProjectRoot is
>>  /usr/X11R6-DRI), but /usr/X11R6-DRI/lib isn't in ld.so.conf . It even looks
>>  there if I set LD_LIBRARY_PATH to the exports/lib directory in the
>>build tree.
>>
>>  Am I still not getting it? :)
>
>Sorry, my mistake.  libGL.so opens $MODULEDIR/dri/r128_dri.so, where
>$MODULEDIR is defined by the Imakefiles (and would be
>/usr/X11R6-DRI/lib/modules in your case).  So, the problem may be that
>the wrong libGL.so is being picked up -- and this *is* an ld.so.conf
>problem.

Could the Imakefiles have been broken by the following options in site.def?

#define NothingOutsideProjectRoot YES
#define EtcX11Directory ProjectRoot/etc

I enabled (uncommented) both of these since I thought it might be a
good idea to force X to be completely self-contained within
ProjectRoot.

I just tried a build without these options and it seems to clear up
the library problem.  After doing so I have only two differences from
the config files in CVS: I set ProjectRoot and disabled Glide3.  So
it's entirely possible that setting Nothing... and/or EtcX11Dir...
caused the compiled-in default library search path you describe to
get mangled.


I still have the problem with keyboard/mouse input being ignored once
a GL app starts.  A friend suggested disabling DGA, but that didn't
help.  I do notice this message popping in the system logs, repeated
numerous times:

[drm:drm_lock_take] *ERROR* 1 holds heavyweight lock

   Tim Seufert

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2001-02-27 10:03 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-30  8:08 r128 DRI driver now fully functional on PPC Gareth Hughes
2001-01-31 11:49 ` Benjamin Herrenschmidt
2001-01-31 14:54   ` [linux-fbdev] " Andreas Hundt
2001-01-31 18:32     ` Michel Dänzer
2001-01-31 18:43       ` Geert Uytterhoeven
2001-01-31 18:53         ` Michel Dänzer
2001-01-31 19:14         ` Andreas Hundt
2001-01-31 16:49   ` Kostas Gewrgiou
2001-01-31 18:26   ` Michel Dänzer
2001-02-23  7:07 ` Timothy A. Seufert
2001-02-23 10:02   ` Gareth Hughes
2001-02-25  8:32     ` Timothy A. Seufert
2001-02-26  9:39       ` Michel Dänzer
2001-02-26 10:06         ` Gareth Hughes
2001-02-26 10:21           ` Michel Dänzer
2001-02-26 10:28             ` Gareth Hughes
2001-02-27 10:03               ` Timothy A. Seufert [this message]
2001-02-27 11:39                 ` Gareth Hughes
2001-02-27 21:43                   ` Michel Dänzer
2001-02-23 12:19   ` Michel Dänzer
2001-02-23 12:23     ` Gareth Hughes
2001-02-23 12:33       ` Michel Dänzer

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='v04220800b6c12899d73e@[10.0.0.42]' \
    --to=tas@mindspring.com \
    --cc=gareth@valinux.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=michdaen@iiic.ethz.ch \
    /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).