Re: [Dri-devel] My experiance with DRI and gcc-3.0(.4)

2002-07-12 Thread José Fonseca
On Fri, Jul 12, 2002 at 11:21:29AM +0200, Marc Poulhiès wrote: > hi, > as you are talking about install.sh, i find a little problem when using > it for the first time. When you dont have a kernel module installed > before the first run of install.sh, the modprobe fails...a simple depmod > -a then

Re: [Dri-devel] My experiance with DRI and gcc-3.0(.4)

2002-07-12 Thread Marc Poulhiès
hi, as you are talking about install.sh, i find a little problem when using it for the first time. When you dont have a kernel module installed before the first run of install.sh, the modprobe fails...a simple depmod -a then the modprobe fixes this... I was thinking that maybe this depmod -a shoul

Re: [Dri-devel] My experiance with DRI and gcc-3.0(.4)

2002-07-12 Thread José Fonseca
On Thu, Jul 11, 2002 at 11:58:56PM -0700, Mike Mestnik wrote: > The install.sh, included with the snapshots,(and make -f Makefile.linux) has allays >built modules > that insmod fine, even print every thing and rmmod, but they don't let X setunique. >getunique > worked fine. The error I get fro

[Dri-devel] My experiance with DRI and gcc-3.0(.4)

2002-07-11 Thread Mike Mestnik
The install.sh, included with the snapshots,(and make -f Makefile.linux) has allays built modules that insmod fine, even print every thing and rmmod, but they don't let X setunique. getunique worked fine. The error I get from an strace is no access, when calling the setunique ioctl. If I bui