Date: Mon, 22 Jan 2001 11:22:45 +0100 From: "Karel J. Bosschaart" <karelj@wop21.wop.wtb.tue.nl> To: Chris <cc@137.org> Cc: David Syphers <dbsypher@uchicago.edu>, current@FreeBSD.ORG Subject: Re: XFree86 4.0.2 Message-ID: <20010122112245.A77620@wop21.wop.wtb.tue.nl> In-Reply-To: <3A6B3D84.58831A5@137.org>; from cc@137.org on Sun, Jan 21, 2001 at 01:50:28PM -0600 References: <4.3.2.7.2.20010121013438.00ba9100@nsit-popmail.uchicago.edu> <20010121023208.A63679@citusc17.usc.edu> <3A6B3D84.58831A5@137.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Jan 21, 2001 at 01:50:28PM -0600, Chris wrote: > > If you are currently running 4.0.1, I would seriously recommend skipping > this > minor revision. I have run into a multitude of problems with it, and am now > back right where I started. > > One, is the lack of DRM support for the matrox cards anymore. The kernel > module has a version number in it, which is less than that required by the > DRM system. > At the moment I'm using XFree86-4.0.2_5 with Matrox G400 and DRM, on 4.2-STABLE. I could get the correct DRM module version compiled thanks to a bunch of patches that someone has sent me. Occasionally things lock up and I need to restart remotely (killing -9 the offending process does not help). This happens only when using drm. > It won't insert the module until you update this--so it appears > that no one is actually using it. FYI, http://wop21.wop.wtb.tue.nl/freebsd/hwaccel.html describes how to install drm/G400 with XFree86-4.0.1. I'm getting a few hits a day, so I suppose there is some interest, although the patches are getting only 20 % of the number of hits on the guidelines, which might be more indicative for the people actually trying. > Another, is that there seem to be delays in the event stream, making > interactive performance terrible. One example: When I go to move a window, > I > start dragging it, moving the outline as I go. Then I unclick, yet the > frame > is still visible. I actually have to move the mouse more to get the window > move to take effect. There are other cases, where it appears to lose events > all together--like clicking on windows to raise them, or with menus. > Hmm, I don't have such troubles. Only minor problem I have, besides above mentioned drm related things, is that VMware doesn't correctly use Full Screen mode. Karel. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010122112245.A77620>