Date: Sun, 15 Aug 2004 23:25:49 +0900 (JST)
Message-Id: <20040815.232549.74751081.garrigue at kurims.kyoto-u.ac.jp>
To: seguso.forever at tin.it
Cc: lablgtk at kaba.or.jp
Subject: Re: What's wrong with this code? [GlGtk.area]
From: Jacques Garrigue <garrigue at kurims.kyoto-u.ac.jp>
In-Reply-To: <200408141716.21116.seguso.forever at tin.it>
References: <200408141519.27667.seguso.forever at tin.it>
	<20040814.232850.78724946.garrigue@kurims.kyoto-u.ac.jp>
	<200408141716.21116.seguso.forever@tin.it>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

From: Maurizio Colucci <seguso.forever at tin.it>

> Thank you Jacques. This is good new because, at worst, I'll try to
> remove the driver. But then I'd have no accelerated 3d :-(

Indeed, a bit self-defeating.
If other (non-lablGL) openGL programs work, this may be a lablGL.
You may also check whether this is a gtkgl problem, by trying
lablgl/togl or lablglut examples.

> > The nvidia driver may be the problem.
> > Try disabling DRI as a first check.
> 
> In /etc/X11/XF86Config-4 I had already commented out the line 
> 
>  Load "dri"
> 
> because the nvidia driver require it. Is that what you mean?

Not exactly, I was speaking of disabling 3d acceleration altogether.
You may have to do something else with your nvidia driver.
Or disable the driver itself if this doesn't work.

> Some additional info: I tried running the C sample program simple.c from 
> GtkGlArea. It works, but the standard output complains that dri is _absent_:
[...]
> Xlib:  extension "XFree86-DRI" missing on display ":0.0".
> Segmentation fault

This is not the problem. I have the same warning, and the program works
OK.

> Also, some opengl games are misbehaving. Some (neverball) crash on startup, 
> some work but crash on fullscreeen mode (neverputt).
[...]
> The nvidia driver is installed correctly. (I installed the kernel headers of 
> the right kernel, 2.4.18-bf2.4, and the right gcc used to compile the 
> kernel.)
> 
> The card is nvidia TNT2 ultra.
> -------
> 
> Any idea what I should try next?

None at all, I'm no hardware expert.
I suppose you should look around in Linux forums for similar problems,
if lablGL is not the cause.

Jacques