Date: Sat, 5 Jan 2002 19:43:41 +0100 From: Bjarne Wichmann Petersen <freebsd.nospam@mekanix.dk> To: Randall Hopper <aa8vb@nc.rr.com>, Bjarne Wichmann Petersen <freebsd.nospam@mekanix.dk> Cc: freebsd-multimedia@FreeBSD.ORG Subject: Re: OpenGL Message-ID: <20020105184239.SRVI27566.fepA.post.tele.dk@there> In-Reply-To: <20020105120024.A1094@nc.rr.com> References: <20020103212324.ILQT16766.fepD.post.tele.dk@there> <20020105090159.PUCN27566.fepA.post.tele.dk@there> <20020105120024.A1094@nc.rr.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Saturday 05 January 2002 18:00, Randall Hopper wrote: > 1) Verifying your libGL is the DRI-enabled one (it almost certainly is, but > just to double-check): > > strings /usr/X11R6/lib/libGL.so.1 | grep XF86DRI Looks like the real thing: XF86DRIQueryExtension XF86DRIQueryVersion XF86DRIQueryDirectRenderingCapable XF86DRIOpenConnection XF86DRIAuthConnection XF86DRICloseConnection XF86DRIGetClientDriverName XF86DRICreateContext XF86DRIDestroyContext XF86DRICreateDrawable XF86DRIDestroyDrawable XF86DRIGetDrawableInfo XF86DRIGetDeviceInfo XF86DRIOpenFullScreen XF86DRICloseFullScreen XF86DRIQueryDirectRenderingCapable failed XF86DRIQueryDirectRenderingCapable returned false XF86DRIQueryExtension failed XF86DRIQueryVersion failed XF86DRIGetClientDriverName failed XF86DRIGetClientDriverName: %d.%d.%d %s > 2) DRM module loaded > > kldstat | grep mga 7 1 0xc1483000 16000 mga.ko It seems loaded > 3) DRI device perms All tests passes ;) > 4) glxinfo probes drm, and renderer acknowledges DRI enabled: > > setenv LIBGL_DEBUG verbose > > glxinfo | grep DRI libGL: XF86DRIGetClientDriverName: 1.0.0 mga libGL: trying /usr/X11R6/lib/modules/dri/mga_dri.so libGL: trying /usr/X11R6/lib/modules/dri/mga_dri.so OpenGL renderer string: Mesa DRI G400 20010321 AGP 1x x86/MMX Looks ok > 5) DRM module claimed your graphics card: > > # pciconf -l | grep drm > drm0@pci1:5:0: class=0x030000 card=0x0641102b chip=0x0525102b rev=0x82 > \ hdr=0x00 drm0@pci1:0:0: class=0x030000 card=0x0338102b chip=0x0525102b rev=0x04 hdr=0x00 > Just for kicks you might try changing your desktop to 640x480x16bpp, and > then kick off tuxracer. That'll probably give you over 6MB more of > video RAM for texture. *This* actually made all the difference. I just pulled 50-60 FPS out of tuxracer. But shouldn't X release that memory it isn't utilizing when running in fullscreen mode? > 8) XFree86.0.log acknowledges DRI enabled?: > > MGA(0): Direct rendering enabled > (I e-mailed you my complete XFree86.0.log in case you want to compare). My XFree-log looks very similar to yours. Only thing I found could be interesting was: (II) MGA(0): [agp] 12288 kB allocated with handle 0xc1443040 ... (II) MGA(0): Reserved 1376 kb for textures at offset 0xea8000 Shouldn't have any influence though, I've just got a smaller card. BTW, what's this dpms I see in your log? > 10) Now I'm down to the wild guesses. I've read that not having an IRQ > assigned to your video card can cause big slowdowns, so might check > that: > > dmesg | grep -i drm0 drm0: <Matrox G400 (AGP)> mem 0xd7000000-0xd77fffff,0xd6000000-0xd6003fff,0xd4000000-0xd5ffffff irq 10 at device 0.0 on pci1 Thanks for all the help.... looks like it's time to go shopping for a new Matrox-card ;) Bjarne -- Homepage: http://www.mekanix.dk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-multimedia" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020105184239.SRVI27566.fepA.post.tele.dk>