[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#236187: xserver-xfree86: [r128] GL lockups



On Fri, Mar 05, 2004 at 12:39:36PM -0500, Daniel Jacobowitz wrote:
> On Fri, Mar 05, 2004 at 06:32:51PM +0100, Michel Dänzer wrote:
> > On Fri, 2004-03-05 at 18:23, Daniel Jacobowitz wrote:
> > > On Fri, Mar 05, 2004 at 06:19:02PM +0100, Michel Dänzer wrote:
> > > > 
> > > > It's probably the 3D driver or the DRM that causes it, not the X server.
> > > 
> > > What do you mean in this context by "the 3D driver"?
> > 
> > r128_dri.so .
> > 
> > > All I know for sure is that I was still using the same kernel version
> > > and kernel DRM module that used to work with XFree86 4.2.1, and now
> > > I get lockups after upgrading X, so I blame X.
> > 
> > Can you verify which one actually makes the difference?
> 
> Well, isn't that interesting.  Because my last upgrade was an 'apt-get
> upgrade' rather than dist-upgrade, I still have xlibmesa3-gl 4.2.1-16
> installed.  It's loading that module into the new X server.  Maybe
> that's the problem?
> 
> I'll upgrade it and see if the problem persists.

Some clarfications:

_dri.so objects don't get loaded into the X server; they are dlopened()
by the Mesa library.

You'll also notice they're not installed to the same place as XFree86
X server modules.

They're also named ".so", whereas XFree86 X server modules are named ".a" or
".o".

Contrast:

/usr/X11R6/lib/modules/dri/debug/r128_dri.so
/usr/X11R6/lib/modules/dri/r128_dri.so

with:

/usr/X11R6/lib/modules/drivers/r128_drv.o

If you were to argue that these paths could be laid out so as to make the
distinction more easily apprehended, I would probably agree.

-- 
G. Branden Robinson                |     Communism is just one step on the
Debian GNU/Linux                   |     long road from capitalism to
branden@debian.org                 |     capitalism.
http://people.debian.org/~branden/ |     -- Russian saying

Attachment: signature.asc
Description: Digital signature


Reply to: