[Dri-users] Re: [Mesa3d-users] how can I put glx working with direct rendering
on savage twister k ?
From: M. B. <ser...@ne...> - 2004-01-31 03:12:24
|
from /var/log/XFree86.0.log=20 (**) SAVAGE(0): XvMC is enabled (=3D=3D) RandR enabled (II) Initializing built-in extension MIT-SHM (II) Initializing built-in extension XInputExtension (II) Initializing built-in extension XTEST (II) Initializing built-in extension XKEYBOARD (II) Initializing built-in extension LBX (II) Initializing built-in extension XC-APPGROUP (II) Initializing built-in extension SECURITY (II) Initializing built-in extension XINERAMA (II) Initializing built-in extension XFree86-Bigfont (II) Initializing built-in extension RENDER (II) Initializing built-in extension RANDR from glxinfo direct rendering: No even after install dri savage-2.0.0 branch from dri cvs=20 On Fri, 2004-01-30 at 20:07, Brian Paul wrote: > S=E9rgio Monteiro Basto wrote: > > Can someone give me one clue ? > > thanks in advance ! >=20 > I don't understand your question. The DRI list might be a better=20 > place to ask. >=20 > -Brian >=20 --=20 S=E9rgio Monteiro Basto=20 Rua Fernando Pessoa n.=BA 226, 1 Dto=20 Vermoim=20 4470-290 Maia=20 Tel: 965508780 Email: ser...@ne... |
From: Felix <fx...@gm...> - 2004-01-31 11:33:21
|
On 31 Jan 2004 03:11:04 +0000 S=E9rgio Monteiro Basto <ser...@ne...> wrote: > from /var/log/XFree86.0.log=20 > (**) SAVAGE(0): XvMC is enabled > (=3D=3D) RandR enabled > (II) Initializing built-in extension MIT-SHM > (II) Initializing built-in extension XInputExtension > (II) Initializing built-in extension XTEST > (II) Initializing built-in extension XKEYBOARD > (II) Initializing built-in extension LBX > (II) Initializing built-in extension XC-APPGROUP > (II) Initializing built-in extension SECURITY > (II) Initializing built-in extension XINERAMA > (II) Initializing built-in extension XFree86-Bigfont > (II) Initializing built-in extension RENDER > (II) Initializing built-in extension RANDR This log extract is not very helpful. A bit further up it should say something about DRI. If you're not sure compress the entire log and send it here. Hints: Make sure that the savage kernel module is compiled and installed before starting X. Enable DRI by loading the Xserver modules "dri" and "glx". Setup the correct permissions for the DRI device in Section "DRI" in your XF86Config-4. >=20 > from glxinfo > direct rendering: No >=20 > even after install dri savage-2.0.0 branch from dri cvs=20 If DRI is really enabled according to /var/log/XFree86.0.log then try runni= ng LIBGL_DEBUG=3Dverbose glxinfo and send us the output. Regards, Felix >=20 >=20 > On Fri, 2004-01-30 at 20:07, Brian Paul wrote: [snip] |
From: M. B. <ser...@ne...> - 2004-01-31 15:12:39
|
On Sat, 2004-01-31 at 11:32, Felix K=FChling wrote: > On 31 Jan 2004 03:11:04 +0000 > S=E9rgio Monteiro Basto <ser...@ne...> wrote: >=20 > > from /var/log/XFree86.0.log=20 > > (**) SAVAGE(0): XvMC is enabled > > (=3D=3D) RandR enabled > > (II) Initializing built-in extension MIT-SHM > > (II) Initializing built-in extension XInputExtension > > (II) Initializing built-in extension XTEST > > (II) Initializing built-in extension XKEYBOARD > > (II) Initializing built-in extension LBX > > (II) Initializing built-in extension XC-APPGROUP > > (II) Initializing built-in extension SECURITY > > (II) Initializing built-in extension XINERAMA > > (II) Initializing built-in extension XFree86-Bigfont > > (II) Initializing built-in extension RENDER > > (II) Initializing built-in extension RANDR >=20 > This log extract is not very helpful. A bit further up it should say > something about DRI. If you're not sure compress the entire log and send > it here. >=20 > Hints: Make sure that the savage kernel module is compiled and installed > before starting X. Enable DRI by loading the Xserver modules "dri" and > "glx". Setup the correct permissions for the DRI device in Section "DRI" > in your XF86Config-4. this is already done ! the DRI permission is : Section "DRI" Mode 0666 EndSection >=20 > >=20 > > from glxinfo > > direct rendering: No > >=20 > > even after install dri savage-2.0.0 branch from dri cvs=20 >=20 > If DRI is really enabled according to /var/log/XFree86.0.log then try run= ning >=20 > LIBGL_DEBUG=3Dverbose glxinfo >=20 > and send us the output. ok=20 >=20 > Regards, > Felix >=20 > >=20 > >=20 > > On Fri, 2004-01-30 at 20:07, Brian Paul wrote: > [snip] --=20 S=E9rgio M B |
From: Felix <fx...@gm...> - 2004-01-31 15:31:00
|
Your XF86Config-4 and XFree86.0.log look ok. DRI is definitely enabled. Did you run glxinfo with the environment variable LIBGL_DEBUG set to verbose? glxinfo.txt doesn't look like you did. Maybe it's using the wrong libGL. You can run ldd `which glxinfo` to see which libGL it's using. It should be <ProjectRoot>/lib/libGL.so.1. Regards, Felix |
From: M. B. <ser...@ne...> - 2004-01-31 17:04:29
|
#ldd `which glxinfo` libGLU.so.1 =3D> /usr/lib/libGLU.so.1 (0x4002c000) libGL.so.1 =3D> /usr/lib/libGL.so.1 (0x400c7000) libXext.so.6 =3D> /usr/X11R6/lib/libXext.so.6 (0x402a0000) libX11.so.6 =3D> /usr/X11R6/lib/libX11.so.6 (0x402ad000) libpthread.so.0 =3D> /lib/i686/libpthread.so.0 (0x40382000) libm.so.6 =3D> /lib/i686/libm.so.6 (0x40396000) libc.so.6 =3D> /lib/i686/libc.so.6 (0x42000000) libSM.so.6 =3D> /usr/X11R6/lib/libSM.so.6 (0x403b9000) libICE.so.6 =3D> /usr/X11R6/lib/libICE.so.6 (0x403c1000) libXmu.so.6 =3D> /usr/X11R6/lib/libXmu.so.6 (0x403d8000) libXt.so.6 =3D> /usr/X11R6/lib/libXt.so.6 (0x403ed000) libXi.so.6 =3D> /usr/X11R6/lib/libXi.so.6 (0x40439000) libdl.so.2 =3D> /lib/libdl.so.2 (0x40441000) /lib/ld-linux.so.2 =3D> /lib/ld-linux.so.2 (0x40000000) #ll /usr/lib/libGLU.so.1=20 lrwxrwxrwx 1 root root 26 Jan 31 16:29 /usr/lib/libGLU.so.1 -> /usr/X11R6/lib/libGLU.so.1 #ll /usr/lib/libGL.so.1 lrwxrwxrwx 1 root root 25 Jan 31 02:34 /usr/lib/libGL.so.1 -> /usr/X11R6/lib/libGL.so.1 Now its totally correct and I have the same result.=20 On Sat, 2004-01-31 at 15:30, Felix K=FChling wrote: > Your XF86Config-4 and XFree86.0.log look ok. DRI is definitely enabled. > Did you run glxinfo with the environment variable LIBGL_DEBUG set to > verbose? glxinfo.txt doesn't look like you did. Maybe it's using the > wrong libGL. You can run >=20 > ldd `which glxinfo` >=20 > to see which libGL it's using. It should be <ProjectRoot>/lib/libGL.so.1. >=20 > Regards, > Felix --=20 S=E9rgio Monteiro Basto=20 Rua Fernando Pessoa n.=BA 226, 1 Dto=20 Vermoim=20 4470-290 Maia=20 Tel: 965508780 Email: ser...@ne... |
From: M. B. <ser...@ne...> - 2004-01-31 16:02:56
|
ldd `which glxinfo` libGLU.so.1 =3D> /usr/local/lib/libGLU.so.1 (0x4002c000) libGL.so.1 =3D> /usr/lib/libGL.so.1 (0x400c7000) libXext.so.6 =3D> /usr/X11R6/lib/libXext.so.6 (0x402a0000) libX11.so.6 =3D> /usr/X11R6/lib/libX11.so.6 (0x402ad000) libpthread.so.0 =3D> /lib/i686/libpthread.so.0 (0x40382000) libm.so.6 =3D> /lib/i686/libm.so.6 (0x40396000) libc.so.6 =3D> /lib/i686/libc.so.6 (0x42000000) libSM.so.6 =3D> /usr/X11R6/lib/libSM.so.6 (0x403b9000) libICE.so.6 =3D> /usr/X11R6/lib/libICE.so.6 (0x403c1000) libXmu.so.6 =3D> /usr/X11R6/lib/libXmu.so.6 (0x403d8000) libXt.so.6 =3D> /usr/X11R6/lib/libXt.so.6 (0x403ed000) libXi.so.6 =3D> /usr/X11R6/lib/libXi.so.6 (0x40439000) libdl.so.2 =3D> /lib/libdl.so.2 (0x40441000) /lib/ld-linux.so.2 =3D> /lib/ld-linux.so.2 (0x40000000) everything looks normal glxinfo is a little short because, I had comment v4l I thing=20 any clue ? On Sat, 2004-01-31 at 15:30, Felix K=FChling wrote: > Your XF86Config-4 and XFree86.0.log look ok. DRI is definitely enabled. > Did you run glxinfo with the environment variable LIBGL_DEBUG set to > verbose? glxinfo.txt doesn't look like you did. Maybe it's using the > wrong libGL. You can run >=20 > ldd `which glxinfo` >=20 > to see which libGL it's using. It should be <ProjectRoot>/lib/libGL.so.1. >=20 > Regards, > Felix --=20 S=E9rgio M B=20 |
[Dri-users] Re: [Mesa3d-users] how can I put glx working with direct rendering
on savage twister k ?
From: M. B. <ser...@ne...> - 2004-01-31 17:34:15
|
Well I don't know, I think with XFree86 telling the true I begging this adventure when I try to install=20 3ddesktop-0.2.5 seems to me a good application of GL, and I got this messages: 3ddeskd: glXIsDirect failed, no Direct Rendering possible! 3ddeskd: Please configure hardware acceleration. Exiting. so I want glXIsDirect return true. thanks On Sat, 2004-01-31 at 17:14, Brian Paul wrote: >=20 > It's not clear to me if you're interested in using DRI drivers with=20 > XFree86 or stand-alone DRI drivers without X (aka miniglx). >=20 > For full DRI drivers, the docs on dri.sf.net should explain everything. >=20 > For "miniglx" drivers, see www.mesa3d.org and click on "fbdev/DRI=20 > Environment" under "Developer Topics". >=20 > -Brian >=20 >=20 > S=E9rgio Monteiro Basto wrote: > > Hi > > Thanks for replying. > >=20 > > So in mesa 6 cvs we have one mini glx > > and one example.miniglx.conf > > lets say=20 > > that PUT =20 > > clientDriverName=3Dsavage_dri.so > > but how compile src/glx/mini > >=20 > > I don't understand a simple thing > > I had install savage dri module kernel. > > and mesa don't make glx stuff, so how I can build glx ? > >=20 > > Looking for what I had write is a very very bad English so I understand > > that could be difficult understand what I am talking about. > >=20 > > I am talking about Xfree86 and Mesa on Linux distributions where mesa > > comes in diffrents place from different distro to distro in redhat 7.3 > > case comes in Xfree86 RPMS that provides Mesa and glx. > > =20 > > But mesa-5.0.2 doesn't provide glx. > > so I think that is my problem. > >=20 > >=20 > > thanks in advance=20 > >=20 > >=20 > >=20 > >=20 > > On Fri, 2004-01-30 at 20:07, Brian Paul wrote: > >=20 > >>S=E9rgio Monteiro Basto wrote: > >> > >>>Can someone give me one clue ? > >>>thanks in advance ! > >> > >>I don't understand your question. The DRI list might be a better=20 > >>place to ask. > >> > >>-Brian > >> >=20 >=20 --=20 S=E9rgio M. B. |
From: Felix <fx...@gm...> - 2004-01-31 20:02:28
|
On 31 Jan 2004 16:01:42 +0000 S=E9rgio Monteiro Basto <ser...@ne...> wrote: > ldd `which glxinfo` > libGLU.so.1 =3D> /usr/local/lib/libGLU.so.1 (0x4002c000) > libGL.so.1 =3D> /usr/lib/libGL.so.1 (0x400c7000) > libXext.so.6 =3D> /usr/X11R6/lib/libXext.so.6 (0x402a0000) > libX11.so.6 =3D> /usr/X11R6/lib/libX11.so.6 (0x402ad000) > libpthread.so.0 =3D> /lib/i686/libpthread.so.0 (0x40382000) > libm.so.6 =3D> /lib/i686/libm.so.6 (0x40396000) > libc.so.6 =3D> /lib/i686/libc.so.6 (0x42000000) > libSM.so.6 =3D> /usr/X11R6/lib/libSM.so.6 (0x403b9000) > libICE.so.6 =3D> /usr/X11R6/lib/libICE.so.6 (0x403c1000) > libXmu.so.6 =3D> /usr/X11R6/lib/libXmu.so.6 (0x403d8000) > libXt.so.6 =3D> /usr/X11R6/lib/libXt.so.6 (0x403ed000) > libXi.so.6 =3D> /usr/X11R6/lib/libXi.so.6 (0x40439000) > libdl.so.2 =3D> /lib/libdl.so.2 (0x40441000) > /lib/ld-linux.so.2 =3D> /lib/ld-linux.so.2 (0x40000000) >=20 > everything looks normal > glxinfo is a little short because, I had comment v4l I thing=20 > any clue ? v4l has nothing to do with DRI. If you have the environment variable LIBGL_DEBUG set to verbose then you should see messages about which DRI driver is used and so on. That was missing completely in the output you sent. Therefore I asked you to check if you're using the correct libGL. Now it seems that you are using the right libGL since you have a link from /usr/lib/libGL.so.1 to /usr/X11R6/lib/libGL.so.1 (your other mail). But I noticed one more strange thing in your glxinfo output. The renderer string indicates that you're using a standalone software Mesa libGL: OpenGL renderer string: Mesa X11 OpenGL version string: 1.3 Mesa 4.0.2 With direct rendering I get this: OpenGL renderer string: Mesa DRI SAVAGE Linux_1.1.18 OpenGL version string: 1.2 Mesa 5.0.2 With indirect rendering: OpenGL renderer string: Mesa GLX Indirect OpenGL version string: 1.4 Mesa 5.0.2 So something is (or was) not installed correctly. It was not using the right libGL. Did you make the symbolic links after you sent glxinfo.txt? What is your glxinfo output now (with LIBGL_DEBUG=3Dverbose)? If you're using the right libGL then you should get one of the last two renderer strings above. >=20 > On Sat, 2004-01-31 at 15:30, Felix K=FChling wrote: [snip] Felix |
From: M. B. <ser...@ne...> - 2004-01-31 20:30:12
Attachments:
glxinfo2.txt
|
uau ! thanks it works, I wrongly ln to version of Xfree86 4.2.1/Mesa 4.0.2 =20 now with correct soft links it work quite nice. libGLU.so.1 -> libGLU.so.1.3 and not libGL.so.1 -> libGL.so.1.3.402 libGLU.so.1 -> libGLU.so.1.3 and not libGLU.so.1 -> libGLU.so.1.3.402 and maybe: libOSMesa.so.3 -> libOSMesa.so.3.3 Thanks all ! On Sat, 2004-01-31 at 20:02, Felix K=FChling wrote: > On 31 Jan 2004 16:01:42 +0000 > S=E9rgio Monteiro Basto <ser...@ne...> wrote: >=20 > > ldd `which glxinfo` > > libGLU.so.1 =3D> /usr/local/lib/libGLU.so.1 (0x4002c000) > > libGL.so.1 =3D> /usr/lib/libGL.so.1 (0x400c7000) > > libXext.so.6 =3D> /usr/X11R6/lib/libXext.so.6 (0x402a0000) > > libX11.so.6 =3D> /usr/X11R6/lib/libX11.so.6 (0x402ad000) > > libpthread.so.0 =3D> /lib/i686/libpthread.so.0 (0x40382000) > > libm.so.6 =3D> /lib/i686/libm.so.6 (0x40396000) > > libc.so.6 =3D> /lib/i686/libc.so.6 (0x42000000) > > libSM.so.6 =3D> /usr/X11R6/lib/libSM.so.6 (0x403b9000) > > libICE.so.6 =3D> /usr/X11R6/lib/libICE.so.6 (0x403c1000) > > libXmu.so.6 =3D> /usr/X11R6/lib/libXmu.so.6 (0x403d8000) > > libXt.so.6 =3D> /usr/X11R6/lib/libXt.so.6 (0x403ed000) > > libXi.so.6 =3D> /usr/X11R6/lib/libXi.so.6 (0x40439000) > > libdl.so.2 =3D> /lib/libdl.so.2 (0x40441000) > > /lib/ld-linux.so.2 =3D> /lib/ld-linux.so.2 (0x40000000) > >=20 > > everything looks normal > > glxinfo is a little short because, I had comment v4l I thing=20 > > any clue ? >=20 > If you have the environment variable > LIBGL_DEBUG set to verbose then you should see messages about which DRI > driver is used and so on. That was missing completely in the output you > sent. Therefore I asked you to check if you're using the correct libGL. > Now it seems that you are using the right libGL since you have a link > from /usr/lib/libGL.so.1 to /usr/X11R6/lib/libGL.so.1 (your other mail). >=20 > But I noticed one more strange thing in your glxinfo output. The > renderer string indicates that you're using a standalone software Mesa > libGL: >=20 > OpenGL renderer string: Mesa X11 > OpenGL version string: 1.3 Mesa 4.0.2 >=20 > With direct rendering I get this: >=20 > OpenGL renderer string: Mesa DRI SAVAGE Linux_1.1.18 > OpenGL version string: 1.2 Mesa 5.0.2 >=20 > With indirect rendering: >=20 > OpenGL renderer string: Mesa GLX Indirect > OpenGL version string: 1.4 Mesa 5.0.2 >=20 > So something is (or was) not installed correctly. It was not using the > right libGL. Did you make the symbolic links after you sent glxinfo.txt? > What is your glxinfo output now (with LIBGL_DEBUG=3Dverbose)? If you're > using the right libGL then you should get one of the last two renderer > strings above. >=20 > >=20 > > On Sat, 2004-01-31 at 15:30, Felix K=FChling wrote: > [snip] >=20 > Felix --=20 S=E9rgio M. B. |