Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 27 Sep 2002 23:11:44 -0700
From:      Corey Holcomb-Hockin <crsntlvs@ipeg.com>
To:        freebsd-multimedia <freebsd-multimedia@freebsd.org>
Subject:   Re: Fxtv crash
Message-ID:  <3D954820.1040706@ipeg.com>
References:  <3D93E29D.9080702@ipeg.com> <1033149309.894.15.camel@anholt.dyndns.org> <3D952B77.90001@ipeg.com> <200209272308.17405.soralx@cydem.zp.ua>

next in thread | previous in thread | raw e-mail | index | archive | help
soralx@cydem.zp.ua wrote:

>>mga(0): [drm] DRIScreenInit failed.  Disabling DRI
>>error message when I startx.
>>    
>>
>'dri' works well for me (about 550fps in `glxgears`;
>X11 from ports, WITH_MATROX_GXX_DRIVER)
>`mgapdesk` coredumps for some reason, though
>also, 'dri' doesn't want to work under linux emu
>`/usr/compat/linux/usr/X11R6/bin/glxinfo` crashes the X-server,
>and `/usr/compat/linux/usr/X11R6/bin/gears` says that
>"/usr/compat/linux/usr/X11R6/bin/gears: relocation error:
>/lib/libglut.so.3: undefined symbol: XmuLookupStandardColormap"
>(probably because 'dri-devel' and 'linux_dri' versions don't match
>in ports)
>
>===========/etc/X11/XF86Config=================
>Section "Module"
>	Load  "xie"
>	Load  "pex5"
>	Load  "glx"
>	Load  "dri"
>	Load  "dbe"
>	Load  "record"
>	Load  "extmod"
>	Load  "type1"
>	Load  "drm"
>EndSection
>
>Section "DRI"
>              Mode 0600
>EndSection
>
>Section "Device"
>	Option "DRI" "1"
>	Option "SWcursor" "1"
>	Option "HWcursor" "0"
>	Option "AGPMode" "4"
>	Option "NoAccel" "0"
>	Identifier  "Card0"
>	Driver      "mga"
>	ChipSet     "mgag550"
>	Card        "Matrox mgag550"
>	BusID       "PCI:1:0:0"
>	VideoRAM    32768
>EndSection
>==============================================
>
>27.09.2002; 22:52:09
>[SorAlx]  http://cydem.zp.ua/
>
>To Unsubscribe: send mail to majordomo@FreeBSD.org
>with "unsubscribe freebsd-multimedia" in the body of the message
>
>  
>
What motherboard do you have?  I'm guessing my problem has to do with 
either my motherboard or just that its uses a athlon cpu.  More likely 
just the motherboard.  I had trouble using Xfree86 4 at all with FreeBSD 
4.5.  That problem got fixed because someone had almost the same model 
of motherboard I knew enough to fix it.  I don't know enough to fix this 
problem myself.

Corey Holcomb-Hockin





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?3D954820.1040706>