Re[2]: [Dri-devel] Mach 64 success and problems

2002-02-24 Thread Nerijus Baliunas
On 19 Feb 2002 19:02:47 + Jose Fonseca <[EMAIL PROTECTED]> wrote: JF> The man page indeed mentions that, but how do you explain what is JF> happening!? I was really suggesting to put /usr/lib before JF> /usr/X11R6/lib because the libGL we are interest in is already symlink'd JF> in /usr/lib..

Re: [Dri-devel] Mach 64 success and problems

2002-02-19 Thread José Fonseca
On 2002.02.19 19:35 Michael Thaler wrote: > On Tue, Feb 19, 2002 at 07:02:47PM +, Jose Fonseca wrote: > > > Michael, please try to copy the glxinfo & glxgears binaries to other > > place and run them from there. > > Jose, I copied glxinfo and glxgears from /usr/X11R6 to /root and tried it >

Re: [Dri-devel] Mach 64 success and problems

2002-02-19 Thread Malte Cornils
Michael wrote: > I don't see your problem? I'm using debian unstable. Adding > /usr/foo/bar/ to /etc/ld.so.conf and running /sbin/ldconfig works just > fine (as Jose described) > > see man 8 ld.so, it searches LD_LIBRARY_PATH, /etc/ld.so.cache then > /usr/lib and /lib. You're right. It was a re

Re: [Dri-devel] Mach 64 success and problems

2002-02-19 Thread Michael
On Wed, Feb 20, 2002 at 01:05:54AM +0100, Malte Cornils wrote: > Symlinking to the "correct" libGL (in /usr/X11R6-DRI) is almost the > same as copying it to /usr/lib, it still interferes with the > distro's packaging system and might not survive the next upgrade (on > Debian unstable, that mean

Re: [Dri-devel] Mach 64 success and problems

2002-02-19 Thread Brian Paul
Ian Romanick wrote: > > On Tue, Feb 19, 2002 at 07:28:54PM +0100, Malte Cornils wrote: > > Jose Fonseca wrote: > > > > > No, there's no need. You probably just have to change the order on which > > > /usr/lib/ and /usr/X11R6/lib/ directories appear on /etc/ld.so.conf and > > > run '/sbin/ldconfig

Re: [Dri-devel] Mach 64 success and problems

2002-02-19 Thread Malte Cornils
Hi Dieter, Dieter Nützel wrote: > OK, Allen Akin told you what the LSB standard is: > libGL* belongs into /usr/lib. > > lrwxrwxrwx1 root root 25 Feb 17 01:50 libGL.so.1 -> > /usr/X11R6/lib/libGL.so.1 > X11R6/lib> l libGL* libglut* > lrwxrwxrwx1 root root 12

Re: [Dri-devel] Mach 64 success and problems

2002-02-19 Thread Dieter Nützel
Malte Cornils wrote: > Leif Delgass wrote: > > I thought this was done by "make install", I have: > > > > % ls -l /usr/lib/libGL* > > lrwxrwxrwx1 root root 27 Feb 18 19:34 /usr/lib/libGL.so > > -> /usr/X11R6-DRI/lib/libGL.so > > lrwxrwxrwx1 root root 29 Feb 18

Re: [Dri-devel] Mach 64 success and problems

2002-02-19 Thread Malte Cornils
Leif Delgass wrote: > I thought this was done by "make install", I have: > > % ls -l /usr/lib/libGL* > lrwxrwxrwx1 root root 27 Feb 18 19:34 /usr/lib/libGL.so > -> /usr/X11R6-DRI/lib/libGL.so > lrwxrwxrwx1 root root 29 Feb 18 19:34 > /usr/lib/libGL.so.1 -> /u

Re: [Dri-devel] Mach 64 success and problems

2002-02-19 Thread Malte Cornils
Ian Romanick wrote: >>Any hints how to do it in a better way? > How about the obvious? Don't put libGL (and friends) in /usr/lib. Always > put them in /usr/X11*/lib. If you have some other libGL (standalone Mesa, > perhaps), but it in /usr/local/lib. Yes, I might do that if it wouldn't greatly

Re: [Dri-devel] Mach 64 success and problems

2002-02-19 Thread Michael Thaler
On Tue, Feb 19, 2002 at 07:02:47PM +, Jose Fonseca wrote: > Michael, please try to copy the glxinfo & glxgears binaries to other > place and run them from there. Jose, I copied glxinfo and glxgears from /usr/X11R6 to /root and tried it with /root/glxinfo and /root/glxgears and it still uses

Re: [Dri-devel] Mach 64 success and problems

2002-02-19 Thread Allen Akin
On Tue, Feb 19, 2002 at 11:05:08AM -0800, Ian Romanick wrote: | | How about the obvious? Don't put libGL (and friends) in /usr/lib. The Linux OpenGL ABI standard requires that libGL and libGLU be in /usr/lib. Obviously a lot of applications will work even if that's not true, but some apps, Mak

Re: [Dri-devel] Mach 64 success and problems

2002-02-19 Thread Leif Delgass
On Tue, 19 Feb 2002, Malte Cornils wrote: > Jose Fonseca wrote: > >>mthaler:~# ldd /usr/X11R6/bin/glxinfo > >>libGL.so.1 => /usr/X11R6/lib/libGL.so.1 (0x4009c000) > >>where quake3 probably uses the libGL from /usr/lib/ > >>lrwxrwxrwx1 root root 31 19. Feb 12:11 /usr/lib

Re: [Dri-devel] Mach 64 success and problems

2002-02-19 Thread Ian Romanick
On Tue, Feb 19, 2002 at 07:28:54PM +0100, Malte Cornils wrote: > Jose Fonseca wrote: > > > No, there's no need. You probably just have to change the order on which > > /usr/lib/ and /usr/X11R6/lib/ directories appear on /etc/ld.so.conf and > > run '/sbin/ldconfig' > > Unfortunately, /usr/lib is

Re: [Dri-devel] Mach 64 success and problems

2002-02-19 Thread Michael Thaler
On Tue, Feb 19, 2002 at 03:35:45PM +0100, Koen Kooi wrote: > Most of my problems were solved when disabling the framebuffer: How can you do that? Greetings, Michael ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/list

Re: [Dri-devel] Mach 64 success and problems

2002-02-19 Thread Jose Fonseca
On Tue, 2002-02-19 at 18:28, Malte Cornils wrote: > Jose Fonseca wrote: > >>mthaler:~# ldd /usr/X11R6/bin/glxinfo > >>libGL.so.1 => /usr/X11R6/lib/libGL.so.1 (0x4009c000) > >>where quake3 probably uses the libGL from /usr/lib/ > >>lrwxrwxrwx1 root root 31 19. Feb 12:11 /

Re: [Dri-devel] Mach 64 success and problems

2002-02-19 Thread Malte Cornils
Jose Fonseca wrote: >>mthaler:~# ldd /usr/X11R6/bin/glxinfo >>libGL.so.1 => /usr/X11R6/lib/libGL.so.1 (0x4009c000) >>where quake3 probably uses the libGL from /usr/lib/ >>lrwxrwxrwx1 root root 31 19. Feb 12:11 /usr/lib/libGL.so.1.2 -> >/usr/X11R6-DRI/lib/libGL.so.1.2

Re: [Dri-devel] Mach 64 success and problems

2002-02-19 Thread Jose Fonseca
On Tue, 2002-02-19 at 16:40, Michael Thaler wrote: > On Tue, Feb 19, 2002 at 03:13:39PM +, José Fonseca wrote: > > > The only explanation I see is that glxinfo is not picking up the correct > > libGL.so. Since this issue can came back to haunt you later, please do > > 'ldd /usr/X11R6/bin/gl

Re: [Dri-devel] Mach 64 success and problems

2002-02-19 Thread Michael Thaler
On Tue, Feb 19, 2002 at 03:13:39PM +, José Fonseca wrote: > The only explanation I see is that glxinfo is not picking up the correct > libGL.so. Since this issue can came back to haunt you later, please do > 'ldd /usr/X11R6/bin/glxinfo' and also 'ldd /usr/X11R6/bin/glxgears' (paths > may v

Re: [Dri-devel] Mach 64 success and problems

2002-02-19 Thread Michel Dänzer
On Tue, 2002-02-19 at 15:35, Koen Kooi wrote: > > Most of my problems were solved when disabling the framebuffer: The framebuffer is the memory on the video card, so what exactly have you disabled? :) > [...] > (WW) ATI(0): Cannot shadow an accelerated frame buffer. > [...] Isn't this a perfec

Re: [Dri-devel] Mach 64 success and problems

2002-02-19 Thread Laurent Pinchart
> > >mthaler:~# glxinfo >name of display: :0.0 >display: :0 screen: 0 >direct rendering: No >server glx vendor string: SGI >server glx version string: 1.2 >server glx extensions: > Try running glxinfo with LIBGL debugging enabled (LIBGL_DEBUG=verbose glxinfo), that might help to trace the proble

Re: [Dri-devel] Mach 64 success and problems

2002-02-19 Thread Brian Paul
José Fonseca wrote: > > On 2002.02.19 14:36 Michael Thaler wrote: > > On Tue, Feb 19, 2002 at 03:10:19PM +0100, R. Reucher wrote: > > > > ... > > (II) ATI(0): Direct rendering enabled > > > > It definitely says direct rendering is enabled! > > > > Yes. That's is definitely true. > > > ... > > >

Re: [Dri-devel] Mach 64 success and problems

2002-02-19 Thread José Fonseca
On 2002.02.19 14:36 Michael Thaler wrote: > On Tue, Feb 19, 2002 at 03:10:19PM +0100, R. Reucher wrote: > > ... > (II) ATI(0): Direct rendering enabled > > It definitely says direct rendering is enabled! > Yes. That's is definitely true. > ... > > I still get: > > mthaler:~# glxinfo > name

Re: [Dri-devel] Mach 64 success and problems

2002-02-19 Thread R. Reucher
On Tuesday 19 February 2002 15:36, Michael Thaler wrote: > (II) ATI(0): Direct rendering enabled > > It definitely says direct rendering is enabled! Ok, then it's working correctly ! Sorry for any confusion caused by me :-)... > > Hmmm, this might just be caused by the less color bits you're usin

Re: [Dri-devel] Mach 64 success and problems

2002-02-19 Thread Koen Kooi
Hello, Most of my problems were solved when disabling the framebuffer: [...] (WW) ATI(0): Cannot shadow an accelerated frame buffer. [...] This helps both on GATOS (2d) and DRI (3d). I have an ATI RAGE XL (onboard tyan S2462) with 4MB, so things may work different on your sys. I hope this helps

Re: [Dri-devel] Mach 64 success and problems

2002-02-19 Thread Michael Thaler
On Tue, Feb 19, 2002 at 03:10:19PM +0100, R. Reucher wrote: > Then it's still not working correctly ! Please look at your XFree86.0.log > again and search for "direct rendering" !!! (II) ATI(0): [drm] created "mach64" driver at busid "PCI:1:0:0" (II) ATI(0): [drm] added 4096 byte SAREA at 0xc88

Re: [Dri-devel] Mach 64 success and problems

2002-02-19 Thread R. Reucher
On Tuesday 19 February 2002 14:48, Michael Thaler wrote: > On Tue, Feb 19, 2002 at 02:00:54PM +0100, R. Reucher wrote: > > Thank you very much! Now I get: > > mthaler:~# lsmod > Module Size Used byNot tainted > mach64 71544 1 > > but glxinfo still shows: > >

Re: [Dri-devel] Mach 64 success and problems

2002-02-19 Thread Michael Thaler
On Tue, Feb 19, 2002 at 02:00:54PM +0100, R. Reucher wrote: Thank you very much! Now I get: mthaler:~# lsmod Module Size Used byNot tainted mach64 71544 1 but glxinfo still shows: mthaler:~# glxinfo name of display: :0.0 display: :0 screen: 0 direct re

Re: [Dri-devel] Mach 64 success and problems

2002-02-19 Thread R. Reucher
I don't have a Mach64 chipset but looked at the attached files... You seem to get out of video memory, starting X at a lower depth might help (16bpp, that is) ! >From your X log: ... (WW) ATI(0): DRI static buffer allocation failed -- need at least 9216 kB video memory (II) ATI(0): Using XFre

Re: [Dri-devel] Mach 64 success and problems

2002-02-19 Thread Michael Thaler
On Tue, Feb 19, 2002 at 10:44:43AM +, José Fonseca wrote: > Please check: > - if /usr/lib/libGL.so.1 is pointing to /usr/X11R6-DRI/lib/libGL.so. lrwxrwxrwx1 root root 10 19. Feb 12:17 /usr/lib/libGL.so -> libGL.so.1 lrwxrwxrwx1 root root 12 19. Feb 12:17

Re: [Dri-devel] Mach 64 success and problems

2002-02-19 Thread José Fonseca
On 2002.02.19 10:14 Michael Thaler wrote: > Hi, > > I compiled the mac64 driver following Leifs excellent mini-HOWTO. I > did not find any errors after compiling in world.log. I installed > XFree86 to /usr/X11R6-DRI, inserted mach64.o with insmod (I have > agpgart compiled into the kernel) and st

[Dri-devel] Mach 64 success and problems

2002-02-19 Thread Michael Thaler
Hi, I compiled the mac64 driver following Leifs excellent mini-HOWTO. I did not find any errors after compiling in world.log. I installed XFree86 to /usr/X11R6-DRI, inserted mach64.o with insmod (I have agpgart compiled into the kernel) and started X with /usr/X11R6-DRI/bin/X which worked fine. I